netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Nault <g.nault@alphalink.fr>
To: Kevin Easton <kevin@guarana.org>
Cc: netdev@vger.kernel.org, Michal Ostrowski <mostrows@earthlink.net>
Subject: Re: [PATCH net] pppoe: check sockaddr length in pppoe_connect()
Date: Fri, 27 Apr 2018 18:27:36 +0200	[thread overview]
Message-ID: <20180427162736.GI1440@alphalink.fr> (raw)
In-Reply-To: <20180427162424.GH1440@alphalink.fr>

On Fri, Apr 27, 2018 at 06:24:24PM +0200, Guillaume Nault wrote:
> exact consequences. That being said if you consider the risk is
> sufficiently low, you can always submit the patch to net-next.
Humm, forget it. I didn't see David's reply before answering.

  reply	other threads:[~2018-04-27 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 14:38 [PATCH net] pppoe: check sockaddr length in pppoe_connect() Guillaume Nault
2018-04-24  1:12 ` David Miller
2018-04-27 12:23 ` Kevin Easton
2018-04-27 15:39   ` Guillaume Nault
2018-04-27 15:51     ` Kevin Easton
2018-04-27 16:24       ` Guillaume Nault
2018-04-27 16:27         ` Guillaume Nault [this message]
2018-04-27 16:01     ` David Miller

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=20180427162736.GI1440@alphalink.fr \
    --to=g.nault@alphalink.fr \
    --cc=kevin@guarana.org \
    --cc=mostrows@earthlink.net \
    --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).