On Tue, 2008-07-15 at 16:24 -0700, Andrew Morton wrote:Since rpcdebug + the sysctl interface are well established interfaces that are probably scripted all over the place by administrators who are using it to as a debugging tool, I'd say that any interface breakages need a managed transition period. IOW: I'd say that any changes are going to need a transition period where a compatibility mode can be compiled in and where both interfaces work. It doesn't have to be too sophisticated, perhaps just something along the lines of +# define ifdebug(fac) if (dynamic_dbg_enabled(TYPE_FLAG, \ + RPCDBG_##fac,\ + rpc_debug) || \ + unlikely(rpc_debug & RPCDBG_##fac)) +# define dfprintk(fac, args...) do { ifdebug(fac) printk(args); } while(0) So that scripts can choose either interface, and still continue to operate. Please also note the 'special' command echo "n" >/proc/sys/sunrpc/rpc_debug (where "n" is an integer) which always triggers a listing of the currently executing rpc calls (see net/sunrpc/sysctl.c:proc_dodebug()) in addition to enabling/disabling debugging. --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| David Newall | Re: Slow DOWN, please!!! |
| Peter Zijlstra | [PATCH 00/23] per device dirty throttling -v8 |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
git: | |
