linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: starlight@binnacle.cx
To: linux-mm@kvack.org, Adam Litke <agl@us.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 12134] can't shmat() 1GB hugepage segment from second process more than one time
Date: Wed, 13 May 2009 16:18:21 -0400	[thread overview]
Message-ID: <6.2.5.6.2.20090513161759.03a54ec0@flumedata.com> (raw)

New life for old bug.

Reproduced under 2.6.29.1.

Also discerned separate hugepage fork() issue now reported
under bug 13302.

Sorry I keep forgetting to stay with e-mail.  Bugzillas
are easier to keep track of over many months.

--
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>

                 reply	other threads:[~2009-05-13 20:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6.2.5.6.2.20090513161759.03a54ec0@flumedata.com \
    --to=starlight@binnacle.cx \
    --cc=agl@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-mm@kvack.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