netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Anton 'EvilMan' Danilov" <littlesmilingcloud@gmail.com>
To: jhs@mojatatu.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] pedit action: add mask for changing bits.
Date: Mon, 27 Feb 2012 17:15:30 +0300	[thread overview]
Message-ID: <CAEzD07KenHteg0S8-OfAwqTNTSQdvPOJsA-m_+8CW-8c_HCgnw@mail.gmail.com> (raw)
In-Reply-To: <1330351135.2384.1039.camel@mojatatu>

Hi, Jamal.

2012/2/27 jamal <hadi@cyberus.ca>:
>
> Looks like a reasonable feature to have - but it has to continue working
> as before for things that dont need the mask.
>
>>
>> diff --git a/tc/m_pedit.c b/tc/m_pedit.c
>> index 7499846..f081eff 100644
>> --- a/tc/m_pedit.c
>> +++ b/tc/m_pedit.c
>
>>
>>       tkey->val = htonl(tkey->val & retain);
>> -     tkey->mask = htonl(tkey->mask | ~retain);
>> +     tkey->mask = htonl(~tkey->mask | ~retain);
>
> A change like the above worries me that this may work for your use case
> but will break other things that used to work. I'd like to run some
> tests but dont have the cycles for the next few days. Alternatively, I
> could explain some tests to you and you could validate and fix whatever
> breaks.
> Let me know what is best for you.
>

Can You explain tests to me? I'll check behavior with my changes and fix breaks


-- 
Anton.

  reply	other threads:[~2012-02-27 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 18:01 [PATCH iproute2] pedit action: add mask for changing bits Anton 'EvilMan' Danilov
2012-02-27 13:58 ` jamal
2012-02-27 14:15   ` Anton 'EvilMan' Danilov [this message]
2012-02-28 13:05     ` Jamal Hadi Salim
2012-02-29 13:12       ` Anton 'EvilMan' Danilov
2012-02-29 14:01         ` jamal
2012-04-25 20:15           ` Stephen Hemminger
2012-04-26 10:21             ` Jamal Hadi Salim

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=CAEzD07KenHteg0S8-OfAwqTNTSQdvPOJsA-m_+8CW-8c_HCgnw@mail.gmail.com \
    --to=littlesmilingcloud@gmail.com \
    --cc=jhs@mojatatu.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).