From: Christoph Hellwig <hch@infradead.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix bmap-vs-truncate race
Date: Tue, 31 Mar 2009 13:54:52 -0400 [thread overview]
Message-ID: <20090331175451.GA19484@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0903301518120.23576@hs20-bc2-1.build.redhat.com>
On Mon, Mar 30, 2009 at 03:20:24PM -0400, Mikulas Patocka wrote:
> Hi
>
> I'm submitting this patch for 2.6.30 merge window.
Please not. i_alloc_sem is really a horrible hack needed for a couple
filesystems only and we should not leak it into more generic code but
rather move the few instances into the filesystem.
next prev parent reply other threads:[~2009-03-31 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 19:20 [PATCH] fix bmap-vs-truncate race Mikulas Patocka
2009-03-31 14:48 ` Aneesh Kumar K.V
2009-03-31 17:54 ` Christoph Hellwig [this message]
2009-03-31 22:42 ` Mikulas Patocka
2009-04-01 11:36 ` Al Viro
2009-04-02 23:22 ` Mikulas Patocka
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=20090331175451.GA19484@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@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;
as well as URLs for NNTP newsgroup(s).