All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Ard Biesheuvel <ardb@kernel.org>, Zorro Lang <zlang@redhat.com>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bug report] kernel BUG at include/linux/scatterlist.h
Date: Sun, 24 Nov 2024 17:24:12 +0100	[thread overview]
Message-ID: <Z0NTLDYJQC242GMB@wunner.de> (raw)
In-Reply-To: <Z0BCtZi2YJywGJAk@gondor.apana.org.au>

On Fri, Nov 22, 2024 at 04:37:09PM +0800, Herbert Xu wrote:
> On Fri, Nov 22, 2024 at 03:44:27PM +0800, Herbert Xu wrote:
> > 
> > This is a bug in the API/driver.  Users should not be expected to know
> > what kind of a virtual pointer is acceptable.
> > 
> > In this particular case, rsassa-pkcs1.c should be fixed to use the
> > crypto_akcipher_sync_encrypt interface.
> 
> Lukas, could you please take a look at this regression?

Hm, my impression is that this needs to be fixed in arm64's
virt_addr_valid() macro.

Let's see what arm64 maintainers have to say about it:

https://lore.kernel.org/r/90667b2b7f773308318261f96ebefd1a67133c4c.1732464395.git.lukas@wunner.de/

Thanks,

Lukas

  reply	other threads:[~2024-11-24 16:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22  4:51 [Bug report] kernel BUG at include/linux/scatterlist.h Zorro Lang
2024-11-22  6:42 ` Ard Biesheuvel
2024-11-22  7:44   ` Herbert Xu
2024-11-22  8:37     ` Herbert Xu
2024-11-24 16:24       ` Lukas Wunner [this message]
2024-11-24 23:13         ` Herbert Xu
2024-11-25 10:29           ` Lukas Wunner
2024-11-25 10:37             ` Herbert Xu
2024-11-29  7:54               ` Lukas Wunner
2024-11-29  8:03                 ` Herbert Xu
2024-11-22 19:28     ` Zorro Lang
2024-11-29  9:53 ` [PATCH] crypto: rsassa-pkcs1 - Copy source data for SG list Herbert Xu
2024-11-30  8:41   ` Lukas Wunner
2024-12-03  7:57     ` 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=Z0NTLDYJQC242GMB@wunner.de \
    --to=lukas@wunner.de \
    --cc=ardb@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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 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.