From: Andries.Brouwer@cwi.nl
To: hch@caldera.de, torvalds@transmeta.com
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
linux-lvm@sistina.com, viro@math.psu.edu
Subject: Re: [linux-lvm] Re: [RFLART] kdev_t in ioctls
Date: Tue, 15 Jan 2002 20:44:55 GMT [thread overview]
Message-ID: <UTC200201152044.UAA324996.aeb@cwi.nl> (raw)
On Mon, 14 Jan 2002, Christoph Hellwig wrote:
>
> I know - still it makes Linus' suggestion not work on ~90% of the
> systems.
It doesn't matter if user-land compilation breaks. As long as old binaries
work (and they will), we're fine.
User-land was _already_ broken. By virtue of using a type that it should
NOT have used.
If you want to use __kernel_dev_t, go ahead.
Linus
Yes. As everyone knows, one should not use kernel includes.
On the other hand, having local copies of everything is also
a bad habit, to be avoided when possible.
With Linux it is generally impossible to avoid going to local
copies, but so far losetup survived with the construction
% cat loop.h
#include <linux/posix_types.h>
#undef dev_t
#define dev_t __kernel_dev_t
#include <linux/loop.h>
#undef dev_t
%
Yecch.
(This is terribly ugly, but the alternative may be even worse:
lots of #ifdef's testing architecture etc.)
It is a pity that dev_t, a type that is not used anywhere in the
kernel except at the interface with user space, is a different
type from what user space uses.
Andries
next reply other threads:[~2002-01-15 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 20:44 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-14 17:56 [RFLART] kdev_t in ioctls Alexander Viro
2002-01-14 18:01 ` Linus Torvalds
2002-01-13 17:17 ` [linux-lvm] " Joe Thornber
2002-01-14 18:08 ` Christoph Hellwig
2002-01-14 18:13 ` Christoph Hellwig
2002-01-14 18:56 ` Alan Cox
2002-01-14 18:45 ` Christoph Hellwig
2002-01-14 18:50 ` Linus Torvalds
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=UTC200201152044.UAA324996.aeb@cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox