From: Jiri Slaby <jslaby@suse.cz>
To: Hugh Dickins <hughd@google.com>, Andrey Korolyov <andrey@xdel.ru>
Cc: Dave Hansen <dave.hansen@intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
Luis Henriques <luis.henriques@canonical.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
stable@vger.kernel.org, linux-mm@kvack.org, kvm@vger.kernel.org,
wanpeng.li@linux.intel.com, jipan yang <jipan.yang@gmail.com>
Subject: Re: copy_huge_page: unable to handle kernel NULL pointer dereference at 0000000000000008
Date: Tue, 31 Mar 2015 11:45:59 +0200 [thread overview]
Message-ID: <551A6CD7.3040901@suse.cz> (raw)
In-Reply-To: <alpine.LSU.2.11.1503281705040.13543@eggly.anvils>
On 03/29/2015, 01:25 AM, Hugh Dickins wrote:
> But you are very appositely mistaken: copy_huge_page() used to make
> the same mistake, and Dave Hansen fixed it back in v3.13, but the fix
> never went to the stable trees.
>
> Your report was on an Ubuntu "3.11.0-15" kernel: I think Ubuntu have
> discontinued their 3.11-stable kernel series, but 3.10-longterm and
> 3.12-longterm would benefit from including this fix. I haven't tried
> patching and building and testing it there, but it looks reasonable.
>
> Hugh
>
> commit 30b0a105d9f7141e4cbf72ae5511832457d89788
> Author: Dave Hansen <dave.hansen@linux.intel.com>
> Date: Thu Nov 21 14:31:58 2013 -0800
>
> mm: thp: give transparent hugepage code a separate copy_page
Applied to 3.12. Thanks.
--
js
suse labs
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jslaby@suse.cz>
To: Hugh Dickins <hughd@google.com>, Andrey Korolyov <andrey@xdel.ru>
Cc: Dave Hansen <dave.hansen@intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
Luis Henriques <luis.henriques@canonical.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
stable@vger.kernel.org, linux-mm@kvack.org, kvm@vger.kernel.org,
wanpeng.li@linux.intel.com, jipan yang <jipan.yang@gmail.com>
Subject: Re: copy_huge_page: unable to handle kernel NULL pointer dereference at 0000000000000008
Date: Tue, 31 Mar 2015 11:45:59 +0200 [thread overview]
Message-ID: <551A6CD7.3040901@suse.cz> (raw)
In-Reply-To: <alpine.LSU.2.11.1503281705040.13543@eggly.anvils>
On 03/29/2015, 01:25 AM, Hugh Dickins wrote:
> But you are very appositely mistaken: copy_huge_page() used to make
> the same mistake, and Dave Hansen fixed it back in v3.13, but the fix
> never went to the stable trees.
>
> Your report was on an Ubuntu "3.11.0-15" kernel: I think Ubuntu have
> discontinued their 3.11-stable kernel series, but 3.10-longterm and
> 3.12-longterm would benefit from including this fix. I haven't tried
> patching and building and testing it there, but it looks reasonable.
>
> Hugh
>
> commit 30b0a105d9f7141e4cbf72ae5511832457d89788
> Author: Dave Hansen <dave.hansen@linux.intel.com>
> Date: Thu Nov 21 14:31:58 2013 -0800
>
> mm: thp: give transparent hugepage code a separate copy_page
Applied to 3.12. Thanks.
--
js
suse labs
--
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:[~2015-03-31 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 16:34 copy_huge_page: unable to handle kernel NULL pointer dereference at 0000000000000008 Andrey Korolyov
2015-02-04 16:42 ` Andrey Korolyov
2015-02-24 0:12 ` Marcelo Tosatti
2015-03-28 15:51 ` Andrey Korolyov
2015-03-29 0:25 ` Hugh Dickins
2015-03-31 9:45 ` Jiri Slaby [this message]
2015-03-31 9:45 ` Jiri Slaby
2015-03-31 10:01 ` Andrey Korolyov
2015-07-02 11:58 ` Andrey Korolyov
-- strict thread matches above, loose matches on Subject: below --
2014-07-03 7:57 jipan yang
2014-07-03 8:08 ` Wanpeng Li
2014-07-03 8:14 ` jipan yang
2014-07-03 8:09 ` jipan yang
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=551A6CD7.3040901@suse.cz \
--to=jslaby@suse.cz \
--cc=andrey@xdel.ru \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=jipan.yang@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luis.henriques@canonical.com \
--cc=mtosatti@redhat.com \
--cc=stable@vger.kernel.org \
--cc=wanpeng.li@linux.intel.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 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.