[TLDR: This mail in primarily relevant for Linux kernel regression tracking. See link in footer if these mails annoy you.] On 06.09.23 23:03, Brian Pardy wrote: > Added committer Ronnie Sahlberg to CC. > > On Tue, Sep 5, 2023 at 9:01 PM Bagas Sanjaya <bagasdotme@xxxxxxxxx> wrote: >> On Tue, Sep 05, 2023 at 01:09:05PM -0400, Brian Pardy wrote: >>> I've noticed an issue with the CIFS client in kernel 6.5.0/6.5.1 that >>> does not exist in 6.4.12 or other previous kernels (I have not tested >>> 6.4.13). Almost immediately after mounting a CIFS share, the reported >>> load average on my system goes up by 2. At the time this occurs I see >>> two [cifsd-cfid-laundromat] kernel threads running the "D" state, >>> where they remain for the entire time the CIFS share is mounted. The >>> load will remain stable at 2 (otherwise idle) until the share is >>> unmounted, at which point the [cifsd-cfid-laundromat] threads >>> disappear and load drops back down to 0. This is easily reproducible >>> on my system, but I am not sure what to do to retrieve more useful >>> debugging information. If I mount two shares from this server, I get >>> four laundromat threads in "D" state and a sustained load average of >>> 4. > [...] > > Thank you for directing me to the bug-bisect documentation. Results below: > > # git bisect bad > d14de8067e3f9653cdef5a094176d00f3260ab20 is the first bad commit > #regzbot ^introduced: d14de8067e3f9653cdef5a094176d00f3260a #regzbot ignore-activity 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.
