Re: [ANNOUNCE] Kconfiglib menuconfig implementation

On 05/03/2018 03:48 PM, Ulf Magnusson wrote: > On Thu, May 3, 2018 at 10:28 PM, Randy Dunlap wrote: >> Hi, >> >> (with new kconfiglib.py and menuconfig.py) >> >> Thanks for the fixes. >> >> If I use "LC_CTYPE=C.UTF-8" then I get the down arrows in the bottom colored >> bar.

Re: [ANNOUNCE] Kconfiglib menuconfig implementation

On 05/03/2018 03:48 PM, Ulf Magnusson wrote: > On Thu, May 3, 2018 at 10:28 PM, Randy Dunlap wrote: >> Hi, >> >> (with new kconfiglib.py and menuconfig.py) >> >> Thanks for the fixes. >> >> If I use "LC_CTYPE=C.UTF-8" then I get the down arrows in the bottom colored >> bar. Without that, I get

Re: [PATCH 1/6] firmware: permit LSMs and IMA to fail firmware sysfs fallback loading

If you can add Andres Rodriguez , and Greg to your Cc list in the future patches that'd be appreciated. On Tue, May 01, 2018 at 09:48:18AM -0400, Mimi Zohar wrote: > Add an LSM hook prior to allowing firmware sysfs fallback loading. > > Signed-off-by: Mimi Zohar

Re: [PATCH 1/6] firmware: permit LSMs and IMA to fail firmware sysfs fallback loading

If you can add Andres Rodriguez , and Greg to your Cc list in the future patches that'd be appreciated. On Tue, May 01, 2018 at 09:48:18AM -0400, Mimi Zohar wrote: > Add an LSM hook prior to allowing firmware sysfs fallback loading. > > Signed-off-by: Mimi Zohar > Cc: Luis R. Rodriguez > Cc:

Re: [PATCH 5/9] firmware: add function to load firmware without warnings v5

On Mon, Apr 23, 2018 at 04:12:01PM -0400, Andres Rodriguez wrote: > diff --git a/include/linux/firmware.h b/include/linux/firmware.h > index db8351a42405..a34e16f77f20 100644 > --- a/include/linux/firmware.h > +++ b/include/linux/firmware.h > @@ -42,6 +42,8 @@ struct builtin_fw { > #if

Re: [PATCH 5/9] firmware: add function to load firmware without warnings v5

On Mon, Apr 23, 2018 at 04:12:01PM -0400, Andres Rodriguez wrote: > diff --git a/include/linux/firmware.h b/include/linux/firmware.h > index db8351a42405..a34e16f77f20 100644 > --- a/include/linux/firmware.h > +++ b/include/linux/firmware.h > @@ -42,6 +42,8 @@ struct builtin_fw { > #if

Re: [PATCH v7 06/24] ASoC: qdsp6: dt-bindings: Add q6asm dt bindings

On 5/1/2018 5:08 AM, Srinivas Kandagatla wrote: This patch add DT bindings for ASM (Audio Stream Manager) DSP module. Signed-off-by: Srinivas Kandagatla Reviewed-and-tested-by: Rohit kumar Reviewed-by: Rob Herring ---

Re: [PATCH v7 06/24] ASoC: qdsp6: dt-bindings: Add q6asm dt bindings

On 5/1/2018 5:08 AM, Srinivas Kandagatla wrote: This patch add DT bindings for ASM (Audio Stream Manager) DSP module. Signed-off-by: Srinivas Kandagatla Reviewed-and-tested-by: Rohit kumar Reviewed-by: Rob Herring --- .../devicetree/bindings/sound/qcom,q6asm.txt | 33

Re: [PATCH v7 05/24] ASoC: qdsp6: dt-bindings: Add q6adm dt bindings

On 5/1/2018 5:08 AM, Srinivas Kandagatla wrote: This patch add DT bindings for ADM (Audio Device Manager) DSP module. This module implements mixer controls to setup the connections between AFE ports and ASM streams. Signed-off-by: Srinivas Kandagatla

[PATCH v1 1/5] drm/tegra: dc: Balance IOMMU group refcounting

Remove unneeded iommu_group_get() and add missing iommu_group_put(), correcting IOMMU group refcount. This is a minor correction / cleanup that doesn't really fix anything because Tegra's IOMMU driver are built-in and hence groups refcounting can't hold IOMMU driver from unloading. Signed-off-by:

Re: [PATCH v7 05/24] ASoC: qdsp6: dt-bindings: Add q6adm dt bindings

On 5/1/2018 5:08 AM, Srinivas Kandagatla wrote: This patch add DT bindings for ADM (Audio Device Manager) DSP module. This module implements mixer controls to setup the connections between AFE ports and ASM streams. Signed-off-by: Srinivas Kandagatla Reviewed-and-tested-by: Rohit kumar

[PATCH v1 1/5] drm/tegra: dc: Balance IOMMU group refcounting

Remove unneeded iommu_group_get() and add missing iommu_group_put(), correcting IOMMU group refcount. This is a minor correction / cleanup that doesn't really fix anything because Tegra's IOMMU driver are built-in and hence groups refcounting can't hold IOMMU driver from unloading. Signed-off-by:

[PATCH v1 3/5] drm/tegra: gr3d: Add IOMMU support

Attach GR3D to the displays IOMMU group in order to provide GR3D access to BO's IOVA. Signed-off-by: Dmitry Osipenko --- drivers/gpu/drm/tegra/gr3d.c | 27 +++ 1 file changed, 27 insertions(+) diff --git a/drivers/gpu/drm/tegra/gr3d.c

[PATCH v1 3/5] drm/tegra: gr3d: Add IOMMU support

Attach GR3D to the displays IOMMU group in order to provide GR3D access to BO's IOVA. Signed-off-by: Dmitry Osipenko --- drivers/gpu/drm/tegra/gr3d.c | 27 +++ 1 file changed, 27 insertions(+) diff --git a/drivers/gpu/drm/tegra/gr3d.c b/drivers/gpu/drm/tegra/gr3d.c

[PATCH v1 5/5] ARM: dts: tegra114: Add IOMMU nodes to Host1x and its clients

Enable IOMMU support for Host1x and its clients. Signed-off-by: Dmitry Osipenko --- arch/arm/boot/dts/tegra114.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/tegra114.dtsi b/arch/arm/boot/dts/tegra114.dtsi index 0e4a13295d8a..84c4358dacac

[PATCH v1 0/5] Support IOMMU for 2d/3d on Tegra30/114

Hi, This series enables IOMMU support for 2d/3d HW on Tegra30/114, as a result userspace that uses 2d/3d could work with the active IOMMU. Dmitry Osipenko (5): drm/tegra: dc: Balance IOMMU group refcounting drm/tegra: gr2d: Add IOMMU support drm/tegra: gr3d: Add IOMMU support ARM: dts:

[PATCH v1 5/5] ARM: dts: tegra114: Add IOMMU nodes to Host1x and its clients

Enable IOMMU support for Host1x and its clients. Signed-off-by: Dmitry Osipenko --- arch/arm/boot/dts/tegra114.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/tegra114.dtsi b/arch/arm/boot/dts/tegra114.dtsi index 0e4a13295d8a..84c4358dacac 100644 ---

[PATCH v1 0/5] Support IOMMU for 2d/3d on Tegra30/114

Hi, This series enables IOMMU support for 2d/3d HW on Tegra30/114, as a result userspace that uses 2d/3d could work with the active IOMMU. Dmitry Osipenko (5): drm/tegra: dc: Balance IOMMU group refcounting drm/tegra: gr2d: Add IOMMU support drm/tegra: gr3d: Add IOMMU support ARM: dts:

[PATCH v1 4/5] ARM: dts: tegra30: Add IOMMU nodes to Host1x and its clients

Enable IOMMU support for Host1x and its clients. Signed-off-by: Dmitry Osipenko --- arch/arm/boot/dts/tegra30.dtsi | 14 ++ 1 file changed, 14 insertions(+) diff --git a/arch/arm/boot/dts/tegra30.dtsi b/arch/arm/boot/dts/tegra30.dtsi index

[PATCH v1 4/5] ARM: dts: tegra30: Add IOMMU nodes to Host1x and its clients

Enable IOMMU support for Host1x and its clients. Signed-off-by: Dmitry Osipenko --- arch/arm/boot/dts/tegra30.dtsi | 14 ++ 1 file changed, 14 insertions(+) diff --git a/arch/arm/boot/dts/tegra30.dtsi b/arch/arm/boot/dts/tegra30.dtsi index a110cf84d85f..09087b9c5e26 100644 ---

[PATCH v1 2/5] drm/tegra: gr2d: Add IOMMU support

Attach GR2D to the display IOMMU group in order to provide GR2D access to BO's IOVA. Signed-off-by: Dmitry Osipenko --- drivers/gpu/drm/tegra/gr2d.c | 31 +-- 1 file changed, 29 insertions(+), 2 deletions(-) diff --git

[PATCH v1 2/5] drm/tegra: gr2d: Add IOMMU support

Attach GR2D to the display IOMMU group in order to provide GR2D access to BO's IOVA. Signed-off-by: Dmitry Osipenko --- drivers/gpu/drm/tegra/gr2d.c | 31 +-- 1 file changed, 29 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/tegra/gr2d.c

Re: [PATCH v7 04/24] ASoC: qdsp6: dt-bindings: Add q6afe dt bindings

On 5/1/2018 5:08 AM, Srinivas Kandagatla wrote: This patch add DT bindings for AFE (Audio Frontend) DSP module. Signed-off-by: Srinivas Kandagatla Reviewed-and-tested-by: Rohit kumar --- .../devicetree/bindings/sound/qcom,q6afe.txt

Re: [PATCH v7 04/24] ASoC: qdsp6: dt-bindings: Add q6afe dt bindings

On 5/1/2018 5:08 AM, Srinivas Kandagatla wrote: This patch add DT bindings for AFE (Audio Frontend) DSP module. Signed-off-by: Srinivas Kandagatla Reviewed-and-tested-by: Rohit kumar --- .../devicetree/bindings/sound/qcom,q6afe.txt | 104 +

Re: [PATCH v7 03/24] ASoC: qdsp6: dt-bindings: Add q6core dt bindings

On 5/1/2018 5:07 AM, Srinivas Kandagatla wrote: This patch add DT bindings for Q6CORE DSP module. Signed-off-by: Srinivas Kandagatla Reviewed-and-tested-by: Rohit kumar Reviewed-by: Rob Herring ---

Re: [PATCH v7 03/24] ASoC: qdsp6: dt-bindings: Add q6core dt bindings

On 5/1/2018 5:07 AM, Srinivas Kandagatla wrote: This patch add DT bindings for Q6CORE DSP module. Signed-off-by: Srinivas Kandagatla Reviewed-and-tested-by: Rohit kumar Reviewed-by: Rob Herring --- .../devicetree/bindings/sound/qcom,q6core.txt | 21 + 1 file

Re: [PATCH 7/9] firmware: use rename fw_sysfs_fallback to use the firmware_ prefix

On Mon, Apr 23, 2018 at 04:12:03PM -0400, Andres Rodriguez wrote: > Use the correct prefix for symbols exported by firmware_loader(). This > is done since firmware_sysfs_fallback() is now exposed through > kernel-doc. > > Signed-off-by: Andres Rodriguez > --- >

Re: [PATCH 7/9] firmware: use rename fw_sysfs_fallback to use the firmware_ prefix

On Mon, Apr 23, 2018 at 04:12:03PM -0400, Andres Rodriguez wrote: > Use the correct prefix for symbols exported by firmware_loader(). This > is done since firmware_sysfs_fallback() is now exposed through > kernel-doc. > > Signed-off-by: Andres Rodriguez > --- >

Re: [PATCH 6/9] firmware: print firmware name on fallback path

On Mon, Apr 23, 2018 at 04:12:02PM -0400, Andres Rodriguez wrote: > Previously, one could assume the firmware name from the preceding > message: "Direct firmware load for {name} failed with error %d". > > However, with the new firmware_request_nowarn() entrypoint, the message > outlined above

Re: [PATCH 6/9] firmware: print firmware name on fallback path

On Mon, Apr 23, 2018 at 04:12:02PM -0400, Andres Rodriguez wrote: > Previously, one could assume the firmware name from the preceding > message: "Direct firmware load for {name} failed with error %d". > > However, with the new firmware_request_nowarn() entrypoint, the message > outlined above

Applied "spi: pxa2xx: check clk_prepare_enable() return value" to the spi tree

The patch spi: pxa2xx: check clk_prepare_enable() return value has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "spi: pxa2xx: check clk_prepare_enable() return value" to the spi tree

The patch spi: pxa2xx: check clk_prepare_enable() return value has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Re: [PATCH 5/9] firmware: add function to load firmware without warnings v5

On Mon, Apr 23, 2018 at 04:12:01PM -0400, Andres Rodriguez wrote: > Currently the firmware loader only exposes one silent path for querying > optional firmware, and that is firmware_request_direct(). This function > also disables the fallback path, which might not always be the > desired

Re: [PATCH 5/9] firmware: add function to load firmware without warnings v5

On Mon, Apr 23, 2018 at 04:12:01PM -0400, Andres Rodriguez wrote: > Currently the firmware loader only exposes one silent path for querying > optional firmware, and that is firmware_request_direct(). This function > also disables the fallback path, which might not always be the > desired

Re: [PATCH] spi: spi-geni-qcom: Add SPI driver support for GENI based QUP

On Thu, May 03, 2018 at 03:34:43PM -0600, Girish Mahadevan wrote: > This driver supports GENI based SPI Controller in the Qualcomm SOCs. The > Qualcomm Generic Interface (GENI) is a programmable module supporting a > wide range of serial interfaces including SPI. This driver supports SPI >

Re: [PATCH] spi: spi-geni-qcom: Add SPI driver support for GENI based QUP

On Thu, May 03, 2018 at 03:34:43PM -0600, Girish Mahadevan wrote: > This driver supports GENI based SPI Controller in the Qualcomm SOCs. The > Qualcomm Generic Interface (GENI) is a programmable module supporting a > wide range of serial interfaces including SPI. This driver supports SPI >

[PATCH v2] x86/kexec: avoid double free_page() upon do_kexec_load() failure.

>From 91a78abed036e1662b11cb54ae6300864e17b709 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Fri, 4 May 2018 08:26:41 +0900 Subject: [PATCH v2] x86/kexec: avoid double free_page() upon do_kexec_load() failure. syzbot is reporting crashes after memory

Re: [PATCH 02/10] staging: lustre: make struct lu_site_bkt_data private

On Wed, May 02 2018, James Simmons wrote: >> This data structure only needs to be public so that >> various modules can access a wait queue to wait for object >> destruction. >> If we provide a function to get the wait queue, rather than the >> whole bucket, the structure can be made private. >>

[PATCH v2] x86/kexec: avoid double free_page() upon do_kexec_load() failure.

>From 91a78abed036e1662b11cb54ae6300864e17b709 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Fri, 4 May 2018 08:26:41 +0900 Subject: [PATCH v2] x86/kexec: avoid double free_page() upon do_kexec_load() failure. syzbot is reporting crashes after memory allocation failure inside

Re: [PATCH 02/10] staging: lustre: make struct lu_site_bkt_data private

On Wed, May 02 2018, James Simmons wrote: >> This data structure only needs to be public so that >> various modules can access a wait queue to wait for object >> destruction. >> If we provide a function to get the wait queue, rather than the >> whole bucket, the structure can be made private. >>

Re: [PATCH 4/9] firmware: use () to terminate kernel-doc function names

On Mon, Apr 23, 2018 at 04:12:00PM -0400, Andres Rodriguez wrote: > The kernel-doc spec dictates a function name ends in (). > > Signed-off-by: Andres Rodriguez > Acked-by: Randy Dunlap 0-day never got back to me about my full sweep API rename so I

Re: [PATCH 4/9] firmware: use () to terminate kernel-doc function names

On Mon, Apr 23, 2018 at 04:12:00PM -0400, Andres Rodriguez wrote: > The kernel-doc spec dictates a function name ends in (). > > Signed-off-by: Andres Rodriguez > Acked-by: Randy Dunlap 0-day never got back to me about my full sweep API rename so I think your changes are best to go in first,

Re: [PATCH 3/9] firmware: add kernel-doc for enum fw_opt

On Mon, Apr 23, 2018 at 04:11:59PM -0400, Andres Rodriguez wrote: > Some basic definitions for the FW_OPT_* values > > v2: Documentation corrections from Luis. Likewise. > Signed-off-by: Andres Rodriguez > --- > drivers/base/firmware_loader/firmware.h | 20

Re: [PATCH 3/9] firmware: add kernel-doc for enum fw_opt

On Mon, Apr 23, 2018 at 04:11:59PM -0400, Andres Rodriguez wrote: > Some basic definitions for the FW_OPT_* values > > v2: Documentation corrections from Luis. Likewise. > Signed-off-by: Andres Rodriguez > --- > drivers/base/firmware_loader/firmware.h | 20 > 1 file

Re: [PATCH 2/9] firmware: wrap FW_OPT_* into an enum

On Mon, Apr 23, 2018 at 04:11:58PM -0400, Andres Rodriguez wrote: > This should let us associate enum kdoc to these values. > > v2: use BIT() macro No need to keep the changelog of series here, best to put them below as I note. > > Signed-off-by: Andres Rodriguez > ---

Re: [PATCH 2/9] firmware: wrap FW_OPT_* into an enum

On Mon, Apr 23, 2018 at 04:11:58PM -0400, Andres Rodriguez wrote: > This should let us associate enum kdoc to these values. > > v2: use BIT() macro No need to keep the changelog of series here, best to put them below as I note. > > Signed-off-by: Andres Rodriguez > --- Here is good to add

Re: [PATCH] async_pq: Remove VLA usage

On Thu, May 3, 2018 at 3:57 PM, Kyle Spiers wrote: > In the quest to remove VLAs from the kernel[1], this moves the > allocation of coefs and blocks from the stack to being kmalloc()ed. > > [1] https://lkml.org/lkml/2018/3/7/621 > > Signed-off-by: Kyle Spiers

Re: [PATCH] async_pq: Remove VLA usage

On Thu, May 3, 2018 at 3:57 PM, Kyle Spiers wrote: > In the quest to remove VLAs from the kernel[1], this moves the > allocation of coefs and blocks from the stack to being kmalloc()ed. > > [1] https://lkml.org/lkml/2018/3/7/621 > > Signed-off-by: Kyle Spiers Reviewed-by: Kees Cook Thanks for

[PATCH v2 3/4] mm: add find_alloc_contig_pages() interface

find_alloc_contig_pages() is a new interface that attempts to locate and allocate a contiguous range of pages. It is provided as a more convenient interface than alloc_contig_range() which is currently used by CMA and gigantic huge pages. When attempting to allocate a range of pages, migration

[PATCH v2 3/4] mm: add find_alloc_contig_pages() interface

find_alloc_contig_pages() is a new interface that attempts to locate and allocate a contiguous range of pages. It is provided as a more convenient interface than alloc_contig_range() which is currently used by CMA and gigantic huge pages. When attempting to allocate a range of pages, migration

Re: [PATCH 1/9] firmware: some documentation fixes

On Mon, Apr 23, 2018 at 04:11:57PM -0400, Andres Rodriguez wrote: > Including: > - Fixup outdated kernel-doc paths > - Slightly too short title underline > - Some typos > > Signed-off-by: Andres Rodriguez This already got merged.

[PATCH v2 1/4] mm: change type of free_contig_range(nr_pages) to unsigned long

free_contig_range() is currently defined as: void free_contig_range(unsigned long pfn, unsigned nr_pages); change to, void free_contig_range(unsigned long pfn, unsigned long nr_pages); Some callers are passing a truncated unsigned long today. It is highly unlikely that these values will overflow

Re: [PATCH 1/9] firmware: some documentation fixes

On Mon, Apr 23, 2018 at 04:11:57PM -0400, Andres Rodriguez wrote: > Including: > - Fixup outdated kernel-doc paths > - Slightly too short title underline > - Some typos > > Signed-off-by: Andres Rodriguez This already got merged.

[PATCH v2 1/4] mm: change type of free_contig_range(nr_pages) to unsigned long

free_contig_range() is currently defined as: void free_contig_range(unsigned long pfn, unsigned nr_pages); change to, void free_contig_range(unsigned long pfn, unsigned long nr_pages); Some callers are passing a truncated unsigned long today. It is highly unlikely that these values will overflow

[PATCH v2 4/4] mm/hugetlb: use find_alloc_contig_pages() to allocate gigantic pages

Use the new find_alloc_contig_pages() interface for the allocation of gigantic pages and remove associated code in hugetlb.c. Signed-off-by: Mike Kravetz --- mm/hugetlb.c | 87 +--- 1 file changed, 6 insertions(+),

[PATCH v2 2/4] mm: check for proper migrate type during isolation

The routine start_isolate_page_range and alloc_contig_range have comments saying that migratetype must be either MIGRATE_MOVABLE or MIGRATE_CMA. However, this is not enforced. What is important is that that all pageblocks in the range are of type migratetype. This is because blocks will be set

[PATCH v2 2/4] mm: check for proper migrate type during isolation

The routine start_isolate_page_range and alloc_contig_range have comments saying that migratetype must be either MIGRATE_MOVABLE or MIGRATE_CMA. However, this is not enforced. What is important is that that all pageblocks in the range are of type migratetype. This is because blocks will be set

[PATCH v2 4/4] mm/hugetlb: use find_alloc_contig_pages() to allocate gigantic pages

Use the new find_alloc_contig_pages() interface for the allocation of gigantic pages and remove associated code in hugetlb.c. Signed-off-by: Mike Kravetz --- mm/hugetlb.c | 87 +--- 1 file changed, 6 insertions(+), 81 deletions(-) diff

[PATCH v2 0/4] Interface for higher order contiguous allocations

A respin of of the series to address these issues: - fix issues found by kbuild - find_alloc_contig_pages() should take nr_pages as argument instead of page order (Vlastimil and Michal). - Cleaned up migratetype handling (Vlastimil and Michal). - Use pfn_to_online_page instead of pfn_to_page as

[PATCH v2 0/4] Interface for higher order contiguous allocations

A respin of of the series to address these issues: - fix issues found by kbuild - find_alloc_contig_pages() should take nr_pages as argument instead of page order (Vlastimil and Michal). - Cleaned up migratetype handling (Vlastimil and Michal). - Use pfn_to_online_page instead of pfn_to_page as

Re: [alsa-devel] [PATCH v7 01/24] soc: qcom dt-bindings: Add APR bus bindings

On 5/1/2018 5:07 AM, Srinivas Kandagatla wrote: This patch add dt bindings for Qualcomm APR (Asynchronous Packet Router) bus driver. This bus is used for communicating with DSP which provides audio and various other services to cpu. Signed-off-by: Srinivas Kandagatla

Re: [alsa-devel] [PATCH v7 01/24] soc: qcom dt-bindings: Add APR bus bindings

On 5/1/2018 5:07 AM, Srinivas Kandagatla wrote: This patch add dt bindings for Qualcomm APR (Asynchronous Packet Router) bus driver. This bus is used for communicating with DSP which provides audio and various other services to cpu. Signed-off-by: Srinivas Kandagatla Reviewed-by: Rob Herring

Re: [PATCH v5 2/5] efi: Add embedded peripheral firmware support

Please Cc andre...@gmail.com on future patches. On Sun, Apr 29, 2018 at 11:35:55AM +0200, Hans de Goede wrote: > Just like with PCI options ROMs, which we save in the setup_efi_pci* > functions from arch/x86/boot/compressed/eboot.c, the EFI code / ROM itself > sometimes may contain data which is

Re: [PATCH v5 2/5] efi: Add embedded peripheral firmware support

Please Cc andre...@gmail.com on future patches. On Sun, Apr 29, 2018 at 11:35:55AM +0200, Hans de Goede wrote: > Just like with PCI options ROMs, which we save in the setup_efi_pci* > functions from arch/x86/boot/compressed/eboot.c, the EFI code / ROM itself > sometimes may contain data which is

Re: [PATCH v5 4/6] x86/microcode/AMD: Check microcode container data in the late loader

On 03.05.2018 12:01, Borislav Petkov wrote: > On Wed, May 02, 2018 at 02:47:39AM +0200, Maciej S. Szmigiero wrote: >> On 01.05.2018 22:03, Borislav Petkov wrote: >>> On Tue, May 01, 2018 at 06:19:56PM +0200, Maciej S. Szmigiero wrote: -EINVAL cast to unsigned int is 4294967274 and this value

Re: [PATCH v5 4/6] x86/microcode/AMD: Check microcode container data in the late loader

On 03.05.2018 12:01, Borislav Petkov wrote: > On Wed, May 02, 2018 at 02:47:39AM +0200, Maciej S. Szmigiero wrote: >> On 01.05.2018 22:03, Borislav Petkov wrote: >>> On Tue, May 01, 2018 at 06:19:56PM +0200, Maciej S. Szmigiero wrote: -EINVAL cast to unsigned int is 4294967274 and this value

RE: [PATCH 1/4] staging: lustre: obdclass: change spinlock of key to rwlock

On Thu, May 03 2018, David Laight wrote: > From: James Simmons >> Sent: 02 May 2018 19:22 >> From: Li Xi >> >> Most of the time, keys are never changed. So rwlock might be >> better for the concurrency of key read. > > OTOH unless there is contention on the spin lock during reads

RE: [PATCH 1/4] staging: lustre: obdclass: change spinlock of key to rwlock

On Thu, May 03 2018, David Laight wrote: > From: James Simmons >> Sent: 02 May 2018 19:22 >> From: Li Xi >> >> Most of the time, keys are never changed. So rwlock might be >> better for the concurrency of key read. > > OTOH unless there is contention on the spin lock during reads the >

Re: [PATCH] proc: use #pragma once

On 2018-05-04 00:42, Al Viro wrote: > On Fri, May 04, 2018 at 12:14:57AM +0200, Rasmus Villemoes wrote: > >> FWIW, it's not just removing some identifiers from cpp's hash tables, it >> also reduces I/O: Due to our header mess, we have some cyclic includes, >> e.g mm.h -> memremap.h -> mm.h. While

Re: [PATCH] proc: use #pragma once

On 2018-05-04 00:42, Al Viro wrote: > On Fri, May 04, 2018 at 12:14:57AM +0200, Rasmus Villemoes wrote: > >> FWIW, it's not just removing some identifiers from cpp's hash tables, it >> also reduces I/O: Due to our header mess, we have some cyclic includes, >> e.g mm.h -> memremap.h -> mm.h. While

Applied "ASoC: tas6424: Allow disabling auto diagnostics for faster power-on" to the asoc tree

The patch ASoC: tas6424: Allow disabling auto diagnostics for faster power-on has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the

Applied "ASoC: tas6424: Allow disabling auto diagnostics for faster power-on" to the asoc tree

The patch ASoC: tas6424: Allow disabling auto diagnostics for faster power-on has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the

Re: [PATCH v2 3/4] seccomp: Audit attempts to modify the actions_logged sysctl

On Thursday, May 3, 2018 6:36:18 PM EDT Tyler Hicks wrote: > On 05/03/2018 04:12 PM, Steve Grubb wrote: > > On Thursday, May 3, 2018 4:51:36 PM EDT Tyler Hicks wrote: > >> On 05/03/2018 03:48 PM, Paul Moore wrote: > >>> On Thu, May 3, 2018 at 4:42 PM, Steve Grubb wrote: >

Re: [PATCH v2 3/4] seccomp: Audit attempts to modify the actions_logged sysctl

On Thursday, May 3, 2018 6:36:18 PM EDT Tyler Hicks wrote: > On 05/03/2018 04:12 PM, Steve Grubb wrote: > > On Thursday, May 3, 2018 4:51:36 PM EDT Tyler Hicks wrote: > >> On 05/03/2018 03:48 PM, Paul Moore wrote: > >>> On Thu, May 3, 2018 at 4:42 PM, Steve Grubb wrote: > On Thursday, May 3,

Re: [PATCH 3/3] spi: meson-axg: add a linear clock divider support

On Thu, May 03, 2018 at 09:36:44PM +, Yixun Lan wrote: > From: Sunny Luo > > The SPICC controller in Meson-AXG SoC is capable of using > a linear clock divider to reach a much fine tuned range of clocks, > while the old controller only use a power of two clock divider,

Re: [PATCH 3/3] spi: meson-axg: add a linear clock divider support

On Thu, May 03, 2018 at 09:36:44PM +, Yixun Lan wrote: > From: Sunny Luo > > The SPICC controller in Meson-AXG SoC is capable of using > a linear clock divider to reach a much fine tuned range of clocks, > while the old controller only use a power of two clock divider, > result at a more

Re: [PATCH 1/3] spi: meson-axg: support MAX 80M clock

On Thu, May 03, 2018 at 09:36:42PM +, Yixun Lan wrote: > static const struct of_device_id meson_spicc_of_match[] = { > - { .compatible = "amlogic,meson-gx-spicc", }, > - { .compatible = "amlogic,meson-axg-spicc", }, > + { > + .compatible =

Re: [PATCH 1/3] spi: meson-axg: support MAX 80M clock

On Thu, May 03, 2018 at 09:36:42PM +, Yixun Lan wrote: > static const struct of_device_id meson_spicc_of_match[] = { > - { .compatible = "amlogic,meson-gx-spicc", }, > - { .compatible = "amlogic,meson-axg-spicc", }, > + { > + .compatible =

[PATCH v3 2/4] random: Return nbytes filled from hw RNG

Currently the function get_random_bytes_arch() has return value 'void'. If the hw RNG fails we currently fall back to using get_random_bytes(). This defeats the purpose of requesting random material from the hw RNG in the first place. There are currently no intree users of

[PATCH v3 2/4] random: Return nbytes filled from hw RNG

Currently the function get_random_bytes_arch() has return value 'void'. If the hw RNG fails we currently fall back to using get_random_bytes(). This defeats the purpose of requesting random material from the hw RNG in the first place. There are currently no intree users of

Re: [Ksummit-discuss] bug-introducing patches

* Mark Brown [180503 22:44]: > On Wed, May 02, 2018 at 08:52:29PM -0700, Guenter Roeck wrote: > > > As for -next, me and others stopped reporting bugs in it, because when we do > > we tend to get flamed for the "noise". Is anyone aware (or cares) that mips > > and nds32

Re: [Ksummit-discuss] bug-introducing patches

* Mark Brown [180503 22:44]: > On Wed, May 02, 2018 at 08:52:29PM -0700, Guenter Roeck wrote: > > > As for -next, me and others stopped reporting bugs in it, because when we do > > we tend to get flamed for the "noise". Is anyone aware (or cares) that mips > > and nds32 images don't build ?

[PATCH v3 4/4] vsprintf: Add command line option debug_early_boot

Currently printing [hashed] pointers requires either a hw RNG or enough entropy to be available. Early in the boot sequence these conditions may not be met resulting in a dummy string '(ptrval)' being printed. This makes debugging the early boot sequence difficult. We can relax the

[PATCH v3 4/4] vsprintf: Add command line option debug_early_boot

Currently printing [hashed] pointers requires either a hw RNG or enough entropy to be available. Early in the boot sequence these conditions may not be met resulting in a dummy string '(ptrval)' being printed. This makes debugging the early boot sequence difficult. We can relax the

[PATCH v3 1/4] random: Fix whitespace pre random-bytes work

There are a couple of whitespace issues around the function get_random_bytes_arch(). In preparation for patching this function let's clean them up. Signed-off-by: Tobin C. Harding Acked-by: Theodore Ts'o --- drivers/char/random.c | 3 +-- 1 file changed, 1

[PATCH v3 1/4] random: Fix whitespace pre random-bytes work

There are a couple of whitespace issues around the function get_random_bytes_arch(). In preparation for patching this function let's clean them up. Signed-off-by: Tobin C. Harding Acked-by: Theodore Ts'o --- drivers/char/random.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff

[PATCH v3 3/4] vsprintf: Use hw RNG for ptr_key

Currently we must wait for enough entropy to become available before hashed pointers can be printed. We can remove this wait by using the hw RNG if available. Use hw RNG to get keying material. Suggested-by: Kees Cook Signed-off-by: Tobin C. Harding ---

[PATCH v3 0/4] enable early printing of hashed pointers

Currently if an attempt is made to print a pointer before there is enough entropy then '(ptrval)' is printed. This makes debugging stack traces during early boot difficult. It was observed that we can relax the requirement for cryptographically secure hashing when debugging while still

[PATCH v3 3/4] vsprintf: Use hw RNG for ptr_key

Currently we must wait for enough entropy to become available before hashed pointers can be printed. We can remove this wait by using the hw RNG if available. Use hw RNG to get keying material. Suggested-by: Kees Cook Signed-off-by: Tobin C. Harding --- lib/vsprintf.c | 19

[PATCH v3 0/4] enable early printing of hashed pointers

Currently if an attempt is made to print a pointer before there is enough entropy then '(ptrval)' is printed. This makes debugging stack traces during early boot difficult. It was observed that we can relax the requirement for cryptographically secure hashing when debugging while still

Re: [PATCH 0/3] kexec: limit kexec_load syscall

Mimi Zohar writes: > On Thu, 2018-05-03 at 16:38 -0500, Eric W. Biederman wrote: >> Mimi Zohar writes: >> >> > [Cc'ing Kees and kernel-hardening] >> > >> > On Thu, 2018-05-03 at 15:13 -0500, Eric W. Biederman wrote: >> >> Mimi Zohar

Re: [PATCH 0/3] kexec: limit kexec_load syscall

Mimi Zohar writes: > On Thu, 2018-05-03 at 16:38 -0500, Eric W. Biederman wrote: >> Mimi Zohar writes: >> >> > [Cc'ing Kees and kernel-hardening] >> > >> > On Thu, 2018-05-03 at 15:13 -0500, Eric W. Biederman wrote: >> >> Mimi Zohar writes: >> >> >> >> > In environments that require the

Re: [PATCH v5 2/5] efi: Add embedded peripheral firmware support

On Thu, 2018-05-03 at 22:23 +, Luis R. Rodriguez wrote: > On Tue, May 01, 2018 at 03:27:27PM -0400, Mimi Zohar wrote: > > On Tue, 2018-05-01 at 21:11 +0200, Hans de Goede wrote: > > > Only the pre hook? I believe the post-hook should still be called too, > > > right? So that we've hashes of

Re: [PATCH v5 2/5] efi: Add embedded peripheral firmware support

On Thu, 2018-05-03 at 22:23 +, Luis R. Rodriguez wrote: > On Tue, May 01, 2018 at 03:27:27PM -0400, Mimi Zohar wrote: > > On Tue, 2018-05-01 at 21:11 +0200, Hans de Goede wrote: > > > Only the pre hook? I believe the post-hook should still be called too, > > > right? So that we've hashes of

Re: [PATCH 01/10] crypto: aead - allow to allocate AEAD requests on the stack

On Thu, May 03, 2018 at 02:23:30PM +0200, 'Antoine Tenart' wrote: > > I was expecting this question :) The thing is this define looks *a lot* > like the ones defined in other places in the crypto framework, such as > SKCIPHER_REQUEST_ON_STACK and AHASH_REQUEST_ON_STACK. Those haven't been >

Re: [PATCH 2/2] mm: Add kvmalloc_ab_c and kvzalloc_struct

On 2018-05-01 19:00, Kees Cook wrote: > On Mon, Apr 30, 2018 at 2:29 PM, Rasmus Villemoes > wrote: >> >> gcc 5.1+ (I think) have the __builtin_OP_overflow checks that should >> generate reasonable code. Too bad there's no completely generic >>

Re: [PATCH 01/10] crypto: aead - allow to allocate AEAD requests on the stack

On Thu, May 03, 2018 at 02:23:30PM +0200, 'Antoine Tenart' wrote: > > I was expecting this question :) The thing is this define looks *a lot* > like the ones defined in other places in the crypto framework, such as > SKCIPHER_REQUEST_ON_STACK and AHASH_REQUEST_ON_STACK. Those haven't been >

Re: [PATCH 2/2] mm: Add kvmalloc_ab_c and kvzalloc_struct

On 2018-05-01 19:00, Kees Cook wrote: > On Mon, Apr 30, 2018 at 2:29 PM, Rasmus Villemoes > wrote: >> >> gcc 5.1+ (I think) have the __builtin_OP_overflow checks that should >> generate reasonable code. Too bad there's no completely generic >> check_all_ops_in_this_expression(a+b*c+d/e,

[PATCH] async_pq: Remove VLA usage

In the quest to remove VLAs from the kernel[1], this moves the allocation of coefs and blocks from the stack to being kmalloc()ed. [1] https://lkml.org/lkml/2018/3/7/621 Signed-off-by: Kyle Spiers --- crypto/async_tx/async_pq.c | 18 ++

[PATCH] async_pq: Remove VLA usage

In the quest to remove VLAs from the kernel[1], this moves the allocation of coefs and blocks from the stack to being kmalloc()ed. [1] https://lkml.org/lkml/2018/3/7/621 Signed-off-by: Kyle Spiers --- crypto/async_tx/async_pq.c | 18 ++ crypto/async_tx/raid6test.c | 8

<    1   2   3   4   5   6   7   8   9   10   >