netdev - Re: [PATCH net-next RFC] Generic XDP

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1491721447.4309.2.camel@sipsolutions.net>
Date:   Sun, 09 Apr 2017 09:04:07 +0200
From:   Johannes Berg <johannes@...solutions.net>
To:     David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Cc:     xdp-newbies@...r.kernel.org
Subject: Re: [PATCH net-next RFC] Generic XDP

On Sun, 2017-04-09 at 08:25 +0200, Johannes Berg wrote:
> That would also let you use rcu_assign_pointer() which seems like the
> right thing to do here, along with marking the xdp_prog pointer as
> __rcu? That'd also let you use rcu_dereference() instead of
> READ_ONCE() which seems like the better annotation?

Looks like drivers do it exactly this way too though.

What I forgot: I guess we could make drivers use dev->xdp_prog after
this, instead of having their own?

johannes