From: javi.merino@arm.com (Javi Merino)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: pl330: fix null pointer dereference in pl330_chan_ctrl()
Date: Wed, 08 Feb 2012 13:59:31 +0000 [thread overview]
Message-ID: <4F327FC3.3030209@arm.com> (raw)
In-Reply-To: <20120113130222.GU1068@n2100.arm.linux.org.uk>
On 13/01/12 13:02, Russell King - ARM Linux wrote:
> On Fri, Jan 13, 2012 at 12:36:31PM +0000, Mans Rullgard wrote:
>> This fixes the thrd->req_running field being accessed before thrd
>> is checked for null. The error was introduced in abb959f.
>>
>> Signed-off-by: Mans Rullgard <mans.rullgard@linaro.org>
>
> I don't know what's happening with the PL330 driver, but there's patches
> around to remove this file and merge it with the DMA engine driver.
The PL330 merge didn't happen in the 3.3 merge window and I can't see it
in linux-next, so linux 3.3 will ship with the driver still split in
arch/arm/common/pl330.c and drivers/dma/pl330.c . I think this patch
should be part of linux 3.3 (and you should add "Cc: stable at kernel.org"
so that it's included in the next 3.2 stable release).
Unless somebody thinks otherwise, Mans, can you please submit it to
rmk's patch tracking system?
http://www.arm.linux.org.uk/developer/patches/
Thanks,
Javi
next prev parent reply other threads:[~2012-02-08 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 12:36 [PATCH] ARM: pl330: fix null pointer dereference in pl330_chan_ctrl() Mans Rullgard
2012-01-13 12:36 ` Mans Rullgard
2012-01-13 13:02 ` Russell King - ARM Linux
2012-01-13 13:02 ` Russell King - ARM Linux
2012-02-08 13:59 ` Javi Merino [this message]
2012-02-09 0:44 ` Boojin Kim
2012-02-09 10:35 ` Javi Merino
2012-01-13 13:48 ` Javi Merino
2012-01-13 13:48 ` Javi Merino
2012-01-13 19:46 ` Mans Rullgard
2012-01-13 19:46 ` Mans Rullgard
2012-01-14 21:53 ` Sergei Shtylyov
2012-01-14 21:53 ` Sergei Shtylyov
2012-01-25 12:11 ` [PATCH] DMA: " Mans Rullgard
2012-01-25 12:11 ` Mans Rullgard
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=4F327FC3.3030209@arm.com \
--to=javi.merino@arm.com \
--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 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.