Re: [PATCH v2 1/1] arch/fault: don't print logs for pte marker poison errors

On Wed, May 15, 2024 at 1:19 PM Borislav Petkov wrote: > > On Wed, May 15, 2024 at 12:19:16PM -0700, Axel Rasmussen wrote: > > An unprivileged process can allocate a VMA, use the userfaultfd API to > > install one of these PTE markers, and then register a no-op SIGBUS >

Re: [PATCH v2 1/1] arch/fault: don't print logs for pte marker poison errors

On Wed, May 15, 2024 at 11:33 AM Borislav Petkov wrote: > > On Wed, May 15, 2024 at 10:33:03AM -0700, Axel Rasmussen wrote: > > Right, the goal is to still have the process get a SIGBUS, but to > > avoid the "MCE error" log message. The basic issue is, unprivileged >

Re: [PATCH v2 1/1] arch/fault: don't print logs for pte marker poison errors

On Wed, May 15, 2024 at 3:54 AM Oscar Salvador wrote: > > On Wed, May 15, 2024 at 12:41:42PM +0200, Borislav Petkov wrote: > > On Fri, May 10, 2024 at 11:29:26AM -0700, Axel Rasmussen wrote: > > > @@ -3938,7 +3938,7 @@ static vm_fault_t handle_pte_marker(struct

[PATCH v2 1/1] arch/fault: don't print logs for pte marker poison errors

tion, add a new VM_FAULT_HWPOISON_SILENT flag. This is expected to be set *in addition to* one of the existing VM_FAULT_HWPOISON or VM_FAULT_HWPOISON_LARGE flags (which are mutually exclusive). Reviewed-by: John Hubbard Signed-off-by: Axel Rasmussen --- arch/parisc/mm/fault.c | 7 +-- arch/pow

[PATCH v2 0/1] arch/fault: don't print logs for simulated poison errors

VM_FAULT_HWPOISON_SILENT. - Rebase onto mm-unstable, to remove dependency on another patch which it appears will not get merged. - Update comments / commit message to mention swapin errors in addition to UFFDIO_POISON. Axel Rasmussen (1): arch/fault: don't print logs for pte marker p

Re: [PATCH 1/1] arch/fault: don't print logs for simulated poison errors

On Thu, May 9, 2024 at 2:05 PM Peter Xu wrote: > > On Thu, May 09, 2024 at 01:39:07PM -0700, Axel Rasmussen wrote: > > For real MCEs, various architectures print log messages when poisoned > > memory is accessed (which results in a SIGBUS). These messages can be > >

Re: [PATCH 1/1] arch/fault: don't print logs for simulated poison errors

On Thu, May 9, 2024 at 2:30 PM John Hubbard wrote: > > On 5/9/24 1:39 PM, Axel Rasmussen wrote: > > For real MCEs, various architectures print log messages when poisoned > > memory is accessed (which results in a SIGBUS). These messages can be > > important for users

[PATCH 1/1] arch/fault: don't print logs for simulated poison errors

ually exclusive). Signed-off-by: Axel Rasmussen --- arch/parisc/mm/fault.c | 7 +-- arch/powerpc/mm/fault.c | 6 -- arch/x86/mm/fault.c | 6 -- include/linux/mm_types.h | 5 + mm/hugetlb.c | 3 ++- mm/memory.c | 2 +- 6 files changed, 21 insertions(

[PATCH 0/1] arch/fault: don't print logs for simulated poison errors

kernel.org/r/20240509100148.22384-1-osalva...@suse.de The latter is in mm-unstable currently, but the former is not (yet?). It would need to be taken before this patch for it to apply cleanly. Axel Rasmussen (1): arch/fault: don't print logs for simulated poison errors arch/parisc/m

Re: [PATCH v2 2/2] arm64: hugetlb: Fix set_huge_pte_at() to work with all swap entries

Looks correct to me - thanks for the fix! Reviewed-by: Axel Rasmussen On Fri, Sep 22, 2023 at 9:41 AM Ryan Roberts wrote: > > On 22/09/2023 17:14, Will Deacon wrote: > > On Fri, Sep 22, 2023 at 12:58:04PM +0100, Ryan Roberts wrote: > >> When called with a swap entry that