mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Douglas Anderson <dianders@chromium.org>,
	Jason Wessel <jason.wessel@windriver.com>,
	kgdb-bugreport@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kgdbts: Switch to do_sys_openat2() for breakpoint testing
Date: Sun, 28 Mar 2021 14:40:02 +0200	[thread overview]
Message-ID: <YGB5IlM7/WqSOdQ2@kroah.com> (raw)
In-Reply-To: <20210325094807.3546702-1-daniel.thompson@linaro.org>

On Thu, Mar 25, 2021 at 09:48:07AM +0000, Daniel Thompson wrote:
> Currently kgdbts can get stuck waiting for do_sys_open() to be called
> in some of the current tests. This is because C compilers often
> automatically inline this function, which is a very thin wrapper around
> do_sys_openat2(), into some of its callers. gcc-10 does this on (at least)
> both x86 and arm64.
> 
> We can fix the test suite by placing the breakpoints on do_sys_openat2()
> instead since that isn't (currently) inlined. However do_sys_openat2() is
> a static function so we cannot simply use an addressof. Since we are
> testing debug machinery it is acceptable to use kallsyms to lookup a
> suitable address because this is more or less what kdb does in the same
> circumstances. Re-implement lookup_addr() to be based on kallsyms rather
> than function pointers.
> 
> Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
> ---
> 
> Notes:
>     So less than a week ago I said I had nothing pending for kgdbts.
>     That was entirely true when I said it... but then this came up.

No worries, I'll take this too :)

thanks,

greg k-h

      reply	other threads:[~2021-03-28 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25  9:48 Daniel Thompson
2021-03-28 12:40 ` Greg Kroah-Hartman [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=YGB5IlM7/WqSOdQ2@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=daniel.thompson@linaro.org \
    --cc=dianders@chromium.org \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®