I missed that. I just checked again and I completely overlooked this. Sorry for the confusion. On Thu, Jan 30, 2020 at 1:55 PM Steve French <smfrench@xxxxxxxxx> wrote: > > Fix is already upstream, merged into mainline Linux (commit > 5739375ee4230980166807d347cc21c305532bbc) > > On Thu, Jan 30, 2020 at 11:47 AM Jacob Shivers <jshivers@xxxxxxxxxx> 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@xxxxxx> wrote: > > > > > > Hi Martijn, > > > > > > Martijn de Gouw <martijn.de.gouw@xxxxxxxxxxxxxxxxxxxxxxxxx> 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 >
