From: smurf@smurf.noris.de
To: Eric Sesterhenn <snakebyte@gmx.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] Overrun in
Date: Mon, 10 Apr 2006 11:31:19 +0200 [thread overview]
Message-ID: <20060410093119.GJ18658@smurf.noris.de> (raw)
In-Reply-To: <1144659666.15586.1.camel@alice>
[-- Attachment #1: Type: text/plain, Size: 291 bytes --]
Hi,
Eric Sesterhenn:
> since the arrays are declared as in_urbs[N_IN_URB]
> and out_urbs[N_OUT_URB] both for loops, go one
> over the end of the array. This fixes coverity id #555
>
Ouch. Thanks.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-04-10 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 9:01 Eric Sesterhenn
2006-04-10 9:31 ` smurf [this message]
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=20060410093119.GJ18658@smurf.noris.de \
--to=smurf@smurf.noris.de \
--cc=linux-kernel@vger.kernel.org \
--cc=snakebyte@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®