From: Isaac Manjarres <isaacmanjarres@google.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
kaleshsingh@google.com, jstultz@google.com, aliceryhl@google.com,
surenb@google.com, kernel-team@android.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Cleanup for memfd_create()
Date: Tue, 7 Jan 2025 10:52:34 -0800 [thread overview]
Message-ID: <Z3138rzvnzBMFEjw@google.com> (raw)
In-Reply-To: <9ee67338-b0af-4fdf-b8d6-bab4e6c4ccc3@lucifer.local>
On Tue, Jan 07, 2025 at 03:09:49PM +0000, Lorenzo Stoakes wrote:
> 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!
>
Hi Lorenzo,
I had uploaded this against Linus' master branch. However, I've uploaded
a second version that is just a rebase on mm-unstable, as requested:
https://lore.kernel.org/all/20250107184804.4074147-1-isaacmanjarres@google.com/
Thanks,
Isaac
prev parent reply other threads:[~2025-01-07 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 23:06 Isaac J. Manjarres
2025-01-02 23:06 ` [PATCH v1 1/2] mm/memfd: Refactor and cleanup the logic in memfd_create() Isaac J. Manjarres
2025-01-02 23:06 ` [PATCH v1 2/2] mm/memfd: Use strncpy_from_user() to read memfd name Isaac J. Manjarres
2025-01-07 15:09 ` [PATCH v1 0/2] Cleanup for memfd_create() Lorenzo Stoakes
2025-01-07 18:52 ` Isaac Manjarres [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z3138rzvnzBMFEjw@google.com \
--to=isaacmanjarres@google.com \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=jstultz@google.com \
--cc=kaleshsingh@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=surenb@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox