From: Johannes Weiner <hannes@cmpxchg.org>
To: Hugh Dickins <hughd@google.com>
Cc: Dave Jones <davej@codemonkey.org.uk>, Jan Kara <jack@suse.cz>,
linux-mm@kvack.org
Subject: Re: 4.10-rc2 list_lru_isolate list corruption
Date: Sat, 7 Jan 2017 21:02:52 -0500 [thread overview]
Message-ID: <20170108020252.GB16312@cmpxchg.org> (raw)
In-Reply-To: <alpine.LSU.2.11.1701071626290.1664@eggly.anvils>
On Sat, Jan 07, 2017 at 04:37:43PM -0800, Hugh Dickins wrote:
> On Sat, 7 Jan 2017, Dave Jones wrote:
> > On Fri, Jan 06, 2017 at 08:19:31PM -0500, Johannes Weiner wrote:
> >
> > > Argh, __radix_tree_delete_node() makes the flawed assumption that only
> > > the immediate branch it's mucking with can collapse. But this warning
> > > points out that a sibling branch can collapse too, including its leaf.
> > >
> > > Can you try if this patch fixes the problem?
> >
> > 18 hours and still running.. I think we can call it good.
>
> I'm inclined to agree, though I haven't had it running long enough
> (on a load like when it hit me a few times before) to be sure yet myself.
> I'd rather see the proposed fix go in than wait longer for me:
> I've certainly seen nothing bad from it yet.
Thank you both!
--
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:[~2017-01-08 2:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170106052056.jihy5denyxsnfuo5@codemonkey.org.uk>
2017-01-06 16:59 ` Johannes Weiner
2017-01-06 19:58 ` Dave Jones
2017-01-07 1:19 ` Johannes Weiner
2017-01-08 0:07 ` Dave Jones
2017-01-08 0:37 ` Hugh Dickins
2017-01-08 2:02 ` Johannes Weiner [this message]
2017-01-08 20:30 ` Hugh Dickins
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=20170108020252.GB16312@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=davej@codemonkey.org.uk \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--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