From: Dave Hansen <dave.hansen@intel.com>
To: Theodore Ts'o <tytso@mit.edu>, Dave Chinner <david@fromorbit.com>
Cc: Pengfei Xu <pengfei.xu@intel.com>,
Eric Sandeen <sandeen@sandeen.net>,
dchinner@redhat.com, djwong@kernel.org, heng.su@intel.com,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
lkp@intel.com, Aleksandr Nogikh <nogikh@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
"Li, Philip" <philip.li@intel.com>
Subject: Re: [Syzkaller & bisect] There is "soft lockup in __cleanup_mnt" in v6.4-rc3 kernel
Date: Fri, 26 May 2023 10:42:55 -0700 [thread overview]
Message-ID: <ddaf2e42-ea1e-2359-4859-310a126bd0c1@intel.com> (raw)
In-Reply-To: <20230525175542.GB821358@mit.edu>
On 5/25/23 10:55, Theodore Ts'o wrote:
> Bottom line, having various companies run their own private instances
> of syzkaller is much less useful for the upstream community.
Yes, totally agree.
> If Intel feels that it's useful to run their own instance, maybe
> there's some way you can work with Google syzkaller team so you don't
> have to do that?
I actually don't know why or when Intel started doing this. 0day in
general runs on a pretty diverse set of systems and I suspect this was
an attempt to leverage that. Philip, do you know the history here?
Pengfei, is there a list somewhere of the things that you think are
missing from Google's syzkaller instance? If not, could you make one,
please?
next prev parent reply other threads:[~2023-05-26 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 2:59 [Syzkaller & bisect] There is "soft lockup in __cleanup_mnt" in v6.4-rc3 kernel Pengfei Xu
2023-05-25 3:51 ` Eric Sandeen
2023-05-25 5:44 ` Pengfei Xu
2023-05-25 6:15 ` Dave Chinner
2023-05-25 17:55 ` Theodore Ts'o
2023-05-26 6:43 ` Pengfei Xu
2023-05-26 17:42 ` Dave Hansen [this message]
2023-05-26 20:54 ` Theodore Ts'o
2023-05-26 21:20 ` Dave Hansen
2023-05-26 4:55 ` Pengfei Xu
2023-05-25 14:17 ` Eric Sandeen
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=ddaf2e42-ea1e-2359-4859-310a126bd0c1@intel.com \
--to=dave.hansen@intel.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=dvyukov@google.com \
--cc=heng.su@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nogikh@google.com \
--cc=pengfei.xu@intel.com \
--cc=philip.li@intel.com \
--cc=sandeen@sandeen.net \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).