linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.2-rc1-mm1
Date: Thu, 22 Jan 2004 16:41:24 -0800	[thread overview]
Message-ID: <20040123004124.GC16052@kroah.com> (raw)
In-Reply-To: <20040123002414.GA21151@parcelfarce.linux.theplanet.co.uk>

On Fri, Jan 23, 2004 at 12:24:14AM +0000, viro@parcelfarce.linux.theplanet.co.uk wrote:
> On Thu, Jan 22, 2004 at 03:38:54PM -0800, Greg KH wrote:
> > On Thu, Jan 22, 2004 at 03:19:43PM +0000, viro@parcelfarce.linux.theplanet.co.uk wrote:
> > > Greg, please, RTFS to see at which point do we decide which driver will
> > > be used by raw device.  It's _not_ RAW_SETBIND, it's open().  So where
> > > your symlink should point is undecided until the same point.
> > 
> > I don't care about which driver is used by the raw device, I care about
> > which block device the raw device is "bound" to.  That happens at
> > RAW_SETBIND time, right?  We do this in the line:
> > 	rawdev->binding = bdget(dev);
> 
> No.  We have no fscking idea what device it is.  All we know is a device
> number.  No driver-related activity (including insmod, etc.) happens
> until open().
> 
> Among other things, RAW_SETBIND on inexistent device is a legitimate use.
> Which kills your "create a symlink at RAW_SETBIND" immediately - there
> might very well be nothing for it to point to.
> 
> You can bind /dev/raw0 to 8:0, then attach USB disk and then open
> /dev/raw0.  That ends up with /dev/raw0 becoming a raw alias for
> that disk.

Ah, ok, I didn't realize this, thanks for making it much clearer.  My
patch is horribly wrong then.  I like Andrew's patch of just marking it
obsolete :)

Andrew, feel free to drop my raw sysfs patch from your -mm tree for now.

thanks,

greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-01-23  0:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22  9:35 2.6.2-rc1-mm1 Andrew Morton
2004-01-22 11:03 ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 15:19   ` 2.6.2-rc1-mm1 viro
2004-01-22 20:31     ` 2.6.2-rc1-mm1 Andrew Morton
2004-01-22 21:30       ` 2.6.2-rc1-mm1 Adrian Bunk
2004-01-22 23:38     ` 2.6.2-rc1-mm1 Greg KH
2004-01-23  0:24       ` 2.6.2-rc1-mm1 viro
2004-01-23  0:41         ` Greg KH [this message]
2004-01-22 11:05 ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 11:07 ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 11:12   ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 12:17   ` 2.6.2-rc1-mm1 Jeff Dike
2004-01-22 12:00     ` 2.6.2-rc1-mm1 Christoph Hellwig
2004-01-22 13:28       ` 2.6.2-rc1-mm1 Jeff Dike
2004-01-22 16:26 ` 2.6.2-rc1-mm1 (compile stats) John Cherry
2004-01-22 21:12 ` 2.6.2-rc1-mm1 Tom Rini

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=20040123004124.GC16052@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=viro@parcelfarce.linux.theplanet.co.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