| 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
| ||
|
Date: Sun, 3 May 2009 23:57:09 +0200 From: Pavel Machek <pavel@....cz> To: Sam Ravnborg <sam@...nborg.org> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Linus Torvalds <torvalds@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, Tim Abbott <tabbott@....EDU> Subject: Re: in_suspend and __nosave Hi! > While unifying vmlinux.lds for x86 I stumbled > over the .data.nosave section. > > Searching a bit I found only a single user: > > swsusp.c:int in_suspend __nosavedata = 0; > > Do we really needs all this complexity for this single integer? > We have this section defined in several arch lds files. Well, original idea was that drivers may need some memory that's not affected by hibernation/restore.... > It also occur to me that only: x86, powerpc, and sh > implement pfn_is_nosave() which I think is the only > place where we decide if we want to save a page or not. > > But we define the .data.nosave section in following > architectures: > arm, m32r, mips, mn10300, parisc, s390 in addition > to the above archs that define pfn_is_nosave(). > Is this something to be cleaned up? I guess people were just too happy with cut&paste. Ouch and someone was working on arm hibernation, iIRC. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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/
Powered by blists - more mailing lists