linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>
To: Paulo Alcantara <pc@cjr.nz>,
	"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: Re: cifs.upcall requests ticket for wrong host when using dfs
Date: Thu, 9 Jan 2020 12:27:46 +0000	[thread overview]
Message-ID: <3ddf0683-0213-1c43-bcc7-cfc3cb8bc28b@prodrive-technologies.com> (raw)
In-Reply-To: <87y2uh264k.fsf@cjr.nz>

Hi Paulo

On 08-01-2020 18:46, Paulo Alcantara wrote:
> Hi Martijn,
> 
> Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com> writes:
> 
>> I applied your patch to 5.4.6 and it seems to work. I attached
>> the logs.
>>
>> Regards, Martijn

[..lots of logging..]

>> [  137.094211] fs/cifs/cifs_dfs_ref.c: cifs_dfs_do_automount: cifs_dfs_do_mount:\DC03.Prodrive.nl\product\KAES6309 , mnt:000000001bbef447
>> [  137.094211] fs/cifs/cifs_dfs_ref.c: leaving cifs_dfs_do_automount
>> [  137.094212] fs/cifs/cifs_dfs_ref.c: leaving cifs_dfs_d_automount [ok]
> 
> Thanks for testing it!
> 
> So far so good?
> 
> Let me know so I can prepare a patch for upstream.

Yes, so far so good. Thanks a lot for the quick response! Not a trivial 
patch as far I as i can judge.

Also the machine we have running with your other DFS patches is running 
for 8 weeks now and survived several relocations of our dfs shares and 
adding/removal of DCs!

Is there any news on the acceptance of your [PATCH v4 0/6] DFS fixes?

Regards, Martijn

-- 
Martijn de Gouw
Designer
Prodrive Technologies
Mobile: +31 63 17 76 161
Phone:  +31 40 26 76 200

  reply	other threads:[~2020-01-09 12:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 14:11 cifs.upcall requests ticket for wrong host when using dfs Martijn de Gouw
     [not found] ` <87png0boej.fsf@cjr.nz>
2020-01-03 16:30   ` Martijn de Gouw
2020-01-03 20:14     ` Paulo Alcantara
2020-01-06 15:07       ` Martijn de Gouw
2020-01-06 23:30         ` Paulo Alcantara
2020-01-07 16:13           ` Martijn de Gouw
2020-01-08 17:46             ` Paulo Alcantara
2020-01-09 12:27               ` Martijn de Gouw [this message]
2020-01-09 13:06                 ` Paulo Alcantara
2020-01-30 17:46                   ` Jacob Shivers
2020-01-30 18:55                     ` Steve French
2020-01-30 19:06                       ` Jacob Shivers

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=3ddf0683-0213-1c43-bcc7-cfc3cb8bc28b@prodrive-technologies.com \
    --to=martijn.de.gouw@prodrive-technologies.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@cjr.nz \
    /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;
as well as URLs for NNTP newsgroup(s).