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:   Tue, 5 Sep 2023 13:28:57 +0100
From:   Mel Gorman <mgorman@...hsingularity.net>
To:     Vlastimil Babka <vbabka@...e.cz>
Cc:     Lecopzer Chen <lecopzer.chen@...iatek.com>,
        akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org, nsaenzju@...hat.com, yj.chiang@...iatek.com,
        Mark-pk Tsai <mark-pk.tsai@...iatek.com>,
        Joe Liu <joe.liu@...iatek.com>
Subject: Re: [PATCH] mm: page_alloc: fix cma pageblock was stolen in rmqueue
 fallback

On Tue, Sep 05, 2023 at 11:37:30AM +0200, Vlastimil Babka wrote:
> On 9/5/23 11:09, Mel Gorman wrote:
> > On Wed, Aug 30, 2023 at 07:13:33PM +0800, Lecopzer Chen wrote:
> >> commit 4b23a68f9536 ("mm/page_alloc: protect PCP lists with a
> >> spinlock") fallback freeing page to free_one_page() if pcp trylock
> >> failed. This make MIGRATE_CMA be able to fallback and be stolen
> >> whole pageblock by MIGRATE_UNMOVABLE in the page allocation.
> >> 
> >> PCP free is fine because free_pcppages_bulk() will always get
> >> migratetype again before freeing the page, thus this only happen when
> >> someone tried to put CMA page in to other MIGRATE_TYPE's freelist.
> >> 
> >> Fixes: 4b23a68f9536 ("mm/page_alloc: protect PCP lists with a spinlock")
> >> Reported-by: Joe Liu <joe.liu@...iatek.com>
> >> Signed-off-by: Lecopzer Chen <lecopzer.chen@...iatek.com>
> >> Cc: Mark-pk Tsai <mark-pk.tsai@...iatek.com>
> >> Cc: Joe Liu <joe.liu@...iatek.com>
> > 
> > Sorry for the long delay and thanks Lecopzer for the patch.
> > 
> > This changelog is difficult to parse but the fix may also me too specific
> > and could be more robust against types other than CMA. It is true that
> > a failed PCP acquire may return a !is_migrate_isolate page to the wrong
> > list but it's more straight-forward to unconditionally lookup the PCP
> > migratetype of the spinlock is not acquired.
> > 
> > How about this? It unconditionally looks up the PCP migratetype after
> > spinlock contention. It's build tested only
> > 
> > --8<--
> > mm: page_alloc: Free pages to correct buddy list after PCP lock contention
> > 
> > Commit 4b23a68f9536 ("mm/page_alloc: protect PCP lists with a spinlock")
> > returns pages to the buddy list on PCP lock contention. However, for
> > migratetypes that are not MIGRATE_PCPTYPES, the migratetype may have
> > been clobbered already for pages that are not being isolated. In
> > practice, this means that CMA pages may be returned to the wrong
> > buddy list. While this might be harmless in some cases as it is
> > MIGRATE_MOVABLE, the pageblock could be reassigned in rmqueue_fallback
> > and prevent a future CMA allocation. Lookup the PCP migratetype
> > against unconditionally if the PCP lock is contended.
> > 
> > [lecopzer.chen@...iatek.com: CMA-specific fix]
> > Fixes: 4b23a68f9536 ("mm/page_alloc: protect PCP lists with a spinlock")
> 
> I think we should Cc: stable for the sake of 6.1 LTS?
> 

Yep.

> > Reported-by: Joe Liu <joe.liu@...iatek.com>
> > Signed-off-by: Mel Gorman <mgorman@...hsingularity.net>
> 
> Acked-by: Vlastimil Babka <vbabka@...e.cz>
> 

Thanks.

-- 
Mel Gorman
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ