From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Eugene Syromyatnikov <evgsyr@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>,
Mike Christie <mchristi@redhat.com>
Subject: Re: ioctl_list.2: complete overhaul needed
Date: Wed, 15 Apr 2020 08:48:28 +0200 [thread overview]
Message-ID: <a2e450ec-2566-d490-9138-674cc54e05da@gmail.com> (raw)
In-Reply-To: <5e9b4408-410f-6fb4-9c8b-0bd68e64577d@gmx.de>
Hello Heinrich,
On 4/14/20 6:21 PM, Heinrich Schuchardt wrote:
> On 2020-04-14 17:37, Eugene Syromyatnikov wrote:
>> On Tue, Apr 14, 2020 at 5:18 PM Michael Kerrisk (man-pages)
>> <mtk.manpages@gmail.com> wrote:
>>>
>>> Hello Heinrich,
>>>
>>> On Sun, 9 Nov 2014 at 16:52, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
>>>>
>>>>
>>>> Hello Michael,
>>>>
>>>> the current ioctl_list.2 man-page descripton starts
>>>> "This is Ioctl List 1.3.27, a list of ioctl calls in Linux/i386 kernel
>>>> 1.3.27."
>>>> So the man-page represents the state of Sep 14th, 1995.
>>>> It enumerates only 421 out of over 1200 calls.
>>>>
>>>> The list contains hex values of different constants. I just wonder for
>>>> which architecture (alpha, i386, mips, or sparc at that time). No
>>>> information is supplied.
>>>>
>>>> Current values depend on the architecture, e.g.
>>>>
>>>> On amd64
>>>> 0x82307201 VFAT_IOCTL_READDIR_BOTH
>>>> 0x82307202 VFAT_IOCTL_READDIR_SHORT
>>>> 0x80047210 FAT_IOCTL_GET_ATTRIBUTES
>>>> 0x40047211 FAT_IOCTL_SET_ATTRIBUTES
>>>> 0x80047213 FAT_IOCTL_GET_VOLUME_ID
>>>>
>>>> On mips
>>>> 0x42187201 VFAT_IOCTL_READDIR_BOTH
>>>> 0x42187202 VFAT_IOCTL_READDIR_SHORT
>>>> 0x40047210 FAT_IOCTL_GET_ATTRIBUTES
>>>> 0x80047211 FAT_IOCTL_SET_ATTRIBUTES
>>>> 0x40047213 FAT_IOCTL_GET_VOLUME_ID
>>>>
>>>> Hence hex values should be removed.
>>>
>>>
>>> As you suggest, I've removed the hex values from the lists.
>>
>> Those can be replaced with the _IO* macro definitions. Meanwhile, the
>> list is somewhat far from complete; strace has some approximation that
>> can be uses a basis of a more complete and reliable list
>> (linux/{32,64}/ioctls_inc*.h and linux/*/ioctls_arch*.h), but I'm not
>> sure if it is worth adding to the man page (moreover, entries are
>> constantly being added and changed there; yes, breaking the kernel ABI
>> in the process sometimes).
>
> Man-pages like netdevices.7 or ioctl_fat.2 are what is needed to help a
> user who does not want to read through the kernel code.
Yes, I agree.
> If ioctl_list.2 has not been reasonably maintained since Linux 1.3.27
> and hence is not a reliable source of information,
I must confess I've never loved that page. and in the 24+ years since
it was released, it's seen very little useful change to the content.
(You of course are well qualified to know that, since the biggest
changes have come from you, and as we know they've not been anything
big.)
> shouldn't it be dropped?
I'm inclined to do so. Let's see if anyone else comments.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-04-15 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 15:50 ioctl_list.2: complete overhaul needed Heinrich Schuchardt
[not found] ` <545F8D2E.5030308-Mmb7MZpHnFY@public.gmane.org>
2014-11-11 7:14 ` Michael Kerrisk (man-pages)
[not found] ` <5461B768.7040603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-11 7:52 ` Mike Frysinger
[not found] ` <20141111075242.GB28132-eAEk4k+vi/E8xmjh+jFwDmGXanvQGlWp@public.gmane.org>
2014-11-11 8:18 ` Michael Kerrisk (man-pages)
2020-04-14 11:07 ` Michael Kerrisk (man-pages)
2020-04-14 15:37 ` Eugene Syromyatnikov
2020-04-14 16:21 ` Heinrich Schuchardt
2020-04-15 6:48 ` Michael Kerrisk (man-pages) [this message]
2020-04-16 7:10 ` Removal of the ioctl_list(2) manual page (was: Re: ioctl_list.2: complete overhaul needed) Michael Kerrisk (man-pages)
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=a2e450ec-2566-d490-9138-674cc54e05da@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=evgsyr@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=xypron.glpk@gmx.de \
/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