ext4: remove vestiges of nobh support
The nobh option was only supported for writeback mode, but given that all write paths actually create buffer heads it effectively was a no-op already. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
这个提交包含在:
@@ -313,17 +313,15 @@ static inline int ext4_should_writeback_data(struct inode *inode)
|
||||
* This function controls whether or not we should try to go down the
|
||||
* dioread_nolock code paths, which makes it safe to avoid taking
|
||||
* i_mutex for direct I/O reads. This only works for extent-based
|
||||
* files, and it doesn't work for nobh or if data journaling is
|
||||
* enabled, since the dioread_nolock code uses b_private to pass
|
||||
* information back to the I/O completion handler, and this conflicts
|
||||
* with the jbd's use of b_private.
|
||||
* files, and it doesn't work if data journaling is enabled, since the
|
||||
* dioread_nolock code uses b_private to pass information back to the
|
||||
* I/O completion handler, and this conflicts with the jbd's use of
|
||||
* b_private.
|
||||
*/
|
||||
static inline int ext4_should_dioread_nolock(struct inode *inode)
|
||||
{
|
||||
if (!test_opt(inode->i_sb, DIOREAD_NOLOCK))
|
||||
return 0;
|
||||
if (test_opt(inode->i_sb, NOBH))
|
||||
return 0;
|
||||
if (!S_ISREG(inode->i_mode))
|
||||
return 0;
|
||||
if (!(ext4_test_inode_flag(inode, EXT4_INODE_EXTENTS)))
|
||||
|
在新工单中引用
屏蔽一个用户