From: Bill Irwin <bill.irwin@oracle.com>
To: "Alexander Y. Fomichev" <gluk@php4.ru>
Cc: Bill Irwin <bill.irwin@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
admin@list.net.ru
Subject: Re: kernel BUG at arch/x86_64/mm/../../i386/mm/hugetlbpage.c:140!
Date: Tue, 6 Mar 2007 12:19:32 -0800 [thread overview]
Message-ID: <20070306201932.GC18774@holomorphy.com> (raw)
In-Reply-To: <200703061545.23470.gluk@php4.ru>
On Saturday 03 March 2007, Bill Irwin wrote:
>> If you have a known-working kernel version, git-bisect might help you
>> track down where it was introduced. Given the messages prior to the
>> hugetlbpage.c BUG_ON I'd say that this is something else besides the
>> specific code listed by line number,
On Tue, Mar 06, 2007 at 03:45:23PM +0300, Alexander Y. Fomichev wrote:
> Nop, seems like it is hugetlb bug fixed by Adam
> commit 516dffdcd8827a40532798602830dfcfc672294c
> [PATCH] Fix get_unmapped_area and fsync for hugetlb shm segments
> I've disregard it thoughtlessly so Adam marks it specific for powerpc/ia64.
> (hmm.. i donno realy why, huge pages should be alined anyway and if i
> understend it correctly it may not be if is_file_hugepages() fails)
> As of "junk" just before the BUG this again IIUC because o-direct staff
> catches this issue before hugetlb.
I'm not terribly surprised. The issue Adam fixed is relatively easily
triggered. Bisecting probably wouldn't have been useful, sorry.
-- wli
prev parent reply other threads:[~2007-03-06 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 13:51 kernel BUG at arch/x86_64/mm/../../i386/mm/hugetlbpage.c:140! Alexander Y. Fomichev
2007-03-02 21:38 ` Nish Aravamudan
2007-03-06 12:16 ` Alexander Y. Fomichev
2007-03-02 21:41 ` Bill Irwin
2007-03-06 12:45 ` Alexander Y. Fomichev
2007-03-06 20:19 ` Bill Irwin [this message]
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=20070306201932.GC18774@holomorphy.com \
--to=bill.irwin@oracle.com \
--cc=admin@list.net.ru \
--cc=gluk@php4.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.