From: Darren Hart <dvhart@linux.intel.com>
To: Zhang Yi <wetpzy@gmail.com>
Cc: linux-kernel@vger.kernel.org, "'Mel Gorman'" <mgorman@suse.de>,
"'Ingo Molnar'" <mingo@kernel.org>,
"'Peter Zijlstra'" <peterz@infradead.org>,
"'Thomas Gleixner'" <tglx@linutronix.de>,
zhang.yi20@zte.com.cn
Subject: Re: Re: [PATCH] futex: bugfix for futex-key conflict when futex use hugepage
Date: Tue, 25 Jun 2013 11:23:30 -0700 [thread overview]
Message-ID: <1372184610.7914.96.camel@envy.home> (raw)
In-Reply-To: <000101ce71a6$a83c5880$f8b50980$@com>
Hi Zhang Yi,
Thanks for turning around an update so quickly. The code itself looks
ready to me. We try to maintain a high level of quality in the commit
message as well to help with understanding complex systems such as
futexes.
On Tue, 2013-06-25 at 21:19 +0800, Zhang Yi wrote:
> The futex-keys of processes share futex determined by page-offset,
"share futex" is rather confusing to me. Maybe:
The futex-key is determined by page-offset, ...
> mapping-host, and mapping-index of the user space address. User
> appications using hugepage for futex may lead to futex-key conflict.
Please take care with spelling. Grammar issues aren't as critical, but
please enable spell checking in your editor.
applications
hugepages for futexes
conflicts
>
> Assume there are two or more futexes in diffrent normal pages of the
different
> hugepage, and each futex has the same offset in its normal page,
> causing all the futexes have the same futex-key.
then all the futexes will have the same futex-key.
>
> This patch adds the normal page index in the compound page into
> the pgoff of futex-key.
of the futex_key.
>
> Steps to reproduce the bug:
> 1. The 1st thread map a file of hugetlbfs, and use the return address
maps
uses
> as the 1st mutex's address, and use the return address with PAGE_SIZE
uses
> added as the 2nd mutex's address.
> 2. The 1st thread initialize the two mutexes with pshared attribute,
initializes
the pshared attribute,
> and lock the two mutexes.
locks
> 3. The 1st thread create the 2nd thread, and the 2nd thread block on
creates
blocks
> the 1st mutex.
> 4. The 1st thread create the 3rd thread, and the 3rd thread block on
creates
blocks
> the 2nd mutex.
> 5. The 1st thread unlock the 2nd mutex, the 3rd thread cannot take
unlocks
> the 2nd mutex, and may block forever.
>
> Signed-off-by: Zhang Yi <zhang.yi20@zte.com.cn>
> Tested-by: Ma Chenggong <ma.chenggong@zte.com.cn>
> Reviewed-by: Jiang Biao <jiang.biao2@zte.com.cn>
>
Otherwise this looks ready to me. Thomas, do you want a resend with
commit message corrections or do you prefer to integrate those
yourself?
With the above fixes:
Acked-by: Darren Hart <dvhart@linux.intel.com>
> diff -uprN linux-3.10-rc7.org/include/linux/hugetlb.h linux-3.10-rc7/include/linux/hugetlb.h
> --- linux-3.10-rc7.org/include/linux/hugetlb.h 2013-06-22 19:47:31.000000000 +0000
> +++ linux-3.10-rc7/include/linux/hugetlb.h 2013-06-25 09:40:06.256556000 +0000
> @@ -358,6 +358,17 @@ static inline int hstate_index(struct hs
> return h - hstates;
> }
>
> +pgoff_t __basepage_index(struct page *page);
> +
> +/* Return page->index in PAGE_SIZE units */
> +static inline pgoff_t basepage_index(struct page *page)
> +{
> + if (!PageCompound(page))
> + return page->index;
> +
> + return __basepage_index(page);
> +}
> +
> #else /* CONFIG_HUGETLB_PAGE */
> struct hstate {};
> #define alloc_huge_page_node(h, nid) NULL
> @@ -378,6 +389,11 @@ static inline unsigned int pages_per_hug
> }
> #define hstate_index_to_shift(index) 0
> #define hstate_index(h) 0
> +
> +static inline pgoff_t basepage_index(struct page *page)
> +{
> + return page->index;
> +}
> #endif /* CONFIG_HUGETLB_PAGE */
>
> #endif /* _LINUX_HUGETLB_H */
> diff -uprN linux-3.10-rc7.org/kernel/futex.c linux-3.10-rc7/kernel/futex.c
> --- linux-3.10-rc7.org/kernel/futex.c 2013-06-22 19:47:31.000000000 +0000
> +++ linux-3.10-rc7/kernel/futex.c 2013-06-25 09:35:59.615425000 +0000
> @@ -61,6 +61,7 @@
> #include <linux/nsproxy.h>
> #include <linux/ptrace.h>
> #include <linux/sched/rt.h>
> +#include <linux/hugetlb.h>
>
> #include <asm/futex.h>
>
> @@ -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);
> }
>
> get_futex_key_refs(key);
> diff -uprN linux-3.10-rc7.org/mm/hugetlb.c linux-3.10-rc7/mm/hugetlb.c
> --- linux-3.10-rc7.org/mm/hugetlb.c 2013-06-25 09:38:53.435151000 +0000
> +++ linux-3.10-rc7/mm/hugetlb.c 2013-06-25 09:39:30.375701000 +0000
> @@ -690,6 +690,23 @@ int PageHuge(struct page *page)
> }
> EXPORT_SYMBOL_GPL(PageHuge);
>
> +pgoff_t __basepage_index(struct page *page)
> +{
> + struct page *page_head = compound_head(page);
> + pgoff_t index = page_index(page_head);
> + unsigned long compound_idx;
> +
> + if (!PageHuge(page_head))
> + return page_index(page);
> +
> + if (compound_order(page_head) >= MAX_ORDER)
> + compound_idx = page_to_pfn(page) - page_to_pfn(page_head);
> + else
> + compound_idx = page - page_head;
> +
> + return (index << compound_order(page_head)) + compound_idx;
> +}
> +
> static struct page *alloc_fresh_huge_page_node(struct hstate *h, int nid)
> {
> struct page *page;
>
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-06-25 18:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 13:57 [PATCH] futex: bugfix for futex-key conflict when futex use hugepage Zhang Yi
2013-05-15 14:20 ` Mel Gorman
2013-05-16 1:16 ` zhang.yi20
2013-05-16 1:30 ` Darren Hart
2013-05-16 2:00 ` zhang.yi20
2013-06-24 21:02 ` Darren Hart
2013-06-25 13:19 ` Zhang Yi
2013-06-25 18:23 ` Darren Hart [this message]
2013-06-25 19:41 ` Thomas Gleixner
2013-06-25 21:15 ` [tip:core/locking] futex: Take hugepages into account when generating futex_key tip-bot for Zhang Yi
-- strict thread matches above, loose matches on Subject: below --
2013-04-26 12:13 [PATCH] futex: bugfix for futex-key conflict when futex use hugepage Zhang Yi
2013-04-26 18:26 ` Thomas Gleixner
2013-05-07 12:23 ` Zhang Yi
2013-05-07 15:20 ` Mel Gorman
2013-05-10 9:08 ` zhang.yi20
2013-05-10 9:42 ` Mel Gorman
2013-04-16 18:37 Dave Hansen
2013-04-17 7:47 ` zhang.yi20
2013-04-16 17:57 Darren Hart
2013-04-17 9:55 ` zhang.yi20
2013-04-17 14:18 ` Darren Hart
2013-04-17 15:26 ` Dave Hansen
2013-04-17 15:51 ` Darren Hart
2013-04-18 8:05 ` zhang.yi20
2013-04-18 14:34 ` Darren Hart
2013-04-19 2:13 ` zhang.yi20
2013-04-19 2:45 ` Darren Hart
2013-04-19 7:03 ` zhang.yi20
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=1372184610.7914.96.camel@envy.home \
--to=dvhart@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=wetpzy@gmail.com \
--cc=zhang.yi20@zte.com.cn \
/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).