linux-kernel - Re: amusing SLUB compaction bug when CC_OPTIMIZE_FOR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 29 Sep 2022 15:01:08 +0200
From:   Vlastimil Babka <vbabka@...e.cz>
To:     David Laight <David.Laight@...LAB.COM>,
        'Hugh Dickins' <hughd@...gle.com>
Cc:     Joel Fernandes <joel@...lfernandes.org>,
        Hyeonggon Yoo <42.hyeyoo@...il.com>,
        Matthew Wilcox <willy@...radead.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: amusing SLUB compaction bug when CC_OPTIMIZE_FOR_SIZE

On 9/29/22 13:53, David Laight wrote:
>> -static void rcu_free_slab(struct rcu_head *h)
>> +/*
>> + * rcu_free_slab() must be __aligned(4) because its address is saved
>> + * in the rcu_head field, which coincides with page->mapping, which
>> + * causes trouble if compaction mistakes it for PAGE_MAPPING_MOVABLE.
>> + */
>> +__aligned(4) static void rcu_free_slab(struct rcu_head *h)
>>  {
>>  	struct slab *slab = container_of(h, struct slab, rcu_head);
>> 
> 
> Isn't that going to cause grief with options that align
> functions on 16/32byte boundaries when adding space for
> 'other stuff'?

How is that done exactly? Also having higher alignment (16/32) is not in
conflict with asking for 4?

> 	David
> 
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>