linux-ext4 - [Bug 107301] system hang during ext4 xattr operation

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]

Date:	Wed, 11 Nov 2015 14:53:10 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 107301] system hang during ext4 xattr operation

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

--- Comment #17 from Jan Kara <jack@...e.cz> ---
Ultimately it is Ted's call but your argument is like (randomly taken out of
top of my head): "Proper locking to protect from hole punching costs us some
performance and our workload doesn't use hole punching so let's create mount
option to disable the locking". Sure it can be done and it will benefit your
workload but how much you gain? And how many users need this? This has to be
weighted against the cost of the new mount option in terms of testing and
usability (and code complexity but that is fairly small in this case so I'm not
that concerned).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html