From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: sg_set_page not usable for .bss? Date: Mon, 01 Dec 2008 22:55:29 -0800 (PST) Message-ID: <20081201.225529.137617862.davem@davemloft.net> References: <20081201.161418.51389602.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: john.haxby@oracle.com, netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org To: jengelh@medozas.de Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:40258 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751222AbYLBGz3 (ORCPT ); Tue, 2 Dec 2008 01:55:29 -0500 In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: From: Jan Engelhardt 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.