From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, Minchan Kim <minchan@kernel.org>
Subject: Re: mmotm 2020-04-26-00-15 uploaded (mm/madvise.c)
Date: Tue, 28 Apr 2020 09:15:41 +1000 [thread overview]
Message-ID: <20200428091541.11a76842@canb.auug.org.au> (raw)
In-Reply-To: <39bcdbb6-cac8-aa3b-c543-041f9c28c730@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]
Hi all,
On Sun, 26 Apr 2020 15:48:35 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> I had to add 2 small patches to have clean madvise.c builds:
>
>
> ---
> include/linux/syscalls.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> --- mmotm-2020-0426-0015.orig/include/linux/syscalls.h
> +++ mmotm-2020-0426-0015/include/linux/syscalls.h
> @@ -876,9 +876,9 @@ asmlinkage long sys_munlockall(void);
> asmlinkage long sys_mincore(unsigned long start, size_t len,
> unsigned char __user * vec);
> asmlinkage long sys_madvise(unsigned long start, size_t len, int behavior);
> -
> -asmlinkage long sys_process_madvise(int which, pid_t pid, unsigned long start,
> - size_t len, int behavior, unsigned long flags);
> +asmlinkage long sys_process_madvise(int which, pid_t upid,
> + const struct iovec __user *vec, unsigned long vlen,
> + int behavior, unsigned long flags);
> asmlinkage long sys_remap_file_pages(unsigned long start, unsigned long size,
> unsigned long prot, unsigned long pgoff,
> unsigned long flags);
>
> ---
> and
> ---
> mm/madvise.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- mmotm-2020-0426-0015.orig/mm/madvise.c
> +++ mmotm-2020-0426-0015/mm/madvise.c
> @@ -23,12 +23,14 @@
> #include <linux/file.h>
> #include <linux/blkdev.h>
> #include <linux/backing-dev.h>
> +#include <linux/compat.h>
> #include <linux/pagewalk.h>
> #include <linux/swap.h>
> #include <linux/swapops.h>
> #include <linux/shmem_fs.h>
> #include <linux/mmu_notifier.h>
> #include <linux/sched/mm.h>
> +#include <linux/uio.h>
>
> #include <asm/tlb.h>
>
I added these to linux-next today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-27 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 7:16 mmotm 2020-04-26-00-15 uploaded akpm
2020-04-26 17:26 ` mmotm 2020-04-26-00-15 uploaded (mm/madvise.c) Randy Dunlap
2020-04-26 22:48 ` Randy Dunlap
2020-04-27 20:50 ` Andrew Morton
2020-04-27 23:45 ` Minchan Kim
2020-04-29 8:43 ` Oleksandr Natalenko
2020-04-27 23:15 ` Stephen Rothwell [this message]
2020-04-27 23:28 ` Minchan Kim
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=20200428091541.11a76842@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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