ltp.lists.linux.it archive mirror
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] statx04: mask STATX_ATTR_COMPRESSED on tmpfs
Date: Thu, 18 Aug 2022 17:59:03 +0800	[thread overview]
Message-ID: <CAEemH2cipQ-k1J7WEoNecqGJvDfXD2iz7zZOX+B9rv6oMkU5JQ@mail.gmail.com> (raw)
In-Reply-To: <da253a0e-d082-9329-3392-aacee81e6c8d@fujitsu.com>


[-- Attachment #1.1: Type: text/plain, Size: 803 bytes --]

On Thu, Aug 18, 2022 at 5:55 PM xuyang2018.jy@fujitsu.com <
xuyang2018.jy@fujitsu.com> wrote:

> Hi Li
>
> > Recently a new kernel commit (e408e695f) introduces the inode attributes
> > being supported in tmpfs, which is like other Linux file systems. But
> that
> > caused statx04 to throw an unsupported error in STATX_ATTR_COMPRESSED.
> >
> > This patch help masks it just like what we did for XFS.
>
> Looks good to me,
>

Thanks, I suddenly realized that we need to add the commit info into .tag
as well.

@@ -132,6 +139,7 @@ static struct tst_test test = {
                {"linux-git", "99652ea56a41"},
                {"linux-git", "04a87e347282"},
                {"linux-git", "5f955f26f3d4"},
+               {"linux-git", "e408e695f5f1"},
                {}
        },

-- 
Regards,
Li Wang

[-- Attachment #1.2: Type: text/html, Size: 1699 bytes --]

[-- Attachment #2: Type: text/plain, Size: 60 bytes --]


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-08-18  9:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  9:50 [LTP] [PATCH] statx04: mask STATX_ATTR_COMPRESSED on tmpfs Li Wang
2022-08-18  9:55 ` xuyang2018.jy
2022-08-18  9:59   ` Li Wang [this message]
2022-08-19  6:21     ` Li Wang

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=CAEemH2cipQ-k1J7WEoNecqGJvDfXD2iz7zZOX+B9rv6oMkU5JQ@mail.gmail.com \
    --to=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=xuyang2018.jy@fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).