From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217174] New: Plugging in usb external drive, mount and umount causes kernel Oops
Date: Fri, 10 Mar 2023 18:49:38 +0000 [thread overview]
Message-ID: <bug-217174-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217174
Bug ID: 217174
Summary: Plugging in usb external drive, mount and umount
causes kernel Oops
Product: Drivers
Version: 2.5
Kernel Version: 6.2.3
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: mike.cloaked@gmail.com
Regression: No
Created attachment 303922
--> https://bugzilla.kernel.org/attachment.cgi?id=303922&action=edit
Kernel Oops for usb external drive umount with kernel 6.2.3
The problem I am about to describe does not occur with the kernel 6.2.2, as the
current arch kernel in the repos.
With kerne. 6.2.3 if I simply plug in a usb external drive, mount it and umount
it, then the journal has a kernel Oops as in the attached journal segment.
This was tested on three different machines, running arch kernel 6.2.2 and
6.2.3 (from arch testing), and is fully reproducible. In all cases running
kernel 6.2.2 does not give this issue, and running kernel 6.2.3 causes the
kernel Oops as soon as the external usb drive is umounted.
Once the Oops had occurred then the machine will hang on shutdown and requires
a hard reboot.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-03-10 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 18:49 bugzilla-daemon [this message]
2023-03-10 19:12 ` [Bug 217174] Plugging in usb external drive, mount and umount causes kernel Oops bugzilla-daemon
2023-03-10 19:16 ` bugzilla-daemon
2023-03-10 19:26 ` bugzilla-daemon
2023-03-10 20:43 ` bugzilla-daemon
2023-03-11 11:18 ` 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-217174-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).