linux-ext4 - Re: [PATCH] fuse2fs: explicitly set _FILE_OFFSET

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

Message-ID: <172982841321.4001088.9223384705402700203.b4-ty@mit.edu>
Date: Thu, 24 Oct 2024 23:53:46 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: linux-ext4 <linux-ext4@...r.kernel.org>,
        "Darrick J. Wong" <djwong@...nel.org>
Cc: "Theodore Ts'o" <tytso@....edu>
Subject: Re: [PATCH] fuse2fs: explicitly set _FILE_OFFSET_BITS again


On Wed, 29 May 2024 11:12:14 -0700, Darrick J. Wong wrote:
> In commit 3ab99d9b602, the build system was changed not to set
> _FILE_OFFSET_BITS explicitly due to some weird error on mips64el.
> Unfortunately, this breaks the aarch64 Debian build because libfuse
> 2.9.9 requires this value to be set explicitly.  Restore this dumb
> preprocessor symbol dependency with even more hackery as documented in
> the commit.
> 
> [...]

Applied, thanks!

[1/1] fuse2fs: explicitly set _FILE_OFFSET_BITS again
      commit: fb702218ab47b045cbbaf3268984fbdc5f75632e

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