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: <20161121110915.GB22120@breakpoint.cc> Date: Mon, 21 Nov 2016 12:09:15 +0100 From: Florian Westphal <fw@...len.de> To: fgao@...ai8.com Cc: mareklindner@...mailbox.ch, sw@...onwunderlich.de, a@...table.cc, davem@...emloft.net, b.a.t.m.a.n@...ts.open-mesh.org, netdev@...r.kernel.org, gfree.wind@...il.com Subject: Re: [PATCH net v2 1/1] net: batman-adv: Treat NET_XMIT_CN as transmit successfully fgao@...ai8.com <fgao@...ai8.com> wrote: > From: Gao Feng <fgao@...ai8.com> > > The tc could return NET_XMIT_CN as one congestion notification, but > it does not mean the packet is lost. Other modules like ipvlan, > macvlan, and others treat NET_XMIT_CN as success too. > > So batman-adv should add the NET_XMIT_CN check. "The tc could return NET_XMIT_CN as one congestion notification, but it means another packet got dropped. Other modules like batman do not treat NET_XMIT_CN as success, so modules like ipvlan, macvlan, .. should ignore it as well." What I am asking is: Are you sure adding NET_XMIT_CN handling everywhere is the right way to resolve the inconsistency?
Powered by blists - more mailing lists