Re: [PATCH 1/3] powerpc/pseries: Correct secvar format representation for static key management

On 4/30/25 5:03 AM, Srish Srinivasan wrote: On a PLPKS enabled PowerVM LPAR, the secvar format property for static key management is misrepresented as "ibm,plpks-sb-unknown", creating reason for confusion. Static key management mode uses fixed, built-in keys. Dynamic key management mode allows

Re: [PATCH 3/3] integrity/platform_certs: Allow loading of keys in static key management mode

On 4/30/25 5:03 AM, Srish Srinivasan wrote: On PLPKS enabled PowerVM LPAR, there is no provision to load signed third-party kernel modules when the key management mode is static. This is because keys from secure boot secvars are only loaded when the key management mode is dynamic. Allow loadin

Re: segmentation fault when stepping multi-threaded application

Le 28/04/2025 à 13:16, Tomas Alvarez Vanoli a écrit : [Vous ne recevez pas souvent de courriers de tomas.alvarez-van...@hitachienergy.com. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ] Hello, I am writing because I have a segmentation fault when rem

Re: [PATCH] ASoC: fsl: fsl_qmc_audio: Reset audio data pointers on TRIGGER_START event

Le 30/04/2025 à 02:23, Mark Brown a écrit : On Mon, Apr 28, 2025 at 11:20:42AM +0200, Christophe Leroy wrote: Le 10/04/2025 à 15:47, Mark Brown a écrit : Would it be possible to get this patch into one of the v6.15 rc as it is a bug fix ? It appears to be queued as a fix, could you be mo

Re: [PATCH v2 0/6] powerpc: use lock guards for mutex Set 1

* Shrikanth Hegde [2025-03-14 17:14:56]: > This is an effort to make the code simpler by making use of lock > guards which were introduced in [1], which works by using __cleanup > attributes. More details in v1 cover letter > > This series aims mainly at simplifying code around mutex with goto

Re: [PATCH] Documentation: ioctl-number: Extend "Include File" column width

On Wed, Apr 30, 2025 at 06:38:27PM +0530, Venkat Rao Bagalkote wrote: > > Note: There is other patch [1] > > which has a different approach to fix the reported issue. Then let the maint

Re: [PATCH v2 6/6] powerpc: sysdev: use lock guard for mutex

* Shrikanth Hegde [2025-03-14 17:15:02]: > use guard(mutex) for scope based resource management of mutex > This would make the code simpler and easier to maintain. > > More details on lock guards can be found at > https://lore.kernel.org/all/20230612093537.614161...@infradead.org/T/#u > > Signe

Re: [PATCH] Documentation: Fix description format for powerpc RTAS ioctls

On 30/04/25 7:58 am, Haren Myneni wrote: Fix the description format for the following build warnings: "Documentation/userspace-api/ioctl/ioctl-number.rst:369: ERROR: Malformed table. Text in column margin in table line 301. 0xB2 03-05 arch/powerpc/include/uapi/asm/papr-indices.h powerpc/pser

Re: [PATCH] powerpc/pseries: Include linux/types.h in papr-platform-dump.h

On 30/04/25 2:44 am, Haren Myneni wrote: Fix the following build warning: usr/include/asm/papr-platform-dump.h:12: found __[us]{8,16,32,64} type without #include Fixes: 8aa9efc0be66 ("powerpc/pseries: Add papr-platform-dump character driver for dump retrieval") Closes: https://lore.kernel.

Re: [PATCH] Documentation: Fix description format for powerpc RTAS ioctls

On Tue, Apr 29, 2025 at 07:28:47PM -0700, Haren Myneni wrote: > Fix the description format for the following build warnings: > > "Documentation/userspace-api/ioctl/ioctl-number.rst:369: > ERROR: Malformed table. Text in column margin in table line 301. > > 0xB2 03-05 arch/powerpc/include/uapi/as

RE: segmentation fault when stepping multi-threaded application

> Am I missing something ? Apologies for that, I made a mistake. The board is based off T1040, with e5500. Previous report affected two of our products, the one from the previous report and the one I am reporting now. Since I wrote the email I was able to also reproduce a crash when stepping 3

Re: [PATCH] Documentation: ioctl-number: Extend "Include File" column width

On 29/04/25 6:35 pm, Bagas Sanjaya wrote: Stephen Rothwell reports htmldocs warning when merging powerpc tree for linux-next: Documentation/userspace-api/ioctl/ioctl-number.rst:369: ERROR: Malformed table. Text in column margin in table line 301. = =

Re: [PATCH 2/3] powerpc/secvar: Expose secvars relevant to the key management mode

On 4/30/25 5:03 AM, Srish Srinivasan wrote: The PLPKS enabled PowerVM LPAR sysfs exposes all of the secure boot secvars irrespective of the key management mode. The PowerVM LPAR supports static and dynamic key management for secure boot. The key management option can be updated in the manageme

Re: [PATCH v3 1/4] tpm: add buf_size parameter in the .send callback

On Mon, Apr 14, 2025 at 04:56:50PM +0200, Stefano Garzarella wrote: > From: Stefano Garzarella > > In preparation for the next commit, add a new `buf_size` parameter to > the `.send` callback in `tpm_class_ops` which contains the entire buffer > size. In this patch it is pretty much ignored by al

Re: [PATCH v3 2/4] tpm: support devices with synchronous send()

On Mon, Apr 14, 2025 at 04:56:51PM +0200, Stefano Garzarella wrote: > From: Stefano Garzarella > > Some devices do not support interrupts and provide a single synchronous > operation to send the command and receive the response on the same buffer. > > Currently, these types of drivers must use a

Re: [PATCH v3 3/4] tpm/tpm_ftpm_tee: support TPM_CHIP_FLAG_SYNC

On Mon, Apr 14, 2025 at 04:56:52PM +0200, Stefano Garzarella wrote: > From: Stefano Garzarella > > This driver does not support interrupts, and receiving the response is > synchronous with sending the command. > > So we can set TPM_CHIP_FLAG_SYNC to support synchronous send() and "Enable synchr

Re: [PATCH v3 4/4] tpm/tpm_svsm: support TPM_CHIP_FLAG_SYNC

On Mon, Apr 14, 2025 at 04:56:53PM +0200, Stefano Garzarella wrote: > From: Stefano Garzarella > > This driver does not support interrupts, and receiving the response is > synchronous with sending the command. > > So we can set TPM_CHIP_FLAG_SYNC to support synchronous send() and > return respon

Re: [PATCH 2/5] powerpc: 83xx/gpio: use new line value setter callbacks

On Wed, Apr 30, 2025 at 7:33 PM Christophe Leroy wrote: > > > > Le 08/04/2025 à 09:21, Bartosz Golaszewski a écrit : > > From: Bartosz Golaszewski > > > > struct gpio_chip now has callbacks for setting line values that return > > an integer, allowing to indicate failures. Convert the driver to us

Re: [PATCH 00/12] crypto: sha256 - Use partial block API

[Added back Cc's that were dropped] On Wed, Apr 30, 2025 at 02:06:15PM +0800, Herbert Xu wrote: > This is based on > > https://patchwork.kernel.org/project/linux-crypto/list/?series=957785 I'm assuming that you mean that with your diff https://lore.kernel.org/r/abgdiv17ztqnh...@gondor.apan

Re: [PATCH 2/5] powerpc: 83xx/gpio: use new line value setter callbacks

On Wed, Apr 30, 2025 at 7:47 PM Christophe Leroy wrote: > > > > Le 30/04/2025 à 19:37, Bartosz Golaszewski a écrit : > > On Wed, Apr 30, 2025 at 7:33 PM Christophe Leroy > > wrote: > >> > >> > >> > >> Le 08/04/2025 à 09:21, Bartosz Golaszewski a écrit : > >>> From: Bartosz Golaszewski > >>> > >>

Re: [PATCH 5/5] powerpc: 8xx/gpio: use new line value setter callbacks

Le 08/04/2025 à 09:21, Bartosz Golaszewski a écrit : From: Bartosz Golaszewski struct gpio_chip now has callbacks for setting line values that return an integer, allowing to indicate failures. Convert the driver to using them. Signed-off-by: Bartosz Golaszewski Reviewed-by: Christophe Le

Re: [PATCH 2/5] powerpc: 83xx/gpio: use new line value setter callbacks

Le 08/04/2025 à 09:21, Bartosz Golaszewski a écrit : From: Bartosz Golaszewski struct gpio_chip now has callbacks for setting line values that return an integer, allowing to indicate failures. Convert the driver to using them. Signed-off-by: Bartosz Golaszewski --- arch/powerpc/platforms

Re: segmentation fault when stepping multi-threaded application

Le 30/04/2025 à 15:18, Tomas Alvarez Vanoli a écrit : [Vous ne recevez pas souvent de courriers de tomas.alvarez-van...@hitachienergy.com. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ] Am I missing something ? Apologies for that, I made a mistake

[PATCH 1/3] powerpc/pseries: Correct secvar format representation for static key management

On a PLPKS enabled PowerVM LPAR, the secvar format property for static key management is misrepresented as "ibm,plpks-sb-unknown", creating reason for confusion. Static key management mode uses fixed, built-in keys. Dynamic key management mode allows keys to be updated in production to handle secu

[PATCH 0/3] Enhancements to the secvar interface in static key management mode

The PLPKS enabled Power LPAR sysfs exposes all of the secure boot secure variables irrespective of the key management mode. There is support for both static and dynamic key management and the key management mode can be updated using the management console. The user can modify the secure boot secvar

[PATCH 2/3] powerpc/secvar: Expose secvars relevant to the key management mode

The PLPKS enabled PowerVM LPAR sysfs exposes all of the secure boot secvars irrespective of the key management mode. The PowerVM LPAR supports static and dynamic key management for secure boot. The key management option can be updated in the management console. Only in the dynamic key mode can the

[PATCH 3/3] integrity/platform_certs: Allow loading of keys in static key management mode

On PLPKS enabled PowerVM LPAR, there is no provision to load signed third-party kernel modules when the key management mode is static. This is because keys from secure boot secvars are only loaded when the key management mode is dynamic. Allow loading of the trustedcadb and moduledb keys even in t

[PATCH] powerpc/pseries/dlpar: Search DRC index from ibm,drc-indexes for IO add

IO hotplug add event is handled in the user space with drmgr tool. After the device is enabled, the user space uses /sys/kerne/dlpar interface with “dt add index ” to update the device tree. The kernel interface (dlpar_hp_dt_add()) finds the parent node for the specified ‘drc_index’ from ibm,drc-in

Re: [PATCH 00/12] crypto: sha256 - Use partial block API

On Wed, Apr 30, 2025 at 07:26:17PM -0700, Eric Biggers wrote: > > Interesting approach -- pushing out misguided optimizations without data, then > demanding data for them to be reverted. It's obviously worse for > len % 64 < 56 for the reason I gave, so this is a waste of time IMO. But > since >

Re: [PATCH 3/5] powerpc: 44x/gpio: use new line value setter callbacks

Le 08/04/2025 à 09:21, Bartosz Golaszewski a écrit : From: Bartosz Golaszewski struct gpio_chip now has callbacks for setting line values that return an integer, allowing to indicate failures. Convert the driver to using them. Signed-off-by: Bartosz Golaszewski Reviewed-by: Christophe Le

Re: [PATCH 4/5] powerpc: 52xx/gpio: use new line value setter callbacks

Le 08/04/2025 à 09:21, Bartosz Golaszewski a écrit : From: Bartosz Golaszewski struct gpio_chip now has callbacks for setting line values that return an integer, allowing to indicate failures. Convert the driver to using them. Signed-off-by: Bartosz Golaszewski Reviewed-by: Christophe Le

Re: [PATCH 00/12] crypto: sha256 - Use partial block API

On Wed, Apr 30, 2025 at 10:45:43AM -0700, Eric Biggers wrote: > > As for your sha256_finup "optimization", it's an interesting idea, but > unfortunately it slightly slows down the common case which is count % 64 < 56, > due to the unnecessary copy to the stack and the following zeroization. In >

Re: [PATCH 00/12] crypto: sha256 - Use partial block API

On Thu, May 01, 2025 at 09:21:15AM +0800, Herbert Xu wrote: > On Wed, Apr 30, 2025 at 10:45:43AM -0700, Eric Biggers wrote: > > > > As for your sha256_finup "optimization", it's an interesting idea, but > > unfortunately it slightly slows down the common case which is count % 64 < > > 56, > > due

Re: [PATCH] bus: fsl_mc: Fix driver_managed_dma check

On 04/25/2025, Robin Murphy wrote: > Since it's not currently safe to take device_lock() in the IOMMU probe > path, that can race against really_probe() setting dev->driver before > attempting to bind. The race itself isn't so bad, since we're only > concerned with dereferencing dev->driver itself

Re: [PATCH 2/5] powerpc: 83xx/gpio: use new line value setter callbacks

Le 30/04/2025 à 19:37, Bartosz Golaszewski a écrit : On Wed, Apr 30, 2025 at 7:33 PM Christophe Leroy wrote: Le 08/04/2025 à 09:21, Bartosz Golaszewski a écrit : From: Bartosz Golaszewski struct gpio_chip now has callbacks for setting line values that return an integer, allowing to ind

Re: [PATCH 1/5] powerpc: sysdev/gpio: use new line value setter callbacks

Le 08/04/2025 à 09:21, Bartosz Golaszewski a écrit : From: Bartosz Golaszewski struct gpio_chip now has callbacks for setting line values that return an integer, allowing to indicate failures. Convert the driver to using them. Signed-off-by: Bartosz Golaszewski Reviewed-by: Christophe Le