linux-toradex.git/net/key, branch v2.6.33.1

af_key: fix netns ops ordering on module load/unload

2010-02-04T02:11:11+00:00

1. After sock_register() returns, it's possible to create sockets,
   even if module still not initialized fully (blame generic module code
   for that!)
2. Consequently, pfkey_create() can be called with pfkey_net_id still not
   initialized which will BUG_ON in net_generic():
	kernel BUG at include/net/netns/generic.h:43!
3. During netns shutdown, netns ops should be unregistered after
   key manager unregistered because key manager calls can be triggered
   from xfrm_user module:

   	general protection fault: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
	pfkey_broadcast+0x111/0x210 [af_key]
	pfkey_send_notify+0x16a/0x300 [af_key]
	km_state_notify+0x41/0x70
	xfrm_flush_sa+0x75/0x90 [xfrm_user]
4. Unregister netns ops after socket ops just in case and for symmetry.

Reported by Luca Tettamanti.

Signed-off-by: Alexey Dobriyan 
Tested-by: Luca Tettamanti 
Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller

xfrm: Fix truncation length of authentication algorithms installed via PF_KEY

2009-12-11T23:07:57+00:00

Commit 4447bb33f09444920a8f1d89e1540137429351b6 ("xfrm: Store aalg in
xfrm_state with a user specified truncation length") breaks
installation of authentication algorithms via PF_KEY, as the state
specific truncation length is not installed with the algorithms
default truncation length.  This patch initializes state properly to
the default if installed via PF_KEY.

Signed-off-by: Martin Willi 
Acked-by: Herbert Xu 
Signed-off-by: David S. Miller

net: Simplify af_key pernet operations.

2009-12-02T00:15:54+00:00

Take advantage of the new pernet automatic storage management,
and stop using compatibility network namespace functions.

Signed-off-by: Eric W. Biederman 
Signed-off-by: David S. Miller

netns: net_identifiers should be read_mostly

2009-11-18T13:03:25+00:00

Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller

net: pass kern to net_proto_family create function

2009-11-06T06:18:14+00:00

The generic __sock_create function has a kern argument which allows the
security system to make decisions based on if a socket is being created by
the kernel or by userspace.  This patch passes that flag to the
net_proto_family specific create function, so it can do the same thing.

Signed-off-by: Eric Paris 
Acked-by: Arnaldo Carvalho de Melo 
Signed-off-by: David S. Miller

net: Generalize socket rx gap / receive queue overflow cmsg

2009-10-12T20:26:31+00:00

Create a new socket level option to report number of queue overflows

Recently I augmented the AF_PACKET protocol to report the number of frames lost
on the socket receive queue between any two enqueued frames.  This value was
exported via a SOL_PACKET level cmsg.  AFter I completed that work it was
requested that this feature be generalized so that any datagram oriented socket
could make use of this option.  As such I've created this patch, It creates a
new SOL_SOCKET level option called SO_RXQ_OVFL, which when enabled exports a
SOL_SOCKET level cmsg that reports the nubmer of times the sk_receive_queue
overflowed between any two given frames.  It also augments the AF_PACKET
protocol to take advantage of this new feature (as it previously did not touch
sk->sk_drops, which this patch uses to record the overflow count).  Tested
successfully by me.

Notes:

1) Unlike my previous patch, this patch simply records the sk_drops value, which
is not a number of drops between packets, but rather a total number of drops.
Deltas must be computed in user space.

2) While this patch currently works with datagram oriented protocols, it will
also be accepted by non-datagram oriented protocols. I'm not sure if thats
agreeable to everyone, but my argument in favor of doing so is that, for those
protocols which aren't applicable to this option, sk_drops will always be zero,
and reporting no drops on a receive queue that isn't used for those
non-participating protocols seems reasonable to me.  This also saves us having
to code in a per-protocol opt in mechanism.

3) This applies cleanly to net-next assuming that commit
977750076d98c7ff6cbda51858bb5a5894a9d9ab (my af packet cmsg patch) is reverted

Signed-off-by: Neil Horman 
Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller

net: mark net_proto_ops as const

2009-10-07T08:10:46+00:00

All usages of structure net_proto_ops should be declared const.

Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

net: file_operations should be const

2009-09-02T08:03:53+00:00

All instances of file_operations should be const.

Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

net: seq_operations should be const

2009-09-02T08:03:39+00:00

Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

net: correct off-by-one write allocations reports

2009-06-18T07:29:12+00:00

commit 2b85a34e911bf483c27cfdd124aeb1605145dc80
(net: No more expensive sock_hold()/sock_put() on each tx)
changed initial sk_wmem_alloc value.

We need to take into account this offset when reporting
sk_wmem_alloc to user, in PROC_FS files or various
ioctls (SIOCOUTQ/TIOCOUTQ)

Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller