From: Paulo Alcantara <pc@cjr.nz>
To: smfrench@gmail.com
Cc: linux-cifs@vger.kernel.org, Paulo Alcantara <pc@cjr.nz>
Subject: [PATCH 0/5] dfs fixes
Date: Mon, 16 Jan 2023 21:09:47 -0300 [thread overview]
Message-ID: <20230117000952.9965-1-pc@cjr.nz> (raw)
Hi Steve,
The most important fix is 1/5 that should fix those random hangs that
we've observed while running dfs tests on buildbot.
I have run twice 50 dfs tests against Windows 2022 and samba 4.16 with
these mount options
vers=3.1.1,echo_interval=10,{,hard}
vers=3.0,echo_interval=10,{,hard}
vers=3.0,echo_interval=10,{,sign}
vers=3.0,echo_interval=10,{,seal}
vers=2.1,echo_interval=10,{,hard}
vers=1.0,echo_interval=10,{,hard}
The only tests which failed (2%) were with SMB1 UNIX extensions
against samba. readdir(2) was getting STATUS_INVALID_LEVEL from
QUERY_PATH_INFO after failover for some reason -- I'll look into that
when time allows. Those failures aren't related to this series,
though.
I also did some quick tests with kerberos.
Paulo Alcantara (5):
cifs: fix potential deadlock in cache_refresh_path()
cifs: avoid re-lookups in dfs_cache_find()
cifs: don't take exclusive lock for updating target hints
cifs: remove duplicate code in __refresh_tcon()
cifs: handle cache lookup errors different than -ENOENT
fs/cifs/dfs_cache.c | 185 ++++++++++++++++++++++----------------------
1 file changed, 94 insertions(+), 91 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-17 0:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 0:09 Paulo Alcantara [this message]
2023-01-17 0:09 ` [PATCH 1/5] cifs: fix potential deadlock in cache_refresh_path() Paulo Alcantara
2023-01-17 17:07 ` Aurélien Aptel
2023-01-17 18:03 ` Paulo Alcantara
2023-01-17 0:09 ` [PATCH 2/5] cifs: avoid re-lookups in dfs_cache_find() Paulo Alcantara
2023-01-17 0:09 ` [PATCH 3/5] cifs: don't take exclusive lock for updating target hints Paulo Alcantara
2023-01-17 0:09 ` [PATCH 4/5] cifs: remove duplicate code in __refresh_tcon() Paulo Alcantara
2023-01-17 0:09 ` [PATCH 5/5] cifs: handle cache lookup errors different than -ENOENT Paulo Alcantara
2023-01-17 22:00 ` [PATCH v2 0/5] dfs fixes Paulo Alcantara
2023-01-17 22:00 ` [PATCH v2 1/5] cifs: fix potential deadlock in cache_refresh_path() Paulo Alcantara
2023-01-17 22:00 ` [PATCH v2 2/5] cifs: avoid re-lookups in dfs_cache_find() Paulo Alcantara
2023-01-17 22:00 ` [PATCH v2 3/5] cifs: don't take exclusive lock for updating target hints Paulo Alcantara
2023-01-17 22:00 ` [PATCH v2 4/5] cifs: remove duplicate code in __refresh_tcon() Paulo Alcantara
2023-01-17 22:00 ` [PATCH v2 5/5] cifs: handle cache lookup errors different than -ENOENT Paulo Alcantara
2023-01-18 1:33 ` [PATCH v2 0/5] dfs fixes Steve French
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=20230117000952.9965-1-pc@cjr.nz \
--to=pc@cjr.nz \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@gmail.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