From: syzbot <syzbot+5301015e05ed3b325b0d@syzkaller.appspotmail.com>
To: apparmor@lists.ubuntu.com, jmorris@namei.org,
john.johansen@canonical.com, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org,
linux-security-module@vger.kernel.org, paul@paul-moore.com,
serge@hallyn.com, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com, terrelln@fb.com
Subject: [syzbot] linux-next build error (14)
Date: Thu, 08 Dec 2022 00:48:33 -0800 [thread overview]
Message-ID: <00000000000025d41005ef4d1a72@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: f925116b24c0 Add linux-next specific files for 20221208
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15dfabd3880000
kernel config: https://syzkaller.appspot.com/x/.config?x=8b2d3e63e054c24f
dashboard link: https://syzkaller.appspot.com/bug?extid=5301015e05ed3b325b0d
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5301015e05ed3b325b0d@syzkaller.appspotmail.com
security/apparmor/policy_unpack.c:316:18: error: unknown type name 'tri'
security/apparmor/policy_unpack.c:325:10: error: 'TRI_TRUE' undeclared (first use in this function)
security/apparmor/policy_unpack.c:328:9: error: 'TRI_NONE' undeclared (first use in this function); did you mean 'IRQ_NONE'?
security/apparmor/policy_unpack.c:331:9: error: 'TRI_FALSE' undeclared (first use in this function)
security/apparmor/policy_unpack.c:455:42: error: 'TRI_TRUE' undeclared (first use in this function)
security/apparmor/policy_unpack.c:529:42: error: 'TRI_TRUE' undeclared (first use in this function)
security/apparmor/policy_unpack.c:559:42: error: 'TRI_TRUE' undeclared (first use in this function)
security/apparmor/policy_unpack.c:611:42: error: 'TRI_TRUE' undeclared (first use in this function)
security/apparmor/policy_unpack.c:674:42: error: 'TRI_TRUE' undeclared (first use in this function)
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2022-12-08 8:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000025d41005ef4d1a72@google.com \
--to=syzbot+5301015e05ed3b325b0d@syzkaller.appspotmail.com \
--cc=apparmor@lists.ubuntu.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=sfr@canb.auug.org.au \
--cc=syzkaller-bugs@googlegroups.com \
--cc=terrelln@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.