From: Helge Deller <deller@gmx.de>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH] fix fanotify syscall check on compat kernel
Date: Wed, 16 Apr 2014 21:00:28 +0200 [thread overview]
Message-ID: <20140416190028.GA2093@ls3530.fritz.box> (raw)
The fanotify[0-5] testcases use the myfanotify_mark() wrapper for the
fanotify_mark() syscall. But the #define does not take into account, that
the mask field is actually of type _u64 where we need to split the hi
and low word in the syscall on a 32bit arch.
The attached patch converts the #define to a inline function where
the compiler will help to convert the given values to the correct types
(e.g. unsigned long).
Bug found and tested on the parisc/hppa (32bit userspace with 64bit
kernel) arch.
Signed-off-by: Helge Deller <deller@gmx.de>
diff --git a/testcases/kernel/syscalls/fanotify/fanotify.h b/testcases/kernel/syscalls/fanotify/fanotify.h
index a4c2a8f..b13cb7b 100644
--- a/testcases/kernel/syscalls/fanotify/fanotify.h
+++ b/testcases/kernel/syscalls/fanotify/fanotify.h
@@ -28,12 +28,26 @@
#ifndef __FANOTIFY_H__
#define __FANOTIFY_H__
+#include <sys/types.h>
+#include <endian.h>
+#include "config.h"
+#include "linux_syscall_numbers.h"
+
/* fanotify(7) wrappers */
#define myfanotify_init(flags, event_f_flags) \
syscall(__NR_fanotify_init, flags, event_f_flags)
-#define myfanotify_mark(fd, flags, mask, dfd, pathname) \
- syscall(__NR_fanotify_mark, fd, flags, mask, dfd, pathname)
+long myfanotify_mark(int fd, unsigned int flags, unsigned long long mask, int dfd, const char *pathname)
+{
+#if __WORDSIZE == 64
+ return ltp_syscall(__NR_fanotify_mark, fd, flags, mask, dfd, pathname);
+#else
+ return ltp_syscall(__NR_fanotify_mark, fd, flags,
+ __LONG_LONG_PAIR((unsigned long) (mask >> 32),
+ (unsigned long) mask),
+ dfd, (unsigned long) pathname);
+#endif
+}
#endif /* __FANOTIFY_H__ */
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2014-04-16 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 19:00 Helge Deller [this message]
2014-04-17 9:33 ` [LTP] [PATCH] fix fanotify syscall check on compat kernel chrubis
[not found] ` <trinity-7fc052ce-4544-4fa4-afc0-9b68430ef693-1397729289569@3capp-gmx-bs62>
2014-04-17 10:16 ` chrubis
2014-04-17 13:27 ` chrubis
2014-04-17 15:00 ` chrubis
2014-04-17 16:57 ` chrubis
[not found] ` <5350E02B.7080104@gmx.de>
[not found] ` <20140418082553.GA3389@ls3530.fritz.box>
2014-04-22 11:57 ` chrubis
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=20140416190028.GA2093@ls3530.fritz.box \
--to=deller@gmx.de \
--cc=ltp-list@lists.sourceforge.net \
/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