From: Minchan Kim <minchan.kim@gmail.com>
To: Norbert Preining <preining@logic.at>, Jody Belka <jody+lkml@jj79.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: OOM killer, page fault
Date: Fri, 6 Nov 2009 07:18:23 +0900 [thread overview]
Message-ID: <28c262360911051418r1aefbff6oa54a63d887c0ea48@mail.gmail.com> (raw)
In-Reply-To: <loom.20091105T213323-393@post.gmane.org>
On Fri, Nov 6, 2009 at 5:37 AM, Jody Belka <jody+lkml@jj79.org> wrote:
> Norbert Preining <preining <at> logic.at> writes:
>> Don't ask me why, please, and I don't have a serial/net console so that
>> I can tell you more, but the booting hangs badly at:
>
> <snip>
>
>>
>> > diff --git a/mm/memory.c b/mm/memory.c
>> > index 7e91b5f..47e4b15 100644
>> > --- a/mm/memory.c
>> > +++ b/mm/memory.c
>> > @@ -2713,7 +2713,11 @@ static int __do_fault(struct mm_struct *mm,
>> > struct vm_area_struct *vma,
>> > vmf.page = NULL;
>> >
>> > ret = vma->vm_ops->fault(vma, &vmf);
>> > - if (unlikely(ret & (VM_FAULT_ERROR | VM_FAULT_NOPAGE)))
>> > + if (unlikely(ret & (VM_FAULT_ERROR | VM_FAULT_NOPAGE))) {
>> > + printk(KERN_DEBUG "vma->vm_ops->fault : 0x%lx\n",
>> > vma->vm_ops->fault);
>> > + WARN_ON(1);
>> > +
>> > + }
>> > return ret;
>> >
>> > if (unlikely(PageHWPoison(vmf.page))) {
>>
>
> Erm, could it not be due to the "return ret;" line being moved outside of the
> if(), so that it always executes?
Right. Sorry it's my fault.
I become blind.
'return ret' should be inclueded in debug code.
>
>
> J
>
> ps, sending this through gmane, don't know if it'll keep cc's or not, so
> apologies if not. please cc me on any replies
>
> --
> 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>
>
--
Kind regards,
Minchan Kim
--
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:[~2009-11-05 22:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091030063216.GA30712@gamma.logic.tuwien.ac.at>
2009-11-02 4:24 ` KOSAKI Motohiro
2009-11-02 4:56 ` Minchan Kim
2009-11-02 5:02 ` KAMEZAWA Hiroyuki
2009-11-02 6:01 ` Minchan Kim
2009-11-02 16:26 ` Hugh Dickins
2009-11-02 23:28 ` Minchan Kim
2009-11-02 6:35 ` Minchan Kim
2009-11-02 14:19 ` Norbert Preining
2009-11-02 14:40 ` Minchan Kim
2009-11-05 13:21 ` Norbert Preining
2009-11-05 15:19 ` Minchan Kim
2009-11-05 15:26 ` Norbert Preining
2009-11-05 16:16 ` Norbert Preining
2009-11-05 20:37 ` Jody Belka
2009-11-05 22:18 ` Minchan Kim [this message]
2009-11-06 0:01 ` Norbert Preining
2009-11-06 13:38 ` Norbert Preining
2009-11-06 15:14 ` Minchan Kim
2009-11-06 15:18 ` Norbert Preining
2009-11-02 6:59 ` KOSAKI Motohiro
2009-11-02 7:00 ` Minchan Kim
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=28c262360911051418r1aefbff6oa54a63d887c0ea48@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=jody+lkml@jj79.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=preining@logic.at \
/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