From: Chris Wright <chrisw@osdl.org>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Chris Wright <chrisw@osdl.org>, Jan Kara <jack@suse.cz>,
Mark Wong <markw@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: ext3 journalling BUG on full filesystem
Date: Thu, 24 Mar 2005 13:33:02 -0800 [thread overview]
Message-ID: <20050324213302.GJ28536@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1111699467.1995.94.camel@sisko.sctweedie.blueyonder.co.uk>
* Stephen C. Tweedie (sct@redhat.com) wrote:
> On Thu, 2005-03-24 at 19:38, Chris Wright wrote:
>
> > OK, good to know. When I last checked you were working on a higher risk
> > yet more complete fix, and I thought we'd wait for that one to stabilize.
> > Looks like the one Jan attached is the better -stable candidate?
>
> Definitely; it's the one I gave akpm. The lock reworking is going to
> remove one layer of locks, so it's worthwhile from that point of view;
> but it's longer-term, and I don't know for sure of any paths to chaos
> with that simpler journal_unmap_buffer() fix in place. (It's just very
> hard to _prove_ all cases are correct without the locking rework.)
Great, I'll add to -stable queue. Thanks Stephen.
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-03-24 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 20:21 ext3 journalling BUG on full filesystem Mark Wong
2005-03-23 22:00 ` Anton Blanchard
2005-03-23 22:17 ` Darren Williams
2005-03-24 10:39 ` Jan Kara
2005-03-24 19:09 ` Stephen C. Tweedie
2005-03-24 19:38 ` Chris Wright
2005-03-24 21:24 ` Stephen C. Tweedie
2005-03-24 21:33 ` Chris Wright [this message]
2005-03-24 8:37 ` Jacky Malcles
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=20050324213302.GJ28536@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=markw@osdl.org \
--cc=sct@redhat.com \
--cc=stable@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