mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	jgross@suse.com, gregkh@linuxfoundation.org
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] xen: xen-pciback: Replace GFP_ATOMIC with GFP_KERNEL in pcistub_probe
Date: Wed, 11 Apr 2018 09:00:40 +0800	[thread overview]
Message-ID: <311acb17-1cab-bb1a-b612-23e7523f6709@gmail.com> (raw)
In-Reply-To: <9703e77f-35e8-aa11-9ddb-fdc322efd6d2@oracle.com>



On 2018/4/10 23:01, Boris Ostrovsky wrote:
> On 04/10/2018 10:31 AM, Jia-Ju Bai wrote:
>>
>>
>> On 2018/4/10 22:27, Boris Ostrovsky wrote:
>>> On 04/09/2018 11:03 AM, Jia-Ju Bai wrote:
>>>> pcistub_probe() is never called in atomic context.
>>>> This function is only set as ".probe" in struct pci_driver.
>>>>
>>>> Despite never getting called from atomic context,
>>>> pcistub_probe() calls kmalloc() 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>
>>> What about use of GFP_ATOMIC in pcistub_reg_add()?
>> Thanks for your reply :)
>> I find pcistub_reg_add() is called by pcistub_quirk_add().
>> And pcistub_quirk_add() is called in the macro DRIVER_ATTR().
>> I am not sure whether DRIVER_ATTR() can make the function called in
>> atomic context,
>> so I do not analyze it in my tool.
> I don't see why it needs to be ATOMIC, it's sysfs access. Can you send a
> patch to fix it as well?

Okay, I will send a patch for it soon.
You can have a look :)


Best wishes,
Jia-Ju Bai

  reply	other threads:[~2018-04-11  1:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 15:03 Jia-Ju Bai
2018-04-10 14:27 ` Boris Ostrovsky
2018-04-10 14:31   ` Jia-Ju Bai
2018-04-10 15:01     ` Boris Ostrovsky
2018-04-11  1:00       ` Jia-Ju Bai [this message]
2018-04-12  2:16 ` Boris Ostrovsky
2018-04-17 15:09 ` Boris Ostrovsky

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=311acb17-1cab-bb1a-b612-23e7523f6709@gmail.com \
    --to=baijiaju1990@gmail.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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 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®