bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: syzbot <syzbot+710043c5d1d5b5013bc7@syzkaller.appspotmail.com>
Cc: ast@kernel.org, bpf@vger.kernel.org, davem@davemloft.net,
	hawk@kernel.org, jakub.kicinski@netronome.com,
	john.fastabend@gmail.com, kafai@fb.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
	yhs@fb.com
Subject: Re: BUG: unable to handle kernel paging request in is_bpf_text_address
Date: Fri, 18 Oct 2019 15:01:28 +0200	[thread overview]
Message-ID: <20191018130128.GC26267@pc-63.home> (raw)
In-Reply-To: <000000000000410cbb059528d6f7@google.com>

On Thu, Oct 17, 2019 at 10:45:09PM -0700, syzbot wrote:
> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    283ea345 coccinelle: api/devm_platform_ioremap_resource: r..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=122f199b600000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=f0a8b0a0736a2ac1
> dashboard link: https://syzkaller.appspot.com/bug?extid=710043c5d1d5b5013bc7
> compiler:       clang version 9.0.0 (/home/glider/llvm/clang
> 80fee25776c2fb61e74c1ecb1a523375c2500b69)
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=142676bb600000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11a2cebb600000

I'll take a look, thanks!

      parent reply	other threads:[~2019-10-18 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  5:45 BUG: unable to handle kernel paging request in is_bpf_text_address syzbot
2019-10-18 10:27 ` syzbot
2019-10-18 13:01 ` Daniel Borkmann [this message]

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=20191018130128.GC26267@pc-63.home \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=hawk@kernel.org \
    --cc=jakub.kicinski@netronome.com \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=syzbot+710043c5d1d5b5013bc7@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).