From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] NS_* ioctl commands fail in 32bit compat mode (-m32)
Date: Mon, 06 May 2019 12:39:09 +0200 [thread overview]
Message-ID: <8736lrx3xu.fsf@rpws.prws.suse.cz> (raw)
In-Reply-To: <874l67x53e.fsf@rpws.prws.suse.cz>
Richard Palethorpe <rpalethorpe@suse.de> writes:
> Hello Federico,
>
> All the tests fail with something similar to:
> ioctl_ns01.c:45: FAIL: unexpected ioctl error: ENOTTY
>
> when compiled with the -m32 flag on at least SUSE kernel 4.20 and
> 4.12.
>
> Do you know if this feature is expected to work in 32bit compat mode?
> Maybe the size of the arguments should be different when using 32bit mode?
FYI, it seems the size of the argument and value are the same on both 32bit
and 64bit mode in user space.
--
Thank you,
Richard.
next prev parent reply other threads:[~2019-05-06 10:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 20:29 [LTP] [PATCH v1] Test ioctl syscall for NS_GET_* requests YourName
2019-03-04 16:16 ` Cyril Hrubis
2019-03-11 7:25 ` [LTP] [PATCH v2] " Federico Bonfiglio
2019-03-18 14:22 ` Cyril Hrubis
2019-03-18 15:30 ` Cyril Hrubis
2019-03-19 18:09 ` [LTP] [PATCH v3] " Federico Bonfiglio
2019-03-26 19:20 ` Cyril Hrubis
2019-03-28 20:22 ` [LTP] [PATCH v4 1/2] include/SAFE_UNSHARE() macro added Federico Bonfiglio
2019-04-03 15:19 ` Cyril Hrubis
2019-03-28 20:22 ` [LTP] [PATCH v4 2/2] Test ioctl syscall for NS_GET_* requests Federico Bonfiglio
2019-04-03 15:22 ` Cyril Hrubis
2019-04-11 19:25 ` [LTP] [PATCH v5] " Federico Bonfiglio
2019-04-12 14:33 ` Cyril Hrubis
2019-05-06 10:14 ` [LTP] NS_* ioctl commands fail in 32bit compat mode (-m32) Richard Palethorpe
2019-05-06 10:39 ` Richard Palethorpe [this message]
2019-05-13 9:00 ` Cyril Hrubis
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=8736lrx3xu.fsf@rpws.prws.suse.cz \
--to=rpalethorpe@suse.de \
--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 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.