Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1401583

Re: [lkp] [xfs] a08ee40a79: kmsg.XFS(vdd):unknown_mount_option[nosuchopt]

From Eric Sandeen <sandeen@sandeen.net>
Newsgroups linux.kernel
Subject Re: [lkp] [xfs] a08ee40a79: kmsg.XFS(vdd):unknown_mount_option[nosuchopt]
Date 2016-05-16 17:50 +0200
Message-ID <rzsWm-oE-17@gated-at.bofh.it> (permalink)
References <rzg8Y-u7-271@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 5/15/16 8:42 PM, kernel test robot wrote:
> FYI, we noticed the following commit:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit a08ee40a79653d082911cab9fbeff94baa7714cb ("xfs: sanitize remount options")
> 
> on test machine: vm-kbuild-4G: 4 threads qemu-system-x86_64 -enable-kvm -cpu qemu64,+ssse3 with 4G memory
> 
> caused below changes:
> 
> 
> [  666.729855] XFS (vdd): unknown mount option [nosuchopt].

This is expected, it's just that we're catching invalid remount options, now,
and being a bit noiser about it.

                default:
                        xfs_warn(mp, "unknown mount option [%s].", p);
                        return -EINVAL;

From tests/generic/082 :

# first remount ro with a bad option, a failed remount ro should not disable
# quota, but currently xfs doesn't fail in this case, the unknown option is
# just ignored, but quota is still on. This may change in future, let's
# re-consider the case then.
_scratch_mount "-o remount,ro,nosuchopt" >>$seqres.full 2>&1

so the test is intentionally passing in a bad mount option, and the kernel
is just letting us know.

Thanks,
-Eric

Back to linux.kernel | Previous | Next | Find similar | Unroll thread


Thread

Re: [lkp] [xfs] a08ee40a79:  kmsg.XFS(vdd):unknown_mount_option[nosuchopt] Eric Sandeen <sandeen@sandeen.net> - 2016-05-16 17:50 +0200

csiph-web