From: Christoph Hellwig <hch@infradead.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/namespace: add __user to open_tree and move_mount syscalls
Date: Tue, 15 Oct 2019 05:41:54 -0700 [thread overview]
Message-ID: <20191015124154.GA23798@infradead.org> (raw)
In-Reply-To: <20191015103502.27691-1-ben.dooks@codethink.co.uk>
On Tue, Oct 15, 2019 at 11:35:02AM +0100, Ben Dooks wrote:
> -SYSCALL_DEFINE3(open_tree, int, dfd, const char *, filename, unsigned, flags)
> +SYSCALL_DEFINE3(open_tree, int, dfd, const char __user *, filename, unsigned, flags)
Please make sure to wrap lines after 80 characters.
Otherwise this looks good.
prev parent reply other threads:[~2019-10-15 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 10:35 [PATCH] fs/namespace: add __user to open_tree and move_mount syscalls Ben Dooks
2019-10-15 12:41 ` Christoph Hellwig [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=20191015124154.GA23798@infradead.org \
--to=hch@infradead.org \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).