linux-ext4 - Re: [PATCH] fuse2fs: clean up the lockfile handling

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 for Android: free password hash cracker in your pocket

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

Message-ID: <175090890592.198062.9803658186310097955.b4-ty@mit.edu>
Date: Wed, 25 Jun 2025 23:35:10 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: "Theodore Ts'o" <tytso@....edu>, Tim Woodall <debianbugs@...dall.me.uk>,
        linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] fuse2fs: clean up the lockfile handling


On Mon, 16 Jun 2025 08:06:14 -0700, Darrick J. Wong wrote:
> Fix various problems with the new lockfile code in fuse2fs: the printfs
> should use the actual logging function err_printf, the messages should
> be looked up in gettext, we should actually exit main properly on
> error instead of calling exit(), and the error message printing for the
> final lockfile unlink is broken.
> 
> 
> [...]

Applied, thanks!

[1/1] fuse2fs: clean up the lockfile handling
      commit: e50fbaa4d156a6ff62dc85c4737fa97c4cb858aa

Best regards,
-- 
Theodore Ts'o <tytso@....edu>