All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215117] ucsi_acpi: kernel NULL pointer dereference
Date: Thu, 16 Dec 2021 11:09:44 +0000	[thread overview]
Message-ID: <bug-215117-208809-1zefJpM7Lw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215117-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215117

--- Comment #4 from Chris Hixon (linux-kernel-bugs@hixontech.com) ---
It sure seems like a regression, starting at v5.16-rc1. I haven't encountered
this bug in any v5.15 version I've used, including -rc versions (v5.15-rcX),
v5.15(mainline), or v5.15.y(stable).

It seems like the bug still exists in v5.16-rc4, though I wasn't able to
capture a kernel oops the one time I tried that. I'll soon try -rc5.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2021-12-16 11:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23  3:51 [Bug 215117] New: ucsi_acpi: kernel NULL pointer dereference bugzilla-daemon
2021-12-07  9:16 ` [Bug 215117] " bugzilla-daemon
2021-12-16  9:22 ` [Bug 215117] New: " Thorsten Leemhuis
2021-12-16 11:47   ` Heikki Krogerus
2021-12-21 18:06   ` [Bug 215117] New: ucsi_acpi: kernel NULL pointer dereference #forregzbot Thorsten Leemhuis
2021-12-22  6:32     ` Greg KH
2021-12-22  8:37       ` Thorsten Leemhuis
2021-12-22  9:02         ` Greg KH
2021-12-22  9:39           ` Thorsten Leemhuis
2021-12-16  9:22 ` [Bug 215117] ucsi_acpi: kernel NULL pointer dereference bugzilla-daemon
2021-12-16 11:09 ` bugzilla-daemon [this message]
2021-12-16 11:43 ` bugzilla-daemon
2021-12-16 11:48 ` bugzilla-daemon
2021-12-16 13:01 ` bugzilla-daemon

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=bug-215117-208809-1zefJpM7Lw@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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.