From: "Serhei Makarov" <me@serhei.io>
To: "Daire Byrne" <daire@dneg.com>, systemtap <systemtap@sourceware.org>
Subject: Re: newer kernel+systemtap & nfs.fop.open
Date: Fri, 01 Apr 2022 10:55:54 -0400 [thread overview]
Message-ID: <6a4c5961-df38-40d6-9491-1f5a587a3dbf@www.fastmail.com> (raw)
In-Reply-To: <CAPt2mGO9ethiAZXZyOt9oOv++sQK_=9Vo0AH+KApLncNsk-e+g@mail.gmail.com>
On Fri, Apr 1, 2022, at 8:26 AM, Daire Byrne via Systemtap wrote:
> Hi,
>
> Is anyone able to point me in the right direction or is there a better
> forum for asking these kinds of questions?
Hi, thank you for reporting this.
IRC oftc.net #systemtap may also be a good venue if you're
interested in partial answers quickly over full answers
at an unknown time.
Unfortunately since the kernel may change the same tapsets
can yield different results until they're fixed to match the
newer kernel too. They are generally coded to use
multiple fallbacks, so if only part of the information is in the same
place the d_name() function would yield just the name
instead of "<unknown>".
In this case the last commit
to tapsets/linux/dentry.stp was in 2020
so it looks like we may have some catching up to the kernel
to do. I'll investigate more (i.e. delve into kernel git history)
and get back to you.
next prev parent reply other threads:[~2022-04-01 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 19:58 Daire Byrne
2022-04-01 12:26 ` Daire Byrne
2022-04-01 14:05 ` David Smith
2022-04-01 14:55 ` Serhei Makarov [this message]
2022-04-01 20:13 ` Serhei Makarov
2022-04-04 11:21 ` Daire Byrne
2022-04-04 12:28 ` Daire Byrne
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=6a4c5961-df38-40d6-9491-1f5a587a3dbf@www.fastmail.com \
--to=me@serhei.io \
--cc=daire@dneg.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).