netdev - Re: [PATCH net-next 2/2] mlxsw: pci: Add shutdown method in PCI 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]

Date:   Tue, 23 Nov 2021 11:15:08 +0200
From:   Ido Schimmel <idosch@...sch.org>
To:     Denis Kirjanov <dkirjanov@...e.de>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
        jiri@...dia.com, mlxsw@...dia.com,
        Danielle Ratson <danieller@...dia.com>,
        Eric Biederman <ebiederm@...ssion.com>,
        Ido Schimmel <idosch@...dia.com>
Subject: Re: [PATCH net-next 2/2] mlxsw: pci: Add shutdown method in PCI
 driver

On Tue, Nov 23, 2021 at 11:47:34AM +0300, Denis Kirjanov wrote:
> 
> 
> 11/23/21 10:54 AM, Ido Schimmel пишет:
> > From: Danielle Ratson <danieller@...dia.com>
> > 
> > On an arm64 platform with the Spectrum ASIC, after loading and executing
> > a new kernel via kexec, the following trace [1] is observed. This seems
> > to be caused by the fact that the device is not properly shutdown before
> > executing the new kernel.
> 
> This should be sent to net tree instead of net-next with Fixes tag added.

This is not a regression (never worked) and the system does not crash.
The trace is only observed on a specific platform and only with kexec
which I assume nobody is using but our team (for development purposes).

Therefore, I prefer to route it via net-next. If users complain
(unlikely), I will send backports to stable kernels.