MIME-Version: 1.0
References: <CACDmwr_b0Z6JK2M6i6RZ4Qg3wb1uqG0NrybQ9mR2iw5QJT8XoA@mail.gmail.com>
 <CACT4Y+ZxnG0sLhqn4uw6ueAUsA4cNZJh0_6eES6C45u9jW-4Pw@mail.gmail.com>
 <CACDmwr8QH-2Kk8DU5zxJ6RLdCho2MzkA9uMJtQ+smoV-qhOq9A@mail.gmail.com> <CACT4Y+buWoqxZoUgzuYyYt6jP76GbjDoVqA7M07itQVgD60C9w@mail.gmail.com>
In-Reply-To: <CACT4Y+buWoqxZoUgzuYyYt6jP76GbjDoVqA7M07itQVgD60C9w@mail.gmail.com>
From:   Hao Sun <sunhao.th@gmail.com>
Date:   Wed, 12 Jan 2022 09:38:58 +0800
Message-ID: <CACkBjsZ5BD7_vNWmLKfHUfU7D_-0A7V1-=U78sbe+qw=XUf9ag@mail.gmail.com>
Subject: Re: KCSAN: data-race in tick_nohz_stop_tick / tick_sched_timer
To:     Dmitry Vyukov <dvyukov@google.com>
Cc:     Kaia Yadira <hypericumperforatum4444@gmail.com>,
        kvartet <xyru1999@gmail.com>,
        LKML <linux-kernel@vger.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
        syzkaller <syzkaller@googlegroups.com>,
        Ingo Molnar <mingo@kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Dmitry Vyukov <dvyukov@google.com> =E4=BA=8E2022=E5=B9=B41=E6=9C=8812=E6=97=
=A5=E5=91=A8=E4=B8=89 01:18=E5=86=99=E9=81=93=EF=BC=9A
>
> On Tue, 11 Jan 2022 at 17:56, Kaia Yadira
> <hypericumperforatum4444@gmail.com> wrote:
> >
> > I'm sorry. They are similar but I can't tell if they are the same bug,
> > so I report them individually.
>
> +CC list back
>
> I did not mean that you report similar bugs. I meant that you and
> kvartet seem to be following the same process. There are several
> complaints about the quality of reports. So I am wondering what you
> are doing/why/what's your goal.
>
> Hao Sun, you are CCed on all emails, maybe you can shed some light on thi=
s?

Hi Dmitry,

I'm on holiday and ignored these emails.
kvartet is an acquaintance of mine, I have no idea who Kaia is.
I have little knowledge of their actions. They may be new to the
kernel community and may not understand the rules in reporting bugs

Maybe we should add some `WARNING` in Syzkaller docs, e.g.,
`how_to_report_bug.md`, to tell people to polish their reports before
sending them out.
Or maybe we should just suppress all the `task-hung` and `kcsan`
reports in Syzkaller by default, enable them manually if the user
knows what they are doing.

Hao