From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 202889] fsync on inode fails to persist its size,
which is changed by pwrite
Date: Wed, 13 Mar 2019 02:54:48 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from [172.30.20.202] (helo=mx.sourceforge.net)
by sfs-ml-4.v29.lw.sourceforge.com with esmtps
(TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1)
(envelope-from )
id 1h3u2j-0002q7-Ta
for linux-f2fs-devel@lists.sourceforge.net; Wed, 13 Mar 2019 02:54:57 +0000
Received: from mail.wl.linuxfoundation.org ([198.145.29.98])
by sfi-mx-3.v28.lw.sourceforge.com with esmtps
(TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1)
id 1h3u2i-00EVoH-C7
for linux-f2fs-devel@lists.sourceforge.net; Wed, 13 Mar 2019 02:54:57 +0000
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
by mail.wl.linuxfoundation.org (Postfix) with ESMTP id A3349284F5
for ;
Wed, 13 Mar 2019 02:54:50 +0000 (UTC)
In-Reply-To:
List-Id:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net
To: linux-f2fs-devel@lists.sourceforge.net
https://bugzilla.kernel.org/show_bug.cgi?id=202889
--- Comment #3 from Seulbae Kim (seulbae@gatech.edu) ---
Hi Chao, Thank you for the quick response again!
And sorry, I missed a line in the PoC.. :(
This bug actually is a little bit tricky, because it's not ALWAYS being
reproduced..
Running the PoC repeatedly on a fresh VM instance, I get the wrong file size at
about 50% chance. However, when I run the same test case on a binary, which
utilizes the Linux Kernel Library for mounting, running PoC, remounting, and
retrieving the stat info from the files, I always get the wrong size for this
file, "foo/bar/xattr".
I've just re-tested the PoC on a new VM with kernel v5.0, and again, this bug
is reproduced 4 times out of 10 trials.
Do you have any idea about what is the cause of this nondeterministic behavior?
(In reply to Chao Yu from comment #1)
> Hi Seulbae,
>
> Thanks for the report. :)
>
> Your test program didn't handle any error paths, it should be fixed.
>
> I try to reproduce this bug, but it looks there is no problem in my
> environment.
>
> Could you add error handling and try again?
--
You are receiving this mail because:
You are watching the assignee of the bug.