All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Nault <g.nault@alphalink.fr>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	James Chapman <jchapman@katalix.com>
Subject: Re: [PATCH net] l2tp: do not accept arbitrary sockets
Date: Tue, 6 Mar 2018 19:45:46 +0100	[thread overview]
Message-ID: <20180306184546.GA1351@alphalink.fr> (raw)
In-Reply-To: <1520351693.109662.17.camel@gmail.com>

On Tue, Mar 06, 2018 at 07:54:53AM -0800, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
> 
> syzkaller found an issue caused by lack of sufficient checks
> in l2tp_tunnel_create()
> 
> RAW sockets can not be considered as UDP ones for instance.
> 
Indeed, missing checks have been the source of so many reports.

Acked-by: Guillaume Nault <g.nault@alphalink.fr>

  reply	other threads:[~2018-03-06 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 15:54 [PATCH net] l2tp: do not accept arbitrary sockets Eric Dumazet
2018-03-06 18:45 ` Guillaume Nault [this message]
2018-03-06 20:26 ` James Chapman
2018-03-07 18:36 ` David Miller
2018-03-07 18:55 ` 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=20180306184546.GA1351@alphalink.fr \
    --to=g.nault@alphalink.fr \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --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 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.