mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: r6144 <rainy6144@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Process-shared futexes on hugepages puts the kernel in an infinite loop in 2.6.32.11; is this fixed now?
Date: Fri, 16 Apr 2010 23:45:22 +0800	[thread overview]
Message-ID: <1271432722.2564.16.camel@localhost.localdomain> (raw)

Hello all,

I'm having an annoying kernel bug regarding huge pages in Fedora 12:

https://bugzilla.redhat.com/show_bug.cgi?id=552257

Basically I want to use huge pages in a multithreaded number crunching
program, which happens to use process-shared semaphores (because fftw
does it).  The futex for the semaphore ends up lying on a huge page, and
I then get an endless loop in get_futex_key(), apparently because the
anonymous huge page containing the futex does not have a page->mapping.
A test case is provided in the above link.

I reported the bug to Fedora bugzilla months ago, but haven't received
any feedback yet.  The Fedora kernel is based on 2.6.32.11, and a
cursory glance at the 2.6.34-rc3 source does not yield any relevant
change.

So, could anyone tell me if the current mainline kernel might act better
in this respect, before I get around to compiling it?

Thank you very much.

Please CC me as I'm not subscribed.

r6144


             reply	other threads:[~2010-04-16 15:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16 15:45 r6144 [this message]
2010-04-16 20:27 ` Peter Zijlstra
2010-04-19 11:43   ` Mel Gorman
2010-04-19 11:52     ` Peter Zijlstra
2010-04-19 15:32       ` Mel Gorman
2010-04-19 15:45         ` Peter Zijlstra
2010-04-19 16:11           ` Andrea Arcangeli
2010-04-19 16:18             ` Peter Zijlstra
2010-04-19 16:32               ` Andrea Arcangeli
2010-04-19 16:34           ` Mel Gorman
2010-04-19 15:48         ` Andrea Arcangeli
2010-04-19 16:04         ` Darren Hart

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=1271432722.2564.16.camel@localhost.localdomain \
    --to=rainy6144@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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
Powered by JetHome