From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Eric Biggers <ebiggers@kernel.org>,
syzbot <syzbot+7add5c56bc2a14145d20@syzkaller.appspotmail.com>,
davem@davemloft.net, herbert@gondor.apana.org.au,
jaegeuk@kernel.org, linux-crypto@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, Neal Gompa <neal@gompa.dev>
Subject: Re: [syzbot] [ext4] [fscrypt] KMSAN: uninit-value in fscrypt_crypt_data_unit
Date: Thu, 11 Dec 2025 21:16:01 -0800 [thread overview]
Message-ID: <aTulEbvkOf0Tsztf@infradead.org> (raw)
In-Reply-To: <20251211185215.GM94594@frogsfrogsfrogs>
On Thu, Dec 11, 2025 at 10:52:15AM -0800, Darrick J. Wong wrote:
> Hey waitaminute, are you planning to withdraw fscrypt from ext4?
No really, just forcing to use one of the two current implementations
of the I/O path.
> (I might just not know enough about what blk-crypto is)
block/blk-crypto*
prev parent reply other threads:[~2025-12-12 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <68ee633c.050a0220.1186a4.002a.GAE@google.com>
2025-10-14 14:58 ` [syzbot] [crypto?] KMSAN: uninit-value in fscrypt_crypt_data_unit Aleksandr Nogikh
2025-12-09 11:08 ` [syzbot] [ext4] [fscrypt] " syzbot
2025-12-10 2:22 ` Eric Biggers
2025-12-11 18:52 ` Darrick J. Wong
2025-12-11 19:45 ` Eric Biggers
2025-12-11 22:19 ` Darrick J. Wong
2025-12-12 5:16 ` Christoph Hellwig [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=aTulEbvkOf0Tsztf@infradead.org \
--to=hch@infradead.org \
--cc=davem@davemloft.net \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jaegeuk@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neal@gompa.dev \
--cc=syzbot+7add5c56bc2a14145d20@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--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