[lkml]   [2020]   [Mar]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v7 5/7] mm: support both pid and pidfd for process_madvise
On 3/2/20 8:36 PM, Minchan Kim wrote:
> There is a demand[1] to support pid as well pidfd for process_madvise
> to reduce unnecessary syscall to get pidfd if the user has control of
> the target process(ie, they could guarantee the process is not gone
> or pid is not reused).
> This patch aims for supporting both options like waitid(2). So, the
> syscall is currently,
> int process_madvise(int which, pid_t pid, void *addr,
> size_t length, int advise, unsigned long flag);

This is again halfway between kernel and userspace description, so if we stick
to userspace then it's:

int process_madvise(idtype_t idtype, id_t id, void *addr,
size_t length, int advice, unsigned long flags);

> @which is actually idtype_t for userspace libray and currently,
> it supports P_PID and P_PIDFD.
> [1]
> Cc: Christian Brauner <>
> Reviewed-by: Suren Baghdasaryan <>
> Suggested-by: Kirill Tkhai <>
> Signed-off-by: Minchan Kim <>

Reviewed-by: Vlastimil Babka <>

 \ /
  Last update: 2020-03-06 12:15    [W:0.326 / U:2.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site