From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, Jim Meyering <jim@meyering.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH regression] dup3: Return an error when oldfd == newfd.
Date: Tue, 9 Oct 2012 15:52:43 +0100 [thread overview]
Message-ID: <20121009145243.GS2616@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20121009142743.GA20047@rhmail.home.annexia.org>
On Tue, Oct 09, 2012 at 03:27:43PM +0100, Richard W.M. Jones wrote:
> I have tested the attached patch to fix the dup3 regression.
>
> Rich.
>
> From 0944e30e12dec6544b3602626b60ff412375c78f Mon Sep 17 00:00:00 2001
> From: "Richard W.M. Jones" <rjones@redhat.com>
> Date: Tue, 9 Oct 2012 14:42:45 +0100
> Subject: [PATCH] dup3: Return an error when oldfd == newfd.
>
> The following commit:
>
> commit fe17f22d7fd0e344ef6447238f799bb49f670c6f
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date: Tue Aug 21 11:48:11 2012 -0400
>
> take purely descriptor-related stuff from fcntl.c to file.c
>
> was supposed to be just code motion, but it dropped the following two
> lines:
>
> if (unlikely(oldfd == newfd))
> return -EINVAL;
*grumble*
So it has; applied, will push to Linus. But now I really want to check
if I'd lost anything else in those code moves (and you are right, it
was supposed to be just that).
prev parent reply other threads:[~2012-10-09 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 9:15 Another bug, in dup3 Richard W.M. Jones
2012-10-09 9:25 ` Richard W.M. Jones
2012-10-09 14:27 ` [PATCH regression] dup3: Return an error when oldfd == newfd Richard W.M. Jones
2012-10-09 14:52 ` Al Viro [this message]
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=20121009145243.GS2616@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jim@meyering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rjones@redhat.com \
--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.