Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Peter Xu <peterx@redhat.com>
To:     linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc:     Hugh Dickins <hughd@google.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Andrea Arcangeli <aarcange@redhat.com>, peterx@redhat.com,
        Mike Kravetz <mike.kravetz@oracle.com>,
        Axel Rasmussen <axelrasmussen@google.com>
Subject: [PATCH 0/2] mm/hugetlb: Fix issues on file sealing and fork
Date:   Sat,  1 May 2021 10:41:08 -0400
Message-Id: <20210501144110.8784-1-peterx@redhat.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hugh reported issue with F_SEAL_FUTURE_WRITE not applied correctly to=0D
hugetlbfs, which I can easily verify using the memfd_test program, which se=
ems=0D
that the program is hardly run with hugetlbfs pages (as by default shmem).=
=0D
=0D
Meanwhile I found another probably even more severe issue on that hugetlb f=
ork=0D
won't wr-protect child cow pages, so child can potentially write to parent=
=0D
private pages.  Patch 2 addresses that.=0D
=0D
After this series applied, "memfd_test hugetlbfs" should start to pass.=0D
=0D
Please review, thanks.=0D
=0D
Peter Xu (2):=0D
  mm/hugetlb: Fix F_SEAL_FUTURE_WRITE=0D
  mm/hugetlb: Fix cow where page writtable in child=0D
=0D
 fs/hugetlbfs/inode.c |  5 +++++=0D
 include/linux/mm.h   | 32 ++++++++++++++++++++++++++++++++=0D
 mm/hugetlb.c         |  2 ++=0D
 mm/shmem.c           | 22 ++++------------------=0D
 4 files changed, 43 insertions(+), 18 deletions(-)=0D
=0D
-- =0D
2.31.1=0D
=0D