linux-kernel - Re: [PATCH 1/1] kernel/torture.c: unmark torture_init_* as _

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: <20140416214730.GC4496@linux.vnet.ibm.com>
Date:	Wed, 16 Apr 2014 14:47:30 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Pranith Kumar <pranith@...ech.edu>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] kernel/torture.c: unmark torture_init_* as __inline

On Wed, Apr 16, 2014 at 05:34:26PM -0400, Pranith Kumar wrote:
> On Wed, Apr 16, 2014 at 4:44 PM, Paul E. McKenney
> <paulmck@...ux.vnet.ibm.com> wrote:
> > Good catch, queued for 3.16!  I missed it because of my habit of building
> > the torture tests directly into the kernel rather than loading them
> > as modules.  So thank you both for the patch and for your testing efforts!
> 
> You are welcome!
> 
> > Just out of curiosity, what are you thinking of using this for?
> >
> 
> I am exploring RCU in my research, looking for ways to apply the ideas
> to GPGPU and was studying the source code in the kernel. I will
> hopefully be using this in the future.

Nice!  Please let me know how it goes!

> (I should probably stick to userspace rcu :)

It might be better suited to your needs, but by all means continue
testing and inspecting the Linux-kernel RCU!  It does feel good to
get rid of some of the cruft, and I probably would never spot it.

Thank you again!

							Thanx, Paul

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