From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Brian Pardy <brian.pardy@gmail.com>,
Linux CIFS <linux-cifs@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Steve French <sfrench@samba.org>
Subject: Re: Possible bug report: kernel 6.5.0/6.5.1 high load when CIFS share is mounted (cifsd-cfid-laundromat in"D" state)
Date: Wed, 6 Sep 2023 08:01:51 +0700 [thread overview]
Message-ID: <ZPfPfyIoVxw5L6El@debian.me> (raw)
In-Reply-To: <CAO+kfxTwOvaxYV0ZRESxZB-4LHsF9b_VBjAKahhwUm5a1_c4ug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]
On Tue, Sep 05, 2023 at 01:09:05PM -0400, Brian Pardy wrote:
> My apologies if I do not have the bug report protocol correct in posting here.
>
> 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.
>
> The client is running Gentoo Linux, the server is a Seagate Personal
> Cloud NAS running Samba 4.6.5. Mount options used are
> "noperm,guest,vers=3.02". The CPUs do not actually appear to be
> spinning, the reported load average appears incorrect as far as actual
> CPU use is concerned.
>
> I am happy to follow any instructions provided to gather more details
> if I can help to track this down. Nothing that appears relevant
> appears in syslog or dmesg output.
Thanks for the regression report. But if you want to get it fixed,
you have to do your part: perform bisection. See Documentation/admin-guide/bug-bisect.rst in the kernel sources for how to do that.
Anyway, I'm adding it to regzbot:
#regzbot ^introduced: v6.4..v6.5
#regzbot title: incorrect CPU utilization report (multiplied) when mounting CIFS
Bye!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-09-06 1:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 17:09 Possible bug report: kernel 6.5.0/6.5.1 high load when CIFS share is mounted (cifsd-cfid-laundromat in"D" state) Brian Pardy
2023-09-06 1:01 ` Bagas Sanjaya [this message]
2023-09-06 21:03 ` Brian Pardy
2023-09-07 3:40 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-09-18 22:55 ` Brian Pardy
2023-09-19 3:00 ` Steve French
2023-09-19 5:36 ` Steve French
2023-09-19 13:21 ` Brian Pardy
2023-09-19 16:38 ` Steve French
2023-09-19 17:42 ` Brian Pardy
2023-09-19 18:06 ` Tom Talpey
2023-09-19 18:23 ` Steve French
2023-09-27 0:54 ` Paul Aurich
2023-10-05 9:55 ` Dr. Bernd Feige
2023-10-05 9:59 ` Steve French
2023-10-13 23:19 ` matoro
2023-10-13 23:52 ` Paulo Alcantara
2023-10-14 0:01 ` Paulo Alcantara
[not found] ` <CAH2r5mse_2sfXF+tdTmie5LLtBuc+6DOumDH3rn=5V24yhrYVQ@mail.gmail.com>
2023-10-14 0:59 ` matoro
2023-10-16 18:41 ` Paulo Alcantara
2023-10-20 14:37 ` Dr. Bernd Feige
2023-10-23 14:07 ` Paulo Alcantara
2023-10-24 2:51 ` Steve French
2023-09-19 3:01 ` Steve French
2023-10-20 10:40 ` Linux regression tracking #update (Thorsten Leemhuis)
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=ZPfPfyIoVxw5L6El@debian.me \
--to=bagasdotme@gmail.com \
--cc=brian.pardy@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sfrench@samba.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.