linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd
Date: Wed, 27 Aug 2025 17:07:17 +0000	[thread overview]
Message-ID: <bug-217965-13602-vGzi4pJCMX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217965-13602@https.bugzilla.kernel.org/>

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

--- Comment #73 from Ojaswin Mujoo (ojaswin.mujoo@ibm.com) ---
Hi Mingyu,

Thanks for looking into this and sharing the reproducer. You are correct in the
analysis that we were getting stuck trying to check the same block group for
aligned blocks, due to the fact that the fragment lists always returned the
same group. 

However, about this:

> The author changed the fragment order RB tree into list for better
> performance.
> However, the function 'ext4_mb_find_good_group_avg_frag_lists' will always 
> returns the same group every time,

The change from rbtree to list was not done in the patchset you listed but
rather here:

https://lore.kernel.org/all/20220908092136.11770-5-jack@suse.cz/

which got merged in v6.0 kernel hence I think the behavior of fragment lists
returning the same block group was there even before my patchset (the one you
listed) However I remember people had mentioned that they started to see it
after v6.5. 

Its been sometime since I looked into this but I remember I had concluded that
since my patchset added new allocation criteria which made the allocator trim
the request to more aggressively look for BGs in the free fragment lists, we
just made this bug more easier to hit.

I tried the replicator however I was unable to get to the high CPU util, but
since you already have the setup, can you check if you are able to hit this
issue in v6.4 vs v6.5.

Thanks again,
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.

      parent reply	other threads:[~2025-08-27 17:07 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02  8:10 [Bug 217965] New: ext4(?) regression since 6.5.0 on sata hdd bugzilla-daemon
2023-10-02  8:52 ` [Bug 217965] " bugzilla-daemon
2023-10-02  8:56 ` bugzilla-daemon
2023-10-02  8:57 ` bugzilla-daemon
2023-10-02 15:22 ` bugzilla-daemon
2023-10-02 15:55 ` bugzilla-daemon
2023-10-03  6:50 ` bugzilla-daemon
2023-10-03  6:57 ` bugzilla-daemon
2023-10-03 11:04 ` bugzilla-daemon
2023-10-03 13:42 ` bugzilla-daemon
2023-10-03 14:23 ` bugzilla-daemon
2023-10-04 12:44 ` bugzilla-daemon
2023-10-04 17:23 ` bugzilla-daemon
2023-10-11  7:53 ` bugzilla-daemon
2023-10-11 16:07 ` bugzilla-daemon
2023-10-11 22:23 ` bugzilla-daemon
2023-10-17 10:45 ` bugzilla-daemon
2023-10-17 10:52 ` bugzilla-daemon
2023-10-20 10:24 ` bugzilla-daemon
2023-10-21 10:07 ` bugzilla-daemon
2023-11-13 22:46 ` bugzilla-daemon
2023-11-14  5:55 ` bugzilla-daemon
2023-11-14  6:47 ` bugzilla-daemon
2023-11-14  8:22 ` bugzilla-daemon
2023-11-14 10:29 ` bugzilla-daemon
2023-11-15  4:06 ` bugzilla-daemon
2023-11-15 17:27 ` bugzilla-daemon
2023-11-15 22:39 ` bugzilla-daemon
2023-11-16  3:15 ` bugzilla-daemon
2023-11-16  4:05 ` bugzilla-daemon
2023-11-16  4:31 ` bugzilla-daemon
2023-11-16  4:33 ` bugzilla-daemon
2023-11-16 19:33 ` bugzilla-daemon
2023-11-17  0:01 ` bugzilla-daemon
2023-11-17  0:44 ` bugzilla-daemon
2023-11-17  1:39 ` bugzilla-daemon
2023-11-17  1:40 ` bugzilla-daemon
2023-11-17 15:39 ` bugzilla-daemon
2023-11-17 23:52 ` bugzilla-daemon
2023-11-17 23:53 ` bugzilla-daemon
2023-11-17 23:57 ` bugzilla-daemon
2023-11-18 12:10 ` bugzilla-daemon
2023-11-18 13:17 ` bugzilla-daemon
2023-11-20  6:11 ` bugzilla-daemon
2023-11-20  8:48 ` bugzilla-daemon
2023-11-27 17:31 ` bugzilla-daemon
2023-12-03  7:33 ` bugzilla-daemon
2023-12-15 11:27 ` bugzilla-daemon
2023-12-23  0:56 ` bugzilla-daemon
2023-12-23  1:48 ` bugzilla-daemon
2023-12-23 12:46 ` bugzilla-daemon
2023-12-23 14:22 ` bugzilla-daemon
2023-12-23 15:47 ` bugzilla-daemon
2023-12-29 20:35 ` bugzilla-daemon
2023-12-29 20:51 ` bugzilla-daemon
2023-12-29 21:05 ` bugzilla-daemon
2023-12-29 22:11 ` bugzilla-daemon
2023-12-29 22:13 ` bugzilla-daemon
2023-12-29 23:07 ` bugzilla-daemon
2023-12-29 23:22 ` bugzilla-daemon
2024-01-02  4:44 ` bugzilla-daemon
2024-01-02  6:44 ` bugzilla-daemon
2024-01-04  5:38 ` bugzilla-daemon
2024-01-04 22:20 ` bugzilla-daemon
2024-01-06  2:11 ` bugzilla-daemon
2024-01-06  3:18 ` bugzilla-daemon
2024-01-07  2:56 ` bugzilla-daemon
2024-02-07 11:44 ` bugzilla-daemon
2024-03-12 20:27 ` bugzilla-daemon
2024-03-17 11:58 ` bugzilla-daemon
2024-03-18  4:45 ` bugzilla-daemon
2024-03-20  6:46 ` bugzilla-daemon
2024-03-23  8:53 ` bugzilla-daemon
2025-08-18 13:48 ` bugzilla-daemon
2025-08-27 17:07 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-217965-13602-vGzi4pJCMX@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).