DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] false positive in check-symbol-change.sh tool
Date: Wed, 19 Sep 2018 19:43:57 +0200	[thread overview]
Message-ID: <1582481.Q53MnriLgg@xps> (raw)

Hi Neil,

I think I've discovered a false positive with the script
devtools/check-symbol-change.sh
When checking the patch http://patches.dpdk.org/patch/40601/,
which is adding an experimental section with a symbol in it,
we can see this message:
ERROR: symbol rte_frag_table_del_expired_entries is added in a section other than the EXPERIMENTAL section of the version map

The code raising this error is below:
            if [ "$secname" != "EXPERIMENTAL" ]
            then
                # Symbols that are getting added in a section
                # other than the experimental section
                # to be moving from an already supported
                # section or its a violation
                grep -q \
                "$mname $symname [^EXPERIMENTAL] del" "$mapdb"
                if [ $? -ne 0 ]
                then
                    echo -n "ERROR: symbol $symname "
                    echo -n "is added in a section "
                    echo -n "other than the EXPERIMENTAL "
                    echo "section of the version map"
                    ret=1
                fi
            fi

After a quick check, I see two strange things:

1/ $secname is "+EXPERIMENTAL" in this case
This is probably the root cause of this false positive.

2/ The grep pattern is probably not what you want.
The regex [^EXPERIMENTAL] means "a character which is none
of the letters in EXPERIMENTAL".

Hope it can help you (or others) to fix some issues.
Thanks

                 reply	other threads:[~2018-09-19 17:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1582481.Q53MnriLgg@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.com \
    /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).