linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Alexandre Messier <alex@me.ssier.org>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	Andrew.Cooper3@citrix.com, mingo@redhat.com,
	dave.hansen@linux.intel.com, x86@kernel.org,
	regressions@lists.linux.dev
Subject: Re: [REGRESSION] Unable to unlock encrypted disk starting with kernel 5.19-rc1+
Date: Tue, 28 Jun 2022 11:20:03 +0200	[thread overview]
Message-ID: <YrrHwxtD2dpts7PF@zn.tnic> (raw)
In-Reply-To: <6025678c-e94a-6966-e298-82fad658a889@me.ssier.org>

On Tue, Jun 28, 2022 at 01:13:30AM -0400, Alexandre Messier wrote:
> Please let me know if more information is needed, or if some tests are needed
> to be run.

Yeah, pls send /proc/cpuinfo and full dmesg - privately is fine too.

Also, it would be lovely if I were able to reproduce this on a machine
here but mine doesn't have a crypto rootfs.

Perhaps you can point me to the exact instructions you're running to
decrypt your rootfs and I can try to create a usb crypto disk and try to
reproduce it with them...

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2022-06-28  9:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28  5:13 [REGRESSION] Unable to unlock encrypted disk starting with kernel 5.19-rc1+ Alexandre Messier
2022-06-28  9:20 ` Borislav Petkov [this message]
2022-06-28 16:52   ` Dave Hansen
2022-06-28 21:31   ` Alexandre Messier
2022-06-28 22:59     ` Thomas Gleixner
2022-06-28 23:24       ` Alexandre Messier
2022-06-29 15:24         ` Dave Hansen

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=YrrHwxtD2dpts7PF@zn.tnic \
    --to=bp@alien8.de \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=alex@me.ssier.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).