From: patchwork-bot+netdevbpf@kernel.org
To: syzbot <syzbot@kernel.org>
Cc: syzkaller-bugs@googlegroups.com, nogikh@google.com,
3chas3@gmail.com, accessrunner-general@lists.sourceforge.net,
gregkh@linuxfoundation.org,
linux-atm-general@lists.sourceforge.net,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
duncan.sands@math.u-psud.fr, linux-kernel@vger.kernel.org,
syzbot@lists.linux.dev
Subject: Re: [PATCH] usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm()
Date: Thu, 06 Aug 2026 15:50:32 +0000 [thread overview]
Message-ID: <178603143263.1348318.9398157117704385774.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <91edfa4c-a63d-400c-9f00-31f3e1f98c00@mail.kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 31 Jul 2026 10:15:20 +0000 (UTC) you wrote:
> From: Aleksandr Nogikh <nogikh@google.com>
>
> If cxacru_cm() encounters an error while submitting or waiting for snd_urb,
> it aborts and returns the error without killing the already submitted
> rcv_urb. This leaves the rcv_urb active.
>
> When this happens during initialization (e.g., in cxacru_atm_start()), the
> driver may ignore the error and proceed to call cxacru_poll_status(), which
> invokes cxacru_cm() again. Attempting to submit the still-active rcv_urb
> triggers a warning in usb_submit_urb():
>
> [...]
Here is the summary with links:
- usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm()
https://git.kernel.org/netdev/net-next/c/d87cabf0b673
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-06 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 10:15 [PATCH] usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm() syzbot
2026-08-06 15:50 ` patchwork-bot+netdevbpf [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=178603143263.1348318.9398157117704385774.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=3chas3@gmail.com \
--cc=accessrunner-general@lists.sourceforge.net \
--cc=duncan.sands@math.u-psud.fr \
--cc=gregkh@linuxfoundation.org \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzbot@kernel.org \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.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