From: Helge Deller <deller@gmx.de>
To: Jeroen Roovers <jer@gentoo.org>
Cc: linux-parisc@vger.kernel.org
Subject: Re: fanotify_mark()
Date: Tue, 13 Aug 2013 23:29:42 +0200 [thread overview]
Message-ID: <520AA546.2070503@gmx.de> (raw)
In-Reply-To: <20130813154958.7514d525@marga.jer-c2.orkz.net>
On 08/13/2013 03:49 PM, Jeroen Roovers wrote:
> Trying out systemd I found that libc 2.17 does not build
> fanotify_mark() support[1]. When I got it to do that (see attached
> patch, which is probably incorrect), calls to fanotify_mark() still
> failed on a C8000 (64-bit kernel). I am sure I am missing something
> obvious.
>
> [1] https://bugs.gentoo.org/show_bug.cgi?id=480268
In the Linux kernel we use the compat layer for 32bit syscalls on 64bit kernel:
arch/parisc/kernel/syscall_table.S: ENTRY_COMP(fanotify_mark)
which means we call (with 32bit userspace on 64bit kernel):
fs/notify/fanotify/fanotify_user.c:COMPAT_SYSCALL_DEFINE6(fanotify_mark, int, fanotify_fd, unsigned int, flags,
__u32, mask0, __u32, mask1, int, dfd, const char __user *, pathname)
which has 6 parameters.
So, I assume you need one more "i" in this line here (change i:iiiis -> i:iiiiis {to 5 i's}):
> +fanotify_mark EXTRA fanotify_mark i:iiiis __fanotify_mark fanotify_mark@@GLIBC_2.17
Just an assumption...
Helge
next prev parent reply other threads:[~2013-08-13 21:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 13:49 fanotify_mark() Jeroen Roovers
2013-08-13 21:29 ` Helge Deller [this message]
2013-08-13 22:54 ` fanotify_mark() Jeroen Roovers
2013-08-25 23:46 ` fanotify_mark() Jeroen Roovers
2013-08-26 21:27 ` fanotify_mark() Helge Deller
2013-08-26 22:37 ` fanotify_mark() John David Anglin
2013-08-27 14:46 ` systemd real-time signals choices clash with Linux/PARISC available SIGRT range, WAS: fanotify_mark() Jeroen Roovers
2013-08-27 15:26 ` John David Anglin
2013-08-27 15:52 ` John David Anglin
2013-09-18 18:40 ` Helge Deller
2013-09-18 18:58 ` John David Anglin
2013-08-27 14:31 ` fanotify_mark() Jeroen Roovers
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=520AA546.2070503@gmx.de \
--to=deller@gmx.de \
--cc=jer@gentoo.org \
--cc=linux-parisc@vger.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).