Hi, this is your Linux kernel regression tracker speaking. CCing regression mailing list, which should be in the loop for all regressions, as explained here: https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html On 23.11.21 17:19, Alexey Avramov wrote: > I found stalls in near-OOM conditions with Linux 5.16. This is not the > hang-up that was reported by Artem S. Tashkinov in 2019 [1]. It's a *new* > regression. I will demonstrate this with one simple experiment, which I > will reproduce with different kernels or settings. > > With older versions of the kernel, running the `tail /dev/zero` command > usually quickly leads to OOM condition. > > I will run the command `for i in {1...3}; do tail /dev/zero; done` and log > PSI metrics (using psi2log script from nohang v0.2.0 [2]) and some values > from `/proc/meminfo` (using mem2log v0.1.0 [3]) while this command is > running. During the experiment a single tab browser will be kept opened in > which some video will be playing. > [...] TWIMC: To be sure this issue doesn't fall through the cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression tracking bot: #regzbot ^introduced v5.15..v5.16-rc1 #regzbot title mm: reclaim_throttle leads to stall in near-OOM conditions #regzbot ignore-activity Ciao, Thorsten, your Linux kernel regression tracker. P.S.: If you want to know more about regzbot, check out its web-interface, the getting start guide, and/or the references documentation: https://linux-regtracking.leemhuis.info/regzbot/ https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md The last two documents will explain how you can interact with regzbot yourself if your want to. Hint for the reporter: when reporting a regression it's in your interest to tell #regzbot about it in the report, as that will ensure the regression gets on the radar of regzbot and the regression tracker. That's in your interest, as they will make sure the report won't fall through the cracks unnoticed. Hint for developers: you normally don't need to care about regzbot, just fix the issue as you normally would. Just remember to include a 'Link:' tag to the report in the commit message, as explained in Documentation/process/submitting-patches.rst That aspect was recently was made more explicit in commit 1f57bd42b77c: https://git.kernel.org/linus/1f57bd42b77c P.P.S.: As a Linux kernel regression tracker I'm getting a lot of reports on my table. I can only look briefly into most of them. Unfortunately therefore I sometimes will get things wrong or miss something important. I hope that's not the case here; if you think it is, don't hesitate to tell me about it in a public reply. That's in everyone's interest, as what I wrote above might be misleading to everyone reading this; any suggestion I gave they thus might sent someone reading this down the wrong rabbit hole, which none of us wants. BTW, I have no personal interest in this issue, which is tracked using regzbot, my Linux kernel regression tracking bot (https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting this mail to get things rolling again and hence don't need to be CC on all further activities wrt to this regression.
