public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris J Arges <chris.j.arges@canonical.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Petr Mladek <pmladek@suse.com>, Jiri Kosina <jikos@kernel.org>,
	Jessica Yu <jeyu@redhat.com>, Miroslav Benes <mbenes@suse.cz>,
	live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] livepatch: Fix the error message about unresolvable ambiguity
Date: Wed, 9 Mar 2016 10:40:23 -0600	[thread overview]
Message-ID: <20160309164004.GA30562@canonical.com> (raw)
In-Reply-To: <20160309161946.GC21308@treble.redhat.com>

On Wed, Mar 09, 2016 at 10:19:46AM -0600, Josh Poimboeuf wrote:
> On Wed, Mar 09, 2016 at 03:20:59PM +0100, Petr Mladek wrote:
> > klp_find_callback() stops the search when sympos is not defined and
> > a second symbol of the same name is found. It means that the current
> > error message about the unresolvable ambiguity always prints "(2 matches)".
> > 
> > Let's remove this information. The total number of occurrences is
> > not much helpful. The author of the patch still must put a non-trivial
> > effort into searching the right position in the object file.
> > 
> > Signed-off-by: Petr Mladek <pmladek@suse.com>
> > ---
> >  kernel/livepatch/core.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/kernel/livepatch/core.c b/kernel/livepatch/core.c
> > index bc2c85c064c1..f2eda09e8357 100644
> > --- a/kernel/livepatch/core.c
> > +++ b/kernel/livepatch/core.c
> > @@ -190,8 +190,8 @@ static int klp_find_object_symbol(const char *objname, const char *name,
> >  	if (args.addr == 0)
> >  		pr_err("symbol '%s' not found in symbol table\n", name);
> >  	else if (args.count > 1 && sympos == 0) {
> > -		pr_err("unresolvable ambiguity (%lu matches) on symbol '%s' in object '%s'\n",
> > -		       args.count, name, objname);
> > +		pr_err("unresolvable ambiguity on symbol '%s' in object '%s'\n",
> 
> While you're at it, can you improve the grammar: s/on/for/ ?
> 
> "unresolvable ambiguity *for* symbol..."
> 
> Either way,
> 
> Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
> 
> -- 
> Josh
>

I agree that the 'matches' error message doesn't added anything helpful.
With the word change above:
Acked-by: Chris J Arges <chris.j.arges@canonical.com>

--chris

  reply	other threads:[~2016-03-09 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 14:20 [PATCH] livepatch: Fix the error message about unresolvable ambiguity Petr Mladek
2016-03-09 16:19 ` Josh Poimboeuf
2016-03-09 16:40   ` Chris J Arges [this message]
2016-03-09 20:59 ` Jiri Kosina

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=20160309164004.GA30562@canonical.com \
    --to=chris.j.arges@canonical.com \
    --cc=jeyu@redhat.com \
    --cc=jikos@kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=pmladek@suse.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