From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: 柳菁峰 <liujingfeng@qianxin.com>
Cc: Marco Elver <elver@google.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"security@kernel.org" <security@kernel.org>,
"syzkaller@googlegroups.com" <syzkaller@googlegroups.com>
Subject: Re: A null-ptr crash in linux-6.4 usb driver
Date: Tue, 31 Oct 2023 12:36:59 +0100 [thread overview]
Message-ID: <2023103132-flinch-rectified-d758@gregkh> (raw)
In-Reply-To: <b60e7642b76b464ca4acddcba5329a3d@qianxin.com>
On Tue, Oct 31, 2023 at 11:10:45AM +0000, 柳菁峰 wrote:
> OK, I took a look and it may be the same reason that caused the
> crash,but I just tested it on the latest Linux-6.6,it also crashed
> while running the reproducer,it didn't be fixed.
Very true, you are injecting faults into the system, so the system
faulted! You are succeeding in breaking things.
But the trick is, is this actually a valid fault? Or is it something
that can never actually happen in real life? That's for you to
determine please.
> > Looks like this report from over a year ago:
> > https://lore.kernel.org/all/000000000000bb7f1c05da29b601@google.com/
>
>
> It seems that this issue will not be fixed because it must rely on
> fault-inject, right?
Yes.
> I am not familiar with this part of the kernel code, and if fixing
> this issue is very difficult, I may not be able to provide an useful
> patch,sorry.
Try it and see! You have the reproducer, so you are in the best
position to work on this.
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-31 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 11:10 A null-ptr crash in linux-6.4 usb driver 柳菁峰
2023-10-31 11:36 ` gregkh [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-31 8:20 柳菁峰
2023-10-31 8:53 ` Marco Elver
2023-10-31 9:12 ` gregkh
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=2023103132-flinch-rectified-d758@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liujingfeng@qianxin.com \
--cc=rafael@kernel.org \
--cc=security@kernel.org \
--cc=syzkaller@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