From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Kerrisk <mtk-manpages@gmx.net>
Cc: lkml <linux-kernel@vger.kernel.org>,
Linux Torvalds <torvalds@linux-foundation.org>,
Davide Libenzi <davidel@xmailserver.org>,
drepper@redhat.com, stable@kernel.org
Subject: Re: Problems with timerfd()
Date: Wed, 25 Jul 2007 15:12:52 -0700 [thread overview]
Message-ID: <20070725151252.8d2d5141.akpm@linux-foundation.org> (raw)
In-Reply-To: <46A7940B.4070901@gmx.net>
On Wed, 25 Jul 2007 20:18:51 +0200
Michael Kerrisk <mtk-manpages@gmx.net> wrote:
> Andrew,
>
> Andrew Morton wrote:
> > On Mon, 23 Jul 2007 08:32:29 +0200 Michael Kerrisk <mtk-manpages@gmx.net> wrote:
> >
> >> Andrew,
> >>
> >> The timerfd() syscall went into 2.6.22. While writing the man page for
> >> this syscall I've found some notable limitations of the interface, and I am
> >> wondering whether you and Linus would consider having this interface fixed
> >> for 2.6.23.
> >>
> >> On the one hand, these fixes would be an ABI change, which is of course
> >> bad. (However, as noted below, you have already accepted one of the ABI
> >> changes that I suggested into -mm, after Davide submitted a patch.)
> >>
> >> On the other hand, the interface has not yet made its way into a glibc
> >> release, and the change will not break applications. (The 2.6.22 version
> >> of the interface would just be "broken".)
> >
> > I think if the need is sufficient we can do this: fix it in 2.6.23 and in
> > 2.6.22.x. That means that there will be a few broken-on-new-glibc kernels
> > out in the wild, but very few I suspect.
>
> So I'm still not quite clear. Can I take it from your statement above that
> the proposed ABI changes would be admissible, as long as Davide is okay
> with them?
>
yup, I'll send that diff into Linus and -stable and see what happens.
next prev parent reply other threads:[~2007-07-25 22:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 6:32 Michael Kerrisk
2007-07-23 6:38 ` Andrew Morton
2007-07-23 6:42 ` Andrew Morton
2007-07-23 8:02 ` Michael Kerrisk
2007-07-25 18:18 ` Michael Kerrisk
2007-07-25 22:12 ` Andrew Morton [this message]
2007-08-07 6:55 ` Michael Kerrisk
2007-08-07 7:36 ` Andrew Morton
2007-08-07 9:14 ` Michael Kerrisk
2007-08-09 21:11 ` [PATCH] Revised timerfd() interface Michael Kerrisk
2007-08-13 23:34 ` Randy Dunlap
2007-08-15 14:40 ` Jonathan Corbet
2007-07-23 16:55 ` Problems with timerfd() Ray Lee
2007-07-24 7:40 ` Michael Kerrisk
2007-07-24 15:22 ` Ray Lee
2007-07-24 15:56 ` Michael Kerrisk
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=20070725151252.8d2d5141.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome