public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: dapm: delete dapm_kcontrol_data paths entry before freeing
Date: Mon, 4 Jun 2018 11:55:10 +0100	[thread overview]
Message-ID: <e37bf559-b040-db34-6273-d4f8ea1e2284@linaro.org> (raw)
In-Reply-To: <20180604104541.GB7536@sirena.org.uk>



On 04/06/18 11:45, Mark Brown wrote:
> On Fri, Jun 01, 2018 at 11:53:34PM +0100, Srinivas Kandagatla wrote:
> 
>> Below is the kernel BUG with SLAB Poisoning
> 
>> =============================================================================
>> BUG kmalloc-128 (Tainted: G        W        ): Poison overwritten
>> -----------------------------------------------------------------------------
>>
>> Disabling lock debugging due to kernel taint
>> INFO: 0xffff80003cf1c310-0xffff80003cf1c31f. First byte 0x10 instead of 0x6b
>> INFO: Allocated in dapm_kcontrol_data_alloc.isra.37+0x34/0x2a8 age=6929 cpu=0 pid=50
>>   __slab_alloc.isra.24+0x24/0x38
>>   kmem_cache_alloc+0x190/0x1d8
> 
> 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.
I agree, Do you want me to resend the patch removing irrelevant sections 
in log?

thanks,
srini
> 

  reply	other threads:[~2018-06-04 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 22:53 [PATCH] ASoC: dapm: delete dapm_kcontrol_data paths entry before freeing Srinivas Kandagatla
2018-06-04 10:45 ` Mark Brown
2018-06-04 10:55   ` Srinivas Kandagatla [this message]
2018-06-04 11:00     ` 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=e37bf559-b040-db34-6273-d4f8ea1e2284@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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