From: Shuah Khan <skhan@linuxfoundation.org>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Shuah Khan <shuah@kernel.org>,
Valentina Manea <valentina.manea.m@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
syzbot <syzbot+bf1a360e305ee719e364@syzkaller.appspotmail.com>,
Nazime Hande Harputluoglu <handeharputlu@google.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: KASAN: null-ptr-deref Write in event_handler
Date: Mon, 19 Oct 2020 09:22:21 -0600 [thread overview]
Message-ID: <9887a296-b98e-ef2b-553f-448cd9ad72b6@linuxfoundation.org> (raw)
In-Reply-To: <CAAeHK+xpbCExXG2xP5xGBbMpJg4sesHLsMn++Qz47jfNELhXjQ@mail.gmail.com>
On 10/19/20 9:10 AM, Andrey Konovalov wrote:
> On Fri, Oct 16, 2020 at 9:48 PM Shuah Khan <skhan@linuxfoundation.org> wrote:
>>
>> Andrey,
>>
>> I am unable to reproduce the problem. I even tweaked the reproducer
>> to launch 10 procs and 100 threads.
>>
>> Can you test the following patch with your setup
>>
>> Here it is - also attached.
>
> Hi Shuah,
>
> I get the crash below with this change. It complains about
> kthread_stop_put() being called in atomic context.
>
Thanks for testing. I was concerned about that. I will try to
reproduce the problem again.
I am running into a amd_gpu issue during boot on my test system
with KASAN enabled which results in disabling lock debugging. This
makes it harder to debug and fix this null-ptr-deref Write in
event_handler as it needs KASAN enabled. Fun stuff.
I will switch to a different test system and see if I can reproduce
the problem first.
Thanks again for testing.
thanks,
-- Shuah
next prev parent reply other threads:[~2020-10-19 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 13:59 syzbot
2020-10-05 14:04 ` Andrey Konovalov
2020-10-05 20:44 ` Shuah Khan
2020-10-07 13:56 ` Shuah Khan
2020-10-07 14:28 ` Andrey Konovalov
2020-10-07 15:48 ` Shuah Khan
2020-10-16 19:48 ` Shuah Khan
2020-10-19 15:10 ` Andrey Konovalov
2020-10-19 15:22 ` Shuah Khan [this message]
[not found] ` <20201007103029.16388-1-hdanton@sina.com>
2020-10-09 14:37 ` Shuah Khan
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=9887a296-b98e-ef2b-553f-448cd9ad72b6@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=andreyknvl@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=handeharputlu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=syzbot+bf1a360e305ee719e364@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=valentina.manea.m@gmail.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®