From: Andrew Morton <akpm@linux-foundation.org>
To: Qian Cai <cai@lca.pw>
Cc: heiko.carstens@de.ibm.com, gor@linux.ibm.com,
borntraeger@de.ibm.com, linux-s390@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page_alloc: fix a crash in free_pages_prepare()
Date: Fri, 27 Sep 2019 13:48:59 -0700 [thread overview]
Message-ID: <20190927134859.95a2f4908bdcea30df0184ed@linux-foundation.org> (raw)
In-Reply-To: <1569613623-16820-1-git-send-email-cai@lca.pw>
On Fri, 27 Sep 2019 15:47:03 -0400 Qian Cai <cai@lca.pw> wrote:
> On architectures like s390, arch_free_page() could mark the page unused
> (set_page_unused()) and any access later would trigger a kernel panic.
> Fix it by moving arch_free_page() after all possible accessing calls.
>
> Hardware name: IBM 2964 N96 400 (z/VM 6.4.0)
> Krnl PSW : 0404e00180000000 0000000026c2b96e
> (__free_pages_ok+0x34e/0x5d8)
> R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3
> Krnl GPRS: 0000000088d43af7 0000000000484000 000000000000007c
> 000000000000000f
> 000003d080012100 000003d080013fc0 0000000000000000
> 0000000000100000
> 00000000275cca48 0000000000000100 0000000000000008
> 000003d080010000
> 00000000000001d0 000003d000000000 0000000026c2b78a
> 000000002717fdb0
> Krnl Code: 0000000026c2b95c: ec1100b30659 risbgn %r1,%r1,0,179,6
> 0000000026c2b962: e32014000036 pfd 2,1024(%r1)
> #0000000026c2b968: d7ff10001000 xc 0(256,%r1),0(%r1)
> >0000000026c2b96e: 41101100 la %r1,256(%r1)
> 0000000026c2b972: a737fff8 brctg %r3,26c2b962
> 0000000026c2b976: d7ff10001000 xc 0(256,%r1),0(%r1)
> 0000000026c2b97c: e31003400004 lg %r1,832
> 0000000026c2b982: ebff1430016a asi 5168(%r1),-1
> Call Trace:
> __free_pages_ok+0x16a/0x5d8)
> memblock_free_all+0x206/0x290
> mem_init+0x58/0x120
> start_kernel+0x2b0/0x570
> startup_continue+0x6a/0xc0
> INFO: lockdep is turned off.
> Last Breaking-Event-Address:
> __free_pages_ok+0x372/0x5d8
> Kernel panic - not syncing: Fatal exception: panic_on_oops
> 00: HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000
> 26A2379C
>
> ...
>
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -1175,11 +1175,11 @@ static __always_inline bool free_pages_prepare(struct page *page,
> debug_check_no_obj_freed(page_address(page),
> PAGE_SIZE << order);
> }
> - arch_free_page(page, order);
> if (want_init_on_free())
> kernel_init_free_pages(page, 1 << order);
>
> kernel_poison_pages(page, 1 << order, 0);
> + arch_free_page(page, order);
> if (debug_pagealloc_enabled())
> kernel_map_pages(page, 1 << order, 0);
This is all fairly mature code, isn't it? What happened to make this
problem pop up now?
IOW, is a -stable backport needed?
next prev parent reply other threads:[~2019-09-27 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 19:47 Qian Cai
2019-09-27 20:48 ` Andrew Morton [this message]
2019-09-27 21:15 ` Qian Cai
2019-09-30 7:44 ` Heiko Carstens
2019-09-27 21:02 ` Andrew Morton
2019-09-27 21:28 ` Qian Cai
2019-09-27 21:59 ` Andrew Morton
2019-09-27 22:17 ` Alexander Duyck
2019-09-28 9:06 ` David Hildenbrand
2019-09-30 6:27 ` Christian Borntraeger
2019-09-30 6:30 ` Christian Borntraeger
2019-09-30 11:00 ` Michal Hocko
2019-09-30 11:04 ` Kirill A. Shutemov
2019-09-30 11:22 ` Qian Cai
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=20190927134859.95a2f4908bdcea30df0184ed@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=cai@lca.pw \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@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