From: Adam Litke <agl@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, bugme-daemon@bugzilla.kernel.org,
starlight@binnacle.cx, 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: Tue, 02 Dec 2008 13:24:40 -0600 [thread overview]
Message-ID: <1228245880.13482.19.camel@localhost.localdomain> (raw)
In-Reply-To: <20081201181459.49d8fcca.akpm@linux-foundation.org>
On Mon, 2008-12-01 at 18:14 -0800, Andrew Morton wrote:
> > can't shmat() 1GB hugepage segment from second process more than one time
> >
> > Steps to reproduce:
starlight@binnacle.cx: I need more information to reproduce this bug.
Please read on.
I've tried these steps and haven't been able to reproduce. Are these
reproduction steps actually a description of what a more complex program
is doing, or have you reproduced this with simple C programs that
implement nothing more than the instructions provided in this bug?
It would make it easier to diagnose this if you could provide a simple C
program that causes the bad behavior.
> >
> > create 1GB or more hugepage shmget/shmat segment
> > attached at explicit virtual address 0x4_00000000
You must mean either 0x400000000 or 0x4000000000; please clarify. (I
tried both addresses and was unable to reproduce. Are you touching any
of the pages in the shared memory segment with this process? What flags
are you passing to shmget and shmat? Could you provide an strace for
each program run?
> > run another program that attaches segment
Does this second program do anything besides attaching the segment (ie.
faulting any of the huge pages)?
> > run it again, fails
> >
> > eventually get attached 'dmesg' output
> >
> > works fine under RHEL 4.6
> >
> >
--
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-02 19:24 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 [this message]
2008-12-02 19:41 ` starlight
2008-12-04 3:15 ` starlight
2008-12-05 17:17 ` Adam Litke
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=1228245880.13482.19.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