From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: mvebu: prevent walking off the end of group array
Date: Wed, 13 Mar 2013 18:48:34 +0100 [thread overview]
Message-ID: <5140BBF2.4050309@gmail.com> (raw)
In-Reply-To: <1363196155-1620-1-git-send-email-jason@lakedaemon.net>
On 03/13/2013 06:35 PM, Jason Cooper wrote:
> From: David Woodhouse<dwmw2@infradead.org>
>
> While investigating (ab)use of krealloc, David found this bug. It's
> unlikely to occur, but now we detect the condition and error out
> appropriately.
>
> Signed-off-by: David Woodhouse<David.Woodhouse@intel.com>
> Signed-off-by: Jason Cooper<jason@lakedaemon.net>
> ---
> David, please double check that this is as you intended. I had to hand-jam it in due to some peculiarities on my side.
>
Jason,
thanks for preparing that patch. I ll test (and Ack) asap but that will not be
before this weekend. If Thomas and Andrew ack it before me, consider it good.
Sebastian
next prev parent reply other threads:[~2013-03-13 17:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1362758331.32099.121.camel@i7.infradead.org>
[not found] ` <513AF783.6050906@gmail.com>
[not found] ` <1362855725.3690.92.camel@shinybook.infradead.org>
[not found] ` <20130309225333.GY23237@titan.lakedaemon.net>
[not found] ` <1362872371.3690.106.camel@shinybook.infradead.org>
2013-03-10 0:06 ` memory leak and other oddness in pinctrl-mvebu.c Jason Cooper
2013-03-13 16:59 ` Linus Walleij
2013-03-13 17:35 ` [PATCH] pinctrl: mvebu: prevent walking off the end of group array Jason Cooper
2013-03-13 17:47 ` Linus Walleij
2013-03-13 17:50 ` Jason Cooper
2013-03-13 18:40 ` Linus Walleij
2013-03-13 17:48 ` Sebastian Hesselbarth [this message]
2013-03-13 17:48 ` [PATCH V2] " Jason Cooper
2013-03-14 10:29 ` David Woodhouse
2013-03-16 11:44 ` [PATCH v3] " Sebastian Hesselbarth
2013-03-22 16:39 ` Jason Cooper
2013-03-27 22:06 ` Linus Walleij
2013-03-27 22:11 ` Woodhouse, David
2013-03-27 22:34 ` Linus Walleij
2013-03-28 11:08 ` Jason Cooper
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=5140BBF2.4050309@gmail.com \
--to=sebastian.hesselbarth@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).