From: Jiri Kosina <jkosina@suse.cz>
To: Li Zefan <lizefan@huawei.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Reviewing new API/ABI
Date: Mon, 12 May 2014 08:37:32 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1405120833540.5813@pobox.suse.cz> (raw)
In-Reply-To: <536B25AD.8040502@huawei.com>
On Thu, 8 May 2014, Li Zefan wrote:
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index 7578deb..52a282b 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -210,6 +210,13 @@ S: Supported
> >> F: Documentation/scsi/aacraid.txt
> >> F: drivers/scsi/aacraid/
> >>
> >> +ABI/API
> >> +L: linux-api@vger.kernel.org
> >> +F: Documentation/ABI/
> >> +F: include/linux/syscalls.h
> >> +F: include/uapi/
> >> +F: kernel/sys_ni.c
> >> +
> >
> > It'd be nice to have also sysfs changes covered as well if this is not
> > just about API, but also ABI; I am not sure whether this could be covered
> > by MAINTAINERS pattern, but at least mentioning this list in
> > Documentation/ABI/README seems appropriate.
>
> If sysfs is in,
Well, sysfs definitely is considered kernel ABI.
> what about cgroupfs? Which has been under dramatic changes.
This is of course interesting (and important) question per se -- the
amount of interfaces between userspace and kernelspace is growing at a
rapid pace (especially a lot of crap gets added into debugfs I guess), and
it's not always clearly defined what is considered proper ABI and thus
should be maintained stable.
Is "if we ever get a report about userspace regression because of kernel
interface change" enough well-defined criteria? What if there is userspace
depending on the contents of the kernel ringbuffer? Etc etc ...
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2014-05-12 6:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 17:45 [Ksummit-discuss] [CORE TOPIC] Reviewing new API/ABI Andy Lutomirski
2014-05-06 17:58 ` josh
2014-05-06 19:12 ` Shuah Khan
2014-05-06 19:16 ` Andy Lutomirski
2014-05-06 19:37 ` Shuah Khan
2014-05-06 19:21 ` Johannes Berg
2014-05-06 19:43 ` Andy Lutomirski
2014-05-06 19:48 ` Johannes Berg
2014-05-06 19:51 ` Andy Lutomirski
2014-05-06 19:45 ` josh
2014-05-06 20:10 ` Daniel Vetter
2014-05-06 20:13 ` Andy Lutomirski
2014-05-07 10:12 ` Laurent Pinchart
2014-05-07 12:36 ` Daniel Vetter
2014-05-07 13:30 ` Laurent Pinchart
2014-05-07 13:50 ` Hans Verkuil
2014-05-12 14:15 ` Wolfram Sang
2014-05-07 17:48 ` Michael Kerrisk (man-pages)
2014-05-06 19:00 ` Greg KH
2014-05-06 20:07 ` Steven Rostedt
2014-05-06 20:34 ` Josh Triplett
2014-05-06 20:42 ` Steven Rostedt
2014-05-06 21:00 ` josh
2014-05-07 11:48 ` Jiri Kosina
2014-05-08 6:35 ` Li Zefan
2014-05-12 6:37 ` Jiri Kosina [this message]
2014-05-07 6:27 ` Michael Kerrisk (man-pages)
2014-05-06 19:57 ` Dan Carpenter
2014-05-08 18:15 ` Randy Dunlap
2014-05-09 11:33 ` Jeff Layton
2014-05-09 11:50 ` 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=alpine.LNX.2.00.1405120833540.5813@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=lizefan@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.