public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: DervishD <raul@viadomus.com>
Cc: garzik@havoc.gtf.org, linux-kernel@vger.kernel.org
Subject: Re: Why 'linux/fs.h' cannot be included? I *can*...
Date: 30 Jan 2002 07:27:41 -0700	[thread overview]
Message-ID: <m1lmefdici.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E16VtWb-0002kV-00@DervishD.viadomus.com>
In-Reply-To: <E16VtWb-0002kV-00@DervishD.viadomus.com>

DervishD <raul@viadomus.com> writes:

>     Hi Jeff :)
> 
> >>     Given the number of user-space apps that needs ioctl definitions
> >> and things like those (that are supposed not to change easily), those
> >> definitions should go in user-includable headers... IMHO.
> >> 
> >>     Fortunately, we have some of them in libc headers now.
> >The policy is, never ever include kernel headers from userspace.
> 
>     I know, but sometimes it is just impossible (when they aren't
> appropriate glibc headers, for example). In fact, all this question
> arose because I'm coding an 'ioctl' command line interface, so you
> can send any 'documented' ioctl to any device. And, since I'm going
> to start with block devices, I need linux/fs.h.
> 
>     The problem is that I don't want to copy the definitions I need
> from linux/fs.h, because this will lead to problems if those
> definitions change. Anyway this is not an issue, because by changing
> the running kernel those definitions in fact may not be valid...
> 
>     Resuming: I don't know how properly address this problem.

In general you are running into the ioctls are messy problem, and probably
need to be cleaned up.  Beyond that though ioctls should be static
they are part of the kernel ABI.  Though they aren't managed tight
enough that you can count on them being 100% static.

> >Your libc should provide a "sanitized" version of the kernel headers,
> >which is completely separate from any kernel sources.
> 
>     I suppose that those headers will contain definitions not subject
> to change, won't they? But I don't know if I can consider the ioctl
> constants as not subject to change (they should be permanent,
> though).

In general ioctls are not be subject to change.
 
> >So, any problems should be reported to your libc maintainer :)
> 
>     Well, I try... I can even try to make the sanitized header myself
> and pray for it to be included in next glibc revision :)

Not that would be progress..

Eric

  reply	other threads:[~2002-01-30 14:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 12:07 Why 'linux/fs.h' cannot be included? I *can* DervishD
2002-01-30 14:27 ` Eric W. Biederman [this message]
2002-01-30 16:12 ` Jeff Garzik
     [not found] <mailman.1012391761.28301.linux-kernel2news@redhat.com>
2002-01-30 18:24 ` Pete Zaitcev
2002-01-30 23:33   ` Keith Owens
2002-01-31  1:17     ` Jeff Garzik
2002-01-31  1:51       ` Keith Owens
2002-01-31  1:57         ` Jeff Garzik
2002-01-31  2:06           ` Keith Owens
2002-01-31  2:35             ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2002-01-29 10:20 DervishD
2002-01-29 14:30 ` Jeff Garzik
2002-01-29 14:51   ` Alan Cox
2002-01-29 14:42     ` Jeff Garzik
2002-01-28 19:31 DervishD
2002-01-28 19:44 ` Eric W. Biederman

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=m1lmefdici.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=garzik@havoc.gtf.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raul@viadomus.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