netdev - Re: Potential regression/bug in net/mlx5 driver

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: <20230417083825.6e034c75@kernel.org>
Date:   Mon, 17 Apr 2023 08:38:25 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Saeed Mahameed <saeedm@...dia.com>
Cc:     Paul Moore <paul@...l-moore.com>,
        Leon Romanovsky <leon@...nel.org>,
        Linux regressions mailing list <regressions@...ts.linux.dev>,
        Saeed Mahameed <saeed@...nel.org>,
        Shay Drory <shayd@...dia.com>, netdev@...r.kernel.org,
        selinux@...r.kernel.org, Tariq Toukan <tariqt@...dia.com>
Subject: Re: Potential regression/bug in net/mlx5 driver

On Fri, 14 Apr 2023 21:40:35 -0700 Saeed Mahameed wrote:
> >What do we do now, tho? If the main side effect of a revert is that
> >users of a newfangled device with an order of magnitude lower
> >deployment continue to see a warning/error in the logs - I'm leaning
> >towards applying it :(  
> 
> I tend to agree with you but let me check with the FW architect what he has
> to offer, either we provide a FW version check or another more accurate
> FW cap test that could solve the issue for everyone. If I don't come up with
> a solution by next Wednesday I will repost your revert in my next net PR
> on Wednesday. You can mark it awaiting-upstream for now, if that works for
> you.

OK, sounds good.