Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:include\linux\buffer_head.h Create Date:2022-07-28 12:16:05
Last Modify:2020-03-12 14:18:49 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:buffer_dirty

Proto:static inline __attribute__((__always_inline__)) int buffer_dirty(const struct buffer_head *bh)

Type:int

Parameter:

TypeParameterName
const struct buffer_head *bh
121  Return If __builtin_constant_p( Is dirty ) Then constant_test_bit(( Is dirty ), ( & buffer state bitmap (see above) )) Else variable_test_bit(( Is dirty ), ( & buffer state bitmap (see above) ))
Caller
NameDescribe
buffer_check_dirty_writebackReturns if the page has dirty or writeback buffers. If all the buffers* are unlocked and clean then the PageDirty information is stale. If* any of the pages are locked, it is assumed they are locked for IO.
write_boundary_blockCalled when we've recently written block `bblock', and it is known that* `bblock' was for a buffer_boundary() buffer. This means that the block at* `bblock + 1' is probably a dirty indirect block. Hunt it down and, if it's* dirty, schedule it for IO
fsync_buffers_list
remove_inode_buffersRemove any clean buffers from the inode's buffer list. This is called* when we're trying to free the inode itself. Those buffers can pin it.* Returns true if all buffers were removed.
mark_buffer_dirtymark_buffer_dirty - mark a buffer_head as needing writeout*@bh: the buffer_head to mark dirty* mark_buffer_dirty() will set the dirty bit against the buffer, then set* its backing page dirty, then tag the page as dirty in the page cache* and then attach
__block_write_full_pageWhile block_write_full_page is writing back the dirty buffers under* the page lock, whoever dirtied the buffers may decide to clean them* again at any time
__mpage_writepage