From: Andrew Morton <akpm@linux-foundation.org>
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Cc: linux-mm@kvack.org, Huang Ying <ying.huang@intel.com>,
Zi Yan <ziy@nvidia.com>, Yang Shi <shy828301@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Oscar Salvador <osalvador@suse.de>,
Matthew Wilcox <willy@infradead.org>,
Bharata B Rao <bharata@amd.com>,
Alistair Popple <apopple@nvidia.com>,
haoxin <xhao@linux.alibaba.com>, Minchan Kim <minchan@kernel.org>
Subject: Re: [BISECTED] first bad commit is c203c6d5b3f0597 ("migrate_pages: batch _unmap and _move")
Date: Tue, 31 Jan 2023 14:45:38 -0800 [thread overview]
Message-ID: <20230131144538.1a9f84b6781bed0c251d54f7@linux-foundation.org> (raw)
In-Reply-To: <Y9lRezBFOtLuQF0O@hyeyoo>
On Wed, 1 Feb 2023 02:35:55 +0900 Hyeonggon Yoo <42.hyeyoo@gmail.com> wrote:
> On Wed, Feb 01, 2023 at 01:09:10AM +0900, Hyeonggon Yoo wrote:
> > I've observed random list_del corruption on mm-unstable,
> > where HEAD is commit d69862e693c069f4
> > ("mm/migrate: convert putback_movable_pages() to use folios").
> >
> > The issue can be easily reproduced by stressing MM multiple times:
> > stress-ng --bigheap 0 --timeout 300
> >
> > The compiler is gcc 12.2.1 and config, dmesg are included as attachment.
> > I will try to bisect but can't promise quick resolution :)
>
>
> The first bad commits appears to be:
> c203c6d5b3f0597 ("migrate_pages: batch _unmap and _move")
>
> the first bad commit _probably_ be earlier, but this is quite
> easy to reproduce so at this point I think above is the real bad commit.
Thanks. I'll disable this series for now, so it won't appear in linux-next.
next prev parent reply other threads:[~2023-01-31 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y9k9Jl9wIaUFZS30@hyeyoo>
2023-01-31 17:35 ` Hyeonggon Yoo
2023-01-31 22:45 ` Andrew Morton [this message]
2023-02-01 23:28 ` Huang, Ying
2023-02-02 23:17 ` Huang, Ying
2023-02-03 14:17 ` Hyeonggon Yoo
2023-02-03 15:02 ` Huang, Ying
2023-02-05 14:38 ` Hyeonggon Yoo
2023-02-06 6:25 ` Huang, Ying
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=20230131144538.1a9f84b6781bed0c251d54f7@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=42.hyeyoo@gmail.com \
--cc=apopple@nvidia.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=bharata@amd.com \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=willy@infradead.org \
--cc=xhao@linux.alibaba.com \
--cc=ying.huang@intel.com \
--cc=ziy@nvidia.com \
/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