linux-kernel - Re: __initdata and struct dmi_system

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080914113316.GA27289@khazad-dum.debian.net>
Date:	Sun, 14 Sep 2008 08:33:16 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Németh Márton <nm127@...email.hu>
Cc:	LKML <linux-kernel@...r.kernel.org>, Helge Deller <deller@....de>,
	linux-input@...r.kernel.org
Subject: Re: __initdata and struct dmi_system_id?

On Sun, 14 Sep 2008, Németh Márton wrote:
> The other interesting question on this topic is that what about the
> error message strings which are used as parameter of the printk() calls.
> Those strings are combined together for a function which is marked with
> __init and the functions which are normal functions. The strings which
> are only used by the functions marked with __init could be freed, but
> the strings of the normal functions shouldn't be.

Yeah, if we could get them all in a init.rodata section, we could just throw
them away along with the init section afterwards...

I do think I have seen a patch about init.rodata in LKML not too long ago,
though.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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/