From: Kees Cook <keescook@chromium.org>
To: Murphy Zhou <jencce.kernel@gmail.com>,
Hugh Dickins <hughd@google.com>,
David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux-Next <linux-next@vger.kernel.org>
Subject: Re: linux-next: panic on 20220307 tree
Date: Thu, 10 Mar 2022 08:29:34 -0800 [thread overview]
Message-ID: <202203100825.8EAF86328B@keescook> (raw)
In-Reply-To: <CADJHv_t0wMLJLCSkSh2CWTA=RKgYK0oxqqhnTdmuwtKSzdP5Jg@mail.gmail.com>
On Tue, Mar 08, 2022 at 10:44:57AM +0800, Murphy Zhou wrote:
> Hi,
>
> Hit this shortly after build the next tree and reboot.
>
> [ 72.985994] ------------[ cut here ]------------
> [ 72.986023] ------------[ cut here ]------------
> [ 73.009468] kernel BUG at include/linux/swapops.h:258!
> [ 73.033065] kernel BUG at include/linux/swapops.h:258!
This is in here:
static inline struct page *pfn_swap_entry_to_page(swp_entry_t entry)
{
struct page *p = pfn_to_page(swp_offset(entry));
/*
* Any use of migration entries may only occur while the
* corresponding page is locked
*/
BUG_ON(is_migration_entry(entry) && !PageLocked(p));
return p;
}
Hugh, David, Andrew, might any of the recent mm/memory.c work caused
problems in here? (Or is this already fixed?)
-Kees
> [ 73.033079] invalid opcode: 0000 [#1] PREEMPT SMP PTI
> [ 73.107068] CPU: 16 PID: 5709 Comm: mksquashfs Tainted: G W
> I 5.17.0-rc6-next-20220307 #1
> [ 73.148943] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 08/02/2014
> [ 73.178737] RIP: 0010:migration_entry_wait_on_locked+0x266/0x300
> [ 73.206068] Code: 06 88 44 24 07 eb d7 66 90 e9 09 ff ff ff 48 8b
> 43 08 a8 01 0f 85 8d 00 00 00 66 90 48 89 d8 48 8b 00 a8 01 0f 85 e6
> fd ff ff <0f> 0b 48 8d 58 ff e9 ec fd ff ff 65 48 8b 04 25 40 ef 01 00
> 48 83
> [ 73.291471] RSP: 0000:ffffb2f68bf27d60 EFLAGS: 00010246
> [ 73.315812] RAX: 0057ffffc009000c RBX: ffffdead13400000 RCX: 0000000000000000
> [ 73.348177] RDX: ffffdead1111d3e8 RSI: 0000000000000000 RDI: 000000000000001b
> [ 73.380458] RBP: 0000000000000000 R08: ffff991900168a78 R09: 0000000000000000
> [ 73.412830] R10: 0000000000000000 R11: 0000000000000000 R12: ffffdead1111d3e8
> [ 73.445535] R13: 0400000000000000 R14: 0400000000000080 R15: ffff9918d107ce10
> [ 73.477657] FS: 00007f0cb9ffb640(0000) GS:ffff9918af800000(0000)
> knlGS:0000000000000000
> [ 73.515499] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 73.544576] CR2: 000055d3d30cc2e0 CR3: 0000000460914004 CR4: 00000000001706e0
> [ 73.578491] Call Trace:
> [ 73.590469] <TASK>
> [ 73.600493] ? dio_warn_stale_pagecache.part.0+0x50/0x50
> [ 73.624513] __handle_mm_fault+0x5cb/0x700
> [ 73.642955] handle_mm_fault+0xc5/0x290
> [ 73.660168] do_user_addr_fault+0x1b4/0x680
> [ 73.678949] exc_page_fault+0x62/0x140
> [ 73.696792] ? asm_exc_page_fault+0x8/0x30
> [ 73.716177] asm_exc_page_fault+0x1e/0x30
> [ 73.734348] RIP: 0033:0x55d3d2da7658
> [ 73.750529] Code: 25 00 80 00 ff 05 00 00 00 01 09 d8 48 8b 54 24
> 08 64 48 2b 14 25 28 00 00 00 75 5a 48 83 c4 10 5b 5d 41 5c c3 0f 1f
> 44 00 00 <48> 8b 05 81 4c 32 00 4c 8d 4c 24 04 ff 50 20 83 f8 ff 74 0a
> 85 c0
> [ 73.836254] RSP: 002b:00007f0cb9ffadf0 EFLAGS: 00010246
> [ 73.860578] RAX: 0000000000000000 RBX: 0000000000020000 RCX: 0000000000020000
> [ 73.894417] RDX: 00007f0c616c5d00 RSI: 00007f0c9c2026a0 RDI: 00007f0c9c020bd0
> [ 73.926629] RBP: 00007f0c9c2026a0 R08: 0000000000020000 R09: 0000000000000000
> [ 73.958922] R10: 0000000000020000 R11: 00007f0c616c5d00 R12: 00007f0c616c5d00
> [ 73.991337] R13: 0000000000000002 R14: 00007f0e19ca43f0 R15: 0000000000000000
> [ 74.024964] </TASK>
>
>
> Kernel config is attached.
--
Kees Cook
next prev parent reply other threads:[~2022-03-10 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 2:44 linux-next: panic on 20220307 tree Murphy Zhou
2022-03-10 16:29 ` Kees Cook [this message]
2022-03-10 16:54 ` David Hildenbrand
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=202203100825.8EAF86328B@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=jencce.kernel@gmail.com \
--cc=linux-next@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.