Error conditions are not handled properly if altmap is not present
and PMD_SIZE vmemmap_alloc_block_buf fails.
In this patch, if vmemmap_alloc_block_buf fails in the non-altmap
case, we will fall back to the base mapping.
Signed-off-by: Donet Tom
---
arch/powerpc/mm/book3s64/radix_pgtable.c | 2
If we always align the vmemmap start to PAGE_SIZE, there is a
chance that we may end up allocating page-sized vmemmap backing
pages in RAM in the altmap not present case, because a PAGE_SIZE
aligned address is not PMD_SIZE-aligned.
In this patch, we are aligning the vmemmap start address to
PMD_SI
On Fri, May 2, 2025, at 15:30, James Bottomley wrote:
> On Fri, 2025-05-02 at 08:53 +0200, Thomas Weißschuh wrote:
> > Specifically the output of any party can recreate bit-by-bit
> > identical copies of all specified artifacta previous build (the
> > public key, module signatures) is not available
On 5/2/25 3:30 PM, James Bottomley wrote:
Under a your interpretation of the above, any signed binary isn't
"reproducible" even if the underlying build was, which means any secure
boot kernel would never be reproducible because it also has to be a
signed binary. The solution is simple: can you s
On Wed, 12 Feb 2025 08:40:48 +0100, Christophe Leroy wrote:
> When a kernel log containing --- at the start of a line is copied into
> a patch message, 'git am' drops everything located after that ---.
>
> Replace --- by to avoid that.
>
>
Applied to powerpc/next.
[1/1] powerpc: Don't use
On Thu, 17 Apr 2025 12:53:05 +0200, Jiri Slaby (SUSE) wrote:
> The Fixes commit below tried to add CONFIG_PPC_BOOK3S to one of the
> conditions to enable the build of ppc_save_regs.o. But it failed to do
> so, in fact. The commit omitted to add a dollar sign.
>
> Therefore, ppc_save_regs.o is buil
On Thu, 17 Apr 2025 00:42:27 +0530, Hari Bathini wrote:
> While r15 is clobbered always with PPC_FTRACE_OUT_OF_LINE, it is
> not restored in livepatch sequence leading to not so obvious fails
> like below:
>
> BUG: Unable to handle kernel data access on write at 0xc00f9078
> Faulting i
On Wed, 05 Mar 2025 14:32:36 +0530, Gautam Menghani wrote:
> When a system is being suspended to RAM, the PCI devices are also
> suspended and the PPC code ends up calling pseries_msi_compose_msg() and
> this triggers the BUG_ON() in __pci_read_msi_msg() because the device at
> this point is in red
On Tue, 11 Feb 2025 10:20:54 -0600, Eddie James wrote:
> In non-smp configurations, crash_kexec_prepare is never called in
> the crash shutdown path. One result of this is that the crashing_cpu
> variable is never set, preventing crash_save_cpu from storing the
> NT_PRSTATUS elf note in the core du
On Tue, 22 Apr 2025 13:56:09 +0530, Hari Bathini wrote:
> arch_bpf_trampoline_size() provides JIT size of the BPF trampoline
> before the buffer for JIT'ing it is allocated. The total number of
> instructions emitted for BPF trampoline JIT code depends on where
> the final image is located. So, the
On Tue, 29 Apr 2025 19:28:47 -0700, Haren Myneni wrote:
> Fix the description format for the following build warnings:
>
> "Documentation/userspace-api/ioctl/ioctl-number.rst:369:
> ERROR: Malformed table. Text in column margin in table line 301.
>
> 0xB2 03-05 arch/powerpc/include/uapi/asm/papr
On Tue, 29 Apr 2025 14:14:18 -0700, Haren Myneni wrote:
> Fix the following build warning:
> usr/include/asm/papr-platform-dump.h:12: found __[us]{8,16,32,64} type
> without #include
>
> Fixes: 8aa9efc0be66 ("powerpc/pseries: Add papr-platform-dump character
> driver for dump retrieval")
> Clos
12 matches
Mail list logo
