From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: checkstack.pl <large_number>
Date: Mon, 21 Feb 2005 13:38:11 +0100 [thread overview]
Message-ID: <20050221123811.GA13273@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <42163E2D.8050106@osdl.org>
On Fri, 18 February 2005 11:12:45 -0800, Randy.Dunlap wrote:
>
> In checkstack.pl, do you recall the reason for this code snippet:
>
> if ($size > 0x80000000) {
> $size = - $size;
> $size += 0x80000000;
> $size += 0x80000000;
> }
>
> There is one (unusual:) case where it fails. Is it needed?
Something like this is needed, also for unusual cases. gcc sometimes
decides to switch "sub 16" with "add -16". Later, when the stack
frame is popped back, the exchange goes vice versa.
Without this code, you'd see a few cases of nearly 4GiB.
> For arch/i386/kernel/efi_stub.S, checkstack reports:
>
> 0xc0116f5d efi_call_phys: 1073741824
> which is 0x4000_0000 (_ added for readability only), however the
> actual change in %esp there is __PAGE_OFFSET (0xc000_0000 on ia32),
>
> so if I alter the "if" test above to check for > 0xf000_0000,
> checkstack reports the correct value:
> 0xc0116f5d efi_call_phys: 3221225472
> which is 0xc000_0000.
>
>
> from objdump of efi_stub.o:
> 5: 81 ea 00 00 00 c0 sub $0xc0000000,%edx
>
> or I can just ignore it, like I've been doing for awhile...
Changing 0x8000_0000 to 0xf000_0000 would work for the add case as
well. Sounds like a sane change.
Checkstack could also do the ignoring for you, maybe like this:
if ($size > 0xf0000000) {
$size = - $size;
$size += 0x80000000;
$size += 0x80000000;
}
if ($size > 0x10000000) {
$size = 0;
}
Jörn
--
Ninety percent of everything is crap.
-- Sturgeon's Law
prev parent reply other threads:[~2005-02-21 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 19:12 Randy.Dunlap
2005-02-21 12:38 ` Jörn Engel [this message]
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=20050221123811.GA13273@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®