The only benefit I can see for this is to make sure we don't leak any of these labels. I can't find a reasonable way to match these up though so it will just give us a hint that we are leaking something. Dave On Fri, 2008-02-29 at 10:00 +1100, James Morris wrote: > On Thu, 28 Feb 2008, Dave Quigley wrote: > > > A question about the debug configuration here. Exactly what information > > are we looking to get for debugging. If we want line/file/function that > > these are called on then I need a macro wrapper for the allocation as > > well. If that is the case I'm guessing we always define the macros > > nfs_fattr_alloc and nfs_fattr_fini and just make the internal functions > > static inline so they can be compiled away when !CONFIG_SECURITY. > > Well, a WARN_ON will give you a stack trace. It's up to you -- how much > debugging do you think this will need now? > > > - James -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
