diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2018-06-11 08:22:34 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-06-11 08:22:34 -0700 |
commit | a2225d931f75ddd3c39f4d0d195fad99dfd68671 (patch) | |
tree | 5b9333556f2fb3f10ea1864f095d8e2f86ddf373 /fs/crypto | |
parent | 0f105cf4f60e5afdf2932fed7f05ce776ce14289 (diff) | |
download | linux-stable-a2225d931f75ddd3c39f4d0d195fad99dfd68671.tar.gz linux-stable-a2225d931f75ddd3c39f4d0d195fad99dfd68671.tar.bz2 linux-stable-a2225d931f75ddd3c39f4d0d195fad99dfd68671.zip |
autofs: remove left-over autofs4 stubs
There's no need to retain the fs/autofs4 directory for backward
compatibility.
Adding an AUTOFS4_FS fragment to the autofs Kconfig and a module alias
for autofs4 is sufficient for almost all cases. Not keeping fs/autofs4
remnants will prevent "insmod <path>/autofs4/autofs4.ko" from working
but this shouldn't be used in automation scripts rather than
modprobe(8).
There were some comments about things to look out for with the module
rename in the fs/autofs4/Kconfig that is removed by this patch, see the
commit patch if you are interested.
One potential problem with this change is that when the
fs/autofs/Kconfig fragment for AUTOFS4_FS is removed any AUTOFS4_FS
entries will be removed from the kernel config, resulting in no autofs
file system being built if there is no AUTOFS_FS entry also.
This would have also happened if the fs/autofs4 remnants had remained
and is most likely to be a problem with automated builds.
Please check your build configurations before the removal which will
occur after the next couple of kernel releases.
Acked-by: Ian Kent <raven@themaw.net>
[ With edits and commit message from Ian Kent ]
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/crypto')
0 files changed, 0 insertions, 0 deletions