Re: Some socket syscalls fail to return an error on bad file-descriptor# argument

On Wed, 31 May 2006, Andrew Morton wrote:

> Confused.  That patch cannot make any difference to this function:

Yep, the code definitely looks correct in current LT git.

> static struct socket *sockfd_lookup_light(int fd, int *err, int *fput_needed)
> {
> 	struct file *file;
> 	struct socket *sock;
> 
> 	*err = -EBADF;
> 	file = fget_light(fd, fput_needed);
> 	if (file) {
> 		sock = sock_from_file(file, err);
> 		if (sock)
> 			return sock;
> 		fput_light(file, *fput_needed);
> 	}
> 	return NULL;
> }



- James
-- 
James Morris
<[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Some socket syscalls fail to return an error on bad file-descriptor# argument
    • From: Tony Griffiths <[email protected]>
  • Re: Some socket syscalls fail to return an error on bad file-descriptor# argument
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: Question about tcp hash function tcp_hashfn()
• Next by Date: printk's - i dont want any limit howto?
• Previous by thread: Re: Some socket syscalls fail to return an error on bad file-descriptor# argument
• Next by thread: Why must NFS access metadata in synchronous mode?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]