Buildresult: linus/nommu_defconfig/microblaze-gcc5 built on Jul 6 2018, 05:58

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Jul 6 2018, 05:58
Duration:	0:00:41.855006
Builder:	ka3
Revision:	autofs: rename 'autofs' module back to 'autofs4' (`d02d21ea007b6b33cdaf15c2f84fb1fea996ecc2)`
Target:	linus/nommu_defconfig/microblaze-gcc5
Branch:	linus
Compiler:	microblaze-gcc5 (microblazeel-linux-gcc.br_real (Buildroot 2016.11-git-00613-ge98b4dd) 5.4.0)
Config:	nommu_defconfig (download)
Log:	Download original No warnings found in log. Full Log # git rev-parse -q --verify d02d21ea007b6b33cdaf15c2f84fb1fea996ecc2^{commit} d02d21ea007b6b33cdaf15c2f84fb1fea996ecc2 already have revision, skipping fetch # git checkout -q -f -B kisskb d02d21ea007b6b33cdaf15c2f84fb1fea996ecc2 # git clean -qxdf # < git log -1 # commit d02d21ea007b6b33cdaf15c2f84fb1fea996ecc2 # Author: Linus Torvalds <torvalds@linux-foundation.org> # Date: Wed Jul 4 18:17:51 2018 -0700 # # autofs: rename 'autofs' module back to 'autofs4' # # It turns out that systemd has a bug: it wants to load the autofs module # early because of some initialization ordering with udev, and it doesn't # do that correctly. Everywhere else it does the proper "look up module # name" that does the proper alias resolution, but in that early code, it # just uses a hardcoded "autofs4" for the module name. # # The result of that is that as of commit a2225d931f75 ("autofs: remove # left-over autofs4 stubs"), you get # # systemd[1]: Failed to insert module 'autofs4': No such file or directory # # in the system logs, and a lack of module loading. All this despite the # fact that we had very clearly marked 'autofs4' as an alias for this # module. # # What's so ridiculous about this is that literally everything else does # the module alias handling correctly, including really old versions of # systemd (that just used 'modprobe' to do this), and even all the other # systemd module loading code. # # Only that special systemd early module load code is broken, hardcoding # the module names for not just 'autofs4', but also "ipv6", "unix", # "ip_tables" and "virtio_rng". Very annoying. # # Instead of creating an _additional_ separate compatibility 'autofs4' # module, just rely on the fact that everybody else gets this right, and # just call the module 'autofs4' for compatibility reasons, with 'autofs' # as the alias name. # # That will allow the systemd people to fix their bugs, adding the proper # alias handling, and maybe even fix the name of the module to be just # "autofs" (so that they can _test_ the alias handling). And eventually, # we can revert this silly compatibility hack. # # See also # # https://github.com/systemd/systemd/issues/9501 # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902946 # # for the systemd bug reports upstream and in the Debian bug tracker # respectively. # # Fixes: a2225d931f75 ("autofs: remove left-over autofs4 stubs") # Reported-by: Ben Hutchings <ben@decadent.org.uk> # Reported-by: Michael Biebl <biebl@debian.org> # Cc: Ian Kent <raven@themaw.net> # Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux-gcc --version # < git log --format=%s --max-count=1 d02d21ea007b6b33cdaf15c2f84fb1fea996ecc2 # < make -s -j 80 ARCH=microblaze O=/kisskb/build/linus_nommu_defconfig_microblaze CROSS_COMPILE=/opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux- nommu_defconfig # make -s -j 80 ARCH=microblaze O=/kisskb/build/linus_nommu_defconfig_microblaze CROSS_COMPILE=/opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux- Kernel: arch/microblaze/boot/linux.bin is ready (#1) Completed OK # rm -rf /kisskb/build/linus_nommu_defconfig_microblaze # Build took: 0:00:41.855006

© Michael Ellerman 2006-2018.