summaryrefslogtreecommitdiffstats
path: root/doc/Tapset_Reference_Guide/en-US
diff options
context:
space:
mode:
authorJosh Stone <jistone@redhat.com>2009-03-13 16:22:04 -0700
committerJosh Stone <jistone@redhat.com>2009-03-13 16:22:04 -0700
commit436b47f678c2fc5397ed66a1eddf6b419cc6585b (patch)
tree372c838479af953282cc03ce6cc0f3801a629168 /doc/Tapset_Reference_Guide/en-US
parent52aeb26b8d83c26e00adaf70bbf5a3a828689fb2 (diff)
downloadsystemtap-steved-436b47f678c2fc5397ed66a1eddf6b419cc6585b.tar.gz
systemtap-steved-436b47f678c2fc5397ed66a1eddf6b419cc6585b.tar.xz
systemtap-steved-436b47f678c2fc5397ed66a1eddf6b419cc6585b.zip
Move lookup_bad_addr call in STAPCONF_PROBE_KERNEL
With most of the implementations, kread/kwrite call deref/store_deref, and so it makes sense to have lookup_bad_addr in the latter as an underlying address check. However, in the STAPCONF_PROBE_KERNEL case that uses probe_kernel_read and probe_kernel_write, the roles are reversed, so lookup_bad_addr needs to be in kread/kwrite. Also note that __deref_bad and __store_deref_bad should only be used in cases that can be determined at compile time. These turn into invalid symbols which prevent the module from loading. (They might be better replaced with compile-time assertions.)
Diffstat (limited to 'doc/Tapset_Reference_Guide/en-US')
0 files changed, 0 insertions, 0 deletions