Hi Moritz, The patch is for NFS client side bug where it was initializing the attributes to zero if NFS4ERR_MOVED is returned in LOOKUP; but referral was not followed later. This only happens with NFSv4 server and the specific error (NFS4ERR_MOVED).
It is not related to nfs-ganesha - it can be reproduced with kernel NFS as well. Are you seeing any regressions with the patch? Thanks, Pradeep On Mon, May 14, 2018 at 2:40 AM, Moritz Schlarb <schla...@uni-mainz.de> wrote: > Hello Frank and Pradeep, > > I was hoping that you would have some insight on a possible > bug/regression/incompability between nfs-ganesha and the Linux kernel > with a specific patch to which you reacted (see below) in > https://marc.info/?l=linux-nfs&m=150998968529002&w=2. > > There is no mail about the results of Pradeep's checking whether that > patch is safe for nfs-ganesha on the server side, or whether there were > additional changes needed. Maybe one of you could shed some light on that. > > I've created a tracking Debian bug report for our issue: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898165 > > Best regards, > Moritz > > On 14.05.2018 11:05, Moritz Schlarb wrote: > > Control: tags -1 + patch upstream > > Control: notfound -1 linux/3.16.51-3+deb8u1 > > > > Hi everyone, > > > > I have identified the upstream commit that introduced this > > bug/regression for us. > > > > It is c05cefcc72416a37eba5a2b35f0704ed758a9145 "nfs: Fix ugly referral > > attributes" > > (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/ > linux.git/commit/?id=c05cefcc72416a37eba5a2b35f0704ed758a9145) > > which seems to have been part of upstream 3.16.54. > > > > I have manually compiled 3.16.56-1+deb8u1 with that patch reversed and I > > can successfully mount my home directory again. > > > > Regards, > > > > -- > Moritz Schlarb > Unix-Gruppe | Systembetreuung > Zentrum für Datenverarbeitung > Johannes Gutenberg-Universität Mainz > Raum 01-331 - Tel. +49 6131 39-29441 > OpenPGP Fingerprint: DF01 2247 BFC6 > 5501 AFF2 8445 0C24 B841 C7DD BAAF >
