From: Jeff Mahoney <jeffm@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Al Viro <viro@ftp.linux.org.uk>
Subject: [PATCH] dup2: Fix return value with oldfd == newfd and invalid fd
Date: Mon, 11 May 2009 14:25:34 -0400 [thread overview]
Message-ID: <4A086D9E.60308@suse.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The return value of dup2 when oldfd == newfd and the fd isn't valid is not
getting properly sign extended. We end up with 4294967287 instead of -EBADF.
I've reproduced this on SLE11 (2.6.27.21), openSUSE Factory (2.6.29-rc5),
and Ubuntu 9.04 (2.6.28).
This patch uses a signed int for the error value so it is properly extended.
Commit 6c5d0512a091480c9f981162227fdb1c9d70e555 introduced this regression.
Reported-by: Jiri Dluhos <jdluhos@novell.com>
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
- ---
fs/fcntl.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
- --- a/fs/fcntl.c
+++ b/fs/fcntl.c
@@ -115,13 +115,14 @@ out_unlock:
SYSCALL_DEFINE2(dup2, unsigned int, oldfd, unsigned int, newfd)
{
+ int ret = oldfd;
if (unlikely(newfd == oldfd)) { /* corner case */
struct files_struct *files = current->files;
rcu_read_lock();
if (!fcheck_files(files, oldfd))
- - oldfd = -EBADF;
+ ret = -EBADF;
rcu_read_unlock();
- - return oldfd;
+ return ret;
}
return sys_dup3(oldfd, newfd, 0);
}
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkoIbZcACgkQLPWxlyuTD7JBVACgnNFiWRb4lhW9JgqR36BnT6SD
4uQAoJDcfqV2jsjCV340HlQLkk585Yw6
=IBqW
-----END PGP SIGNATURE-----
next reply other threads:[~2009-05-11 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 18:25 Jeff Mahoney [this message]
2009-05-11 18:40 ` [PATCH] dup2: Fix return value with oldfd == newfd and invalid fd Linus Torvalds
2009-05-11 19:00 ` Jeff Mahoney
2009-05-11 19:11 ` Al Viro
2009-05-11 19:26 ` Linus Torvalds
2009-05-11 19:49 ` Al Viro
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=4A086D9E.60308@suse.com \
--to=jeffm@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
/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