Re: [moderation/CI] Re: mm: split the file's i_mmap tree for NUMA

#syz upstream

On Thu, Jun 11, 2026 at 9:45 PM syzbot ci
<[email protected]> wrote:
>
> syzbot ci has tested the following series
>
> [v2] mm: split the file's i_mmap tree for NUMA
> https://lore.kernel.org/all/[email protected]
> * [PATCH v2 1/4] mm: use mapping_mapped to simplify the code
> * [PATCH v2 2/4] mm: use get_i_mmap_root to access the file's i_mmap
> * [PATCH v2 3/4] mm/fs: split the file's i_mmap tree
> * [PATCH v2 4/4] docs/mm: update document for split i_mmap tree
>
> and found the following issue:
> INFO: trying to register non-static key in do_one_initcall
>
> Full report is available here:
> https://ci.syzbot.org/series/a9bada61-06e7-40d5-b423-5f2d69a60209
>
> ***
>
> INFO: trying to register non-static key in do_one_initcall
>
> tree:      linux-next
> URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
> base:      14546c7bef6c1036fc82e36c1a200b0caccd339a
> arch:      amd64
> compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
> config:    https://ci.syzbot.org/builds/2f92f704-660a-4108-9172-7e620e10ce46/config
>
> acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug LTR]
> acpi PNP0A08:00: _OSC: OS now controls [PME AER PCIeCapability]
> PCI host bridge to bus 0000:00
> pci_bus 0000:00: Unknown NUMA node; performance will be reduced
> pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
> pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
> pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
> pci_bus 0000:00: root bus resource [mem 0x80000000-0xafffffff window]
> pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window]
> pci_bus 0000:00: root bus resource [mem 0x240000000-0xa3fffffff window]
> pci_bus 0000:00: root bus resource [bus 00-ff]
> pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000 conventional PCI endpoint
> pci 0000:00:01.0: [1234:1111] type 00 class 0x030000 conventional PCI endpoint
> pci 0000:00:01.0: BAR 0 [mem 0xfd000000-0xfdffffff pref]
> pci 0000:00:01.0: BAR 2 [mem 0xfebf0000-0xfebf0fff]
> pci 0000:00:01.0: ROM [mem 0xfebe0000-0xfebeffff pref]
> pci 0000:00:01.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
> pci 0000:00:02.0: [1af4:1005] type 00 class 0x00ff00 conventional PCI endpoint
> pci 0000:00:02.0: BAR 0 [io  0xc080-0xc09f]
> pci 0000:00:02.0: BAR 1 [mem 0xfebf1000-0xfebf1fff]
> pci 0000:00:02.0: BAR 4 [mem 0xfe000000-0xfe003fff 64bit pref]
> pci 0000:00:03.0: [8086:100e] type 00 class 0x020000 conventional PCI endpoint
> pci 0000:00:03.0: BAR 0 [mem 0xfebc0000-0xfebdffff]
> pci 0000:00:03.0: BAR 1 [io  0xc000-0xc03f]
> pci 0000:00:03.0: ROM [mem 0xfeb80000-0xfebbffff pref]
> pci 0000:00:1f.0: [8086:2918] type 00 class 0x060100 conventional PCI endpoint
> pci 0000:00:1f.0: quirk: [io  0x0600-0x067f] claimed by ICH6 ACPI/GPIO/TCO
> pci 0000:00:1f.2: [8086:2922] type 00 class 0x010601 conventional PCI endpoint
> pci 0000:00:1f.2: BAR 4 [io  0xc0a0-0xc0bf]
> pci 0000:00:1f.2: BAR 5 [mem 0xfebf2000-0xfebf2fff]
> pci 0000:00:1f.3: [8086:2930] type 00 class 0x0c0500 conventional PCI endpoint
> pci 0000:00:1f.3: BAR 4 [io  0x0700-0x073f]
> ACPI: PCI: Interrupt link LNKA configured for IRQ 10
> ACPI: PCI: Interrupt link LNKB configured for IRQ 10
> ACPI: PCI: Interrupt link LNKC configured for IRQ 11
> ACPI: PCI: Interrupt link LNKD configured for IRQ 11
> ACPI: PCI: Interrupt link LNKE configured for IRQ 10
> ACPI: PCI: Interrupt link LNKF configured for IRQ 10
> ACPI: PCI: Interrupt link LNKG configured for IRQ 11
> ACPI: PCI: Interrupt link LNKH configured for IRQ 11
> ACPI: PCI: Interrupt link GSIA configured for IRQ 16
> ACPI: PCI: Interrupt link GSIB configured for IRQ 17
> ACPI: PCI: Interrupt link GSIC configured for IRQ 18
> ACPI: PCI: Interrupt link GSID configured for IRQ 19
> ACPI: PCI: Interrupt link GSIE configured for IRQ 20
> ACPI: PCI: Interrupt link GSIF configured for IRQ 21
> ACPI: PCI: Interrupt link GSIG configured for IRQ 22
> ACPI: PCI: Interrupt link GSIH configured for IRQ 23
> iommu: Default domain type: Translated
> iommu: DMA domain TLB invalidation policy: lazy mode
> INFO: trying to register non-static key.
> The code is fine but needs lockdep annotation, or maybe
> you didn't initialize this object before use?
> turning off the locking correctness validator.
> CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> Call Trace:
>  <TASK>
>  dump_stack_lvl+0xe8/0x150
>  assign_lock_key+0x133/0x150
>  register_lock_class+0xcc/0x2e0
>  __lock_acquire+0xad/0x2cf0
>  lock_acquire+0x106/0x350
>  down_write+0x96/0x200
>  dma_resv_lockdep+0x39c/0x660
>  do_one_initcall+0x250/0x870
>  do_initcall_level+0x104/0x190
>  do_initcalls+0x59/0xa0
>  kernel_init_freeable+0x2a6/0x3e0
>  kernel_init+0x1d/0x1d0
>  ret_from_fork+0x514/0xb70
>  ret_from_fork_asm+0x1a/0x30
>  </TASK>
> ------------[ cut here ]------------
> DEBUG_RWSEMS_WARN_ON(sem->magic != sem): count = 0x1, magic = 0x0, owner = 0xffff888102a95940, curr 0xffff888102a95940, list not empty
> WARNING: kernel/locking/rwsem.c:1405 at up_write+0x1e2/0x410, CPU#0: swapper/0/1
> Modules linked in:
> CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> RIP: 0010:up_write+0x2b1/0x410
> Code: c0 c0 e6 cc 8b 49 c7 c2 a0 e6 cc 8b 4c 0f 44 d0 48 8b 7c 24 10 48 c7 c6 40 e8 cc 8b 48 8b 54 24 08 48 8b 0c 24 4d 89 f9 41 52 <67> 48 0f b9 3a 48 83 c4 08 e8 21 1f 0d 03 e9 b2 fd ff ff 90 0f 0b
> RSP: 0000:ffffc90000067480 EFLAGS: 00010246
> RAX: ffffffff8bcce6c0 RBX: ffffc900000677d0 RCX: 0000000000000000
> RDX: 0000000000000001 RSI: ffffffff8bcce840 RDI: ffffffff90338290
> RBP: ffffc90000067830 R08: ffff888102a95940 R09: ffff888102a95940
> R10: ffffffff8bcce6c0 R11: fffff5200000cefc R12: ffffc90000067828
> R13: dffffc0000000000 R14: 1ffff9200000cf06 R15: ffff888102a95940
> FS:  0000000000000000(0000) GS:ffff88818dc9e000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffff88823ffff000 CR3: 000000000e74a000 CR4: 00000000000006f0
> Call Trace:
>  <TASK>
>  dma_resv_lockdep+0x3a4/0x660
>  do_one_initcall+0x250/0x870
>  do_initcall_level+0x104/0x190
>  do_initcalls+0x59/0xa0
>  kernel_init_freeable+0x2a6/0x3e0
>  kernel_init+0x1d/0x1d0
>  ret_from_fork+0x514/0xb70
>  ret_from_fork_asm+0x1a/0x30
>  </TASK>
>
>
> ***
>
> If these findings have caused you to resend the series or submit a
> separate fix, please add the following tag to your commit message:
>   Tested-by: [email protected]
>
> ---
> This report is generated by a bot. It may contain errors.
> syzbot ci engineers can be reached at [email protected].
>
> To test a patch for this bug, please reply with `#syz test`
> (should be on a separate line).
>
> The patch should be attached to the email.
> Note: arguments like custom git repos and branches are not supported.
>
> The email will later be sent to:
> [[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]]
>
> If the report looks fine to you, reply with:
> #syz upstream
>
> If the report is a false positive, reply with
> #syz invalid
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/6a2b1043.db1573ee.1e58f8.0004.GAE%40google.com.