Searched hist:"56 cbb429" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/include/linux/ |
| H A D | fs_pin.h | 56cbb429 Thu Jul 04 15:57:51 CDT 2019 Al Viro <viro@zeniv.linux.org.uk> switch the remnants of releasing the mountpoint away from fs_pin
We used to need rather convoluted ordering trickery to guarantee
that dput() of ex-mountpoints happens before the final mntput()
of the same. Since we don't need that anymore, there's no point
playing with fs_pin for that.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
56cbb429 Thu Jul 04 15:57:51 CDT 2019 Al Viro <viro@zeniv.linux.org.uk> switch the remnants of releasing the mountpoint away from fs_pin
We used to need rather convoluted ordering trickery to guarantee
that dput() of ex-mountpoints happens before the final mntput()
of the same. Since we don't need that anymore, there's no point
playing with fs_pin for that.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
| /openbmc/linux/fs/ |
| H A D | fs_pin.c | 56cbb429 Thu Jul 04 15:57:51 CDT 2019 Al Viro <viro@zeniv.linux.org.uk> switch the remnants of releasing the mountpoint away from fs_pin
We used to need rather convoluted ordering trickery to guarantee
that dput() of ex-mountpoints happens before the final mntput()
of the same. Since we don't need that anymore, there's no point
playing with fs_pin for that.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
56cbb429 Thu Jul 04 15:57:51 CDT 2019 Al Viro <viro@zeniv.linux.org.uk> switch the remnants of releasing the mountpoint away from fs_pin
We used to need rather convoluted ordering trickery to guarantee
that dput() of ex-mountpoints happens before the final mntput()
of the same. Since we don't need that anymore, there's no point
playing with fs_pin for that.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
| H A D | mount.h | 56cbb429 Thu Jul 04 15:57:51 CDT 2019 Al Viro <viro@zeniv.linux.org.uk> switch the remnants of releasing the mountpoint away from fs_pin
We used to need rather convoluted ordering trickery to guarantee
that dput() of ex-mountpoints happens before the final mntput()
of the same. Since we don't need that anymore, there's no point
playing with fs_pin for that.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
56cbb429 Thu Jul 04 15:57:51 CDT 2019 Al Viro <viro@zeniv.linux.org.uk> switch the remnants of releasing the mountpoint away from fs_pin
We used to need rather convoluted ordering trickery to guarantee
that dput() of ex-mountpoints happens before the final mntput()
of the same. Since we don't need that anymore, there's no point
playing with fs_pin for that.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
| H A D | namespace.c | 56cbb429 Thu Jul 04 15:57:51 CDT 2019 Al Viro <viro@zeniv.linux.org.uk> switch the remnants of releasing the mountpoint away from fs_pin
We used to need rather convoluted ordering trickery to guarantee
that dput() of ex-mountpoints happens before the final mntput()
of the same. Since we don't need that anymore, there's no point
playing with fs_pin for that.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
56cbb429 Thu Jul 04 15:57:51 CDT 2019 Al Viro <viro@zeniv.linux.org.uk> switch the remnants of releasing the mountpoint away from fs_pin
We used to need rather convoluted ordering trickery to guarantee
that dput() of ex-mountpoints happens before the final mntput()
of the same. Since we don't need that anymore, there's no point
playing with fs_pin for that.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|