linux-ext4 - [Bug 218626] fstest ext4/014 fails when using filesystem quotas

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]

Date: Tue, 26 Mar 2024 15:38:09 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 218626] fstest ext4/014 fails when using filesystem quotas

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

--- Comment #1 from Luis Henriques (luis.henriques@...ux.dev) ---
Created attachment 306044
  --> https://bugzilla.kernel.org/attachment.cgi?id=306044&action=edit
Fix lost+found directory

OK, I've a patch that seems to fix the issue.

When mke2fs creates the 'lost+found' directory, it ensures that there are a few
empty blocks in it.  However, this test (ext4/014) corrupts the filesystem and
this directory needs to be created again.

The e2fsck program, however, when recreating the lost+found directory, isn't
making sure that there are these empty blocks.  These extra blocks will be then
taken into account in the quota calculation, as they were in the initial
(non-corrupted) filesystem.  The patch I'm attaching basically copies the loop
that adds the blocks to the empty directory.  There are a few I haven't yet
understood -- for example, the '16*1024' magic number is still a mistery.

Any thoughts?

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

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