From: David Howells <dhowells@redhat.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: dhowells@redhat.com, "Herbert Xu" <herbert@gondor.apana.org.au>,
"Paolo Abeni" <pabeni@redhat.com>,
netdev@vger.kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Ondrej Mosnáček" <omosnacek@gmail.com>,
"Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>
Subject: Re: Another regression in the af_alg series (s390x-specific)
Date: Wed, 26 Jul 2023 11:43:02 +0100 [thread overview]
Message-ID: <20079.1690368182@warthog.procyon.org.uk> (raw)
In-Reply-To: <31ddce1d-6014-bf9f-95da-97deb3240606@leemhuis.info>
"Linux regression tracking (Thorsten Leemhuis)" wrote:
> What's the status wrt to this regression (caused by c1abe6f570af from
> David)? It looks like there never was a real reply and the regression
> still is unresolved. But maybe I missed something, which can easily
> happen in my position.
I was on holiday when the regression was posted. This week I've been working
through various things raised during the last couple of weeks whilst fighting
an intermittent apparent bug on my desktop kernel somewhere in ext4, the mm
subsys, md or dm-crypt.
I'll get round to it, but I'll I don't have s390x h/w immediately to hand.
David
next prev parent reply other threads:[~2023-07-26 10:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 8:03 Another regression in the af_alg series (s390x-specific) Ondrej Mosnáček
2023-07-14 2:10 ` Bagas Sanjaya
2023-07-26 10:15 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-26 10:43 ` David Howells [this message]
2023-07-26 11:02 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-26 15:38 ` David Howells
2023-07-26 19:20 ` Sven Schnelle
2023-07-26 21:53 ` [PATCH] crypto: Fix missing initialisation affecting gcm-aes-s390 David Howells
2023-07-27 5:55 ` Sven Schnelle
2023-07-31 13:35 ` Ondrej Mosnáček
2023-07-31 14:18 ` Ard Biesheuvel
2023-08-04 9:11 ` Herbert Xu
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=20079.1690368182@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=omosnacek@gmail.com \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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).