[moderation] [mm?] WARNING: refcount bug in __set_page_owner

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b1e6ec0a0fd0 Merge tag 'docs-6.9-fixes' of git://git.lwn.n..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15bc76c5180000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c2c72b264636e25
dashboard link: https://syzkaller.appspot.com/bug?extid=aafdd7ba0170fc29cdf5
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-b1e6ec0a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d663cd8c641c/vmlinux-b1e6ec0a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/854ec343dac8/bzImage-b1e6ec0a.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+aafdd7...@syzkaller.appspotmail.com

------------[ cut here ]------------
refcount_t: saturated; leaking memory.
WARNING: CPU: 3 PID: 7222 at lib/refcount.c:22 refcount_warn_saturate+0xd4/0x210 lib/refcount.c:22
Modules linked in:

CPU: 3 PID: 7222 Comm: syz-executor.3 Not tainted 6.9.0-rc2-syzkaller-00040-gb1e6ec0a0fd0 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:refcount_warn_saturate+0xd4/0x210 lib/refcount.c:22
Code: 34 0d 0b 31 ff 89 de e8 0a 4d 12 fd 84 db 75 dc e8 81 52 12 fd c6 05 78 34 0d 0b 01 90 48 c7 c7 a0 b4 6e 8b e8 dd 25 d5 fc 90 <0f> 0b 90 90 eb bc e8 61 52 12 fd 0f b6 1d 59 34 0d 0b 31 ff 89 de
RSP: 0018:ffffc90003ede9a8 EFLAGS: 00010282

RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8150eb59
RDX: ffff88806713a440 RSI: ffffffff8150eb66 RDI: 0000000000000001
RBP: ffff88806041b0bc R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000002 R12: 00000000c0000000
R13: ffff8880532e9128 R14: ffff88805e94a580 R15: 0000000000000007
FS: 0000000000000000(0000) GS:ffff88802c500000(0063) knlGS:00000000f5f16b40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 000000c000a18000 CR3: 00000000554dc000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__refcount_add include/linux/refcount.h:192 [inline]
__refcount_inc include/linux/refcount.h:241 [inline]
refcount_inc include/linux/refcount.h:258 [inline]
inc_stack_record_count mm/page_owner.c:220 [inline]
__set_page_owner+0x62e/0x7f0 mm/page_owner.c:308
set_page_owner include/linux/page_owner.h:32 [inline]
post_alloc_hook+0x2d4/0x350 mm/page_alloc.c:1534
prep_new_page mm/page_alloc.c:1541 [inline]
get_page_from_freelist+0xa28/0x3780 mm/page_alloc.c:3317
__alloc_pages+0x22b/0x2460 mm/page_alloc.c:4575


---
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 syzk...@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