From: Andries.Brouwer@cwi.nl
To: corryk@us.ibm.com, linux-kernel@vger.kernel.org
Cc: joe@fib011235813.fsnet.co.uk, lvm-devel@sistina.com
Subject: struct dm_ioctl
Date: Wed, 26 Mar 2003 12:27:29 +0100 (MET) [thread overview]
Message-ID: <UTC200303261127.h2QBRTt05048.aeb@smtp.cwi.nl> (raw)
The main users of dev_t in the userspace-kernel interface
are mknod and stat. But there is a small collection of
more obscure interfaces that use a dev_t parameter
(like the ustat system call) or a dev_t field in a
parameter struct (for example, struct loopinfo,
struct nfsctl_export, struct dm_ioctl).
It is almost always a mistake to have an interface
with a dev_t field, since nobody knows the size of
a dev_t field. The kernel size differs from the user
space size, the libc5 size differs from the glibc size.
A struct with such a field therefore has unknown size,
the fields following the dev_t field have unknown offset,
and lots of troubles arise.
Such interfaces are broken from the start.
But there are a few and we must deal with them one by one.
One is struct dm_ioctl. Google tells me that it was
noticed already that it defined a broken interface,
and Kevin Corry submitted a patch against 2.5.51.
Today this has not been applied yet.
What is the status? Should I resubmit that patch?
[http://marc.theaimsgroup.com/?l=linux-kernel&m=103956089203199&w=3]
Andries
next reply other threads:[~2003-03-26 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 11:27 Andries.Brouwer [this message]
2003-03-26 11:34 ` Christoph Hellwig
2003-03-26 12:48 ` Joe Thornber
2003-03-27 0:49 ` Andrew Morton
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=UTC200303261127.h2QBRTt05048.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=corryk@us.ibm.com \
--cc=joe@fib011235813.fsnet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lvm-devel@sistina.com \
/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
all inboxes | Powered by JetHome®