public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug kprobes/28557] unable to probe function in kernel module (xfs:xfs_ilock &others?)
Date: Sun, 14 Nov 2021 21:31:18 +0000	[thread overview]
Message-ID: <bug-28557-6586-fbMRw1NZnT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28557-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28557

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
                 CC|                            |fche at redhat dot com

--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
commit 0425c60d7eed27437c5f83d79612786e50aed8ba 
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Sun Nov 14 16:28:12 2021 -0500

    PR28557: module probe insertion on modern kernels

appears to fix this on newer kernels, and keep things working on older kernels.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2021-11-14 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-06 20:40 [Bug kprobes/28557] New: dwflpp not getting inline entry point of xfs:xfs_ilock me at serhei dot io
2021-11-11 13:41 ` [Bug kprobes/28557] unable to probe function in kernel module (xfs:xfs_ilock &others?) me at serhei dot io
2021-11-14 21:31 ` fche at redhat dot com [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=bug-28557-6586-fbMRw1NZnT@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).