From: Stephen Smalley <sds@tycho.nsa.gov>
To: Jan Stancek <jstancek@redhat.com>
Cc: selinux@tycho.nsa.gov, serge@hallyn.com, jburke@redhat.com
Subject: Re: [selinux-testsuite][PATCH] use extfs ioctls only when running on ext[234]
Date: Wed, 23 Jan 2013 10:41:38 -0500 [thread overview]
Message-ID: <510004B2.5020703@tycho.nsa.gov> (raw)
In-Reply-To: <6012e6d654ddc5defd9e283745ff7d10a2fa20b5.1358947507.git.jstancek@redhat.com>
On 01/23/2013 08:27 AM, Jan Stancek wrote:
> EXT2_* ioctls are likely to fail on other filesystems,
> for example: xfs.
>
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
> ---
> tests/ioctl/Makefile | 6 ++++++
> tests/ioctl/test_ioctl.c | 2 ++
> tests/ioctl/test_noioctl.c | 2 ++
> 3 files changed, 10 insertions(+), 0 deletions(-)
Shouldn't really be a compile-time flag but rather a runtime test of the
filesystem type, right? Otherwise it presumes you built it on the same
system and in the same filesystem where you will run it.
I thought however that your earlier patch to switch it to using FS_IOC_
command values would have
addressed the issue of other filesystem types already? What error are
you getting from xfs? The code already checks for one errno value to
distinguish the not-supported case.
> diff --git a/tests/ioctl/Makefile b/tests/ioctl/Makefile
> index 8dce555..def5267 100644
> --- a/tests/ioctl/Makefile
> +++ b/tests/ioctl/Makefile
> @@ -1,4 +1,10 @@
> TARGETS=$(patsubst %.c,%,$(wildcard *.c))
> +
> +DIR_FS=$(shell df -TP . | awk '{print $2}' | grep 'ext[234]')
> +ifneq (x$(DIR_FS),x)
> + CFLAGS += -DUSE_EXTFS_IOCTLS
> +endif
> +
> all: $(TARGETS)
> clean:
> rm -f $(TARGETS)
> diff --git a/tests/ioctl/test_ioctl.c b/tests/ioctl/test_ioctl.c
> index 0852f41..fa5d021 100644
> --- a/tests/ioctl/test_ioctl.c
> +++ b/tests/ioctl/test_ioctl.c
> @@ -49,6 +49,7 @@ int main(int argc, char **argv) {
> exit(1);
> }
>
> +#ifdef USE_EXTFS_IOCTLS
> /* This one should hit the FILE__GETATTR or FILE__READ test */
> rc = ioctl(fd, EXT2_IOC_GETVERSION, &val);
> if( rc != 0 ) {
> @@ -63,6 +64,7 @@ int main(int argc, char **argv) {
> perror("test_ioctl:EXT2_IOC_SETVERSION");
> exit(1);
> }
> +#endif
>
> close(fd);
> exit(0);
> diff --git a/tests/ioctl/test_noioctl.c b/tests/ioctl/test_noioctl.c
> index ef3fac5..b0ca660 100644
> --- a/tests/ioctl/test_noioctl.c
> +++ b/tests/ioctl/test_noioctl.c
> @@ -68,6 +68,7 @@ int main(int argc, char **argv) {
> exit(1);
> }
>
> +#ifdef USE_EXTFS_IOCTLS
> /*
> * This one depends on kernel version:
> * New: Should hit the FILE__READ test and succeed.
> @@ -86,6 +87,7 @@ int main(int argc, char **argv) {
> perror("test_noioctl:EXT2_IOC_SETVERSION");
> exit(1);
> }
> +#endif
>
> close(fd);
> exit(0);
>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2013-01-23 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 13:27 [selinux-testsuite][PATCH] use extfs ioctls only when running on ext[234] Jan Stancek
2013-01-23 15:41 ` Stephen Smalley [this message]
2013-01-23 16:50 ` Jan Stancek
2013-01-23 17:51 ` Stephen Smalley
2013-01-23 18:15 ` Jan Stancek
2013-01-23 18:31 ` Stephen Smalley
2013-01-24 4:36 ` Serge E. Hallyn
2013-01-24 15:54 ` Stephen Smalley
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=510004B2.5020703@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=jburke@redhat.com \
--cc=jstancek@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=serge@hallyn.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.