From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hui Guo <guohui.study@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Alex Elder <elder@kernel.org>,
Aditya Garg <gargaditya08@live.com>,
Grant Grundler <grundler@chromium.org>,
Kerem Karabay <kekrby@gmail.com>,
Douglas Anderson <dianders@chromium.org>,
Oliver Neukum <oneukum@suse.com>,
Yajun Deng <yajun.deng@linux.dev>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING: refcount bug in put_device
Date: Tue, 15 Oct 2024 08:48:04 +0200 [thread overview]
Message-ID: <2024101515-helmet-stoic-1c97@gregkh> (raw)
In-Reply-To: <CAHOo4gL5BYS53rd2bJiKmL1XSg94hn0u4yCPut7NqZ0XZMNf3A@mail.gmail.com>
On Tue, Oct 15, 2024 at 02:37:47PM +0800, Hui Guo wrote:
> Hi Kernel Maintainers,
> we found a crash "WARNING: refcount bug in put_device" in upstream, we
> also have successfully reproduced it manually:
>
> HEAD Commit: 9852d85ec9d492ebef56dc5f229416c925758edc(tag 'v6.12-rc1')
> kernel config: https://raw.githubusercontent.com/androidAppGuard/KernelBugs/main/6.12.config
>
> console output:
> https://raw.githubusercontent.com/androidAppGuard/KernelBugs/main/9852d85ec9d492ebef56dc5f229416c925758edc/83e10c2b482009dbb3b32ece907dcc361978f9b9/log0
> repro report: https://raw.githubusercontent.com/androidAppGuard/KernelBugs/main/9852d85ec9d492ebef56dc5f229416c925758edc/83e10c2b482009dbb3b32ece907dcc361978f9b9/repro.report
> syz reproducer:
> https://raw.githubusercontent.com/androidAppGuard/KernelBugs/main/9852d85ec9d492ebef56dc5f229416c925758edc/83e10c2b482009dbb3b32ece907dcc361978f9b9/repro.prog
> c reproducer: https://raw.githubusercontent.com/androidAppGuard/KernelBugs/main/9852d85ec9d492ebef56dc5f229416c925758edc/83e10c2b482009dbb3b32ece907dcc361978f9b9/repro.cprog
As this is using a "fake" yealink device, odds are there's some
reference counting bug on the disconnect path that you have found. Care
to send a patch to fix it up as you can test it easily?
thanks,
greg k-h
prev parent reply other threads:[~2024-10-15 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 6:37 WARNING: refcount bug in put_device Hui Guo
2024-10-15 6:48 ` Greg Kroah-Hartman [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=2024101515-helmet-stoic-1c97@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dianders@chromium.org \
--cc=elder@kernel.org \
--cc=gargaditya08@live.com \
--cc=grundler@chromium.org \
--cc=guohui.study@gmail.com \
--cc=kekrby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=rafael@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yajun.deng@linux.dev \
/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