From mboxrd@z Thu Jan 1 00:00:00 1970 From: dvyukov@google.com (Dmitry Vyukov) Date: Thu, 6 Sep 2018 21:35:58 +0200 Subject: WARNING in apparmor_secid_to_secctx In-Reply-To: References: <000000000000c178e305749daba4@google.com> <37aec45f-69ad-9705-21f1-64ee4ce4a772@tycho.nsa.gov> <9537a6ff-daf4-d572-bf93-68230909b68e@tycho.nsa.gov> <4b37e892-4d79-aefb-92ab-7753b89b8963@tycho.nsa.gov> <1ea19628-3bbe-2073-d623-824337c15ed6@tycho.nsa.gov> <6c9112a2-33f3-0c29-c944-1d129a0026e7@tycho.nsa.gov> Message-ID: To: linux-security-module@vger.kernel.org List-Id: linux-security-module.vger.kernel.org On Thu, Sep 6, 2018 at 1:19 PM, Dmitry Vyukov wrote: > On Thu, Sep 6, 2018 at 12:59 PM, Dmitry Vyukov wrote: >> On Wed, Sep 5, 2018 at 7:37 PM, Casey Schaufler 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. First one that looks smack-specific: https://syzkaller.appspot.com/bug?id=9eda6092f146cb23cb9109f675a2e2cb743ee48b