Files
linux-stable-mirror/include/linux
Al Viro c64cd6e34e reimplement path_mountpoint() with less magic
... and get rid of a bunch of bugs in it.  Background:
the reason for path_mountpoint() is that umount() really doesn't
want attempts to revalidate the root of what it's trying to umount.
The thing we want to avoid actually happen from complete_walk();
solution was to do something parallel to normal path_lookupat()
and it both went overboard and got the boilerplate subtly
(and not so subtly) wrong.

A better solution is to do pretty much what the normal path_lookupat()
does, but instead of complete_walk() do unlazy_walk().  All it takes
to avoid that ->d_weak_revalidate() call...  mountpoint_last() goes
away, along with everything it got wrong, and so does the magic around
LOOKUP_NO_REVAL.

Another source of bugs is that when we traverse mounts at the final
location (and we need to do that - umount . expects to get whatever's
overmounting ., if any, out of the lookup) we really ought to take
care of ->d_manage() - as it is, manual umount of autofs automount
in progress can lead to unpleasant surprises for the daemon.  Easily
solved by using handle_lookup_down() instead of follow_mount().

Tested-by: Ian Kent <raven@themaw.net>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2020-01-15 01:36:06 -05:00
..
2019-11-12 11:43:29 -05:00
2019-11-15 23:44:48 +01:00
2019-12-03 07:36:38 -07:00
2019-11-26 10:26:26 +01:00
2019-12-03 11:20:37 +01:00
2019-11-20 09:40:10 +01:00
2019-12-01 12:59:06 -08:00
2019-11-11 09:02:56 +01:00
2019-12-04 19:44:14 -08:00
2019-11-14 19:06:47 -08:00
2019-11-06 08:55:23 -05:00
2019-11-06 08:55:23 -05:00
2019-11-13 19:09:47 +08:00
2019-11-14 13:07:48 +08:00
2019-12-04 19:44:14 -08:00
2019-12-01 06:29:17 -08:00
2019-11-13 12:15:34 -08:00
2019-11-13 00:33:21 +11:00
2019-11-07 07:00:26 +01:00
2019-11-14 12:20:02 +08:00