mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "Jason A . Donenfeld" <Jason@zx2c4.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/crypto: tests: Annotate worker to be on stack
Date: Thu, 24 Jul 2025 11:29:58 -0700	[thread overview]
Message-ID: <b4bdb833-5fdd-48e6-989a-1d4059e9cd81@roeck-us.net> (raw)
In-Reply-To: <20250724173657.GB26800@sol>

On Thu, Jul 24, 2025 at 10:36:57AM -0700, Eric Biggers wrote:
> > 
> > Configuration file and decoded stacktrace are at
> > 
> > http://server.roeck-us.net/qemu/crypto/
> > 
> > Please let me know if you need anything else.
> 
> Thanks!  It seems the kconfig is actually unrelated; what matters is how
> the kernel is being run.  It reproduces only in QEMU with KVM disabled.
> It doesn't reproduce with KVM enabled or on bare metal.
> 
> The crashed instruction is 'vinserti128 $0x1,0x30(%rsi),%ymm8,%ymm8'.
> 
> I think it's a QEMU bug: its implementation of vinserti128 reads 32
> bytes from memory instead of 16.  I'll report it to qemu-devel once I
> have a bit more information.
> 
> It will be the second QEMU bug found by the crypto tests this month....
> https://lore.kernel.org/r/20250710052824.GA608727@sol/ was the first.
> 

Oh well :-(. Thanks for tracking it down. I'll disable this test
for the time being for x86 tests. I'll let you know if I see it
or something similar for other architectures.

Thanks,
Guenter

      reply	other threads:[~2025-07-24 18:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21 23:19 Guenter Roeck
2025-07-22  0:05 ` Ard Biesheuvel
2025-07-22  3:16 ` Eric Biggers
2025-07-24 14:19   ` Guenter Roeck
2025-07-24 16:26     ` Eric Biggers
2025-07-24 17:03       ` Guenter Roeck
2025-07-24 17:36         ` Eric Biggers
2025-07-24 18:29           ` Guenter Roeck [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=b4bdb833-5fdd-48e6-989a-1d4059e9cd81@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®