From: Eric Biggers <ebiggers@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: linux-ext4@vger.kernel.org, linux-fscrypt@vger.kernel.org
Subject: Re: [Bug report][xfstests ext4/024 crash on ext4&fscrypt] kernel BUG at lib/list_debug.c:32!
Date: Sat, 14 Mar 2026 10:04:34 -0700 [thread overview]
Message-ID: <20260314170434.GA8675@quark> (raw)
In-Reply-To: <20260314080937.pghb4aa7d4je3mhh@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Sat, Mar 14, 2026 at 04:09:37PM +0800, Zorro Lang wrote:
> [ 859.430320] KASAN: probably user-memory-access in range [0x00000004e3534580-0x00000004e3534587]
> [ 859.439808] crypto_transfer_skcipher_request_to_engine+0x1c/0x38 [crypto_engine]
> [ 859.439816] tegra_aes_crypt+0x17c/0x308 [tegra_se]
> [ 859.443046] Mem abort info:
> [ 859.450307] tegra_aes_encrypt+0x1c/0x28 [tegra_se]
> [ 859.450316] crypto_skcipher_encrypt+0xe0/0x158
> [ 859.457490] ESR = 0x000000008600000f
> [ 859.464835] fscrypt_crypt_data_unit+0x21c/0x2d0
> [ 859.472193] EC = 0x21: IABT (current EL), IL = 32 bits
> [ 859.479359] fscrypt_encrypt_pagecache_blocks+0x1e8/0x350
> [ 859.479366] ext4_bio_write_folio+0x8e4/0x1128 [ext4]
Thanks. fscrypt isn't supposed to be using the tegra crypto driver.
But that driver is actually so broken that it doesn't even set its flags
correctly, causing the crypto_skcipher API to select it anyway.
https://lore.kernel.org/linux-fscrypt/20260314165515.9678-1-ebiggers@kernel.org/
fixes this by making the driver set the correct flags.
I'm looking forward to lib/crypto/ offering all the algorithms that
fscrypt needs so that we don't have to use crypto_skcipher.
- Eric
prev parent reply other threads:[~2026-03-14 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 8:09 [Bug report][xfstests ext4/024 crash on ext4&fscrypt] kernel BUG at lib/list_debug.c:32! Zorro Lang
2026-03-14 17:04 ` Eric Biggers [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=20260314170434.GA8675@quark \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=zlang@redhat.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