All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org, hadi@cyberus.ca, lartc@mailman.ds9a.nl
Subject: [LARTC] Re: [PATCH] TC: bug fixes to the "sample" clause
Date: Mon, 13 Mar 2006 18:04:21 +0000	[thread overview]
Message-ID: <20060313100421.7df7f9ed@localhost.localdomain> (raw)
In-Reply-To: <4415B217.30507@trash.net>

On Mon, 13 Mar 2006 18:55:35 +0100
Patrick McHardy <kaber@trash.net> wrote:

> jamal wrote:
> > On Mon, 2006-13-03 at 14:44 +1000, Russell Stuart wrote: 
> > 
> >>You are wrong on both counts.
> > 
> > 
> > I am wrong on why it is being rejected - but what you are seeing is
> > worse than i thought initially. 
> > 
> > Lets put it this way:
> > The only you will _ever_ get that message is if you had made a syntax
> > error (which you did not). Please look at the code on where that message
> > appears and:
> > 
> > a) tell me how you would have got that message to begin with using
> > perfectly legal syntax.
> > a) tell me how a memset would have fixed that.
> 
> He already told you, pack_key expects the selector to be initialized,
> otherwise nkeys might contain a value >= 128, which would cause
> exactly this error, if a matching key is not found within the
> uninitialized memory by accident.
> 
> > Just send the memset fix to Stephen with a different reason. Your
> > current reason is _wrong_ and i really dont have much time to have this
> > kind of discussion.  
> > If you had said "I added that memset there because it looks like the
> > right thing to do" then we would not have had this discussion.
> > 
> > You made claims you fixed a bug. It cant possibly be the bug you fixed.
> > Was it some other bug perhaps and you mixed up the two?

The memset fix is in current CVS. I just wasn't going to take the
patch that looked at utsname to decide what hash to use.

> The patch as well as the description are perfectly fine.
> 
> BTW, running valgrind on tc shows lots of uses of uninitialized values,
> it seems like a good idea if someone would go over these and fix them
> up.

If we had a test script of commands (code coverage), that would help.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <shemminger@osdl.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org, hadi@cyberus.ca, lartc@mailman.ds9a.nl
Subject: Re: [PATCH] TC: bug fixes to the "sample" clause
Date: Mon, 13 Mar 2006 10:04:21 -0800	[thread overview]
Message-ID: <20060313100421.7df7f9ed@localhost.localdomain> (raw)
In-Reply-To: <4415B217.30507@trash.net>

On Mon, 13 Mar 2006 18:55:35 +0100
Patrick McHardy <kaber@trash.net> wrote:

> jamal wrote:
> > On Mon, 2006-13-03 at 14:44 +1000, Russell Stuart wrote: 
> > 
> >>You are wrong on both counts.
> > 
> > 
> > I am wrong on why it is being rejected - but what you are seeing is
> > worse than i thought initially. 
> > 
> > Lets put it this way:
> > The only you will _ever_ get that message is if you had made a syntax
> > error (which you did not). Please look at the code on where that message
> > appears and:
> > 
> > a) tell me how you would have got that message to begin with using
> > perfectly legal syntax.
> > a) tell me how a memset would have fixed that.
> 
> He already told you, pack_key expects the selector to be initialized,
> otherwise nkeys might contain a value >= 128, which would cause
> exactly this error, if a matching key is not found within the
> uninitialized memory by accident.
> 
> > Just send the memset fix to Stephen with a different reason. Your
> > current reason is _wrong_ and i really dont have much time to have this
> > kind of discussion.  
> > If you had said "I added that memset there because it looks like the
> > right thing to do" then we would not have had this discussion.
> > 
> > You made claims you fixed a bug. It cant possibly be the bug you fixed.
> > Was it some other bug perhaps and you mixed up the two?

The memset fix is in current CVS. I just wasn't going to take the
patch that looked at utsname to decide what hash to use.

> The patch as well as the description are perfectly fine.
> 
> BTW, running valgrind on tc shows lots of uses of uninitialized values,
> it seems like a good idea if someone would go over these and fix them
> up.

If we had a test script of commands (code coverage), that would help.

  reply	other threads:[~2006-03-13 18:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10  2:33 [LARTC] [PATCH] TC: bug fixes to the "sample" clause Russell Stuart
2006-02-10  2:33 ` Russell Stuart
     [not found] ` <1142082696.5184.53.camel@jzny2>
2006-03-13  4:44   ` [LARTC] " Russell Stuart
2006-03-13  4:44     ` Russell Stuart
     [not found]     ` <1142269090.5242.29.camel@jzny2>
2006-03-13 17:55       ` [LARTC] " Patrick McHardy
2006-03-13 17:55         ` Patrick McHardy
2006-03-13 18:04         ` Stephen Hemminger [this message]
2006-03-13 18:04           ` Stephen Hemminger
2006-03-13 18:15           ` [LARTC] " Patrick McHardy
2006-03-13 18:15             ` Patrick McHardy
2006-03-13 19:02           ` [LARTC] " Patrick McHardy
2006-03-13 19:02             ` Patrick McHardy
2006-03-13 21:43           ` [LARTC] " Russell Stuart
2006-03-13 21:43             ` Russell Stuart
2006-03-13 21:50             ` [LARTC] " Stephen Hemminger
2006-03-13 21:50               ` Stephen Hemminger
2006-03-14  0:31               ` [LARTC] " Russell Stuart
2006-03-14  0:31                 ` Russell Stuart
     [not found]                 ` <1142303082.5219.16.camel@jzny2>
     [not found]                   ` <1142306212.17608.178.camel@ras.pc.brisbane.lube>
     [not found]                     ` <1142307572.5219.73.camel@jzny2>
     [not found]                       ` <1142312708.17608.270.camel@ras.pc.brisbane.lube>
     [not found]                         ` <1142436098.5346.3.camel@jzny2>
     [not found]                           ` <1142470323.17608.341.camel@ras.pc.brisbane.lube>
     [not found]                             ` <20060315165757.44bf1548@localhost.localdomain>
2006-03-16  1:43                               ` [LARTC] " Russell Stuart
2006-03-16  1:43                                 ` Russell Stuart
     [not found]                             ` <1142472481.5417.20.camel@jzny2>
     [not found]                               ` <1142476647.17608.394.camel@ras.pc.brisbane.lube>
     [not found]                                 ` <1142478478.5417.46.camel@jzny2>
     [not found]                                   ` <1142488027.17608.485.camel@ras.pc.brisbane.lube>
     [not found]                                     ` <1142517116.5417.137.camel@jzny2>
2006-03-16 23:24                                       ` [LARTC] " Russell Stuart
2006-03-16 23:24                                         ` Russell Stuart
     [not found]                                         ` <1142606049.5322.89.camel@jzny2>
2006-03-18  5:10                                           ` [LARTC] " Russell Stuart
2006-03-18  5:10                                             ` Russell Stuart
2006-03-20  3:11                                           ` [LARTC] " Russell Stuart
2006-03-20  3:11                                             ` Russell Stuart
2006-03-14  2:29   ` [LARTC] " Russell Stuart
2006-03-14  2:29     ` Russell Stuart
     [not found]   ` <1142085718.5184.73.camel@jzny2>
     [not found]     ` <1142088594.4199.115.camel@ras.pc.stuart.local>
     [not found]       ` <1142092598.5184.93.camel@jzny2>
2006-03-14  2:45         ` [LARTC] " Russell Stuart
2006-03-14  2:45           ` Russell Stuart

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=20060313100421.7df7f9ed@localhost.localdomain \
    --to=shemminger@osdl.org \
    --cc=hadi@cyberus.ca \
    --cc=kaber@trash.net \
    --cc=lartc@mailman.ds9a.nl \
    --cc=netdev@vger.kernel.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 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.