public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Vincent Lefevre <vincent@vinc17.net>, linux-ext4@vger.kernel.org
Subject: Re: ext4: unexpected delayed file creation with a 5.17 kernel
Date: Thu, 12 May 2022 10:52:34 -0400	[thread overview]
Message-ID: <Yn0fMj0jXPrMIZd9@mit.edu> (raw)
In-Reply-To: <20220511135917.GA3381602@zira.vinc17.org>

On Wed, May 11, 2022 at 03:59:17PM +0200, Vincent Lefevre wrote:
> Hi,
> 
> On a Linux machine (12-core x86_64 Debian/unstable, 5.17 kernel)
> with an ext4 filesystem, I got a file born 30 seconds after its
> actual creation by a script. This is completely unreproducible.

completely *reproducible* or *unreproducible*?

If it is completely reproducible, can you try to reduce your shell
script to a minimal reproducer?

					- Ted

  reply	other threads:[~2022-05-12 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 13:59 ext4: unexpected delayed file creation with a 5.17 kernel Vincent Lefevre
2022-05-12 14:52 ` Theodore Ts'o [this message]
2022-05-12 15:22   ` Vincent Lefevre

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=Yn0fMj0jXPrMIZd9@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=vincent@vinc17.net \
    /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