From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>, Andrea Arcangeli <andrea@suse.de>
Subject: [patch] fix race in __block_prepare_write (again)
Date: Thu, 21 Apr 2005 16:14:06 +1000 [thread overview]
Message-ID: <1114064046.5182.13.camel@npiggin-nld.site> (raw)
[-- Attachment #1: Type: text/plain, Size: 79 bytes --]
... I somehow didn't send it to Andrew last time.
--
SUSE Labs, Novell Inc.
[-- Attachment #2: __block_prepare_write-bug.patch --]
[-- Type: text/x-patch, Size: 1151 bytes --]
Fix a race where __block_prepare_write can leak out an in-flight
read against a bh if get_block returns an error. This can lead to
the page becoming unlocked while the buffer is locked and the read
still in flight. __mpage_writepage BUGs on this condition.
BUG sighted on a 2-way Itanium2 system with 16K PAGE_SIZE running
fsstress -v -d $DIR/tmp -n 1000 -p 1000 -l 2
where $DIR is a new ext2 filesystem with 4K blocks that is quite
small (causing get_block to fail often with -ENOSPC).
Signed-off-by: Nick Piggin <nickpiggin@yahoo.com.au>
Index: linux-2.6/fs/buffer.c
===================================================================
--- linux-2.6.orig/fs/buffer.c 2005-04-21 11:55:17.549614278 +1000
+++ linux-2.6/fs/buffer.c 2005-04-21 15:55:41.483826075 +1000
@@ -1988,6 +1988,7 @@
*wait_bh++=bh;
}
}
+out:
/*
* If we issued read requests - let them complete.
*/
@@ -1996,8 +1997,9 @@
if (!buffer_uptodate(*wait_bh))
return -EIO;
}
- return 0;
-out:
+ if (!err)
+ return err;
+
/*
* Zero out any newly allocated blocks to avoid exposing stale
* data. If BH_New is set, we know that the block was newly
next reply other threads:[~2005-04-21 6:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 6:14 Nick Piggin [this message]
2005-04-21 7:01 ` Anton Altaparmakov
2005-04-21 7:10 ` Anton Altaparmakov
2005-04-21 7:20 ` Nick Piggin
2005-04-21 7:31 ` Anton Altaparmakov
2005-04-22 15:10 ` Nikita Danilov
2005-04-22 15:50 ` Anton Altaparmakov
2005-04-24 21:24 ` Andrew Morton
2005-04-25 7:44 ` Anton Altaparmakov
2005-04-21 7:13 ` Nick Piggin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1114064046.5182.13.camel@npiggin-nld.site \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®