On Tue, 2014-07-15 at 14:05 +1000, NeilBrown wrote: > On Tue, 15 Jul 2014 11:48:33 +0800 Ian Kent <raven@xxxxxxxxxx> wrote: > ... > > So far I've tracked this to something that was introduced between 3.11 > > and 3.12. One change that went into 3.12 was Jeff Laytons' umount > > specific path resolution for umount. I've found this is also broken on > > recent RHEL-6 kernels and that change is present in them too so the > > evidence is leaning toward that being the problem. Just how could happen > > with this change I have no clue so far, it just doesn't make sense. > > Such a familiar story! I've not yet failed to find bugs like that, but > sometimes it takes a looooong time. Good luck! > > > > > Anyway that's going to make testing these patches impossible until I can > > work out what the problem is and fix it. > > > > Very sorry to hold you up on this but it can't be avoided. > > Thanks a lot for letting me know the situation! > While I always appreciate upstream review I've learnt not to depend on it. > I'll proceed with my customers based on my judgement and look forward to any > input you can provide whenever you are able to provide it. Yeah, I planed to spend some time to have a look on Wednesday and still will but, as I say, testing is going to take more time than I have just now. Usual autofs usage rarely, if ever, uses symlinks so your customers should be fine but be aware of the difficulty if you run into people that want to use amd maps. > > Thanks, > NeilBrown -- To unsubscribe from this list: send the line "unsubscribe autofs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
