From: Greg KH <greg@kroah.com>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: stable@vger.kernel.org, Michal Kubecek <mkubecek@suse.cz>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 3.10.y 0/2] ipv6: avoid soft lockups in fib6_run_gc()
Date: Mon, 29 Jun 2015 17:28:51 -0700 [thread overview]
Message-ID: <20150630002851.GE6430@kroah.com> (raw)
In-Reply-To: <20150610103926.3791.22866.stgit@buzz>
On Wed, Jun 10, 2015 at 01:40:42PM +0300, Konstantin Khlebnikov wrote:
> Two patches from 3.11 which are missing in 3.10.y
>
> I've just seen livelock in 3.10.69+ where all cpus are stuck in fib6_run_gc()
As David doesn't queue up network patches for 3.10-stable anymore (and I
don't blame him), I've added these myself to the tree.
thanks,
greg k-h
next prev parent reply other threads:[~2015-06-30 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 10:40 [PATCH 3.10.y 0/2] ipv6: avoid soft lockups in fib6_run_gc() Konstantin Khlebnikov
2015-06-10 10:40 ` [PATCH 3.10.y 1/2] ipv6: prevent fib6_run_gc() contention Konstantin Khlebnikov
2015-06-10 10:40 ` [PATCH 3.10.y 2/2] ipv6: update ip6_rt_last_gc every time GC is run Konstantin Khlebnikov
2015-06-30 0:28 ` Greg KH [this message]
2015-10-08 22:04 ` [PATCH 3.10.y 0/2] ipv6: avoid soft lockups in fib6_run_gc() Ben Hutchings
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=20150630002851.GE6430@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=khlebnikov@yandex-team.ru \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=stable@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).