Messages in this thread | | | Date | Thu, 20 Apr 2006 18:04:19 +0100 | From | Christoph Hellwig <> | Subject | Re: [RFC][PATCH 10/11] security: AppArmor - Add flags to d_path |
| |
On Thu, Apr 20, 2006 at 09:43:29AM -0700, Tony Jones wrote: > I can't tell if you are claiming there is a fundamental problem calling d_path > *period* in this scenario. If so, I'd appreciate a little more concrete detail
The purpose of d_path is to give user information about a path, to be used in things like procfs output. For everything else it's fundamentally broken and shouldn't be used. And for exactly that reason it isn't used for anything like that in the whole tree (except the possible fishy use in nfsd).
p.s.: I also see that your patch doesn't include on to export d_path so couldn't actually use it anyway. Not that a patch to export it would ever be ACKed for above reasons..
> > in the way of an actual example, this is a bit hand-wavy. > > Or that you are just saying another version of "pathames are crap" which I'm > not sure if appropos to this patch itself. > > If it's the former, I'll happily go off and write some code to test your > assertion and it's ramifications if I can better understand what the actual > assertion is :-) > > Thanks > > Tony ---end quoted text--- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |