From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
idosch@nvidia.com, horms@kernel.org, netdev@vger.kernel.org,
eric.dumazet@gmail.com,
syzbot+d6fa74e3f19d6ee01e3a@syzkaller.appspotmail.com,
jchapman@katalix.com, gnault@redhat.com
Subject: Re: [PATCH v3 net] l2tp: fix tunnel and session refcount leak on seq_file release
Date: Thu, 13 Aug 2026 10:00:06 +0000 [thread overview]
Message-ID: <178661520639.2350073.15095295535866945481.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260811144651.2733424-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 11 Aug 2026 14:46:51 +0000 you wrote:
> In pppol2tp_proc_open() and l2tp_dfs_seq_open(), iteration state
> (pd->tunnel and pd->session) is kept in seq_file private data to allow
> iteration across multiple read() system calls.
>
> However, if userspace closes /proc/net/pppol2tp or /sys/kernel/debug/l2tp/tunnels
> before reading to end-of-file (EOF), any tunnel or session reference stored in
> pd->tunnel / pd->session is left un-dropped when seq_file private data is freed.
>
> [...]
Here is the summary with links:
- [v3,net] l2tp: fix tunnel and session refcount leak on seq_file release
https://git.kernel.org/netdev/net/c/9006c116dd11
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-13 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 14:46 [PATCH v3 net] l2tp: fix tunnel and session refcount leak on seq_file release Eric Dumazet
2026-08-13 10:00 ` 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=178661520639.2350073.15095295535866945481.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=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jchapman@katalix.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+d6fa74e3f19d6ee01e3a@syzkaller.appspotmail.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.