lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161824200934.5298.13769733038332592467.git-patchwork-notify@kernel.org>
Date:   Mon, 12 Apr 2021 15:40:09 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Cong Wang <xiyou.wangcong@...il.com>
Cc:     netdev@...r.kernel.org, bpf@...r.kernel.org,
        cong.wang@...edance.com,
        syzbot+320a3bc8d80f478c37e4@...kaller.appspotmail.com,
        john.fastabend@...il.com, edumazet@...gle.com,
        daniel@...earbox.net, jakub@...udflare.com, lmb@...udflare.com
Subject: 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 <cong.wang@...edance.com>
> 
> 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().
> 
> [...]

Here is the summary with links:
  - [bpf-next] skmsg: pass psock pointer to ->psock_update_sk_prot()
    https://git.kernel.org/bpf/bpf-next/c/51e0158a5432

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ