Linux filesystem development
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: bug-gnulib@gnu.org,  linux-kernel@vger.kernel.org,
	linux-btrfs@vger.kernel.org,  linux-fsdevel@vger.kernel.org,
	 Jan Kara <jack@suse.cz>,  Christian Brauner <brauner@kernel.org>
Subject: Re: test-fdutimensat failures after 7.0.6-200.fc44.x86_64 kernel update
Date: Sat, 23 May 2026 11:32:22 -0700	[thread overview]
Message-ID: <87ik8enfih.fsf@gmail.com> (raw)
In-Reply-To: <20260518055617.GB10368@lst.de>

Hi Christoph,

Christoph Hellwig <hch@lst.de> writes:

> On Fri, May 15, 2026 at 10:14:28PM -0700, Collin Funk wrote:
>> Adding some print statements in place of the comment:
>> 
>>         fprintf (stderr, "%jd\n", (intmax_t) st3.st_atime);
>>         fprintf (stderr, "%jd\n", (intmax_t) Y2K);
>>         fprintf (stderr, "----------------\n");
>
> Can you share a complete stand-alone C source file for this
> reproducer?

It would be quite difficult. The test uses a nap function that sleeps
until the system can notice a timestamp difference. It attempts to use
the smallest interval possible, which requires a bit of work [1].

Apologies for the late reply, I haven't been able to reproduce this
since my original report. I'll let you know if it occurs again and
hopefully I can create a simple reproducer.

Thanks,
Collin

[1] https://github.com/coreutils/gnulib/blob/5ab7a04761dac69403f677de4ee44c1940777b46/tests/nap.h

      reply	other threads:[~2026-05-23 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-16  5:14 test-fdutimensat failures after 7.0.6-200.fc44.x86_64 kernel update Collin Funk
2026-05-18  5:56 ` Christoph Hellwig
2026-05-23 18:32   ` Collin Funk [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=87ik8enfih.fsf@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=brauner@kernel.org \
    --cc=bug-gnulib@gnu.org \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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