From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jan Kara <jack@suse.cz>
Cc: Josh Hunt <johunt@akamai.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"sandeen@redhat.com" <sandeen@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC][PATCH] ext2: Resolve i_nlink race in ext2_rename
Date: Tue, 1 Mar 2011 12:15:30 +0000 [thread overview]
Message-ID: <20110301121530.GH22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20110228205652.GH20805@quack.suse.cz>
On Mon, Feb 28, 2011 at 09:56:52PM +0100, Jan Kara wrote:
> On Mon 28-02-11 12:17:55, Josh Hunt wrote:
> > On 02/28/2011 09:57 AM, Jan Kara wrote:
> > > So I took your patch and used a changelog from mine as I find it more
> > > descriptive. The resulting patch is in my tree (and attached).
> > >
> > > Honza
> > Jan
> >
> > Thanks. We should probably send this to the stable guys as well.
> Good point. Made sure they are warned when the patch gets in.
I have an equivalent of that for other affected fs in my tree; will go
to Linus in an hour or so.
next prev parent reply other threads:[~2011-03-01 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 6:21 [RFC][PATCH] ext2: Resolve i_nlink race in ext2_rename Josh Hunt
2011-02-24 6:37 ` Al Viro
2011-02-24 6:42 ` fat64 implementation Keshava Munegowda
2011-02-24 11:20 ` [RFC][PATCH] ext2: Resolve i_nlink race in ext2_rename Jan Kara
2011-02-24 20:18 ` Josh Hunt
2011-02-25 7:38 ` Marco Stornelli
2011-02-28 17:57 ` Jan Kara
2011-02-28 20:17 ` Josh Hunt
2011-02-28 20:56 ` Jan Kara
2011-03-01 12:15 ` Al Viro [this message]
2011-03-01 11:07 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2011-02-22 23:42 Josh Hunt
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=20110301121530.GH22723@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jack@suse.cz \
--cc=johunt@akamai.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).