From: syzbot <syzbot+94cc2a66fc228b23f360@syzkaller.appspotmail.com>
To: Yong.Zhao@amd.com, airlied@linux.ie, alexander.deucher@amd.com,
amd-gfx@lists.freedesktop.org, ast@kernel.org,
bpf@vger.kernel.org, christian.koenig@amd.com, daniel@ffwll.ch,
daniel@iogearbox.net, davem@davemloft.net, david1.zhou@amd.com,
dri-devel@lists.freedesktop.org, evan.quan@amd.com,
felix.kuehling@amd.com, harry.wentland@amd.com, kafai@fb.com,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, ozeng@amd.com, ray.huang@amd.com,
rex.zhu@amd.com, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com, yong.zhao@amd.com,
yoshfuji@linux-ipv6.org
Subject: Re: WARNING: locking bug in inet_autobind
Date: Tue, 21 May 2019 20:16:01 -0700 [thread overview]
Message-ID: <0000000000008b645c058971629b@google.com> (raw)
In-Reply-To: <00000000000033a0120588fac894@google.com>
syzbot has bisected this bug to:
commit c0d9271ecbd891cdeb0fad1edcdd99ee717a655f
Author: Yong Zhao <Yong.Zhao@amd.com>
Date: Fri Feb 1 23:36:21 2019 +0000
drm/amdgpu: Delete user queue doorbell variables
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1433ece4a00000
start commit: f49aa1de Merge tag 'for-5.2-rc1-tag' of git://git.kernel.o..
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=1633ece4a00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1233ece4a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=fc045131472947d7
dashboard link: https://syzkaller.appspot.com/bug?extid=94cc2a66fc228b23f360
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=163731f8a00000
Reported-by: syzbot+94cc2a66fc228b23f360@syzkaller.appspotmail.com
Fixes: c0d9271ecbd8 ("drm/amdgpu: Delete user queue doorbell variables")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-05-22 3:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 5:46 WARNING: locking bug in inet_autobind syzbot
2019-05-21 8:31 ` syzbot
2019-05-22 3:16 ` syzbot [this message]
[not found] ` <0000000000008b645c058971629b-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2019-05-22 3:21 ` Zhao, Yong
2022-09-18 15:52 ` Tetsuo Handa
2022-09-18 18:25 ` Boqun Feng
2022-09-19 5:02 ` Tetsuo Handa
2022-09-27 13:00 ` Tetsuo Handa
2022-11-22 18:02 ` Jakub Sitnicki
2022-12-29 6:26 ` [syzbot] " syzbot
2023-01-03 15:39 ` Felix Kuehling
2023-01-03 16:05 ` Waiman Long
2023-01-03 16:20 ` Felix Kuehling
2023-01-03 22:07 ` Tetsuo Handa
2023-01-03 22:07 ` Tetsuo Handa
2023-01-03 22:07 ` Tetsuo Handa
2023-01-03 22:12 ` Eric Dumazet
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=0000000000008b645c058971629b@google.com \
--to=syzbot+94cc2a66fc228b23f360@syzkaller.appspotmail.com \
--cc=Yong.Zhao@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=david1.zhou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=evan.quan@amd.com \
--cc=felix.kuehling@amd.com \
--cc=harry.wentland@amd.com \
--cc=kafai@fb.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ozeng@amd.com \
--cc=ray.huang@amd.com \
--cc=rex.zhu@amd.com \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.