From: syzbot ci <syzbot+ci410bbf8b6339678e@syzkaller.appspotmail.com>
To: glider@google.com, syzbot@lists.linux.dev
Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot ci] Re: kcov: fix data corruption and race conditions on PREEMPT_RT by moving saved remote state to task_struct (v7)
Date: Tue, 21 Jul 2026 07:51:43 -0700 [thread overview]
Message-ID: <6a5f877f.33ea6125.251e5.0003.GAE@google.com> (raw)
In-Reply-To: <20260720124126.1977559-1-glider@google.com>
syzbot ci has tested the following series
[v7] kcov: fix data corruption and race conditions on PREEMPT_RT by moving saved remote state to task_struct (v7)
https://lore.kernel.org/all/20260720124126.1977559-1-glider@google.com
* [PATCH v7] kcov: fix data corruption and race conditions on PREEMPT_RT by moving saved remote state to task_struct (v7)
and found no issues.
Full report is available here:
https://ci.syzbot.org/series/28387885-cfb9-4942-8b74-4b9f310211ad
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
next prev parent reply other threads:[~2026-07-21 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 12:41 [PATCH v7] kcov: fix data corruption and race conditions on PREEMPT_RT by moving saved remote state to task_struct (v7) Alexander Potapenko
2026-07-21 14:51 ` [syzbot ci] " syzbot ci
2026-07-21 14:51 ` syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-20 15:01 [PATCH v7] " Alexander Potapenko
2026-07-20 19:54 ` [syzbot ci] " syzbot ci
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=6a5f877f.33ea6125.251e5.0003.GAE@google.com \
--to=syzbot+ci410bbf8b6339678e@syzkaller.appspotmail.com \
--cc=glider@google.com \
--cc=syzbot@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox