Re: [PATCH net-next] rxrpc: Don't expose skbs to in-kernel users

2016-09-01 Thread David Howells
David Miller wrote: > Actually, reverted, this adds a new warning to the build: > > net/rxrpc/recvmsg.c: In function ‘rxrpc_kernel_recv_data’: > net/rxrpc/recvmsg.c:531:1: warning: label ‘need_more_data’ defined but not > used [-Wunused-label] > need_more_data: > ^ > net/rxrpc/recvmsg.c:475:7

Re: [PATCH net-next] rxrpc: Don't expose skbs to in-kernel users

2016-09-01 Thread David Miller
From: David Miller Date: Thu, 01 Sep 2016 16:38:32 -0700 (PDT) > From: David Howells > Date: Tue, 30 Aug 2016 16:52:39 +0100 > >> Don't expose skbs to in-kernel users, such as the AFS filesystem, but >> instead provide a notification hook the indicates that a call needs >> attention and another

Re: [PATCH net-next] rxrpc: Don't expose skbs to in-kernel users

2016-09-01 Thread David Miller
From: David Howells Date: Tue, 30 Aug 2016 16:52:39 +0100 > Don't expose skbs to in-kernel users, such as the AFS filesystem, but > instead provide a notification hook the indicates that a call needs > attention and another that indicates that there's a new call to be > collected. ... > Signed-o

[PATCH net-next] rxrpc: Don't expose skbs to in-kernel users

2016-08-30 Thread David Howells
Don't expose skbs to in-kernel users, such as the AFS filesystem, but instead provide a notification hook the indicates that a call needs attention and another that indicates that there's a new call to be collected. This makes the following possibilities more achievable: (1) Call refcounting can