linux-ext4 - [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd

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-217965-13602-ojYEQ4z9yT@https.bugzilla.kernel.org/>
Date:   Tue, 03 Oct 2023 13:42:04 +0000
From:   bugzilla-daemon@...nel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd

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

--- Comment #8 from Ojaswin Mujoo (ojaswin.mujoo@....com) ---
Hey Ivan, thanks! 

Seems like stripe mount option is automatically added if the filesystem is made
using stride or stripe-width options during mkfs time. 

Can you kindly perform the below steps as well to further help narrow this
issue down:

1. Mount FS with the usual options (including using stripe=32752). 
2. Once mounted, run:

$ echo "0" > /sys/fs/ext4/sdb2/mb_best_avail_max_trim_order

This might need sudo. Basically this disables one of the allocator feature that
was added in 6.5.

3. Run the workload again and see if the issue is still visible.

Regards,
ojaswin

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

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