From: Cyril Hrubis <chrubis@suse.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Christian Brauner <brauner@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] LTP: syscalls: statx06.c:138: TFAIL: Modified time > after_time
Date: Wed, 24 May 2023 13:32:47 +0200 [thread overview]
Message-ID: <ZG3130X0GO9eNJfc@yuki> (raw)
In-Reply-To: <dca09245-5b59-438b-b7d6-c65db7a84a85@app.fastmail.com>
Hi!
> > [ 1192.088987] loop0: detected capacity change from 0 to 614400
> > tst_device.c:93: TINFO: Found free device 0 '/dev/loop0'
> > tst_test.c:1093: TINFO: Formatting /dev/loop0 with ext4 opts='-I 256'
> > extra opts=''
> > mke2fs 1.46.5 (30-Dec-2021)
> > [ 1192.337350] EXT4-fs (loop0): mounted filesystem
> > dfe9283c-5d2f-43f8-840e-a2bbbff5b202 r/w with ordered data mode. Quota
> > mode: none.
> > tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
> >
> > statx06.c:140: TPASS: Birth time Passed
> > statx06.c:138: TFAIL: Modified time > after_time
> > statx06.c:140: TPASS: Access time Passed
> > statx06.c:140: TPASS: Change time Passed
>
> I found a description in
>
> https://lwn.net/ml/linux-kernel/20230503142037.153531-1-jlayton@kernel.org/
>
> which indicates that this is expected. Added Jeff to Cc in case
> I'm misreading his explanation.
We even have in-flight patch from Jeff to fix the test with fine-grained
timestamps in LTP:
http://patchwork.ozlabs.org/project/ltp/patch/20230518113216.126233-1-jlayton@kernel.org/
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
LTP List <ltp@lists.linux.it>,
open list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, lkft-triage@lists.linaro.org,
Jeff Layton <jlayton@kernel.org>, Petr Vorel <pvorel@suse.cz>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: LTP: syscalls: statx06.c:138: TFAIL: Modified time > after_time
Date: Wed, 24 May 2023 13:32:47 +0200 [thread overview]
Message-ID: <ZG3130X0GO9eNJfc@yuki> (raw)
In-Reply-To: <dca09245-5b59-438b-b7d6-c65db7a84a85@app.fastmail.com>
Hi!
> > [ 1192.088987] loop0: detected capacity change from 0 to 614400
> > tst_device.c:93: TINFO: Found free device 0 '/dev/loop0'
> > tst_test.c:1093: TINFO: Formatting /dev/loop0 with ext4 opts='-I 256'
> > extra opts=''
> > mke2fs 1.46.5 (30-Dec-2021)
> > [ 1192.337350] EXT4-fs (loop0): mounted filesystem
> > dfe9283c-5d2f-43f8-840e-a2bbbff5b202 r/w with ordered data mode. Quota
> > mode: none.
> > tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
> >
> > statx06.c:140: TPASS: Birth time Passed
> > statx06.c:138: TFAIL: Modified time > after_time
> > statx06.c:140: TPASS: Access time Passed
> > statx06.c:140: TPASS: Change time Passed
>
> I found a description in
>
> https://lwn.net/ml/linux-kernel/20230503142037.153531-1-jlayton@kernel.org/
>
> which indicates that this is expected. Added Jeff to Cc in case
> I'm misreading his explanation.
We even have in-flight patch from Jeff to fix the test with fine-grained
timestamps in LTP:
http://patchwork.ozlabs.org/project/ltp/patch/20230518113216.126233-1-jlayton@kernel.org/
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2023-05-24 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 10:48 [LTP] LTP: syscalls: statx06.c:138: TFAIL: Modified time > after_time Naresh Kamboju
2023-05-24 10:48 ` Naresh Kamboju
2023-05-24 11:23 ` [LTP] " Dan Carpenter
2023-05-24 11:23 ` Dan Carpenter
2023-05-25 8:19 ` Joel Granados
2023-05-24 11:28 ` [LTP] " Arnd Bergmann
2023-05-24 11:28 ` Arnd Bergmann
2023-05-24 11:32 ` Cyril Hrubis [this message]
2023-05-24 11:32 ` 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=ZG3130X0GO9eNJfc@yuki \
--to=chrubis@suse.cz \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=viro@zeniv.linux.org.uk \
/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.