From: Paul Mundt <lethal@linux-sh.org>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: linux-sh@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sh: Make sure indexes are positive
Date: Wed, 04 Nov 2009 03:15:40 +0000 [thread overview]
Message-ID: <20091104031540.GF12841@linux-sh.org> (raw)
In-Reply-To: <4AEF0572.9020609@gmail.com>
On Mon, Nov 02, 2009 at 05:14:42PM +0100, Roel Kluin wrote:
> The indexes are signed, make sure they are not negative
> when we read array elements.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
In practice none of these are likely to be an issue, but it doesn't
really hurt to add the sanity checks given that there's already a number
of them anyways. So, applied.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: linux-sh@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sh: Make sure indexes are positive
Date: Wed, 4 Nov 2009 12:15:40 +0900 [thread overview]
Message-ID: <20091104031540.GF12841@linux-sh.org> (raw)
In-Reply-To: <4AEF0572.9020609@gmail.com>
On Mon, Nov 02, 2009 at 05:14:42PM +0100, Roel Kluin wrote:
> The indexes are signed, make sure they are not negative
> when we read array elements.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
In practice none of these are likely to be an issue, but it doesn't
really hurt to add the sanity checks given that there's already a number
of them anyways. So, applied.
next prev parent reply other threads:[~2009-11-04 3:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 16:14 [PATCH] sh: Make sure indexes are positive Roel Kluin
2009-11-02 16:14 ` Roel Kluin
2009-11-04 3:15 ` Paul Mundt [this message]
2009-11-04 3:15 ` Paul Mundt
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=20091104031540.GF12841@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=roel.kluin@gmail.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.