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]
Date:   Wed, 1 Mar 2017 20:40:16 +0800 (CST)
From:   "Xiaobo Yan" <>
To:     "Cong Wang" <>
Cc:     "Stephen Hemminger" <>,
        "Linux Kernel Network Developers" <>
Subject: Re:Re: [drivers/net/vxlan]Why rcu_read_lock is not obtained before
 rculist travelling

Hi Cong,

Thanks very much for your reply.  It's indeeded acquired by upper layer.


At 2017-03-01 05:29:17, "Cong Wang" <> wrote:
>On Tue, Feb 28, 2017 at 6:03 AM, Xiaobo Yan <> wrote:
>> But I don’t find any rcu_read_lock invoked before travelling fdb_head list.  In vxlan_xmit and vxlan_snoop function, vxlan_find_mac function is called to search the vxlan_fdb of the dst_mac or src_mac. Then information in vxlan_fdb  is used for further process.  But as no rcu_read_lock is obtained before the list travelling, I am wondering if it is possible that vxlan_fdb is freed when it is being used.
>In both RX and TX paths, rcu read lock is acquired by upper layer.
>Check __dev_queue_xmit() and process_backlog().

Powered by blists - more mailing lists