[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZG3130X0GO9eNJfc@yuki>
Date: Wed, 24 May 2023 13:32:47 +0200
From: Cyril Hrubis <chrubis@...e.cz>
To: Arnd Bergmann <arnd@...db.de>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
LTP List <ltp@...ts.linux.it>,
open list <linux-kernel@...r.kernel.org>,
linux-fsdevel@...r.kernel.org, lkft-triage@...ts.linaro.org,
Jeff Layton <jlayton@...nel.org>, Petr Vorel <pvorel@...e.cz>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
Dan Carpenter <dan.carpenter@...aro.org>,
Anders Roxell <anders.roxell@...aro.org>
Subject: Re: LTP: syscalls: statx06.c:138: TFAIL: Modified time > after_time
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@...e.cz
Powered by blists - more mailing lists