All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: torvalds@transmeta.com, viro@math.psu.edu
Cc: Nikita@Namesys.COM, alessandro.suardi@oracle.com,
	andries.brouwer@cwi.nl, jgarzik@mandrakesoft.com,
	linux-kernel@vger.kernel.org
Subject: Re: 2.5.2-pre7 still missing bits of kdev_t
Date: Fri, 4 Jan 2002 19:24:24 GMT	[thread overview]
Message-ID: <UTC200201041924.TAA230416.aeb@cwi.nl> (raw)

    From viro@math.psu.edu Fri Jan  4 19:11:10 2002

    On Fri, 4 Jan 2002, Linus Torvalds wrote:

    > On Fri, 4 Jan 2002, Jeff Garzik wrote:
    > >
    > > As mentioned to viro on IRC, I think init_special_inode should take
    > > major and minor arguments, to nudge the filesystem implementors into
    > > thinking that major and minor should be treated separately, and be
    > > given additional thought as to how they are encoded on-disk.
    > 
    > Yes. If somebody sends me a patch, I'll apply it in a jiffy.

    Guys, wait a minute with that.  There is a related issue (->i_rdev
    becoming dev_t) and I'd rather see it handled first.

Those are independent issues.

If init_special_inode() has major,minor arguments instead of
the present rdev, then the line

	inode->i_rdev = to_kdev_t(rdev);

just becomes

	inode->i_rdev = mk_kdev(major,minor);

I consider every occurrence of mk_kdev() and of to_kdev_t()
a flaw in the kernel, so this change does not make things
better or worse inside init_special_inode().

Andries

             reply	other threads:[~2002-01-04 19:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 19:24 Andries.Brouwer [this message]
2002-01-04 21:10 ` 2.5.2-pre7 still missing bits of kdev_t Alexander Viro
2002-01-04 21:14   ` Linus Torvalds
2002-01-05  0:10     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-01-04 19:32 Andries.Brouwer
2002-01-04 13:21 Andries.Brouwer
2002-01-04  1:47 Andries.Brouwer
2002-01-04  0:05 Alessandro Suardi
2002-01-04  0:13 ` Jeff Garzik
2002-01-04  2:32   ` Linus Torvalds
2002-01-04  6:52     ` Jeff Garzik
2002-01-04 16:45       ` Linus Torvalds
2002-01-04 17:34         ` Nikita Danilov
2002-01-04 17:51           ` Jeff Garzik
2002-01-04 17:53             ` Linus Torvalds
2002-01-04 18:11               ` Alexander Viro

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=UTC200201041924.TAA230416.aeb@cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=Nikita@Namesys.COM \
    --cc=alessandro.suardi@oracle.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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.