Re: [PATCH] PCI/ERR: handle disconnected devices in report_error_detected

2022-06-07 Thread Sathyanarayanan Kuppuswamy
Hi, On 6/1/22 12:40 AM, Christoph Hellwig wrote: When a device is already unplugged by pciehp by the time that the AER handler is invoked, the PCIe device will lready be in the /s/lready/already pci_channel_io_perm_failure state. In that case we should simply return

Re: [PATCH] kprobes: Enable tracing for mololithic kernel images

2022-06-07 Thread Guo Ren
on , Masahiro Yamada , Sami Tolvanen , "Naveen N. Rao" , Marco Elver , Kees Cook , Steven Rostedt , Nathan Chancellor , "Russell King \(Oracle\)" , Mark Brown , Borislav Petkov , Alexander Egorenkov , Thomas Bogendoerfer , Parisc List , Nathaniel McCallum , Dmitry Torokhov , "David S.

[PATCH] kprobes: Enable tracing for mololithic kernel images

2022-06-07 Thread Jarkko Sakkinen
nel.org>, Jarkko Sakkinen , Sami Tolvanen , "Naveen N. Rao" , Marco Elver , Kees Cook , Steven Rostedt , Nathan Chancellor , "Russell King \(Oracle\)" , Mark Brown , Borislav Petkov , Alexander Egorenkov , Thomas Bogendoerfer , linux-par...@vger.kernel.org, Nathaniel McCallum , Dmitry

[PATCH] backlight: Use backlight helper

2022-06-07 Thread Stephen Kitt
backlight_properties.fb_blank is deprecated. The states it represents are handled by other properties; but instead of accessing those properties directly, drivers should use the helpers provided by backlight.h. Instead of retrieving the backlight brightness in struct backlight_properties

Re: [PATCH 0/6] phase out CONFIG_VIRT_TO_BUS

2022-06-07 Thread Martyn Welch
On Mon, 6 Jun 2022 at 10:25, Greg Kroah-Hartman wrote: > > On Mon, Jun 06, 2022 at 10:41:03AM +0200, Arnd Bergmann wrote: > > From: Arnd Bergmann > > > > The virt_to_bus/bus_to_virt interface has been deprecated for > > decades. After Jakub Kicinski put a lot of work into cleaning out the > >

Re: [PATCH v3] of: check previous kernel's ima-kexec-buffer against memory bounds

2022-06-07 Thread Rob Herring
On Tue, 31 May 2022 09:44:46 +0530, Vaibhav Jain wrote: > Presently ima_get_kexec_buffer() doesn't check if the previous kernel's > ima-kexec-buffer lies outside the addressable memory range. This can result > in a kernel panic if the new kernel is booted with 'mem=X' arg and the >

Re: [PATCH v1] kernel/reboot: Fix powering off using a non-syscall code paths

2022-06-07 Thread Rafael J. Wysocki
On Mon, Jun 6, 2022 at 6:57 PM Dmitry Osipenko wrote: > > There are other methods of powering off machine than the reboot syscall. > Previously we missed to coved those methods and it created power-off > regression for some machines, like the PowerPC e500. Fix this problem > by moving the legacy

Re: outside array bounds error on ppc64_defconfig, GCC 12.1.0

2022-06-07 Thread Segher Boessenkool
On Tue, Jun 07, 2022 at 02:23:25PM +, David Laight wrote: > > I don't see a really simple fix. I tried clamping the size parameter to > > do_byte_reverse() with max(), but that didn't work :/ > > I had a quick look at the code - it is somewhat horrid! > Not really surprising the compiler is

Re: outside array bounds error on ppc64_defconfig, GCC 12.1.0

2022-06-07 Thread Segher Boessenkool
On Tue, Jun 07, 2022 at 12:05:18PM +1000, Michael Ellerman wrote: > > arch/powerpc/lib/sstep.c:287:23: error: array subscript [3, 4] is outside > > array bounds of 'union [1]' [-Werror=array-bounds] > > 287 | up[3] = tmp; > > | ~~^ > > This happens

RE: outside array bounds error on ppc64_defconfig, GCC 12.1.0

2022-06-07 Thread David Laight
From: Michael Ellerman > Sent: 07 June 2022 03:05 > > Bagas Sanjaya writes: > > Hi, > > > > I'm trying to verify Drop ppc_inst_as_str() patch on [1] by performing > > ppc64_defconfig build with powerpc64-unknown-linux-gnu-gcc (GCC 12.1.0). > > The patch is applied on top of powerpc tree, next

Re: [PATCH 6/6] arch/*/: remove CONFIG_VIRT_TO_BUS

2022-06-07 Thread Michael Ellerman
Arnd Bergmann writes: > diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig > index be68c1f02b79..48e1aa0536b6 100644 > --- a/arch/powerpc/Kconfig > +++ b/arch/powerpc/Kconfig > @@ -277,7 +277,6 @@ config PPC > select SYSCTL_EXCEPTION_TRACE > select THREAD_INFO_IN_TASK >

Re: [PATCH] ASoC: fsl_sai: Add support for i.MX8MN

2022-06-07 Thread Mark Brown
On Tue, 31 May 2022 11:02:03 +0800, Shengjiu Wang wrote: > The SAI module on i.MX8MN is almost same as i.MX8MP, > So reuse same soc data as i.MX8MP. > > Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: fsl_sai: Add support for

Re: (subset) [PATCH 1/3] ASoC: fsl_sai: use local device pointer

2022-06-07 Thread Mark Brown
On Wed, 1 Jun 2022 11:23:40 +0200, Marco Felsch wrote: > Use a local variable to dereference the device pointer once and use the > local variable in further calls. No functional changes. > > Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks!

Re: [PATCH V4] ASoC: fsl_xcvr:Fix unbalanced pm_runtime_enable in fsl_xcvr_probe

2022-06-07 Thread Mark Brown
On Thu, 2 Jun 2022 15:20:24 +0800, zhangqilong wrote: > a) Add missing pm_runtime_disable() when probe error out. It could > avoid pm_runtime implementation complains when removing and probing > again the driver. > b) Add remove for missing pm_runtime_disable(). > > Fix:c590fa80b3928 ("ASoC:

Re: [PATCH] cxl: Fix refcount leak in cxl_calc_capp_routing

2022-06-07 Thread Frederic Barrat
On 05/06/2022 08:00, Miaoqian Lin wrote: of_get_next_parent() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. This function only calls of_node_put() in normal path, missing it in the error path. Add missing of_node_put() to avoid

[Bug 216090] GCC12: printk.h:446:44: error: using a dangling pointer to '__str'

2022-06-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=216090 Artem S. Tashkinov (a...@gmx.com) changed: What|Removed |Added Status|NEW |RESOLVED

Re: [PATCH 6/6] arch/*/: remove CONFIG_VIRT_TO_BUS

2022-06-07 Thread Geert Uytterhoeven
On Mon, Jun 6, 2022 at 11:10 AM Arnd Bergmann wrote: > From: Arnd Bergmann > > All architecture-independent users of virt_to_bus() and bus_to_virt() > have been fixed to use the dma mapping interfaces or have been > removed now. This means the definitions on most architectures, and the >