From: Craig Ringer <craig@2ndquadrant.com>
To: systemtap@sourceware.org
Subject: [Bug tapsets/26184] fullpath_struct_file does not handle struct dentry on 5.6.19-300.fc32.x86_64
Date: Mon, 13 Jul 2020 14:48:27 +0800 [thread overview]
Message-ID: <CAMsr+YG12+3w+UXE2GHRuY5zzhUV3ON0qcdZTLF7d2Tjp=q_FA@mail.gmail.com> (raw)
Hi all
Bugzilla failed to generate mail on this bug so I'm posting it directly.
It's a compilation issue on recent kernels relating to struct dentry that
prevents the use of tapset functions such as fullpath_struct_file() .
Noticed while trying to determine the actual path of the process being
attached to.
I had a bit of a look in the headers but I admit I quickly got lost.
--
Craig Ringer http://www.2ndQuadrant.com/
2ndQuadrant - PostgreSQL Solutions for the Enterprise
next reply other threads:[~2020-07-13 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 6:48 Craig Ringer [this message]
2021-05-26 21:26 [Bug tapsets/26184] New: " guillaume at morinfr dot org
2021-05-26 22:06 ` [Bug tapsets/26184] " guillaume at morinfr dot org
2022-03-22 18:15 ` wcohen at redhat dot com
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='CAMsr+YG12+3w+UXE2GHRuY5zzhUV3ON0qcdZTLF7d2Tjp=q_FA@mail.gmail.com' \
--to=craig@2ndquadrant.com \
--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).