From: David Miller <davem@davemloft.net>
To: g.nault@alphalink.fr
Cc: netdev@vger.kernel.org, jchapman@katalix.com
Subject: Re: [PATCH net 0/4] l2tp: pppol2tp_connect() fixes
Date: Thu, 14 Jun 2018 17:10:32 -0700 (PDT) [thread overview]
Message-ID: <20180614.171032.1730500975104561705.davem@davemloft.net> (raw)
In-Reply-To: <cover.1528887257.git.g.nault@alphalink.fr>
From: Guillaume Nault <g.nault@alphalink.fr>
Date: Wed, 13 Jun 2018 15:09:16 +0200
> This series fixes a few remaining issues with pppol2tp_connect().
>
> It doesn't try to prevent invalid configurations that have no effect on
> kernel's reliability. That would be work for a future patch set.
>
> Patch 2 is the most important as it avoids an invalid pointer
> dereference crashing the kernel. It depends on patch 1 for correctly
> identifying L2TP session types.
>
> Patches 3 and 4 avoid creating stale tunnels and sessions.
Series applied, thank you.
prev parent reply other threads:[~2018-06-15 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 13:09 [PATCH net 0/4] l2tp: pppol2tp_connect() fixes Guillaume Nault
2018-06-13 13:09 ` [PATCH net 1/4] l2tp: fix pseudo-wire type for sessions created by pppol2tp_connect() Guillaume Nault
2018-06-13 13:09 ` [PATCH net 2/4] l2tp: only accept PPP sessions in pppol2tp_connect() Guillaume Nault
2018-06-13 13:09 ` [PATCH net 3/4] l2tp: prevent pppol2tp_connect() from creating kernel sockets Guillaume Nault
2018-06-13 13:09 ` [PATCH net 4/4] l2tp: clean up stale tunnel or session in pppol2tp_connect's error path Guillaume Nault
2018-06-15 0:10 ` David Miller [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=20180614.171032.1730500975104561705.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=g.nault@alphalink.fr \
--cc=jchapman@katalix.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).