From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: cgel.zte@gmail.com, jejb@linux.ibm.com
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Minghao Chi <chi.minghao@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH] drivers/scsi/csiostor: do not sleep with a spin lock held
Date: Wed, 19 Jan 2022 17:45:33 +0900 [thread overview]
Message-ID: <f68657d6-027c-c842-ce35-5524cd782c7e@opensource.wdc.com> (raw)
In-Reply-To: <20220119055955.931355-1-chi.minghao@zte.com.cn>
On 1/19/22 14:59, cgel.zte@gmail.com wrote:
> From: Minghao Chi <chi.minghao@zte.com.cn>
>
> The might_sleep_if function in the mempool_alloc
> may cause a sleep lock.We can't mempool_alloc()
> with a spin lock held, so bring it up front.
But the allocation is GFP_ATOMIC, which does not have
__GFP_DIRECT_RECLAIM, so how come mempool_alloc() triggers the
might_sleep() warning ?
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
> Signed-off-by: CGEL ZTE <cgel.zte@gmail.com>
> ---
> drivers/scsi/csiostor/csio_attr.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/csiostor/csio_attr.c b/drivers/scsi/csiostor/csio_attr.c
> index 200e50089711..3d4ab439c756 100644
> --- a/drivers/scsi/csiostor/csio_attr.c
> +++ b/drivers/scsi/csiostor/csio_attr.c
> @@ -424,8 +424,8 @@ csio_fcoe_alloc_vnp(struct csio_hw *hw, struct csio_lnode *ln)
>
> /* Issue VNP cmd to alloc vport */
> /* Allocate Mbox request */
> - spin_lock_irq(&hw->lock);
> mbp = mempool_alloc(hw->mb_mempool, GFP_ATOMIC);
> + spin_lock_irq(&hw->lock);
> if (!mbp) {
> CSIO_INC_STATS(hw, n_err_nomem);
> ret = -ENOMEM;
> @@ -505,8 +505,8 @@ csio_fcoe_free_vnp(struct csio_hw *hw, struct csio_lnode *ln)
> /* Issue VNP cmd to free vport */
> /* Allocate Mbox request */
>
> - spin_lock_irq(&hw->lock);
> mbp = mempool_alloc(hw->mb_mempool, GFP_ATOMIC);
> + spin_lock_irq(&hw->lock);
> if (!mbp) {
> CSIO_INC_STATS(hw, n_err_nomem);
> ret = -ENOMEM;
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-01-19 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 5:59 [PATCH] drivers/scsi/csiostor: do not sleep with a spin lock held cgel.zte
2022-01-19 8:45 ` Damien Le Moal [this message]
2022-01-19 8:57 ` cgel.zte
2022-01-19 9:05 ` Damien Le Moal
2022-01-19 9:22 ` cgel.zte
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=f68657d6-027c-c842-ce35-5524cd782c7e@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=zealci@zte.com.cn \
/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