linux-kernel - Re: [PATCH 2/3] relay - make subbuf switch replaceable

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: <20080923131737.d5a8512d.akpm@linux-foundation.org>
Date:	Tue, 23 Sep 2008 13:17:37 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Tom Zanussi <zanussi@...cast.net>
Cc:	a.p.zijlstra@...llo.nl, prasad@...ux.vnet.ibm.com,
	mbligh@...gle.com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, tglx@...utronix.de,
	compudj@...stal.dyndns.org, rostedt@...dmis.org, od@...ell.com,
	fche@...hat.com, hch@....de, dwilder@...ibm.com
Subject: Re: [PATCH 2/3] relay - make subbuf switch replaceable

On Tue, 23 Sep 2008 00:27:30 -0500
Tom Zanussi <zanussi@...cast.net> wrote:

> Make the relay sub-buffer switch code replaceable.
>     
> With this patch, tracers now have complete control over the relay
> write (or reserve) path if they choose to do so, by implementing their
> own version of the sub-buffer switch function (switch_subbuf()), in
> addition to their own local write/reserve functions.  Tracers who
> choose not to do so automatically default to the normal behavior.
> 
>
> ...
>
> -EXPORT_SYMBOL_GPL(relay_switch_subbuf);
> +EXPORT_SYMBOL_GPL(switch_subbuf_default_callback);

It would be nice to keep the `relay_' prefix on the exported relay
interface?  Something called `switch_subbuf_default_callback' could
belong to pretty much anywhere in the kernel.


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