From: David Miller <davem@davemloft.net>
To: ben@decadent.org.uk
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, joseph.salisbury@canonical.com,
steffen.klassert@secunet.com, edumazet@google.com
Subject: Re: [PATCH][v3.2.y] inetpeer: Invalidate the inetpeer tree along with the routing cache
Date: Tue, 10 Sep 2013 14:53:34 -0400 (EDT) [thread overview]
Message-ID: <20130910.145334.1669114772684195996.davem@davemloft.net> (raw)
In-Reply-To: <1377986658.21578.5.camel@deadeye.wl.decadent.org.uk>
From: Ben Hutchings <ben@decadent.org.uk>
Date: Sat, 31 Aug 2013 23:04:18 +0100
> On Tue, 2013-08-20 at 13:34 -0400, Joseph Salisbury wrote:
>> Hello,
>>
>> Please consider including mainline commit 5faa5df in the next v3.2.y
>> release. It was included in the mainline tree as of v3.3-rc7. It has
>> been tested and confirmed to resolve
>> http://bugs.launchpad.net/bugs/1205741 .
>>
>>
>> commit 5faa5df1fa2024bd750089ff21dcc4191798263d
>> Author: Steffen Klassert <steffen.klassert@secunet.com>
>> Date: Tue Mar 6 21:20:26 2012 +0000
>>
>> inetpeer: Invalidate the inetpeer tree along with the routing cache
>>
>>
>> Also note that commit 5faa5df introduced a race condition that is fixed
>> by mainline commit 55432d2, so that commit would also be required:
>>
>> commit 55432d2b543a4b6dfae54f5c432a566877a85d90
>> Author: Eric Dumazet <edumazet@google.com>
>> Date: Tue Jun 5 03:00:18 2012 +0000
>>
>> inetpeer: fix a race in inetpeer_gc_worker()
>
> David, could you ack/nak these for 3.2 (maybe 3.0 as well?).
I'm queueing these two patches up for 3.2 only, the
inetpeer/metrics-cache situation in 3.0 has so many deeper problems
than can be reasonably dealt with using backports. Just look at the
layout differences of struct inetpeer between 3.0 and 3.2, and the
reasons for that, for the tip of the iceberg.
next prev parent reply other threads:[~2013-09-10 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 17:34 [PATCH][v3.2.y] inetpeer: Invalidate the inetpeer tree along with the routing cache Joseph Salisbury
2013-08-31 22:04 ` Ben Hutchings
2013-09-10 18:53 ` David Miller [this message]
2013-09-10 18:49 ` 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=20130910.145334.1669114772684195996.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ben@decadent.org.uk \
--cc=edumazet@google.com \
--cc=joseph.salisbury@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.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).