From: Vlastimil Babka <vbabka@suse.cz>
To: lkp@lists.01.org
Subject: Re: [mm/sl[au]b] 3c4cafa313: canonical_address#:#[##]
Date: Fri, 09 Sep 2022 15:44:19 +0200 [thread overview]
Message-ID: <3d178109-5981-f4ee-8fe5-4f1d0c557ed2@suse.cz> (raw)
In-Reply-To: <Yxsd625lvTS6IWc+@hyeyoo>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
On 9/9/22 13:05, Hyeonggon Yoo wrote:
>> ----8<----
>> From d6f9fbb33b908eb8162cc1f6ce7f7c970d0f285f Mon Sep 17 00:00:00 2001
>> From: Vlastimil Babka <vbabka@suse.cz>
>> Date: Fri, 9 Sep 2022 12:03:10 +0200
>> Subject: [PATCH 2/3] mm/migrate: make isolate_movable_page() skip slab pages
>>
>> In the next commit we want to rearrange struct slab fields to allow a
>> larger rcu_head. Afterwards, the page->mapping field will overlap
>> with SLUB's "struct list_head slab_list", where the value of prev
>> pointer can become LIST_POISON2, which is 0x122 + POISON_POINTER_DELTA.
>> Unfortunately the bit 1 being set can confuse PageMovable() to be a
>> false positive and cause a GPF as reported by lkp [1].
>>
>> To fix this, make isolate_movable_page() skip pages with the PageSlab
>> flag set. This is a bit tricky as we need to add memory barriers to SLAB
>> and SLUB's page allocation and freeing, and their counterparts to
>> isolate_movable_page().
>
> Hello, I just took a quick grasp,
> Is this approach okay with folio_test_anon()?
Not if used on a completely random page as compaction scanners can, but
relies on those being first tested for PageLRU or coming from a page table
lookup etc.
Not ideal huh. Well I could improve also by switching 'next' and 'slabs'
field and relying on the fact that the value of LIST_POISON2 doesn't include
0x1, just 0x2.
next prev parent reply other threads:[~2022-09-09 13:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220906074548.GA72649@inn2.lkp.intel.com>
2022-09-06 7:51 ` [mm/sl[au]b] 3c4cafa313: canonical_address#:#[##] kernel test robot
2022-09-06 14:56 ` Hyeonggon Yoo
2022-09-06 15:11 ` Vlastimil Babka
2022-09-09 10:21 ` Vlastimil Babka
2022-09-09 11:05 ` Hyeonggon Yoo
2022-09-09 13:44 ` Vlastimil Babka [this message]
2022-09-09 14:32 ` Hyeonggon Yoo
2022-09-09 21:16 ` Vlastimil Babka
2022-09-10 3:34 ` Hyeonggon Yoo
2022-09-14 6:33 ` Hyeonggon Yoo
2022-09-14 7:42 ` Matthew Wilcox
2022-09-16 17:06 ` Vlastimil Babka
2022-09-06 15:09 ` Hyeonggon Yoo
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=3d178109-5981-f4ee-8fe5-4f1d0c557ed2@suse.cz \
--to=vbabka@suse.cz \
--cc=lkp@lists.01.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).