From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] open14 and openat03 failed on arm64
Date: Fri, 27 Jan 2017 08:21:05 -0500 (EST) [thread overview]
Message-ID: <746496870.1567645.1485523265470.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CA+G9fYsrnhpUMa3VZ-q7qw8XHFycOuH6hUigZXAhjCcoaiNQHQ@mail.gmail.com>
----- Original Message -----
> From: "Naresh Kamboju" <naresh.kamboju@linaro.org>
> To: ltp@lists.linux.it
> Cc: "Milosz Wasilewski" <milosz.wasilewski@linaro.org>
> Sent: Friday, 27 January, 2017 2:03:27 PM
> Subject: [LTP] open14 and openat03 failed on arm64
>
> Hi LTP Team,
>
> Test cases open14.c and openat03.c failed on arm64 on latest Linux kernel
> 4.9.x.
There was a known glibc bug associated with these 2 tests, and also possible
issue with tmpfs, see this for details:
https://github.com/linux-test-project/ltp/issues/118
>
> Have you noticed these failures on x86_64 and other architectures and
> which kernel version ?
>
> Test output:
> -----------------
> create multiple directories, link files into them
> and check file permissions
> file mode read 0, but expected
> file mode read 0, but expected 7755
> file mode read 0, but expected 1
> file mode read 0, but expected 755
> file mode read 0, but expected 644
> file mode read 0, but expected 440
>
> Linux version 4.9.0-rc6-00086-g3b404a5 (broonie@optimist) (gcc version
> 5.1.1 20150608 (Linaro GCC 5.1-2015.08) ) #1 SMP PREEMPT Tue Nov 22
> 04:14:54 GMT 2016
>
> Test case is trimmed version of LTP,
> you can find test case here in this link
> [1] http://people.linaro.org/~naresh.kamboju/open14-arm64-test.c
> [2] http://people.linaro.org/~naresh.kamboju/open14-x86-test.c
>
> Best regards
> Naresh Kamboju
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
>
next prev parent reply other threads:[~2017-01-27 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 13:03 [LTP] open14 and openat03 failed on arm64 Naresh Kamboju
2017-01-27 13:21 ` Jan Stancek [this message]
2017-01-27 13:28 ` Naresh Kamboju
2017-01-27 13:40 ` Milosz Wasilewski
2017-01-27 13:45 ` Jan Stancek
2017-01-27 16:32 ` Jan Stancek
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=746496870.1567645.1485523265470.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--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