[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20120625.160603.2046472954169103270.davem@davemloft.net>
Date: Mon, 25 Jun 2012 16:06:03 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: ncardwell@...gle.com
Cc: eric.dumazet@...il.com, netdev@...r.kernel.org,
edumazet@...gle.com, therbert@...gle.com
Subject: Re: [PATCH 5/5] tcp: plug dst leak in tcp_v6_conn_request()
From: Neal Cardwell <ncardwell@...gle.com>
Date: Sun, 24 Jun 2012 13:12:33 -0400
> Yes, the patches in this series were generated as patches against the
> "net" tree (sorry for not indicating that).
>
> The dst leak on the v6 sysctl_tw_recycle code path (patches 2-5) seems
> like a pretty low priority, so I think we could simplify your plan
> even a little further... How about this as a plan: we could apply the
> first patch in the series (tcp: heed result of
> security_inet_conn_request() in tcp_v6_conn_request()) to the net tree
> now, and skip patches 2-5 for now. Once your pending synack work is in
> net-next, I can respin patches 2-5 for net-next. How does that sound?
I've applied the first patch to 'net' and you can simply respin
your patches against net-next right now since I rejected Eric's
SYN-ACK patches.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists