Re: 2.6 path_lookup bug?
tvrtko.ursulin_at_sophos.com
Date: 12/08/04
- Previous message: Michael Buesch: "Re: [PATCH, RFC] protect call to set_tsk_need_resched() by the rq-lock"
- Maybe in reply to: tvrtko.ursulin_at_sophos.com: "2.6 path_lookup bug?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: tvrtko.ursulin@sophos.com Date: Wed, 8 Dec 2004 10:35:17 +0000
>>What would you expect to happen if one called:
>>
>>path_lookup("foo:/bar", &nd); ?
>>
>>I suspect there is something fishy going on there because when I do that
>>"/bar" gets destabilised and soon afterwards, another lookup on it will
>>BUG at dcache.c:276.
>
>dcache.h:276, sorry about that!
Ooops, my fault, please ignore the thread!
I was doing an unconditional path_release even if path_lookup failed.
Sorry once more!
-
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/
- Previous message: Michael Buesch: "Re: [PATCH, RFC] protect call to set_tsk_need_resched() by the rq-lock"
- Maybe in reply to: tvrtko.ursulin_at_sophos.com: "2.6 path_lookup bug?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|