From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Peter Xu <peterx@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nick Bowler <nbowler@draconx.ca>,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH] mm/migrate: Fix wrongly apply write bit after mkdirty on sparc64
Date: Thu, 16 Feb 2023 17:59:16 +0100 [thread overview]
Message-ID: <611c1202-1978-8886-eec3-929933ee75cd@leemhuis.info> (raw)
In-Reply-To: <20230216153059.256739-1-peterx@redhat.com>
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].
Thx for handling this.
> [...]
>
> Note: this is based on mm-unstable, because the breakage was since 6.1 and
> we're at a very late stage of 6.2 (-rc8), so I assume for this specific
> case we should target this at 6.3.
>
> [1] https://lore.kernel.org/all/20221021160603.GA23307@u164.east.ru/
> [2] https://lore.kernel.org/all/20221212130213.136267-1-david@redhat.com/
>
> Cc: regressions@leemhuis.info
Not that it matters much, but feel free to use this instead:
CC: regressions@lists.linux.dev
Then things don't depend on me (in case I ever get help with my cat
herding job). And it also make it even more obvious that this patch
fixes a regression to anyone who handles it downstream.
> Fixes: 2e3468778dbe ("mm: remember young/dirty bit for page migrations")
That's a commit from 6.1, hence this should likely have:
Cc: stable@vger.kernel.org # 6.1.y
[no, a fixes tag alone does not suffice, see docs]
> Link: https://lore.kernel.org/all/CADyTPExpEqaJiMGoV+Z6xVgL50ZoMJg49B10LcZ=8eg19u34BA@mail.gmail.com/
> Reported-by: Nick Bowler <nbowler@draconx.ca>
> [...]
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
next prev parent reply other threads:[~2023-02-16 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 15:30 Peter Xu
2023-02-16 15:37 ` David Hildenbrand
2023-02-16 21:54 ` Andrew Morton
2023-02-16 16:59 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-02-16 19:18 ` Peter Xu
2023-02-16 17:04 ` David Hildenbrand
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=611c1202-1978-8886-eec3-929933ee75cd@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nbowler@draconx.ca \
--cc=peterx@redhat.com \
--cc=regressions@lists.linux.dev \
/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