From: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: mgross@linux.intel.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, anil.s.keshavamurthy@intel.com
Subject: Re: [PATCH] intel-iommu: Fix array overflow
Date: Thu, 25 Oct 2007 08:15:56 -0700 [thread overview]
Message-ID: <20071025151555.GE18751@askeshav-devel.jf.intel.com> (raw)
In-Reply-To: <s5htzofbqh5.wl%tiwai@suse.de>
On Thu, Oct 25, 2007 at 09:31:02AM +0200, Takashi Iwai wrote:
> At Wed, 24 Oct 2007 16:30:37 -0700,
> Mark Gross wrote:
> >
> > On Tue, Oct 23, 2007 at 10:57:51AM +0200, Takashi Iwai wrote:
> > > Fix possible array overflow:
> > >
> > > drivers/pci/intel-iommu.c: In function ‘dmar_get_fault_reason’:
> > > drivers/pci/intel-iommu.c:753: warning: array subscript is above array bounds
> > > drivers/pci/intel-iommu.c: In function ‘iommu_page_fault’:
> > > drivers/pci/intel-iommu.c:753: warning: array subscript is above array bounds
> > >
> > > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > >
> > > ---
> > > drivers/pci/intel-iommu.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/pci/intel-iommu.c b/drivers/pci/intel-iommu.c
> > > index b3d7031..e4b0a0d 100644
> > > --- a/drivers/pci/intel-iommu.c
> > > +++ b/drivers/pci/intel-iommu.c
> > > @@ -749,8 +749,8 @@ static char *fault_reason_strings[] =
> > >
> > > char *dmar_get_fault_reason(u8 fault_reason)
> > > {
> > > - if (fault_reason > MAX_FAULT_REASON_IDX)
> > > - return fault_reason_strings[MAX_FAULT_REASON_IDX];
> > > + if (fault_reason >= MAX_FAULT_REASON_IDX)
> > > + return fault_reason_strings[MAX_FAULT_REASON_IDX - 1];
> >
> > This looks like what the code meant to implement.
>
> I think not. The size of fault_reason_strings[] is
> MAX_FAULT_REASON_IDX, not + 1. So gcc warning is correct.
> Maybe the main problem is that the constant name is confusing...
Yup, GCC warning is correct. the size of fault_reason_strings[]
is MAX_FAULT_REASON_IDX and hence the max array that can be
referenced is [MAX_FAULT_REASON_IDX -1], hence the fix by
Takashi is correct.
-Anil
prev parent reply other threads:[~2007-10-25 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 8:57 Takashi Iwai
2007-10-24 23:30 ` Mark Gross
2007-10-25 7:31 ` Takashi Iwai
2007-10-25 15:15 ` Keshavamurthy, Anil S [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=20071025151555.GE18751@askeshav-devel.jf.intel.com \
--to=anil.s.keshavamurthy@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome