From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220052] The usb/cdc-acm driver uses memory after it is freed
Date: Mon, 05 May 2025 09:27:47 +0000 [thread overview]
Message-ID: <bug-220052-208809-TFKoSgx98J@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220052-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220052
--- Comment #4 from oneukum@suse.com ---
On 30.04.25 14:56, bugzilla-daemon@kernel.org wrote:
> Exchanging the 2 lines as indicated in the patch solves the problem
> completely
> and the kernel panic is not seen anymore. This is proved by 7000 'virtual'
> disconnects.
>
Yes, it solves your particular problem.
Now, with your patch, you first call
acm_submit_read_urbs() -> acm_submit_read_urb():
res = usb_submit_urb(acm->read_urbs[index], mem_flags);
And then you do
+ for (i = 0; i < acm->rx_buflimit; i++)
+ usb_kill_urb(acm->read_urbs[i]);
In other words, you undo what you just did.
Your diagnosis of the issue may be good, but the fix is _not_.
The purpose of acm_softint() is to
1. kill outstanding IO
2. error handling with usb_clear_halt()
3. restart the outstanding IO
You cannot reverse steps 1 and 3 and expect that to work.
The issue must be one of refcounting.
Sorry
Oliver
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-05-05 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 14:31 [Bug 220052] New: The usb/cdc-acm driver uses memory after it is freed bugzilla-daemon
2025-04-24 15:26 ` Greg KH
2025-04-30 12:56 ` Ben Maan
2025-04-24 15:26 ` [Bug 220052] " bugzilla-daemon
2025-04-30 12:48 ` bugzilla-daemon
2025-04-30 12:56 ` bugzilla-daemon
2025-05-05 9:27 ` Oliver Neukum
2025-05-05 9:27 ` bugzilla-daemon [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=bug-220052-208809-TFKoSgx98J@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).