From: David Miller <davem@davemloft.net>
To: kraigatgoog@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] Fixes for SO_REUSEPORT and mixed v4/v6 sockets
Date: Thu, 14 Apr 2016 21:18:02 -0400 (EDT) [thread overview]
Message-ID: <20160414.211802.2280436220533771683.davem@davemloft.net> (raw)
In-Reply-To: <1460481086-12982-1-git-send-email-kraigatgoog@gmail.com>
From: Craig Gallek <kraigatgoog@gmail.com>
Date: Tue, 12 Apr 2016 13:11:24 -0400
> From: Craig Gallek <kraig@google.com>
>
> Recent changes to the datastructures associated with SO_REUSEPORT broke
> an existing behavior when equivalent SO_REUSEPORT sockets are created
> using both AF_INET and AF_INET6. This patch series restores the previous
> behavior and includes a test to validate it.
>
> This series should be a trivial merge to stable kernels (if deemed
> necessary), but will have conflicts in net-next. The following patches
> recently replaced the use of hlist_nulls with hlists for UDP and TCP
> socket lists:
> ca065d0cf80f ("udp: no longer use SLAB_DESTROY_BY_RCU")
> 3b24d854cb35 ("tcp/dccp: do not touch listener sk_refcnt under synflood")
>
> If this series is accepted, I will send an RFC for the net-next change
> to assist with the merge.
Applied and patch #1 queued up for -stable.
prev parent reply other threads:[~2016-04-15 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 17:11 [PATCH net 0/2] Fixes for SO_REUSEPORT and mixed v4/v6 sockets Craig Gallek
2016-04-12 17:11 ` [PATCH net 1/2] soreuseport: fix ordering for " Craig Gallek
2016-04-12 17:11 ` [PATCH net 2/2] soreuseport: test " Craig Gallek
2016-04-15 1:18 ` 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=20160414.211802.2280436220533771683.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kraigatgoog@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).