[RFC PATCH] powerpc: udbg: export udbg_putc

2023-05-12 Thread Randy Dunlap
In a randconfig with CONFIG_SERIAL_CPM=m and CONFIG_PPC_EARLY_DEBUG_CPM=y, there is a build error: ERROR: modpost: "udbg_putc" [drivers/tty/serial/cpm_uart/cpm_uart.ko] undefined! The build can be fixed by exporting "udbg_putc" in udbg.c. OTOH, maybe something like this is more appropriate in

[PATCH v2] powerpc/embedded6xx: select MPC10X_BRIDGE only if PCI is set

2023-05-12 Thread Randy Dunlap
When CONFIG_SMP is not set, CONFIG_BROKEN_ON_SMP is set, and CONFIG_PCI is not set, there can be a kconfig warning: WARNING: unmet direct dependencies detected for PPC_INDIRECT_PCI Depends on [n]: PCI [=n] Selected by [y]: - MPC10X_BRIDGE [=y] To fix that, make the selects of MPC10X_BRIDGE

Re: [PATCH v2] soc/fsl/qe: fix usb.c build errors

2023-05-12 Thread Randy Dunlap
Any comments on this patch? I am still seeing this build error. On 4/9/23 18:12, Randy Dunlap wrote: > Fix build errors in soc/fsl/qe/usb.c when QUICC_ENGINE is not set. > This happens when PPC_EP88XC is set, which selects CPM1 & CPM. > When CPM is set, USB_FSL_QE can be set without QUICC_ENGINE

Re: Fwd: Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-12 Thread Greg Kroah-Hartman
On Fri, May 12, 2023 at 03:25:47PM +, Christophe Leroy wrote: > > > Le 12/05/2023 à 17:16, Christophe Leroy a écrit : > > > > > > Le 11/05/2023 à 19:25, Niccolò Belli a écrit : > >> [Vous ne recevez pas souvent de courriers de > >> darkba...@linuxsystems.it. D?couvrez pourquoi ceci est

Re: Fwd: Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-12 Thread Niccolò Belli
Il 2023-05-12 10:32 Bagas Sanjaya ha scritto: #regzbot introduced: f4f3b7dedbe849 #regzbot link: https://gitlab.freedesktop.org/drm/amd/-/issues/2553 It doesn't look like the aforementioned patch made its way into 6.3 yet: niko@talos2 ~/devel/linux-stable $ git branch * linux-6.3.y master

Re: [PATCH v8 0/7] Add pci_dev_for_each_resource() helper and update users

2023-05-12 Thread Bjorn Helgaas
On Fri, May 12, 2023 at 01:56:29PM +0300, Andy Shevchenko wrote: > On Tue, May 09, 2023 at 01:21:22PM -0500, Bjorn Helgaas wrote: > > On Tue, Apr 04, 2023 at 11:11:01AM -0500, Bjorn Helgaas wrote: > > > On Thu, Mar 30, 2023 at 07:24:27PM +0300, Andy Shevchenko wrote: > > > > Provide two new helper

Re: [PATCH v8 1/3] riscv: Introduce CONFIG_RELOCATABLE

2023-05-12 Thread Palmer Dabbelt
On Thu, 11 May 2023 11:18:23 PDT (-0700), sch...@linux-m68k.org wrote: On Mai 09 2023, Alexandre Ghiti wrote: On 5/9/23 21:07, Andreas Schwab wrote: That does not work with UEFI booting: Loading Linux 6.4.0-rc1-1.g668187d-default ... Loading initial ramdisk ... Unhandled exception:

Re: [PATCH 1/3] kcsan: Don't expect 64 bits atomic builtins from 32 bits architectures

2023-05-12 Thread Christophe Leroy
Le 12/05/2023 à 18:09, Marco Elver a écrit : > On Fri, 12 May 2023 at 17:31, Christophe Leroy > wrote: >> >> Activating KCSAN on a 32 bits architecture leads to the following >> link-time failure: >> >> LD .tmp_vmlinux.kallsyms1 >>powerpc64-linux-ld: kernel/kcsan/core.o: in

[Bug 217427] Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

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

Re: [PATCH 3/3] xtensa: Remove 64 bits atomic builtins stubs

2023-05-12 Thread Max Filippov
On Fri, May 12, 2023 at 8:31 AM Christophe Leroy wrote: > > The stubs were provided by commit 725aea873261 ("xtensa: enable KCSAN") > to make linker happy allthought they are not meant to be used at all. > > KCSAN core has been fixed to not require them anymore on > 32 bits architectures. > >

Re: [PATCH 0/3] Extend KCSAN to all powerpc

2023-05-12 Thread Marco Elver
On Fri, 12 May 2023 at 17:31, Christophe Leroy wrote: > > This series enables KCSAN on all powerpc. > > To do this, a fix is required to KCSAN core. > > Once that fix is done, the stubs can also be removed from xtensa. > > It would be nice if patch 1 could go in v6.4 as a fix, then patches 2 and

Re: [PATCH 1/3] kcsan: Don't expect 64 bits atomic builtins from 32 bits architectures

2023-05-12 Thread Marco Elver
On Fri, 12 May 2023 at 17:31, Christophe Leroy wrote: > > Activating KCSAN on a 32 bits architecture leads to the following > link-time failure: > > LD .tmp_vmlinux.kallsyms1 > powerpc64-linux-ld: kernel/kcsan/core.o: in function `__tsan_atomic64_load': > kernel/kcsan/core.c:1273:

[PATCH 2/3] powerpc/{32,book3e}: kcsan: Extend KCSAN Support

2023-05-12 Thread Christophe Leroy
From: Rohan McLure Enable HAVE_ARCH_KCSAN on all powerpc platforms, permitting use of the kernel concurrency sanitiser through the CONFIG_KCSAN_* kconfig options. Boots and passes selftests on 32-bit and 64-bit platforms. See documentation in Documentation/dev-tools/kcsan.rst for more

[PATCH 0/3] Extend KCSAN to all powerpc

2023-05-12 Thread Christophe Leroy
This series enables KCSAN on all powerpc. To do this, a fix is required to KCSAN core. Once that fix is done, the stubs can also be removed from xtensa. It would be nice if patch 1 could go in v6.4 as a fix, then patches 2 and 3 could be handled separately in each architecture in next cycle.

[PATCH 3/3] xtensa: Remove 64 bits atomic builtins stubs

2023-05-12 Thread Christophe Leroy
The stubs were provided by commit 725aea873261 ("xtensa: enable KCSAN") to make linker happy allthought they are not meant to be used at all. KCSAN core has been fixed to not require them anymore on 32 bits architectures. Then they can be removed. Signed-off-by: Christophe Leroy ---

[PATCH 1/3] kcsan: Don't expect 64 bits atomic builtins from 32 bits architectures

2023-05-12 Thread Christophe Leroy
Activating KCSAN on a 32 bits architecture leads to the following link-time failure: LD .tmp_vmlinux.kallsyms1 powerpc64-linux-ld: kernel/kcsan/core.o: in function `__tsan_atomic64_load': kernel/kcsan/core.c:1273: undefined reference to `__atomic_load_8' powerpc64-linux-ld:

Re: Fwd: Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-12 Thread Christophe Leroy
Le 12/05/2023 à 17:16, Christophe Leroy a écrit : > > > Le 11/05/2023 à 19:25, Niccolò Belli a écrit : >> [Vous ne recevez pas souvent de courriers de >> darkba...@linuxsystems.it. D?couvrez pourquoi ceci est important ? >> https://aka.ms/LearnAboutSenderIdentification ] >> >> Il 2023-05-12

Re: Fwd: Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-12 Thread Alex Deucher
On Fri, May 12, 2023 at 11:16 AM Christophe Leroy wrote: > > > > Le 11/05/2023 à 19:25, Niccolò Belli a écrit : > > [Vous ne recevez pas souvent de courriers de darkba...@linuxsystems.it. > > D?couvrez pourquoi ceci est important ? > > https://aka.ms/LearnAboutSenderIdentification ] > > > > Il

Re: Fwd: Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-12 Thread Christophe Leroy
Le 11/05/2023 à 19:25, Niccolò Belli a écrit : > [Vous ne recevez pas souvent de courriers de darkba...@linuxsystems.it. > D?couvrez pourquoi ceci est important ? > https://aka.ms/LearnAboutSenderIdentification ] > > Il 2023-05-12 10:32 Bagas Sanjaya ha scritto: >> #regzbot introduced:

Re: [PATCH v4 12/17] watchdog/hardlockup: Have the perf hardlockup use __weak functions more cleanly

2023-05-12 Thread Petr Mladek
On Thu 2023-05-04 15:13:44, Douglas Anderson wrote: > The fact that there watchdog_hardlockup_enable(), > watchdog_hardlockup_disable(), and watchdog_hardlockup_probe() are > declared __weak means that the configured hardlockup detector can > define non-weak versions of those functions if it needs

Re: [PATCH v4 11/17] watchdog/hardlockup: Rename some "NMI watchdog" constants/function

2023-05-12 Thread Petr Mladek
On Fri 2023-05-05 13:06:41, Nicholas Piggin wrote: > On Fri May 5, 2023 at 8:13 AM AEST, Douglas Anderson wrote: > > Do a search and replace of: > > - NMI_WATCHDOG_ENABLED => HARD_WATCHDOG_ENABLED > > - watchdog_nmi_ => watchdog_hardlockup_ > > These are just making prefixes inconsistent again.

Re: [PATCH v8 0/7] Add pci_dev_for_each_resource() helper and update users

2023-05-12 Thread Andy Shevchenko
On Tue, May 09, 2023 at 01:21:22PM -0500, Bjorn Helgaas wrote: > On Tue, Apr 04, 2023 at 11:11:01AM -0500, Bjorn Helgaas wrote: > > On Thu, Mar 30, 2023 at 07:24:27PM +0300, Andy Shevchenko wrote: > > > Provide two new helper macros to iterate over PCI device resources and > > > convert users. >

Re: Fwd: Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)

2023-05-12 Thread Bagas Sanjaya
On 5/11/23 15:06, Bagas Sanjaya wrote: > Hi, > > I notice a regression report on bugzilla ([1]). As many developers > don't keep an eye on it, I decide to forward it by email. > > Quoting from it: > >> darkbasic 2023-05-10 13:36:37 UTC >> >> I'm using Gentoo Linux on a Raptor CS Talos 2