From: James Smart <jsmart2021@gmail.com>
To: kbuild-all@lists.01.org
Subject: Re: [mkp-scsi:for-next 67/132] drivers/scsi/elx/libefc/efc_els.c:73 efc_els_io_alloc_size() warn: sleeping in atomic context
Date: Mon, 10 Jan 2022 08:39:36 -0800 [thread overview]
Message-ID: <39a00fdf-e6fd-f421-ccc5-73aec33595e1@gmail.com> (raw)
In-Reply-To: <20220110071104.GA625@lst.de>
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
On 1/9/2022 11:11 PM, Christoph Hellwig wrote:
> So while this warning is correct, it is not new. GFP_DMA can sleep
> just like GFP_KERNEL. Someone was already trying to give this a spin
> on the linux-scsi list, but we really need maintainer helper here.
Yep - I'll go look at it.
-- james
WARNING: multiple messages have this Message-ID (diff)
From: James Smart <jsmart2021@gmail.com>
To: Christoph Hellwig <hch@lst.de>, Dan Carpenter <dan.carpenter@oracle.com>
Cc: kbuild@lists.01.org, lkp@intel.com, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [mkp-scsi:for-next 67/132] drivers/scsi/elx/libefc/efc_els.c:73 efc_els_io_alloc_size() warn: sleeping in atomic context
Date: Mon, 10 Jan 2022 08:39:36 -0800 [thread overview]
Message-ID: <39a00fdf-e6fd-f421-ccc5-73aec33595e1@gmail.com> (raw)
In-Reply-To: <20220110071104.GA625@lst.de>
On 1/9/2022 11:11 PM, Christoph Hellwig wrote:
> So while this warning is correct, it is not new. GFP_DMA can sleep
> just like GFP_KERNEL. Someone was already trying to give this a spin
> on the linux-scsi list, but we really need maintainer helper here.
Yep - I'll go look at it.
-- james
next prev parent reply other threads:[~2022-01-10 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 15:50 [mkp-scsi:for-next 67/132] drivers/scsi/elx/libefc/efc_els.c:73 efc_els_io_alloc_size() warn: sleeping in atomic context kernel test robot
2022-01-10 7:01 ` Dan Carpenter
2022-01-10 7:01 ` Dan Carpenter
2022-01-10 7:11 ` Christoph Hellwig
2022-01-10 7:11 ` Christoph Hellwig
2022-01-10 16:39 ` James Smart [this message]
2022-01-10 16:39 ` James Smart
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=39a00fdf-e6fd-f421-ccc5-73aec33595e1@gmail.com \
--to=jsmart2021@gmail.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.