[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADrL8HVGNPWrhBNgpofgt1kpc5-rCm3GKAFwbupm6_3i6=OBaA@mail.gmail.com>
Date: Thu, 5 Jan 2023 01:52:56 +0000
From: James Houghton <jthoughton@...gle.com>
To: Peter Xu <peterx@...hat.com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Mike Kravetz <mike.kravetz@...cle.com>,
Muchun Song <songmuchun@...edance.com>,
Nadav Amit <nadav.amit@...il.com>,
Andrea Arcangeli <aarcange@...hat.com>,
David Hildenbrand <david@...hat.com>,
Axel Rasmussen <axelrasmussen@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 3/3] mm/uffd: Detect pgtable allocation failures
On Wed, Jan 4, 2023 at 10:52 PM Peter Xu <peterx@...hat.com> wrote:
>
> Before this patch, when there's any pgtable allocation issues happened
> during change_protection(), the error will be ignored from the syscall.
> For shmem, there will be an error dumped into the host dmesg. Two issues
> with that:
>
> (1) Doing a trace dump when allocation fails is not anything close to
> grace..
>
> (2) The user should be notified with any kind of such error, so the user
> can trap it and decide what to do next, either by retrying, or stop
> the process properly, or anything else.
>
> For userfault users, this will change the API of UFFDIO_WRITEPROTECT when
> pgtable allocation failure happened. It should not normally break anyone,
> though. If it breaks, then in good ways.
>
> One man-page update will be on the way to introduce the new -ENOMEM for
> UFFDIO_WRITEPROTECT. Not marking stable so we keep the old behavior on the
> 5.19-till-now kernels.
>
> Reported-by: James Houghton <jthoughton@...gle.com>
> Signed-off-by: Peter Xu <peterx@...hat.com>
Acked-by: James Houghton <jthoughton@...gle.com>
Thanks Peter! :)
Powered by blists - more mailing lists