Date:   Thu, 16 Feb 2023 13:54:08 -0800
From:   Andrew Morton <akpm@linux-foundation.org>
To:     David Hildenbrand <david@redhat.com>
Cc:     Peter Xu <peterx@redhat.com>, linux-kernel@vger.kernel.org,
        linux-mm@kvack.org, regressions@leemhuis.info,
        Nick Bowler <nbowler@draconx.ca>
Subject: Re: [PATCH] mm/migrate: Fix wrongly apply write bit after mkdirty
 on sparc64
Message-Id: <20230216135408.18b8ccc91d1677d5d762feab@linux-foundation.org>
In-Reply-To: <7c218446-cd3a-da90-0c18-83579bef34ca@redhat.com>
References: <20230216153059.256739-1-peterx@redhat.com>
        <7c218446-cd3a-da90-0c18-83579bef34ca@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Thu, 16 Feb 2023 16:37:19 +0100 David Hildenbrand <david@redhat.com> wrote:

> On 16.02.23 16:30, Peter Xu wrote:
> > Nick Bowler reported another sparc64 breakage after the young/dirty
> > persistent work for page migration (per "Link:" below).  That's after a
> > similar report [2].
> > 
> > It turns out page migration was overlooked, and it wasn't failing before
> > because page migration was not enabled in the initial report test environment.
> > 
> > David proposed another way [2] to fix this from sparc64 side, but that
> > patch didn't land somehow. 
> 
> I pinged another time and asked Andrew to pick it up eventually.
> 

urgh, sorry, I'd have filtered that out as a sparc patch.