From: Andrew Morton <akpm@linux-foundation.org>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Brian Foster <bfoster@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>,
Vitaly Wool <vitaly.wool@konsulko.com>,
Miaohe Lin <linmiaohe@huawei.com>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: Panic/lockup in z3fold_zpool_free
Date: Mon, 17 Oct 2022 15:24:23 -0700 [thread overview]
Message-ID: <20221017152423.37a126325b4330e71cf8f869@linux-foundation.org> (raw)
In-Reply-To: <4433520.LvFx2qVVIh@natalenko.name>
On Mon, 17 Oct 2022 18:34:50 +0200 Oleksandr Natalenko <oleksandr@natalenko.name> wrote:
> > > > I'll give it a try. The only problem is that for me the issue is not reproducible at will, it can take 1 day, or it can take 2 weeks before the panic is hit.
> > > >
> > > > > [1] https://lore.kernel.org/linux-mm/YxDyZLfBdFHK1Y1P@bfoster/
> > > > > [2] https://lore.kernel.org/linux-mm/20220906190602.1626037-1-bfoster@redhat.com/
> > >
> > > So far, I haven't reproduced this issue with your patch. I haven't run the machine sufficiently long, just under a week, so this is rather to let you know that I haven't abandoned testing.
> > >
> >
> > Thanks for the update. Is this still going well, or reached a point
> > where you typically see the problem? I can still reproduce the original
> > problem so I may have to ping the patch again..
>
> So far, no issue observed with your patch.
Thanks.
It's actually unclear (to me) why Matthew's b653db77350c73 ("mm: Clear
page->private when splitting or migrating a page") was considered
necessary. What problem did it solve?
https://lore.kernel.org/linux-mm/20220906190602.1626037-1-bfoster@redhat.com/
is a partial undoing of that change, but should we simply revert
b653db77350c73?
prev parent reply other threads:[~2022-10-17 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 6:53 Oleksandr Natalenko
2022-09-22 11:37 ` Brian Foster
2022-09-23 8:33 ` Oleksandr Natalenko
2022-10-06 15:52 ` Oleksandr Natalenko
2022-10-17 16:13 ` Brian Foster
2022-10-17 16:34 ` Oleksandr Natalenko
2022-10-17 22:24 ` Andrew Morton [this message]
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=20221017152423.37a126325b4330e71cf8f869@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bfoster@redhat.com \
--cc=ddstreet@ieee.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleksandr@natalenko.name \
--cc=sjenning@redhat.com \
--cc=vitaly.wool@konsulko.com \
--cc=willy@infradead.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