linux-kernel - Re: [ANNOUNCE] 3.0-rt4

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]

Message-ID: <alpine.LFD.2.02.1107281134310.2660@ionos>
Date:	Thu, 28 Jul 2011 11:37:46 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	"Nikita V. Youshchenko" <yoush@...msu.su>
cc:	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-rt-users <linux-rt-users@...r.kernel.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Jason Wessel <jason.wessel@...driver.com>,
	lasaine@....cs.msu.su
Subject: Re: [ANNOUNCE] 3.0-rt4

On Thu, 28 Jul 2011, Nikita V. Youshchenko wrote:

> > On Thu, 2011-07-28 at 12:24 +0400, Nikita V. Youshchenko wrote:
> > > (*) we need >1G of memory for data buffers, and have too much legacy
> > > software components so moving to 64bit system is not practical within
> > > available resource
> >
> > You can run a complete 32bit userspace on a 64bit kernel without any
> > problems.
> 
> ... expect shared data between kernel and userspace (structures passed over 
> ioctl()s, structures in mmapped buffers). Unfortunately, in scope of our 
> project (that lasts since 2001 or so), we do have such issues :(.

Aside of that being horrid, it's trivial to solve with proper data
types. u32 and friends are there for a reason. But feel free to get
the highmem thing working again :)

Thanks,

	tglx

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