From: "mcermak at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/28634] New: ioscheduler.stp broken with new kernel 5.16.0-0.rc2
Date: Mon, 29 Nov 2021 12:32:12 +0000 [thread overview]
Message-ID: <bug-28634-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28634
Bug ID: 28634
Summary: ioscheduler.stp broken with new kernel 5.16.0-0.rc2
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: mcermak at redhat dot com
Target Milestone: ---
:: [ 12:13:36 ] :: [ BEGIN ] :: Running 'stap -c sync
--suppress-handler-errors -e 'probe
ioscheduler.elv_add_request{println(elevator_name) exit()}''
semantic error: unresolved struct elevator_queue: operator '->' at
/usr/share/systemtap/tapset/linux/ioscheduler.stp:155:65
source:
$rq->q->elevator->elevator_name)), "")
^
in expansion of macro: operator '@alternate' at
/usr/share/systemtap/tapset/choose_defined.stpm:3:57
source: ( @defined(@value_if_defined) ? (@value_if_defined) :
(@alternate) )
I guess this is caused by linux commit:
commit 2e9bc3465ac54d282b855b073409c2c3a7d1ae00
Author: Christoph Hellwig <hch@lst.de>
Date: Mon Sep 20 14:33:23 2021 +0200
block: move elevator.h to block/
Except for the features passed to blk_queue_required_elevator_features,
elevator.h is only needed internally to the block layer. Move the
ELEVATOR_F_* definitions to blkdev.h, and the move elevator.h to
block/, dropping all the spurious includes outside of that.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-11-29 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 12:32 mcermak at redhat dot com [this message]
2021-12-13 16:48 ` [Bug tapsets/28634] " mcermak at redhat dot com
2022-05-09 19:23 ` 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-28634-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).