From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 202485] chmod'ed permission not persisted upon fsync
Date: Sat, 02 Feb 2019 04:01:14 +0000 [thread overview]
Message-ID: <bug-202485-13602-1zdUGW8bIY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202485-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202485
Vijay Chidambaram (vijayc@utexas.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vijayc@utexas.edu
--- Comment #2 from Vijay Chidambaram (vijayc@utexas.edu) ---
Hi Seulbae,
Adding on to what Ted said, the POSIX standards are not very specific about
crash-consistency guarantees. I'd recommend you go through the ext4/btrfs/xfs
mailing lists searching for "Vijay Chidambaram", Jayashree Mohan", or "Ashlie
Martinez" to find prior discussions and other potential dead-ends. The previous
discussions also document the guarantees provided by the widely-used Linux file
systems, so that you know what is a bug and what is not.
For example, a symlink also does not have crash-consistency guarantees:
https://www.spinics.net/lists/linux-btrfs/msg76816.html
Our OSDI paper has more details:
http://www.cs.utexas.edu/~vijay/papers/osdi18-crashmonkey.pdf
Thanks,
Vijay Chidambaram, UT Austin
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-02-02 4:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 20:10 [Bug 202485] New: chmod'ed permission not persisted upon fsync bugzilla-daemon
2019-02-02 3:38 ` [Bug 202485] " bugzilla-daemon
2019-02-02 4:01 ` bugzilla-daemon [this message]
2019-02-02 14:29 ` 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-202485-13602-1zdUGW8bIY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.