From: Hengyu Liang <hengyul@cs.unc.edu>
To: gnault@redhat.com
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
jchapman@katalix.com, tparkin@katalix.com
Subject: Re: [PATCH net] l2tp: only return sessions of the given tunnel in l2tp_session_get()
Date: Mon, 26 Oct 2026 08:57:02 -0400 [thread overview]
Message-ID: <20261026125702.3101778-1-hengyul@cs.unc.edu> (raw)
In-Reply-To: <at8-2mFyrmPxfu29@debian>
Hi Guillaume,
Thanks for looking at this.
I wasn't sure about the intended semantics. l2tp.rst says "L2TPv3
session ids are unique across all tunnels", but it also says Linux
allows the same ID in different tunnels, told apart by sk, and
l2tp_session_register() still allows that for UDP encap.
The patch only changes callers of l2tp_session_get() that pass a
tunnel_id, and the result differs from v6.8:
- pppol2tp_connect() for session 5 in tunnel 2 fails with EEXIST if
tunnel 1 (another UDP socket) already has a connected session 5.
- "ip l2tp del session tunnel_id 4 session_id 7" deletes tunnel 3's
session 7 when only tunnel 3 has it. On v6.8 it fails. l2tp.rst
describes CONN_ID there as the parent tunnel of the session.
Am I misreading the documentation, is the documentation out of date, or
is this behaviour not intended?
Thanks,
Hengyu
next prev parent reply other threads:[~2026-10-26 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 14:58 [PATCH net] l2tp: only return sessions of the given tunnel in l2tp_session_get() Hengyu Liang
2026-10-25 15:01 ` netdev-bot+sinfo
2026-10-26 8:47 ` Hengyu Liang
2026-10-26 11:51 ` Guillaume Nault
2026-10-26 12:57 ` Hengyu Liang [this message]
2026-10-26 16:55 ` Guillaume Nault
2026-10-27 4:32 ` Hengyu Liang
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=20261026125702.3101778-1-hengyul@cs.unc.edu \
--to=hengyul@cs.unc.edu \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gnault@redhat.com \
--cc=horms@kernel.org \
--cc=jchapman@katalix.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tparkin@katalix.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