From: syzbot <syzbot+23a256029191772c2f02@syzkaller.appspotmail.com>
To: elver@google.com, frederic@kernel.org,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, naresh.kamboju@linaro.org, paulmck@kernel.org,
peterz@infradead.org,
syzkaller-upstream-moderation@googlegroups.com,
tglx@linutronix.de, will@kernel.org
Subject: Re: KCSAN: data-race in tick_nohz_stop_tick / tick_nohz_stop_tick (2)
Date: Thu, 09 Mar 2023 01:15:39 -0800 [thread overview]
Message-ID: <0000000000009a1f7c05f6741666@google.com> (raw)
In-Reply-To: <000000000000fa5a2205b4c33093@google.com>
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
parent reply other threads:[~2023-03-09 9:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000fa5a2205b4c33093@google.com>]
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=0000000000009a1f7c05f6741666@google.com \
--to=syzbot+23a256029191772c2f02@syzkaller.appspotmail.com \
--cc=elver@google.com \
--cc=frederic@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-upstream-moderation@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=will@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