From: Paulo Alcantara <pc@cjr.nz>
To: linux-cifs@vger.kernel.org, smfrench@gmail.com
Cc: Paulo Alcantara <pc@cjr.nz>
Subject: [PATCH 0/3] Support multiple ips per hostname
Date: Tue, 11 May 2021 13:36:06 -0300 [thread overview]
Message-ID: <20210511163609.11019-1-pc@cjr.nz> (raw)
Steve,
Follow a series to handle multiple ip addresses per hostame when
mounting, chasing DFS referrals and reconnecting.
We've defined a maximum number of 16 addresses a hostname can handle
as we did in mount.cifs (resolve_host.c::resolve_host). If that's not
OK, then we could make it flexible by creating a new mount option like
'maxaddrs=N' or just increase it in both sides.
The mount.cifs(8) patch that passes multiple 'ip=' options to handle
all resolved addresses will be posted soon.
Paulo Alcantara (3):
cifs: introduce smb3_options_for_each() helper
cifs: handle multiple ip addresses per hostname
cifs: fix find_root_ses() when refresing dfs cache
fs/cifs/cifs_dfs_ref.c | 48 +-
fs/cifs/cifsglob.h | 24 +-
fs/cifs/connect.c | 1042 ++++++++++++++++++++++++----------------
fs/cifs/dfs_cache.c | 12 +-
fs/cifs/dns_resolve.c | 72 +--
fs/cifs/dns_resolve.h | 5 +-
fs/cifs/fs_context.c | 22 +-
fs/cifs/fs_context.h | 4 +-
fs/cifs/misc.c | 95 +++-
9 files changed, 828 insertions(+), 496 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-11 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 16:36 Paulo Alcantara [this message]
2021-05-11 16:36 ` [PATCH 1/3] cifs: introduce smb3_options_for_each() helper Paulo Alcantara
2021-05-11 18:15 ` kernel test robot
2021-05-11 16:36 ` [PATCH 2/3] cifs: handle multiple ip addresses per hostname Paulo Alcantara
2021-05-11 18:47 ` kernel test robot
2021-05-11 18:47 ` kernel test robot
2021-05-11 16:36 ` [PATCH 3/3] cifs: fix find_root_ses() when refresing dfs cache Paulo Alcantara
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=20210511163609.11019-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