From: Yin Fengwei <fengwei.yin@intel.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: <aaron.lu@intel.com>, <tony.luck@intel.com>,
<qiuxu.zhuo@intel.com>, <linux-mm@kvack.org>,
HORIGUCHI NAOYA <naoya.horiguchi@nec.com>,
"Matthew Wilcox" <willy@infradead.org>,
Yang Shi <shy828301@gmail.com>
Subject: Re: [PATCH v3] mm: release private data before split THP
Date: Thu, 11 Aug 2022 15:27:53 +0800 [thread overview]
Message-ID: <89527e99-7c58-beb6-7b48-2bb96322b5b5@intel.com> (raw)
In-Reply-To: <eea76fec-eb14-6e40-f8f3-1933868bc9f5@huawei.com>
On 2022/8/11 09:54, Miaohe Lin wrote:
> On 2022/8/10 14:49, Yin Fengwei wrote:
>> If there is private data attached to THP, the refcount of
>> THP will be increased and block the THP split. Release
>> private data attached to THP before split it to increase
>> the chance of splitting THP successfully.
>>
>> There was a memory failure issue hit during HW error
>> injection testing with 5.18 kernel + xfs as rootfs. Test
>> got killed and system reboot was required to re-run the
>> test.
>>
>> The issue was tracked down to THP split failure caused the
>> memory failure not being handled. The page dump showed:
>>
>> [ 1785.433075] page:0000000025f9530b refcount:18 mapcount:0 mapping:000000008162eea7 index:0xa10 pfn:0x2f0200
>> [ 1785.443954] head:0000000025f9530b order:4 compound_mapcount:0 compound_pincount:0
>> [ 1785.452408] memcg:ff4247f2d28e9000
>> [ 1785.456304] aops:xfs_address_space_operations ino:8555182 dentry name:"baseos-filenames.solvx"
>> [ 1785.466612] flags: 0x1000000000012036(referenced|uptodate|lru|active|private|head|node=0|zone=2)
>> [ 1785.476514] raw: 1000000000012036 ffb9460f8bc07c08 ffb9460f8bc08408 ff4247f22e6299f8
>> [ 1785.485268] raw: 0000000000000a10 ff4247f194ade900 00000012ffffffff ff4247f2d28e9000
>>
>> It was like the error was injected to a large folio for xfs
>> with private data attached.
>>
>> With private data released before split THP, the test case
>> could be run successfully many times without reboot system.
>>
>> Co-developed-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
>> Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
>> Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
>> Suggested-by: Matthew Wilcox <willy@infradead.org>
>
> Thanks for your work.
>
> Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
Thanks for your reviewing.
Regards
Yin, Fengwei
>
next prev parent reply other threads:[~2022-08-11 7:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 6:49 Yin Fengwei
2022-08-10 17:09 ` Yang Shi
2022-08-11 7:26 ` Yin Fengwei
2022-08-11 1:54 ` Miaohe Lin
2022-08-11 7:27 ` Yin Fengwei [this message]
2022-08-11 8:18 ` Lu, Aaron
2022-08-19 5:04 ` Yin, Fengwei
2022-08-20 0:45 ` Andrew Morton
2022-08-20 1:48 ` Yin, Fengwei
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=89527e99-7c58-beb6-7b48-2bb96322b5b5@intel.com \
--to=fengwei.yin@intel.com \
--cc=aaron.lu@intel.com \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=qiuxu.zhuo@intel.com \
--cc=shy828301@gmail.com \
--cc=tony.luck@intel.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