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
| ||
|
Message-ID: <CAF=yD-L5JKJSaLGr_DwUKER-xEJ8ma2B2xSH93AQarP3gRcVvw@mail.gmail.com> Date: Tue, 16 May 2017 18:29:39 -0400 From: Willem de Bruijn <willemdebruijn.kernel@...il.com> To: Miroslav Lichvar <mlichvar@...hat.com> Cc: Network Development <netdev@...r.kernel.org>, Richard Cochran <richardcochran@...il.com>, Willem de Bruijn <willemb@...gle.com> Subject: Re: [PATCH v3 net-next 3/7] net: add function to retrieve original skb device using NAPI ID On Tue, May 16, 2017 at 8:44 AM, Miroslav Lichvar <mlichvar@...hat.com> wrote: > Since commit b68581778cd0 ("net: Make skb->skb_iif always track > skb->dev") skbs don't have the original index of the interface which > received the packet. This information is now needed for a new control > message related to hardware timestamping. > > Instead of adding a new field to skb, we can find the device by the NAPI > ID if it is available, i.e. CONFIG_NET_RX_BUSY_POLL is enabled and the > driver is using NAPI. Add dev_get_by_napi_id() and also skb_napi_id() to > hide the CONFIG_NET_RX_BUSY_POLL ifdef. > > CC: Richard Cochran <richardcochran@...il.com> > CC: Willem de Bruijn <willemb@...gle.com> > Suggested-by: Willem de Bruijn <willemb@...gle.com> > Signed-off-by: Miroslav Lichvar <mlichvar@...hat.com> Acked-by: Willem de Bruijn <willemb@...gle.com>
Powered by blists - more mailing lists