Re: [PATCH v2] selinux: fix regression introduced by move_mount(2) syscall

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

 



On Mon, Jan 20, 2020 at 7:52 AM Paul Moore <paul@xxxxxxxxxxxxxx> wrote:
> This looks good to me too, thanks Stephen.  Because of the nature of
> this fix, I'm going to merge this into next now, even though we are at
> -rc7.  Since we are effectively treating this as another mount
> operation, and reusing the file:mounton permission, I don't believe
> there should be any widespread access denials on existing distros ...
> I assume you've at least tested this on Fedora and everything looked
> okay?

I did basic boot testing plus selinux-testsuite on Fedora without any issues.
I'm not sure that Linux userspace (at least shipped in distros)
besides test/sample programs is using the new system calls yet.
And since anything that performed mounts previously using mount(2)
would have required mounton permission,
I would expect anything converted to use the new system calls would
likewise have that permission already.

> It also looks like the fs tests Richard is working on includes tests
> for the move_mount() so I think we are covered as far as the
> selinux-testsuite is concerned.

Not sure since those tests were just added in the latest version of
his patches and at this point he would
be running on kernels that lack this permission check.



[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux