linux-kernel - Re: [RFC][PATCH] extable: Make sure all archs define

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:	Fri, 20 May 2011 11:04:31 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Richard Henderson <rth@...ddle.net>
Cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	Matt Turner <mattst88@...il.com>, linux-alpha@...r.kernel.org,
	Hirokazu Takata <takata@...ux-m32r.org>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Roman Zippel <zippel@...ux-m68k.org>,
	linux-m68k@...r.kernel.org, Ralf Baechle <ralf@...ux-mips.org>,
	Kyle McMartin <kyle@...artin.ca>, Helge Deller <deller@....de>,
	"JamesE.J.Bottomley" <jejb@...isc-linux.org>
Subject: Re: [RFC][PATCH] extable: Make sure all archs define _sdata

On Fri, 2011-05-20 at 07:28 -0700, Richard Henderson wrote:

> Although I suppose if we're supposedly standardizing on _sdata,
> the two uses of _data in arch/alpha/mm/ could be transitioned.
> 

If we start getting more uses of _sdata, then perhaps this would be a
good idea.

Currently I only need it to know if a pointer passed in to one of my
functions can be freed or not. If the pointer is pointing to a struct in
the core kernel data, it is safe from being freed. Anything else will
need the extra work to keep it safe (rcu logic and such) and takes a
path with a bit more overhead.

Thanks!

-- Steve


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