From: Al Viro <viro@ZenIV.linux.org.uk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Amerigo Wang <amwang@redhat.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [Patch 1/2] ia32: use generic sys_pipe()
Date: Sat, 12 Sep 2009 15:48:04 +0100 [thread overview]
Message-ID: <20090912144804.GB14381@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20090912133014.GA5858@ZenIV.linux.org.uk>
On Sat, Sep 12, 2009 at 02:30:14PM +0100, Al Viro wrote:
> On Tue, Aug 04, 2009 at 02:24:32PM +0200, Ingo Molnar wrote:
>
> > Please _ALWAYS_ mention the change in behavior in the changelog,
> > just in case someone ends up bisecting it. I only found out when i
> > reviewed the two syscalls out of caution.
[snip]
> > The generic version looks like the better choice to me but this
> > difference should be mentioned in the changelog nevertheless, just
> > in case some buggy app runs into this issue.
>
> It's not a matter of QOI, actually - sys32_pipe() is supposed to do what
> sys_pipe() would do on i386 host. So any difference in handling of an
> error case is simply wrong.
>
> Whether we want those sys_close() in sys_pipe() or not is a separate
> question, but we definitely want the same behaviour when 32bit process is
> run natively and when it's run on amd64. So sys32_pipe() has no business
> existing at all.
PS: said that, mentioning the change in commit message is a Good Idea(tm),
obviously...
next prev parent reply other threads:[~2009-09-12 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 9:08 [Patch 1/2] ia32: use generic sys_pipe() Amerigo Wang
2009-07-22 9:08 ` [Patch 2/2] xtensa: " Amerigo Wang
2009-07-22 10:10 ` Johannes Weiner
2009-07-23 9:47 ` Amerigo Wang
2009-07-23 11:18 ` Johannes Weiner
2009-07-24 9:04 ` Amerigo Wang
2009-08-04 12:24 ` [Patch 1/2] ia32: " Ingo Molnar
2009-08-05 11:38 ` Amerigo Wang
2009-09-12 13:30 ` Al Viro
2009-09-12 14:48 ` Al Viro [this message]
2009-09-18 9:46 ` Ingo Molnar
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=20090912144804.GB14381@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.