linux-kernel - Re: [PATCH] futex: bugfix for futex-key conflict when futex use hugepage

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: <20130507155411.GO11497@suse.de>
Date:	Tue, 7 May 2013 16:54:11 +0100
From:	Mel Gorman <mgorman@...e.de>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Zhang Yi <wetpzy@...il.com>, linux-kernel@...r.kernel.org,
	'Peter Zijlstra' <peterz@...radead.org>,
	'Darren Hart' <dvhart@...ux.intel.com>,
	'Ingo Molnar' <mingo@...nel.org>,
	'Dave Hansen' <dave.hansen@...ux.intel.com>,
	zhang.yi20@....com.cn, wetpzy@....com
Subject: Re: [PATCH] futex: bugfix for futex-key conflict when futex use
 hugepage

On Tue, May 07, 2013 at 05:24:57PM +0200, Thomas Gleixner wrote:
> 
> 
> On Tue, 7 May 2013, Mel Gorman wrote:
> 
> > On Tue, May 07, 2013 at 08:23:48PM +0800, Zhang Yi wrote:
> > > diff -uprN linux3.9-orig/kernel/futex.c linux3.9/kernel/futex.c
> > > --- linux3.9-orig/kernel/futex.c	2013-04-15 00:45:16.000000000 +0000
> > > +++ linux3.9/kernel/futex.c	2013-05-06 16:24:40.403525000 +0000
> > > @@ -215,6 +215,22 @@ static void drop_futex_key_refs(union fu
> > >  	}
> > >  }
> > > 
> > > +/*
> > > +* Get subpage index in compound page, and add it into futex_key.
> > > +*/
> > > +static void key_add_compound_idx(union futex_key *key,
> > > +				 struct page *head_page, struct page *page)
> > > +{
> > > +	int compound_idx;
> > > +
> > > +	if (compound_order(head_page) >= MAX_ORDER)
> > > +		compound_idx = page_to_pfn(page) - page_to_pfn(head_page);
> > > +	else
> > > +		compound_idx = page - head_page;
> > > +
> > > +	key->both.offset |= compound_idx << PAGE_SHIFT;
> > > +}
> > > +
> > 
> > This implicitely assumies it is dealing with a hugetlbfs page. Today, it
> > is the case that an inode-based futex with PageCompound is a hugetlbfs
> > page but that could change in the future if THP ever backs files. This
> > would then break again except it would be harder to fix because THP pages
> > can be collapsed underneath you after the futex key has been generated.
> > 
> > As this problem is hugetlbfs-specific should the fix be firmly in hugetlbfs
> > land? Something like the following untested and only partial diff? Is the
> > use of PageCompound in the futex path like this going to be problematic?
> 
> Why should it ?
>  

The comment for it states that it is "generally not used in hot code
paths" but it's a light-weight check that the cache lines should already
be fetched for. I doubt that the overhead of this check versus
page_head == page is noticable.

> > @@ -365,7 +366,7 @@ again:
> >  	} else {
> >  		key->both.offset |= FUT_OFF_INODE; /* inode-based key */
> >  		key->shared.inode = page_head->mapping->host;
> > -		key->shared.pgoff = page_head->index;
> > +		key->shared.pgoff = basepage_index(page_head);
> 
>   That want's to be  basepage_index(page), right ?
> 

BAH, yes.

-- 
Mel Gorman
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/