linux-kernel - [syzbot] linux-next build error (18)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <67371529.050a0220.1324f8.00a4.GAE@google.com>
Date: Fri, 15 Nov 2024 01:32:25 -0800
From: syzbot <syzbot+a521f132f5a83d10ab40@...kaller.appspotmail.com>
To: apparmor@...ts.ubuntu.com, jmorris@...ei.org, john.johansen@...onical.com, 
	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org, 
	linux-security-module@...r.kernel.org, paul@...l-moore.com, serge@...lyn.com, 
	sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com
Subject: [syzbot] linux-next build error (18)

Hello,

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@...kaller.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'

---
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@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup