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]

Date: Fri, 29 Dec 2023 20:35:19 +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

Matthew Stapleton (matthew4196@...il.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matthew4196@...il.com

--- Comment #52 from Matthew Stapleton (matthew4196@...il.com) ---
I'm a bit late to reporting this, but it might be related to this bug report.

Since noticing this 100% cpu flush problem on my computer with a non-raid
Samsung SSD 990 PRO NMVe and kernel 6.6.3 (and now 6.6.8) I decided to do a git
bisect and seemed to track down the problem to commit:
7e170922f06bf46effa7c57f6035fc463d6edc7e if that helps, although I haven't
tested if disabling CR1_5 also resolves the problem.  Running "tar xf
linux-6.6.8.tar.xz" is enough to trigger 100% cpu for a few seconds after tar
is finished on my system, although it doesn't noticeably trigger the problem on
my server with raid 6 and hard drives.  It also looks like my ext4 filesystem
is mounting with stripe=32733 according to /proc/mounts, although dumpe2fs -h
doesn't show any stripe settings on the filesystem.

I'll try the patch and see if it fixes the problem.

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

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