lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000000000006f7e4d0620042b96@google.com>
Date: Mon, 19 Aug 2024 00:22:20 -0700
From: syzbot <syzbot+ef4ecf7b6bdc4157bfa4@...kaller.appspotmail.com>
To: akpm@...ux-foundation.org, cgroups@...r.kernel.org, hannes@...xchg.org, 
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, mhocko@...nel.org, 
	muchun.song@...ux.dev, roman.gushchin@...ux.dev, shakeel.butt@...ux.dev, 
	songmuchun@...edance.com, syzkaller-bugs@...glegroups.com, vbabka@...e.cz
Subject: [syzbot] [cgroups?] [mm?] WARNING in folio_memcg

Hello,

syzbot found the following issue on:

HEAD commit:    367b5c3d53e5 Add linux-next specific files for 20240816
git tree:       linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=11be396b980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=61ba6f3b22ee5467
dashboard link: https://syzkaller.appspot.com/bug?extid=ef4ecf7b6bdc4157bfa4
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=147469f5980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=153c5ad5980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0b1b4e3cad3c/disk-367b5c3d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5bb090f7813c/vmlinux-367b5c3d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6674cb0709b1/bzImage-367b5c3d.xz

The issue was bisected to:

commit ebadc95608dc3ee87ad4e5dc4f2c665c709bb899
Author: Muchun Song <songmuchun@...edance.com>
Date:   Wed Aug 14 09:34:15 2024 +0000

    mm: kmem: add lockdep assertion to obj_cgroup_memcg

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=170875f5980000
final oops:     https://syzkaller.appspot.com/x/report.txt?x=148875f5980000
console output: https://syzkaller.appspot.com/x/log.txt?x=108875f5980000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ef4ecf7b6bdc4157bfa4@...kaller.appspotmail.com
Fixes: ebadc95608dc ("mm: kmem: add lockdep assertion to obj_cgroup_memcg")

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5235 at include/linux/memcontrol.h:373 obj_cgroup_memcg include/linux/memcontrol.h:373 [inline]
WARNING: CPU: 1 PID: 5235 at include/linux/memcontrol.h:373 folio_memcg+0x111/0x220 include/linux/memcontrol.h:443
Modules linked in:
CPU: 1 UID: 0 PID: 5235 Comm: syz-executor874 Not tainted 6.11.0-rc3-next-20240816-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
RIP: 0010:obj_cgroup_memcg include/linux/memcontrol.h:373 [inline]
RIP: 0010:folio_memcg+0x111/0x220 include/linux/memcontrol.h:443
Code: 10 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 e2 2f f8 ff 48 8b 1b 48 89 d8 5b 41 5c 41 5e 41 5f c3 cc cc cc cc 90 <0f> 0b 90 eb ce 44 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 55 ff ff ff
RSP: 0018:ffffc9000361ef40 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff8880276c5000 RCX: 0000000080000000
RDX: 0000000000000000 RSI: ffffffff8c0adfc0 RDI: ffffffff8c60a8c0
RBP: ffffea0001dc8008 R08: ffffffff9018c5af R09: 1ffffffff20318b5
R10: dffffc0000000000 R11: fffffbfff20318b6 R12: dffffc0000000000
R13: 0000000001000108 R14: ffffea0001dc8000 R15: ffffea0001dc8030
FS:  000055556cc4f380(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000045ad50 CR3: 000000005247a000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 split_page_memcg+0x58/0x3f0 mm/memcontrol.c:3083
 vm_area_alloc_pages mm/vmalloc.c:3614 [inline]
 __vmalloc_area_node mm/vmalloc.c:3669 [inline]
 __vmalloc_node_range_noprof+0xa63/0x1400 mm/vmalloc.c:3850
 __kvmalloc_node_noprof+0x142/0x1b0 mm/util.c:681
 nf_tables_newset+0x1743/0x2ea0 net/netfilter/nf_tables_api.c:5282
 nfnetlink_rcv_batch net/netfilter/nfnetlink.c:524 [inline]
 nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:647 [inline]
 nfnetlink_rcv+0x14dc/0x2ad0 net/netfilter/nfnetlink.c:665
 netlink_unicast_kernel net/netlink/af_netlink.c:1331 [inline]
 netlink_unicast+0x7f6/0x990 net/netlink/af_netlink.c:1357
 netlink_sendmsg+0x8e4/0xcb0 net/netlink/af_netlink.c:1901
 sock_sendmsg_nosec net/socket.c:730 [inline]
 __sock_sendmsg+0x221/0x270 net/socket.c:745
 ____sys_sendmsg+0x525/0x7d0 net/socket.c:2597
 ___sys_sendmsg net/socket.c:2651 [inline]
 __sys_sendmsg+0x298/0x390 net/socket.c:2680
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff9c3845d49
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe78486ba8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007ff9c3845d49
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ff9c388f036
R13: 00007ffe78486be0 R14: 00007ffe78486c20 R15: 0000000000000000
 </TASK>


---
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@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ