From: Dave Jones <davej@codemonkey.org.uk>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: page_cache_tree_insert WARN_ON hit on 4.8+
Date: Tue, 4 Oct 2016 13:46:45 -0400 [thread overview]
Message-ID: <20161004174645.urwwmvgibabaokjn@codemonkey.org.uk> (raw)
In-Reply-To: <20161004173425.GA1223@cmpxchg.org>
On Tue, Oct 04, 2016 at 07:34:25PM +0200, Johannes Weiner wrote:
> Hi Dave,
>
> On Tue, Oct 04, 2016 at 01:09:55PM -0400, Dave Jones wrote:
> > Hit this during a trinity run.
> > Kernel built from v4.8-1558-g21f54ddae449
> >
> > WARNING: CPU: 0 PID: 5670 at ./include/linux/swap.h:276 page_cache_tree_insert+0x198/0x1b0
>
> Thanks for the report.
>
> I've been trying to reproduce this too after Linus got hit by it. Is
> there any way to trace back the steps what trinity was doing exactly?
That run didn't have logging enabled, so not sure..
> What kind of file(system) this was operating on,
btrfs
> file size, what the /proc/vmstat delta before the operation until the trigger looks like?
No idea.
Let me play with some options, see if I can narrow it down.
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>
next prev parent reply other threads:[~2016-10-04 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 17:09 page_cache_tree_insert WARN_ON hit on 4.8+ Dave Jones
2016-10-04 17:34 ` Johannes Weiner
2016-10-04 17:46 ` Dave Jones [this message]
2016-10-06 13:41 ` Johannes Weiner
2016-10-06 14:02 ` 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=20161004174645.urwwmvgibabaokjn@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).