From: Dave Hansen <dave.hansen@intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Saranya Gopal" <saranya.gopal@intel.com>,
"Rajaram Regupathy" <rajaram.regupathy@intel.com>,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Wayne Chang" <waynec@nvidia.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Mario Limonciello" <mario.limonciello@amd.com>,
linux-usb@vger.kernel.org
Subject: Re: ucsi debugfs oops (current Linus pre-6.6-rc1)
Date: Tue, 5 Sep 2023 12:16:35 -0700 [thread overview]
Message-ID: <911a3e8f-7adf-6089-6651-1f847e4edce6@intel.com> (raw)
In-Reply-To: <700df3c4-2f6c-85f9-6c61-065bc5b2db3a@intel.com>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
On 9/5/23 12:10, Dave Hansen wrote:
> I'm having some problems booting Linus's current tree. It seems to have
> happened in some content between commit 3f86ed6ec0b3 and df0383ffad.
>
> I'm suspecting this commit:
>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=df0383ffad64dc09954a60873c1e202b47f08d90
The attached patch works around the problem for me and at least lets me
get booting again. I do see this in dmesg (from my patch):
[ 7.818203] no ucsi->debugfs
[-- Attachment #2: sillydebug.patch --]
[-- Type: text/x-patch, Size: 518 bytes --]
diff --git a/drivers/usb/typec/ucsi/debugfs.c b/drivers/usb/typec/ucsi/debugfs.c
index 0c7bf88d4a7f..f99d84165f3e 100644
--- a/drivers/usb/typec/ucsi/debugfs.c
+++ b/drivers/usb/typec/ucsi/debugfs.c
@@ -84,6 +84,14 @@ void ucsi_debugfs_register(struct ucsi *ucsi)
void ucsi_debugfs_unregister(struct ucsi *ucsi)
{
+ if (!ucsi) {
+ printk("no ucsi");
+ return;
+ }
+ if (!ucsi->debugfs) {
+ printk("no ucsi->debugfs");
+ return;
+ }
debugfs_remove_recursive(ucsi->debugfs->dentry);
kfree(ucsi->debugfs);
}
next prev parent reply other threads:[~2023-09-05 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 19:10 Dave Hansen
2023-09-05 19:16 ` Dave Hansen [this message]
2023-09-05 19:25 ` Mario Limonciello
2023-09-06 8:36 ` Heikki Krogerus
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=911a3e8f-7adf-6089-6651-1f847e4edce6@intel.com \
--to=dave.hansen@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=neil.armstrong@linaro.org \
--cc=rajaram.regupathy@intel.com \
--cc=saranya.gopal@intel.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=waynec@nvidia.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
all inboxes | Powered by JetHome®