From: Borislav Petkov <bp@alien8.de>
To: "V, Narasimhan" <Narasimhan.V@amd.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Aithal, Srikanth" <Srikanth.Aithal@amd.com>,
Dawei Li <dawei.li@shingroup.cn>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Yury Norov <yury.norov@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Boot failure with kernel BUG at mm/usercopy.c on next-20240325
Date: Mon, 25 Mar 2024 13:50:17 +0100 [thread overview]
Message-ID: <20240325125017.GBZgFzCXVxeF50uGVE@fat_crate.local> (raw)
In-Reply-To: <DM4PR12MB5086E76CF24A39017DA8567189362@DM4PR12MB5086.namprd12.prod.outlook.com>
Adding more people from that
328c801335d5 ("cpumask: create dedicated kmem cache for cpumask var")
in linux-next.
On Mon, Mar 25, 2024 at 01:40:20PM +0100, V, Narasimhan wrote:
> [AMD Official Use Only - General]
>
> Hi,
> There is a boot failure as below.
> On bisecting, the bad commit is found to be 328c801335d5f7edf2a3c9c331ddf8978f21e2a7.
> Boots fine if we revert the above bad commit.
Narasimhan,
please send your .config and reproduction instructions. I'm guessing
you're simply booting it, right?
Leaving in the rest for the newly CCed people.
> kernel BUG at mm/usercopy.c:102!
> invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
> CPU: 15 PID: 567 Comm: systemd-udevd Not tainted 6.9.0-rc1-next-20240325-1711333827684 #1
> Hardware name: AMD Corporation Shale96/Shale96, BIOS RSH100BD 12/11/2023
> RIP: 0010:usercopy_abort+0x72/0x90
> Code: 4f f7 b8 50 48 c7 c2 31 a6 f4 b8 57 48 c7 c7 50 10 fe b8 48 0f 44 d6 48 c7 c6 32 30 f5 b8 4c 89 d1 49 0f 44 f3 e8 5e 2b d1 ff <0f> 0b 49 c7 c1 1c 60 f4 b8 4c 89 cf 4d 89 c8 eb a9 66 66 2e 0f 1f
> RSP: 0018:ff855d5641947e08 EFLAGS: 00010246
> RAX: 0000000000000060 RBX: 0000000000000000 RCX: ff44c5dccd9ff8a8
> RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000001
> RBP: ff855d5641947e20 R08: 0000000000000060 R09: 6c656e72654b203a
> R10: ffffffffba1edd60 R11: 657275736f707865 R12: 0000000000000008
> R13: ff44c5cd80037800 R14: 0000000000000001 R15: 0000000000000000
> FS: 00007fbc2be258c0(0000) GS:ff44c5dc86f80000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007fbc2c459230 CR3: 0000000103f54004 CR4: 0000000000771ef0
> PKRU: 55555554
> Call Trace:
> <TASK>
> ? show_regs+0x6d/0x80
> ? die+0x3c/0xa0
> ? do_trap+0xcf/0xf0
> ? do_error_trap+0x75/0xa0
> ? usercopy_abort+0x72/0x90
> ? exc_invalid_op+0x57/0x80
> ? usercopy_abort+0x72/0x90
> ? asm_exc_invalid_op+0x1f/0x30
> ? usercopy_abort+0x72/0x90
> ? usercopy_abort+0x72/0x90
> __check_heap_object+0xd6/0x110
> __check_object_size+0x28a/0x2f0
> ? srso_alias_return_thunk+0x5/0xfbef5
> __x64_sys_sched_getaffinity+0xda/0x120
> do_syscall_64+0x76/0x120
> ? srso_alias_return_thunk+0x5/0xfbef5
> ? do_syscall_64+0x85/0x120
> ? srso_alias_return_thunk+0x5/0xfbef5
> ? syscall_exit_to_user_mode+0x75/0x190
> ? srso_alias_return_thunk+0x5/0xfbef5
> ? do_syscall_64+0x85/0x120
> entry_SYSCALL_64_after_hwframe+0x6c/0x74
> RIP: 0033:0x7fbc2c507d6a
> Code: d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa 49 89 f0 be ff ff ff 7f b8 cc 00 00 00 49 39 f0 49 0f 46 f0 0f 05 <48> 3d 00 f0 ff ff 77 2e 41 89 c1 83 f8 ff 74 38 48 98 48 83 ec 08
> RSP: 002b:00007ffceab058d8 EFLAGS: 00000297 ORIG_RAX: 00000000000000cc
> RAX: ffffffffffffffda RBX: 0000000000000010 RCX: 00007fbc2c507d6a
> RDX: 000055b26dfa3040 RSI: 0000000000000008 RDI: 0000000000000000
> RBP: 000055b26dfa3040 R08: 0000000000000008 R09: 00000000ffffffff
> R10: 000055b26dfa3030 R11: 0000000000000297 R12: 0000000000000008
> R13: 000000000000003c R14: 00007ffceab05ac8 R15: 000055b258445078
> </TASK>
> Modules linked in: aesni_intel crypto_simd cryptd
> ---[ end trace 0000000000000000 ]---
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-03-25 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 12:40 Boot failure with kernel BUG at mm/usercopy.c on next-20240325 V, Narasimhan
2024-03-25 12:50 ` Borislav Petkov [this message]
2024-03-25 18:34 ` Andrew Morton
2024-03-25 20:37 ` Borislav Petkov
2024-03-26 2:30 ` Feng Tang
2024-03-26 19:56 ` Andrew Morton
2024-03-25 15:28 ` Feng Tang
2024-03-25 17:48 ` V, Narasimhan
-- strict thread matches above, loose matches on Subject: below --
2024-03-25 12:36 V, Narasimhan
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=20240325125017.GBZgFzCXVxeF50uGVE@fat_crate.local \
--to=bp@alien8.de \
--cc=Narasimhan.V@amd.com \
--cc=Srikanth.Aithal@amd.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dawei.li@shingroup.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=yury.norov@gmail.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.