From: Sasha Levin <sashal@kernel.org>
To: Steve French <smfrench@gmail.com>
Cc: Stable <stable@vger.kernel.org>,
Paulo Alcantara <pc@manguebit.com>,
ronnie sahlberg <ronniesahlberg@gmail.com>,
Linux Regressions <regressions@lists.linux.dev>,
"Dr. Bernd Feige" <bernd.feige@uniklinik-freiburg.de>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: Some additional cifs patches for 6.5 stable to address issue brought up by kernel regression tracker
Date: Thu, 26 Oct 2023 09:09:31 -0400 [thread overview]
Message-ID: <ZTplC1_qJYL1wR2G@sashalap> (raw)
In-Reply-To: <CAH2r5mvHUnxfOU1URs2s6O3As8WLyMEkK+KNdUy6Ct9u+=d5YA@mail.gmail.com>
On Mon, Oct 23, 2023 at 11:32:21PM -0500, Steve French wrote:
>There were a set of issues brought up in 6.5 by the introduction of
>the "laundromat" (which cleans up directory leases). After discussion
>and testing with Paulo, Bernd Feige and others, we request that the
>following set also be included to address these problems. They are
>all in mainline (added in 6.6) and the patches (from mainline since
>they apply cleanly) are also attached.
>
> 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")
> 3b8bb3171571 ("smb: client: do not start laundromat thread on
>nohandlecache")
> e95f3f744650 ("smb: client: make laundromat a delayed worker")
> 81ba10959970 ("smb: client: prevent new fids from being
>removed by laundromat")
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2023-10-26 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 4:32 Some additional cifs patches for 6.5 stable to address issue brought up by kernel regression tracker Steve French
2023-10-26 13:09 ` Sasha Levin [this message]
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=ZTplC1_qJYL1wR2G@sashalap \
--to=sashal@kernel.org \
--cc=bernd.feige@uniklinik-freiburg.de \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=regressions@lists.linux.dev \
--cc=ronniesahlberg@gmail.com \
--cc=smfrench@gmail.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox