From: Hannes Reinecke <hare@suse.de>
To: Lee Duncan <leeman.duncan@gmail.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Chengfeng Ye <dg573847474@gmail.com>,
Satish Kharat <satishkh@cisco.com>,
Sesidhar Baddela <sebaddel@cisco.com>,
Karan Tilak Kumar <kartilak@cisco.com>,
Lee Duncan <lduncan@suse.com>
Subject: Re: [PATCH v4 1/2] Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock"
Date: Sun, 11 Feb 2024 22:52:27 +0900 [thread overview]
Message-ID: <1e231871-0e49-446f-8a3b-d66e5cf6838b@suse.de> (raw)
In-Reply-To: <c578cdcd46b60470535c4c4a953e6a1feca0dffd.1707500786.git.lduncan@suse.com>
On 2/10/24 02:07, Lee Duncan wrote:
> From: Lee Duncan <lduncan@suse.com>
>
> This reverts commit 1a1975551943f681772720f639ff42fbaa746212
>
> This commit causes interrupts to be lost for FCoE devices,
> since it changed sping locks from "bh" to "irqsave".
>
> Instead, a work queue should be used, and will be addressed
> in a separate patch.
>
> Fixes: 1a1975551943 ("scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock")
> Signed-off-by: Lee Duncan <lduncan@suse.com>
> ---
> drivers/scsi/fcoe/fcoe_ctlr.c | 20 ++++++++------------
> 1 file changed, 8 insertions(+), 12 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Ivo Totev, Andrew McDonald,
Werner Knoblich
next prev parent reply other threads:[~2024-02-11 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 18:07 [PATCH v4 0/2] Ensure FCoE target interrupts work correctly Lee Duncan
2024-02-09 18:07 ` [PATCH v4 1/2] Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock" Lee Duncan
2024-02-11 13:52 ` Hannes Reinecke [this message]
2024-02-09 18:07 ` [PATCH v4 2/2] fnic: move fnic_fnic_flush_tx() to a work queue Lee Duncan
2024-02-13 1:57 ` [PATCH v4 0/2] Ensure FCoE target interrupts work correctly Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1e231871-0e49-446f-8a3b-d66e5cf6838b@suse.de \
--to=hare@suse.de \
--cc=dg573847474@gmail.com \
--cc=kartilak@cisco.com \
--cc=lduncan@suse.com \
--cc=leeman.duncan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®