All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Olliver Schinagl <oliver@schinagl.nl>,
	Andreas Noever <andreas.noever@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	linux-usb <linux-usb@vger.kernel.org>
Subject: Re: kernel NULL pointer dereference on hotplug
Date: Wed, 7 Feb 2024 11:21:52 +0200	[thread overview]
Message-ID: <20240207092152.GQ8454@black.fi.intel.com> (raw)
In-Reply-To: <b0388b9e-5ec2-422d-94ce-192b33fef16d@leemhuis.info>

Hi,

On Wed, Feb 07, 2024 at 10:12:07AM +0100, Thorsten Leemhuis wrote:
> On 07.02.24 07:13, Linux regression tracking (Thorsten Leemhuis) wrote:
> > 
> > On 04.02.24 07:40, Mika Westerberg wrote:
> >> On Fri, Feb 02, 2024 at 05:47:01PM +0100, Olliver Schinagl wrote:
> >>>
> >>> I noticed this nasty kernel NULL pointer dereference yesterday on
> >>> 6.7.2-arch1-1 (haven't done this in a while) but also today, after updating
> >>> to 6.7.3-arch1-1 it's still there, so dumping the panic here. Hopefully
> >>> it'll be resolved by 6.7.4-arch1-1.
> >>
> >> Thanks for the report.
> >>
> >>> The thunderbolt gbit adapter always worked in the past, so this seems like a
> >>> regression. Anyway, here's the log.
> 
> FWIW, Leon Weiß (BCCed) just posted another NULL pointer deference issue
> in 6.7 and found the culprit; for details see:
> https://lore.kernel.org/all/38c253ea42072cc825dc969ac4e6b9b600371cc8.camel@ruhr-uni-bochum.de/
>
> Sadly Leon's report lacks a backtrace we had in this thread (
> https://lore.kernel.org/all/c24c7882-6254-4e68-8f22-f3e8f65dc84f@schinagl.nl/
> ), so it might be something totally different. Leon's problem afaics
> also happens on unplug while this one on hotplug. But well, I thought I
> better quickly mention it here anyway so everyone is aware of it.

Thanks for the information. 

As you mention, this seems to be unrelated. The one above is about DRM
and graphics, the one Olliver reported is about Thunderbolt (okay there
is Thunderbolt device involved in both but this one seems to be purely
DP thing).

      reply	other threads:[~2024-02-07 13:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 16:47 kernel NULL pointer dereference on hotplug Olliver Schinagl
2024-02-04  6:40 ` Mika Westerberg
2024-02-07  6:13   ` Linux regression tracking (Thorsten Leemhuis)
2024-02-07  9:12     ` Thorsten Leemhuis
2024-02-07  9:21       ` Mika Westerberg [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=20240207092152.GQ8454@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=oliver@schinagl.nl \
    --cc=regressions@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.