Commit a9777845 authored by Ryusuke Konishi's avatar Ryusuke Konishi

nilfs2: fix oops due to inconsistent state in page with discrete b-tree nodes

Andrea Gelmini gave me a report that a kernel oops hit on a nilfs
filesystem with a 1KB block size when doing rsync.

This turned out to be caused by an inconsistency of dirty state
between a page and its buffers storing b-tree node blocks.

If the page had multiple buffers split over multiple logs, and if the
logs were written at a time, a dirty flag remained in the page even
every dirty flag in the buffers was cleared.

This will fix the failure by dropping the dirty flag properly for
pages with the discrete multiple b-tree nodes.
Reported-by: default avatarAndrea Gelmini <andrea.gelmini@gmail.com>
Signed-off-by: default avatarRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Tested-by: default avatarAndrea Gelmini <andrea.gelmini@gmail.com>
Cc: stable@kernel.org
parent ed680c4a
...@@ -1859,12 +1859,26 @@ static void nilfs_end_page_io(struct page *page, int err) ...@@ -1859,12 +1859,26 @@ static void nilfs_end_page_io(struct page *page, int err)
if (!page) if (!page)
return; return;
if (buffer_nilfs_node(page_buffers(page)) && !PageWriteback(page)) if (buffer_nilfs_node(page_buffers(page)) && !PageWriteback(page)) {
/* /*
* For b-tree node pages, this function may be called twice * For b-tree node pages, this function may be called twice
* or more because they might be split in a segment. * or more because they might be split in a segment.
*/ */
if (PageDirty(page)) {
/*
* For pages holding split b-tree node buffers, dirty
* flag on the buffers may be cleared discretely.
* In that case, the page is once redirtied for
* remaining buffers, and it must be cancelled if
* all the buffers get cleaned later.
*/
lock_page(page);
if (nilfs_page_buffers_clean(page))
__nilfs_clear_page_dirty(page);
unlock_page(page);
}
return; return;
}
__nilfs_end_page_io(page, err); __nilfs_end_page_io(page, err);
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment