From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <owner-linux-mm@kvack.org>
Date: Thu, 5 Jul 2018 14:43:52 -0400
From: Johannes Weiner <hannes@cmpxchg.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Peter Geis <pgwipeout@gmail.com>, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [BUG] Swap xarray workingset eviction warning.
Message-ID: <20180705184352.GA16681@cmpxchg.org>
References: <2920a634-0646-1500-7c4d-62c56932fe49@gmail.com>
 <20180702025059.GA9865@bombadil.infradead.org>
 <20180705170019.GA14929@cmpxchg.org>
 <20180705175352.GA21635@bombadil.infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180705175352.GA21635@bombadil.infradead.org>
Sender: owner-linux-mm@kvack.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Thu, Jul 05, 2018 at 10:53:52AM -0700, Matthew Wilcox wrote:
> On Thu, Jul 05, 2018 at 01:00:19PM -0400, Johannes Weiner wrote:
> > This could be a matter of uptime, but the warning triggers on a thing
> > that is supposed to happen everywhere eventually. Let's fix it.
> 
> Ahh!  Thank you!
> 
> > xa_mk_value() doesn't understand that we're okay with it chopping off
> > our upper-most bit. We shouldn't make this an API behavior, either, so
> > let's fix the workingset code to always clear those bits before hand.
> 
> Makes sense.  I'll just fold this in, if that's OK with you?

Sounds good to me, thanks.