linux-kernel - Re: sg_set_page not usable for .bss?

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

Message-Id: <20081201.225529.137617862.davem@davemloft.net>
Date:	Mon, 01 Dec 2008 22:55:29 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	jengelh@...ozas.de
Cc:	john.haxby@...cle.com, netfilter-devel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: sg_set_page not usable for .bss?

From: Jan Engelhardt <jengelh@...ozas.de>
Date: Tue, 2 Dec 2008 02:41:02 +0100 (CET)

> 
> On Tuesday 2008-12-02 01:14, David Miller wrote:
> >> >> 
> >> >> Well, sysrq_password is in the .bss section, where as digest_password
> >> >> is on the heap due to being kmalloc'ed. Maybe that makes a difference?
> >> >> Someone more versed with the virtual memory layer might know.
> >> >
> >> >You can't use these interfaces on kernel image addresses.
> >> >
> >> Great :-)  So what is the best way to use the SHA1 crypto algo
> >> with in-kernel addresses?
> >
> >kmalloc and copy it there, or something like that, you just
> >can't use in-kernel addresses, ever.
> >
> Yes, kmalloc is already used. But then, what sort of address
> does kmalloc return, if not an address within kernelspace?
> (usually >=0xc0000000 on standard i386)

I said "kernel image" addresses are a problem, not "kernel space."

And by "kernel image" I mean addresses within the confines defined
by the sections of the vmlinux binary.
--
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/