linux-kernel - Re: [syzbot] upstream build error (20)

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-prev] [day] [month] [year] [list]

Message-ID: <CANp29Y4ySB6_s8zqO3zgskzx5y6ECUVobYxje-k3V2hSEiULGQ@mail.gmail.com>
Date:   Mon, 3 Jul 2023 18:45:39 +0200
From:   Aleksandr Nogikh <nogikh@...gle.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     syzbot <syzbot+3ea47fc22e48e9ec4324@...kaller.appspotmail.com>,
        dave.hansen@...ux.intel.com, hpa@...or.com,
        linux-kernel@...r.kernel.org, mingo@...hat.com,
        syzkaller-bugs@...glegroups.com, tglx@...utronix.de, x86@...nel.org
Subject: Re: [syzbot] upstream build error (20)

On Sun, Jul 2, 2023 at 9:51 PM Borislav Petkov <bp@...en8.de> wrote:
>
> On Sun, Jul 02, 2023 at 11:56:57AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:    77b1a7f7a05c Merge tag 'mm-nonmm-stable-2023-06-24-19-23' ..
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=1701aabd280000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=dbdd409f194c6563
> > dashboard link: https://syzkaller.appspot.com/bug?extid=3ea47fc22e48e9ec4324
> > 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+3ea47fc22e48e9ec4324@...kaller.appspotmail.com
> >
> > ./arch/x86/include/asm/mem_encrypt.h:23:20: error: static declaration of 'mem_encrypt_init' follows non-static declaration
> >
> > ---
> > 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 bug is already fixed, let syzbot know by replying with:
> > #syz fix: exact-commit-title
> >
> > If you want to change bug's subsystems, reply with:
> > #syz set subsystems: new-subsystem
> > (See the list of subsystem names on the web dashboard)
> >
> > If the bug is a duplicate of another bug, reply with:
> > #syz dup: exact-subject-of-another-report
> >
> > If you want to undo deduplication, reply with:
> > #syz undup
>
> #syz fix: 0a9567ac5e6a ("x86/mem_encrypt: Unbreak the AMD_MEM_ENCRYPT=n build")

Thank you for letting syzbot know the fixing commit!
Syzbot expects to see only the title, so here's an update:

#syz fix: x86/mem_encrypt: Unbreak the AMD_MEM_ENCRYPT=n build

>
> --
> Regards/Gruss,
>     Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>
> --