On Mon, 10 Sep 2001, Greg KH wrote: > The "where it is called from" section might be tough to guarentee that > it will remain correct in the future as things change (you aren't going > to think to change a header file if you just move the placement of a > hook.) And isn't that what grep/ctags/cscope/cgvg good for? :) Hmmm...but knowing the placement of the hooks is relevant to security module implementors. Other information in the hook documentation can be dependent on the placement of the hook, e.g. what locks are held, whether or not the hook can be called from interrupt context, and, in some cases, how to interpret the parameters to the hook. Also, simply understanding the purpose of the hook can often be enhanced by knowing where it is placed. So, although I understand the concern about keeping this part of the documentation up-to-date, I would still advocate retaining it. -- Stephen D. Smalley, NAI Labs ssmalleyat_private _______________________________________________ linux-security-module mailing list linux-security-moduleat_private http://mail.wirex.com/mailman/listinfo/linux-security-module
This archive was generated by hypermail 2b30 : Mon Sep 10 2001 - 10:49:30 PDT