From: syzbot <syzbot+438a5abd4f53adb1c073@syzkaller•appspotmail.com>
To: davem@davemloft•net, edumazet@google•com, jmaloy@redhat•com,
jon.maloy@ericsson•com, kuba@kernel•org,
linux-kernel@vger•kernel.org, linux-mm@kvack•org,
netdev@vger•kernel.org, syzkaller-bugs@googlegroups•com,
tipc-discussion@lists•sourceforge.net, ying.xue@windriver•com
Subject: Re: BUG: unable to handle kernel paging request in free_block (5)
Date: Fri, 14 Aug 2020 15:59:06 -0700 [thread overview]
Message-ID: <00000000000031c95f05acde5eda@google.com> (raw)
In-Reply-To: <000000000000c770710586c6fc92@google.com>
syzbot suspects this issue was fixed by commit:
commit 1378817486d6860f6a927f573491afe65287abf1
Author: Eric Dumazet <edumazet@google•com>
Date: Thu May 21 18:29:58 2020 +0000
tipc: block BH before using dst_cache
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1537694a900000
start commit: e6986423 socket: fix compat SO_RCVTIMEO_NEW/SO_SNDTIMEO_NEW
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=4fb64439e07a1ec0
dashboard link: https://syzkaller.appspot.com/bug?extid=438a5abd4f53adb1c073
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12adddbf200000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: tipc: block BH before using dst_cache
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-08-14 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 5:08 BUG: unable to handle kernel paging request in free_block (5) syzbot
2019-04-18 9:59 ` syzbot
2020-08-14 22:59 ` syzbot [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=00000000000031c95f05acde5eda@google.com \
--to=syzbot+438a5abd4f53adb1c073@syzkaller$(echo .)appspotmail.com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jmaloy@redhat$(echo .)com \
--cc=jon.maloy@ericsson$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=tipc-discussion@lists$(echo .)sourceforge.net \
--cc=ying.xue@windriver$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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