linux-next build error (7)

linux-next build error (7)

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit:    ba0b4dfd Add linux-next specific files for 20200122
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17caa985e00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7b604c617a6b217c
dashboard link: https://syzkaller.appspot.com/bug?extid=dc92421ed22129134c0f
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+dc92421ed22129134c0f@syzkaller.appspotmail.com

/syzkaller/managers/upstream-linux-next-kasan-gce-root/kernel/arch/x86/platform/efi/efi_64.c:560: undefined reference to `__efi64_thunk'
/syzkaller/managers/upstream-linux-next-kasan-gce-root/kernel/arch/x86/platform/efi/efi_64.c:902: undefined reference to `efi_uv1_memmap_phys_prolog'
/syzkaller/managers/upstream-linux-next-kasan-gce-root/kernel/arch/x86/platform/efi/efi_64.c:921: undefined reference to `efi_uv1_memmap_phys_epilog'

---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

Re: linux-next build error (7)

[Dmitry Vyukov]

On Wed, Jan 22, 2020 at 2:17 PM syzbot
<syzbot+dc92421ed22129134c0f@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:    ba0b4dfd Add linux-next specific files for 20200122
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=17caa985e00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=7b604c617a6b217c
> dashboard link: https://syzkaller.appspot.com/bug?extid=dc92421ed22129134c0f
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
>
> Unfortunately, I don't have any reproducer for this crash yet.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+dc92421ed22129134c0f@syzkaller.appspotmail.com
>
> /syzkaller/managers/upstream-linux-next-kasan-gce-root/kernel/arch/x86/platform/efi/efi_64.c:560: undefined reference to `__efi64_thunk'
> /syzkaller/managers/upstream-linux-next-kasan-gce-root/kernel/arch/x86/platform/efi/efi_64.c:902: undefined reference to `efi_uv1_memmap_phys_prolog'
> /syzkaller/managers/upstream-linux-next-kasan-gce-root/kernel/arch/x86/platform/efi/efi_64.c:921: undefined reference to `efi_uv1_memmap_phys_epilog'

There are 2 recent commits in linux-next touching this file:

commit 6616face70e25c80420539075a943ac1bc9b990c
Date:   Wed Jan 22 09:12:37 2020 +1100
    x86: mm+efi: convert ptdump_walk_pgd_level() to take a mm_struct

commit 3cc028619e284188cdde652631e1c3c5a83692b9
Date:   Sat Jan 18 17:57:03 2020 +0100
    efi/x86: avoid KASAN false positives when accessing the 1: 1 mapping

Not sure which one is this. But linux-next is build broken.

Re: linux-next build error (7)

[Ard Biesheuvel]

On Wed, 22 Jan 2020 at 15:24, Dmitry Vyukov <dvyukov@google.com> wrote:
>
> On Wed, Jan 22, 2020 at 2:17 PM syzbot
> <syzbot+dc92421ed22129134c0f@syzkaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:    ba0b4dfd Add linux-next specific files for 20200122
> > git tree:       linux-next
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17caa985e00000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=7b604c617a6b217c
> > dashboard link: https://syzkaller.appspot.com/bug?extid=dc92421ed22129134c0f
> > compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> >
> > Unfortunately, I don't have any reproducer for this crash yet.
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+dc92421ed22129134c0f@syzkaller.appspotmail.com
> >
> > /syzkaller/managers/upstream-linux-next-kasan-gce-root/kernel/arch/x86/platform/efi/efi_64.c:560: undefined reference to `__efi64_thunk'
> > /syzkaller/managers/upstream-linux-next-kasan-gce-root/kernel/arch/x86/platform/efi/efi_64.c:902: undefined reference to `efi_uv1_memmap_phys_prolog'
> > /syzkaller/managers/upstream-linux-next-kasan-gce-root/kernel/arch/x86/platform/efi/efi_64.c:921: undefined reference to `efi_uv1_memmap_phys_epilog'
>
> There are 2 recent commits in linux-next touching this file:
>
> commit 6616face70e25c80420539075a943ac1bc9b990c
> Date:   Wed Jan 22 09:12:37 2020 +1100
>     x86: mm+efi: convert ptdump_walk_pgd_level() to take a mm_struct
>
> commit 3cc028619e284188cdde652631e1c3c5a83692b9
> Date:   Sat Jan 18 17:57:03 2020 +0100
>     efi/x86: avoid KASAN false positives when accessing the 1: 1 mapping
>
> Not sure which one is this. But linux-next is build broken.

Does this help?

https://lore.kernel.org/linux-efi/20200121093912.5246-1-ardb@kernel.org/