From: Mark Brown <broonie@kernel.org>
To: Clark Wang <xiaoning.wang@nxp.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/4] spi: lpspi: Fix kernel warning dump when probe fail after calling spi_register
Date: Mon, 27 Jul 2020 12:11:09 +0100 [thread overview]
Message-ID: <20200727111109.GB6275@sirena.org.uk> (raw)
In-Reply-To: <20200727031448.31661-2-xiaoning.wang@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On Mon, Jul 27, 2020 at 11:14:46AM +0800, Clark Wang wrote:
> Calling devm_spi_register_controller() too early will cause problem.
> When probe failed occurs after calling devm_spi_register_controller(),
> the call of spi_controller_put() will trigger the following warning dump.
>
> [ 2.092138] ------------[ cut here ]------------
> [ 2.096876] kernfs: can not remove 'uevent', no directory
> [ 2.102440] WARNING: CPU: 0 PID: 181 at fs/kernfs/dir.c:1503 kernfs_remove_by_name_ns+0xa0/0xb0
> [ 2.111142] Modules linked in:
> [ 2.114207] CPU: 0 PID: 181 Comm: kworker/0:7 Not tainted 5.4.24-05024-g775c6e8a738c-dirty #1314
> [ 2.122991] Hardware name: Freescale i.MX8DXL EVK (DT)
> [ 2.128141] Workqueue: events deferred_probe_work_func
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative (it often is
for search engines if nothing else) then it's usually better to pull out
the relevant sections.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-27 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 3:14 [PATCH V2 0/4] Some bug fix for lpspi Clark Wang
2020-07-27 3:14 ` [PATCH V2 1/4] spi: lpspi: Fix kernel warning dump when probe fail after calling spi_register Clark Wang
2020-07-27 11:11 ` Mark Brown [this message]
2020-07-31 2:01 ` [EXT] " Clark Wang
2020-07-27 3:14 ` [PATCH V2 2/4] spi: lpspi: remove unused fsl_lpspi->chipselect Clark Wang
2020-07-27 3:14 ` [PATCH V2 3/4] spi: lpspi: fix using CS discontinuously on i.MX8DXLEVK Clark Wang
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=20200727111109.GB6275@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=xiaoning.wang@nxp.com \
/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;
as well as URLs for NNTP newsgroup(s).