public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Andries.Brouwer@cwi.nl, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] linuxabi
Date: Thu, 2 Oct 2003 17:33:01 +0200	[thread overview]
Message-ID: <20031002153301.GA2033@win.tue.nl> (raw)
In-Reply-To: <m17k3nhfex.fsf@ebiederm.dsl.xmission.com>

On Thu, Oct 02, 2003 at 08:39:50AM -0600, Eric W. Biederman wrote:

> This is a 2.7 project.

I disagree. This is unrelated to kernel development, just like working
on sparse is unrelated to kernel development. 

> Doing this right requires a lot more
> than what you are doing here.

Possibly. So we need discussion.

I have registered comment #1: Al prefers the enum style.
A possibility.

Now you come with comment #2: write LINUX_MS_RDONLY instead of
MS_RDONLY. You have not convinced me.

> One example is that we need to be very careful with is that the
> glibc abi is not the same as the linux kernel abi.  Even though most
> of the functions are pass through some are not.  And which are which
> is a fairly arbitrary decision.  So all of the definitions exported
> through linuxabi need to be in a linux centric namespace.  This is
> especially true because otherwise I could not include
> linuxabi/mountflags.h and sys/mount.h and not get compilation 
> conflicts.

Today glibc tells me in sys/mount.h
 #define MS_RMT_MASK (MS_RDONLY | MS_MANDLOCK)
and in linux/fs.h
 #define MS_RMT_MASK (MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC|MS_SYNCHRONOUS|MS_MANDLOCK|MS_NOATIME|MS_NODIRATIME)

It seems glibc is not even self-consistent.
Consider linuxabi/mountflags.h as part of the replacement for linux/fs.h.

Andries



  reply	other threads:[~2003-10-02 15:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01  0:01 [PATCH] linuxabi Andries.Brouwer
2003-10-01  2:05 ` Bernd Eckenfels
2003-10-01  3:34   ` viro
2003-10-01  4:52     ` H. Peter Anvin
2003-10-01  5:22       ` Philippe Troin
2003-10-01  5:50         ` Miles Bader
2003-10-01 14:33     ` Daniel Jacobowitz
2003-10-01 10:20 ` J.A. Magallon
2003-10-02 14:39 ` Eric W. Biederman
2003-10-02 15:33   ` Andries Brouwer [this message]
2003-10-03  7:36     ` Eric W. Biederman
2003-10-04  3:37       ` Rob Landley
2003-10-04  6:31         ` Erik Andersen
     [not found]   ` <fa.e2g5r6g.u3igb4@ifi.uio.no>
2003-10-03 16:49     ` Kai Henningsen
2003-10-03 17:32   ` Sam Ravnborg
     [not found] <BCSP.62t.7@gated-at.bofh.it>
     [not found] ` <CcWl.7kh.9@gated-at.bofh.it>
     [not found]   ` <CdIL.8ts.13@gated-at.bofh.it>
2003-10-03 14:02     ` Ihar 'Philips' Filipau

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=20031002153301.GA2033@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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