From: Bart Van Assche <bvanassche@acm.org>
To: phil@philpotter.co.uk
Cc: David Wang <00107082@163.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com
Subject: Re: [BUG] general protection fault when connecting an old mp3/usb device
Date: Tue, 19 Aug 2025 12:20:51 -0700 [thread overview]
Message-ID: <2899b7cb-106b-48dc-890f-9cc80f1d1f8b@acm.org> (raw)
In-Reply-To: <20250818095008.6473-1-00107082@163.com>
On 8/18/25 2:50 AM, David Wang wrote:
> [Sat Aug 23 03:56:09 2025] Oops: general protection fault, probably for non-canonical address 0x2e2e2f2e2e2f308e: 0000 [#1] SMP NOPTI
> [Sat Aug 23 03:56:09 2025] Call Trace:
> [Sat Aug 23 03:56:09 2025] <TASK>
> [Sat Aug 23 03:56:09 2025] sr_do_ioctl+0x5b/0x1c0 [sr_mod]
> [Sat Aug 23 03:56:09 2025] sr_packet+0x2c/0x50 [sr_mod]
> [Sat Aug 23 03:56:09 2025] cdrom_get_disc_info+0x60/0xe0 [cdrom]
> [Sat Aug 23 03:56:09 2025] cdrom_mrw_exit+0x29/0xb0 [cdrom]
> [Sat Aug 23 03:56:09 2025] ? xa_destroy+0xaa/0x120
> [Sat Aug 23 03:56:09 2025] unregister_cdrom+0x76/0xc0 [cdrom]
> [Sat Aug 23 03:56:09 2025] sr_free_disk+0x44/0x50 [sr_mod]
> [Sat Aug 23 03:56:09 2025] disk_release+0xb0/0xe0
> [Sat Aug 23 03:56:09 2025] device_release+0x37/0x90
> [Sat Aug 23 03:56:09 2025] kobject_put+0x8e/0x1d0
> [Sat Aug 23 03:56:09 2025] blkdev_release+0x11/0x20
> [Sat Aug 23 03:56:09 2025] __fput+0xe3/0x2a0
> [Sat Aug 23 03:56:09 2025] task_work_run+0x59/0x90
> [Sat Aug 23 03:56:09 2025] exit_to_user_mode_loop+0xd6/0xe0
> [Sat Aug 23 03:56:09 2025] do_syscall_64+0x1c1/0x1e0
> [Sat Aug 23 03:56:09 2025] entry_SYSCALL_64_after_hwframe+0x76/0x7e
Phillip, is this behavior perhaps introduced by commit 5ec9d26b78c4
("cdrom: Call cdrom_mrw_exit from cdrom_release function")? Please do
not call code that invokes ioctls from the disk_release() callback.
Thanks,
Bart.
next prev parent reply other threads:[~2025-08-19 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 9:50 [BUG] general protection fault when connecting an old mp3/usb device David Wang
2025-08-19 19:20 ` Bart Van Assche [this message]
2025-08-20 1:38 ` David Wang
2025-08-20 10:02 ` David Wang
2025-08-20 20:06 ` Phillip Potter
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=2899b7cb-106b-48dc-890f-9cc80f1d1f8b@acm.org \
--to=bvanassche@acm.org \
--cc=00107082@163.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=phil@philpotter.co.uk \
/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