From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 217965] New: ext4(?) regression since 6.5.0 on sata hdd
Date: Mon, 02 Oct 2023 08:10:21 +0000 [thread overview]
Message-ID: <bug-217965-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217965
Bug ID: 217965
Summary: ext4(?) regression since 6.5.0 on sata hdd
Product: File System
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: iivanich@gmail.com
Regression: No
Since kernel 6.5.x and 6.6-rc* I'm getting weird kworker flush activity when
building openwrt from sources.
91 root 20 0 0 0 0 R 99,7 0,0 18:06.57
kworker/u16:4+flush-8:16
Openwrt sources resides on the sata hdd drive with ext4 fs,I'm using this setup
for a last 5 years, the problem is that since 6.5 kernels after the openwrt
kernel patch make
step(https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=scripts/patch-kernel.sh;h=c2b7e7204952f93946a6075d546cbeae32c2627f;hb=HEAD
which probably involves a lot of copy and write operations)
kworker/u16:4+flush-8:16 uses 100% of one core for a while(5-15 minutes) even
after I canceling openwrt build.
I tried to move this openwrt sources folder to an ssd drive where my system is
resides and run openwrt build from there and getting no issues with kworker
flush cpu usage. Also I have no such behavior with 6.4.x and older kernels so
it looks like regression to me, not sure if this is a fs, vfs or even block
subsystem issue.
This is how it looks in perf
Samples: 320K of event 'cycles:P', Event count (approx.): 363448649248
Children Self Command Shared Object
Symbol
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
ret_from_fork_asm
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
ret_from_fork
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
kthread
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
worker_thread
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
process_one_work
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
wb_workfn
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
wb_writeback
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
__writeback_inodes_wb
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
writeback_sb_inodes
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
__writeback_single_inode
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
do_writepages
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
ext4_writepages
+ 12,40% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
ext4_do_writepages
+ 12,39% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
ext4_map_blocks
+ 12,39% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
ext4_ext_map_blocks
+ 12,38% 0,00% kworker/u16:2+f [kernel.vmlinux] [k]
ext4_mb_new_blocks
+ 12,38% 0,93% kworker/u16:2+f [kernel.vmlinux] [k]
ext4_mb_regular_allocator
+ 9,42% 0,00% cc1 [unknown] [.]
0000000000000000
+ 5,42% 0,53% kworker/u16:2+f [kernel.vmlinux] [k]
ext4_mb_scan_aligned
+ 4,88% 0,69% kworker/u16:2+f [kernel.vmlinux] [k]
mb_find_extent
+ 3,99% 3,95% kworker/u16:2+f [kernel.vmlinux] [k]
mb_find_order_for_block
+ 3,51% 0,61% kworker/u16:2+f [kernel.vmlinux] [k]
ext4_mb_load_buddy_gfp
+ 2,95% 0,01% cc1 [kernel.vmlinux] [k]
asm_exc_page_fault
+ 2,67% 0,18% kworker/u16:2+f [kernel.vmlinux] [k]
pagecache_get_page
+ 2,41% 0,40% kworker/u16:2+f [kernel.vmlinux] [k]
__filemap_get_folio
+ 2,33% 2,10% cc1 cc1 [.]
cpp_get_token_1
+ 2,12% 0,05% cc1 [kernel.vmlinux] [k]
exc_page_fault
+ 2,07% 0,04% cc1 [kernel.vmlinux] [k]
do_user_addr_fault
+ 1,81% 0,52% kworker/u16:2+f [kernel.vmlinux] [k]
filemap_get_entry
1,80% 1,71% cc1 cc1 [.]
ht_lookup_with_hash
+ 1,77% 0,08% cc1 [kernel.vmlinux] [k]
handle_mm_fault
+ 1,65% 0,14% cc1 [kernel.vmlinux] [k]
__handle_mm_fault
1,60% 1,49% cc1 cc1 [.]
_cpp_lex_direct
+ 1,54% 0,73% kworker/u16:2+f [kernel.vmlinux] [k]
ext4_mb_good_group
+ 1,49% 1,46% cc1 cc1 [.]
ggc_internal_alloc
+ 1,28% 0,05% cc1 [kernel.vmlinux] [k]
do_anonymous_page
+ 1,28% 0,04% cc1 [kernel.vmlinux] [k]
entry_SYSCALL_64
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-10-02 8:10 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 8:10 bugzilla-daemon [this message]
2023-10-02 8:52 ` [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd 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
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.