From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: benjamin.tissoires@redhat.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hid: hid-core: Fix a sleep-in-atomic-context bug in __hid_request()
Date: Thu, 6 Sep 2018 10:35:14 +0800 [thread overview]
Message-ID: <6ec3d032-6d33-d2af-965f-7f3457dc8311@gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1809051026540.15880@cbobk.fhfr.pm>
On 2018/9/5 16:29, Jiri Kosina wrote:
> On Sat, 1 Sep 2018, Jia-Ju Bai wrote:
>
>> The driver may sleep with holding a spinlock.
>>
>> The function call paths (from bottom to top) in Linux-4.16 are:
>>
>> [FUNC] hid_alloc_report_buf(GFP_KERNEL)
>> drivers/hid/hid-core.c, 1435:
>> hid_alloc_report_buf in __hid_request
>> ./include/linux/hid.h, 1023:
>> __hid_request in hid_hw_request
>> drivers/hid/hid-picolcd_core.c, 111:
>> hid_hw_request in picolcd_send_and_wait
>> drivers/hid/hid-picolcd_core.c, 100:
>> _raw_spin_lock_irqsave in picolcd_send_and_wait
>>
>> [FUNC] hid_alloc_report_buf(GFP_KERNEL)
>> drivers/hid/hid-core.c, 1435:
>> hid_alloc_report_buf in __hid_request
>> ./include/linux/hid.h, 1023:
>> __hid_request in hid_hw_request
>> drivers/hid/hid-picolcd_core.c, 245:
>> hid_hw_request in picolcd_reset
>> drivers/hid/hid-picolcd_core.c, 235:
>> _raw_spin_lock_irqsave in picolcd_reset
>>
>> [FUNC] hid_alloc_report_buf(GFP_KERNEL)
>> drivers/hid/hid-core.c, 1435:
>> hid_alloc_report_buf in __hid_request
>> ./include/linux/hid.h, 1023:
>> __hid_request in hid_hw_request
>> drivers/hid/hid-picolcd_fb.c, 215:
>> hid_hw_request in picolcd_fb_reset
>> drivers/hid/hid-picolcd_fb.c, 206:
>> _raw_spin_lock_irqsave in picolcd_fb_reset
>>
>> [FUNC] hid_alloc_report_buf(GFP_KERNEL)
>> drivers/hid/hid-core.c, 1435:
>> hid_alloc_report_buf in __hid_request
>> ./include/linux/hid.h, 1023:
>> __hid_request in hid_hw_request
>> drivers/hid/hid-lg4ff.c, 465:
>> hid_hw_request in lg4ff_play
>> drivers/hid/hid-lg4ff.c, 441:
>> _raw_spin_lock_irqsave in lg4ff_play
>>
>> To fix this bug, GFP_KERNEL is replaced with GFP_ATOMIC.
>>
>> This bug is found by my static analysis tool DSAC.
> Could you please rewrite the changelog so that it's human readable? The
> above is a bit hard to understand, I think something along the lines of
> "__hid_request() has to be allocating with GFP_ATOMIC because there are
> the following callchains leading to __hid_request() being an atomic
> context: ... a->b->c.._hid_request()" etc.
>
Okay, I will send a new patch.
Best wishes,
Jia-Ju Bai
prev parent reply other threads:[~2018-09-06 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 12:16 [PATCH] hid: hid-core: Fix a sleep-in-atomic-context bug in __hid_request() Jia-Ju Bai
2018-09-05 8:29 ` Jiri Kosina
2018-09-06 2:35 ` Jia-Ju Bai [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=6ec3d032-6d33-d2af-965f-7f3457dc8311@gmail.com \
--to=baijiaju1990@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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