public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] statx04.c:53: FAIL: STATX_ATTR_COMPRESSED flag is not set - Testing on ext2
Date: Mon, 17 Sep 2018 10:27:52 +0200	[thread overview]
Message-ID: <20180917082752.GA7857@rei> (raw)
In-Reply-To: <CA+G9fYsr=iYgaaepEnJOOu_-bR0p=3gCxAhcw6adQWPUnPfiYA@mail.gmail.com>

Hi!
> statx04 test failed on Hikey (arm64) while testing for ext2 which is
> running 4.18 stable kernel and LTP master branch. Same test case got
> PASS for ext3 and ext4.
> 
> Is this test case need any special prerequirements ?

That is a confirmed kernel bug that I've been told by kernel dev will be fixed,
it's written in the test commit message as well:

commit 5ffb23e2c051c718814515527275e92a8d3155e0
Author: vaishnavid <vaishnavi.d@zilogic.com>
Date:   Mon Sep 3 12:18:28 2018 +0000

    syscalls/statx04: Add new test.

    This test will check if statx() reports attribute flags by adding
    FS_COMPR_FL, FS_APPEND_FL, FS_IMMUTABLE_FL and FS_NODUMP_FL to a
    direcotry and checks that the flags are reported correctly and also
    tests a directory with no flags.

    The test is executed against all filesystems, since most of the kernel
    code that implements this functionality is filesystem specific.

    * The ntfs3g fuse driver reports wrong errno for unimplemented ioctls()
      EINVAL while every other filesystem reports ENOTTY correctly

    * The test fails for ext2 filesystem mounted by kernel ext2 driver,
      which is confirmed to be kernel bug that will be fixed later on
      ^
      |
     See this part


-- 
Cyril Hrubis
chrubis@suse.cz

      parent reply	other threads:[~2018-09-17  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-15  9:53 [LTP] statx04.c:53: FAIL: STATX_ATTR_COMPRESSED flag is not set - Testing on ext2 Naresh Kamboju
2018-09-16 16:26 ` Rafael David Tinoco
2018-09-17  8:36   ` Cyril Hrubis
2018-09-17  8:27 ` Cyril Hrubis [this message]

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=20180917082752.GA7857@rei \
    --to=chrubis@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