From: "Bryant G. Ly" <bryantly@linux.ibm.com>
To: Wei Yongjun <weiyongjun1@huawei.com>,
"Bryant G. Ly" <bryantly@linux.vnet.ibm.com>,
Steven Royer <seroyer@linux.vnet.ibm.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH -next] misc: ibmvmc: Use GFP_ATOMIC under spin lock
Date: Tue, 29 May 2018 09:15:39 -0500 [thread overview]
Message-ID: <995601ab-6fa5-4a72-fd49-337976755861@linux.ibm.com> (raw)
In-Reply-To: <1527327959-83701-1-git-send-email-weiyongjun1@huawei.com>
On 5/26/18 4:45 AM, Wei Yongjun wrote:
> The function alloc_dma_buffer() is called from ibmvmc_add_buffer(),
> in which a spin lock be held here, so we should use GFP_ATOMIC when
> a lock is held.
>
> Fixes: 0eca353e7ae7 ("misc: IBM Virtual Management Channel Driver (VMC)")
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> ---
> drivers/misc/ibmvmc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/misc/ibmvmc.c b/drivers/misc/ibmvmc.c
> index fb83d13..8f82bb9 100644
> --- a/drivers/misc/ibmvmc.c
> +++ b/drivers/misc/ibmvmc.c
> @@ -273,7 +273,7 @@ static void *alloc_dma_buffer(struct vio_dev *vdev, size_t size,
> dma_addr_t *dma_handle)
> {
> /* allocate memory */
> - void *buffer = kzalloc(size, GFP_KERNEL);
> + void *buffer = kzalloc(size, GFP_ATOMIC);
>
> if (!buffer) {
> *dma_handle = 0;
>
Reviewed-by: Bryant G. Ly <bryantly@linux.vnet.ibm.com>
prev parent reply other threads:[~2018-05-29 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-26 9:45 Wei Yongjun
2018-05-29 14:15 ` Bryant G. Ly [this message]
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=995601ab-6fa5-4a72-fd49-337976755861@linux.ibm.com \
--to=bryantly@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=bryantly@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seroyer@linux.vnet.ibm.com \
--cc=weiyongjun1@huawei.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®