From: Mark Brown <broonie@kernel.org>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: linux-spi@vger.kernel.org, Fugang Duan <B38611@freescale.com>,
Gao Pan <pandy.gao@nxp.com>
Subject: Re: [PATCH] spi: lpspi: Avoid potential use-after-free in probe()
Date: Tue, 12 Mar 2024 13:46:08 +0000 [thread overview]
Message-ID: <87c1553e-355e-4249-9f1d-3f5140842c6c@sirena.org.uk> (raw)
In-Reply-To: <20240312112050.2503643-1-alexander.sverdlin@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On Tue, Mar 12, 2024 at 12:20:48PM +0100, A. Sverdlin wrote:
> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000070
> ...
> Call trace:
> kernfs_find_ns
> kernfs_find_and_get_ns
> sysfs_remove_group
> sysfs_remove_groups
> device_remove_attrs
> device_del
> spi_unregister_controller
> devm_spi_unregister
> release_nodes
> devres_release_all
> really_probe
> driver_probe_device
> __device_attach_driver
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:[~2024-03-12 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 11:20 [PATCH] spi: lpspi: Avoid potential use-after-free in probe() A. Sverdlin
2024-03-12 13:46 ` Mark Brown [this message]
2024-03-12 16:57 ` Mark Brown
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=87c1553e-355e-4249-9f1d-3f5140842c6c@sirena.org.uk \
--to=broonie@kernel.org \
--cc=B38611@freescale.com \
--cc=alexander.sverdlin@siemens.com \
--cc=linux-spi@vger.kernel.org \
--cc=pandy.gao@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 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.