Re: mount(2) with NULL fstype returns ENOENT instead of EINVAL after introducing fs_context methods

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



FIX: It's calling mount(2) with a NULL device name.

On Thu, Mar 14, 2019 at 3:20 PM Murphy Zhou <jencce.kernel@xxxxxxxxx> wrote:
>
> Hi,
>
> Since this
> commit f3a09c92018a91ad0981146a4ac59414f814d801 Author: Al Viro
> <viro@xxxxxxxxxxxxxxxxxx>
> Date:   Sun Dec 23 18:55:56 2018 -0500
>
>     introduce fs_context methods
>
>     Signed-off-by: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
>
>
> LTP[1] mount02 tests #5 starts to fail.
>
> This testcase is calling mount(2) with a  NULL fs type. It's expecting
> EINVAL to PASS but now we are getting ENOENT.
>
> Should I fix the testcase or there is some work in the kernel ? I'm
> wring this email to confirm with you guys.
>
> Thanks,
> M
> [1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/mount/mount02.c



[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux