From: syzbot <syzbot+4925d60532bf4c399608@syzkaller.appspotmail.com>
To: a@unstable.cc, akpm@linux-foundation.org, alex.aring@gmail.com,
allison@lohutok.net, andrew@lunn.ch, andy@greyhouse.net,
ap420073@gmail.com, aryabinin@virtuozzo.com, ast@domdv.de,
b.a.t.m.a.n@lists.open-mesh.org,
bridge@lists.linux-foundation.org, christophe.leroy@c-s.fr,
cleech@redhat.com, daniel@iogearbox.net, davem@davemloft.net,
dja@axtens.net, dsa@cumulusnetworks.com, dvyukov@google.com,
edumazet@google.com, f.fainelli@gmail.com, fw@strlen.de,
glider@google.com, gor@linux.ibm.com, gregkh@linuxfoundation.org,
gustavo@embeddedor.com, gvaradar@cisco.com,
haiyangz@microsoft.com, hdanton@sina.com, idosch@mellanox.com,
info@metux.net, j.vosburgh@gmail.com, j@w1.fi,
jakub.kicinski@netronome.com, jhs@mojatatu.com, jiri@resnulli.us,
johan.hedberg@gmail.com, johannes.berg@intel.com,
jwi@linux.ibm.com, kasan-dev@googlegroups.com,
kstewart@linuxfoundation.org, kvalo@codeaurora.org,
kys@microsoft.com, lariel@mellanox.com, linmiaohe@huawei.com,
linux-bluetooth@vger.kernel.org, linux-hams@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-ppp@vger.kernel.org
Subject: Re: BUG: sleeping function called from invalid context in __alloc_pages_nodemask
Date: Sun, 01 Dec 2019 20:07:01 -0800 [thread overview]
Message-ID: <000000000000293e9f0598b0b69d@google.com> (raw)
In-Reply-To: <000000000000c280ba05988b6242@google.com>
syzbot has bisected this bug to:
commit ab92d68fc22f9afab480153bd82a20f6e2533769
Author: Taehee Yoo <ap420073@gmail.com>
Date: Mon Oct 21 18:47:51 2019 +0000
net: core: add generic lockdep keys
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15769712e00000
start commit: 419593da Add linux-next specific files for 20191129
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=17769712e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=13769712e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7c04b0959e75c206
dashboard link: https://syzkaller.appspot.com/bug?extid=4925d60532bf4c399608
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16148e9ce00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12a1f786e00000
Reported-by: syzbot+4925d60532bf4c399608@syzkaller.appspotmail.com
Fixes: ab92d68fc22f ("net: core: add generic lockdep keys")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+4925d60532bf4c399608@syzkaller.appspotmail.com>
To: a@unstable.cc, akpm@linux-foundation.org, alex.aring@gmail.com,
allison@lohutok.net, andrew@lunn.ch, andy@greyhouse.net,
ap420073@gmail.com, aryabinin@virtuozzo.com, ast@domdv.de,
b.a.t.m.a.n@lists.open-mesh.org,
bridge@lists.linux-foundation.org, christophe.leroy@c-s.fr,
cleech@redhat.com, daniel@iogearbox.net, davem@davemloft.net,
dja@axtens.net, dsa@cumulusnetworks.com, dvyukov@google.com,
edumazet@google.com, f.fainelli@gmail.com, fw@strlen.de,
glider@google.com, gor@linux.ibm.com, gregkh@linuxfoundation.org,
gustavo@embeddedor.com, gvaradar@cisco.com,
haiyangz@microsoft.com, hdanton@sina.com, idosch@mellanox.com,
info@metux.net, j.vosburgh@gmail.com, j@w1.fi,
jakub.kicinski@netronome.com, jhs@mojatatu.com, jiri@resnulli.us,
johan.hedberg@gmail.com, johannes.berg@intel.com,
jwi@linux.ibm.com, kasan-dev@googlegroups.com,
kstewart@linuxfoundation.org, kvalo@codeaurora.org,
kys@microsoft.com, lariel@mellanox.com, linmiaohe@huawei.com,
linux-bluetooth@vger.kernel.org, linux-hams@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-ppp@vger.kernel.org
Subject: Re: [Bridge] BUG: sleeping function called from invalid context in __alloc_pages_nodemask
Date: Sun, 01 Dec 2019 20:07:01 -0800 [thread overview]
Message-ID: <000000000000293e9f0598b0b69d@google.com> (raw)
In-Reply-To: <000000000000c280ba05988b6242@google.com>
syzbot has bisected this bug to:
commit ab92d68fc22f9afab480153bd82a20f6e2533769
Author: Taehee Yoo <ap420073@gmail.com>
Date: Mon Oct 21 18:47:51 2019 +0000
net: core: add generic lockdep keys
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15769712e00000
start commit: 419593da Add linux-next specific files for 20191129
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=17769712e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=13769712e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7c04b0959e75c206
dashboard link: https://syzkaller.appspot.com/bug?extid=4925d60532bf4c399608
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16148e9ce00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12a1f786e00000
Reported-by: syzbot+4925d60532bf4c399608@syzkaller.appspotmail.com
Fixes: ab92d68fc22f ("net: core: add generic lockdep keys")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+4925d60532bf4c399608@syzkaller.appspotmail.com>
To: a@unstable.cc, akpm@linux-foundation.org, alex.aring@gmail.com,
allison@lohutok.net, andrew@lunn.ch, andy@greyhouse.net,
ap420073@gmail.com, aryabinin@virtuozzo.com, ast@domdv.de,
b.a.t.m.a.n@lists.open-mesh.org,
bridge@lists.linux-foundation.org, christophe.leroy@c-s.fr,
cleech@redhat.com, daniel@iogearbox.net, davem@davemloft.net,
dja@axtens.net, dsa@cumulusnetworks.com, dvyukov@google.com,
edumazet@google.com, f.fainelli@gmail.com, fw@strlen.de,
glider@google.com, gor@linux.ibm.com, gregkh@linuxfoundation.org,
gustavo@embeddedor.com, gvaradar@cisco.com,
haiyangz@microsoft.com, hdanton@sina.com, idosch@mellanox.com,
info@metux.net, j.vosburgh@gmail.com, j@w1.fi,
jakub.kicinski@netronome.com, jhs@mojatatu.com, jiri@resnulli.us,
johan.hedberg@gmail.com, johannes.berg@intel.com,
jwi@linux.ibm.com, kasan-dev@googlegroups.com,
kstewart@linuxfoundation.org, kvalo@codeaurora.org,
kys@microsoft.com, lariel@mellanox.com, linmiaohe@huawei.com,
linux-bluetooth@vger.kernel.org, linux-hams@vger.kernel.org,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-ppp@vger.kernel.org
Subject: Re: BUG: sleeping function called from invalid context in __alloc_pages_nodemask
Date: Mon, 02 Dec 2019 04:07:01 +0000 [thread overview]
Message-ID: <000000000000293e9f0598b0b69d@google.com> (raw)
In-Reply-To: <000000000000c280ba05988b6242@google.com>
syzbot has bisected this bug to:
commit ab92d68fc22f9afab480153bd82a20f6e2533769
Author: Taehee Yoo <ap420073@gmail.com>
Date: Mon Oct 21 18:47:51 2019 +0000
net: core: add generic lockdep keys
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x\x15769712e00000
start commit: 419593da Add linux-next specific files for 20191129
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x\x17769712e00000
console output: https://syzkaller.appspot.com/x/log.txt?x\x13769712e00000
kernel config: https://syzkaller.appspot.com/x/.config?x|04b0959e75c206
dashboard link: https://syzkaller.appspot.com/bug?extidI25d60532bf4c399608
syz repro: https://syzkaller.appspot.com/x/repro.syz?x\x16148e9ce00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x\x12a1f786e00000
Reported-by: syzbot+4925d60532bf4c399608@syzkaller.appspotmail.com
Fixes: ab92d68fc22f ("net: core: add generic lockdep keys")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-12-02 4:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 7:35 BUG: sleeping function called from invalid context in __alloc_pages_nodemask syzbot
2019-11-30 7:57 ` Dmitry Vyukov
2019-11-30 12:48 ` Tetsuo Handa
2019-11-30 13:44 ` Uladzislau Rezki
2019-12-01 11:22 ` syzbot
2019-12-01 15:11 ` syzbot
2019-12-02 4:07 ` syzbot [this message]
2019-12-02 4:07 ` syzbot
2019-12-02 4:07 ` [Bridge] " syzbot
-- strict thread matches above, loose matches on Subject: below --
2019-11-30 8:32 Hillf Danton
2019-11-30 11:50 ` Tetsuo Handa
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=000000000000293e9f0598b0b69d@google.com \
--to=syzbot+4925d60532bf4c399608@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=akpm@linux-foundation.org \
--cc=alex.aring@gmail.com \
--cc=allison@lohutok.net \
--cc=andrew@lunn.ch \
--cc=andy@greyhouse.net \
--cc=ap420073@gmail.com \
--cc=aryabinin@virtuozzo.com \
--cc=ast@domdv.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bridge@lists.linux-foundation.org \
--cc=christophe.leroy@c-s.fr \
--cc=cleech@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dja@axtens.net \
--cc=dsa@cumulusnetworks.com \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=fw@strlen.de \
--cc=glider@google.com \
--cc=gor@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=gvaradar@cisco.com \
--cc=haiyangz@microsoft.com \
--cc=hdanton@sina.com \
--cc=idosch@mellanox.com \
--cc=info@metux.net \
--cc=j.vosburgh@gmail.com \
--cc=j@w1.fi \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=johan.hedberg@gmail.com \
--cc=johannes.berg@intel.com \
--cc=jwi@linux.ibm.com \
--cc=kasan-dev@googlegroups.com \
--cc=kstewart@linuxfoundation.org \
--cc=kvalo@codeaurora.org \
--cc=kys@microsoft.com \
--cc=lariel@mellanox.com \
--cc=linmiaohe@huawei.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-ppp@vger.kernel.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.