[v6.1] linux-6.1.y build error

2 views
Skip to first unread message

syzbot

unread,
Mar 17, 2023, 5:32:44 AM3/17/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 7eaef76fbc46 Linux 6.1.20
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11badcd2c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=28c36fe4d02f8c88
dashboard link: https://syzkaller.appspot.com/bug?extid=583af86d78d2fd877bf8
compiler: Debian clang version 15.0.7, 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+583af8...@syzkaller.appspotmail.com

objtool.c:152:1: fatal error: closing dependency file tools/objtool/.objtool.o.d: No space left on device
orc_dump.c:215:1: fatal error: closing dependency file tools/objtool/.orc_dump.o.d: No space left on device
exec-cmd.c:213:1: fatal error: closing dependency file tools/objtool/.exec-cmd.o.d: No space left on device
orc_gen.c:245:1: fatal error: closing dependency file tools/objtool/.orc_gen.o.d: No space left on device
help.c:272:1: fatal error: closing dependency file tools/objtool/.help.o.d: No space left on device
scripts/genksyms/lex.lex.c:2257:1: fatal error: closing dependency file scripts/genksyms/.lex.lex.o.d: No space left on device
../lib/rbtree.c:597:1: fatal error: closing dependency file tools/objtool/.librbtree.o.d: No space left on device
parse-options.c:1039:1: fatal error: closing dependency file tools/objtool/.parse-options.o.d: No space left on device
arch/x86/decode.c:800:1: fatal error: closing dependency file tools/objtool/arch/x86/.decode.o.d: No space left on device
elf.c:1362:1: fatal error: closing dependency file tools/objtool/.elf.o.d: No space left on device
check.c:4357:1: fatal error: closing dependency file tools/objtool/.check.o.d: No space left on device

---
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 syzk...@googlegroups.com.

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

syzbot

unread,
Jul 15, 2023, 5:32:35 AM7/15/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages