archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <>
To: David Howells <>
Cc: Linus Torvalds <>,
	Al Viro <>,
	Christian Brauner <>,
	Linux FS-devel Mailing List <>,
	Linux Kernel Mailing List <>
Subject: Re: [PATCH 3/4] uapi, x86: Fix the syscall numbering of the mount API syscalls
Date: Thu, 16 May 2019 13:29:19 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, May 16, 2019 at 1:24 PM David Howells <> wrote:
> Fix the syscall numbering of the mount API syscalls so that the numbers
> match between i386 and x86_64 and that they're in the common numbering
> scheme space.
> Fixes: a07b20004793 ("vfs: syscall: Add open_tree(2) to reference or clone a mount")
> Fixes: 2db154b3ea8e ("vfs: syscall: Add move_mount(2) to move mounts around")
> Fixes: 24dcb3d90a1f ("vfs: syscall: Add fsopen() to prepare for superblock creation")
> Fixes: ecdab150fddb ("vfs: syscall: Add fsconfig() for configuring and managing a context")
> Fixes: 93766fbd2696 ("vfs: syscall: Add fsmount() to create a mount for a superblock")
> Fixes: cf3cba4a429b ("vfs: syscall: Add fspick() to select a superblock for reconfiguration")
> Reported-by: Arnd Bergmann <>
> Signed-off-by: David Howells <>


Reviewed-by: Arnd Bergmann <>

  reply	other threads:[~2019-05-16 11:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 11:23 [PATCH 0/4] uapi, vfs: Change the mount API UAPI David Howells
2019-05-16 11:23 ` [PATCH 1/4] uapi, fs: make all new mount api fds cloexec by default David Howells
2019-05-16 11:23 ` [PATCH 2/4] uapi, fsopen: use square brackets around "fscontext" David Howells
2019-05-16 11:23 ` [PATCH 3/4] uapi, x86: Fix the syscall numbering of the mount API syscalls David Howells
2019-05-16 11:29   ` Arnd Bergmann [this message]
2019-05-16 11:24 ` [PATCH 4/4] uapi: Wire up the mount API syscalls on non-x86 arches David Howells
2019-05-16 11:32   ` Arnd Bergmann

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).