From: Matthew Bobrowski <repnop@google.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Vlastimil Babka <vbabka@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 0/2] Introduce simple pidfd to task helper
Date: Thu, 7 Oct 2021 22:12:57 +0000 [thread overview]
Message-ID: <YV9w6QQcGlgYWjfd@google.com> (raw)
In-Reply-To: <20211004125050.1153693-1-christian.brauner@ubuntu.com>
On Mon, Oct 04, 2021 at 02:50:48PM +0200, Christian Brauner wrote:
> Hey everyone,
>
> This adds a simple helper to get rid of some code duplication introduced
> with the addition of two new pidfd-based syscalls in mm. We should've
> probably added the helper right away and I think I mentioned this during
> in the review on one of the revisions but we probably just lost track of
> it. If this looks ok to you, I'll queue this up for next.
I went through the series. Seems like a very sensible thing to do, so thanks for
adding the helper and updating the call sites accordingly.
Reviewed-by: Matthew Bobrowski <repnop@google.com>
> Christian Brauner (2):
> pid: add pidfd_get_task() helper
> mm: use pidfd_get_task()
>
> include/linux/pid.h | 1 +
> kernel/pid.c | 34 ++++++++++++++++++++++++++++++++++
> mm/madvise.c | 15 +++------------
> mm/oom_kill.c | 15 +++------------
> 4 files changed, 41 insertions(+), 24 deletions(-)
>
>
> base-commit: 9e1ff307c779ce1f0f810c7ecce3d95bbae40896
> --
> 2.30.2
>
/M
prev parent reply other threads:[~2021-10-07 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 12:50 Christian Brauner
2021-10-04 12:50 ` [PATCH 1/2] pid: add pidfd_get_task() helper Christian Brauner
2021-10-08 8:47 ` David Hildenbrand
2021-10-11 10:45 ` Christian Brauner
2021-10-04 12:50 ` [PATCH 2/2] mm: use pidfd_get_task() Christian Brauner
2021-10-07 22:12 ` Matthew Bobrowski [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=YV9w6QQcGlgYWjfd@google.com \
--to=repnop@google.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=christian.brauner@ubuntu.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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