From: syzbot <syzbot+05d673e83ec640f0ced9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [trace?] BUG: corrupted list in ring_buffer_subbuf_order_set
Date: Fri, 06 Jun 2025 05:24:13 -0700 [thread overview]
Message-ID: <6842dded.a00a0220.29ac89.003e.GAE@google.com> (raw)
In-Reply-To: <684298d8.050a0220.2461cf.0039.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [trace?] BUG: corrupted list in ring_buffer_subbuf_order_set
Author: hdanton@sina.com
> Date: Fri, 06 Jun 2025 00:29:28 -0700
> syzbot found the following issue on:
>
> HEAD commit: cd2e103d57e5 Merge tag 'hardening-v6.16-rc1-fix1-take2' of..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17f0680c580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=d97b092471e3ab82
> dashboard link: https://syzkaller.appspot.com/bug?extid=05d673e83ec640f0ced9
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1795b970580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13b281d4580000
#syz test
--- x/kernel/trace/ring_buffer.c
+++ y/kernel/trace/ring_buffer.c
@@ -6909,7 +6909,6 @@ error:
buffer->subbuf_size = old_size;
atomic_dec(&buffer->record_disabled);
- mutex_unlock(&buffer->mutex);
for_each_buffer_cpu(buffer, cpu) {
cpu_buffer = buffer->buffers[cpu];
@@ -6922,6 +6921,7 @@ error:
free_buffer_page(bpage);
}
}
+ mutex_unlock(&buffer->mutex);
return err;
}
--
prev parent reply other threads:[~2025-06-06 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 7:29 syzbot
2025-06-06 9:00 ` [syzbot] #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git e271ed52b344ac02d4581286961d0c40acc54c03 syzbot
2025-06-06 12:24 ` syzbot [this message]
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=6842dded.a00a0220.29ac89.003e.GAE@google.com \
--to=syzbot+05d673e83ec640f0ced9@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®