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: <20250905160720.1e7b2136@kernel.org>
Date: Fri, 5 Sep 2025 16:07:20 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Naveen Mamindlapalli <naveenm@...vell.com>
Cc: <davem@...emloft.net>, <edumazet@...gle.com>, <pabeni@...hat.com>,
 <horms@...nel.org>, <corbet@....net>, <andrew@...n.ch>,
 <netdev@...r.kernel.org>, <linux-doc@...r.kernel.org>,
 <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next] docs: networking: clarify expectation of
 persistent stats

On Fri, 5 Sep 2025 16:34:30 +0530 Naveen Mamindlapalli wrote:
> > Note that the following legacy drivers do not comply with this requirement
> > and cannot be fixed without breaking existing users:
> >  - driver1
> >  - driver2
> >  ...  
> I don’t have a definitive list of non-compliant drivers. Would you prefer to add
> a brief note stating that some drivers may not comply, without naming them explicitly?

We don't have to list them all from the start.
It's for a quick sanity check so that users don't duplicate work
validating that their driver is broken. Maybe say ".. following legacy
drivers are known not to comply .." Hopefully the "are known"
sufficiently indicates that we're covering only one quadrant of 
the Rumsfeld matrix.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ