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: <20161219.111156.1987012114474401231.davem@davemloft.net> Date: Mon, 19 Dec 2016 11:11:56 -0500 (EST) From: David Miller <davem@...emloft.net> To: mahesh@...dewar.net Cc: netdev@...r.kernel.org, edumazet@...gle.com, maheshb@...gle.com Subject: Re: [PATCH net v2] ipvlan: fix crash when master is set in loopback mode From: Mahesh Bandewar <mahesh@...dewar.net> Date: Sun, 18 Dec 2016 11:00:25 -0800 > From: Mahesh Bandewar <maheshb@...gle.com> > > In an IPvlan setup when master is set in loopback mode e.g. > > ethtool -K eth0 set loopback on > > where eth0 is master device for IPvlan setup. > > The failure actually happens while processing mulitcast packets > but that's a result of unconditionally queueing packets without > ensuring ether-header is part of the linear part of skb. > > This patch forces this check at the reception and drops packets > which fail this check before queuing them. ... > Signed-off-by: Mahesh Bandewar <maheshb@...gle.com> > --- > v1->v2: commit log update Like Eric, I still do not like this change nor the explanation. Whether in loopback mode or not, your explanation makes no sense at all. If the packet comes from the ethernet device, the freakin' ethernet header is there in the linear SKB area. No pulling should be needed whatsoever. Something creates this bad situation where the ethernet header is not there, but you have not explained that sufficiently yet. Thank you.
Powered by blists - more mailing lists