netdev - Re: [PATCH net-next] net: Use rx_nohandler for unhandled packets

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

Message-Id: <20191216.121619.2170160029247719261.davem@davemloft.net>
Date:   Mon, 16 Dec 2019 12:16:19 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     ptalbert@...hat.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net-next] net: Use rx_nohandler for unhandled packets

From: Patrick Talbert <ptalbert@...hat.com>
Date: Mon, 16 Dec 2019 15:07:14 +0100

> On Sun, Dec 15, 2019 at 9:41 PM David Miller <davem@...emloft.net> wrote:
>> I'm not applying this patch, sorry.
> 
> If you do not agree with adjusting the purpose of rx_nohandler to
> track these events then would you agree to a new counter?

I guess the people relying on the current rx_dropped behavior don't
matter and we can just change things from underneath them?  No,
actually, we cannot do that.

Educating people to solve this problem has the benefit of not screwing
over the users who understand what the counter means in this situation
already.