Even though the smbpasswd usage is a bit wonky/unclear, there is a real bug with autofs 5.1.8 in s390x. dmesg is full of messages like these when the problem happens:
[ 435.375028] autofs4:pid:9655:validate_dev_ioctl: invalid path supplied for cmd(0xc018937e)
[ 435.375116] autofs4:pid:9655:validate_dev_ioctl: invalid path supplied for cmd(0xc018937e)
[ 435.375163] autofs4:pid:9655:validate_dev_ioctl: invalid path supplied for cmd(0xc018937e)
[ 435.375211] autofs4:pid:9655:validate_dev_ioctl: invalid path supplied for cmd(0xc018937e)
[ 435.375215] autofs4:pid:9655:validate_dev_ioctl: invalid path supplied for cmd(0xc018937e)
[ 435.375217] autofs4:pid:9655:validate_dev_ioctl: invalid path supplied for cmd(0xc018937e)
Even though the smbpasswd usage is a bit wonky/unclear, there is a real bug with autofs 5.1.8 in s390x. dmesg is full of messages like these when the problem happens:
[ 435.375028] autofs4: pid:9655: validate_ dev_ioctl: invalid path supplied for cmd(0xc018937e) pid:9655: validate_ dev_ioctl: invalid path supplied for cmd(0xc018937e) pid:9655: validate_ dev_ioctl: invalid path supplied for cmd(0xc018937e) pid:9655: validate_ dev_ioctl: invalid path supplied for cmd(0xc018937e) pid:9655: validate_ dev_ioctl: invalid path supplied for cmd(0xc018937e) pid:9655: validate_ dev_ioctl: invalid path supplied for cmd(0xc018937e)
[ 435.375116] autofs4:
[ 435.375163] autofs4:
[ 435.375211] autofs4:
[ 435.375215] autofs4:
[ 435.375217] autofs4: