linux-kernel - Re: [PATCH 17/20] tracing: don't trace the BKL

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] [day] [month] [year] [list]

Message-ID: <20110125222828.GA2532@nowhere>
Date:	Tue, 25 Jan 2011 23:28:31 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 17/20] tracing: don't trace the BKL

On Tue, Jan 25, 2011 at 11:17:31PM +0100, Arnd Bergmann wrote:
> No reason to trace it when the last user is gone.
> 
> Signed-off-by: Arnd Bergmann <arnd@...db.de>

Acked-by: Frederic Weisbecker <fweisbec@...il.com>

You could also remove file and line arguments from _(un)lock_kernel
but as the final removal follows, we just don't care.

Tell us if you want that in the tracing tree. But I guess this
should be included in the same set than the rest or?

Thanks!
--
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/