linux.git/net/socket.c, branch v2.6.33

fs: no games with DCACHE_UNHASHED

2009-12-17T15:51:40+00:00

Filesystems outside the regular namespace do not have to clear DCACHE_UNHASHED
in order to have a working /proc/$pid/fd/XXX. Nothing in proc prevents the
fd link from being used if its dentry is not in the hash.

Also, it does not get put into the dcache hash if DCACHE_UNHASHED is clear;
that depends on the filesystem calling d_add or d_rehash.

So delete the misleading comments and needless code.

Acked-by: Miklos Szeredi 
Signed-off-by: Nick Piggin 
Signed-off-by: Al Viro

switch alloc_file() to passing struct path

2009-12-16T17:16:42+00:00

... and have the caller grab both mnt and dentry; kill
leak in infiniband, while we are at it.

Signed-off-by: Al Viro

switch sock_alloc_file() to alloc_file()

2009-12-16T17:16:42+00:00

Signed-off-by: Al Viro

merge sock_alloc_fd/sock_attach_fd into a new helper

2009-12-16T17:16:41+00:00

Signed-off-by: Al Viro

reorder alloc_fd/attach_fd in socketpair()

2009-12-16T17:16:41+00:00

Signed-off-by: Al Viro

net: compat_mmsghdr must be used in sys_recvmmsg

2009-12-02T09:23:23+00:00

Both to traverse the entries and to set the msg_len field.

Commiter note: folded two patches and avoided one branch repeating the
compat test.

Signed-off-by: Jean-Mickael Guerin 
Signed-off-by: Arnaldo Carvalho de Melo 
Signed-off-by: David S. Miller

net/atm: move all compat_ioctl handling to atm/ioctl.c

2009-11-12T03:22:23+00:00

We have two implementations of the compat_ioctl handling for ATM, the
one that we have had for ages in fs/compat_ioctl.c and the one added to
net/atm/ioctl.c by David Woodhouse. Unfortunately, both versions are
incomplete, and in practice we use a very confusing combination of the
two.

For ioctl numbers that have the same identifier on 32 and 64 bit systems,
we go directly through the compat_ioctl socket operation, for those that

differ, we do a conversion in fs/compat_ioctl.c.

This patch moves both variants into the vcc_compat_ioctl() function,
while preserving the current behaviour. It also kills off the COMPATIBLE_IOCTL
definitions that we never use here.
Doing it this way is clearly not a good solution, but I hope it is a
step into the right direction, so that someone is able to clean up this
mess for real.

Signed-off-by: Arnd Bergmann 
Cc: Eric Dumazet 
Cc: David Woodhouse 
Signed-off-by: David S. Miller

net/compat: fix dev_ifsioc emulation corner cases

2009-11-12T03:22:22+00:00

Handling for SIOCSHWTSTAMP is broken on architectures
with a split user/kernel address space like s390,
because it passes a real user pointer while using
set_fs(KERNEL_DS).
A similar problem might arise the next time somebody
adds code to dev_ifsioc.

Split up dev_ifsioc into three separate functions for
SIOCSHWTSTAMP, SIOC*IFMAP and all other numbers so
we can get rid of set_fs in all potentially affected
cases.

Signed-off-by: Arnd Bergmann 
Cc: Patrick Ohly 
Cc: David S. Miller 
Signed-off-by: David S. Miller

net/compat_ioctl: support SIOCWANDEV

2009-11-09T04:57:03+00:00

This adds compat_ioctl support for SIOCWANDEV, which has
always been missing.

The definition of struct compat_ifreq was missing an
ifru_settings fields that is needed to support SIOCWANDEV,
so add that and clean up the whitespace damage in the
struct definition.

Signed-off-by: Arnd Bergmann 
Signed-off-by: David S. Miller

net, compat_ioctl: fix SIOCGMII ioctls

2009-11-09T04:56:21+00:00

SIOCGMIIPHY and SIOCGMIIREG return data through ifreq,
so it needs to be converted on the way out as well.

SIOCGIFPFLAGS is unused, but has the same problem in theory.

Signed-off-by: Arnd Bergmann 
Signed-off-by: David S. Miller