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: <4dddfda5-1c03-6386-e204-e21df07aabd1@gmail.com>
Date:   Wed, 13 Oct 2021 17:17:51 +0100
From:   Edward Cree <ecree.xilinx@...il.com>
To:     Stephen Suryaputra <ssuryaextr@...il.com>
Cc:     Network Development <netdev@...r.kernel.org>
Subject: Re: ip_list_rcv() question

On 07/10/2021 13:14, Stephen Suryaputra wrote:
> Under what condition that ip_list_rcv() would restart the sublist, i.e.
> that the skb in the list is having different skb->dev?

IIRC, something earlier in the call chain (possibly
 __netif_receive_skb_core()?) can change skb->dev to something other
 than the device that originally received the packet (orig_dev).  I
 think it's if the packet gets handled/transformed by a software
 netdevice (maybe a VLAN device?).
But really when I wrote ip_list_rcv() I just worked on the basis
 that "I don't know it can't change, so I shall assume it can".

HTH,
-ed

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ