public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: grinberg@compulab•co.il (Igor Grinberg)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: OMAP: mcbsp: Fix possible memory corruption
Date: Mon, 12 Dec 2011 13:57:07 +0200	[thread overview]
Message-ID: <4EE5EC13.40901@compulab.co.il> (raw)
In-Reply-To: <4EE5E3F4.6060701@bitmer.com>

On 12/12/11 13:22, Jarkko Nikula wrote:
> Hi
> 
> On 12/12/2011 12:23 PM, Igor Grinberg wrote:
>> On 12/12/11 10:38, Jarkko Nikula wrote:
>>> Commits 09d28d ("ARM: OMAP: mcbsp: Start generalize omap2_mcbsp_set_clks_src")
>>> and 7bc0c4 ("ARM: OMAP: mcbsp: Start generalize signal muxing functions")
>>> incorrectly set two struct omap_mcbsp_platform_data fields after
>>> omap_device_build_ss and kfree calls.
>>>
>>> Fix this by moving these pdata assignments before those calls.
>>>
>>> Signed-off-by: Jarkko Nikula <jarkko.nikula@bitmer•com>
>>> Reported-by: neilb at suse.de
>> Perhaps, should be:
>> Reported-by: NeilBrown <neilb@suse•de>
>> and
>> Cc: <stable@vger•kernel.org>	[3.1]
>> as for below.
>>> ---
>>> For 3.2, 3.1 is ok.
>>> ---
> No need to cc stable since the issue is not in stable kernels.

Ah, so I've misunderstood what was that about...
So it has been introduced in 3.2-rc cycle.
Ok. Then now it is the perfect time to fix this ;)


-- 
Regards,
Igor.

  reply	other threads:[~2011-12-12 11:57 UTC|newest]

Thread overview: 8+ 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 10:23   ` Igor Grinberg
2011-12-12 11:22     ` Jarkko Nikula
2011-12-12 11:57       ` Igor Grinberg [this message]
2011-12-12 18:33         ` Tony Lindgren
2011-12-14 20:50           ` Ramirez Luna, Omar
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=4EE5EC13.40901@compulab.co.il \
    --to=grinberg@compulab$(echo .)co.il \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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