From: syzbot <syzbot+d55757faa9b80590767b@syzkaller.appspotmail.com>
To: christophe.jaillet@wanadoo.fr, dhowells@redhat.com,
fmdefrancesco@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: null-ptr-deref Read in __free_pages
Date: Sun, 20 Mar 2022 16:38:11 -0700 [thread overview]
Message-ID: <0000000000007442a005daaedf30@google.com> (raw)
In-Reply-To: <2238978.ElGaqSPkdT@leap>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
kernel/watch_queue.c:365:13: error: invalid storage class for function '__put_watch_queue'
kernel/watch_queue.c:390:15: error: non-static declaration of 'put_watch_queue' follows static declaration
kernel/watch_queue.c:392:13: error: invalid storage class for function 'free_watch'
kernel/watch_queue.c:401:13: error: invalid storage class for function '__put_watch'
kernel/watch_queue.c:411:13: error: invalid storage class for function 'put_watch'
kernel/watch_queue.c:473:15: error: non-static declaration of 'add_watch_to_object' follows static declaration
kernel/watch_queue.c:554:15: error: non-static declaration of 'remove_watch_from_object' follows static declaration
kernel/watch_queue.c:644:15: error: non-static declaration of 'get_watch_queue' follows static declaration
kernel/watch_queue.c:664:1: error: expected declaration or statement at end of input
kernel/watch_queue.c:664: error: control reaches end of non-void function [-Werror=return-type]
Tested on:
commit: f443e374 Linux 5.17
git tree: upstream
dashboard link: https://syzkaller.appspot.com/bug?extid=d55757faa9b80590767b
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=129f0625700000
next prev parent reply other threads:[~2022-03-20 23:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 22:04 [syzbot] KASAN: null-ptr-deref Read in __free_pages syzbot
2022-03-20 23:32 ` Fabio M. De Francesco
2022-03-20 23:38 ` syzbot [this message]
2022-03-20 23:40 ` Fabio M. De Francesco
2022-03-20 23:50 ` syzbot
2022-03-21 0:28 ` Fabio M. De Francesco
2022-03-21 0:37 ` syzbot
2022-03-21 8:46 ` David Howells
2022-03-21 9:02 ` Fabio M. De Francesco
2022-03-21 9:37 ` David Howells
2022-03-21 8:24 ` David Howells
2022-03-21 8:34 ` syzbot
2022-03-21 8:43 ` Fabio M. De Francesco
2022-03-21 8:50 ` Fabio M. De Francesco
2022-03-21 11:19 ` David Howells
2022-03-21 11:30 ` syzbot
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=0000000000007442a005daaedf30@google.com \
--to=syzbot+d55757faa9b80590767b@syzkaller.appspotmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dhowells@redhat.com \
--cc=fmdefrancesco@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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