linux-kernel - Re: [PATCH v1 0/2] Cleanup for memfd

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9ee67338-b0af-4fdf-b8d6-bab4e6c4ccc3@lucifer.local>
Date: Tue, 7 Jan 2025 15:09:49 +0000
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: "Isaac J. Manjarres" <isaacmanjarres@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, kaleshsingh@...gle.com,
        jstultz@...gle.com, aliceryhl@...gle.com, surenb@...gle.com,
        kernel-team@...roid.com, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 0/2] Cleanup for memfd_create()

On Thu, Jan 02, 2025 at 03:06:53PM -0800, Isaac J. Manjarres wrote:
> memfd_create() handles all of its logic in a single function. Some of
> the logic in the function is also somewhat contrived (i.e. copying the
> memfd name from userpace).
>
> This series aims to cleanup memfd_create() by splitting out the logic
> into helper functions, and simplifying the memfd name copying to make
> the code easier to follow.
>
> This has no intended functional changes.
>

What is this against? I tried b4 shazam'ing it against mm-unstable and it
didn't apply. Could you rebase on mm-unstable?

Thanks!

> Isaac J. Manjarres (2):
>   mm/memfd: Refactor and cleanup the logic in memfd_create()
>   mm/memfd: Use strncpy_from_user() to read memfd name
>
>  mm/memfd.c | 101 +++++++++++++++++++++++++++++++----------------------
>  1 file changed, 59 insertions(+), 42 deletions(-)
>
> --
> 2.47.1.613.gc27f4b7a9f-goog
>