linux-ext4 - [Bug 205957] Ext4 64 bit hash breaks 32 bit glibc 2.28+

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

Message-ID: <bug-205957-13602-ce7D5uRyXO@https.bugzilla.kernel.org/>
Date:   Sat, 28 Dec 2019 07:50:36 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 205957] Ext4 64 bit hash breaks 32 bit glibc 2.28+

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

--- Comment #10 from Andreas Dilger (adilger.kernelbugzilla@...ger.ca) ---
IMHO, adding a new syscall for this is a lot of complexity that could be
avoided.  Using an ioctl() or fadvise() to set the "32-bitness" of the file
descriptor would seem like a simpler implementation that could be handled
directly by an ext4 patch rather than having to change every architecture just
to pass this flag.

Then, in the cases that QEMU is running in the confusing "I want 32-bit values
returned from a 64-bit system call" mode, it would call the ioctl(fd,
FS_IOC_32BITHASH) once before calling getdents64(fd, ...).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.