All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Josh Hunt <johunt@akamai.com>
Cc: Jan Kara <jack@suse.cz>, Al Viro <viro@ZenIV.linux.org.uk>,
	"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: Mon, 28 Feb 2011 21:56:52 +0100	[thread overview]
Message-ID: <20110228205652.GH20805@quack.suse.cz> (raw)
In-Reply-To: <4D6C02F3.7070209@akamai.com>

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.

								Honza

-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2011-02-28 20:56 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 [this message]
2011-03-01 12:15             ` Al Viro
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=20110228205652.GH20805@quack.suse.cz \
    --to=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 \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.