From: Tony Griffiths <tonyg@agile.tv>
To: linux-kernel@vger.kernel.org
Subject: Some socket syscalls fail to return an error on bad file-descriptor# argument
Date: Thu, 01 Jun 2006 13:38:55 +1000 [thread overview]
Message-ID: <447E614F.3090905@agile.tv> (raw)
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
Description:
The sockfd_lookup_light() function does not set the return error status
on a particular failure mode when the passed-in fd# is erroneous.
Environment:
2.6.16 kernel with the -mm2 patch-set applied. Linux 2.6.17 kernels are
also affected. Without the fix, a number of tests in LTP fail! Any
program calling one of the syscalls listed below with a bad fd# will not
get an error return indicating that the syscall failed.
Fix:
The attached patch correctly sets *err = -EBADF if the attempt to map
the fd# to a file pointer returns NULL. The following syscalls are
affected-
bind()
listen()
accept()
connect()
getsockname()
getpeername()
setsockopt()
setsockopt()
shutdown()
sendmsg()
recvmsg()
[-- Attachment #2: atv-40018-socket-fix-2.6.16.patch --]
[-- Type: text/x-patch, Size: 338 bytes --]
diff -urpN ./net/socket.c.orig ./net/socket.c
--- ./net/socket.c.orig 2006-06-01 10:28:30.000000000 +1000
+++ ./net/socket.c 2006-06-01 10:34:09.000000000 +1000
@@ -496,6 +496,8 @@ static struct socket *sockfd_lookup_ligh
if (sock)
return sock;
fput_light(file, *fput_needed);
+ } else {
+ *err = -EBADF;
}
return NULL;
}
next reply other threads:[~2006-06-01 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 3:38 Tony Griffiths [this message]
2006-06-01 4:33 ` Some socket syscalls fail to return an error on bad file-descriptor# argument Hua Zhong
2006-06-01 4:41 ` Andrew Morton
2006-06-01 7:21 ` James Morris
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=447E614F.3090905@agile.tv \
--to=tonyg@agile.tv \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox