Re: [PATCH virt] virt: fix uninit-value in vhost_vsock_dev_open

fields, so you could argue seqpacket_allow should just be explicitly initialized to false. However, eliminating this class of errors by zeroing seems reasonable in this code path. vhost_vsock_dev_open() is not performance-critical. Acked-by: Stefan Hajnoczi signature.asc Description: PGP signature

Re: [syzbot] [virtualization?] upstream boot error: WARNING: refcount bug in __free_pages_ok

On Thu, Mar 21, 2024 at 08:52:03AM -0700, syzbot wrote: > Hello, > > syzbot tried to test the proposed patch but the build/boot failed: > > bcore: registered new interface driver viperboard > [7.297712][T1] usbcore: registered new interface driver dln2 > [7.299149][T1] usbcore:

Re: [syzbot] [virtualization?] upstream boot error: WARNING: refcount bug in __free_pages_ok

On Wed, Mar 20, 2024 at 01:08:02PM -0700, syzbot wrote: > Hello, > > syzbot has tested the proposed patch and the reproducer did not trigger any > issue: > > Reported-and-tested-by: syzbot+70f57d8a3ae84934c...@syzkaller.appspotmail.com > > Tested on: > > commit: 4bedfb31

Re: [syzbot] [virtualization?] upstream boot error: WARNING: refcount bug in __free_pages_ok

On Tue, Mar 19, 2024 at 03:51:18PM -0500, Mike Christie wrote: > On 3/19/24 12:19 PM, Stefan Hajnoczi wrote: > > On Tue, Mar 19, 2024 at 03:40:53AM -0400, Michael S. Tsirkin wrote: > >> On Tue, Mar 19, 2024 at 12:32:26AM -0700, syzbot wrote: > >>> Hello, > >

Re: [syzbot] [virtualization?] upstream boot error: WARNING: refcount bug in __free_pages_ok

virtio_scsi.c commits need to be bisected. Stefan signature.asc Description: PGP signature

Re: [syzbot] [virtualization?] upstream boot error: WARNING: refcount bug in __free_pages_ok

n.c:1437 > > ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 > > ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243 > > > > > > I think I saw this already and also with virtio scsi. virtio > core does not seem to be doing anything special here, >

Re: [PATCH] virtiofs: don't mark virtio_fs_sysfs_exit as __exit

_fs.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Thanks, Arnd. Please see the duplicate patch that Miklos applied: https://lore.kernel.org/linux-fsdevel/cajfpegsjcz-dnzyft3b5gbgcntmdr6r1n8pm5yclmw9fjy1...@mail.gmail.com/T/#t Stefan > > diff --git a/fs/fuse/virtio_fs.c b/fs/fuse/vi

Re: [PATCH v3] vduse: Fix off by one in vduse_dev_mmap()

pa_user/vduse_dev.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) Reviewed-by: Stefan Hajnoczi > diff --git a/drivers/vdpa/vdpa_user/vduse_dev.c > b/drivers/vdpa/vdpa_user/vduse_dev.c > index b7a1fb88c506..eb914084c650 100644 > --- a/drivers/vdpa/vdpa_user/vduse_dev.c >

Re: [PATCH v2] vduse: Fix off by one in vduse_dev_mmap()

On Wed, 28 Feb 2024 at 12:44, Dan Carpenter wrote: > > The dev->vqs[] array has "dev->vq_num" elements. It's allocated in > vduse_dev_init_vqs(). Thus, this > comparison needs to be >= to avoid > reading one element beyond the end of the array. > > Add an array_index_nospec() as well to prevent

[PATCH v6 4/4] ARM: dts: qcom: samsung-matisse-common: Add UART

This was not enabled in the matisse-wifi tree. Without this, it is not possible to use the USB port for serial debugging via a "Carkit debug cable". Signed-off-by: Stefan Hansson Reviewed-by: Krzysztof Kozlowski Reviewed-by: Konrad Dybcio --- .../boot/dts/qcom/qcom-msm8226-samsu

[PATCH v6 3/4] ARM: dts: qcom: Add support for Samsung Galaxy Tab 4 10.1 LTE (SM-T535)

Add a device tree for the Samsung Galaxy Tab 4 10.1 (SM-T535) LTE tablet based on the MSM8926 platform. The common dtsi is also modified to describe the widest constraints, which required modifications to the matisse-wifi dts. Signed-off-by: Stefan Hansson Reviewed-by: Krzysztof Kozlowski

[PATCH v6 2/4] dt-bindings: arm: qcom: Add Samsung Galaxy Tab 4 10.1 LTE

This documents Samsung Galaxy Tab 4 10.1 LTE (samsung,matisselte) which is a tablet by Samsung based on the MSM8926 SoC. Signed-off-by: Stefan Hansson Reviewed-by: Krzysztof Kozlowski --- Documentation/devicetree/bindings/arm/qcom.yaml | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v6 1/4] ARM: dts: qcom: samsung-matisse-common: Add initial common device tree

point. As such, add a common device tree for all matisse devices by Samsung based on the matissewifi dts. Support for matisselte will be introduced in a later patch in this series and will use the common dtsi as well. Signed-off-by: Stefan Hansson Reviewed-by: Krzysztof Kozlowski --- .../qcom

[PATCH v6 0/4] Add samsung-matisselte and common matisse dtsi

readable patch. Changes since v3: - Collect tags. - Remove spurious copyright notice. - Miscellaneous fixes following review feedback. Changes since v4: - Collect tags. - Enable SD card support on matisselte. Changes since v5: - Rebased on latest linux-next. Stefan Hansson (4): ARM

Re: [syzbot] [virtualization?] KMSAN: uninit-value in virtqueue_add (4)

On Wed, Jan 24, 2024 at 11:47:32AM +0100, Alexander Potapenko wrote: > On Thu, Jan 4, 2024 at 9:45 PM Stefan Hajnoczi wrote: > > > > On Tue, Jan 02, 2024 at 08:03:46AM -0500, Michael S. Tsirkin wrote: > > > On Mon, Jan 01, 2024 at 05:38:24AM -0800, syz

Re: [syzbot] [virtualization?] KMSAN: uninit-value in virtqueue_add (4)

Alexander, Please take a look at this KMSAN failure. The uninitialized memory was created for the purpose of writing a coredump. vring_map_one_sg() should have direction=DMA_TO_DEVICE. I can't easily tell whether this is a genuine bug or an issue with commit 88938359e2df ("virtio: kmsan:

[PATCH v5 1/4] ARM: dts: qcom: samsung-matisse-common: Add initial common device tree

point. As such, add a common device tree for all matisse devices by Samsung based on the matissewifi dts. Support for matisselte will be introduced in a later patch in this series and will use the common dtsi as well. Signed-off-by: Stefan Hansson Reviewed-by: Krzysztof Kozlowski --- .../qcom

[PATCH v5 3/4] ARM: dts: qcom: Add support for Samsung Galaxy Tab 4 10.1 LTE (SM-T535)

Add a device tree for the Samsung Galaxy Tab 4 10.1 (SM-T535) LTE tablet based on the MSM8926 platform. The common dtsi is also modified to describe the widest constraints, which required modifications to the matisse-wifi dts. Signed-off-by: Stefan Hansson Reviewed-by: Krzysztof Kozlowski

[PATCH v5 2/4] dt-bindings: arm: qcom: Add Samsung Galaxy Tab 4 10.1 LTE

This documents Samsung Galaxy Tab 4 10.1 LTE (samsung,matisselte) which is a tablet by Samsung based on the MSM8926 SoC. Signed-off-by: Stefan Hansson Reviewed-by: Krzysztof Kozlowski --- Documentation/devicetree/bindings/arm/qcom.yaml | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v5 4/4] ARM: dts: qcom: samsung-matisse-common: Add UART

This was not enabled in the matisse-wifi tree. Without this, it is not possible to use the USB port for serial debugging via a "Carkit debug cable". Signed-off-by: Stefan Hansson Reviewed-by: Krzysztof Kozlowski Reviewed-by: Konrad Dybcio --- .../boot/dts/qcom/qcom-msm8226-samsu

[PATCH v5 0/4] Add samsung-matisselte and common matisse dtsi

readable patch. Changes since v3: - Collect tags. - Remove spurious copyright notice. - Miscellaneous fixes following review feedback. Changes since v4: - Collect tags. - Enable SD card support on matisselte. Stefan Hansson (4): ARM: dts: qcom: samsung-matisse-common: Add initial common

Re: [PATCH v3 3/4] ARM: dts: qcom: Add support for Samsung Galaxy Tab 4 10.1 LTE (SM-T535)

On 2023-10-31 12:08, Konrad Dybcio wrote: On 25.10.2023 10:37, Stefan Hansson wrote: Add a device tree for the Samsung Galaxy Tab 4 10.1 (SM-T535) LTE tablet based on the MSM8926 platform. Signed-off-by: Stefan Hansson --- arch/arm/boot/dts/qcom/Makefile | 1 + .../qcom

[PATCH v4 3/4] ARM: dts: qcom: Add support for Samsung Galaxy Tab 4 10.1 LTE (SM-T535)

Add a device tree for the Samsung Galaxy Tab 4 10.1 (SM-T535) LTE tablet based on the MSM8926 platform. The common dtsi is also modified to describe the widest constraints, which required modifications to the matisse-wifi dts. Signed-off-by: Stefan Hansson --- arch/arm/boot/dts/qcom/Makefile

[PATCH v4 4/4] ARM: dts: qcom: samsung-matisse-common: Add UART

This was not enabled in the matisse-wifi tree. Without this, it is not possible to use the USB port for serial debugging via a "Carkit debug cable". Signed-off-by: Stefan Hansson --- .../boot/dts/qcom/qcom-msm8226-samsung-matisse-common.dtsi| 4 1 file changed, 4 insertion

[PATCH v4 1/4] ARM: dts: qcom: samsung-matisse-common: Add initial common device tree

point. As such, add a common device tree for all matisse devices by Samsung based on the matissewifi dts. Support for matisselte will be introduced in a later patch in this series and will use the common dtsi as well. Signed-off-by: Stefan Hansson --- .../qcom-apq8026-samsung-matisse-wifi.dts

[PATCH v4 2/4] dt-bindings: arm: qcom: Add Samsung Galaxy Tab 4 10.1 LTE

This documents Samsung Galaxy Tab 4 10.1 LTE (samsung,matisselte) which is a tablet by Samsung based on the MSM8926 SoC. Signed-off-by: Stefan Hansson Reviewed-by: Krzysztof Kozlowski --- Documentation/devicetree/bindings/arm/qcom.yaml | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v4 0/4] Add samsung-matisselte and common matisse dtsi

readable patch. Changes since v3: - Collect tags. - Remove spurious copyright notice. - Miscellaneous fixes following review feedback. Stefan Hansson (4): ARM: dts: qcom: samsung-matisse-common: Add initial common device tree dt-bindings: arm: qcom: Add Samsung Galaxy Tab 4 10.1 LTE ARM

Re: [PATCH v3 0/4] Add samsung-matisselte and common matisse dtsi

On 2023-10-25 10:48, Krzysztof Kozlowski wrote: On 25/10/2023 10:37, Stefan Hansson wrote: This series adds a common samsung-matisse dtsi and reworks samsung-matisse-wifi to use it, and introduces samsung-matisselte. I choose matisselte over matisse-lte as this is how most other devices

Re: [PATCH v3 2/4] dt-bindings: arm: qcom: Add Samsung Galaxy Tab 4 10.1 LTE

On 2023-10-25 10:48, Krzysztof Kozlowski wrote: On 25/10/2023 10:37, Stefan Hansson wrote: This documents Samsung Galaxy Tab 4 10.1 LTE (samsung,matisselte) which is a tablet by Samsung based on the MSM8926 SoC. Signed-off-by: Stefan Hansson --- This is a friendly reminder during

[PATCH v3 4/4] ARM: dts: qcom: samsung-matisse-common: Add UART

This was not enabled in the matisse-wifi tree. Without this, it is not possible to use the USB port for serial debugging via a "Carkit debug cable". Signed-off-by: Stefan Hansson --- .../boot/dts/qcom/qcom-msm8226-samsung-matisse-common.dtsi| 4 1 file changed, 4 insertion

[PATCH v3 1/4] ARM: dts: qcom: samsung-matisse-common: Add initial common device tree

point. As such, add a common device tree for all matisse devices by Samsung based on the matissewifi dts. Support for matisselte will be introduced in a later patch in this series and will use the common dtsi as well. Signed-off-by: Stefan Hansson --- .../qcom-apq8026-samsung-matisse-wifi.dts

[PATCH v3 3/4] ARM: dts: qcom: Add support for Samsung Galaxy Tab 4 10.1 LTE (SM-T535)

Add a device tree for the Samsung Galaxy Tab 4 10.1 (SM-T535) LTE tablet based on the MSM8926 platform. Signed-off-by: Stefan Hansson --- arch/arm/boot/dts/qcom/Makefile | 1 + .../qcom/qcom-msm8926-samsung-matisselte.dts | 36 +++ 2 files changed, 37 insertions

[PATCH v3 2/4] dt-bindings: arm: qcom: Add Samsung Galaxy Tab 4 10.1 LTE

This documents Samsung Galaxy Tab 4 10.1 LTE (samsung,matisselte) which is a tablet by Samsung based on the MSM8926 SoC. Signed-off-by: Stefan Hansson --- Documentation/devicetree/bindings/arm/qcom.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/arm

[PATCH v3 0/4] Add samsung-matisselte and common matisse dtsi

readable patch. Stefan Hansson (4): ARM: dts: qcom: samsung-matisse-common: Add initial common device tree dt-bindings: arm: qcom: Add Samsung Galaxy Tab 4 10.1 LTE ARM: dts: qcom: Add support for Samsung Galaxy Tab 4 10.1 LTE (SM-T535) ARM: dts: qcom: samsung-matisse-common: Add UART

[PATCH v2 2/4] dt-bindings: arm: qcom: Add Samsung Galaxy Tab 4 10.1 LTE

This documents Samsung Galaxy Tab 4 10.1 LTE (samsung,matisselte) which is a tablet by Samsung based on the MSM8926 SoC. Signed-off-by: Stefan Hansson --- Documentation/devicetree/bindings/arm/qcom.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/arm

[PATCH v2 4/4] ARM: dts: qcom: samsung-matisse-common: Add UART

This was not enabled in the matisse-wifi tree. Signed-off-by: Stefan Hansson --- .../boot/dts/qcom/qcom-msm8226-samsung-matisse-common.dtsi| 4 1 file changed, 4 insertions(+) diff --git a/arch/arm/boot/dts/qcom/qcom-msm8226-samsung-matisse-common.dtsi b/arch/arm/boot/dts/qcom/qcom

[PATCH v2 1/4] ARM: dts: qcom: samsung-matisse-common: Add initial common device tree

point. As such, add a common device tree for all matisse devices by Samsung based on the matissewifi dts. Support for matisselte will be introduced in a later patch in this series and will use the common dtsi as well. Signed-off-by: Stefan Hansson --- .../qcom-apq8026-samsung-matisse-wifi.dts

[PATCH v2 3/4] ARM: dts: qcom: Add support for Samsung Galaxy Tab 4 10.1 LTE (SM-T535)

Add a device tree for the Samsung Galaxy Tab 4 10.1 (SM-T535) LTE tablet based on the MSM8926 platform. Signed-off-by: Stefan Hansson --- arch/arm/boot/dts/qcom/Makefile | 1 + .../qcom/qcom-msm8926-samsung-matisselte.dts | 36 +++ 2 files changed, 37 insertions

[PATCH v2 0/4] Add samsung-matisselte and common matisse dtsi

with msm8226, and I was not sure how to resolve that. As such, I'm copying what was done in the Lumia 830 (microsoft-tesla) patch given that it was accepted. Stefan Hansson (4): ARM: dts: qcom: samsung-matisse-common: Add initial common device tree dt-bindings: arm: qcom: Add Samsung Galaxy Tab

Re: [PATCH] [v4] ieee802154: ca8210: Fix a potential UAF in ca8210_probe

ister_ext_clock(). v4: -Remove an unused variable 'ret'. This patch has been applied to the wpan tree and will be part of the next pull request to net. Thanks! regards Stefan Schmidt

Re: [PATCH] [v3] ieee802154: ca8210: Fix a potential UAF in ca8210_probe

riable 'ret' [-Wunused-variable] 2743 | int ret = 0; | ^~~ Please take care of this now unused variable after your re-factor. With this fixed and send out as v4 I am happy to get this applied to the wpan tree. regards Stefan Schmidt

Re: [PATCH] [v2] ieee802154: ca8210: Fix a potential UAF in ca8210_probe

t ca8210_priv *priv = spi_get_drvdata(spi); - if (!priv->clk) + if (IS_ERR_OR_NULL(priv->clk)) return of_clk_del_provider(spi->dev.of_node); Alex, Stefan, who handles wpan and wpan/next this release? IIRC it would be me for wpan and Alex for wpan-next. regards Stefan Schmidt

Re: [PATCH v3 25/25] integrity: Switch from rbtree to LSM-managed blob for integrity_iint_cache

On 9/4/23 09:40, Roberto Sassu wrote: From: Roberto Sassu Before the security field of kernel objects could be shared among LSMs with the LSM stacking feature, IMA and EVM had to rely on an alternative storage of inode metadata. The association between inode metadata and inode is maintained

Re: [PATCH v2 2/2] certs: Add support for using elliptic curve keys for signing modules

On 4/20/21 10:03 AM, Jessica Yu wrote: +++ Stefan Berger [08/04/21 11:24 -0400]: diff --git a/crypto/asymmetric_keys/pkcs7_parser.c b/crypto/asymmetric_keys/pkcs7_parser.c index 967329e0a07b..2546ec6a0505 100644 --- a/crypto/asymmetric_keys/pkcs7_parser.c +++ b/crypto/asymmetric_keys

[PATCH 1/3] drm/panel: Add connector_type and bus_format for AUO G104SN02 V2 panel

The AUO G104SN02 V2 is an LVDS display which supports 6 and 8 bpc PSWG. Add the corresponding connector type and 8 bpc as default bus_format. Signed-off-by: Stefan Riedmueller --- drivers/gpu/drm/panel/panel-simple.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/panel

[PATCH 2/3] drm/panel: Add connector_type for some EDT displays

The connector_type for following two EDT displays is missing: - EDT ETM0430G0DH6 - EDT ETM0700G0BDH6 Both are parallel displays thus add the corresponding connector_type. Signed-off-by: Stefan Riedmueller --- drivers/gpu/drm/panel/panel-simple.c | 2 ++ 1 file changed, 2 insertions(+) diff

[PATCH 3/3] drm/panel: Add bus_format and bus_flags for EDT ETM0430G0DH6

Add corresponding bus_format and bus_flags for the EDT ETM0430G0DH6 display. Signed-off-by: Stefan Riedmueller --- drivers/gpu/drm/panel/panel-simple.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index

Re: [PATCH] io_thread/x86: don't reset 'cs', 'ss', 'ds' and 'es' registers for io_threads

ust keep the values of the copy_thread() caller. Do you plan to do something about this before 5.12 final? metze Am 11.04.21 um 17:27 schrieb Stefan Metzmacher: > This allows gdb attach to userspace processes using io-uring, > which means that they have io_threads (PF_IO_WORKER), which appea

[PATCH] leds: pca9532: Assign gpio base dynamically

When using devicetree, gpio_base holds its initial zero value which can lead to a rejection if another gpio controller already occupies this base. To prevent that collision let the gpio base be assigned dynamically. Signed-off-by: Stefan Riedmueller --- drivers/leds/leds-pca9532.c | 2 ++ 1

Re: [PATCH] virtio_blk: Add support for lifetime feature

yet. Why exactly is exposing eMMC-style lifetime information problematic? Can you and Enrico discuss the use case to figure out an alternative interface? Thanks, Stefan signature.asc Description: PGP signature

Re: [PATCH] virtiofs: remove useless function

/virtio_fs.c | 5 - > 1 file changed, 5 deletions(-) The function was never used... Reviewed-by: Stefan Hajnoczi signature.asc Description: PGP signature

RE: [EXT] Re: [PATCH net-next] net: mvpp2: Add parsing support for different IPv4 IHL values

> -Original Message- > From: Marcin Wojtas > Sent: Tuesday, April 13, 2021 12:59 PM > To: Stefan Chulski > Cc: Russell King - ARM Linux admin ; > net...@vger.kernel.org; thomas.petazz...@bootlin.com; > da...@davemloft.net; Nadav Haklai ; Yan > Markman ; linu

RE: [EXT] Re: [PATCH net-next] net: mvpp2: Add parsing support for different IPv4 IHL values

> > -Original Message- > > From: Russell King - ARM Linux admin > > Sent: Tuesday, April 13, 2021 12:18 PM > > To: Stefan Chulski > > Cc: net...@vger.kernel.org; thomas.petazz...@bootlin.com; > > da...@davemloft.net; Nadav Haklai ; Yan > Markman

RE: [EXT] Re: [PATCH net-next] net: mvpp2: Add parsing support for different IPv4 IHL values

> -Original Message- > From: Russell King - ARM Linux admin > Sent: Tuesday, April 13, 2021 12:18 PM > To: Stefan Chulski > Cc: net...@vger.kernel.org; thomas.petazz...@bootlin.com; > da...@davemloft.net; Nadav Haklai ; Yan > Markman ; linux-kernel@vger.kernel.org;

Re: [PATCH] virtio_blk: Add support for lifetime feature

On Tue, Mar 30, 2021 at 11:16:02PM +, Enrico Granata wrote: > The VirtIO TC has adopted a new feature in virtio-blk enabling > discovery of lifetime information. > > This commit adds support for the VIRTIO_BLK_T_LIFETIME command > to the virtio_blk driver, and adds two new attributes to the >

[PATCH] io_thread/x86: don't reset 'cs', 'ss', 'ds' and 'es' registers for io_threads

Signed-off-by: Stefan Metzmacher cc: Linus Torvalds cc: Jens Axboe cc: linux-kernel@vger.kernel.org cc: io-ur...@vger.kernel.org --- arch/x86/kernel/process.c | 49 +++ 1 file changed, 49 insertions(+) diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/proce

Re: [PATCH 4/4] ARM: dts: Fix-up EMMC2 controller's frequency

Hi Nicolas, Am 09.04.21 um 12:54 schrieb Nicolas Saenz Julienne: > Hi again, > > On Wed, 2021-04-07 at 16:37 -0400, Alan Cooper wrote: >> Nicolas, >> >> I got a better description of the failure and it looks like the bus >> clock needs to be limited to 300KHz for a 500MHz core clock. >> What's

Re: [PATCH v2 1/2] certs: Trigger creation of RSA module signing key if it's not an RSA key

On 4/8/21 1:15 PM, Mimi Zohar wrote: On Thu, 2021-04-08 at 11:24 -0400, Stefan Berger wrote: Address a kbuild issue where a developer created an ECDSA key for signing kernel modules and then builds an older version of the kernel, when bi- secting the kernel for example, that does not support

[PATCH v2 0/2] Add support for ECDSA-signed kernel modules

://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git/log/?h=ecc Stefan v2: - Adjustment to ECDSA key detector string in 2/2 - Rephrased cover letter and patch descriptions with Mimi Stefan Berger (2): certs: Trigger creation of RSA module signing key if it's not an RSA key

[PATCH v2 1/2] certs: Trigger creation of RSA module signing key if it's not an RSA key

: cfc411e7fff3 ("Move certificate handling to its own directory") Signed-off-by: Stefan Berger --- certs/Makefile | 5 + 1 file changed, 5 insertions(+) diff --git a/certs/Makefile b/certs/Makefile index e3185c57fbd8..f64bc89ccbf1 100644 --- a/certs/Makefile +++ b/certs/Makefile @@ -5

[PATCH v2 2/2] certs: Add support for using elliptic curve keys for signing modules

/signing_key.*) when building an older version of a kernel that only supports RSA keys. Unless kbuild automati- cally detects and generates a new kernel module key, ECDSA-signed kernel modules will fail signature verification. Signed-off-by: Stefan Berger --- v2: - check for ECDSA key by id

Re: [PATCH 0/2] Add support for ECDSA-signed kernel modules

On 4/7/21 12:10 PM, Mimi Zohar wrote: On Wed, 2021-04-07 at 18:53 +0300, Jarkko Sakkinen wrote: On Tue, Apr 06, 2021 at 02:53:38PM -0400, Stefan Berger wrote: This series adds support for ECDSA-signed kernel modules. The first patch in this series attempts to address the issue where

Re: [PATCH v2] net: mac802154: Fix general protection fault

to gerrit public mirror. I'm using it to check patches with syzbot. Change ids are useless outside gerrit, so it shouldn't be here. Btw, should I sent v2 or this is already fixed? Otherwise the patch looks good. May Stefan can fix this. Acked-by: Alexander Aring I removed the Change-ID locally

[PATCH 2/2] certs: Add support for using elliptic curve keys for signing modules

/signing_key.*) when falling back to building an older version of a kernel that only supports RSA keys since otherwise ECDSA-signed modules will not be usable when that older kernel runs and the ECDSA key was still used for signing modules. Signed-off-by: Stefan Berger --- certs/Kconfig

[PATCH 1/2] certs: Trigger recreation of module signing key if it's not an RSA key

if falling back to kernels that have actually been patched with this kernel, such as the stable trees. Fixes: cfc411e7fff3 ("Move certificate handling to its own directory") Signed-off-by: Stefan Berger --- certs/Makefile | 5 + 1 file changed, 5 insertions(+) diff --git a/certs/

[PATCH 0/2] Add support for ECDSA-signed kernel modules

here: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git/log/?h=ecc Stefan Stefan Berger (2): certs: Trigger recreation of module signing key if it's not an RSA key certs: Add support for using elliptic curve keys for signing modules certs/Kconfig

Re: [PATCH 2/3] mmc: sdhci-iproc: Cap min clock frequency on BCM2711

Hi Nicolas, Am 06.04.21 um 12:48 schrieb Nicolas Saenz Julienne: > There is a known bug on BCM2711's SDHCI core integration where the > controller will hang when the difference between the core clock and the > bus clock is too great. Specifically this can be reproduced under the > following

Re: [PATCH] tools/kvm_stat: fix out of date aarch64 kvm_exit reason definations

, +'IMP_DEF': 0x1f, 'IABT': 0x20, 'IABT_HYP': 0x21, 'PC_ALIGN': 0x22, Reviewed-by: Stefan Raspl -- Mit freundlichen Grüßen / Kind regards Stefan Raspl Linux on Z

Re: [PATCH 0/6] Allow signals for IO threads

Am 01.04.21 um 18:24 schrieb Linus Torvalds: > On Thu, Apr 1, 2021 at 9:00 AM Stefan Metzmacher wrote: >> >> I haven't tried it, but it seems gdb tries to use PTRACE_PEEKUSR >> against the last thread tid listed under /proc//tasks/ in order to >> get the architecture fo

Re: [PATCH v3 3/3] ima: enable loading of build time generated key on .ima keyring

On 3/30/21 9:16 AM, Nayna Jain wrote: The kernel currently only loads the kernel module signing key onto the builtin trusted keyring. Load the module signing key onto the IMA keyring as well. Signed-off-by: Nayna Jain Acked-by: Stefan Berger --- certs/system_certificates.S | 13

Re: [PATCH v3 2/3] ima: enable signing of modules with build time generated key

On 3/30/21 9:16 AM, Nayna Jain wrote: The kernel build process currently only signs kernel modules when MODULE_SIG is enabled. Also, sign the kernel modules at build time when IMA_APPRAISE_MODSIG is enabled. Signed-off-by: Nayna Jain Acked-by: Stefan Berger --- certs/Kconfig | 2

Re: [PATCH 0/2] Don't show PF_IO_WORKER in /proc//task/

Hi Jens, >> I know you brought this one up as part of your series, not sure I get >> why you want it owned by root and read-only? cmdline and exe, yeah those >> could be hidden, but is there really any point? >> >> Maybe I'm missing something here, if so, do clue me in! > > I looked through

Re: [PATCH 2/8] kernel: unmask SIGSTOP for IO threads

Hi Jens, >>> I don't assume signals wanted by userspace should potentially handled in an >>> io_thread... >>> e.g. things set with fcntl(fd, F_SETSIG,) used together with F_SETLEASE? >> >> I guess we do actually need it, if we're not fiddling with >> wants_signal() for them. To quell Oleg's

Re: [PATCH] Document that PF_KTHREAD _is_ ABI

Am 31.03.21 um 21:23 schrieb Alexey Dobriyan: > On Mon, Mar 22, 2021 at 07:53:10AM +, Christoph Hellwig wrote: >> On Sat, Mar 20, 2021 at 10:23:12AM -0700, Andy Lutomirski wrote: https://github.com/systemd/systemd/blob/main/src/basic/process-util.c#L354

Re: [PATCH 0/6] Allow signals for IO threads

Am 01.04.21 um 17:39 schrieb Linus Torvalds: > On Thu, Apr 1, 2021 at 7:58 AM Stefan Metzmacher wrote: >> >>> >>> Ok, the following makes gdb happy again: >>> >>> --- a/arch/x86/kernel/process.c >>> +++ b/arch/x86/kernel/process.c

Re: [PATCH 0/6] Allow signals for IO threads

Hi Jens, >> For help, type "help". >> Type "apropos word" to search for commands related to "word". >> Attaching to process 1320 >> [New LWP 1321] >> [New LWP 1322] >> >> warning: Selected architecture i386:x86-64 is not compatible with reported >> target architecture i386 >> >> warning:

Re: memory leak in virtio_transport_send_pkt_info

en the syzkaller leak check runs. I don't see a fix for this in linux.git. Have you already looked at this? Stefan > > executing program > BUG: memory leak > unreferenced object 0x88811477d380 (size 96): > comm "syz-executor196", pid 8793, jiffies 4294968272 (age 26

Re: [PATCH] virtio_blk: make virtio blks as non-rotational devices

On Fri, Mar 26, 2021 at 11:39:13AM +0800, Sochin Jiang wrote: > This confuses some users seeing one rotational block device > in the guest(/sys/block/vdx/queue/rotational), let's make > virtio blks as virtual block devices, just like xen blks, > and as we known, QUEUE_FLAG_VIRT is defined as

[PATCH v2 3/3] ARM: dts: imx6: pbab01: Set vmmc supply for both SD interfaces

hytec phyFLEX-i.MX6 Ouad module") Signed-off-by: Stefan Riedmueller Reviewed-by: Fabio Estevam --- Changes in v2: - Added fixes tag - Added reviewed-by arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl-phytec-pfla

[PATCH v2 2/3] ARM: dts: imx6: pbab01: Set USB OTG port to peripheral

Due to a hardware bug preventing the correct detection if the ID pin the USB OTG port cannot be used in otg mode. It can either be set to host or peripheral. Set it to peripheral so vbus is disabled by default. Signed-off-by: Stefan Riedmueller Reviewed-by: Fabio Estevam --- Changes in v2

[PATCH v2 1/3] ARM: dts: imx6: pfla02: Fix USB vbus enable pinmuxing

The pinmuxing for the enable pin of the usbh1 node is wrong. It needs to be muxed as GPIO. While at it, move the pinctrl to the vbus regulator since it is actually the regulator enable pin. Signed-off-by: Stefan Riedmueller --- Changes in v2: - Use default pad ctl value instead of 0x8000

Re: [PATCH 3/3] ARM: dts: imx6: pbab01: Set vmmc supply for both SD interfaces

Hi Fabio, On Mon, 2021-03-29 at 08:34 -0300, Fabio Estevam wrote: > On Mon, Mar 29, 2021 at 8:28 AM Stefan Riedmueller > wrote: > > Setting the vmmc supplies is crucial since otherwise the supplying > > regulators get disabled and the SD interfaces are no longer powered > &g

Re: [PATCH 1/3] ARM: dts: imx6: pfla02: Fix USB vbus enable pinmuxing

Hi Fabio, On Mon, 2021-03-29 at 08:32 -0300, Fabio Estevam wrote: > Hi Stefan, > > On Mon, Mar 29, 2021 at 8:28 AM Stefan Riedmueller > wrote: > > > - pinctrl_usbh1: usbh1grp { > > + pinctrl_usbh1_vbus: usbh1vbusgrp { > >

[PATCH 2/3] ARM: dts: imx6: pbab01: Set USB OTG port to peripheral

Due to a hardware bug preventing the correct detection if the ID pin the USB OTG port cannot be used in otg mode. It can either be set to host or peripheral. Set it to peripheral so vbus is disabled by default. Signed-off-by: Stefan Riedmueller --- arch/arm/boot/dts/imx6qdl-phytec-pbab01.dtsi

[PATCH 3/3] ARM: dts: imx6: pbab01: Set vmmc supply for both SD interfaces

Setting the vmmc supplies is crucial since otherwise the supplying regulators get disabled and the SD interfaces are no longer powered which leads to system failures if the system is booted from that SD interface. Signed-off-by: Stefan Riedmueller --- arch/arm/boot/dts/imx6qdl-phytec-pfla02

[PATCH 1/3] ARM: dts: imx6: pfla02: Fix USB vbus enable pinmuxing

The pinmuxing for the enable pin of the usbh1 node is wrong. It needs to be muxed as GPIO. While at it, move the pinctrl to the vbus regulator since it is actually the regulator enable pin. Signed-off-by: Stefan Riedmueller --- arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi | 8 1 file

Re: [PATCH 0/6] Allow signals for IO threads

Hi Jens, > root@ub1704-166:~# LANG=C gdb --pid 1320 > GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2 > Copyright (C) 2020 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > This is free software: you are free to change and redistribute it.

Re: [PATCH] s390: dasd: Mundane spelling fixes

Am 22.03.21 um 03:39 schrieb Bhaskar Chowdhury: > s/Subssystem/Subsystem/ ..two different places > s/reportet/reported/ > s/managemnet/management/ > > Signed-off-by: Bhaskar Chowdhury > --- > drivers/s390/block/dasd_eckd.h | 8 > 1 file changed, 4 insertions(+), 4 deletions(-)

Re: [PATCH 2/8] kernel: unmask SIGSTOP for IO threads

Am 26.03.21 um 16:29 schrieb Jens Axboe: > On 3/26/21 9:23 AM, Stefan Metzmacher wrote: >> Am 26.03.21 um 16:01 schrieb Jens Axboe: >>> On 3/26/21 7:48 AM, Oleg Nesterov wrote: >>>> Jens, sorry, I got lost :/ >>> >>> Let's bring you

Re: [PATCH 4/4] ARM: dts: Fix-up EMMC2 controller's frequency

Am 26.03.21 um 17:17 schrieb Nicolas Saenz Julienne: > On Thu, 2021-03-25 at 20:11 +0100, Stefan Wahren wrote: >> Am 24.03.21 um 16:34 schrieb Nicolas Saenz Julienne: >>> Hi Stefan, >>> >>> On Wed, 2021-03-24 at 16:16 +0100, Stefan Wahren wrote: >>>

Re: [PATCH 2/8] kernel: unmask SIGSTOP for IO threads

Am 26.03.21 um 16:01 schrieb Jens Axboe: > On 3/26/21 7:48 AM, Oleg Nesterov wrote: >> Jens, sorry, I got lost :/ > > Let's bring you back in :-) > >> On 03/25, Jens Axboe wrote: >>> >>> With IO threads accepting signals, including SIGSTOP, >> >> where can I find this change? Looks like I wasn't

Re: [PATCH 0/6] Allow signals for IO threads

Am 26.03.21 um 16:10 schrieb Jens Axboe: > On 3/26/21 9:08 AM, Stefan Metzmacher wrote: >> Am 26.03.21 um 15:55 schrieb Jens Axboe: >>> On 3/26/21 8:53 AM, Jens Axboe wrote: >>>> On 3/26/21 8:45 AM, Stefan Metzmacher wrote: >>>>> Am 26.03.21 um 15:43

Re: [PATCH 0/6] Allow signals for IO threads

Am 26.03.21 um 15:55 schrieb Jens Axboe: > On 3/26/21 8:53 AM, Jens Axboe wrote: >> On 3/26/21 8:45 AM, Stefan Metzmacher wrote: >>> Am 26.03.21 um 15:43 schrieb Stefan Metzmacher: >>>> Am 26.03.21 um 15:38 schrieb Jens Axboe: >>>>> On 3/26/21 7:59 AM

Re: [PATCH 0/6] Allow signals for IO threads

Am 26.03.21 um 15:53 schrieb Jens Axboe: > On 3/26/21 8:45 AM, Stefan Metzmacher wrote: >> Am 26.03.21 um 15:43 schrieb Stefan Metzmacher: >>> Am 26.03.21 um 15:38 schrieb Jens Axboe: >>>> On 3/26/21 7:59 AM, Jens Axboe wrote: >>>>> On 3/26/21 7:54

Re: [PATCH 0/6] Allow signals for IO threads

Am 26.03.21 um 15:43 schrieb Stefan Metzmacher: > Am 26.03.21 um 15:38 schrieb Jens Axboe: >> On 3/26/21 7:59 AM, Jens Axboe wrote: >>> On 3/26/21 7:54 AM, Jens Axboe wrote: >>>>> The KILL after STOP deadlock still exists. >>>> >>>&g

Re: [PATCH 0/6] Allow signals for IO threads

Am 26.03.21 um 15:38 schrieb Jens Axboe: > On 3/26/21 7:59 AM, Jens Axboe wrote: >> On 3/26/21 7:54 AM, Jens Axboe wrote: The KILL after STOP deadlock still exists. >>> >>> In which tree? Sounds like you're still on the old one with that >>> incremental you sent, which wasn't complete. >>>

Re: [PATCH 0/6] Allow signals for IO threads

Am 26.03.21 um 13:56 schrieb Jens Axboe: > On 3/26/21 5:48 AM, Stefan Metzmacher wrote: >> >> Am 26.03.21 um 01:39 schrieb Jens Axboe: >>> Hi, >>> >>> As discussed in a previous thread today, the seemingly much saner approach >>> is just to allow

Re: [PATCH 0/2] Don't show PF_IO_WORKER in /proc//task/

Hi Jens, >> And /proc/$iothread/ should be read only and owned by root with >> "cmdline" and "exe" being empty. > > I know you brought this one up as part of your series, not sure I get > why you want it owned by root and read-only? cmdline and exe, yeah those > could be hidden, but is there

Re: [PATCH 0/2] Don't show PF_IO_WORKER in /proc//task/

Am 25.03.21 um 22:44 schrieb Jens Axboe: > On 3/25/21 2:40 PM, Jens Axboe wrote: >> On 3/25/21 2:12 PM, Linus Torvalds wrote: >>> On Thu, Mar 25, 2021 at 12:42 PM Linus Torvalds >>> wrote: On Thu, Mar 25, 2021 at 12:38 PM Linus Torvalds wrote: > > I don't know what the

Re: [PATCH 0/2] Don't show PF_IO_WORKER in /proc//task/

Am 25.03.21 um 22:20 schrieb Stefan Metzmacher: > > Am 25.03.21 um 21:55 schrieb Eric W. Biederman: >> Oleg Nesterov writes: >> >>> On 03/25, Linus Torvalds wrote: >>>> >>>> The whole "signals are very special for IO threads" th

  1   2   3   4   5   6   7   8   9   10   >