From: Thomas Monjalon <thomas@monjalon.net>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] check-experimental-syms.sh: prevent symbol matches on substrings
Date: Thu, 11 Oct 2018 13:59:58 +0200 [thread overview]
Message-ID: <3543645.ZMkEL9mWDR@xps> (raw)
In-Reply-To: <20181010201919.GA19761@hmswarspite.think-freely.org>
10/10/2018 22:19, Neil Horman:
> On Wed, Oct 10, 2018 at 04:43:14PM +0200, Thomas Monjalon wrote:
> > 10/10/2018 16:29, Neil Horman:
> > > Thomas attempted to submit this:
> > > https://patches.dpdk.org/patch/46311/
> > >
> > > The other day, because the other patches being submitted with it were
> > > breaking on a false positive from the check-experimental-syms check.
> > >
> > > The problem was that the experimental symbol check script matched on the
> > > regexs "\.text.*$SYM" and "\.text\.experimental.*$SYM" which allows for
> > > substring matches, and librte_ethdev recently introduced symbols that
> > > are leading substrings of one another (e.g. symbol foo is a substring of
> > > symbol foobar), and so we would match on symbols when we shouldn't
> > >
> > > Instead of dropping the check, fix this properly by matching
> > > additionally on the end of line so that symbols are an exact match.
> > >
> > > Confirmed to build properly on Thomas' submitted patch set with the
> > > experimental check patch reverted (so that the checking actually
> > > happens)
> >
> > That's great Neil!
> > I would like to push it now.
> > May I suggest to remove the details of how I (baldly) reported it?
> >
> > I suggest this text:
> > "
> > The experimental symbol check script matched on the regexes
> > "\.text.*$SYM" and "\.text\.experimental.*$SYM" which allows for
> > substring matches.
> > If a symbol is leading substring of another one (e.g. symbol foo
> > is a substring of symbol foobar), it would match on symbols
> > when it shouldn't.
> >
> > It is fixed by matching additionally on the end of line
> > so that symbols are an exact match.
> > "
> Sure, if you want to make that change on commit, I'm ok with it.
Applied, thanks
prev parent reply other threads:[~2018-10-11 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 14:29 Neil Horman
2018-10-10 14:43 ` Thomas Monjalon
2018-10-10 20:19 ` Neil Horman
2018-10-11 11:59 ` Thomas Monjalon [this message]
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=3543645.ZMkEL9mWDR@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).