From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi2-f0.google.com (mail-oi2-f0.google.com [74.125.231.192]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 030591A6830 for ; Fri, 21 Aug 2026 16:57:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=74.125.231.192 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787331457; cv=none; b=oai+xhFCK0s4Kqd612FEWUrxk3YTbo1O/WtwyajqL9km0MIwG2rv8pgUi0Kke4JSVUzIEZX6x6JlzYww2J7SDti/WKIcqdhOXM3W1w92RL9JW0SmEiS8TvhnI1NN3SstBSC8JTdQTlNqGnvGA3LQrNSnNqEbMq6HD9OlwfgCZNw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787331457; c=relaxed/simple; bh=Ai/d0RNIhomwHBDbLYEwfCzm7H0aoIEFUxERkOmLaUw=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=E9ztcZf1UPdfrj0mJnjGkY9kkpV/fuKwW7KtBVDsXuSITmnsNDWP/rvS94843lnDYtc6c5mUHQA7FH0ezt0HcoRvBW1dgNbyU5AfEicwRTbIrpY/epS0QDp4MakrQyzDCjr+bYr8bLtD+exSM8DTSSKOx/bBNBjCKyP6qhrPjdo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=74.125.231.192 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oi2-f0.google.com with SMTP id 5614622812f47-4a49b13b745so425161b6e.0 for ; Fri, 21 Aug 2026 09:57:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1787331455; x=1787936255; h=content-type:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=Lk+KPE4O52Ld5IPp84hUSFU1LFd3FsfSNj5Q6uVv6A0=; b=W5N+w4l9ZyPIVMxkoErwz0mQQ0P9+vvnN2JssEa+vzMn/+1i8Glj9K+mdLVCuHMz0S VDYM88Jua9hiPKGTLtKjN4eGWYCrpR9neksHB3EPzvswl6q0X0oBm3pQNn5ZiaYSjorg W6nC1mL4AHXbM/g0Fqs6Y5A9SJLaHPRvrS4Wd26SDSIXwtfLkNnGVioTW57aNXT9KeW6 wBcl91uYk1Rs38bahpvfHTnIGcTgNZ22hdiXGcUFRW4Osb+AEf+SN4GMD5hRcvCVgSv/ wmzGxzAPWdRiBrBZz7RCi+H8weyeW9I5SzTq0ElPXcpyxRrLPwqMUuaTWdMu9BE17IW9 11aA== X-Forwarded-Encrypted: i=1; AHgh+Rof8eXcvT0tU6cxO/zGpMYPtp/hiWp87PzZkCdU6lm1fwQ+kN64Cyu2vh3qZrwpPjuCk0qRX2XtBYxFkYU=@vger.kernel.org X-Gm-Message-State: AOJu0YzL0ExAGaW0cwwPnDTw9ftu6HddxoxnMoeigxbPcgYa/QqLL2OH 8ZAwIxYtL0htLOzXxXGTX133dk4mAmMvIrL0pKAvrNK61xXurRYdda9OMnpykcCMHD380d3QSA6 bwGacsHH1xmXgH/Sf6LnOk8gIhI+cTzoecNF45Ro2QHQWBoP8FZ3ZS1fm9HQ= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6808:138c:b0:4b2:8d9e:de11 with SMTP id 5614622812f47-4b2ef439a80mr7776113b6e.19.1787331454770; Fri, 21 Aug 2026 09:57:34 -0700 (PDT) Date: Fri, 21 Aug 2026 09:57:34 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a88837e.ae6ddae5.3da009.0040.GAE@google.com> Subject: [syzbot] [mm?] BUG: sleeping function called from invalid context in bucket_table_alloc From: syzbot To: akpm@linux-foundation.org, apopple@nvidia.com, byungchul@sk.com, david@kernel.org, gourry@gourry.net, joshua.hahnjy@gmail.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, matthew.brost@intel.com, rakie.kim@sk.com, syzkaller-bugs@googlegroups.com, ying.huang@linux.alibaba.com, ziy@nvidia.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 7079a12d7506 Add linux-next specific files for 20260820 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=119afa25580000 kernel config: https://syzkaller.appspot.com/x/.config?x=aa9dec010c9e69a7 dashboard link: https://syzkaller.appspot.com/bug?extid=0dbf6d295b3350944f0b compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/9682e92d9ec7/disk-7079a12d.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/829f3c29b6e1/vmlinux-7079a12d.xz kernel image: https://storage.googleapis.com/syzbot-assets/2e0cdd08b0f5/bzImage-7079a12d.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+0dbf6d295b3350944f0b@syzkaller.appspotmail.com BUG: sleeping function called from invalid context at ./include/linux/sched/mm.h:322 in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 15133, name: syz.6.1501 preempt_count: 0, expected: 0 RCU nest depth: 1, expected: 0 locks held by syz.6.1501/15133: 2, last CPU#1: #0: ffffffff90250500 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline] #0: ffffffff90250500 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x767/0xc00 net/core/rtnetlink.c:7138 #1: ffffffff8ed5ca60 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline] #1: ffffffff8ed5ca60 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline] #1: ffffffff8ed5ca60 (rcu_read_lock){....}-{1:3}, at: rhashtable_insert_slow+0x1cf/0x2000 lib/rhashtable.c:683 CPU: 1 UID: 0 PID: 15133 Comm: syz.6.1501 Tainted: G L syzkaller #0 PREEMPT(full) Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 __might_resched+0x36a/0x4c0 kernel/sched/core.c:9236 might_alloc include/linux/sched/mm.h:322 [inline] slab_pre_alloc_hook mm/slub.c:4636 [inline] slab_alloc_node mm/slub.c:4974 [inline] __do_kmalloc_node mm/slub.c:5413 [inline] __kmalloc_noprof+0xef/0x720 mm/slub.c:5439 _kmalloc_noprof include/linux/slab.h:995 [inline] _kzalloc_noprof include/linux/slab.h:1312 [inline] alloc_pages_bulk_weighted_interleave mm/mempolicy.c:2682 [inline] alloc_pages_bulk_mempolicy_noprof+0xaef/0x1690 mm/mempolicy.c:2785 vm_area_alloc_pages mm/vmalloc.c:3736 [inline] __vmalloc_area_node mm/vmalloc.c:3914 [inline] __vmalloc_node_range_noprof+0xa0a/0x1540 mm/vmalloc.c:4104 __vmalloc_node_noprof mm/vmalloc.c:4165 [inline] __vmalloc_area_node mm/vmalloc.c:3890 [inline] __vmalloc_node_range_noprof+0x58b/0x1540 mm/vmalloc.c:4104 __kvmalloc_node_noprof+0x5a1/0x820 mm/slub.c:7033 bucket_table_alloc+0x75/0x380 lib/rhashtable.c:197 rhashtable_insert_rehash lib/rhashtable.c:503 [inline] rhashtable_try_insert lib/rhashtable.c:671 [inline] rhashtable_insert_slow+0x1c66/0x2000 lib/rhashtable.c:684 __rhashtable_insert_fast include/linux/rhashtable.h:789 [inline] rhashtable_lookup_insert_fast include/linux/rhashtable.h:966 [inline] vxlan_vni_add drivers/net/vxlan/vxlan_vnifilter.c:744 [inline] vxlan_vni_add_del drivers/net/vxlan/vxlan_vnifilter.c:824 [inline] vxlan_process_vni_filter drivers/net/vxlan/vxlan_vnifilter.c:891 [inline] vxlan_vnifilter_process+0x357a/0x4d40 drivers/net/vxlan/vxlan_vnifilter.c:973 rtnetlink_rcv_msg+0x7b9/0xc00 net/core/rtnetlink.c:7141 netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2556 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline] netlink_unicast+0x7bd/0x940 net/netlink/af_netlink.c:1345 netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1900 sock_sendmsg_nosec+0x13a/0x180 net/socket.c:800 __sock_sendmsg net/socket.c:815 [inline] ____sys_sendmsg+0x54e/0x850 net/socket.c:2713 ___sys_sendmsg+0x2a5/0x360 net/socket.c:2767 __sys_sendmsg net/socket.c:2799 [inline] __do_sys_sendmsg net/socket.c:2804 [inline] __se_sys_sendmsg net/socket.c:2802 [inline] __x64_sys_sendmsg+0x1b1/0x290 net/socket.c:2802 --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup