diff options
author | Hillf Danton <dhillf@gmail.com> | 2012-04-05 14:25:09 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-04-05 15:25:50 -0700 |
commit | 7563ec4c211ba59c2331dc6b94a068250345c387 (patch) | |
tree | a0ae6582dc77ea46cb3a2fa422f2606f0155f939 /fs/libfs.c | |
parent | fd835d1f2d4826a19530bc045579ffda5775b8f7 (diff) | |
download | linux-7563ec4c211ba59c2331dc6b94a068250345c387.tar.gz linux-7563ec4c211ba59c2331dc6b94a068250345c387.tar.bz2 linux-7563ec4c211ba59c2331dc6b94a068250345c387.zip |
hugetlbfs: remove unregister_filesystem() when initializing module
It was introduced by d1d5e05ffdc1 ("hugetlbfs: return error code when
initializing module") but as Al pointed out, is a bad idea.
Quoted comments from Al:
"Note that unregister_filesystem() in module init is *always* wrong;
it's not an issue here (it's done too early to care about and
realistically the box is not going anywhere - it'll panic when attempt
to exec /sbin/init fails, if not earlier), but it's a damn bad
example.
Consider a normal fs module. Somebody loads it and in parallel with
that we get a mount attempt on that fs type. It comes between
register and failure exits that causes unregister; at that point we
are screwed since grabbing a reference to module as done by mount is
enough to prevent exit, but not to prevent the failure of init. As
the result, module will get freed when init fails, mounted fs of that
type be damned."
So remove it.
Signed-off-by: Hillf Danton <dhillf@gmail.com>
Cc: David Rientjes <rientjes@google.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/libfs.c')
0 files changed, 0 insertions, 0 deletions