All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ying Lu <luying526@gmail.com>
Cc: oneukum@suse.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
	luying1@xiaomi.com
Subject: Re: [PATCH v4 0/1] usbnet:fix NPE during rx_complete
Date: Fri, 04 Apr 2025 14:30:46 +0000	[thread overview]
Message-ID: <174377704699.3279917.8004013265274717921.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1743584159.git.luying1@xiaomi.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  2 Apr 2025 16:58:58 +0800 you wrote:
> From: Ying Lu <luying1@xiaomi.com>
> 
> The patchset fix the issue caused by the following modifications:
> commit 04e906839a053f092ef53f4fb2d610983412b904
> (usbnet: fix cyclical race on disconnect with work queue)
> 
> The issue:
> The usb_submit_urb function lacks a usbnet_going_away validation,
> whereas __usbnet_queue_skb includes this check. This inconsistency
> creates a race condition where: A URB request may succeed, but
> the corresponding SKB data fails to be queued.
> 
> [...]

Here is the summary with links:
  - [v4,1/1] usbnet:fix NPE during rx_complete
    https://git.kernel.org/netdev/net/c/51de36000934

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-04-04 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  8:58 [PATCH v4 0/1] usbnet:fix NPE during rx_complete Ying Lu
2025-04-02  8:58 ` [PATCH v4 1/1] " Ying Lu
2025-04-04 14:30 ` 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=174377704699.3279917.8004013265274717921.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=luying1@xiaomi.com \
    --cc=luying526@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.