linux-kernel - Re: [PATCH 01/10] sparc/mm: Fix MAX_ORDER usage in tsb

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]

Message-ID: <ZBQo1rUXmTrFgCsR@kernel.org>
Date:   Fri, 17 Mar 2023 10:46:14 +0200
From:   Mike Rapoport <rppt@...nel.org>
To:     Mike Kravetz <mike.kravetz@...cle.com>
Cc:     "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Mel Gorman <mgorman@...e.de>, Vlastimil Babka <vbabka@...e.cz>,
        David Hildenbrand <david@...hat.com>, linux-mm@...ck.org,
        linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
        sparclinux@...r.kernel.org, David Miller <davem@...emloft.net>
Subject: Re: [PATCH 01/10] sparc/mm: Fix MAX_ORDER usage in tsb_grow()

On Wed, Mar 15, 2023 at 08:04:37PM -0700, Mike Kravetz wrote:
> On 03/15/23 14:31, Kirill A. Shutemov wrote:
> > MAX_ORDER is not inclusive: the maximum allocation order buddy allocator
> > can deliver is MAX_ORDER-1.
> > 
> > Fix MAX_ORDER usage in tsb_grow().
> > 
> > Signed-off-by: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>
> > Cc: sparclinux@...r.kernel.org
> > Cc: David Miller <davem@...emloft.net>
> > ---
> >  arch/sparc/mm/tsb.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/sparc/mm/tsb.c b/arch/sparc/mm/tsb.c
> > index 912205787161..dba8dffe2113 100644
> > --- a/arch/sparc/mm/tsb.c
> > +++ b/arch/sparc/mm/tsb.c
> > @@ -402,8 +402,8 @@ void tsb_grow(struct mm_struct *mm, unsigned long tsb_index, unsigned long rss)
> >  	unsigned long new_rss_limit;
> >  	gfp_t gfp_flags;
> >  
> > -	if (max_tsb_size > (PAGE_SIZE << MAX_ORDER))
> > -		max_tsb_size = (PAGE_SIZE << MAX_ORDER);
> > +	if (max_tsb_size > (PAGE_SIZE << (MAX_ORDER - 1)))
> > +		max_tsb_size = (PAGE_SIZE << (MAX_ORDER - 1));
> >  
> >  	new_cache_index = 0;
> >  	for (new_size = 8192; new_size < max_tsb_size; new_size <<= 1UL) {
> > 
> 
> Fortunately, I think this only comes into play if MAX_ORDER <= 7.
 
I think it's unlikely that such low ARCH_FORCE_MAX_ORDER is ever used.

Judging by c88c545bf320 ("sparc64: Add FORCE_MAX_ZONEORDER and default to
13") log the option to override MAX_ORDER was added to "request large (32M)
contiguous memory during boot for creating IOTSB backing store", so it was
about to increase MAX_ORDER.

Generally, we may restrict sparc::ARCH_FORCE_MAX_ORDER to be above 7 and
drop this check entirely

> Reviewed-by: Mike Kravetz <mike.kravetz@...cle.com>
> -- 
> Mike Kravetz
> 

-- 
Sincerely yours,
Mike.