From: Jan Kara <jack@suse.cz>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Jan Kara <jack@suse.cz>, Eric Sandeen <sandeen@redhat.com>,
linux-ext4@vger.kernel.org, mszeredi@suse.cz,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: EXT4-fs (dm-1): Couldn't remount RDWR because of unprocessed orphan inode list
Date: Sat, 10 Sep 2011 22:04:14 +0200 [thread overview]
Message-ID: <20110910200414.GA6709@quack.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.01.1109091809180.9183@trent.utfs.org>
On Fri 09-09-11 18:11:26, Christian Kujau wrote:
> On Thu, 8 Sep 2011 at 20:51, Jan Kara wrote:
> > There's race where VFS remount code can race with unlink and result will
> > be unlinked file in orphan list on read-only filesystem. Christian seems to
> > be hitting this race. Miklos Szeredi has patches
> > (http://lkml.indiana.edu/hypermail/linux/kernel/1108.3/00169.html) to
> > mostly close this hole but they're waiting for Al to find time to look at
> > them / merge them AFAIK.
>
> While these patches are still pending review, are they "dangerous" to
> apply? If not, I'd like to volunteer as a tester :-)
As far as I saw them, they should be pretty safe. So feel free to test
them.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2011-09-10 20:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 21:00 EXT4-fs (dm-1): Couldn't remount RDWR because of unprocessed orphan inode list Christian Kujau
2011-09-06 16:17 ` Eric Sandeen
2011-09-06 16:37 ` Christian Kujau
2011-09-06 16:44 ` Eric Sandeen
2011-09-06 18:14 ` Christian Kujau
2011-09-08 18:51 ` Jan Kara
2011-09-10 1:11 ` Christian Kujau
2011-09-10 20:04 ` Jan Kara [this message]
2011-09-13 4:52 ` Christian Kujau
2011-09-16 3:49 ` Christian Kujau
2011-09-16 12:04 ` Amir Goldstein
2011-09-16 12:17 ` Christian Kujau
2011-09-16 12:36 ` Amir Goldstein
2011-10-05 18:03 ` Jan Kara
2011-10-06 1:34 ` Christian Kujau
2011-10-06 10:12 ` Toshiyuki Okajima
2011-10-11 8:45 ` Miklos Szeredi
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=20110910200414.GA6709@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=mszeredi@suse.cz \
--cc=sandeen@redhat.com \
--cc=viro@ZenIV.linux.org.uk \
/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