From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [take12 3/3] kevent: Timer notifications. Date: Mon, 21 Aug 2006 13:27:22 +0200 Message-ID: <1156159642.23756.144.camel@laptopd505.fenrus.org> References: <11561555893621@2ka.mipt.ru> <1156155589287@2ka.mipt.ru> <20060821111239.GA30945@infradead.org> <20060821111848.GB8608@2ka.mipt.ru> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , lkml , David Miller , Ulrich Drepper , Andrew Morton , netdev , Zach Brown , tglx@linutronix.de Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:63150 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S964961AbWHUL1l (ORCPT ); Mon, 21 Aug 2006 07:27:41 -0400 To: Evgeniy Polyakov In-Reply-To: <20060821111848.GB8608@2ka.mipt.ru> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Mon, 2006-08-21 at 15:18 +0400, Evgeniy Polyakov wrote: > ]> > + lockdep_set_class(&t->ktimer_storage.lock, &kevent_timer_key); > > > > When looking at the kevent_storage_init callers most need to do > > those lockdep_set_class class. Shouldn't kevent_storage_init just > > get a "struct lock_class_key *" argument? > > It will not work, since inode is used for both socket and inode > notifications (to save some space in struct sock), lockdep initalization > is performed on the highest level, so I put it alone. Call me a cynic, but I'm always a bit sceptical about needing lockdep annotations like this... Can you explain why you need it in this case, including the proof that it's safe?