[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <170778915962.2192303.5279236168147495494.b4-ty@oracle.com>
Date: Mon, 12 Feb 2024 20:57:09 -0500
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
Lee Duncan <leeman.duncan@...il.com>
Cc: "Martin K . Petersen" <martin.petersen@...cle.com>,
Chengfeng Ye <dg573847474@...il.com>, hare@...e.de,
Satish Kharat <satishkh@...co.com>,
Sesidhar Baddela <sebaddel@...co.com>,
Karan Tilak Kumar <kartilak@...co.com>, Lee Duncan <lduncan@...e.com>
Subject: Re: [PATCH v4 0/2] Ensure FCoE target interrupts work correctly
On Fri, 09 Feb 2024 10:07:33 -0800, Lee Duncan wrote:
> Commit 1a1975551943 "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock"
> changed locking for fnic/FCoE, but it did so by disabling interrupts
> where they weren't disabled before, and this caused FCoE targets
> to go offline. Reverting that patch fixed the issue.
>
> But to handle the problem originally addressed by the commit,
> instead of modifying the locking, move the work to be done
> into a work queue.
>
> [...]
Applied to 6.8/scsi-fixes, thanks!
[1/2] Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock"
https://git.kernel.org/mkp/scsi/c/977fe773dcc7
[2/2] fnic: move fnic_fnic_flush_tx() to a work queue
https://git.kernel.org/mkp/scsi/c/379a58caa199
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists