linux-kernel - [PATCH 00/12] mm/debug_vm

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: <20210706061748.161258-1-gshan@redhat.com>
Date:   Tue,  6 Jul 2021 14:17:36 +0800
From:   Gavin Shan <gshan@...hat.com>
To:     linux-mm@...ck.org
Cc:     linux-kernel@...r.kernel.org, anshuman.khandual@....com,
        catalin.marinas@....com, will@...nel.org,
        akpm@...ux-foundation.org, shan.gavin@...il.com, chuhu@...hat.com
Subject: [PATCH 00/12] mm/debug_vm_pgtable: Enhancements

There are couple of issues with current implementations and this series
tries to resolve the issues:

  (a) All needed information are scattered in variables, passed to various
      test functions. The code is organized in pretty much relaxed fashion.

  (b) The page isn't allocated from buddy during page table entry modifying
      tests. The page can be invalid, conflicting to the implementations
      of set_{pud, pmd, pte}_at() on ARM64. The target page is accessed
      so that the iCache can be flushed when execution permission is given
      on ARM64. Besides, the target page can be unmapped and access to
      it causes kernel crash.

"struct vm_pgtable_debug" is introduced to address issue (a). For issue
(b), the used page is allocated from buddy in page table entry modifying
tests. The corresponding tets will be skipped if we fail to allocate the
(huge) page. For other test cases, the original page around to kernel
symbol (@start_kernel) is still used.

The patches are organized as below. PATCH[2-10] could be combined to one
patch, but it will make the review harder:

  PATCH[1] introduces "struct vm_pgtable_debug" as place holder of all
           needed information. With it, the old and new implementation
           can coexist.
  PATCH[2-10] uses "struct vm_pgtable_debug" in various test functions.
  PATCH[11] removes the old implementation.
  PATCH[12] fixes the issue of corrupted page flag for ARM64


Gavin Shan (12):
  mm/debug_vm_pgtable: Introduce struct vm_pgtable_debug
  mm/debug_vm_pgtable: Use struct vm_pgtable_debug in basic tests
  mm/debug_vm_pgtable: Use struct vm_pgtable_debug in leaf and savewrite
    tests
  mm/debug_vm_pgtable: Use struct vm_pgtable_debug in protnone and
    devmap tests
  mm/vm_debug_pgtable: Use struct vm_pgtable_debug in soft_dirty and
    swap tests
  mm/debug_vm_pgtable: Use struct vm_pgtable_debug in migration and thp
    tests
  mm/debug_vm_pgtable: Use struct vm_pgtable_debug in PTE modifying
    tests
  mm/debug_vm_pgtable: Use struct vm_pgtable_debug in PMD modifying
    tests
  mm/vm_debug_pgtable: Use struct vm_pgtable_debug in PUD modifying
    tests
  mm/debug_vm_pgtable: Use struct vm_pgtable_debug in PGD and P4D
    modifying tests
  mm/debug_vm_pgtable: Remove unused code
  mm/debug_vm_pgtable: Fix corrupted page flag

 mm/debug_vm_pgtable.c | 875 ++++++++++++++++++++++++------------------
 1 file changed, 500 insertions(+), 375 deletions(-)

-- 
2.23.0