netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Shyam Saini <mayhs11saini@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCHv3] tests: py: Add test for ambiguity while setting the value
Date: Sun, 18 Jun 2017 11:29:13 +0200	[thread overview]
Message-ID: <20170618092913.GA8026@salvia> (raw)
In-Reply-To: <1497641742-25272-1-git-send-email-mayhs11saini@gmail.com>

On Sat, Jun 17, 2017 at 01:05:42AM +0530, Shyam Saini wrote:
> This test checks bug identified and fixed in the commit mentioned below
> In a statement if there are  multiple src data then it  would be
> totally ambiguous to decide which value to set.
> 
> Before the commit was made it returned 134(BUG), but now it returns 1
> i.e, an error message.

Applied, thanks.

One change though before applying, see below.

> Test: 986dea8 ("evaluate: avoid reference to multiple src data in
> statements which set values")
> Signed-off-by: Shyam Saini <mayhs11saini@gmail.com>
> ---
>  tests/py/any/ct.t       | 10 ++++++++++
>  tests/py/any/meta.t     |  8 ++++++++
>  tests/py/bridge/ether.t |  7 +++++++
>  tests/py/inet/tcp.t     |  7 +++++++
>  tests/py/inet/udp.t     |  7 +++++++
>  tests/py/ip/ip.t        |  7 +++++++
>  6 files changed, 46 insertions(+)
> 
> diff --git a/tests/py/any/ct.t b/tests/py/any/ct.t
> index 20f047a..f7c2321 100644
> --- a/tests/py/any/ct.t
> +++ b/tests/py/any/ct.t
> @@ -58,6 +58,16 @@ ct mark set 0x11;ok;ct mark set 0x00000011
>  ct mark set mark;ok;ct mark set mark
>  ct mark set mark map { 1 : 10, 2 : 20, 3 : 30 };ok;ct mark set mark map { 0x00000003 : 0x0000001e, 0x00000002 : 0x00000014, 0x00000001 : 0x0000000a}
>  
> +# Following rules tests ambguity while setting the value
> +# sudo nft add rule ip test-ip4 output ct mark set {0x11333, 0x11}
> +# <cmdline>:1:41-55: Error: you cannot use a set here, unknown value to use
> +# add rule ip test-ip4 output ct mark set {0x11333, 0x11}
> +#                             ~~~~~~~~~~~~^^^^^^^^^^^^^^^

No need to copy and paste this over and over again.

Look, next time you place this in the commit message, we can find the
reason why this line was added via:

$ git annotate

So I have removed them all before applying.

  reply	other threads:[~2017-06-18  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16 19:35 [PATCHv3] tests: py: Add test for ambiguity while setting the value Shyam Saini
2017-06-18  9:29 ` Pablo Neira Ayuso [this message]
2017-06-18  9:31   ` Pablo Neira Ayuso
2017-06-21  8:46     ` Shyam Saini
2017-06-18  9:48   ` Pablo Neira Ayuso
2017-06-21  8:50     ` Shyam Saini
2017-06-21  8:45   ` Shyam Saini

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=20170618092913.GA8026@salvia \
    --to=pablo@netfilter.org \
    --cc=mayhs11saini@gmail.com \
    --cc=netfilter-devel@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).