stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guillaume Morin <guillaume@morinfr.org>
To: Jason Baron <jbaron@akamai.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>,
	Al Viro <viro@zeniv.linux.org.uk>,
	mika.westerberg@linux.intel.com
Subject: Re: Linux 3.14.58
Date: Tue, 22 Dec 2015 17:39:33 +0100	[thread overview]
Message-ID: <20151222163933.GA20860@bender.morinfr.org> (raw)
In-Reply-To: <56797413.3090904@akamai.com>

Jason,

On 22 Dec 11:02, Jason Baron wrote:
> We've noticed livelocks in shrink_dentry_list() very similar to this
> report on stable 3.14.56:
> http://lkml.iu.edu/hypermail/linux/kernel/1405.3/00470.html
> 
> It appears that the patches that introduced this issue came into 3.14.51
> in August with the same set of patches mentioned in the referenced
> report. We unfortunately haven't narrowed down a reproducer, so I can't
> bisect the issue, but 3.14.50 did not appear to have the issue.
> 
> Upstream merge commit - 6f6111e4a73d0f6370eb8be4f8e4523210b6a67d (Pull
> vfs dcache livelock fix from Al Viro) brought in a series to address
> this issue. So that may be needed here as well...

FWIW I noticed the same thing.  The commits listed in
http://www.spinics.net/lists/stable/msg111553.html fixed the problem for me.

I assume Greg will pick them up soon...

-- 
Guillaume Morin <guillaume@morinfr.org>

  reply	other threads:[~2015-12-22 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 20:15 Linux 3.14.58 Greg KH
2015-12-09 20:15 ` Greg KH
2015-12-22 16:02 ` Jason Baron
2015-12-22 16:39   ` Guillaume Morin [this message]
2015-12-22 19:30     ` Jason Baron

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=20151222163933.GA20860@bender.morinfr.org \
    --to=guillaume@morinfr.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbaron@akamai.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=mika.westerberg@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).