From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+5b0d0de84d6c65b8dd2b@syzkaller.appspotmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: upstream build error (11)
Date: Sat, 9 Jan 2021 21:41:23 +0100 [thread overview]
Message-ID: <CACT4Y+b0-Rw+_aNtGnbwKj7FFM2yKDAsPFO3XP5DnirCRCbbNg@mail.gmail.com> (raw)
In-Reply-To: <0000000000001bc23b05b2b6fd8a@google.com>
On Wed, Oct 28, 2020 at 9:31 AM syzbot
<syzbot+5b0d0de84d6c65b8dd2b@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 4d09c1d9 Merge tag 'devicetree-fixes-for-5.10-1' of git://..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1615899c500000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a5c844e56cc50cdb
> dashboard link: https://syzkaller.appspot.com/bug?extid=5b0d0de84d6c65b8dd2b
> compiler: gcc (GCC) 10.1.0-syz 20200507
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+5b0d0de84d6c65b8dd2b@syzkaller.appspotmail.com
>
> mm/process_vm_access.c:277:5: error: implicit declaration of function 'in_compat_syscall'; did you mean 'in_ia32_syscall'? [-Werror=implicit-function-declaration]
Other build failures are piling behind this.
#syz fix: mm/process_vm_access: Add missing #include <linux/compat.h>
next prev parent reply other threads:[~2021-01-09 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 8:31 syzbot
2021-01-09 20:41 ` Dmitry Vyukov [this message]
2021-01-09 22:34 ` Andrew Morton
2021-01-10 8:44 ` Dmitry Vyukov
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=CACT4Y+b0-Rw+_aNtGnbwKj7FFM2yKDAsPFO3XP5DnirCRCbbNg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+5b0d0de84d6c65b8dd2b@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