linux-ext4 - [Bug 202485] chmod'ed permission not persisted upon fsync

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 02 Feb 2019 04:01:14 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 202485] chmod'ed permission not persisted upon fsync

https://bugzilla.kernel.org/show_bug.cgi?id=202485

Vijay Chidambaram (vijayc@...xas.edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vijayc@...xas.edu

--- Comment #2 from Vijay Chidambaram (vijayc@...xas.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.