mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org,
	Andrew Morton <akpm@osdl.org>,
	davej@redhat.com, perex@suse.cz, gregkh@suse.de,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [RFC] Add kernel<->userspace ABI stability documentation
Date: Mon, 27 Feb 2006 13:22:05 -0600	[thread overview]
Message-ID: <8C0F522E-E21E-40DD-8EFA-6D1111AF4CA1@kernel.crashing.org> (raw)
In-Reply-To: <20060227190150.GA9121@kroah.com>


On Feb 27, 2006, at 1:01 PM, Greg KH wrote:

> Hi all,
>
> As has been noticed recently by a lot of different people, it seems  
> like
> we are breaking the userspace<->kernelspace interface a lot.  Well, in
> looking back over time, we always have been doing this, but no one  
> seems
> to notice (proc files changing format and location, netlink library
> bindings, etc.)
>
> Linux is a dynamic system, we add and change things all the time based
> on the need of its developers and users.  Because of this, we now  
> run on
> more platforms than any other operating system ever has, from the
> world's top supercomputers, to the phone in your pocket.  It is how we
> have survived so far, and is how we will survive in the future.
>
> In order to ensure that we can continue to be dynamic in the  
> future, and
> not get bogged down by interfaces that are half-baked, or just turn  
> out
> to be wrong once we implement them and find ways to break them (anyone
> remember the sys_futex evolution?) we need to be able to handle the
> changes in the userspace<->kernelspace ABI properly.
>
> So, here's a first cut at how we can do this.  Lots of other operating
> systems explicity document what the interfaces to it are, and give a
> "stability" rating of those interfaces (for one example, look at
> http://opensolaris.org/os/community/onnv/devref_toc/devref_7/ ).  I  
> feel
> that we too need to document this interface, in order to keep everyone
> in the loop and not cause any unwanted surprises at times they do not
> need them (like right before a company's deadline.)
>
> I've sketched out a directory structure that starts in
> Documentation/ABI/ and has five different states, "stable", "testing",
> "unstable", "obsolete", and "private".  The README file describes  
> these
> different states, and how things can move between them.  I've also
> seeded the directories with some well known examples of the different
> interfaces that are already in these states.
>
> So, any comments?  Criticisms?

It would be nice if we can come up with some way for Linus to  
document state changes in his release notes.

- kumar

  parent reply	other threads:[~2006-02-27 19:22 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 19:01 Greg KH
2006-02-27 19:08 ` Arjan van de Ven
2006-02-27 19:11   ` Greg KH
2006-02-27 19:17     ` Arjan van de Ven
2006-02-27 19:22 ` Kumar Gala [this message]
2006-02-27 19:30   ` Greg KH
2006-02-27 19:31 ` Andi Kleen
2006-02-27 19:44   ` Greg KH
2006-03-01 13:53     ` Lars Marowsky-Bree
2006-03-01 14:10       ` Gabor Gombas
2006-03-01 14:35         ` Jes Sorensen
2006-03-01 16:30         ` Lars Marowsky-Bree
2006-02-27 20:06   ` Jesper Juhl
2006-02-27 19:35 ` Diego Calleja
2006-02-27 19:49   ` Greg KH
2006-02-27 19:57     ` Diego Calleja
2006-02-27 20:00       ` Greg KH
2006-02-27 20:13         ` Diego Calleja
2006-02-28  0:26           ` Greg KH
2006-02-27 19:36 ` Benjamin LaHaise
2006-02-27 19:46   ` Greg KH
2006-02-27 20:01     ` Benjamin LaHaise
2006-02-27 20:13       ` Greg KH
2006-02-27 20:22         ` John W. Linville
2006-02-27 22:00           ` Greg KH
2006-02-27 20:10     ` Arjan van de Ven
2006-02-27 22:58       ` Olivier Galibert
2006-02-27 20:20     ` Linus Torvalds
2006-02-27 21:04       ` Al Viro
2006-02-27 23:33         ` Nicholas Miell
2006-02-27 23:45       ` Greg KH
2006-02-28  1:52         ` Jason Lunz
2006-02-28  6:32         ` Theodore Ts'o
2006-02-28  6:41           ` Dave Jones
2006-03-01  0:34           ` Greg KH
2006-03-01  1:17             ` Nicholas Miell
2006-03-02  4:24               ` Greg KH
2006-03-05 16:17                 ` Eric W. Biederman
2006-03-05 23:23                   ` Benjamin LaHaise
2006-03-06  0:12                     ` Eric W. Biederman
2006-03-06  0:39                       ` Benjamin LaHaise
2006-03-06  2:15                         ` Eric W. Biederman
2006-03-07  3:56                           ` Greg KH
2006-02-27 19:52 ` Alistair John Strachan
2006-02-27 19:57   ` Greg KH
2006-02-27 20:05     ` Alistair John Strachan
2006-02-27 20:12       ` Greg KH
2006-02-27 20:15         ` Greg KH
2006-02-27 22:56           ` Olivier Galibert
2006-02-28  0:11             ` Greg KH
2006-02-27 20:01 ` Jesper Juhl
2006-03-01  0:21   ` Greg KH
2006-02-28 11:39 ` Nikita Danilov
2006-03-01  0:23   ` Greg KH
2006-03-01  7:27     ` Arjan van de Ven
2006-03-01 20:56       ` Greg KH
2006-03-07 14:44 Al Boldi
2006-03-07 15:21 ` Josh Boyer

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=8C0F522E-E21E-40DD-8EFA-6D1111AF4CA1@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --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

all inboxes | Powered by JetHome®