From: David Miller <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?
Date: Mon, 01 Dec 2008 22:55:29 -0800 (PST) [thread overview]
Message-ID: <20081201.225529.137617862.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0812020237520.23359@fbirervta.pbzchgretzou.qr>
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.
next prev parent reply other threads:[~2008-12-02 6:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 12:28 [PATCH] More secure SYSRQ for xtables-addons John Haxby
2008-12-01 19:34 ` Jan Engelhardt
2008-12-01 22:02 ` John Haxby
2008-12-01 22:37 ` Jan Engelhardt
2008-12-01 22:40 ` sg_set_page not usable for .bss? Jan Engelhardt
2008-12-02 0:10 ` David Miller
2008-12-02 0:13 ` Jan Engelhardt
2008-12-02 0:14 ` David Miller
2008-12-02 1:41 ` Jan Engelhardt
2008-12-02 6:55 ` David Miller [this message]
2008-12-02 1:39 ` [PATCH] More secure SYSRQ for xtables-addons Patrick McHardy
2008-12-02 1:53 ` Jan Engelhardt
2008-12-02 9:43 ` John Haxby
2008-12-02 17:46 ` John Haxby
2008-12-12 8:38 ` John Haxby
2008-12-13 22:14 ` Jan Engelhardt
2008-12-15 12:09 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081201.225529.137617862.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=john.haxby@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).