Date: Mon, 01 Dec 2008 22:55:29 -0800 (PST)
Message-Id: <20081201.225529.137617862.davem@davemloft.net>
To: jengelh@medozas.de
Cc: john.haxby@oracle.com, netfilter-devel@vger.kernel.org,
       linux-kernel@vger.kernel.org
Subject: Re: sg_set_page not usable for .bss?
From: David Miller <davem@davemloft.net>
In-Reply-To: <alpine.LNX.1.10.0812020237520.23359@fbirervta.pbzchgretzou.qr>
References: <alpine.LNX.1.10.0812020112480.19492@fbirervta.pbzchgretzou.qr>
	<20081201.161418.51389602.davem@davemloft.net>
	<alpine.LNX.1.10.0812020237520.23359@fbirervta.pbzchgretzou.qr>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1250
Lines: 31

From: Jan Engelhardt <jengelh@medozas.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/