Re: long name length protection triggering when it shouldn't

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for testing and confirming the patch fixes the issue.

I will try to figure out why the mount options affect this. But that
is not as urgent.





On Sat, Oct 28, 2017 at 10:58 AM, Jack Hill <jackhill@xxxxxxxx> wrote:
> On Thu, 26 Oct 2017, Leif Sahlberg wrote:
>
>> Can you try that patch and confirm if it fixes the issue for you too ?
>
>
> I am happy to confirm that the patch fixes the issue for me.
>
> Is it worth trying to figure out why MaxPathNameComponentLength is not being
> set correctly? For me, it seems to be set correctly when I use different
> mount options (either a different sec= option, or when using multiuser).
>
> Do you expect the proposed patch to be the eventual fix that ends up in a
> released kernel?
>
>
> Thanks,
> Jack
> --
> To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux