While running file system tests (xfstest) on IBM Power following warning
was seen:
[ 750.845015] run fstests generic/347 at 2024-04-13 03:58:42
[ 751.017900] XFS (loop0): Mounting V5 Filesystem
998a731d-ad3f-467d-ad31-92990b381696
[ 751.019105] XFS (loop0): Ending clean mount
[ 751.372715] --
c: sta...@vger.kernel.org
> Signed-off-by: Alexander Wetzel
> ---
Thanks for the fix. I tested this patch and confirm it fixes the reported
problem.
Tested-by: Sachin Sant
— Sachin
> Can you check the debug patch below and provide output?
> When I'm right the warning should be gone and you should just get the
> "Modification triggered" instead. When I'm wrong we should at least see,
> how many references d_ref has left.
>
With the debug patch applied, code says d_ref val
Following WARN_ON_ONCE is triggered while running LTP tests
(specifically ioctl_sg01) on IBM Power booted with 6.9.0-rc1-next-20240328
[ 64.230233] [ cut here ]
[ 64.230269] WARNING: CPU: 10 PID: 452 at drivers/scsi/sg.c:2236
sg_remove_sfp_usercontext+0x270/0x280 [sg]
> On 01-Mar-2024, at 3:48 AM, Michael Ellerman wrote:
>
> Sachin Sant writes:
>> Powerpc specific selftests (specifically powerpc/primitives) included in
>> linux-next
>> tree fails to build with following error
>>
>> gcc -std=gnu99 -O2 -Wall -Wer
Powerpc specific selftests (specifically powerpc/primitives) included in
linux-next
tree fails to build with following error
gcc -std=gnu99 -O2 -Wall -Werror
-DGIT_VERSION='"next-20240229-0-gf303a3e2bcfb-dirty"'
-I/home/sachin/linux-next/tools/testing/selftests/powerpc/include
-I/home/sachin/
s, CFLAGS and
> GIT_VERSION macros are defined in the powerpc/ folder Makefile which
> in this case not involved.
>
> To address the failure incase of executing specific sub-folder test directly,
> a new rule file has been addded by the patch called "flags.mk" under
&
> On 29-Feb-2024, at 7:52 AM, Michael Ellerman wrote:
>
> Tasmiya Nalatwad writes:
>> Greetings,
>>
>> [netdev] Build failure on powerpc
>> latest netdev 6.8.0-rc5-auto-g1ce7d306ea63 fails to build on powerpc
>> below traces
>
> Please include the defconfig you're building, and the toolcha
> On 27-Feb-2024, at 10:38 PM, Steven Rostedt wrote:
>
> On Tue, 27 Feb 2024 11:56:14 -0500
> Steven Rostedt wrote:
>
>> On Tue, 27 Feb 2024 22:08:18 +0530
>> Sachin Sant wrote:
>>
>>>> Can you apply this, and see if it triggers and if it do
> On 27-Feb-2024, at 9:54 PM, Steven Rostedt wrote:
>
> On Tue, 27 Feb 2024 21:38:57 +0530
> Sachin Sant wrote:
>
>> This warning was not triggered.
>
> Interesting.
>
>>
>> I have attached .config
>
> This is what I was loo
>> --- interrupt: c00
>> Code: f821ff91 2f89 409e0034 7c0802a6 3c62fff0 3921 3d420177
>> 3863e310 992ad6db f8010080 4b209899 6000 <0fe0> e8010080 7c0803a6
>> 2f9f
>> ---[ end trace ]—
>>
>> This warning is seen while running test that was added by
>> followi
> On 25-Feb-2024, at 10:09 PM, Madhavan Srinivasan wrote:
>
> When running `make -C powerpc/pmu run_tests` from top level selftests
> directory, currently this error is being reported
>
> make: Entering directory
> '/home/maddy/linux/tools/testing/selftests/powerpc/pmu'
> Makefile:40: warnin
While running ftrace specific kernel selftests following warning
is seen on a Power10 logical partition (LPAR) booted with
latest mainline kernel.
[ cut here ]
precision 63492 too large
WARNING: CPU: 15 PID: 2538829 at lib/vsprintf.c:2721 set_precision+0x68/0xa4
Modules lin
Kdump fails to save vmcore with recent linux-next builds on IBM Power server
with following messages
Starting Kdump Vmcore Save Service...
[ 17.349599] kdump[367]: Kdump is using the default log level(3).
[ 17.407407] kdump[391]: saving to
/sysroot//var/crash//127.0.0.1-2024-02-21-15:03:
> On 24-Nov-2023, at 2:25 PM, Vlastimil Babka wrote:
>
> On 11/23/23 15:35, Chengming Zhou wrote:
>> On 2023/11/23 19:27, Sachin Sant wrote:
>>> While booting recent -next kernel on IBM Power server, I have observed
>>> lockups
>>> either during
While booting recent -next kernel on IBM Power server, I have observed lockups
either during boot or just after.
[ 3631.015775] watchdog: CPU 3 self-detected hard LOCKUP @
__update_freelist_slow+0x74/0x90
[ 3631.015783] watchdog: CPU 3 TB:7766577908812231, last heartbeat
TB:7766572528409444 (105
Following warning is observed during boot of latest -next
kernel (6.6.0-rc7-next-20231030 and todays -next) on IBM Power server.
[ 0.085775] workingset: timestamp_bits=38 max_order=20 bucket_order=0
[ 0.085801] zbud: loaded
[ 0.086473] [ cut here ]
[ 0.086477] WARNING: CPU:
> On 13-Oct-2023, at 2:49 AM, Dave Chinner wrote:
>
> On Thu, Oct 12, 2023 at 03:51:04PM +0530, Sachin Sant wrote:
>> While running xfstests on a IBM Power10 server having xfs file system with
>> 4k block size following crash was seen
>>
>> [ 1609.771548] run
> does.
>
> If the copros count is elevated then it will cause a global flush, which
> should flush translations from any copros. Note that the process table
> entry was cleared in arch_exit_mmap(), so copros should not be able to
> fetch any new translations.
>
> Fixes: e4
> On 17-Oct-2023, at 4:35 PM, Lorenzo Stoakes wrote:
>
> On Tue, Oct 17, 2023 at 02:46:07PM +0530, Sachin Sant wrote:
>> While running LTP tests (getpid02) on a Power10 server booted with
>> 6.6.0-rc6-next-20231016 following crash was seen:
>>
>> [ 76.3866
While running LTP tests (getpid02) on a Power10 server booted with
6.6.0-rc6-next-20231016 following crash was seen:
[ 76.386628] Kernel attempted to read user page (d8) - exploit attempt? (uid:
0)
[ 76.386649] BUG: Kernel NULL pointer dereference on read at 0x00d8
[ 76.386653] Faulting
While running xfstests on a IBM Power10 server having xfs file system with
4k block size following crash was seen
[ 1609.771548] run fstests xfs/238 at 2023-10-11 17:00:40
[ 1609.971214] XFS (sdb1): Mounting V5 Filesystem
1105d60c-9514-4e7a-af6a-632d99bf06ea
[ 1609.980693] XFS (sdb1): Ending clea
While running kernel selftests (powerpc/mce) following warning is triggered
TAP version 13
1..1
# timeout set to 45
# selftests: powerpc/mce: inject-ra-err
[ 37.851967] Disabling lock debugging due to kernel taint
[ 37.851977] MCE: CPU19: machine check (Severe) Real address Load/Store
(forei
> On 14-Sep-2023, at 6:52 PM, Michael Ellerman wrote:
>
> Sachin Sant writes:
>>> On 11-Sep-2023, at 2:44 PM, Aditya Gupta wrote:
>>>
>>> Presently, while reading a vmcore, makedumpfile uses
>>> `cur_cpu_spec.mmu_features` to decide whethe
that the symbol address and offset
> is accessible to makedumpfile, without needing the vmlinux file
>
> Signed-off-by: Aditya Gupta
> ---
Thanks for the patch. With this patch applied (along with makedumpfile changes)
I am able to capture vmcore against a kernel which contains commit 8dc9a0
ameters.
>
> Signed-off-by: Athira Rajeev
> ---
> Changelog:
> v1 -> v2:
> Addressed review comments from Ian. Updated size of
> pmu event name variable and changed bool name which is
> used to skip the test.
>
The patch fixes the reported issue.
6.2: Parsing of a
While running LTP tests (specifically min_free_kbytes) on a Power server
booted with 6.5.0-next-20230906 following crash was encountered.
[ 3952.404936] __vm_enough_memory: pid: 440285, comm: min_free_kbytes, not
enough memory for the allocation
[ 3956.895519] __vm_enough_memory: pid: 440286, com
avocado-vt based cpu, guest lifecycle and ras bucket.
The test completed successfully.
Based on this testing for patches 1 to 10
Tested-by: Sachin Sant
- Sachin
meters.
>
> Signed-off-by: Athira Rajeev
> —
Thanks Athira for the fix. With this fix applied the reported problem
Is fixed.
6.1: Test event parsing: Ok
6.2: Parsing of all PMU events from sysfs : Ok
6.3: Parsing of given PMU events from sysfs: Ok
Tested-by: Sachin Sant
- Sachin
_program__set_type function. This commit also fixed
> bpf_prog_test_load() helper in selftests/bpf to force-set program
> type only if it differs from the desired one.
>
> The "bpf__probe" function in util/bpf-loader.c, also calls
> bpf_program__set_type to set bpf_prog_type. Add s
Kernel Crash dump(kdump) and firmware assisted dump on powerpc
fails to capture vmcore on recent linux-next builds.
Starting Kdump Vmcore Save Service...
systemd[1]: Starting Kdump Vmcore Save Service...
kdump[599]: Kdump is using the default log level(3).
kdump[635]: saving to /sysroot/var/crash/
> On 19-Jul-2023, at 11:33 PM, Mahesh J Salgaonkar wrote:
>
> On 2023-07-18 23:19:23 Tue, Michael Ellerman wrote:
>> Mahesh J Salgaonkar writes:
>>> On 2023-07-17 20:15:53 Mon, Sachin Sant wrote:
>>>> Kdump seems to be broken with 6.5 for ppc64le.
>>
Kdump seems to be broken with 6.5 for ppc64le.
[ 14.200412] systemd[1]: Starting dracut pre-pivot and cleanup hook...
[[0;32m OK [0m] Started dracut pre-pivot and cleanup hook.
Starting Kdump Vmcore Save Service...
[ 14.231669] systemd[1]: Started dracut pre-pivot and cleanup hook.
[ 14.231801] sy
While running LTP tests (madvise06) on IBM Power9 LPAR booted with
6.4.0-next-20230705 following crash is seen
Injecting memory failure for pfn 0x3f79 at process virtual address
0x7fff9b74
Memory failure: 0x3f79: recovery action for clean LRU page: Recovered
madvise06 (133636): drop_caches: 3
e ppc64_cpu &
lparstat utility. With patched ppc64_cpu utility verified that SMT level
changed at runtime was preserved across processor core add (on
a kernel booted without smt-enabled= parameter)
Based on these test results
Tested-by: Sachin Sant
- Sachin
>>
>> Without this option but changing SMT level during runtime using
>> ppc64_cpu —smt=, the SMT level is not retained after
>> cpu core add.
>
> That's because ppc64_cpu is not using the sysfs SMT control file, it's
> just onlining/offlining threads manually.
>
> If you run:
> $ ppc64_cpu --
> On 28-Jun-2023, at 3:35 PM, Laurent Dufour wrote:
>
> I'm taking over the series Michael sent previously [1] which is smartly
> reviewing the initial series I sent [2]. This series is addressing the
> comments sent by Thomas and me on the Michael's one.
>
> Here is a short introduction to
his should fix it:
Yes, with this change kexec works correctly.
Since Aneesh first reported this problem including reported by credit for him
Reported-by: Aneesh Kumar K. V
Reported-by: Sachin Sant
Tested-by: Sachin Sant
-Sachin
>> The problem was introduced in 6.4.0-rc7-next-20230619. I tried git bisect,
>> but unsure of the
>> result reported by it. Bisect points to following patch
>>
>> # git bisect bad
>> 70c94cc2eefd4f98d222834cbe7512804977c2d4 is the first bad commit
>> commit 70c94cc2eefd4f98d222834cbe7512804977
6.4.0-rc7-next-20230620 fails to boot on IBM Power LPAR with following
[ 5.548368] BUG: Unable to handle kernel data access at 0x95bdcf954bc34e73
[ 5.548380] Faulting instruction address: 0xc0548090
[ 5.548384] Oops: Kernel access of bad area, sig: 11 [#1]
[ 5.548387] LE PAGE_SIZE=64K MMU=
ith different alignment values.
> * Correctly check for section validity to before we free vmemmap area
Thanks for the updated series.
The previously reported WARN_ON is not seen with this series.
I also ran few regression tests against this series and did not
see any problems.
Based on the test results
Tested-by: Sachin Sant mailto:sach...@linux.ibm.com>>
-Sachin
>> [ 34.381788] Code: 5463063e 408201c8 38210080 4e800020 6000 6000
>> 6000 7c0802a6 fbe10078 7c7f1b78 f8010090 e9230728 2c2c
>> 41820020 7d8903a6
>
> 2c: 28 07 23 e9 ld r9,1832(r3)
> 30: 50 00 89 e9 ld r12,80(r9)
>
> Where r3 is *chip.
> r9 is NULL,
Following crash is observed during a kexec operation on
IBM Power10 server:
[ 34.381548] Kernel attempted to read user page (50) - exploit attempt? (uid: 0)
[ 34.381562] BUG: Kernel NULL pointer dereference on read at 0x0050
[ 34.381565] Faulting instruction address: 0xc09db1e4
[ 34.3
> 1. First try to map things using PMD (2M)
> 2. With altmap if altmap cross-boundary check returns true, fall back to
> PAGE_SIZE
> 3. IF we can't allocate PMD_SIZE backing memory for vmemmap, fallback to
> PAGE_SIZE
>
> On removing vmemmap mapping, check if every subsection that is using the
> On 07-Jun-2023, at 3:40 PM, Nicholas Piggin wrote:
>
> The refcount on mm is dropped before the coprocessor is detached.
>
> Reported-by: Sachin Sant
> Fixes: 7bc6f71bdff5f ("powerpc/vas: Define and use common vas_window struct")
> Fixes: b22f2d88e435c (&quo
While running powerpc selftests on a Power10 LPAR, following warning
is seen:
[ 43.878929] MCE: CPU25: PID: 6025 Comm: inject-ra-err NIP: [1e48]
[ 43.878933] MCE: CPU25: Initiator CPU
[ 43.878935] MCE: CPU25: Unknown
[ 43.906866] [ cut here ]
[ 43.9068
> Reported-by: Sachin Sant
> Link:
> https://lore.kernel.org/linuxppc-dev/87a5xcgopc.fsf@mail.lhotse/T/#m105488939d0cd9f980978ed2fdeeb89bf731e673
> Fixes: a665eec0a22e1 ("powerpc/64s/radix: Fix mm_cpumask trimming race vs
> kthread_use_mm")
> Signed-off-by: N
While compiling a kernel on a IBM Power system booted with
6.4.0-rc4-next-20230601 following warning is observed
[ 276.351697] [ cut here ]
[ 276.351709] WARNING: CPU: 27 PID: 9237 at kernel/sched/core.c:5358
kthread_end_lazy_tlb_mm+0x90/0xa0
[ 276.351719] Modules linke
While running ftrace specific kernel selftests on IBM Power9 server,
following crash is observed. I have observed this crash only on Power9.
Similar test run on a Power10 server works.
[14350.791484] Kernel attempted to read user page (8) - exploit attempt? (uid:
0)
[14350.791507] BUG: Kernel NUL
While running xfstests against btrfs (with 4k block size) on IBM Power server
booted with 6.4.0-rc3-next-20230525, following warning is seen. This warning
Is seen several times during the test run.
This problem was first seen with 6.4.0-rc2-next-20230516
[ 365.885258] run fstests btrfs/001 at 202
callbacks as __cpuidle and use the
> raw_local_irq_*() routines to ensure that is the case.
>
> Reported-by: Sachin Sant
> Suggested-by: Peter Zijlstra
> Signed-off-by: Michael Ellerman
> ---
Thanks for the patch. With this patch (and others from the series)
applied, I no long
rcu_torture.sh relies on modprobe to load/unload
>> the rcutorture module.
>>
>>> Whatever the reproducer, does the following patch help?
>>
>> Thank you for the patch. Yes, with this patch applied, the test completes
>> successfully without the reported wa
>> [ 3629.243407] NIP [7fff8cd39558] 0x7fff8cd39558
>> [ 3629.243410] LR [00010d800398] 0x10d800398
>> [ 3629.243413] --- interrupt: c00
>> [ 3629.243415] Code: 419dffa4 e93a0078 3941 552907be 2f89 7d20579e
>> 0b09 e95a0078 e91a0080 3921 7fa85000 7d204f9e <0b09> 7f23c
While running rcutorture tests from LTP on an IBM Power10 server booted with
6.3.0-rc3-next-20230322 following warning is observed:
[ 3629.242831] [ cut here ]
[ 3629.242835] WARNING: CPU: 8 PID: 614614 at kernel/workqueue.c:3182
__flush_work.isra.44+0x44/0x370
[ 3629.2428
r now.
>
> Reviewed-by: Nicholas Piggin
> Tested-by: Nicholas Piggin
> Signed-off-by: Paul Mackerras
> ---
Tested on a Power10 system. Prefixed instructions work correctly.
Tested-by: Sachin Sant
> arch/powerpc/include/asm/reg.h | 1 +
> arch/powerpc/kvm/book3s_hv.
While running powerpc/primitives selftests, the test (load_unaligned_zeropad)
hangs indefinitely. This behaviour is seen with linux-next 6.2.0-next-20230303
on a Power10 logical partition.
Git bisect points to following commit
commit 169db3bb460903443e25ac9c0737da45d6bb5402
powerc/mm: try VMA
> On 03-Feb-2023, at 3:55 PM, Nicholas Piggin wrote:
>
> On Fri Feb 3, 2023 at 4:26 PM AEST, Sachin Sant wrote:
>> I am observing an intermittent crash while running powerpc/security
>> selftests on a Power10 LPAR booted with powerpc/merge branch code.
>>
>> ---[ end trace ]---
>> [ cut here ]
>> RCU not on for: shared_cede_loop+0xc/0x170
>>
>> The code in question was added by
>> commit d099dbfd330686a8c09cd8944bcc77a56f9e7815
>>cpuidle: tracing: Warn about !rcu_is_watching()
>
> Note that by selecting
>
> Reported-by: Sachin Sant
> Suggested-by: Peter Zijlstra
> Signed-off-by: Michael Ellerman
> ---
Thanks for the patch Michael.
Tested-by: Sachin Sant
> arch/powerpc/Kconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/powerpc/Kconfig b/a
Following warning is seen with 6.2.0-rc6-next-20230201 on a
Power10 server.
[ cut here ]
RCU not on for: check_return_regs_valid+0xc/0x1e0
WARNING: CPU: 9 PID: 0 at include/linux/trace_recursion.h:162
arch_ftrace_ops_list_func+0x2c0/0x2e0
Modules linked in: kmem device_dax
s issue by adding the checks for PVR_POWER8E and
> PVR_POWER8NVL as well.
>
> Fixes: ec3eb9d941a9 ("powerpc/perf: Use PVR rather than oprofile field to
> determine CPU version")
> Reported-by: Sachin Sant
> Signed-off-by: Kajol Jain
> ---
Thanks for the fix. Tested on
t region, so that the
> permission change only applies to the interrupt text, and not the region
> following it.
>
> Fixes: c55d7b5e6426 ("powerpc: Remove STRICT_KERNEL_RWX incompatibility with
> RELOCATABLE")
> Signed-off-by: Michael Ellerman
> ---
Thanks Michael. This fixes t
0002c0 with 2.00 MiB pages
> (exec)
> radix-mmu: Mapped 0x02c0-0x00010000 with 2.00 MiB pages
>
> Fixes: c55d7b5e6426 ("powerpc: Remove STRICT_KERNEL_RWX incompatibility with
> RELOCATABLE")
> Signed-off-by: Michael Ellerman
> ---
Tested successfully with different crash kernel memory values
Tested-by : Sachin Sant
- Sachin
>> [ 0.445046] Code: 392990f8 4814 3d02ffe9 390827f0 7d074378 7d094378
>> 7c661b78 3c62ffe7 f9610060 386319f0 4bca6935 6000 <0fe0>
>> 7c0802a6
>> [ 0.445061] ---[ end trace ]—
>> Git bisect points to following patch:
>> commit 317c8194e6aeb8b3b573ad
6.2.0-rc3-next-20230109 fails to boot on powerpc with following:
[ 0.444834] [ cut here ]
[ 0.444838] kernel BUG at mm/usercopy.c:102!
[ 0.444842] Oops: Exception in kernel mode, sig: 5 [#1]
[ 0.444845] LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA pSeries
[ 0.444849] Mo
While running transparent hugepage defragmentation test [1]
on Power10 server following crash was seen
[11725.379229] Kernel attempted to read user page (8) - exploit attempt? (uid:
0)
[11725.379251] BUG: Kernel NULL pointer dereference on read at 0x0008
[11725.379257] Faulting instruction ad
>> [ 8.809079] [c7c37e10] [c000cffc]
>> ret_from_kernel_thread+0x5c/0x64
>> [ 8.809086] Instruction dump:
>> [ 8.809090] f821ffc1 41820034 395e03c0 7c0004ac 7d205028 2c090001 3929
>> 41c00010
>> [ 8.809101] 7d20512d
>> [ 8.809101] sd 1:0:0:1: [sdc] Preferred minimum I/O size 3
While booting 6.1.0-rc4-next-20221109 next kernel on a IBM Power9 LPAR
following warning is seen:
[ 8.808868] [ cut here ]
[ 8.808872] WARNING: CPU: 1 PID: 378 at kernel/module/main.c:852
module_put+0x48/0x100
[ 8.808881] Modules linked in: sr_mod(E) cdrom(E) sd_mod(E) sg(
> On 09-Nov-2022, at 3:25 PM, Jason A. Donenfeld wrote:
>
> Should be fixed already in today's next.
Yup, thanks. next-20221109 boots successfully.
- Sachin
elp me test the attached file?
> Please use this new patch instead of the one in memblock tree.
Thanks for the fix. With the updated patch kernel boots correctly.
Tested-by: Sachin Sant mailto:sach...@linux.ibm.com>>
- Sachin
6.1.0-rc4-next-20221108 fails to boot on IBM Power Server with
following traces.
[0.609442] PowerPC PowerNV PCI Hotplug Driver version: 0.1
[0.609699] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[0.610037] tpm_ibmvtpm 3003: CRQ initialization completed
[1.681458] --
With CONFIG_DEBUG_WX=y I am observing following warning
During kdump kernel boot. This warning is not seen during production
kernel boot. Kernel crash dump is captured correctly.
[ cut here ]
[ 11.541311] powerpc/mm: Found insecure W+X mapping at address
749d3849
ag, which is not clear when the original context is returned to.
>
> Reported-by: Sachin Sant
> Fixes: a4cb3651a1743 ("powerpc/64s/interrupt: Fix lost interrupts when
> returning to soft-masked context")
> Signed-off-by: Nicholas Piggin
> ---
Thanks Nick. The patch fixes the reported problem
Tested-by: Sachin Sant
While running powerpc kselftests (mm/stress_code_patching.sh)
on a PowerVM LPAR following warning is seen. The test passes.
I can reliably recreate it on a Power9 server, not so easily on
Power10.
# ./stress_code_patching.sh
Testing for spurious faults when mapping kernel memory...
[ 175.289418]
ed handler debug check for
> previous hard disable")
> Reported-by: Sachin Sant
> Signed-off-by: Nicholas Piggin
> ---
Thanks Nick. Tested both the patches on Power9 and Power10. I no longer
see the reported problem.
Tested-by: Sachin Sant
- Sachin
With recent versions of linux-next I am observing kernel crashes on Power
server.
I saw this crash once just after boot. I also saw similar crash while compiling
a
Kernel or during a git clone of kernel source. Seem to occur at random times.
[ 175.165592] [ cut here ]
[
force inline or mark no instrumentation
> for functions which can run in realmode, to avoid KASAN
> instrumentation.
>
> Signed-off-by: Ganesh Goudar
> ---
> v2: Force inline few more functions.
>
> v3: Adding noinstr to few functions instead of __always_inline.
> ---
Tested-by: Sachin Sant
- Sachin
> On 22-Sep-2022, at 5:11 AM, Mike Kravetz wrote:
>
> On 09/21/22 12:00, Sachin Sant wrote:
>> While running transparent huge page tests [1] against 6.0.0-rc6-next-20220920
>> following crash is seen on IBM Power server.
>
> Thanks Sachin,
>
> Naoya rep
> On 22-Sep-2022, at 2:13 AM, Kees Cook wrote:
>
> On Wed, Sep 21, 2022 at 09:21:52PM +0530, Sachin Sant wrote:
>> While booting recent linux-next kernel on a Power server following
>> warning is seen:
>>
>> [6.427054] lpfc 0022:01:00.0: 0:6468
While booting recent linux-next kernel on a Power server following
warning is seen:
[6.427054] lpfc 0022:01:00.0: 0:6468 Set host date / time: Status x10:
[6.471457] lpfc 0022:01:00.0: 0:6448 Dual Dump is enabled
[7.432161] [ cut here ]
[7.432178] memcpy: de
While running transparent huge page tests [1] against 6.0.0-rc6-next-20220920
following crash is seen on IBM Power server.
Kernel attempted to read user page (34) - exploit attempt? (uid: 0)
BUG: Kernel NULL pointer dereference on read at 0x0034
Faulting instruction address: 0xc04d2744
es during kdump kernel boot, due to RTAS or other allocation
> restrictions.
>
> Also, while here, use SZ_128M instead of opening coding it.
>
> Signed-off-by: Hari Bathini
> ---
Tested on a Power10 and Power9 LPAR. Kdump works as expected.
Tested-by: Sachin Sant
>
&g
force inline or mark no instrumentation
> for functions which can run in realmode, to avoid KASAN
> instrumentation.
>
> Signed-off-by: Ganesh Goudar
> ---
> v2: Force inline few more functions.
Thanks for the patch. The test successfully ran to completion.
Tested-by: Sachin Sant
> On 29-Aug-2022, at 5:02 PM, Sachin Sant wrote:
>
>
>
>> On 29-Aug-2022, at 1:15 PM, Ganesh Goudar wrote:
>>
>> Part of machine check error handling is done in realmode,
>> As of now instrumentation is not possible for any code that
>> runs in
> On 29-Aug-2022, at 1:15 PM, Ganesh Goudar wrote:
>
> Part of machine check error handling is done in realmode,
> As of now instrumentation is not possible for any code that
> runs in realmode.
> When MCE is injected on KASAN enabled kernel, crash is
> observed, Hence force inline or mark no
> On 19-Aug-2022, at 10:12 AM, Ganesh wrote
>>
>> We'll have to make sure everything get_pseries_errorlog() is either
>> forced inline, or marked noinstr.
>>
> Making the following functions always_inline and noinstr is fixing the issue.
> __always_inline pseries_errorlog_id()
> __always_inli
Following crash is seen while running powerpc/mce subtest on
a Power10 LPAR.
1..1
# selftests: powerpc/mce: inject-ra-err
[ 155.240591] BUG: Unable to handle kernel data access on read at
0xc00e00022d55b503
[ 155.240618] Faulting instruction address: 0xc06f1f0c
[ 155.240627] Oops: Ker
> On 11-Aug-2022, at 3:45 PM, Stefano Garzarella wrote:
>
>> Date: Wed Aug 10 11:43:47 2022 +0200
>>vdpa_sim_blk: add support for discard and write-zeroes
>>
>
> Thanks for the report, I already re-sent a new series with that patch fixed:
> https://lore.kernel.org/virtualization/202208
5.19.0-next-20220811 linux-next fails to build on IBM Power with
following error:
drivers/vdpa/vdpa_sim/vdpa_sim_blk.c: In function 'vdpasim_blk_handle_req':
drivers/vdpa/vdpa_sim/vdpa_sim_blk.c:201:3: error: a label can only be part of
a statement and a declaration is not a statement
struct
saddr_to_nid(), so
> export the symbol.
>
> Fixes: 04ad63f086d1 ("cxl/region: Introduce cxl_pmem_region objects")
> Reported-by: Sachin Sant
> Signed-off-by: Michael Ellerman
> ---
Thanks Michael.
Tested-by: Sachin Sant
> arch/powerpc/mm/mem.c | 1 +
> 1 file chang
Linux-next (5.19.0-rc8-next-20220728) fails to build on powerpc with
following error:
ERROR: modpost: "memory_add_physaddr_to_nid" [drivers/cxl/cxl_pmem.ko]
undefined!
make[1]: *** [scripts/Makefile.modpost:128: modules-only.symvers] Error 1
The code in question was last changed by following pat
> The definition of lockup_detector_reconfigure should be exported even in
> that case, and __lockup_detector_reconfigure should remain static.
>
> Fixes: 24a1260705b7 ("watchdog: export lockup_detector_reconfigure")
> Reported-by: Sachin Sant
> Signed-off-by: La
Linux-next (5.19.0-rc8-next-20220726) fails to build on powerpc with following
error:
kernel/watchdog.c:597:20: error: static declaration of
'lockup_detector_reconfigure' follows non-static declaration
static inline void lockup_detector_reconfigure(void)
^~~~
> Fix it by removing the xfs_buf_init/terminate wrappers that just
> allocate and destroy the xfs_buf slab, and move them to the same
> place that all the other slab caches are set up and destroyed.
>
> Reported-by: Sachin Sant
> Fixes: 298f34224506 ("xfs: lockless buffe
While running xfstests (specifically xfs/435) on a IBM Power server booted with
5.19.0-rc6-next-20220715 following warnings are seen:
[ 110.954136] XFS (sdb2): Unmounting Filesystem
[ 110.968860] XFS (sdb1): Unmounting Filesystem
[ 111.115807]
=
> On 15-Jul-2022, at 6:11 PM, Kanchan Joshi wrote:
>
> On Fri, Jul 15, 2022 at 06:07:01PM +0530, Sachin Sant wrote:
>> While running blktests[*] (block/10) on a IBM Power server booted with
>> 5.19.0-rc6-next-20220714 following crash is seen:
> Ming has posted a fix
While running blktests[*] (block/10) on a IBM Power server booted with
5.19.0-rc6-next-20220714 following crash is seen:
[ 9089.636612] null_blk: disk nullb30 created
[ 9089.640752] null_blk: disk nullb31 created
[ 9089.640759] null_blk: module loaded
[ 9134.099371] Kernel attempted to read user p
of thr DR flag.
>
> Jason A. Donenfeld (2):
> powerpc/powernv: rename remaining rng powernv_ functions to pnv_
> powerpc/kvm: don't crash on missing rng, and use darn
>
Boot tested this series and can successfully boot a Power8 server.
fwiw Tested-by: Sachin Sant
- Sachin
> Thanks for the report. I've already submitted a follow up patch:
> https://patchwork.kernel.org/project/linux-crypto/patch/20220630140506.904-1-ig...@cloudflare.com/
Thanks, the fix resolves the issue for me.
- Sachin
Following warning is seen while booting recent -next kernel on IBM Power server.
[1.544420] [ cut here ]
[1.544422] alg: self-tests for rsa-generic (rsa) failed (rc=-22)
[1.544429] WARNING: CPU: 18 PID: 512 at crypto/testmgr.c:5774
alg_test+0x42c/0x850
[1.5
1 - 100 of 371 matches
Mail list logo
