linux-kernel - [PATCHES v2][CFT] rename deadlock fixes

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20231125201015.GA38156@ZenIV>
Date:   Sat, 25 Nov 2023 20:10:15 +0000
From:   Al Viro <viro@...iv.linux.org.uk>
To:     linux-fsdevel@...r.kernel.org
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Mo Zou <lostzoumo@...il.com>, Jan Kara <jack@...e.cz>,
        linux-kernel@...r.kernel.org
Subject: [PATCHES v2][CFT] rename deadlock fixes

Updated variant forced-pushed into #work.rename; changes since v1:
	* rebased on top of #merged-selinux, to avoid a bisection hazard;
selinuxfs used to abuse lock_rename() badly enough to trigger the checks
in the last commit.  Fixed in #merged-selinux (which consists of a commit
already in selinux git tree), and rebase on top of that does not require
any changes in the series.
	* (hopefully) fixed the markup in directory-locking.rst.  I would
really appreciate if somebody familiar with reST took a look at that.
	* fixed another part of directory-locking.rst, not touched in v1 -
the proof that operations will not introduce loops if none had been present
should've been updated when RENAME_EXCHANGE got introduced; it hadn't been.
Rewritten.

Same branch, same overall description, individual patches in followups.