Hi Steve,
Please consider the attached patch for performing the DNS query again
on reconnect.
This is important when connecting to Azure file shares. The UNC
generally contains the server name as a FQDN, and the IP address which
the name resolves to can change over time.
After our last conversation about this, I discovered that for the
non-DFS scenario, we never do DNS resolutions in cifs.ko, since
mount.cifs already resolves the name and passes the "addr=" arg during
mount.
Hi Paulo,
I noticed that you had a patch for this long back. But I don't see
that call happening in the latest code. Any idea why that was done?
========================
commit 28eb24ff75c5ac130eb326b3b4d0dcecfc0f427d
Author: Paulo Alcantara <paulo@xxxxxxxx>
Date: Tue Nov 20 15:16:36 2018 -0200
cifs: Always resolve hostname before reconnecting
In case a hostname resolves to a different IP address (e.g. long
running mounts), make sure to resolve it every time prior to calling
generic_ip_connect() in reconnect.
Suggested-by: Steve French <stfrench@xxxxxxxxxxxxx>
Signed-off-by: Paulo Alcantara <palcantara@xxxxxxx>
Signed-off-by: Steve French <stfrench@xxxxxxxxxxxxx>
=========================
--
Regards,
Shyam
Attachment:
0001-cifs-On-cifs_reconnect-resolve-the-hostname-again.patch
Description: Binary data
