linux-kernel - Re: [PATCH] Fix WARN_ON / WARN_ON

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: <1159920569.8035.71.camel@localhost.localdomain>
Date:	Tue, 03 Oct 2006 17:09:29 -0700
From:	Tim Chen <tim.c.chen@...ux.intel.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	herbert@...dor.apana.org.au, linux-kernel@...r.kernel.org,
	leonid.i.ananiev@...el.com
Subject: Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression

On Tue, 2006-10-03 at 17:07 -0700, Andrew Morton wrote:

> 
> Perhaps the `static int __warn_once' is getting put in the same cacheline
> as some frequently-modified thing.   Perhaps try marking that as __read_mostly?
> 

I've tried marking static int __warn_once as __read_mostly.  However, it
did not help with reducing the cache miss :(

So I would suggest reversing the "Let WARN_ON/WARN_ON_ONCE return the
condition" patch.  It has just been added 3 days ago so reversing it
should not be a problem.

Tim
-
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/