[TLDR: I'm adding this report to the list of tracked Linux kernel regressions; the text you find below is based on a few templates paragraphs you might have encountered already in similar form. See link in footer if these mails annoy you.] On 17.10.23 05:37, Andres Freund wrote: > > As previously reported in https://lore.kernel.org/all/20231004004247.zkswbseowwwc6vvk@xxxxxxxxxxxxxxxxx/ > I found some hangs below ext4_fallocate(), in 6.6-rc*. As it looks like my > issue was unrelated to the thread I had responded to, I was asked to start > this new thread. > > I just was able to reproduce the issue, after upgrading to 6.6-rc6 - this time > it took ~55min of high load (io_uring using branch of postgres, running a > write heavy transactional workload concurrently with concurrent bulk data > load) to trigger the issue. > > For now I have left the system running, in case there's something you would > like me to check while the system is hung. > [...] Thanks for the report. To be sure the issue doesn't fall through the cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression tracking bot: #regzbot ^introduced v6.5..v6.6-rc6 #regzbot title ext4: task hung in ext4_fallocate #regzbot ignore-activity This isn't a regression? This issue or a fix for it are already discussed somewhere else? It was fixed already? You want to clarify when the regression started to happen? Or point out I got the title or something else totally wrong? Then just reply and tell me -- ideally while also telling regzbot about it, as explained by the page listed in the footer of this mail. Developers: When fixing the issue, remember to add 'Link:' tags pointing to the report (the parent of this mail). See page linked in footer for details. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
