From: Dave Chinner <david@fromorbit.com>
To: Alexander Potapenko <glider@google.com>
Cc: Dave Chinner <dchinner@redhat.com>,
syzbot+a6d6b8fffa294705dbd8@syzkaller.appspotmail.com,
hch@lst.de, davem@davemloft.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, linux-xfs@vger.kernel.org
Subject: Re: [syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (3)
Date: Fri, 15 Dec 2023 08:39:18 +1100 [thread overview]
Message-ID: <ZXt2BklghFSmDbhg@dread.disaster.area> (raw)
In-Reply-To: <CAG_fn=UukAf5sPrwqQtmL7-_dyUs3neBpa75JAaeACUzXsHwOA@mail.gmail.com>
On Thu, Dec 14, 2023 at 03:55:00PM +0100, Alexander Potapenko wrote:
> On Wed, Dec 13, 2023 at 10:58 PM 'Dave Chinner' via syzkaller-bugs
> <syzkaller-bugs@googlegroups.com> wrote:
> >
> > On Thu, Dec 14, 2023 at 08:16:07AM +1100, Dave Chinner wrote:
> > > [cc linux-xfs@vger.kernel.org because that's where all questions
> > > about XFS stuff should be directed, not to random individual
> > > developers. ]
> > >
> > > On Wed, Dec 13, 2023 at 11:49:50AM +0100, Alexander Potapenko wrote:
> > > > Hi Christoph, Dave,
> > > >
> > > > The repro provided by Xingwei indeed works.
> >
> > Can you please test the patch below?
>
> It fixed the problem for me, feel free to add:
>
> Tested-by: Alexander Potapenko <glider@google.com>
Thanks.
> As for the time needed to detect the bug, note that kmemcheck was
> never used together with syzkaller, so it couldn't have the chance to
> find it.
>
> KMSAN found this bug in April
> (https://syzkaller.appspot.com/bug?extid=a6d6b8fffa294705dbd8),
KMSAN has been used for quite a long time with syzbot, however,
and it's supposed to find these problems, too. Yet it's only been
finding this for 6 months?
> only
> half a year after we started mounting XFS images on syzbot.
Really? Where did you get that from? syzbot has been exercising XFS
filesystems since 2017 - the bug reports to the XFS list go back at
least that far.
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2023-12-14 21:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 20:50 [syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (3) syzbot
2023-12-13 10:49 ` Alexander Potapenko
2023-12-13 10:50 ` Alexander Potapenko
2023-12-13 21:16 ` Dave Chinner
2023-12-13 21:58 ` Dave Chinner
2023-12-14 14:55 ` Alexander Potapenko
2023-12-14 21:39 ` Dave Chinner [this message]
2023-12-15 14:41 ` Alexander Potapenko
2023-12-15 21:59 ` Dave Chinner
2023-12-18 10:22 ` Aleksandr Nogikh
2023-12-19 12:41 ` Dave Chinner
2023-12-19 13:56 ` Alexander Potapenko
2023-12-19 23:33 ` Dave Chinner
2024-03-17 23:21 ` [syzbot] " syzbot
2023-12-04 12:56 [syzbot] [crypto?] " xingwei lee
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=ZXt2BklghFSmDbhg@dread.disaster.area \
--to=david@fromorbit.com \
--cc=davem@davemloft.net \
--cc=dchinner@redhat.com \
--cc=glider@google.com \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzbot+a6d6b8fffa294705dbd8@syzkaller.appspotmail.com \
--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.