summaryrefslogtreecommitdiffstats
path: root/drivers/nubus
diff options
context:
space:
mode:
authorAlexey Korolev <akorolev@infradead.org>2008-04-14 21:45:06 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2008-04-15 00:43:14 +0200
commitabe2f41430770270a1512bf78f489284bfbdbd04 (patch)
treed40b557f0ce346a56de428dc520816b19e74d4df /drivers/nubus
parentlocks: fix possible infinite loop in fcntl(F_SETLKW) over nfs (diff)
downloadlinux-abe2f41430770270a1512bf78f489284bfbdbd04.tar.xz
linux-abe2f41430770270a1512bf78f489284bfbdbd04.zip
JFFS2 Fix of panics caused by wrong condition for hole frag creation in write_begin
This fixes a regression introduced in commit 205c109a7a96d9a3d8ffe64c4068b70811fef5e8 when switching to write_begin/write_end operations in JFFS2. The page offset is miscalculated, leading to corruption of the fragment lists and subsequently to memory corruption and panics. [ Side note: the bug is a fairly direct result of the naming. Nick was likely misled by the use of "offs", since we tend to use the notion of "offset" not as an absolute position, but as an offset _within_ a page or allocation. Alternatively, a "pgoff_t" is a page index, but not a byte offset - our VM naming can be a bit confusing. So in this case, a VM person would likely have called this a "pos", not an "offs", or perhaps talked about byte offsets rather than page offsets (since it's counted in bytes, not pages). - Linus ] Signed-off-by: Alexey Korolev <akorolev@infradead.org> Signed-off-by: Vasiliy Leonenko <vasiliy.leonenko@mail.ru> Signed-off-by: David Woodhouse <dwmw2@infradead.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/nubus')
0 files changed, 0 insertions, 0 deletions