Bug 490801 - [PATCH] Could not probe interrupt handler
Summary: [PATCH] Could not probe interrupt handler
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: systemtap
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Frank Ch. Eigler
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-18 06:17 UTC by Lubomir Rintel
Modified: 2009-03-19 17:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-03-19 17:04:28 UTC
Type: ---
Embargoed:


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

Description Lubomir Rintel 2009-03-18 06:17:08 UTC
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 17:04:28 UTC
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.