From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/29766] New: kernel.function("__set_page_dirty_buffers") not found in tapset/linux/vfs.stp
Date: Wed, 09 Nov 2022 14:00:34 +0000 [thread overview]
Message-ID: <bug-29766-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29766
Bug ID: 29766
Summary: kernel.function("__set_page_dirty_buffers") not found
in tapset/linux/vfs.stp
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Target Milestone: ---
The new 5.14.0-186.kpq1.el9 seems to be missing
kernel.function("__set_page_dirty_buffers"). Suspectedly the following kernel
commit is related:
commit e621900ad28b748e058b81d6078a5d5eb37b3973
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Wed Feb 9 20:22:12 2022 +0000
fs: Convert __set_page_dirty_buffers to block_dirty_folio
Convert all callers; mostly this is just changing the aops to point
at it, but a few implementations need a little more work.
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Tested-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Acked-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Tested-by: Mike Marshall <hubcap@omnibond.com> # orangefs
Tested-by: David Howells <dhowells@redhat.com> # afs
Reproducer:
# stap -P -w -p4 /root/systemtap/testsuite/buildok/vfs-all-probes.stp
semantic error: while resolving probe point: identifier 'kernel' at
/usr/local/share/systemtap/tapset/linux/vfs.stp:825:38
source: probe vfs.__set_page_dirty_buffers =
kernel.function("__set_page_dirty_buffers")
^
semantic error: no match (similar functions: __set_page_dirty_nobuffers,
write_dirty_buffer, __set_page_dirty, __sync_dirty_buffer, set_page_dirty_lock)
Pass 2: analysis failed. [man error::pass2]
Number of similar error messages suppressed: 1.
Rerun with -v to see them.
#
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-11-09 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 14:00 mcermak at redhat dot com [this message]
2022-12-14 12:58 ` [Bug runtime/29766] " mcermak at redhat dot com
2022-12-14 16:39 ` mcermak 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=bug-29766-6586@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).