netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net] packet: validate address length if non-zero
Date: Sun, 23 Dec 2018 09:15:40 +0200	[thread overview]
Message-ID: <20181223071540.GA22519@splinter> (raw)
In-Reply-To: <20181222215345.128704-1-willemdebruijn.kernel@gmail.com>

On Sat, Dec 22, 2018 at 04:53:45PM -0500, Willem de Bruijn wrote:
> From: Willem de Bruijn <willemb@google.com>
> 
> Validate packet socket address length if a length is given. Zero
> length is equivalent to not setting an address.
> 
> Fixes: 99137b7888f4 ("packet: validate address length")
> Reported-by: Ido Schimmel <idosch@idosch.org>
> Signed-off-by: Willem de Bruijn <willemb@google.com>

Thanks for the quick fix! Issue is gone with this patch.

  parent reply	other threads:[~2018-12-23  7:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-22 21:53 [PATCH net] packet: validate address length if non-zero Willem de Bruijn
2018-12-22 23:13 ` David Miller
2018-12-23 16:30   ` Willem de Bruijn
2018-12-23  7:15 ` Ido Schimmel [this message]
2019-04-23 10:00 ` David Laight
2019-04-23 15:07   ` Willem de Bruijn
2019-04-23 15:53     ` David Laight
2019-04-23 17:04       ` Willem de Bruijn
2019-04-23 17:21         ` Willem de Bruijn
2019-04-23 18:21           ` Willem de Bruijn
2019-04-24 19:14             ` Willem de Bruijn
2019-04-24 19:34               ` Willem de Bruijn
2019-04-25  9:34                 ` David Laight
2019-04-25 13:56                   ` Willem de Bruijn
2019-04-25 14:35                     ` David Laight
2019-04-25 15:42                       ` Willem de Bruijn
2019-04-26 15:10                         ` Willem de Bruijn
2019-04-26 15:14                           ` David Laight
2019-04-26 19:32                             ` Willem de Bruijn

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=20181223071540.GA22519@splinter \
    --to=idosch@idosch.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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;
as well as URLs for NNTP newsgroup(s).