[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAD-N9QUK-wHnXaWkUiwOLFaQH_P+aHCC79UkB7Zs9OuB93dxfg@mail.gmail.com>
Date: Thu, 21 Jan 2021 12:11:55 +0800
From: 慕冬亮 <mudongliangabcd@...il.com>
To: bjorn.andersson@...aro.org, davem@...emloft.net, kuba@...nel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
manivannan.sadhasivam@...aro.org, netdev@...r.kernel.org,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: "WARNING: refcount bug in qrtr_node_lookup" and "WARNING: refcount
bug in qrtr_recvmsg" should share the same root cause
Dear kernel developers,
I found that on the syzbot dashboard, “WARNING: refcount bug in
qrtr_node_lookup”[1] and "WARNING: refcount bug in qrtr_recvmsg"[2]
should share the same root cause.
The reasons for the above statement:
1) the stack trace is the same, and this title difference is due to
the inline property of "qrtr_node_lookup";
2) their PoCs are the same as each other;
If you can have any issues with this statement or our information is
useful to you, please let us know. Thanks very much.
[1] “WARNING: refcount bug in qrtr_node_lookup” -
https://syzkaller.appspot.com/bug?id=e10e2fe9023e90256a35bfd34c181910bf7a874d
[2] “WARNING: refcount bug in qrtr_recvmsg” -
https://syzkaller.appspot.com/bug?id=6532173a22405c4e16c79f35609b71a0e19e29ae
--
My best regards to you.
No System Is Safe!
Dongliang Mu
Powered by blists - more mailing lists