From: fche@redhat.com (Frank Ch. Eigler)
To: Steve Dickson
<public-SteveD-H+wXaHxf7aLQT0dZR+AlfA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>
Cc: SystemTAP
<public-systemtap-R2MHTz/CkKAf7BdofF/totBPR1lH4CV8-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>,
Linux NFS Mailing list
<public-linux-nfs-u79uwXL29TY76Z2rM5mHXA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>
Subject: Re: 2.6.33 NFS server header reorg breaks existing systemtap scripts.
Date: Sat, 19 Dec 2009 11:40:58 -0500 [thread overview]
Message-ID: <y0mmy1e9asl.fsf@fche.csb> (raw)
In-Reply-To: <4B2CF5AB.9040000-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org> (Steve Dickson's message of "Sat, 19 Dec 2009 10:47:55 -0500")
Hi -
steved wrote:
> [...]
> In the upcoming 2.6.33 kernel release the following
> NFS server header files have been moved out of the
> 'include/linux/nfsd' include directory and into the
> 'fs/nfsd' source directory:
> linux/nfsd/nfsd.h
> linux/nfsd/cache.h
> linux/nfsd/xdr.h
> linux/nfsd/xdr3.h
> linux/nfsd/xdr4.h
>
> This reorg will break any and all existing systemtap scripts
> including the nfsd.stp in the current systemtap release.
Sigh. Well, nfsd.stp can probably adapt to avoid using those headers,
and rewrite __get_fh etc. to rely on @cast() instead of embedded-C.
> Plus it appears the header files that live in source directories are
> not include in the kernel-devel package
Yes, it's a problem. This is harder to work around for tracepoints,
which systemtap finds by parsing kernel-devel header files (instead of
searching debuginfo or whatnot). Perhaps we should lobby kernel-devel
to include all .h files from the kernel build trees, even subsystem
internal .h files.
- FChE
prev parent reply other threads:[~2009-12-19 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 15:47 2.6.33 NFS server header reorg breaks existing systemtap scripts Steve Dickson
[not found] ` <4B2CF5AB.9040000-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-12-19 16:40 ` Frank Ch. Eigler [this message]
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=y0mmy1e9asl.fsf@fche.csb \
--to=fche@redhat.com \
--cc=public-SteveD-H+wXaHxf7aLQT0dZR+AlfA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
--cc=public-linux-nfs-u79uwXL29TY76Z2rM5mHXA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
--cc=public-systemtap-R2MHTz/CkKAf7BdofF/totBPR1lH4CV8-wOFGN7rlS/M9smdsby/KFg@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.