From: James Chapman <jchapman@katalix.com>
To: Ridge Kennedy <ridge.kennedy@alliedtelesis.co.nz>,
netdev@vger.kernel.org
Cc: gnault@redhat.com, tparkin@katalix.com
Subject: Re: [PATCH v2 net] l2tp: Allow duplicate session creation with UDP
Date: Tue, 4 Feb 2020 10:27:35 +0000 [thread overview]
Message-ID: <d14d7bba-c29b-7831-f976-5658e9503bf3@katalix.com> (raw)
In-Reply-To: <20200203232400.28981-1-ridge.kennedy@alliedtelesis.co.nz>
On 03/02/2020 23:24, Ridge Kennedy wrote:
> In the past it was possible to create multiple L2TPv3 sessions with the
> same session id as long as the sessions belonged to different tunnels.
> The resulting sessions had issues when used with IP encapsulated tunnels,
> but worked fine with UDP encapsulated ones. Some applications began to
> rely on this behaviour to avoid having to negotiate unique session ids.
>
> Some time ago a change was made to require session ids to be unique across
> all tunnels, breaking the applications making use of this "feature".
>
> This change relaxes the duplicate session id check to allow duplicates
> if both of the colliding sessions belong to UDP encapsulated tunnels.
>
> Fixes: dbdbc73b4478 ("l2tp: fix duplicate session creation")
> Signed-off-by: Ridge Kennedy <ridge.kennedy@alliedtelesis.co.nz>
Acked-by: James Chapman <jchapman@katalix.com>
> ---
> net/l2tp/l2tp_core.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/net/l2tp/l2tp_core.c b/net/l2tp/l2tp_core.c
> index f82ea12bac37..425b95eb7e87 100644
> --- a/net/l2tp/l2tp_core.c
> +++ b/net/l2tp/l2tp_core.c
> @@ -322,8 +322,13 @@ int l2tp_session_register(struct l2tp_session *session,
>
> spin_lock_bh(&pn->l2tp_session_hlist_lock);
>
> + /* IP encap expects session IDs to be globally unique, while
> + * UDP encap doesn't.
> + */
> hlist_for_each_entry(session_walk, g_head, global_hlist)
> - if (session_walk->session_id == session->session_id) {
> + if (session_walk->session_id == session->session_id &&
> + (session_walk->tunnel->encap == L2TP_ENCAPTYPE_IP ||
> + tunnel->encap == L2TP_ENCAPTYPE_IP)) {
> err = -EEXIST;
> goto err_tlock_pnlock;
> }
next prev parent reply other threads:[~2020-02-04 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 23:24 [PATCH v2 net] l2tp: Allow duplicate session creation with UDP Ridge Kennedy
2020-02-04 10:27 ` James Chapman [this message]
2020-02-04 11:39 ` David Miller
2020-02-04 12:09 ` Guillaume Nault
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=d14d7bba-c29b-7831-f976-5658e9503bf3@katalix.com \
--to=jchapman@katalix.com \
--cc=gnault@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ridge.kennedy@alliedtelesis.co.nz \
--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