From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Zhongping Tan (谭中平)" <Zhongping.Tan@spreadtrum.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] char: misc: Init misc->list in a safe way
Date: Wed, 28 Jun 2017 07:18:15 +0200 [thread overview]
Message-ID: <20170628051815.GA4748@kroah.com> (raw)
In-Reply-To: <20170628015431.GA32195@spreadtrum.com>
On Wed, Jun 28, 2017 at 09:54:32AM +0800, Orson Zhai wrote:
> We found the device is "fm". We highly suspect that fm driver call
> misc_register twice and reinitialize list to make ->pre & ->next
> pointing to himself.
>
> Meanwhile, we checked fm driver and found nothing obviously wrong in the code.
Do you have a pointer to this driver? Is it in the kernel tree?
> Consider that this is a crash after 46 hours continuous power-on/off,
> it maybe caused by some special cases we are hard to know for now.
What would cause this driver to want to register/unregister itself? Is
it "recycling" the misc structure, or creating it new each time?
And what kernel version are you testing here?
> We think it might make some sence to add protection code into
> misc_register() at first.
To protect from "foolish" callers? Usually we fix the calling code to
not do foolish things. :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-28 5:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 9:31 [RFC PATCH] char: misc: Init misc->list in a safe way Orson Zhai
2017-06-26 10:02 ` Arnd Bergmann
2017-06-26 11:48 ` Zhongping Tan (谭中平)
2017-06-26 12:28 ` Arnd Bergmann
[not found] ` <ca76fa84d77449bf84c2f3ddf29048a0@SHMBX02.spreadtrum.com>
2017-06-26 14:10 ` 答复: " Arnd Bergmann
2017-06-27 2:02 ` Zhongping Tan (谭中平)
2017-06-27 6:29 ` Greg Kroah-Hartman
2017-06-28 1:54 ` Orson Zhai
2017-06-28 5:18 ` Greg Kroah-Hartman [this message]
2017-06-28 10:34 ` Arnd Bergmann
2017-06-28 11:21 ` Greg Kroah-Hartman
2017-06-29 6:54 ` Chunyan Zhang
2017-06-29 7:03 ` Greg Kroah-Hartman
2017-06-29 7:30 ` Chunyan Zhang
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=20170628051815.GA4748@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Zhongping.Tan@spreadtrum.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox