From: Jon Mason <jdmason@kudzu.us>
To: Jia-Ju Bai <baijiaju1990@gmail.com>
Cc: dave.jiang@intel.com, Allen.Hubbe@emc.com,
linux-ntb@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ntb: ntb_transport: Replace GFP_ATOMIC with GFP_KERNEL in ntb_transport_create_queue
Date: Mon, 21 May 2018 20:35:03 -0400 [thread overview]
Message-ID: <20180522003503.GA3255@kudzu.us> (raw)
In-Reply-To: <1523366274-31737-1-git-send-email-baijiaju1990@gmail.com>
On Tue, Apr 10, 2018 at 09:17:54PM +0800, Jia-Ju Bai wrote:
> ntb_transport_create_queue() is never called in atomic context.
>
> ntb_transport_create_queue() is only called by ntb_netdev_probe(),
> which is set as ".probe" in struct ntb_transport_client.
>
> Despite never getting called from atomic context,
> ntb_transport_create_queue() calls kzalloc_node() with GFP_ATOMIC,
> which does not sleep for allocation.
> GFP_ATOMIC is not necessary and can be replaced with GFP_KERNEL,
> which can sleep and improve the possibility of sucessful allocation.
>
> This is found by a static analysis tool named DCNS written by myself.
> And I also manually check it
>
> Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
Both patches have been applied to my ntb-next branch.
Thanks,
Jon
> ---
> drivers/ntb/ntb_transport.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/ntb/ntb_transport.c b/drivers/ntb/ntb_transport.c
> index f58d8e3..2c0c8bc 100644
> --- a/drivers/ntb/ntb_transport.c
> +++ b/drivers/ntb/ntb_transport.c
> @@ -1825,7 +1825,7 @@ struct ntb_transport_qp *
> qp->rx_dma_chan ? "DMA" : "CPU");
>
> for (i = 0; i < NTB_QP_DEF_NUM_ENTRIES; i++) {
> - entry = kzalloc_node(sizeof(*entry), GFP_ATOMIC, node);
> + entry = kzalloc_node(sizeof(*entry), GFP_KERNEL, node);
> if (!entry)
> goto err1;
>
> @@ -1836,7 +1836,7 @@ struct ntb_transport_qp *
> qp->rx_alloc_entry = NTB_QP_DEF_NUM_ENTRIES;
>
> for (i = 0; i < qp->tx_max_entry; i++) {
> - entry = kzalloc_node(sizeof(*entry), GFP_ATOMIC, node);
> + entry = kzalloc_node(sizeof(*entry), GFP_KERNEL, node);
> if (!entry)
> goto err2;
>
> --
> 1.9.1
>
prev parent reply other threads:[~2018-05-22 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 13:17 [PATCH 2/2] ntb: ntb_transport: Replace GFP_ATOMIC with GFP_KERNEL in ntb_transport_create_queue Jia-Ju Bai
2018-05-22 0:35 ` Jon Mason [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=20180522003503.GA3255@kudzu.us \
--to=jdmason@kudzu.us \
--cc=Allen.Hubbe@emc.com \
--cc=baijiaju1990@gmail.com \
--cc=dave.jiang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.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