From: Michal Hocko <mhocko@suse.cz>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org, kamezawa.hiroyu@jp.fujitsu.com,
akpm@linux-foundation.org, rientjes@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/hugetlb: Use compound page head in migrate_huge_page
Date: Tue, 29 May 2012 11:58:27 +0200 [thread overview]
Message-ID: <20120529095827.GC15293@tiehlicka.suse.cz> (raw)
In-Reply-To: <87obp7u13r.fsf@skywalker.in.ibm.com>
On Tue 29-05-12 08:48:00, Aneesh Kumar K.V wrote:
> Michal Hocko <mhocko@suse.cz> writes:
>
> > On Mon 28-05-12 20:51:30, Aneesh Kumar K.V wrote:
> >> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
> >>
> >> The change was introduced by "hugetlb: simplify migrate_huge_page() "
> >>
> >> We should use compound page head instead of tail pages in
> >> migrate_huge_page().
> >>
> >> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> >> ---
> >> mm/memory-failure.c | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> This is an important bug fix. If we want we can fold it with the not
> >> yet merged upstream patch mentioned above in linux-next. The stack
> >> trace for the crash is
> >>
> >> [ 75.337421] BUG: unable to handle kernel NULL pointer dereference at 0000000000000080
> >> [ 75.338386] IP: [<ffffffff816b3f0f>] __mutex_lock_common+0xa1/0x350
> >> [ 75.338386] PGD 1d700067 PUD 1d7dd067 PMD 0
> >> [ 75.338386] Oops: 0002 [#1] SMP
> >> [ 75.338386] CPU 1
> >> [ 75.338386] Modules linked in:
> >> ...
> >> ...
> >>
> >> [ 75.338386] Call Trace:
> >> [ 75.338386] [<ffffffff810ffc04>] ? try_to_unmap_file+0x38/0x51c
> >> [ 75.338386] [<ffffffff810ffc04>] ? try_to_unmap_file+0x38/0x51c
> >> [ 75.338386] [<ffffffff813b5f8b>] ? vsnprintf+0x83/0x421
> >> [ 75.338386] [<ffffffff816b427d>] mutex_lock_nested+0x2a/0x31
> >> [ 75.338386] [<ffffffff8110999b>] ? alloc_huge_page_node+0x1d/0x55
> >> [ 75.338386] [<ffffffff810ffc04>] try_to_unmap_file+0x38/0x51c
> >> [ 75.338386] [<ffffffff8110999b>] ? alloc_huge_page_node+0x1d/0x55
> >> [ 75.338386] [<ffffffff810a06b9>] ? arch_local_irq_save+0x9/0xc
> >> [ 75.338386] [<ffffffff816b5e3b>] ? _raw_spin_unlock+0x23/0x27
> >> [ 75.338386] [<ffffffff81100839>] try_to_unmap+0x25/0x3c
> >> [ 75.338386] [<ffffffff810641c2>] ? console_unlock+0x210/0x238
> >> [ 75.338386] [<ffffffff811141e3>] migrate_huge_page+0x8d/0x178
> >
> > This should be part of the changelog.
>
> I was expecting the patch to be folded back to the existing patch in
> -mm. That is the reason I added stack trace in the notes section so that
> if we decided to keep it as a separate patch we can pull the stack trace
> and add it to commit message.
OK.
--
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-05-29 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 15:21 Aneesh Kumar K.V
2012-05-28 19:13 ` Michal Hocko
2012-05-29 3:18 ` Aneesh Kumar K.V
2012-05-29 9:58 ` Michal Hocko [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=20120529095827.GC15293@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
/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