From: Andrew Morton <akpm@linux-foundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix array overflow in parport_serial.c
Date: Fri, 21 Nov 2008 14:16:21 -0800 [thread overview]
Message-ID: <20081121141621.fe4277bb.akpm@linux-foundation.org> (raw)
In-Reply-To: <s5habbu9wzb.wl%tiwai@suse.de>
On Thu, 20 Nov 2008 17:35:20 +0100
Takashi Iwai <tiwai@suse.de> wrote:
> Subject: [PATCH] Fix array overflow in parport_serial.c
Please prefer titles in the form
subsystem identifer: what was done to it
I renamed this one to
parport_serial: fix array overflow
> Date: Thu, 20 Nov 2008 17:35:20 +0100
> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
> FLIM/1.14.7 (Sanj__) APEL/10.6 Emacs/22.3
> (x86_64-suse-linux-gnu) MULE/5.0 (SAKAKI)
>
> The netmos_9xx5_combo type assumes that PCI SSID provides always the
> correct value for the number of parallel and serial ports, but there
> are indeed broken devices with wrong numbers, which may result in
> Oops.
>
> This patch simply adds the check of the array range.
>
> Reference: Novell bnc#447067
> https://bugzilla.novell.com/show_bug.cgi?id=447067
>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
>
> ---
> diff --git a/drivers/parport/parport_serial.c b/drivers/parport/parport_serial.c
> index e2e95b3..101ed49 100644
> --- a/drivers/parport/parport_serial.c
> +++ b/drivers/parport/parport_serial.c
> @@ -70,6 +70,8 @@ static int __devinit netmos_parallel_init(struct pci_dev *dev, struct parport_pc
> * parallel ports and <S> is the number of serial ports.
> */
> card->numports = (dev->subsystem_device & 0xf0) >> 4;
> + if (card->numports > ARRAY_SIZE(card->addr))
hm. ARRAY_SIZE returns an unsigned type so we don't have to worry
about negative values when doing comparisons like this. Not that
card->numports could be negative anyway, but it's always nice to set
readers' minds at rest..
> + card->numports = ARRAY_SIZE(card->addr);
> return 0;
> }
Should we emit some kind of warning when this is detected? I guess
not, if we're sure that there will never be a situation in which users
find that some of their ports don't work?
next prev parent reply other threads:[~2008-11-21 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 16:35 [PATCH] Fix array overflow in parport_serial.c Takashi Iwai
2008-11-21 22:16 ` Andrew Morton [this message]
2008-11-22 9:56 ` Takashi Iwai
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=20081121141621.fe4277bb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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.