From: Paulo Alcantara <pc@manguebit.com>
To: "Dr. Bernd Feige" <bernd.feige@uniklinik-freiburg.de>,
"smfrench@gmail.com" <smfrench@gmail.com>,
"matoro_mailinglist_kernel@matoro.tk"
<matoro_mailinglist_kernel@matoro.tk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>,
"bagasdotme@gmail.com" <bagasdotme@gmail.com>,
"paul@darkrain42.org" <paul@darkrain42.org>,
"tom@talpey.com" <tom@talpey.com>,
"ronniesahlberg@gmail.com" <ronniesahlberg@gmail.com>,
"bharathsm@microsoft.com" <bharathsm@microsoft.com>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"brian.pardy@gmail.com" <brian.pardy@gmail.com>,
"nspmangalore@gmail.com" <nspmangalore@gmail.com>
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: Mon, 23 Oct 2023 11:07:01 -0300 [thread overview]
Message-ID: <b8e37bfc992532038f9d562f5596cbf3.pc@manguebit.com> (raw)
In-Reply-To: <779ef3ac542e7e39027dee19d669ad2f81b05bcc.camel@uniklinik-freiburg.de>
"Dr. Bernd Feige" <bernd.feige@uniklinik-freiburg.de> writes:
> I can confirm that the patches apply cleanly on 6.5.8 and help a lot
> with the issue here (vers=3.1.1, gentoo client, MS AD server with DFS).
Thanks for testing it.
Steve, I would suggest below commits for v6.5.y
238b351d0935 ("smb3: allow controlling length of time directory entries are cached with dir leases")
6a50d71d0fff ("smb3: allow controlling maximum number of cached directories")
2da338ff752a ("smb3: do not start laundromat thread when dir leases disabled")
e95f3f744650 ("smb: client: make laundromat a delayed worker")
81ba10959970 ("smb: client: prevent new fids from being removed by laundromat")
If OK, please ask stable team to pick those up.
next prev parent reply other threads:[~2023-10-23 14:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAO+kfxTwOvaxYV0ZRESxZB-4LHsF9b_VBjAKahhwUm5a1_c4ug@mail.gmail.com>
2023-09-06 1:01 ` Possible bug report: kernel 6.5.0/6.5.1 high load when CIFS share is mounted (cifsd-cfid-laundromat in"D" state) Bagas Sanjaya
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 [this message]
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=b8e37bfc992532038f9d562f5596cbf3.pc@manguebit.com \
--to=pc@manguebit.com \
--cc=bagasdotme@gmail.com \
--cc=bernd.feige@uniklinik-freiburg.de \
--cc=bharathsm@microsoft.com \
--cc=brian.pardy@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matoro_mailinglist_kernel@matoro.tk \
--cc=nspmangalore@gmail.com \
--cc=paul@darkrain42.org \
--cc=regressions@lists.linux.dev \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.com \
--cc=tom@talpey.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox