On Sun, Jun 22, 2025 at 9:39 PM Ming Lei <ming.lei@xxxxxxxxxx> wrote:
> On Sat, Jun 21, 2025 at 02:40:41PM -0400, Paul Moore wrote:
> > On Sat, Jun 21, 2025 at 2:08 AM Ming Lei <ming.lei@xxxxxxxxxx> wrote:
> > >
> > > Hello Guys,
> > >
> > > The latest v6.16-rc2+ kernel panics during booting, commit
> > > 3f75bfff44be ("Merge tag 'mtd/fixes-for-6.16-rc3' of
> > > git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux"):
> > >
> > >
> > > [ OK ] Finished systemd-modules-load.service - Load Kernel Modules.
> > > Starting systemd-sysctl.service - Apply Kernel Variables...
> > > Starting systemd-sysusers.service - Create System Users...
> > > [ OK ] Finished systemd-sysctl.service - Apply Kernel Variables.
> > > [ 1.851473] Oops: general protection fault, probably for
> > > non-canonical address 0x8cbad568292ed62c: 0000 [#1] SMP NOPTI
> > > [ 1.853362] CPU: 9 UID: 0 PID: 269 Comm: systemd-sysuser Not
> > > tainted 6.16.0-rc2+ #328 PREEMPT(full)
> > > [ 1.854923] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),
> > > BIOS 1.16.3-1.fc39 04/01/2014
> > > [ 1.856374] RIP: 0010:__list_add_valid_or_report+0x1e/0xa0
> > > [ 1.857366] Code: 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa
> > > 53 48 83 ec 08 48 85 f6 0f 84 76 2f 76 ff 48 89 d3 48 85 d2 0f 84 5c
> > > 2f9
> > > [ 1.860338] RSP: 0018:ffffd152c0de3a10 EFLAGS: 00010286
> > > [ 1.861244] RAX: ffff8aa5414d38d8 RBX: 8cbad568292ed624 RCX: 0000000000000000
> > > [ 1.862439] RDX: 8cbad568292ed624 RSI: ffff8aa5401f40f0 RDI: ffff8aa5414d38d8
> > > [ 1.863622] RBP: ffff8aa5414d38f4 R08: ffffd152c0de3a7c R09: ffffd152c0de3a20
> > > [ 1.864810] R10: ffff8aa5401f40c0 R11: 0000000000000007 R12: ffff8aa5414d38d8
> > > [ 1.864813] R13: ffff8aa5401f40c0 R14: ffff8aa5401f40f0 R15: ffff8aa5414d38d0
> > > [ 1.864814] FS: 00007feebef42bc0(0000) GS:ffff8aa9ed02f000(0000)
> > > knlGS:0000000000000000
> > > [ 1.864816] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > > [ 1.864818] CR2: 00007feebfb58180 CR3: 0000000117f4d004 CR4: 0000000000770ef0
> > > [ 1.870018] PKRU: 55555554
> > > [ 1.870020] Call Trace:
> > > [ 1.870029] <TASK>
> > > [ 1.870031] inode_doinit_with_dentry+0x42d/0x520
> >
> > Thanks for the report. I'm assuming you didn't see this with
> > v6.16-rc1, or earlier?
>
> It isn't observed on -rc2.
>
> >
> > Do you have any line number information you could share? Also, based
> > on the RIP in __list_add_valid_or_report(), can you confirm that this
> > is either happening in an initrd/initramfs or on a system where a
> > SELinux policy is not being loaded?
>
> Looks the issue can't be reproduced any more with -rc3.
Thanks for the update. If you see this again, please let us know.
--
paul-moore.com
