From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
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 [thread overview]
Message-ID: <bug-202889-202145-guk7nSNSwJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202889-202145@https.bugzilla.kernel.org/>
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.
next prev parent reply other threads:[~2019-03-13 2:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 20:58 [Bug 202889] New: fsync on file fails to persist its size, which is changed by pwrite bugzilla-daemon
2019-03-12 20:59 ` [Bug 202889] fsync on inode " bugzilla-daemon
2019-03-13 2:24 ` bugzilla-daemon
2019-03-13 2:40 ` bugzilla-daemon
2019-03-13 2:54 ` bugzilla-daemon [this message]
2019-03-13 3:09 ` bugzilla-daemon
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=bug-202889-202145-guk7nSNSwJ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).