linux-ext4 - [Bug 216317] "ext4: lblock 0 mapped to illegal pblock" after upgrading to 5.19.0

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: <bug-216317-13602-7HItArPNRt@https.bugzilla.kernel.org/>
Date:   Tue, 02 Aug 2022 06:14:12 +0000
From:   bugzilla-daemon@...nel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 216317] "ext4: lblock 0 mapped to illegal pblock" after
 upgrading to 5.19.0

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

--- Comment #3 from David Korth (gerbilsoft@...bilsoft.com) ---
Reading the various commits, it seems that ext4's inline_data option previously
supported inlining symlinks, but as of v5.19.0, that's no longer supported. The
patch restores read-only compatibility, but new symlinks will not be inlined.
Is there any particular reason why symlink inlining was removed, and/or does
the new method work better than inlining?

-- 
You may reply to this email to add a comment.

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