From: Steve French <smfrench@gmail.com>
To: Jacob Shivers <jshivers@redhat.com>
Cc: Paulo Alcantara <pc@cjr.nz>,
Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>,
"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: Re: cifs.upcall requests ticket for wrong host when using dfs
Date: Thu, 30 Jan 2020 12:55:19 -0600 [thread overview]
Message-ID: <CAH2r5mvEjD9rggUyTJMXKiyPn9fyRAq9DDWsn5xAkJC_6bFfrw@mail.gmail.com> (raw)
In-Reply-To: <CALe0_75hsoemi1-du=-YO=xO_gR7-41RKirwNrnU+L753Ycrhg@mail.gmail.com>
Fix is already upstream, merged into mainline Linux (commit
5739375ee4230980166807d347cc21c305532bbc)
On Thu, Jan 30, 2020 at 11:47 AM Jacob Shivers <jshivers@redhat.com> wrote:
>
> Hello Paulo,
>
> I ran into this issue and noted that I can reproduce this 100% of the
> time with a Samba SMB target. I tried with Windows SMB targets, even
> when they are not part of the direct DFS namespace, but I have so far
> been unable to reproduce that way.
>
> Hello Martijn,
> Would you mind stating who the provider is for the impacted SMB target
> in your environment?
>
> Thanks,
> Jacob
>
> On Thu, Jan 9, 2020 at 8:06 AM Paulo Alcantara <pc@cjr.nz> wrote:
> >
> > Hi Martijn,
> >
> > Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com> writes:
> >
> > > Yes, so far so good. Thanks a lot for the quick response! Not a trivial
> > > patch as far I as i can judge.
> >
> > Cool! Thanks for the confirmation. Just sent a patch with this fix, BTW.
> >
> > > 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?
> >
> > I don't have any news, but I'll talk to Steve and Aurelien about them.
> >
> > Thanks,
> > Paulo
> >
>
--
Thanks,
Steve
next prev parent reply other threads:[~2020-01-30 18:55 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
2020-01-09 13:06 ` Paulo Alcantara
2020-01-30 17:46 ` Jacob Shivers
2020-01-30 18:55 ` Steve French [this message]
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=CAH2r5mvEjD9rggUyTJMXKiyPn9fyRAq9DDWsn5xAkJC_6bFfrw@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=jshivers@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=martijn.de.gouw@prodrive-technologies.com \
--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).