From: Dave Jones <davej@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Chris Metcalf <cmetcalf@tilera.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: deadlock in lru_add_drain ? (3.14rc5)
Date: Mon, 10 Mar 2014 11:50:53 -0400 [thread overview]
Message-ID: <20140310155053.GA26188@redhat.com> (raw)
In-Reply-To: <20140310150106.GD25290@htj.dyndns.org>
On Mon, Mar 10, 2014 at 11:01:06AM -0400, Tejun Heo wrote:
> > On Sat, Mar 8, 2014 at 2:00 PM, Dave Jones <davej@redhat.com> wrote:
> > > I left my fuzzing box running for the weekend, and checked in on it this evening,
> > > to find that none of the child processes were making any progress.
> > > cat'ing /proc/n/stack shows them all stuck in the same place..
> > > Some examples:
>
> Dave, any chance you can post full sysrq-t dump?
It's too big to fit in the ring-buffer, so some of it gets lost before
it hits syslog, but hopefully what made it to disk is enough.
http://codemonkey.org.uk/junk/sysrq-t
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Chris Metcalf <cmetcalf@tilera.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: deadlock in lru_add_drain ? (3.14rc5)
Date: Mon, 10 Mar 2014 11:50:53 -0400 [thread overview]
Message-ID: <20140310155053.GA26188@redhat.com> (raw)
In-Reply-To: <20140310150106.GD25290@htj.dyndns.org>
On Mon, Mar 10, 2014 at 11:01:06AM -0400, Tejun Heo wrote:
> > On Sat, Mar 8, 2014 at 2:00 PM, Dave Jones <davej@redhat.com> wrote:
> > > I left my fuzzing box running for the weekend, and checked in on it this evening,
> > > to find that none of the child processes were making any progress.
> > > cat'ing /proc/n/stack shows them all stuck in the same place..
> > > Some examples:
>
> Dave, any chance you can post full sysrq-t dump?
It's too big to fit in the ring-buffer, so some of it gets lost before
it hits syslog, but hopefully what made it to disk is enough.
http://codemonkey.org.uk/junk/sysrq-t
Dave
next prev parent reply other threads:[~2014-03-10 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 22:00 deadlock in lru_add_drain ? (3.14rc5) Dave Jones
2014-03-08 22:00 ` Dave Jones
2014-03-09 1:18 ` Linus Torvalds
2014-03-09 1:18 ` Linus Torvalds
2014-03-10 15:01 ` Tejun Heo
2014-03-10 15:01 ` Tejun Heo
2014-03-10 15:50 ` Dave Jones [this message]
2014-03-10 15:50 ` Dave Jones
2014-03-10 20:09 ` Tejun Heo
2014-03-10 20:09 ` Tejun Heo
2014-03-10 20:15 ` Dave Jones
2014-03-10 20:15 ` Dave Jones
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=20140310155053.GA26188@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.