Bug 155326 – 2 * array subscript out of range

Bug 155326 - 2 * array subscript out of range

Summary:	2 * array subscript out of range

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	iproute (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Radek Vokal
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-04-19 04:39 EDT by David Binderman
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-08-10 07:33:53 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description David Binderman 2005-04-19 04:39:15 EDT

Description of problem:

I just tried to compile iproute-2.6.11-1 from Redhat
Fedora Core development tree with the Intel C compiler.

The compiler said

m_action.c(256): warning #175: subscript out of range
m_action.c(258): warning #175: subscript out of range

The source code is

        if (show_stats && tb[TCA_ACT_STATS]) {
                fprintf(f, "\tAction statistics:\n");
                print_tcstats2_attr(f, tb[TCA_ACT_STATS], "\t", NULL);

But

        struct rtattr *tb[TCA_ACT_MAX + 1];

and TCA_ACT_STATS has the value 8, and TCA_ACT_MAX has the value 4.

Suggest code re-work.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Radek Vokal 2005-08-10 07:33:53 EDT

Got response from upstream and this is sane. Closing as NOTABUG

Comment 2 David Binderman 2005-08-10 16:43:55 EDT

>Got response from upstream and this is sane. 

I'd be grateful if you could show where 
either I or the Intel compiler has gone wrong.

Note You need to log in before you can comment on or make changes to this bug.