From: Adam Litke <agl@us.ibm.com>
To: starlight@binnacle.cx
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, bugme-daemon@bugzilla.kernel.org,
Andy Whitcroft <apw@shadowen.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Bug 12134] New: can't shmat() 1GB hugepage segment from second process more than one time
Date: Fri, 05 Dec 2008 11:17:30 -0600 [thread overview]
Message-ID: <1228497450.13428.26.camel@localhost.localdomain> (raw)
In-Reply-To: <6.2.5.6.2.20081203221021.01cf8e88@binnacle.cx>
On Wed, 2008-12-03 at 22:15 -0500, starlight@binnacle.cx wrote:
> At 13:24 12/2/2008 -0600, Adam Litke wrote:
> >starlight@binnacle.cx: I need more information
> >to reproduce this bug.
>
> I'm too swamped to build a test-case, but here are straces
> that show the relevant system calls and the failure.
Starlight,
Thanks for the strace output. As I suspected, this is more complex than
it first appeared. There are several hugetlb shared memory segments
involved. Couple that with threading and an interesting approach to
mlocking the address space and I've got a very difficult to reproduce
scenario. Is it possible/practical for me to have access to your
program? If so, I could quickly bisect the kernel and identify the
guilty patch. Without the program, I am left stabbing in the dark.
Could you try on a 2.6.18 kernel to see if it works or not? Thanks.
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-12-05 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12134-27@http.bugzilla.kernel.org/>
2008-12-02 2:14 ` Andrew Morton
2008-12-02 19:24 ` Adam Litke
2008-12-02 19:41 ` starlight
2008-12-04 3:15 ` starlight
2008-12-05 17:17 ` Adam Litke [this message]
2008-12-05 17:49 ` starlight
2008-12-05 18:57 ` Adam Litke
2008-12-05 19:04 ` starlight
2008-12-06 5:17 starlight
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=1228497450.13428.26.camel@localhost.localdomain \
--to=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=david@gibson.dropbear.id.au \
--cc=linux-mm@kvack.org \
--cc=starlight@binnacle.cx \
/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