From: syzbot ci <syzbot+cif7d88c05182adc80@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: Mon, 20 Jul 2026 12:54:30 -0700 [thread overview]
Message-ID: <6a5e7cf6.f1649fcc.2a4208.0575.GAE@google.com> (raw)
In-Reply-To: <20260720150104.2634801-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/20260720150104.2634801-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/33930a89-bb2a-4c5a-b6c5-d45829d5c94c
***
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-20 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 15:01 [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-20 19:54 ` syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-20 12:41 Alexander Potapenko
2026-07-21 14:51 ` [syzbot ci] " syzbot ci
2026-07-21 14:51 ` 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=6a5e7cf6.f1649fcc.2a4208.0575.GAE@google.com \
--to=syzbot+cif7d88c05182adc80@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 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.