[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2023103132-flinch-rectified-d758@gregkh>
Date: Tue, 31 Oct 2023 12:36:59 +0100
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: 柳菁峰 <liujingfeng@...nxin.com>
Cc: Marco Elver <elver@...gle.com>,
"rafael@...nel.org" <rafael@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"security@...nel.org" <security@...nel.org>,
"syzkaller@...glegroups.com" <syzkaller@...glegroups.com>
Subject: Re: A null-ptr crash in linux-6.4 usb driver
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
Powered by blists - more mailing lists