aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@infradead.org>2010-11-10 21:39:11 +0000
committerAlex Elder <aelder@sgi.com>2010-11-10 15:51:10 -0600
commitece413f59f257682de4a2e2e42af33b016af53f3 (patch)
treefe26d60458a4bfbd39e7e319e41c0ceca011914d /Documentation
parentc6f6cd0608b1826ee1797cf57a808416e4bdb806 (diff)
downloadmrst-s0i3-test-ece413f59f257682de4a2e2e42af33b016af53f3.tar.gz
mrst-s0i3-test-ece413f59f257682de4a2e2e42af33b016af53f3.tar.xz
mrst-s0i3-test-ece413f59f257682de4a2e2e42af33b016af53f3.zip
xfs: remove incorrect assert in xfs_vm_writepage
In commit 20cb52ebd1b5ca6fa8a5d9b6b1392292f5ca8a45, titled "xfs: simplify xfs_vm_writepage" I added an assert that any !mapped and uptodate buffers are not dirty. That asserts turns out to trigger a lot when running fsx on filesystems with small block sizes. The reason for that is that the assert is simply incorrect. !mapped and uptodate just mean this buffer covers a hole, and whenever we do a set_page_dirty we mark all blocks in the page dirty, no matter if they have data or not. So remove the assert, and update the comment above the condition to match reality. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Alex Elder <aelder@sgi.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions