Re: [PATCH] powerpc/boot: Remove duplicate typedefs from libfdt_env.h

On Thu, Mar 29, 2018 at 07:26:52PM -0700, Mark Greer wrote: > On Thu, Mar 29, 2018 at 07:22:50PM -0700, Mark Greer wrote: > > On Tue, Mar 20, 2018 at 10:55:07AM +1100, Oliver wrote: > > > > Yeah that's pretty odd. It might be a bug in your specific version of > > > GCC since I can't replicate it

Re: [PATCH] PCI/IOV: Add missing prototype for powerpc specific

On Thu, Mar 22, 2018 at 09:33:55PM +0100, Mathieu Malaterre wrote: > Some prototypes for weak functions were missing for powerpc specific > functions. Add the missing prototypes to the CONFIG_PCI_IOV block. This > fixes the following three warnings treated as error when using W=1: > >

Re: [PATCH v2] crypto: talitos - fix IPsec cipher in length

On Thu, Mar 22, 2018 at 10:57:01AM +0100, Christophe Leroy wrote: > For SEC 2.x+, cipher in length must contain only the ciphertext length. > In case of using hardware ICV checking, the ICV length is provided via > the "extent" field of the descriptor pointer. > > Cc: #

[PATCH 2/2] powerpc/pseries: Restore default security feature flags on setup

After migration the security feature flags might have changed (e.g., destination system with unpatched firmware), but some flags are not set/clear again in init_cpu_char_feature_flags() because it assumes the security flags to be the defaults. Additionally, if the H_GET_CPU_CHARACTERISTICS

[PATCH 1/2] powerpc: Move default security feature flags

This moves the definition of the default security feature flags (i.e., enabled by default) closer to the security feature flags. This can be used to restore current flags to the default flags. Signed-off-by: Mauricio Faria de Oliveira ---

Re: [RFC] new SYSCALL_DEFINE/COMPAT_SYSCALL_DEFINE wrappers

On Fri, Mar 30, 2018 at 12:58:02PM +0200, Ingo Molnar wrote: > * John Paul Adrian Glaubitz wrote: > > > On 03/27/2018 12:40 PM, Linus Torvalds wrote: > > > On Mon, Mar 26, 2018 at 4:37 PM, John Paul Adrian Glaubitz > > > wrote: > > >>

Linux 4.16: Reported regressions as of Friday, 2018-03-30

On 26.03.2018 01:37, Linus Torvalds wrote: > […] Anyway. Go out and test. And let's hope next week is nice and calm and > I can release the final 4.16 next Sunday without any extra rc's. > >Linus Hi! Find below my seventh regression report for Linux 4.16; it's a "the final

[PATCH] powerpc: fix spelling mistake: "Usupported" -> "Unsupported"

From: Colin Ian King Trivial fix to spelling mistake in bootx_printf message text Signed-off-by: Colin Ian King --- arch/powerpc/platforms/powermac/bootx_init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] powerpc/mm/hash: Move the slb_addr_limit check within PPC_MM_SLICES

Michael Ellerman a écrit : "Aneesh Kumar K.V" writes: Should not have any impact, because we always select PP_MM_SLICES these days. Nevertheless it is good to indicate that slb_addr_limit is available only with slice code. That file

[RFC 3/3] powerpc/mce: Handle memcpy_mcsafe

Add a blocking notifier callback to be called in real-mode on machine check exceptions for UE (ld/st) errors only. The patch registers a callback on boot to be notified of machine check exceptions and returns a NOTIFY_STOP when a page of interest is seen as the source of the machine check

[RFC 2/3] powerpc/memcpy: Add memcpy_mcsafe for pmem

The pmem infrastructure uses memcpy_mcsafe in the pmem layer so as to convert machine check excpetions into a return value on failure in case a machine check exception is encoutered during the memcpy. This patch largely borrows from the copyuser_power7 logic and does not add the VMX

[RFC 1/3] powerpc/mce: Bug fixes for MCE handling in kernel space

The code currently assumes PAGE_SHIFT as the shift value of the pfn, this works correctly (mostly) for user space pages, but the correct thing to do is 1. Extrace the shift value returned via the pte-walk API's 2. Use the shift value to access the instruction address. Note, the final physical

[RFC 0/3] Add support for memcpy_mcsafe

memcpy_mcsafe() is an API currently used by the pmem subsystem to convert errors while doing a memcpy (machine check exception errors) to a return value. This patchset consists of three patches 1. The first patch is a bug fix to handle machine check errors correctly while walking the page tables

[PATCH 2/2] powerpc/mm/radix: Update command line parsing for disable_radix

kernel parameter disable_radix takes different options disable_radix=yes|no|1|0 or just disable_radix. prom_init parsing is not supporting these options. Signed-off-by: Aneesh Kumar K.V --- arch/powerpc/kernel/prom_init.c| 16 +---

[PATCH 1/2] powerpc/mm/radix: Parse disable_radix commandline correctly.

From: "Aneesh Kumar K.V" kernel parameter disable_radix takes different options disable_radix=yes|no|1|0 or just disable_radix. When using the later format we get below error. `Malformed early option 'disable_radix'` Signed-off-by: Aneesh Kumar K.V

[PATCH V3] powerpc/mm/hugetlb: initialize the pagetable cache correctly for hugetlb

From: "Aneesh Kumar K.V" With 64k page size, we have hugetlb pte entries at the pmd and pud level for book3s64. We don't need to create a separate page table cache for that. With 4k we need to make sure hugepd page table cache for 16M is placed at PUD level and

[PATCH] powerpc/kvm: Fix guest boot issue DAWR cpu feature

SLOF check the 'sc 1' support by issuing a hcall with H_SET_DABR. With recent patch to make the hcall return H_UNSUPPORTED, we get guest boot failures. SLOF can work with the hcall failure H_HARDWARE for the above hcall. Switch the return value to H_HARDWARE instead of H_UNSUPPORTED so that we

Re: [PATCH] powerpc/mm/hash: Move the slb_addr_limit check within PPC_MM_SLICES

"Aneesh Kumar K.V" writes: > Should not have any impact, because we always select PP_MM_SLICES these days. > Nevertheless it is good to indicate that slb_addr_limit is available only > with slice code. That file can only be built if PPC_MM_SLICES=y. So let's

Re: [PATCH] Extract initrd free logic from arch-specific code.

* Shea Levy wrote: > Now only those architectures that have custom initrd free requirements > need to define free_initrd_mem. > > Signed-off-by: Shea Levy Please put the Kconfig symbol name this patch introduces both into the title, so that people know

Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap.

On Fri 2018-03-30 12:07:58, Ilya Smith wrote: > Hi > > > On 30 Mar 2018, at 10:55, Pavel Machek wrote: > > > > Hi! > > > >> Current implementation doesn't randomize address returned by mmap. > >> All the entropy ends with choosing mmap_base_addr at the process > >> creation.

Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap.

Hi! > Current implementation doesn't randomize address returned by mmap. > All the entropy ends with choosing mmap_base_addr at the process > creation. After that mmap build very predictable layout of address > space. It allows to bypass ASLR in many cases. This patch make > randomization of

Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap.

> On 30 Mar 2018, at 12:57, Pavel Machek wrote: > > On Fri 2018-03-30 12:07:58, Ilya Smith wrote: >> Hi >> >>> On 30 Mar 2018, at 10:55, Pavel Machek wrote: >>> >>> Hi! >>> Current implementation doesn't randomize address returned by mmap. All the

Re: [RFC PATCH v2 0/2] Randomization of address chosen by mmap.

Hi > On 30 Mar 2018, at 10:55, Pavel Machek wrote: > > Hi! > >> Current implementation doesn't randomize address returned by mmap. >> All the entropy ends with choosing mmap_base_addr at the process >> creation. After that mmap build very predictable layout of address >> space.

Re: [PATCH] powerpc: kexec_file: Fix error code when trying to load kdump kernel

On Thu, Mar 29, 2018 at 04:05:43PM -0300, Thiago Jung Bauermann wrote: > kexec_file_load() on powerpc doesn't support kdump kernels yet, so it > returns -ENOTSUPP in that case. > > I've recently learned that this errno is internal to the kernel and isn't > supposed to be exposed to userspace.

Re: [RFC] new SYSCALL_DEFINE/COMPAT_SYSCALL_DEFINE wrappers

* John Paul Adrian Glaubitz wrote: > On 03/27/2018 12:40 PM, Linus Torvalds wrote: > > On Mon, Mar 26, 2018 at 4:37 PM, John Paul Adrian Glaubitz > > wrote: > >> > >> What about a tarball with a minimal Debian x32 chroot? Then you can

Re: [PATCH] powerpc: kexec_file: Fix error code when trying to load kdump kernel

On 03/29/18 at 04:05pm, Thiago Jung Bauermann wrote: > kexec_file_load() on powerpc doesn't support kdump kernels yet, so it > returns -ENOTSUPP in that case. > > I've recently learned that this errno is internal to the kernel and isn't > supposed to be exposed to userspace. Therefore, change to