linux-kernel - Re: [PATCH v2] scsi: pm8001: Fix bogus FW crash for maxcpus=1

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: <164308671270.32373.5920693563555904240.b4-ty@oracle.com>
Date:   Tue, 25 Jan 2022 00:40:41 -0500
From:   "Martin K. Petersen" <martin.petersen@...cle.com>
To:     jinpu.wang@...ud.ionos.com, Ajish.Koshy@...rochip.com,
        damien.lemoal@...nsource.wdc.com, jejb@...ux.ibm.com,
        John Garry <john.garry@...wei.com>
Cc:     "Martin K . Petersen" <martin.petersen@...cle.com>,
        Ruksar.devadi@...rochip.com, ipylypiv@...gle.com,
        linux-kernel@...r.kernel.org, vishakhavc@...gle.com,
        linux-scsi@...r.kernel.org, Viswas.G@...rochip.com,
        Vasanthalakshmi.Tharmarajan@...rochip.com
Subject: Re: [PATCH v2] scsi: pm8001: Fix bogus FW crash for maxcpus=1

On Tue, 18 Jan 2022 20:15:05 +0800, John Garry wrote:

> According to the comment in check_fw_ready() we should not check the
> IOP1_READY field in register SCRATCH_PAD_1 for 8008 or 8009 controllers.
> 
> However we check this very field in process_oq() for processing the highest
> index interrupt vector. The highest interrupt vector is checked as the FW
> is programmed to signal fatal errors through this irq.
> 
> [...]

Applied to 5.17/scsi-fixes, thanks!

[1/1] scsi: pm8001: Fix bogus FW crash for maxcpus=1
      https://git.kernel.org/mkp/scsi/c/62afb379a0fe

-- 
Martin K. Petersen	Oracle Linux Engineering