From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Naoya Horiguchi <naoya.horiguchi@linux.dev>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Matthew Wilcox <willy@infradead.org>,
Miaohe Lin <linmiaohe@huawei.com>,
Christoph Hellwig <hch@infradead.org>,
John Hubbard <jhubbard@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
William Kucharski <william.kucharski@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mm/hwpoison: use pr_err() instead of dump_page() in get_any_page()
Date: Wed, 27 Apr 2022 22:37:52 +0000 [thread overview]
Message-ID: <20220427223751.GA3935899@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <20220427121517.a9515a17697424604f8fbcf0@linux-foundation.org>
On Wed, Apr 27, 2022 at 12:15:17PM -0700, Andrew Morton wrote:
> On Wed, 27 Apr 2022 14:32:20 +0900 Naoya Horiguchi <naoya.horiguchi@linux.dev> wrote:
>
> > From: Naoya Horiguchi <naoya.horiguchi@nec.com>
> >
> > The following VM_BUG_ON_FOLIO() is triggered when memory error event
> > happens on the (thp/folio) pages which are about to be freed:
> >
> > ...
> >
> > Fixes: 74e8ee4708a8 ("mm: Turn head_compound_mapcount() into folio_entire_mapcount()")
>
> I added cc:stable to this, OK?
Yes, that's fine. 74e8ee4708a8 is new, and only v5.17.z is the target tree.
Thank you.
- Naoya Horiguchi
next prev parent reply other threads:[~2022-04-27 22:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 5:32 [PATCH v2] mm/hwpoison: use pr_err() instead of dump_page() in get_any_page() Naoya Horiguchi
2022-04-27 19:15 ` Andrew Morton
2022-04-27 22:37 ` HORIGUCHI NAOYA(堀口 直也) [this message]
2022-04-27 23:48 ` John Hubbard
2022-04-28 1:46 ` Miaohe Lin
2022-04-28 17:25 ` Yang Shi
2022-05-09 7:14 ` ##freemail## " HORIGUCHI NAOYA(堀口 直也)
2022-05-10 0:16 ` Yang Shi
2022-05-10 2:28 ` Matthew Wilcox
2022-05-10 10:31 ` HORIGUCHI NAOYA(堀口 直也)
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=20220427223751.GA3935899@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@linux.dev \
--cc=william.kucharski@oracle.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;
as well as URLs for NNTP newsgroup(s).