[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200601104944.GA5234@sirena.org.uk>
Date: Mon, 1 Jun 2020 11:49:44 +0100
From: Mark Brown <broonie@...nel.org>
To: John Stultz <john.stultz@...aro.org>
Cc: lkml <linux-kernel@...r.kernel.org>,
Patrick Lai <plai@...eaurora.org>,
Banajit Goswami <bgoswami@...eaurora.org>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Vinod Koul <vkoul@...nel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Stephan Gerhold <stephan@...hold.net>,
Sami Tolvanen <samitolvanen@...gle.com>,
Todd Kjos <tkjos@...gle.com>,
Alistair Delva <adelva@...gle.com>,
Amit Pundir <amit.pundir@...aro.org>,
Sumit Semwal <sumit.semwal@...aro.org>,
alsa-devel@...a-project.org
Subject: Re: [RFC][PATCH] ASoC: qcom: q6asm-dai: kCFI fix
On Fri, May 29, 2020 at 09:38:23PM +0000, John Stultz wrote:
> [ 82.585661] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000001
> [ 82.595387] Mem abort info:
> [ 82.599463] ESR = 0x96000005
> [ 82.602658] EC = 0x25: DABT (current EL), IL = 32 bits
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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists