All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Ramirez Luna, Omar" <omar.ramirez@ti.com>
Cc: Igor Grinberg <grinberg@compulab.co.il>,
	Jarkko Nikula <jarkko.nikula@bitmer.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	neilb@suse.de
Subject: Re: [PATCH] ARM: OMAP: mcbsp: Fix possible memory corruption
Date: Wed, 14 Dec 2011 13:54:24 -0800	[thread overview]
Message-ID: <20111214215424.GO32251@atomide.com> (raw)
In-Reply-To: <CAB-zwWgkme_SPDMOkT9Xuv2yYdpVAGoNGGRN95vNWh7hb91JSw@mail.gmail.com>

* Ramirez Luna, Omar <omar.ramirez@ti.com> [111214 12:18]:
> On Mon, Dec 12, 2011 at 12:33 PM, Tony Lindgren <tony@atomide.com> wrote:
> > Applying into fixes.
> 
> FWIW, I was bisecting this issue, the patch fixes the following slab
> corruptions on boot log:

Thanks for the info, I've sent the pull request for the two patches
in fixes branch.

Regards,

Tony

 
> hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
> hw-breakpoint: maximum watchpoint size is 4 bytes.
> Slab corruption: size-32 start=eea66740, len=32
> 010: d8 9d 02 c0 04 9d 02 c0 6b 6b 6b 6b 6b 6b 6b a5  ........kkkkkkk.
> Prev obj: start=eea66720, len=32
> 000: 6f 6d 61 70 32 5f 6d 63 73 70 69 2e 31 00 5a 5a  omap2_mcspi.1.ZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Next obj: start=eea66760, len=32
> 000: 70 6f 77 65 72 00 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  power.ZZZZZZZZZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Slab corruption: size-32 start=eea66740, len=32
> 010: d8 9d 02 c0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5  ....kkkkkkkkkkk.
> Prev obj: start=eea66720, len=32
> 000: 6f 6d 61 70 32 5f 6d 63 73 70 69 2e 31 00 5a 5a  omap2_mcspi.1.ZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Next obj: start=eea66760, len=32
> 000: 70 6f 77 65 72 00 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  power.ZZZZZZZZZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Slab corruption: size-32 start=eea66740, len=32
> 010: d8 9d 02 c0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5  ....kkkkkkkkkkk.
> Prev obj: start=eea66720, len=32
> 000: 6f 6d 61 70 32 5f 6d 63 73 70 69 2e 31 00 5a 5a  omap2_mcspi.1.ZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Next obj: start=eea66760, len=32
> 000: 70 6f 77 65 72 00 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  power.ZZZZZZZZZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Slab corruption: size-32 start=eea66740, len=32
> 010: d8 9d 02 c0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5  ....kkkkkkkkkkk.
> Prev obj: start=eea66720, len=32
> 000: 6f 6d 61 70 32 5f 6d 63 73 70 69 2e 31 00 5a 5a  omap2_mcspi.1.ZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Next obj: start=eea66760, len=32
> 000: 70 6f 77 65 72 00 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  power.ZZZZZZZZZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> OMAP DMA hardware revision 0.0
> ...
> 
> Regards,
> 
> Omar

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP: mcbsp: Fix possible memory corruption
Date: Wed, 14 Dec 2011 13:54:24 -0800	[thread overview]
Message-ID: <20111214215424.GO32251@atomide.com> (raw)
In-Reply-To: <CAB-zwWgkme_SPDMOkT9Xuv2yYdpVAGoNGGRN95vNWh7hb91JSw@mail.gmail.com>

* Ramirez Luna, Omar <omar.ramirez@ti.com> [111214 12:18]:
> On Mon, Dec 12, 2011 at 12:33 PM, Tony Lindgren <tony@atomide.com> wrote:
> > Applying into fixes.
> 
> FWIW, I was bisecting this issue, the patch fixes the following slab
> corruptions on boot log:

Thanks for the info, I've sent the pull request for the two patches
in fixes branch.

Regards,

Tony

 
> hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
> hw-breakpoint: maximum watchpoint size is 4 bytes.
> Slab corruption: size-32 start=eea66740, len=32
> 010: d8 9d 02 c0 04 9d 02 c0 6b 6b 6b 6b 6b 6b 6b a5  ........kkkkkkk.
> Prev obj: start=eea66720, len=32
> 000: 6f 6d 61 70 32 5f 6d 63 73 70 69 2e 31 00 5a 5a  omap2_mcspi.1.ZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Next obj: start=eea66760, len=32
> 000: 70 6f 77 65 72 00 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  power.ZZZZZZZZZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Slab corruption: size-32 start=eea66740, len=32
> 010: d8 9d 02 c0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5  ....kkkkkkkkkkk.
> Prev obj: start=eea66720, len=32
> 000: 6f 6d 61 70 32 5f 6d 63 73 70 69 2e 31 00 5a 5a  omap2_mcspi.1.ZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Next obj: start=eea66760, len=32
> 000: 70 6f 77 65 72 00 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  power.ZZZZZZZZZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Slab corruption: size-32 start=eea66740, len=32
> 010: d8 9d 02 c0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5  ....kkkkkkkkkkk.
> Prev obj: start=eea66720, len=32
> 000: 6f 6d 61 70 32 5f 6d 63 73 70 69 2e 31 00 5a 5a  omap2_mcspi.1.ZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Next obj: start=eea66760, len=32
> 000: 70 6f 77 65 72 00 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  power.ZZZZZZZZZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Slab corruption: size-32 start=eea66740, len=32
> 010: d8 9d 02 c0 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5  ....kkkkkkkkkkk.
> Prev obj: start=eea66720, len=32
> 000: 6f 6d 61 70 32 5f 6d 63 73 70 69 2e 31 00 5a 5a  omap2_mcspi.1.ZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> Next obj: start=eea66760, len=32
> 000: 70 6f 77 65 72 00 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  power.ZZZZZZZZZZ
> 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a a5  ZZZZZZZZZZZZZZZ.
> OMAP DMA hardware revision 0.0
> ...
> 
> Regards,
> 
> Omar

  reply	other threads:[~2011-12-14 21:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12  8:36 [PATCH] ARM: OMAP: mcbsp: Fix possible memory corruption Jarkko Nikula
2011-12-12  8:38 ` Jarkko Nikula
2011-12-12  8:38   ` Jarkko Nikula
2011-12-12 10:23   ` Igor Grinberg
2011-12-12 10:23     ` Igor Grinberg
2011-12-12 11:22     ` Jarkko Nikula
2011-12-12 11:22       ` Jarkko Nikula
2011-12-12 11:57       ` Igor Grinberg
2011-12-12 11:57         ` Igor Grinberg
2011-12-12 18:33         ` Tony Lindgren
2011-12-12 18:33           ` Tony Lindgren
2011-12-14 20:50           ` Ramirez Luna, Omar
2011-12-14 20:50             ` Ramirez Luna, Omar
2011-12-14 21:54             ` Tony Lindgren [this message]
2011-12-14 21:54               ` Tony Lindgren

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=20111214215424.GO32251@atomide.com \
    --to=tony@atomide.com \
    --cc=grinberg@compulab.co.il \
    --cc=jarkko.nikula@bitmer.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=omar.ramirez@ti.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.