Received-SPF: softfail (google.com: domain of transitioning linux-ext4-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Date:   Thu, 12 May 2022 17:22:02 +0200
From:   Vincent Lefevre <vincent@vinc17.net>
To:     linux-ext4@vger.kernel.org
Subject: Re: ext4: unexpected delayed file creation with a 5.17 kernel
Message-ID: <20220512152202.GE3360150@zira.vinc17.org>
Mail-Followup-To: Vincent Lefevre <vincent@vinc17.net>,
        linux-ext4@vger.kernel.org
References: <20220511135917.GA3381602@zira.vinc17.org>
 <Yn0fMj0jXPrMIZd9@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <Yn0fMj0jXPrMIZd9@mit.edu>
User-Agent: Mutt/2.2.4+14 (d448c911) vl-138565 (2022-05-08)
Precedence: bulk

On 2022-05-12 10:52:34 -0400, Theodore Ts'o wrote:
> 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*?

Completely unreproducible. This was the only time I noticed such an
issue with ext4.

-- 
Vincent Lef?vre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)