netdev - RE: [PATCH net-next 0/3] qed*: Error recovery process

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: <BLUPR18MB0130E67F11EEE010B26933E3A1950@BLUPR18MB0130.namprd18.prod.outlook.com>
Date:   Sun, 27 Jan 2019 13:42:35 +0000
From:   Michal Kalderon <mkalderon@...vell.com>
To:     David Miller <davem@...emloft.net>,
        "michal.kalderon@...ium.com" <michal.kalderon@...ium.com>
CC:     "ariel.elior@...ium.com" <ariel.elior@...ium.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH net-next 0/3] qed*: Error recovery process

> From: David Miller <davem@...emloft.net>
> Sent: Wednesday, January 23, 2019 3:37 AM
> 
> > Parity errors might happen in the device's memories due to momentary
> > bit flips which are caused by radiation.
> > Errors that are not correctable initiate a process kill event, which
> > blocks the device access towards the host and the network, and a
> > recovery process is started in the management FW and in the driver.
> >
> > This series adds the support of this process in the qed core module
> > and in the qede driver (patches 2 & 3).
> > Patch 1 in the series revises the load sequence, to avoid PCI errors
> > that might be observed during a recovery process.
> 
> Series applied.

Thanks Dave, though I don't see this in net-next, I noticed this was recently applied
and reverted from net, should I resend to have it applied to net-next ? 

Thanks,
Michal