public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a6d6b8fffa294705dbd8@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] Re: KMSAN: uninit-value in __crc32c_le_base (3)
Date: Sun, 17 Mar 2024 16:21:52 -0700	[thread overview]
Message-ID: <000000000000954b4e0613e381dc@google.com> (raw)
In-Reply-To: <000000000000f66a3005fa578223@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: KMSAN: uninit-value in __crc32c_le_base (3)
Author: david@fromorbit.com

On Mon, Mar 18, 2024 at 09:52:35AM +1100, Dave Chinner wrote:
> This XFS issue was fixed in 6.8 by commit 0573676fdde7. I'm closing
> this so the future reproduction of this same error signatiure on
> btrfs and other filesystems trigger a new issue to be reported..

#syz fix: xfs: initialise di_crc in xfs_log_dinode
-- 
Dave Chinner
david@fromorbit.com

      parent reply	other threads:[~2024-03-17 23:21 UTC|newest]

Thread overview: 14+ 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
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 [this message]

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=000000000000954b4e0613e381dc@google.com \
    --to=syzbot+a6d6b8fffa294705dbd8@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox