linux-kernel - Re: [PATCH 10/15] module_param: make bool parameters really bool (core code)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <87ty4xnvxw.fsf@rustcorp.com.au>
Date:	Mon, 19 Dec 2011 12:50:59 +1030
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	paulmck@...ux.vnet.ibm.com
Cc:	lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Pawel Moll <pawel.moll@....com>
Subject: Re: [PATCH 10/15] module_param: make bool parameters really bool (core code)

On Fri, 16 Dec 2011 11:58:30 -0800, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:
> On Thu, Dec 15, 2011 at 01:43:24PM +1030, Rusty Russell wrote:
> > module_param(bool) used to counter-intuitively take an int.  In
> > fddd5201 (mid-2009) we allowed bool or int/unsigned int using a messy
> > trick.
> > 
> > It's time to remove the int/unsigned int option.  For this version
> > it'll simply give a warning, but it'll break next kernel version.
> > 
> > Signed-off-by: Rusty Russell <rusty@...tcorp.com.au>
> 
> For the rcutorture component:
> 
> Acked-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> Tested-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> 
> Given that this portion of the patch is self-sufficient, I have queued
> the rcutorture portion of this patch with your signed-off-by, which I
> can push for either 3.3 or 3.4 (default is most likely 3.4).  Of course,
> if you would prefer some other approach, please let me know.

Nope, more than happy.  Have removed it from my patch.

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/