[Patch bpf-next] skmsg: pass psock pointer to ->psock_update_sk_prot()

From: Cong Wang Using sk_psock() to retrieve psock pointer from sock requires RCU read lock, but we already get psock pointer before calling ->psock_update_sk_prot() in both cases, so we can just pass it without bothering sk_psock(). Reported-and-tested-by: syzbot+320a3bc8d80f478c3...@syzkaller.

RE: [Patch bpf-next] skmsg: pass psock pointer to ->psock_update_sk_prot()

Cong Wang wrote: > From: Cong Wang > > Using sk_psock() to retrieve psock pointer from sock requires > RCU read lock, but we already get psock pointer before calling > ->psock_update_sk_prot() in both cases, so we can just pass it > without bothering sk_psock(). > > Reported-and-tested-by: syzbo

Re: [Patch bpf-next] skmsg: pass psock pointer to ->psock_update_sk_prot()

On Wed, Apr 07, 2021 at 05:21 AM CEST, Cong Wang wrote: > From: Cong Wang > > Using sk_psock() to retrieve psock pointer from sock requires > RCU read lock, but we already get psock pointer before calling > ->psock_update_sk_prot() in both cases, so we can just pass it > without bothering sk_psock

Re: [Patch bpf-next] skmsg: pass psock pointer to ->psock_update_sk_prot()

Hello: This patch was applied to bpf/bpf-next.git (refs/heads/master): On Tue, 6 Apr 2021 20:21:11 -0700 you wrote: > From: Cong Wang > > Using sk_psock() to retrieve psock pointer from sock requires > RCU read lock, but we already get psock pointer before calling > ->psock_update_sk_prot() in