All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f71493d41adfafb97a1a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] kernel BUG in __free_frozen_pages
Date: Sun, 16 Aug 2026 05:47:37 -0700	[thread overview]
Message-ID: <6a81b169.dbb3a75c.20434b.002f.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    f5bbbfec59b4 Merge tag 'probes-fixes-v7.2-rc7' of git://gi..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=106a5079580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c44651ea7dd2f307
dashboard link: https://syzkaller.appspot.com/bug?extid=f71493d41adfafb97a1a
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=166c4c79580000

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

 vfs_read+0x1e4/0xb40 fs/read_write.c:572
 ksys_read+0x12a/0x250 fs/read_write.c:716
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
------------[ cut here ]------------
kernel BUG at mm/page_alloc.c:1361!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 1 UID: 0 PID: 6026 Comm: syz-executor398 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__free_pages_prepare mm/page_alloc.c:1361 [inline]
RIP: 0010:__free_frozen_pages+0xcd3/0x1090 mm/page_alloc.c:2950
Code: 48 c7 c6 c0 8c e1 8b 4c 89 f7 e8 68 eb ef ff 90 0f 0b 85 db 0f 84 6e f5 ff ff 48 c7 c6 20 8d e1 8b 4c 89 ff e8 4e eb ef ff 90 <0f> 0b 48 c7 44 24 20 01 00 00 00 48 c7 44 24 28 01 00 00 00 e9 d5
RSP: 0018:ffffc900030f7af8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffc900030f79dc
RDX: ffff88802b830000 RSI: ffffffff825c2128 RDI: ffff88802b8304c4
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
R13: ffffea00009afb88 R14: ffffea00009afb80 R15: ffffea00009afb80
FS:  00007f34a2fe96c0(0000) GS:ffff8880d5eec000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f34a27e6208 CR3: 0000000027e6e000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 free_buffer_page kernel/trace/ring_buffer.c:398 [inline]
 ring_buffer_subbuf_order_set+0x1325/0x18e0 kernel/trace/ring_buffer.c:7444
 buffer_subbuf_size_write+0x182/0x280 kernel/trace/trace.c:8221
 vfs_write+0x2aa/0x1050 fs/read_write.c:685
 ksys_pwrite64 fs/read_write.c:794 [inline]
 __do_sys_pwrite64 fs/read_write.c:802 [inline]
 __se_sys_pwrite64 fs/read_write.c:799 [inline]
 __x64_sys_pwrite64+0x1eb/0x250 fs/read_write.c:799
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f34a303ec1e
Code: 08 0f 85 f5 e2 ff ff 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> 90 41 57 41 56 4d 89 c6 41 55 4d 89 cd 41 54 55 53 48 83 ec 08
RSP: 002b:00007f34a2fe9198 EFLAGS: 00000246 ORIG_RAX: 0000000000000012
RAX: ffffffffffffffda RBX: 00007f34a2fe96c0 RCX: 00007f34a303ec1e
RDX: 0000000000000002 RSI: 00007f34a308a02b RDI: 0000000000000003
RBP: 00007f34a308a028 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: ffffffffffffffd0
R13: 0000000000000000 R14: 00007ffcb8a85c30 R15: 00007ffcb8a85d18
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__free_pages_prepare mm/page_alloc.c:1361 [inline]
RIP: 0010:__free_frozen_pages+0xcd3/0x1090 mm/page_alloc.c:2950
Code: 48 c7 c6 c0 8c e1 8b 4c 89 f7 e8 68 eb ef ff 90 0f 0b 85 db 0f 84 6e f5 ff ff 48 c7 c6 20 8d e1 8b 4c 89 ff e8 4e eb ef ff 90 <0f> 0b 48 c7 44 24 20 01 00 00 00 48 c7 44 24 28 01 00 00 00 e9 d5
RSP: 0018:ffffc900030f7af8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffc900030f79dc
RDX: ffff88802b830000 RSI: ffffffff825c2128 RDI: ffff88802b8304c4
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
R13: ffffea00009afb88 R14: ffffea00009afb80 R15: ffffea00009afb80
FS:  00007f34a2fe96c0(0000) GS:ffff8880d5eec000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f34a27e6208 CR3: 0000000027e6e000 CR4: 0000000000352ef0


---
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 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

                 reply	other threads:[~2026-08-16 12:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a81b169.dbb3a75c.20434b.002f.GAE@google.com \
    --to=syzbot+f71493d41adfafb97a1a@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.