From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Meneghini <jmeneghi@redhat.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
GR-QLogic-Storage-Upstream@marvell.com, mlombard@redhat.com,
skashyap@marvell.com, guazhang@redhat.com
Subject: Re: [PATCH v3] scsi: bnx2fc: flush destroy_work queue before calling bnx2fc_interface_put
Date: Tue, 18 Jan 2022 22:51:03 -0500 [thread overview]
Message-ID: <yq1pmool6y1.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220115040044.1013475-1-jmeneghi@redhat.com> (John Meneghini's message of "Fri, 14 Jan 2022 23:00:44 -0500")
John,
> The bnx2fc_destroy functions are removing the interface before calling
> destroy_work. This results multiple WARNings from sysfs_remove_group
> as the controller rport device attributes are removed to early.
>
> Replace the fcoe_port's destroy_work queue. It's not needed.
Applied to 5.17/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-01-19 3:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 4:00 John Meneghini
2022-01-19 3:51 ` Martin K. Petersen [this message]
2022-01-25 5:40 ` 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=yq1pmool6y1.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=guazhang@redhat.com \
--cc=jmeneghi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mlombard@redhat.com \
--cc=skashyap@marvell.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
Powered by JetHome