On Tue, Feb 19, 2013 at 03:20:15PM -0500, Steve Dickson wrote: > On 19/02/13 10:40, Steve Dickson wrote: > >>>> >>> Also: did you figure out why NFSv4 wasn't working when the labeled NFS > >>>> >>> support is configured out? > >>> >> I'll look into this but this was not the case the last time I checked... > >> > > >> > Let me know how I can help reproduce the problem. All I did was: > >> > > >> > - build a kernel with CONFIG_NFS_V4_SECURITY_LABEL and > >> > CONFIG_NFSD_V4_SECURITY_LABEL both off. > >> > - attempt a v4 mount between client and server both running that > >> > kernel. > The bug is due to the fact the the bit masked used when labels are not > wanted (attr_bitmask_nl) was not being initialized when CONFIG_NFS_V4_SECURITY_LABEL > is not defined. Nice catch! Oh, OK, that would explain the 0-bitmask getattr. Thanks! --b. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
