On Thu, Jan 19, 2017 at 06:14:33PM -0000, Thomas Fili wrote:
> @Seth : Yes, this problem is very confusing
Thanks for the clarifications.
> Unfortunately the kernel 4.4.0-54 is not available any longer from
> offical repos ... so i not able to test this one again ... but maybe
> this kernel had also the problem ?!
Yeah, looks like this build never made it out of our PPA.
> But i will try to find the last working kernel between 4.4.0-34 to
> 4.4.0-53 tomorrow.
Please do. So far we've been working under the assumption that this is a
bug introduced after 4.4.0-54, so if it was introduced before that we
would never have found it. Honestly though if the build at commit
50f208e18014589971583a8495987194724d56e4 is bad then 4.4.0-54 is almost
certainly bad as well.
> And there is also another bug with accessing a nfsv4 subshare
Yes, I haven't forgotten about this one. I'm waiting on the upstream
developers right now, but if they don't come back with something by
early next week I'll pursue a temporary fix in x/y.
On Thu, Jan 19, 2017 at 06:14:33PM -0000, Thomas Fili wrote:
> @Seth : Yes, this problem is very confusing
Thanks for the clarifications.
> Unfortunately the kernel 4.4.0-54 is not available any longer from
> offical repos ... so i not able to test this one again ... but maybe
> this kernel had also the problem ?!
Yeah, looks like this build never made it out of our PPA.
> But i will try to find the last working kernel between 4.4.0-34 to
> 4.4.0-53 tomorrow.
Please do. So far we've been working under the assumption that this is a 971583a84959871 94724d56e4 is bad then 4.4.0-54 is almost
bug introduced after 4.4.0-54, so if it was introduced before that we
would never have found it. Honestly though if the build at commit
50f208e18014589
certainly bad as well.
> And there is also another bug with accessing a nfsv4 subshare
Yes, I haven't forgotten about this one. I'm waiting on the upstream
developers right now, but if they don't come back with something by
early next week I'll pursue a temporary fix in x/y.