From: David Miller <davem@davemloft.net>
To: kraigatgoog@gmail.com
Cc: netdev@vger.kernel.org, marc.c.dionne@gmail.com
Subject: Re: [PATCH net] soreuseport: fix NULL ptr dereference SO_REUSEPORT after bind
Date: Tue, 19 Jan 2016 14:44:52 -0500 (EST) [thread overview]
Message-ID: <20160119.144452.555969872261254175.davem@davemloft.net> (raw)
In-Reply-To: <1453231628-18603-1-git-send-email-kraigatgoog@gmail.com>
From: Craig Gallek <kraigatgoog@gmail.com>
Date: Tue, 19 Jan 2016 14:27:08 -0500
> From: Craig Gallek <kraig@google.com>
>
> Marc Dionne discovered a NULL pointer dereference when setting
> SO_REUSEPORT on a socket after it is bound.
> This patch removes the assumption that at least one socket in the
> reuseport group is bound with the SO_REUSEPORT option before other
> bind calls occur.
>
> Fixes: e32ea7e74727 ("soreuseport: fast reuseport UDP socket selection")
> Reported-by: Marc Dionne <marc.c.dionne@gmail.com>
> Signed-off-by: Craig Gallek <kraig@google.com>
Applied, thanks everyone.
prev parent reply other threads:[~2016-01-19 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 19:27 [PATCH net] soreuseport: fix NULL ptr dereference SO_REUSEPORT after bind Craig Gallek
2016-01-19 19:43 ` Marc Dionne
2016-01-19 19:44 ` 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=20160119.144452.555969872261254175.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kraigatgoog@gmail.com \
--cc=marc.c.dionne@gmail.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).