On Wednesday June 3, SteveD@xxxxxxxxxx wrote: > > > Neil Brown wrote: > > Hi, > > there is a bug in the old-cache behaviour of mountd. > > Hopefully no-one is using this but you never know.... > > > > The bug was reported to redhat > > https://bugzilla.redhat.com/show_bug.cgi?id=164186 > > > > It was fixed incorrectly and never (that I recall) reported > > upstream. :-( > > > > A SLES customer thinks they have hit the same problem, which is why > > I'm looking at it. (They shouldn't really hit it because that > > version of sles uses 'new_cache' but maybe nfsdfs was disabled > > somehow - don't know yet). > > > > Anyway, when mountd gets a mount request, it tells the kernel about it > > and remembers that it told the kernel so it doesn't have to tell the > > kernel again. > > It is possible that "exportfs -r" will tell the kernel to forget that > > information if the client has since unmounted. > > So mountd really needs to tell the kernel even if it thinks the > > kernel should already know. > > > > The following patch does this if the kernel refuses to provide a > > valid filehandle. > > > > Does RHEL3 use old-cache or new-cache ?? > The new cache, if it exists... That's what I would have thought... which leave me wondering how both your customer and our customer hit the bug... I must be missing something important. > > Committed.. Thanks. NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
