All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net 0/2] net: atm: protect dev_lec[] with a mutex
Date: Thu, 19 Jun 2025 15:40:18 +0000	[thread overview]
Message-ID: <175034761899.906129.12488340697198687590.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250618140844.1686882-1-edumazet@google.com>

Hello:

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

On Wed, 18 Jun 2025 14:08:42 +0000 you wrote:
> Based on an initial syzbot report.
> 
> First patch is adding lec_mutex to address the report.
> 
> Second patch protects /proc/net/atm/lec operations.
> 
> We probably should delete this driver, it seems quite broken.
> 
> [...]

Here is the summary with links:
  - [net,1/2] net: atm: add lec_mutex
    https://git.kernel.org/netdev/net/c/d13a3824bfd2
  - [net,2/2] net: atm: fix /proc/net/atm/lec handling
    https://git.kernel.org/netdev/net/c/d03b79f459c7

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-06-19 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 14:08 [PATCH net 0/2] net: atm: protect dev_lec[] with a mutex Eric Dumazet
2025-06-18 14:08 ` [PATCH net 1/2] net: atm: add lec_mutex Eric Dumazet
2025-06-18 14:08 ` [PATCH net 2/2] net: atm: fix /proc/net/atm/lec handling Eric Dumazet
2025-06-18 23:43   ` Francois Romieu
2025-06-19  2:37     ` Eric Dumazet
2025-06-19 15:40 ` 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=175034761899.906129.12488340697198687590.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --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.