From: Mark Brown <broonie@kernel.org>
To: YueHaibing <yuehaibing@huawei.com>
Cc: axel.lin@ingics.com, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, albeu@free.fr,
lorenzo.bianconi@redhat.com
Subject: Re: [PATCH] spi: bitbang: Fix NULL pointer dereference in spi_unregister_master
Date: Thu, 16 May 2019 10:51:48 +0100 [thread overview]
Message-ID: <20190516095148.GA5598@sirena.org.uk> (raw)
In-Reply-To: <20190516075656.25880-1-yuehaibing@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
On Thu, May 16, 2019 at 03:56:56PM +0800, YueHaibing wrote:
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014
> Call Trace:
> dump_stack+0xa9/0x10e
> ? __list_del_entry_valid+0x45/0xd0
> ? __list_del_entry_valid+0x45/0xd0
> __kasan_report+0x171/0x18d
> ? __list_del_entry_valid+0x45/0xd0
> kasan_report+0xe/0x20
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 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:[~2019-05-16 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 7:56 [PATCH] spi: bitbang: Fix NULL pointer dereference in spi_unregister_master YueHaibing
2019-05-16 8:25 ` Geert Uytterhoeven
2019-05-16 8:36 ` Axel Lin
2019-05-16 9:43 ` Mukesh Ojha
2019-05-16 9:51 ` Mark Brown [this message]
2019-05-16 13:27 ` YueHaibing
2019-05-16 10:17 ` Applied "spi: bitbang: Fix NULL pointer dereference in spi_unregister_master" to the spi tree 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=20190516095148.GA5598@sirena.org.uk \
--to=broonie@kernel.org \
--cc=albeu@free.fr \
--cc=axel.lin@ingics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=yuehaibing@huawei.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