Re: [PATCH] misc: bcm-vk: Fix a couple error codes in probe()

On Wed, Feb 03, 2021 at 11:15:35AM -0800, Scott Branden wrote: > Thanks Dan, > > On 2021-02-03 6:42 a.m., Dan Carpenter wrote: > > These errors should return negative error codes instead of returning > > success. > Do you have a script running to report such issues or just manually reviewing > to

Re: [PATCH 09/11] x86/fault: Rename no_context() to kernelmode_fixup_or_oops()

On Wed, Feb 03, 2021 at 11:53:03AM -0800, Andy Lutomirski wrote: > I feel like that would be more obfuscated — then the function would > return without fixing anything for usermode faults, return after > fixing it for kernel mode faults, or oops. You practically pretty much have it already with

[PATCH RESEND] kernel: debug: fix typo issue

From: wengjianfeng change 'regster' to 'register'. Signed-off-by: wengjianfeng --- kernel/debug/gdbstub.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/debug/gdbstub.c b/kernel/debug/gdbstub.c index a77df59..e149a0a 100644 --- a/kernel/debug/gdbstub.c +++

Re: Linux 5.11-rc6 compile error

On Wed, Feb 3, 2021 at 11:58 AM Shuah Khan wrote: > > ld: arch/x86/built-in.a: member arch/x86/kernel/pci-swiotlb.o in archive > is not an object > make: *** [Makefile:1170: vmlinux] Error 1 That honestly sounds like something went wrong earlier - things like doing a system upgrade in the middle

Re: [PATCH] mm/mremap: fix BUILD_BUG_ON() error in get_extent

On Wed, Feb 03, 2021 at 11:48:40AM -0700, Nathan Chancellor wrote: > On Tue, Jan 12, 2021 at 12:16:34PM -0700, Nathan Chancellor wrote: > > On Wed, Dec 30, 2020 at 04:40:40PM +0100, Arnd Bergmann wrote: > > > From: Arnd Bergmann > > > > > > clang cannt evaluate this function argument at compile

Re: [PATCH 2/9] perf tools: Support the auxiliary event

Em Tue, Feb 02, 2021 at 12:09:06PM -0800, kan.li...@linux.intel.com escreveu: > From: Kan Liang > diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c > index c26ea822..c48f6de 100644 > --- a/tools/perf/util/evsel.c > +++ b/tools/perf/util/evsel.c > @@ -2689,6 +2689,9 @@ int

Re: [PATCH][RESEND] lib/vsprintf: make-printk-non-secret printks all addresses as unhashed

On Wed, Feb 03, 2021 at 12:58:41PM -0600, Timur Tabi wrote: > On 2/3/21 7:31 AM, Petr Mladek wrote: > > Also please make sure that lib/test_printf.c will work with > > the new option. > > As you suspected, it doesn't work: > > [ 206.966478] test_printf: loaded. > [ 206.966528] test_printf:

Re: [PATCH -next] RISCV: Add some depends for NUMA

On Wed, Feb 3, 2021 at 6:20 AM Kefeng Wang wrote: > > The numa feature is useless for riscv32 platform(MAXPHYSMEM_1GB if 32bit), > and it should depends on SMP feature, this also fix the build error, > > riscv64-buildroot-linux-gnu-ld: mm/page_alloc.o: in function `.L0 ': >

Linux 5.11-rc6 compile error

I am seeing the following compile error on Linux 5.11-rc6. No issues on 5.11.0-rc5 with the same config. ld: arch/x86/built-in.a: member arch/x86/kernel/pci-swiotlb.o in archive is not an object make: *** [Makefile:1170: vmlinux] Error 1 CONFIG_SWIOTLB_XEN=y CONFIG_SWIOTLB=y I can debug

Re: [PATCH 1/2] misc/pvpanic: split-up generic and platform dependent code

a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/Mihai-Carabas/misc-pvpanic-split-up-generic-and-platform-dependent-code/20210203-234431 base: https://git.kernel.org/pub/scm

[PATCH v2] platform/x86: Move all dell drivers to their own subdirectory

A user without a Dell system doesn't need to pick any of these drivers. Users with a Dell system can enable this submenu and all drivers behind it will be enabled. Suggested-by: Andy Shevchenko Signed-off-by: Mario Limonciello --- Changes from v1->v2: - Rename menu per Andy's suggestion -

Re: [PATCH 1/2] hwmon: lm75: Add NXP LM75A to of_match list

On 2/3/21 9:13 AM, Matwey V. Kornilov wrote: > > > сб, 30 янв. 2021 г. в 18:41, Guenter Roeck >: >> >> On 1/30/21 2:38 AM, Matwey V. Kornilov wrote: >> > NXP LM75A is compatible with original LM75A while it has improved >> > 11-bit precision. >> > >> >

Re: [PATCH] sched/fair: Rate limit calls to update_blocked_averages() for NOHZ

On Fri, Jan 29, 2021 at 06:27:27PM +0100, Vincent Guittot wrote: [...] > > update_blocked_averages with preempt and irq off is not a good thing > > because we don't manage the number of csf_rq to update and I'm going > > to provide a patchset for this > > The patch below moves the update of the

Re: memory_model.h:64:14: error: implicit declaration of function 'page_to_section'

On 2/3/21 7:51 AM, Naresh Kamboju wrote: > Linux next tag 20210203 the mips and sh builds failed due to below errors. > Following builds failed with gcc-8, gcc-9 and gcc-10, > - mips (cavium_octeon_defconfig) > - sh (defconfig) > - sh (shx3_defconfig) > > make --silent

Re: [PATCH 09/11] x86/fault: Rename no_context() to kernelmode_fixup_or_oops()

> On Feb 3, 2021, at 11:39 AM, Borislav Petkov wrote: > > On Sun, Jan 31, 2021 at 09:24:40AM -0800, Andy Lutomirski wrote: >> The name no_context() has never been very clear. It's only called for >> faults from kernel mode, so rename it and change the no-longer-useful >> user_mode(regs)

Re: [PATCH 0/6] Support second Image Signal Processor on rk3399

Hi Sebastian, Am Mittwoch, 3. Februar 2021, 19:14:22 CET schrieb Sebastian Fricke: > Hey Heiko, > > I have tested your patch set on my nanoPC-T4, here is a complete log > with: > - relevant kernel log entries > - system information > - media ctl output > - sysfs entry information > >

Re: [PATCH v2 2/2] dma-buf: heaps: Map system heap pages as managed by linux vm

On Wed, Feb 3, 2021 at 12:06 AM Christian König wrote: > > Am 03.02.21 um 03:02 schrieb Suren Baghdasaryan: > > On Tue, Feb 2, 2021 at 5:39 PM Minchan Kim wrote: > >> On Tue, Feb 02, 2021 at 04:31:34PM -0800, Suren Baghdasaryan wrote: > >>> Currently system heap maps its buffers with VM_PFNMAP

[GIT PULL] UML fixes for 5.11-rc7

Linus, The following changes since commit 4992eb41ab1b5d08479193afdc94f9678e5ded13: Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm (2021-01-26 11:10:14 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git

Re: [PATCH 10/11] x86/fault: Don't run fixups for SMAP violations

On Sun, Jan 31, 2021 at 09:24:41AM -0800, Andy Lutomirski wrote: > A SMAP-violating kernel access is not a recoverable condition. Imagine > kernel code that, outside of a uaccess region, dereferences a pointer to > the user range by accident. If SMAP is on, this will reliably generate > as an

Re: [PATCH v4 1/4] lib: vsprintf: scanf: Negative number must have field width > 1

On Wed, Feb 03, 2021 at 04:50:06PM +, Richard Fitzgerald wrote: > If a signed number field starts with a '-' the field width must be > 1, > or unlimited, to allow at least one digit after the '-'. > > This patch adds a check for this. If a signed field starts with '-' > and field_width == 1

Re: [PATCH v4 4/4] selftests: lib: Add wrapper script for test_scanf

On Wed, Feb 03, 2021 at 04:50:09PM +, Richard Fitzgerald wrote: > Adds a wrapper shell script for the test_scanf module. Acked-by: Andy Shevchenko > Signed-off-by: Richard Fitzgerald > Reviewed-by: Petr Mladek > --- > tools/testing/selftests/lib/Makefile | 2 +- >

Re: [PATCH v4 3/4] lib: test_scanf: Add tests for sscanf number conversion

On Wed, Feb 03, 2021 at 04:50:08PM +, Richard Fitzgerald wrote: > Adds test_sscanf to test various number conversion cases, as > number conversion was previously broken. > > This also tests the simple_strtoxxx() functions exported from > vsprintf.c. Cool! Acked-by: Andy Shevchenko >

Re: [PATCH v4 2/4] lib: vsprintf: Fix handling of number field widths in vsscanf

On Wed, Feb 03, 2021 at 04:50:07PM +, Richard Fitzgerald wrote: > The existing code attempted to handle numbers by doing a strto[u]l(), > ignoring the field width, and then repeatedly dividing to extract the > field out of the full converted value. If the string contains a run of > valid

Re: [PATCH 07/11] x86/fault: Split the OOPS code out from no_context()

On Wed, Feb 03, 2021 at 11:29:39AM -0800, Andy Lutomirski wrote: > That function is a lie. It tries to keep the system alive but it > doesn’t return if it “recovers”. Maybe I should add a comment? ... or rename it? That schedule() at the end, I dunno if that does anything since we're going to

Re: [PATCH v2 1/1] mm: Optimizing hugepage zeroing in arm64

On Wed, Feb 03, 2021 at 04:08:08PM +0530, Prathu Baronia wrote: >Hey Ira, >I looked at your below-mentioned patch and I agree that the >above-mentioned functions also need modification similar to >clear_user_highpage(). >Would it be okay with you if I send your patch again with

Re: [PATCH 09/11] x86/fault: Rename no_context() to kernelmode_fixup_or_oops()

On Sun, Jan 31, 2021 at 09:24:40AM -0800, Andy Lutomirski wrote: > The name no_context() has never been very clear. It's only called for > faults from kernel mode, so rename it and change the no-longer-useful > user_mode(regs) check to a WARN_ON_ONCE. > > Cc: Dave Hansen > Cc: Peter Zijlstra >

Re: [GIT PULL] tracing: Fixes for 5.11-rc5

The pull request you sent on Wed, 3 Feb 2021 09:51:19 -0500: > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git > trace-v5.11-rc5 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/dbc15d24f9fa6f25723ef750b65b98bfcd3d3910 Thank you! --

Re: [GIT PULL] platform-drivers-x86 for 5.11-3

The pull request you sent on Wed, 3 Feb 2021 11:23:52 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git > tags/platform-drivers-x86-v5.11-3 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/4aa2fb4ef799b01dd5d2dcc3970344a9a036c1f2

Re: [GIT PULL] arm64 fixes for 5.11-rc7

The pull request you sent on Wed, 3 Feb 2021 18:44:11 +: > git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/3afe9076a7c19140b789d144d0ba1e9be2db4265 Thank you! -- Deet-doot-dot, I am a

Re: [GIT PULL] gpio: fixes for v5.11-rc7

The pull request you sent on Wed, 3 Feb 2021 14:08:57 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git > tags/gpio-fixes-for-v5.11-rc7 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/40615974f88a918d01606ba27d75de2ff50b8d4e Thank you! --

Re: [PATCH] swiotlb: Validate bounce size in the sync/unmap path

On Wed, Feb 03, 2021 at 01:49:22PM +0100, Christoph Hellwig wrote: > On Mon, Jan 18, 2021 at 12:44:58PM +0100, Martin Radev wrote: > > Your comment makes sense but then that would require the cooperation > > of these vendors and the cloud providers to agree on something meaningful. > > I am also

Re: [PATCH 1/3] kvfree_rcu: Allocate a page for a single argument

On Mon, Feb 01, 2021 at 12:47:55PM +0100, Michal Hocko wrote: > On Fri 29-01-21 17:35:31, Uladzislau Rezki wrote: > > On Fri, Jan 29, 2021 at 09:56:29AM +0100, Michal Hocko wrote: > > > On Thu 28-01-21 19:02:37, Uladzislau Rezki wrote: > > > [...] > > > > >From

Re: [PATCH] platform/x86: Move all dell drivers to their own subdirectory

On Wed, Feb 03, 2021 at 01:26:37PM -0600, Mario Limonciello wrote: > A user without a Dell system doesn't need to pick any of these > drivers. > > Suggested-by: Andy Shevchenko > Signed-off-by: Mario Limonciello You are fast, thanks! ... > +menuconfig DELL_X86_PLATFORM_DRIVERS I'm not sure

Re: [PATCH 1/1] iscsi_ibft: KASAN false positive failure occurs in ibft_init()

On Wed, Feb 3, 2021 at 8:29 PM Konrad Rzeszutek Wilk wrote: > > Hey Dmitry, Rafael, George, please see below.. > > On Wed, Jan 27, 2021 at 10:10:07PM +0100, Dmitry Vyukov wrote: > > On Wed, Jan 27, 2021 at 9:01 PM George Kennedy > > wrote: > > > > > > Hi Dmitry, > > > > > > On 1/27/2021 1:48 PM,

Re: [PATCH] fcntl: make F_GETOWN(EX) return 0 on dead owner task

On Wed, Feb 03, 2021 at 03:41:56PM +0300, Pavel Tikhomirov wrote: > Currently there is no way to differentiate the file with alive owner > from the file with dead owner but pid of the owner reused. That's why > CRIU can't actually know if it needs to restore file owner or not, > because if it

Re: [PATCH] perf tools: Resolve symbols against debug file first

On Thu, Jan 28, 2021 at 11:43:07AM +0100, Jiri Slaby wrote: > On 13. 01. 21, 11:46, Jiri Olsa wrote: > > On Wed, Jan 13, 2021 at 09:01:28AM +0100, Jiri Slaby wrote: > > > With LTO, there are symbols like these: > > > /usr/lib/debug/usr/lib64/libantlr4-runtime.so.4.8-4.8-1.4.x86_64.debug > > >

Re: [PATCH][RESEND] lib/vsprintf: make-printk-non-secret printks all addresses as unhashed

On Wed, Feb 03, 2021 at 12:58:41PM -0600, Timur Tabi wrote: > On 2/3/21 7:31 AM, Petr Mladek wrote: > > Also please make sure that lib/test_printf.c will work with > > the new option. > > As you suspected, it doesn't work: > > [ 206.966478] test_printf: loaded. > [ 206.966528] test_printf:

Re: [PATCH 07/11] x86/fault: Split the OOPS code out from no_context()

> On Feb 3, 2021, at 10:56 AM, Borislav Petkov wrote: > > On Sun, Jan 31, 2021 at 09:24:38AM -0800, Andy Lutomirski wrote: >> Not all callers of no_context() want to run exception fixups. >> Separate the OOPS code out from the fixup code in no_context(). >> >> Cc: Dave Hansen >> Cc: Peter

Re: [PATCH mvebu v2 00/10] Armada 37xx: Fix cpufreq changing base CPU speed to 800 MHz from 1000 MHz

Hi Marek & Pali On 1/14/21 1:40 PM, Pali Rohár wrote: Hello! The armada-37xx-cpufreq driver changes base CPU speed from 1000 MHz to 800 MHz on EspressoBIN and Turris MOX. The commit message in patch 2/10 explains why and how can this be discovered. That patch 2/10 led us to discover another

Re: [PATCH 1/1] iscsi_ibft: KASAN false positive failure occurs in ibft_init()

Hey Dmitry, Rafael, George, please see below.. On Wed, Jan 27, 2021 at 10:10:07PM +0100, Dmitry Vyukov wrote: > On Wed, Jan 27, 2021 at 9:01 PM George Kennedy > wrote: > > > > Hi Dmitry, > > > > On 1/27/2021 1:48 PM, Dmitry Vyukov wrote: > > > > On Wed, Jan 27, 2021 at 7:44 PM Konrad Rzeszutek

Re: [PATCH v1 00/10] mfd, x86: remove msic driver and leftovers

On Wed, Feb 03, 2021 at 08:05:55PM +0100, Rafael J. Wysocki wrote: > On Tue, Feb 2, 2021 at 9:15 AM Lee Jones wrote: ... > This series has been applied as 5.12 material and will show up in > linux-next on Friday if all goes well. > > I can export an immutable branch with these commits if need

Re: [PATCH v3 0/5] arm64: dts: meson: add support for ODROID-HC4

On Tue, 2 Feb 2021 02:10:16 +, Christian Hewitt wrote: > This series fixes minor sort-order issues in the Amlogic bindings yaml and > dtb Makefile, then converts the existing ODROID-C4 dts into dtsi so we can > support its new sister product the ODROID-HC4. > > I've also given the devices

Re: [PATCH] arm64: dts: meson: fix broken wifi node for Khadas VIM3L

On Fri, 29 Jan 2021 16:50:40 +0800, Artem Lapkin wrote: > move _emmc_a ... from /* */ commented area, because cant load wifi fw > without sd-uhs-sdr50 option on VIM3L > > [ 11.686590] brcmfmac: brcmf_chip_cores_check: CPU core not detected > [ 11.696382] brcmfmac: brcmf_sdio_probe_attach:

[PATCH] platform/x86: Move all dell drivers to their own subdirectory

A user without a Dell system doesn't need to pick any of these drivers. Suggested-by: Andy Shevchenko Signed-off-by: Mario Limonciello --- MAINTAINERS | 22 +-- drivers/platform/x86/Kconfig | 182 +-

Re: syzbot reporting less duplicates

Hi! On Wed 2021-02-03 19:22:34, Dmitry Vyukov wrote: > On Wed, Feb 3, 2021 at 6:39 PM bobwxc wrote: > > > > On Wed, Feb 03, 2021 at 05:05:43PM +0100, Pavel Machek wrote: > > > On Mon 2021-02-01 11:52:12, Dmitry Vyukov wrote: > > > Could we please get common prefix (like syzbot: KASAN:) so

Re: [PATCH] Revert "dmaengine: dw: Enable runtime PM"

On 2021-02-03 6:08 PM, Andy Shevchenko wrote: On Wed, Feb 3, 2021 at 7:06 PM Andy Shevchenko wrote: On Wed, Feb 3, 2021 at 5:53 PM Cezary Rojewski wrote: This reverts commit 842067940a3e3fc008a60fee388e000219b32632. For some solutions e.g. sound/soc/intel/catpt, DW DMA is part of a

Re: [PATCH] Revert "dmaengine: dw: Enable runtime PM"

On 2021-02-03 6:06 PM, Andy Shevchenko wrote: On Wed, Feb 3, 2021 at 5:53 PM Cezary Rojewski wrote: This reverts commit 842067940a3e3fc008a60fee388e000219b32632. For some solutions e.g. sound/soc/intel/catpt, DW DMA is part of a compound device (in that very example, domains: ADSP, SSP0,

[PATCH v2] Revert "dmaengine: dw: Enable runtime PM"

This reverts commit 842067940a3e3fc008a60fee388e000219b32632. For some solutions e.g. sound/soc/intel/catpt, DW DMA is part of a compound device (in that very example, domains: ADSP, SSP0, SSP1, DMA0 and DMA1 are part of a single entity) rather than being a standalone one. Driver for said device

Re: [PATCH] misc: bcm-vk: Fix a couple error codes in probe()

Thanks Dan, On 2021-02-03 6:42 a.m., Dan Carpenter wrote: > These errors should return negative error codes instead of returning > success. Do you have a script running to report such issues or just manually reviewing to find such paths? > > Fixes: 064ffc7c3939 ("misc: bcm-vk: add autoload

Re: [PATCH 2/2] audit: show (grand)parents information of an audit context

On top of what Daniel just said: As there are many components being tested in regression runs, it's expensive to look back and reproduce the AVCs. And there's no prior knowledge of what processes may generate AVCs. The alternative would be to audit all fork/exec, but this could easily blow up the

Re: BUG: KASAN: stack-out-of-bounds in unwind_next_frame+0x1df5/0x2650

On Wed, Feb 03, 2021 at 09:46:55AM -0800, Ivan Babrou wrote: > > Can you pretty please not line-wrap console output? It's unreadable. > > GMail doesn't make it easy, I'll send a link to a pastebin next time. > Let me know if you'd like me to regenerate the decoded stack. > > > >

Re: [PATCH V3 07/14] coresight: etm-perf: Handle stale output handles

On Wed, Jan 27, 2021 at 02:25:31PM +0530, Anshuman Khandual wrote: > From: Suzuki K Poulose > > The context associated with an ETM for a given perf event > includes : > - handle -> the perf output handle for the AUX buffer. > - the path for the trace components > - the buffer config for

Re: [PATCH v1 00/10] mfd, x86: remove msic driver and leftovers

On Tue, Feb 2, 2021 at 9:15 AM Lee Jones wrote: > > On Mon, 01 Feb 2021, Rafael J. Wysocki wrote: > > > On Mon, Feb 1, 2021 at 7:45 PM Andy Shevchenko > > wrote: > > > > > > On Tue, Jan 26, 2021 at 12:39:59PM +0200, Andy Shevchenko wrote: > > > > On Tue, Jan 26, 2021 at 08:21:01AM +, Lee

[PATCH v2] [RFC] arm64: Exposes support for 32-bit syscalls

From: Ryan Houdek Sorry about the noise. I obviously don't work in this ecosystem. The problem: We need to support 32-bit processes running under a userspace compatibility layer. The compatibility layer is a AArch64 process. This means exposing the 32bit compatibility syscalls to userspace.

Re: [PATCH 2/2] perf parse-events: Break out tracepoint and printing.

On Wed, Feb 3, 2021 at 8:21 AM Arnaldo Carvalho de Melo wrote: > > Em Tue, Feb 02, 2021 at 09:26:59PM -0800, Ian Rogers escreveu: > > Move print_*_events functions out of parse-events.c into a new > > print-events.c. Move tracepoint code into tracepoint.c or > > trace-event-info.c (sole user).

Re: [RFC PATCH] sched/core: Fix premature p->migration_pending completion

On 03/02/21 17:23, Qais Yousef wrote: > On 01/27/21 19:30, Valentin Schneider wrote: >> Fiddling some more with a TLA+ model of set_cpus_allowed_ptr() & friends >> unearthed one more outstanding issue. This doesn't even involve >> migrate_disable(), but rather affinity changes and execution of the

Re: [PATCH][RESEND] lib/vsprintf: make-printk-non-secret printks all addresses as unhashed

On 2/3/21 7:31 AM, Petr Mladek wrote: Also please make sure that lib/test_printf.c will work with the new option. As you suspected, it doesn't work: [ 206.966478] test_printf: loaded. [ 206.966528] test_printf: plain 'p' does not appear to be hashed [ 206.966740] test_printf: failed 1 out

Re: [PATCH 2/2] audit: show (grand)parents information of an audit context

On Tue, Feb 02, 2021 at 04:44:47PM -0500, Paul Moore wrote: > On Tue, Feb 2, 2021 at 4:29 PM Daniel Walker wrote: > > From: Phil Zhang > > > > To ease the root cause analysis of SELinux AVCs, this new feature > > traverses task structs to iteratively find all parent processes > > starting with

Re: [PATCH 07/11] x86/fault: Split the OOPS code out from no_context()

On Sun, Jan 31, 2021 at 09:24:38AM -0800, Andy Lutomirski wrote: > Not all callers of no_context() want to run exception fixups. > Separate the OOPS code out from the fixup code in no_context(). > > Cc: Dave Hansen > Cc: Peter Zijlstra > Signed-off-by: Andy Lutomirski > --- >

Re: [PATCH net-next v1 2/6] lan743x: support rx multi-buffer packets

Thank you Bryan. I will prepare a v2 early next week. Would Microchip be able to donate some time to test v2? My own tests are certainly not perfect. Various stress tests across architectures (intel/arm) would help create confidence in the multi-buffer frame implementation. Perhaps Microchip has

Re: [PATCH] lib/vsprintf: make-printk-non-secret printks all addresses as unhashed

On Tue, Feb 02, 2021 at 02:51:00PM -0800, Linus Torvalds wrote: > On Tue, Feb 2, 2021 at 2:34 PM Steven Rostedt wrote: > > > > "I also suspect that everybody has already accepted that KASLR isn't > >really working locally anyway (due to all the hw leak models with > >cache and TLB

Re: [PATCH v2 25/28] KVM: x86/mmu: Allow zapping collapsible SPTEs to use MMU read lock

On Wed, Feb 3, 2021 at 3:34 AM Paolo Bonzini wrote: > > On 02/02/21 19:57, Ben Gardon wrote: > > @@ -1485,7 +1489,9 @@ void kvm_tdp_mmu_zap_collapsible_sptes(struct kvm > > *kvm, > > struct kvm_mmu_page *root; > > int root_as_id; > > > > - for_each_tdp_mmu_root_yield_safe(kvm,

[PATCH v3 0/5] ACPI: More cleanups related to printing messages

Hi All, On Tuesday, February 2, 2021 7:11:47 PM CET Rafael J. Wysocki wrote: > > On Monday, February 1, 2021 7:14:38 PM CET Rafael J. Wysocki wrote: > > > > This series is a continuation of the effort to drop ACPICA-specific debug > > code from non-ACPICA pieces of the ACPI subsystem and to

Re: [PATCH] x86: efi: avoid BUILD_BUG_ON() for non-constant p4d_index

On Wed, Jan 20, 2021 at 10:33:43AM +0100, Ard Biesheuvel wrote: > On Mon, 18 Jan 2021 at 22:42, Arvind Sankar wrote: > > > > On Mon, Jan 18, 2021 at 09:24:09PM +0100, Borislav Petkov wrote: > > > > > > As a matter of fact, it seems like the four assertions could be > > > > > > combined > > > > >

[PATCH v3 1/5] ACPI: AC: Clean up printing messages

From: Rafael J. Wysocki Replace the ACPI_DEBUG_PRINT() and ACPI_EXCEPTION() instances in ac.c with acpi_handle_debug() and acpi_handle_info() calls, respectively, which among other things causes the excessive log level of the messages previously printed via ACPI_EXCEPTION() to be increased.

[PATCH v3 4/5] ACPI: video: Clean up printing messages

From: Rafael J. Wysocki Replace the ACPI_DEBUG_PRINT() instances in acpi_video.c with acpi_handle_debug() calls and the ACPI_EXCEPTION()/ACPI_ERROR()/ ACPI_WARNING() instances in there with acpi_handle_info() calls, which among other things causes the excessive log levels of those messages to be

[PATCH v3 2/5] ACPI: battery: Clean up printing messages

From: Rafael J. Wysocki Replace the ACPI_DEBUG_PRINT() and ACPI_EXCEPTION() instances in battery.c with acpi_handle_debug() and acpi_handle_info() calls, respectively, which among other things causes the excessive log level of the messages previously printed via ACPI_EXCEPTION() to be increased.

[PATCH v3 3/5] ACPI: button: Clean up printing messages

From: Rafael J. Wysocki Replace the ACPI_DEBUG_PRINT() instance in button.c with an acpi_handle_debug() call, drop the _COMPONENT and ACPI_MODULE_NAME() definitions that are not used any more, drop the no longer needed ACPI_BUTTON_COMPONENT definition from the headers and update the

Re: Conflict with Mickaël Salaün's blacklist patches [was [PATCH v5 0/4] Add EFI_CERT_X509_GUID support for dbx/mokx entries]

This looks good to me, and it still works for my use case. Eric's patchset only looks for asymmetric keys in the blacklist keyring, so even if we use the same keyring we don't look for the same key types. My patchset only allows blacklist keys (i.e. hashes, not asymmetric keys) to be added by user

Re: [PATCH] mm/mremap: fix BUILD_BUG_ON() error in get_extent

On Tue, Jan 12, 2021 at 12:16:34PM -0700, Nathan Chancellor wrote: > On Wed, Dec 30, 2020 at 04:40:40PM +0100, Arnd Bergmann wrote: > > From: Arnd Bergmann > > > > clang cannt evaluate this function argument at compile time > > when the function is not inlined, which leads to a link > > time

[PATCH v3 5/5] ACPI: thermal: Clean up printing messages

From: Rafael J. Wysocki Replace the ACPI_DEBUG_PRINT() instances in thermal.c with acpi_handle_debug() calls and modify the ACPI_THERMAL_TRIPS_EXCEPTION() macro in there to use acpi_handle_info() internally, which among other things causes the excessive log level of the messages printed by it

[GIT PULL] arm64 fixes for 5.11-rc7

Hi Linus, Please pull the arm64 fixes below. Thanks. The following changes since commit a1df829ead5877d4a1061e976a50e2e665a16f24: ACPI/IORT: Do not blindly trust DMA masks from firmware (2021-01-27 12:26:24 +) are available in the Git repository at:

Re: [PATCH 7/8] sched/fair: Attempt misfit active balance when migration_type != migrate_misfit

On 03/02/21 15:16, Qais Yousef wrote: > On 01/28/21 18:31, Valentin Schneider wrote: >> Giving group_misfit_task a higher group_classify() priority than >> group_imbalance doesn't seem like the right thing to do. Instead, make >> need_active_balance() return true for any migration_type when the >

Re: [PATCH 0/8] sched/fair: misfit task load-balance tweaks

Hi Qais, On 03/02/21 15:14, Qais Yousef wrote: > On 01/28/21 18:31, Valentin Schneider wrote: >> Hi folks, >> >> Here is this year's series of misfit changes. On the menu: >> >> o Patch 1 is an independent active balance cleanup >> o Patch 2 adds some more sched_asym_cpucapacity static branches

Re: [PATCH 3/8] sched/fair: Tweak misfit-related capacity checks

On 03/02/21 15:15, Qais Yousef wrote: > On 01/28/21 18:31, Valentin Schneider wrote: >> @@ -113,6 +113,13 @@ int __weak arch_asym_cpu_priority(int cpu) >> */ >> #define fits_capacity(cap, max) ((cap) * 1280 < (max) * 1024) >> >> +/* >> + * The margin used when comparing CPU capacities. >>

Re: [PATCH 6/8] sched/fair: Filter out locally-unsolvable misfit imbalances

On 03/02/21 15:16, Qais Yousef wrote: > On 01/28/21 18:31, Valentin Schneider wrote: >> Consider the following (hypothetical) asymmetric CPU capacity topology, >> with some amount of capacity pressure (RT | DL | IRQ | thermal): >> >> DIE [ ] >> MC [][] >>0 1 2 3

Re: [PATCH 1/8] sched/fair: Clean up active balance nr_balance_failed trickery

>> @@ -9805,9 +9810,6 @@ static int load_balance(int this_cpu, struct rq >> *this_rq, >> active_load_balance_cpu_stop, busiest, >> >active_balance_work); >> } >> - >> -/* We've

Re: [RESEND PATCH v18 0/3] userspace MHI client interface driver

On Wed, 3 Feb 2021 19:28:28 +0100 Loic Poulain wrote: > On Wed, 3 Feb 2021 at 19:05, Jakub Kicinski wrote: > > On Wed, 03 Feb 2021 09:45:06 +0530 Manivannan Sadhasivam wrote: > > > The current patchset only supports QMI channel so I'd request you to > > > review the chardev node created for it.

Re: [PATCH v2 3/3] soc: qcom: rpmh: Conditionally check lockdep_assert_irqs_disabled()

Hi, On Sun, Jan 24, 2021 at 10:21 PM Maulik Shah wrote: > > @@ -136,6 +136,6 @@ void rpmh_rsc_invalidate(struct rsc_drv *drv); > int rpmh_rsc_mode_solver_set(struct rsc_drv *drv, bool enable); > > void rpmh_tx_done(const struct tcs_request *msg, int r); > -int rpmh_flush(struct rpmh_ctrlr

Re: [PATCH v2 1/4] arm64: kasan: don't populate vmalloc area for CONFIG_KASAN_VMALLOC

On Sat, 9 Jan 2021 at 11:33, Lecopzer Chen wrote: > > Linux support KAsan for VMALLOC since commit 3c5c3cfb9ef4da9 > ("kasan: support backing vmalloc space with real shadow memory") > > Like how the MODULES_VADDR does now, just not to early populate > the VMALLOC_START between VMALLOC_END. >

Re: [PATCH v2 2/3] soc: qcom: rpmh: Add rpmh_write_sleep_and_wake() function

Hi, On Sun, Jan 24, 2021 at 10:21 PM Maulik Shah wrote: > > Let RPMH clients call rpmh_write_sleep_and_wake() to immediately > write cached sleep and wake data to the TCSes. > > Signed-off-by: Maulik Shah > --- > (no changes since v1) > --- > drivers/soc/qcom/rpmh.c | 16 >

Re: [PATCH v2 1/3] drivers: qcom: rpmh: Disallow active requests in solver mode

Hi, On Sun, Jan 24, 2021 at 10:21 PM Maulik Shah wrote: > > From: Lina Iyer > > Controllers may be in 'solver' state, where they could be in autonomous > mode executing low power modes for their hardware and as such are not > available for sending active votes. Device driver may notify RPMH >

Re: [RESEND PATCH v18 0/3] userspace MHI client interface driver

On Wed 03 Feb 12:05 CST 2021, Jakub Kicinski wrote: > On Wed, 03 Feb 2021 09:45:06 +0530 Manivannan Sadhasivam wrote: > > >> Jakub, Dave, Adding you both to get your reviews on this series. I've > > >> provided an explanation above and in the previous iteration [1]. > > > > > >Let's be clear

Re: [RFC PATCH v2 12/26] KVM: arm64: Introduce a Hyp buddy page allocator

Hey Will, On Tuesday 02 Feb 2021 at 18:13:08 (+), Will Deacon wrote: > Hi Quentin, > > Sorry for the delay, this one took me a while to grok. No need to be sorry, thanks for having a look! > On Fri, Jan 08, 2021 at 12:15:10PM +, Quentin Perret wrote: > > When memory protection is

Re: [PATCH v2 24/28] KVM: x86/mmu: Allow zap gfn range to operate under the mmu read lock

On 03/02/21 19:31, Ben Gardon wrote: On Wed, Feb 3, 2021 at 3:26 AM Paolo Bonzini wrote: On 02/02/21 19:57, Ben Gardon wrote: +#ifdef CONFIG_LOCKDEP + if (shared) + lockdep_assert_held_read(>mmu_lock); + else + lockdep_assert_held_write(>mmu_lock); +#endif /*

Re: [PATCH v2 0/4] arm64: kasan: support CONFIG_KASAN_VMALLOC

On Sat, 9 Jan 2021 at 11:33, Lecopzer Chen wrote: > > Linux supports KAsan for VMALLOC since commit 3c5c3cfb9ef4da9 > ("kasan: support backing vmalloc space with real shadow memory") > > Acroding to how x86 ported it [1], they early allocated p4d and pgd, > but in arm64 I just simulate how KAsan

Re: [PATCH v2 23/28] KVM: x86/mmu: Allow parallel page faults for the TDP MMU

On 03/02/21 18:46, Ben Gardon wrote: enum kvm_mmu_lock_mode lock_mode = get_mmu_lock_mode_for_root(vcpu->kvm, vcpu->arch.mmu->root_hpa); kvm_mmu_lock_for_mode(lock_mode); Not sure if either of those are actually clearer, but the latter trends in the direction the RCF took, having an enum

Re: [PATCH v2 24/28] KVM: x86/mmu: Allow zap gfn range to operate under the mmu read lock

On Wed, Feb 3, 2021 at 3:26 AM Paolo Bonzini wrote: > > On 02/02/21 19:57, Ben Gardon wrote: > > +#ifdef CONFIG_LOCKDEP > > + if (shared) > > + lockdep_assert_held_read(>mmu_lock); > > + else > > + lockdep_assert_held_write(>mmu_lock); > > +#endif /* CONFIG_LOCKDEP

Re: [PATCH] selftests: breakpoints: Fix wrong argument of ptrace() when single step

On 2/3/21 1:39 AM, Tiezhu Yang wrote: According to the error message, the first argument of ptrace() should be PTRACE_SINGLESTEP instead of PTRACE_CONT when ptrace single step. Fixes: f43365ee17f8 ("selftests: arm64: add test for unaligned/inexact watchpoint handling") Signed-off-by: Tiezhu

Re: [PATCH v2 1/5] ACPI: AC: Clean up printing messages

On Wednesday, February 3, 2021 2:31:08 AM CET Hanjun Guo wrote: > Hi Rafael, > > On 2021/2/3 2:14, Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > > > Replace the ACPI_DEBUG_PRINT() and ACPI_EXCEPTION() instances > > in ac.c with acpi_handle_debug() and acpi_handle_info() calls, > >

Re: [PATCH v3 1/1] x86,sched: On AMD EPYC set freq_max = max_boost in schedutil invariant formula

On Wednesday, February 3, 2021 3:11:37 PM CET Rafael J. Wysocki wrote: > On Wed, Feb 3, 2021 at 2:53 PM Giovanni Gherdovich > wrote: > > > > [cut] > > > Fixes: 41ea667227ba ("x86, sched: Calculate frequency invariance for AMD > > systems") > > Fixes: 976df7e5730e ("x86, sched: Use midpoint of

Re: [PATCH v7 0/2] ARM: Implement MODULE_PLT support in FTRACE

On 1/27/21 3:09 AM, Alexander A Sverdlin wrote: > From: Alexander Sverdlin > > FTRACE's function tracer currently doesn't always work on ARM with > MODULE_PLT option enabled. If the module is loaded too far, FTRACE's > code modifier cannot cope with introduced veneers and turns the > function

Re: [PATCH] MIPS: of: Introduce helper function to get DTB

On 1/27/21 5:24 AM, Thomas Bogendoerfer wrote: > Selection of the DTB to be used was burried in more or less readable > code in head.S. Move this code into a inline helper function and > use it. > > Signed-off-by: Thomas Bogendoerfer > --- > arch/mips/bmips/setup.c | 7 +++---

Re: syzbot reporting less duplicates

On Wed, Feb 3, 2021 at 6:39 PM bobwxc wrote: > > On Wed, Feb 03, 2021 at 05:05:43PM +0100, Pavel Machek wrote: > > On Mon 2021-02-01 11:52:12, Dmitry Vyukov wrote: > > Could we please get common prefix (like syzbot: KASAN:) so that > > the bulk of emails is easier to remove? > There are

Re: [PATCH] entry: Fix missed trap after single-step on system call return

On Wed, Feb 3, 2021 at 10:18 AM Andy Lutomirski wrote: > > So if we want to reliably single-step a system call and trap after the > system call, we just need to synthesize a trap on the way out. Well, I think Gabriel's patch does exactly that, due to how SYSCALL_EXIT_TRAP is set. It looks like

Re: [RESEND PATCH v18 0/3] userspace MHI client interface driver

Hi Jakub, On Wed, 3 Feb 2021 at 19:05, Jakub Kicinski wrote: > > On Wed, 03 Feb 2021 09:45:06 +0530 Manivannan Sadhasivam wrote: > > >> Jakub, Dave, Adding you both to get your reviews on this series. I've > > >> provided an explanation above and in the previous iteration [1]. > > > > > >Let's

Re: [PATCH v3 5/9] userfaultfd: add minor fault registration mode

On Tue, Feb 2, 2021 at 9:15 AM Peter Xu wrote: > > On Mon, Feb 01, 2021 at 01:31:59PM -0500, Peter Xu wrote: > > On Thu, Jan 28, 2021 at 02:48:15PM -0800, Axel Rasmussen wrote: > > > This feature allows userspace to intercept "minor" faults. By "minor" > > > faults, I mean the following

Re: [PATCH] entry: Fix missed trap after single-step on system call return

On Wed, Feb 3, 2021 at 10:10 AM Linus Torvalds wrote: > > On Wed, Feb 3, 2021 at 10:00 AM Gabriel Krisman Bertazi > wrote: > > > > Does the patch below follows your suggestion? I'm setting the > > SYSCALL_WORK shadowing TIF_SINGLESTEP every time, instead of only when > > the child is inside a

[PATCH v3 2/7] selftests: lib:test_seqnum_ops: add new test for seqnum_ops

Add a new selftest for testing seqnum_ops. This test loads test_seqnum_ops test module and unloads it. The test module runs tests and prints results to dmesg. Sequence Number api provides interfaces for unsigned atomic up counters leveraging atomic_t and atomic64_t ops underneath. There are a

Re: [PATCH v2 00/28] Allow parallel MMU operations with TDP MMU

On 03/02/21 18:54, Sean Christopherson wrote: On Wed, Feb 03, 2021, Paolo Bonzini wrote: Looks good! I'll wait for a few days of reviews, I guess I know what I'm doing this afternoon :-) but I'd like to queue this for 5.12 and I plan to make it the default in 5.13 or 5.12-rc (depending on

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