From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] tst_device: use raw syscall in the tst_device.h
Date: Thu, 9 Jan 2020 10:59:40 +0100 [thread overview]
Message-ID: <20200109095940.GA23230@dell5510> (raw)
In-Reply-To: <20200109095239.GB31981@rei.lan>
Hi Cyril, Li,
> Hi!
> > +#define _GNU_SOURCE
> > #include <unistd.h>
> > +#include <sys/syscall.h>
> Defining _GNU_SOURCE anywhere but at the top of the test source is
> meaningless. It has to be defined before we include any libc headers
> otherwise it's ignored.
> > struct tst_device {
> > const char *dev;
> > @@ -75,9 +77,9 @@ int tst_detach_device(const char *dev_path);
> > * simply before the tst_dev_bytes_written invocation. For easy to use,
> > * we create this inline function tst_dev_sync.
> > */
> > -static inline void tst_dev_sync(int fd)
> > +static inline int tst_dev_sync(int fd)
> > {
> > - syncfs(fd);
> > + return syscall(__NR_syncfs, fd);
> > }
> > diff --git a/testcases/kernel/syscalls/fadvise/posix_fadvise01.c b/testcases/kernel/syscalls/fadvise/posix_fadvise01.c
> > +#define _GNU_SOURCE
> > #define _XOPEN_SOURCE 600
> > #include <fcntl.h>
> Why do we need the _GNU_SOURCE here? We switched to a syscall() in the
> header, hence we do not need the syncfs() prototype anymore.
Correct, both. Sorry for a complete wrong review.
Kind regards,
Petr
next prev parent reply other threads:[~2020-01-09 9:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 7:15 [LTP] [PATCH] tst_device: use raw syscall in the tst_device.h Li Wang
2020-01-09 7:45 ` Petr Vorel
2020-01-09 8:02 ` Li Wang
2020-01-09 8:21 ` Petr Vorel
2020-01-09 9:52 ` Cyril Hrubis
2020-01-09 9:59 ` Petr Vorel [this message]
2020-01-09 12:41 ` Li Wang
2020-01-09 12:49 ` Cyril Hrubis
2020-01-09 12:56 ` Li Wang
2020-01-09 12:56 ` Petr Vorel
2020-01-09 13:10 ` Cyril Hrubis
2020-01-09 14:28 ` Petr Vorel
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=20200109095940.GA23230@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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