linux-kernel - [PATCH 0/3] mm/arch: Fix a few collide definition on private use of VM_FAULT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230205231704.909536-1-peterx@redhat.com>
Date:   Sun,  5 Feb 2023 18:17:01 -0500
From:   Peter Xu <peterx@...hat.com>
To:     linux-mm@...ck.org, linux-kernel@...r.kernel.org
Cc:     peterx@...hat.com, Andrew Morton <akpm@...ux-foundation.org>,
        linux-arm-kernel@...ts.infradead.org, linux-s390@...r.kernel.org
Subject: [PATCH 0/3] mm/arch: Fix a few collide definition on private use of VM_FAULT_*

I noticed a few collision usage on VM_FAULT_* definition in the page fault
path on arm/arm64/s390 where the VM_FAULT_* can overlap with the generic
definition of vm_fault_reason.

The major overlapped part being VM_FAULT_HINDEX_MASK which is used only by
the hugetlb hwpoisoning.

I'm not sure whether any of them can have a real impact, but that does not
look like to be expected.  I didn't copy stable, if anyone thinks it should
please shoot.  Nor did I test them in any form - I just changed the
allocations from top bits and added a comment for each of them.

Please have a look, thanks.

Peter Xu (3):
  mm/arm: Define private VM_FAULT_* reasons from top bits
  mm/arm64: Define private VM_FAULT_* reasons from top bits
  mm/s390: Define private VM_FAULT_* reasons from top bits

 arch/arm/mm/fault.c   |  8 ++++++--
 arch/arm64/mm/fault.c |  8 ++++++--
 arch/s390/mm/fault.c  | 14 +++++++++-----
 3 files changed, 21 insertions(+), 9 deletions(-)

-- 
2.37.3