From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] - deleting huge pages
Date: Mon, 03 May 2004 14:53:06 +0000 [thread overview]
Message-ID: <20040503145306.GA15182@sgi.com> (raw)
In-Reply-To: <20040502123028.GA13812@sgi.com>
On Sun, May 02, 2004 at 11:33:33AM -0700, Chen, Kenneth W wrote:
> >>>> Jack Steiner wrote on Sunday, May 02, 2004 5:30 AM
> > I found this problem in 2.4,21, but AFAICT, the same problem
> > exists in 2.6.5.
> >
> > If you attempt to allocate a LOT more huge pages than are physically
> > available, the kernel may reference invalid PGDs or PMDs.
> >
> > Here is the 2.4 backtrace of a failure. If the mmap fails, do_mmap_pgoff
> > attempts to unmap the vma range it was mapping. Depending on where it failed
> > during the mmap, some of the higher level PGD/PMDs may not have been assigned.
> >
> > The bug (at least in 2.4) exists on all platforms but on our platform
> > attempts to dereference NULL pointers usually cause MCAs. (If a platform
> > has zeros in page 0, you may be lucky & the code would appear to work,
> > but it is still a bug).
> >
> > The MCA was caused by the NULL pmd dereference in huge_pte_offset. The
> > MCA doesnt surface until the bad data is consumed.
> >
> > A patch against 2.6.5:
>
> Recent work on cleaning up hugepage_vma has at least one hunk covered here.
> http://linux.bkbits.net:8080/linux-2.5/cset@40842336E3nkJ7cWJ0-3zQ7yP4WbHg
>
> - Ken
>
Yep... Looks like the same problem has been fixed by David Gibson.
Ignore my patch.
--
Thanks
Jack Steiner (steiner@sgi.com) 651-683-5302
Principal Engineer SGI - Silicon Graphics, Inc.
next prev parent reply other threads:[~2004-05-03 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-02 12:30 [PATCH] - deleting huge pages Jack Steiner
2004-05-02 18:33 ` Chen, Kenneth W
2004-05-03 14:53 ` Jack Steiner [this message]
2004-05-03 17:12 ` Chen, Kenneth W
2004-05-03 19:47 ` Jack Steiner
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=20040503145306.GA15182@sgi.com \
--to=steiner@sgi.com \
--cc=linux-ia64@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