linux-kernel - Re: [PATCH] Delegate unknown module parameters to interested parties

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]

Date:	Wed, 10 Nov 2010 16:21:28 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Chris Wilson <chris@...is-wilson.co.uk>,
	Yuanhan Liu <yuanhan.liu@...ux.intel.com>,
	linux-kernel@...r.kernel.org, fweisbec@...il.com, mingo@...hat.com
Subject: Re: [PATCH] Delegate unknown module parameters to interested parties

On Wed, 10 Nov 2010 01:09:21 am Steven Rostedt wrote:
> [ Added Rusty "Module God" Russell ]

And I also wrote the parameter parsing code, so sending to me is probably
a good idea.

So, what's this for?  You want trace= as a standard module parameter
or something?  If this is a once-off I'd prefer a custom hack I think.
If you can think of other users, this might be a good idea; though don't
use "void *data" use an explicit struct module *...

Cheers,
Rusty.
--
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/