xfs: writepage always has buffers
PATCH 1/1 xfs: writepage always has buffers
These days we always have buffers thanks to ->page_mkwrite. And we already have an assert a few lines above tripping in case that was not true due to a bug.
fs/xfs/linux-2.6/xfs_aops.c +0 -7
@@ -1072,13 +1072,6 @@ xfs_vm_writepage(if ((current->flags &PF_FSTRANS ) && (delalloc || unwritten)) goto out_fail; -/* -* Delay hooking up buffer heads until we have -* made our go/no-go decision. -*/ -if (!page_has_buffers (page)) -create_empty_buffers (page,1 << inode->i_blkbits,0 ); -/* Is this page beyond the end of the file? */ offset =i_size_read (inode); end_index = offset >>PAGE_CACHE_SHIFT ;
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
ping?
Quoted 25 lines · Christoph Hellwig
These days we always have buffers thanks to ->page_mkwrite. And we already have an assert a few lines above tripping in case that was not true due to a bug.
Signed-off-by Christoph Hellwig <[email protected]>Index:
xfs-dev/fs/xfs/linux-2.6/xfs_aops.c
===================================================================fs/xfs/linux-2.6/xfs_aops.c +0
-7@@ -1072,13 +1072,6 @@ xfs_vm_writepage(if ((current->flags &PF_FSTRANS ) && (delalloc || unwritten)) goto out_fail; -/* -* Delay hooking up buffer heads until we have -* made our go/no-go decision. -*/ -if (!page_has_buffers (page)) -create_empty_buffers (page,1 << inode->i_blkbits,0 ); -/* Is this page beyond the end of the file? */ offset =i_size_read (inode); end_index = offset >>PAGE_CACHE_SHIFT ;
Quoted 4 lines
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
---end quoted text---
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 3 lines · Christoph Hellwig
These days we always have buffers thanks to ->page_mkwrite. And we already have an assert a few lines above tripping in case that was not true due to a bug.
Should the ASSERT() be made stronger (i.e., BUG_ON())? Looks to me like we'll crash if it ever happens in a non-debug kernel, and a BUG() call would more directly tell us what the problem was...
In an case, this looks OK to me.
Quoted 1 line
Signed-off-by Christoph Hellwig <[email protected]>
Quoted 19 lines
Index:
xfs-dev/fs/xfs/linux-2.6/xfs_aops.c
===================================================================fs/xfs/linux-2.6/xfs_aops.c +0
-7@@ -1072,13 +1072,6 @@ xfs_vm_writepage(if ((current->flags &PF_FSTRANS ) && (delalloc || unwritten)) goto out_fail; -/* -* Delay hooking up buffer heads until we have -* made our go/no-go decision. -*/ -if (!page_has_buffers (page)) -create_empty_buffers (page,1 << inode->i_blkbits,0 ); -/* Is this page beyond the end of the file? */ offset =i_size_read (inode); end_index = offset >>PAGE_CACHE_SHIFT ;
Quoted 4 lines
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 9 lines · Alex Elder
Quoted 3 lines · Christoph Hellwig
These days we always have buffers thanks to ->page_mkwrite. And we already have an assert a few lines above tripping in case that was not true due to a bug.
Should the
ASSERT()be made stronger (i.e.,BUG_ON())? Looks to me like we'll crash if it ever happens in a non-debug kernel, and aBUG()call would more directly tell us what the problem was...
The crash tells it quite directly as well, the ASSERT is there more as a documentation of what we require.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs