public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: 柳菁峰 <liujingfeng@qianxin.com>
To: Marco Elver <elver@google.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"rafael@kernel.org" <rafael@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"security@kernel.org" <security@kernel.org>,
	"secalert@redhat.com" <secalert@redhat.com>,
	"syzkaller@googlegroups.com" <syzkaller@googlegroups.com>
Subject: Re: A null-ptr crash in linux-6.4 usb driver
Date: Tue, 31 Oct 2023 11:10:45 +0000	[thread overview]
Message-ID: <b60e7642b76b464ca4acddcba5329a3d@qianxin.com> (raw)

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.

> 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?
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.

> Great, please submit a patch to resolve this and we will be glad to review it.


             reply	other threads:[~2023-10-31 11:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 11:10 柳菁峰 [this message]
2023-10-31 11:36 ` A null-ptr crash in linux-6.4 usb driver gregkh
  -- 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=b60e7642b76b464ca4acddcba5329a3d@qianxin.com \
    --to=liujingfeng@qianxin.com \
    --cc=elver@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=secalert@redhat.com \
    --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