linux-ext4 - [PATCH 0/11] quota: Stop setting IMMUTABLE and NOATIME flags directly

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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

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

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

Message-Id: <20170412072611.29017-1-jack@suse.cz>
Date:   Wed, 12 Apr 2017 09:26:00 +0200
From:   Jan Kara <jack@...e.cz>
To:     <linux-fsdevel@...r.kernel.org>
Cc:     <linux-ext4@...r.kernel.org>, <reiserfs-devel@...r.kernel.org>,
        jfs-discussion@...ts.sourceforge.net, Jan Kara <jack@...e.cz>
Subject: [PATCH 0/11] quota: Stop setting IMMUTABLE and NOATIME flags directly

Hello,

this series removes setting of IMMUTABLE and NOATIME flags from generic quota
code and moves it to filesystem's quota_on / quota_off handlers. Since this
was the only place where generic code was modifying inode flags that need to
be persistent on disk, we can remove functions syncing inode->i_flags to
on-disk flags after this. This was motivated by recent statx() work that
wants consistent view of inode flags without holding i_mutex.

Patches passed basic testing for ext2, ext4, reiserfs, compile-tested for jfs
only. Please review, patches are mostly trivial but I could have missed
something. If people are fine with the changes, I plan to merge them through
my tree.

								Honza