From: Andries.Brouwer@cwi.nl
To: bcrl@redhat.com, torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [resend PATCH] reserve BLKGETSIZE64 ioctl
Date: Mon, 3 Sep 2001 20:57:29 GMT [thread overview]
Message-ID: <200109032057.UAA36797@vlet.cwi.nl> (raw)
From: Ben LaHaise <bcrl@redhat.com>
Is there any problem with the patch below for reserving a 64 bit get block
device size ioctl?
+#define BLKBSZGET _IOR(0x12,110,sizeof(u64))
#define BLKBSZGET _IOR(0x12,112,sizeof(int))
Yes.
(1) As you can see you'll only get redefinition complaints.
In other words, there is a B too much in the ioctl name.
(2) We just concluded that 108-111 have been used for various
private purposes. If we avoid 108-111 in all official kernels
then nobody will be surprised if he ever uses some system
utility that uses one of these.
Thus, it is a very bad idea to want to use these again.
(3) Soon we'll all need a BLKGETSIZE64 ioctl, that gives
the size of a block device in bytes. Your proposed ioctl
gave the size in blocks if I recall correctly.
So, if you have to change the name and the number,
you might as well change the definition.
Andries
[We might reserve an area for private use - some ioctl numbers
that are guaranteed never to become part of an official kernel.]
next reply other threads:[~2001-09-03 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 20:57 Andries.Brouwer [this message]
2001-09-04 1:09 ` [resend PATCH] reserve BLKGETSIZE64 ioctl Ben LaHaise
-- strict thread matches above, loose matches on Subject: below --
2001-09-04 21:43 Andries.Brouwer
2001-09-04 22:27 ` Ben LaHaise
2001-09-04 13:50 Andries.Brouwer
2001-09-04 20:54 ` Ben LaHaise
[not found] <Pine.LNX.4.33.0109031119400.1610-100000@toomuch.toronto.re dhat.com>
2001-09-03 15:40 ` Anton Altaparmakov
2001-09-03 15:21 Ben LaHaise
2001-09-03 16:02 ` Andreas Schwab
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=200109032057.UAA36797@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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