linux-kernel - Re: irda rmmod lockdep trace.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070313.192237.112853631.davem@davemloft.net>
Date:	Tue, 13 Mar 2007 19:22:37 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	samuel@...tiz.org
Cc:	davej@...hat.com, linux-kernel@...r.kernel.org, mingo@...hat.com
Subject: Re: irda rmmod lockdep trace.

From: Samuel Ortiz <samuel@...tiz.org>
Date: Wed, 14 Mar 2007 02:50:03 +0200

> On Mon, Mar 12, 2007 at 04:49:21PM -0700, David Miller wrote:
> > I would strongly caution against adding any run-time overhead just to
> > cure a false lockdep warning.  Even adding a new function argument
> > is too much IMHO.
> > 
> > Make the cost show up for lockdep only, perhaps by putting each
> > hashbin lock into a seperate locking class?
> Does that look better to you:

Yes, it does.:)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/