From: Andy Lutomirski <luto@kernel.org>
To: Jan Kara <jack@suse.cz>, linux-arch <linux-arch@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Brian Gerst <brgerst@gmail.com>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] fanotify: Fix fanotify_mark() on 32-bit x86
Date: Fri, 27 Nov 2020 10:13:01 -0800 [thread overview]
Message-ID: <CALCETrVaj6rnvqX2cxj3u++hg_XZD-Zo4iYUPTFDiwaO49xDrg@mail.gmail.com> (raw)
In-Reply-To: <20201126155246.25961-1-jack@suse.cz>
On Thu, Nov 26, 2020 at 7:52 AM Jan Kara <jack@suse.cz> wrote:
>
> Commit converting syscalls taking 64-bit arguments to new scheme of compat
> handlers omitted converting fanotify_mark(2) which then broke the
> syscall for 32-bit x86 builds. Add missed conversion. It is somewhat
> cumbersome since we need to keep the original compat handler for all the
> other 32-bit archs.
>
This is stupendously ugly. I'm not really sure how this is supposed
to work on any 32-bit arch. I'm also not sure whether we should
expect the SYSCALL_DEFINE macros to figure this out by themselves.
At the very least, the native arm 32 and arm64 compat cases should get tested.
Al and Christoph, you're probably a lot more familiar than I am with
the nasty details of syscall ABI with 64-bit arguments.
> CC: Brian Gerst <brgerst@gmail.com>
> Suggested-by: Borislav Petkov <bp@suse.de>
> Reported-by: Paweł Jasiak <pawel@jasiak.xyz>
> Reported-and-tested-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> Fixes: 121b32a58a3a ("x86/entry/32: Use IA32-specific wrappers for syscalls taking 64-bit arguments")
> CC: stable@vger.kernel.org
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> arch/x86/entry/syscalls/syscall_32.tbl | 2 +-
> fs/notify/fanotify/fanotify_user.c | 7 ++++++-
> 2 files changed, 7 insertions(+), 2 deletions(-)
>
> I plan to queue this fix into my tree next week. I'd be happy if someone with
> x86 ABI knowledge checks whether I've got the patch right (especially various
> config variants) because it was mostly a guesswork of me & Boris ;). Thanks!
>
> diff --git a/arch/x86/entry/syscalls/syscall_32.tbl b/arch/x86/entry/syscalls/syscall_32.tbl
> index 0d0667a9fbd7..b2ec6ff88307 100644
> --- a/arch/x86/entry/syscalls/syscall_32.tbl
> +++ b/arch/x86/entry/syscalls/syscall_32.tbl
> @@ -350,7 +350,7 @@
> 336 i386 perf_event_open sys_perf_event_open
> 337 i386 recvmmsg sys_recvmmsg_time32 compat_sys_recvmmsg_time32
> 338 i386 fanotify_init sys_fanotify_init
> -339 i386 fanotify_mark sys_fanotify_mark compat_sys_fanotify_mark
> +339 i386 fanotify_mark sys_ia32_fanotify_mark
> 340 i386 prlimit64 sys_prlimit64
> 341 i386 name_to_handle_at sys_name_to_handle_at
> 342 i386 open_by_handle_at sys_open_by_handle_at compat_sys_open_by_handle_at
> diff --git a/fs/notify/fanotify/fanotify_user.c b/fs/notify/fanotify/fanotify_user.c
> index 3e01d8f2ab90..ba38f0fec4d0 100644
> --- a/fs/notify/fanotify/fanotify_user.c
> +++ b/fs/notify/fanotify/fanotify_user.c
> @@ -1292,8 +1292,13 @@ SYSCALL_DEFINE5(fanotify_mark, int, fanotify_fd, unsigned int, flags,
> return do_fanotify_mark(fanotify_fd, flags, mask, dfd, pathname);
> }
>
> -#ifdef CONFIG_COMPAT
> +#if defined(CONFIG_COMPAT) || defined(CONFIG_X86_32) || \
> + defined(CONFIG_IA32_EMULATION)
> +#if defined(CONFIG_X86_32) || defined(CONFIG_IA32_EMULATION)
> +SYSCALL_DEFINE6(ia32_fanotify_mark,
> +#elif CONFIG_COMPAT
> COMPAT_SYSCALL_DEFINE6(fanotify_mark,
> +#endif
> int, fanotify_fd, unsigned int, flags,
> __u32, mask0, __u32, mask1, int, dfd,
> const char __user *, pathname)
> --
> 2.16.4
>
next parent reply other threads:[~2020-11-27 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201126155246.25961-1-jack@suse.cz>
2020-11-27 18:13 ` Andy Lutomirski [this message]
2020-11-27 22:30 ` [PATCH] fanotify: Fix fanotify_mark() on 32-bit x86 Brian Gerst
2020-11-28 0:36 ` Andy Lutomirski
2020-11-30 22:21 ` Brian Gerst
2020-12-01 8:30 ` Jan Kara
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=CALCETrVaj6rnvqX2cxj3u++hg_XZD-Zo4iYUPTFDiwaO49xDrg@mail.gmail.com \
--to=luto@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=will@kernel.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).