Messages in this thread | | | From | Dmitry Vyukov <> | Date | Thu, 6 Sep 2018 13:19:31 +0200 | Subject | Re: WARNING in apparmor_secid_to_secctx |
| |
On Thu, Sep 6, 2018 at 12:59 PM, Dmitry Vyukov <dvyukov@google.com> wrote: > On Wed, Sep 5, 2018 at 7:37 PM, Casey Schaufler <casey@schaufler-ca.com> wrote: >> On 9/5/2018 4:08 AM, Dmitry Vyukov wrote: >>> Thanks! I've re-enabled selinux on syzbot: >>> https://github.com/google/syzkaller/commit/196410e4f5665d4d2bf6c818d06f1c8d03cfa8cc >>> Now we will have instances with apparmor and with selinux. >> >> Any chance we could get a Smack instance as well? > > Hi Casey, > > Sure! > Provided you want to fix bugs ;) > I've setup an instance with smack enabled: > https://github.com/google/syzkaller/commit/0bb7a7eb8e0958c6fbe2d69615b9fae4af88c8ee
But just doing default things does not seem to find much. I guess common paths through the hooks are well exercised already. So perhaps if we do more non-trivial things, it can find more stuff. But what are they? Adding/changing/removing xattr's? Which? What are the values? Changing security contexts? How? What else? selinux has own filesystem and we should touch some files there: https://github.com/google/syzkaller/blob/master/sys/linux/selinux.txt But we don't anything similar for other modules.
| |