пт, 1 февр. 2019 г. в 06:11, Sasha Levin sashal@kernel.org:
On Thu, Jan 31, 2019 at 10:37:54AM -0800, Pavel Shilovsky wrote:
ср, 30 янв. 2019 г. в 23:16, Greg KH gregkh@linuxfoundation.org:
On Wed, Jan 30, 2019 at 04:07:30PM -0800, Pavel Shilovsky wrote:
Commit 28eb24ff75c5 ("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.
This patch needs user space changes of cifs.upcall that set a timeout value for the "dns_resolver" key.
Suggested-by: Steve French stfrench@microsoft.com Signed-off-by: Paulo Alcantara palcantara@suse.de Signed-off-by: Steve French stfrench@microsoft.com Signed-off-by: Pavel Shilovsky pshilov@microsoft.com
fs/cifs/connect.c | 53 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 53 insertions(+)
What stable kernel(s) is this to be applied to? \
All stable kernels that are under active maintenance may have the fix if it applies clearly. Please let me know if it doesn't.
So this wasn't actually tested against any of the stable kernels? Why not? Microsoft has a solid testsuite for it.
This was successfully tested on v4.4.y kernel.
-- Best regards, Pavel Shilovsky