All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Nixdorf <mixi@shadowice.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>, Mark Brown <broonie@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [BUG] dm-crypt broken after 2632e2521769 ("arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD")
Date: Thu, 16 May 2024 19:34:44 +0200	[thread overview]
Message-ID: <ZkZDtJXWrgshJJn6@nailbender> (raw)
In-Reply-To: <cb8822182231850108fa43e0446a4c7f@kernel.org>

On 2024-05-16 17:22, Johannes Nixdorf wrote:
> I noticed frequent FS corruption on my M1 MacBook running Linux after
> the Asahi Linux Kernel was updated to 6.9.x (from 6.6.x).

A small correction: I noticed it at the jump to 6.8.x. The bisect started
with 6.8.9 as the first bad commit.

To make sure I now tested it again with the current master at ea5f6ad9ad96. The
bug still reproduces with it.

> This was reproduced with fio's examples/basic-verify.fio (1GB of writing
> was not reliably, 10GB triggered it reliably) on vanilla kernels and
> happens on any storage backend behind dm-crypt.

I reproduced it with the following script in the initramfs since I did not
have a working keyboard with vanilla kernels:

 fallocate -l $((1024 * 1024 * 1024)) disk.img
 losetup -f disk.img
 echo test | cryptsetup luksFormat -q /dev/loop0
 echo test | cryptsetup open /dev/loop0 test
 fio /verify.fio

And the following verify.fio:

 [write-and-verify]
 loops=10
 rw=randwrite
 bs=4k
 direct=1
 ioengine=libaio
 iodepth=16
 verify=crc32c
 filename=/dev/mapper/test

Regards,
Johannes Nixdorf

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-05-16 17:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 16:22 [BUG] dm-crypt broken after 2632e2521769 ("arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD") Johannes Nixdorf
2024-05-16 16:25 ` Marc Zyngier
2024-05-16 17:16   ` Dave Martin
2024-05-16 17:17   ` Ard Biesheuvel
2024-05-17 11:37     ` Will Deacon
2024-05-17 11:40     ` Mark Brown
2024-05-17 11:57     ` Mark Rutland
2024-05-16 17:34   ` Johannes Nixdorf [this message]
2024-05-21  6:22   ` Johannes Nixdorf
2024-05-21  8:55     ` Ard Biesheuvel
2024-05-21 12:56       ` Mark Brown
2024-05-21 18:34     ` Will Deacon
2024-05-21 18:44       ` Mark Brown
2024-05-21 18:57         ` Ard Biesheuvel
2024-05-21 20:06       ` Janne Grunau
2024-05-21 20:06         ` Janne Grunau
2024-05-21 20:21         ` Mark Brown
2024-05-21 20:21           ` Mark Brown
2024-05-21 21:23           ` Janne Grunau
2024-05-21 21:23             ` Janne Grunau
2024-05-22 11:14             ` Mark Brown
2024-05-22 11:14               ` Mark Brown

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=ZkZDtJXWrgshJJn6@nailbender \
    --to=mixi@shadowice.org \
    --cc=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    /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.