linux-kernel - Re: [PATCH 1/1] rcu: cleanup: make rcutorture specific definitions depend on config value

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: <CAJhHMCAcahHKaXvCVZL51aUhdiejT_T5-vqJ+08D40HrH3cS_A@mail.gmail.com>
Date:	Mon, 21 Apr 2014 14:08:48 -0400
From:	Pranith Kumar <bobby.prani@...il.com>
To:	Paul McKenney <paulmck@...ux.vnet.ibm.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] rcu: cleanup: make rcutorture specific definitions
 depend on config value

On Mon, Apr 21, 2014 at 11:50 AM, Paul E. McKenney
<paulmck@...ux.vnet.ibm.com> wrote:
>
> Good observation, but this approach prevents someone from building an
> rcutorture module after the fact for a kernel that was built with
> CONFIG_RCU_TORTURE_TEST=n.  So I have to say "no" on this one.
>

OK, I did not consider that case!  I will keep my eyes open while
studying the code.

Regards,
-- 
Pranith
--
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/