From: Paulo Alcantara <pc@manguebit.com>
To: David Voit <david.voit@gmail.com>, linux-cifs@vger.kernel.org
Cc: David Voit <david.voit@gmail.com>,
Jacob Shivers <jshivers@redhat.com>,
Pavel Shilovsky <piastryyy@gmail.com>
Subject: Re: [PATCH v4 1/1] Implement CLDAP Ping to find the closest site
Date: Wed, 10 Apr 2024 16:08:14 -0300 [thread overview]
Message-ID: <80e09054c9490c359e8534e07f924897@manguebit.com> (raw)
In-Reply-To: <20240403052448.4290-2-david.voit@gmail.com>
David Voit <david.voit@gmail.com> writes:
> For domain based DFS we always need to contact the domain controllers.
> On setups, which are using bigger AD installations you could get random dc on the other side of the world,
> if you don't have site support. This can lead to network timeouts and other problems.
>
> CLDAP-Ping uses ASN.1 + UDP (CLDAP) and custom-DCE encoding including DName compressions without
> field separation. Finally after finding the sitename we now need to do a DNS SRV lookups to find
> the correct IPs to our closest site and fill up the remaining IPs from the global list.
>
> Signed-off-by: David Voit <david.voit@gmail.com>
> ---
> Makefile.am | 15 ++-
> cldap_ping.c | 346 +++++++++++++++++++++++++++++++++++++++++++++++++
> cldap_ping.h | 14 ++
> mount.cifs.c | 5 +-
> resolve_host.c | 258 +++++++++++++++++++++++++++++++-----
> resolve_host.h | 6 +-
> 6 files changed, 606 insertions(+), 38 deletions(-)
> create mode 100644 cldap_ping.c
> create mode 100644 cldap_ping.h
Great work! I've tested it and found no issues.
Most of the cifs-utils code seems to follow the Linux kernel coding
style, but I don't see it being mentioned anywhere, so the patch looks
good.
Thanks!
next prev parent reply other threads:[~2024-04-10 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 5:24 [PATCH v4 0/1] cifs-utils: CLDAP-Ping to find the correct site David Voit
2024-04-03 5:24 ` [PATCH v4 1/1] Implement CLDAP Ping to find the closest site David Voit
2024-04-04 2:10 ` Jacob Shivers
2024-04-10 19:08 ` Paulo Alcantara [this message]
[not found] ` <CAPmGGo7XogXA8RppeqOtidWsgL84u+J4SUB7-st=A9a2ooPriQ@mail.gmail.com>
2024-04-20 20:55 ` Pavel Shilovsky
2024-04-22 15:10 ` Paulo Alcantara
2024-04-23 11:40 ` Jacob Shivers
2024-04-28 0:10 ` Pavel Shilovsky
2024-04-22 15:10 ` David Voit
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=80e09054c9490c359e8534e07f924897@manguebit.com \
--to=pc@manguebit.com \
--cc=david.voit@gmail.com \
--cc=jshivers@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=piastryyy@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