From: Nathan Chancellor <nathan@kernel.org>
To: syzbot <syzbot+a521f132f5a83d10ab40@syzkaller.appspotmail.com>
Cc: 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
Subject: Re: [syzbot] linux-next build error (18)
Date: Fri, 15 Nov 2024 17:59:35 -0700 [thread overview]
Message-ID: <20241116005935.GA1180844@thelio-3990X> (raw)
In-Reply-To: <67371529.050a0220.1324f8.00a4.GAE@google.com>
On Fri, Nov 15, 2024 at 01:32:25AM -0800, syzbot wrote:
> syzbot found the following issue on:
>
> HEAD commit: 744cf71b8bdf Add linux-next specific files for 20241115
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=10525cc0580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ada879778ea11d6f
> dashboard link: https://syzkaller.appspot.com/bug?extid=a521f132f5a83d10ab40
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+a521f132f5a83d10ab40@syzkaller.appspotmail.com
>
> security/apparmor/domain.c:695:3: error: expected expression
> security/apparmor/domain.c:697:3: error: use of undeclared identifier 'new_profile'
> security/apparmor/domain.c:699:8: error: use of undeclared identifier 'new_profile'
> security/apparmor/domain.c:704:11: error: use of undeclared identifier 'new_profile'
I sent a patch for this earlier this week but it does not look like it
has been picked up yet:
https://lore.kernel.org/20241111-apparmor-fix-label-declaration-warning-v1-1-adb64ab6482b@kernel.org/
Cheers,
Nathan
prev parent reply other threads:[~2024-11-16 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 9:32 [syzbot] linux-next build error (18) syzbot
2024-11-16 0:59 ` Nathan Chancellor [this message]
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=20241116005935.GA1180844@thelio-3990X \
--to=nathan@kernel.org \
--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=syzbot+a521f132f5a83d10ab40@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox