Bug 490801 - [PATCH] Could not probe interrupt handler
[PATCH] Could not probe interrupt handler
Product: Fedora
Classification: Fedora
Component: systemtap (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Frank Ch. Eigler
Fedora Extras Quality Assurance
: EasyFix, Patch
Depends On:
  Show dependency treegraph
Reported: 2009-03-18 02:17 EDT by Lubomir Rintel
Modified: 2009-03-19 13:04 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-19 13:04:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Disable blacklist in Guru mode (757 bytes, text/plain)
2009-03-18 02:17 EDT, Lubomir Rintel
no flags Details

  None (edit)
Description Lubomir Rintel 2009-03-18 02:17:08 EDT
Created attachment 335653 [details]
Disable blacklist in Guru mode

With 0.9 I could not attach a probe to interrupt handlers with *_intr() (such as e1000_intr()) names (while those with names not matching the pattern, such as ata_sff_interrupt() or usb_hcd_irq() could be probed for without a problem).

While this worked for me flawlessly on Rawhide's 2.6.29, I understand that there may be some problems with probing interrupt handlers, still it would be nice if the blacklist could be just disabled.

If I understand the documentation correctly, the feature to turn off security measures is the Guru mode, therefore I attach a tiny patch, that disables the blacklist in guru mode. I tested it successfully being able to add module("e1000).function("e1000_intr") and module("e1000).function("e1000_intr").return probes.
Comment 1 Frank Ch. Eigler 2009-03-19 13:04:28 EDT
Thanks, your patch is applied and should appear in the next version of systemtap.

Note You need to log in before you can comment on or make changes to this bug.