From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
chris.mason@oracle.com, linux-fsdevel@vger.kernel.org,
reiserfs-devel@vger.kernel.org
Subject: Re: [PATCH] reiserfs: use open_bdev_excl
Date: Thu, 7 Feb 2008 06:19:56 +0100 [thread overview]
Message-ID: <20080207051956.GA5229@lst.de> (raw)
In-Reply-To: <20080206211627.9683a9e2.akpm@linux-foundation.org>
On Wed, Feb 06, 2008 at 09:16:27PM -0800, Andrew Morton wrote:
> On Thu, 7 Feb 2008 05:45:13 +0100 Christoph Hellwig <hch@lst.de> wrote:
>
> > On Wed, Dec 26, 2007 at 04:31:01PM +0100, Christoph Hellwig wrote:
> > > Use the proper helper to open a blockdevice by name for filesystem
> > > use, this makes sure it's properly claimed (also added for open-by-number)
> > > and gets rid of the struct file abuse.
> > >
> > > Tested by mounting a reiserfs filesystem with external journal.
> >
> > Folks, what do we do with this patch? It's been out for more than a
> > month but didn't actually get picked up in any tree.
>
> It's still sitting in the great pile of things I got sent over Christmas
> and haven't looked at yet. It didn't look like a bugfix.
Well, it's fixing that reiserds doesn't bd_claim it's journal device so
people can open the block device with O_EXCL against the documetned
semantics. It's probably also fixing various corner cases that
open_bdev_excl deals with and a hand-crafted filp_open doesn't.
> > I'd really like
> > to see this going in soon.
>
> How come?
I just hate sitting on a stack of patches. Even more so if I'd like to
see the public API removed in there eventually go away.
next prev parent reply other threads:[~2008-02-07 5:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 15:31 [PATCH] reiserfs: use open_bdev_excl Christoph Hellwig
2008-02-07 4:45 ` Christoph Hellwig
2008-02-07 5:16 ` Andrew Morton
2008-02-07 5:19 ` Christoph Hellwig [this message]
2008-04-29 18:13 ` Christoph Hellwig
2008-04-29 18:24 ` Andrew Morton
2008-04-29 22:49 ` Edward Shishkin
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=20080207051956.GA5229@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=reiserfs-devel@vger.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;
as well as URLs for NNTP newsgroup(s).