From: Mike Frysinger <vapier@gentoo.org>
To: Helge Deller <deller@gmx.de>
Cc: Guy Martin <gmsoft@tuxicoman.be>,
"Carlos O'Donell" <carlos@systemhalted.org>,
John David Anglin <dave.anglin@bell.net>,
"linux-parisc" <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] Make EWOULDBLOCK be equal to EAGAIN on parisc.
Date: Thu, 16 Jan 2014 17:43:23 -0500 [thread overview]
Message-ID: <201401161743.25096.vapier@gentoo.org> (raw)
In-Reply-To: <52D84BF5.3010001@gmx.de>
[-- Attachment #1: Type: Text/Plain, Size: 1251 bytes --]
On Thursday 16 January 2014 16:15:33 Helge Deller wrote:
> On 01/16/2014 10:05 PM, Carlos O'Donell wrote:
> > On Thu, Jan 16, 2014 at 3:49 PM, John David Anglin wrote:
> >>> This is an ABI break.
> >>>
> >>> You can't do this without rebuilding userspace.
> >>>
> >>> You need debian an gentoo onboard to do this ABI break.
> >>
> >> This would take about a month on Debian, so I'm against. Various bits
> >> of kernel code traditionally return EWOULDBLOCK, so any application
> >> code that just checks EWOULDBLOCK would fail.
> >
> > That's not true if, like all other targets, EWOULDBLOCK == AGAIN. It's
> > only true on hppa, and that's the problem.
> >
> > The kernel is completely inconsistent about returning EWOULDBLOCK or
> > EAGAIN, and the standards do dictate one or the other so the kernel
> > and glibc are correct to use one or the other to match the standard.
> >
> > However, user applications are equally sloppy about checking the right
> > value.
>
> Guy, do you have actual programs which are currently broken and which don't
> check for both? My feeling is, that most programs were fixed, but I might
> be wrong...
my guess is memcached:
https://bugs.gentoo.org/show_bug.cgi?id=498262
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-16 22:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 16:17 [PATCH] Make EWOULDBLOCK be equal to EAGAIN on parisc Guy Martin
2014-01-16 20:02 ` Carlos O'Donell
2014-01-16 20:49 ` John David Anglin
2014-01-16 21:05 ` Carlos O'Donell
2014-01-16 21:15 ` Helge Deller
2014-01-16 22:43 ` Mike Frysinger [this message]
2014-01-17 8:55 ` Guy Martin
2014-01-17 14:01 ` John David Anglin
2014-01-17 14:08 ` Carlos O'Donell
2014-01-17 15:11 ` Guy Martin
2014-01-17 22:27 ` Helge Deller
2014-01-31 16:53 ` Helge Deller
2014-01-31 17:24 ` Carlos O'Donell
2014-01-31 23:16 ` 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=201401161743.25096.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=carlos@systemhalted.org \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=gmsoft@tuxicoman.be \
--cc=linux-parisc@vger.kernel.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 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.