All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Guy Martin <gmsoft@tuxicoman.be>,
	Carlos O'Donell <carlos@systemhalted.org>
Cc: 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: Fri, 17 Jan 2014 23:27:55 +0100	[thread overview]
Message-ID: <52D9AE6B.9000405@gmx.de> (raw)
In-Reply-To: <02413c24ce7571300e50655bd7bb420d@tuxicoman.be>

On 01/17/2014 04:11 PM, Guy Martin wrote:
> On 2014-01-17 15:08, Carlos O'Donell wrote:
>> On Fri, Jan 17, 2014 at 9:01 AM, John David Anglin
>> <dave.anglin@bell.net> wrote:
>>> 
>>> On 17-Jan-14, at 3:55 AM, Guy Martin wrote:
>>> 
>>>> So despite the fact that this will break the ABI, the breakage
>>>> should be minimal if non existent while it will fix a lot of
>>>> hard to find and identify issues.
>>> 
>>> 
>>> Have you tested the change?
>> 
>> This is a good point.
>> 
>> If you can make this change and still boot your system with a
>> rebuilt kernel, then there is hope that your claims are true.
>> 
>> The basic argument would be: * Change kernel header to make
>> EWOULDBLOCK == AGAIN. * Rebuild kernel. * Boot system. * Verify
>> system is semifunctional, networking, IO, disk, XVnc, etc.
>> 
>> That would go a long way to showing that most of the system works.
>> 
>> Then if you emerge the world against those changed headers and it
>> goes well, then we might be talking about it being a low-impact
>> change.
>> 
> 
> I've rebuilt the kernel with the change and I can't see any impact. 
> NFS/SSH works fine and upgrading a few packages doesn't show any
> issue. I don't have X on that box.


Just a comment:
If we do an ABI break, we maybe should take other topics into account at the same time as well, e.g.
- increasing number of signals for systemd
- dropping some HP-UX signals
- maybe something needed to better support 64bit userspace ?
- ...

Helge

  reply	other threads:[~2014-01-17 22:27 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
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 [this message]
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=52D9AE6B.9000405@gmx.de \
    --to=deller@gmx.de \
    --cc=carlos@systemhalted.org \
    --cc=dave.anglin@bell.net \
    --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.