From: Willy Tarreau <w@1wt.eu>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
rth@twiddle.net, linux-kernel@vger.kernel.org, alpha@gentoo.org
Subject: Re: epoll handling in the alpha port
Date: Fri, 2 Feb 2007 06:48:28 +0100 [thread overview]
Message-ID: <20070202054828.GE24090@1wt.eu> (raw)
In-Reply-To: <200702020019.36248.vapier@gentoo.org>
On Fri, Feb 02, 2007 at 12:19:35AM -0500, Mike Frysinger wrote:
> On Friday 02 February 2007, Andrew Morton wrote:
> > It might be to late to fix this - we risk breaking userspace which worked
> > around it.
>
> we'd be breaking userspace API, but not ABI ... and the largest consumers out
> there (glibc/uclibc) have not been accounting for this, so we wouldnt be
> breaking them
>
> that's how we noticed the issue in Gentoo ... all the epoll calls are
> automatically declared -ENOSYS stubs in glibc's libc.so
>
> is there some other large consumer i'm not thinking of ?
Not necessarily some large consumers, but epoll() is quite older than its
kernel inclusion, so there certainly are some apps still using the syscall
without going through libc.
> > It would be safer to add the correct definitions while leaving the old ones
> > in place.
>
> in the end, either works for me ... i can see linux's pretty hard 'dont break
> userspace' policy coming into play here
I think it would be reasonable to use the NR_epoll* names first, and to
declare NR_sys_epoll* aliases which will point to NR_epoll*. You would
then add a comment with the date of the change, stating that you keep
them just in case there are some old apps. Then, someone coming on the
comment in 3 or 4 years could reasonably suggest removing those aliases.
Willy
next prev parent reply other threads:[~2007-02-02 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 20:20 epoll handling in the alpha port Mike Frysinger
2007-02-02 5:05 ` Andrew Morton
2007-02-02 5:19 ` Mike Frysinger
2007-02-02 5:48 ` Willy Tarreau [this message]
2007-02-02 6:22 ` Mike Frysinger
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=20070202054828.GE24090@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=alpha@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=vapier@gentoo.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