From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix markup_oops to work with 32-bit userspace on a 64-bit kernel
Date: Thu, 06 Aug 2009 15:05:17 +0300 [thread overview]
Message-ID: <4A7AC6FD.6080600@pardus.org.tr> (raw)
In-Reply-To: <20090713141819.GG24310@parisc-linux.org>
Matthew Wilcox wrote On 13-07-2009 17:18:
> A 32-bit perl can't handle 64-bit addresses without using the BigInt package.
>
>
> -my $decodestart = hex($target) - hex($func_offset);
> -my $decodestop = hex($target) + 8192;
> +my $decodestart = Math::BigInt->from_hex("0x$target") - Math::BigInt->from_hex("0x$func_offset");
> +my $decodestop = Math::BigInt->from_hex("0x$target") + 8192;
> if ($target eq "0") {
> print "No oops found!\n";
> print "Usage: \n";
>
$func_offset has already "0x" so this commit prepends another "0x"
causing decodestart to be NaN.
Regards,
Ozan
prev parent reply other threads:[~2009-08-06 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 14:18 [PATCH] Fix markup_oops to work with 32-bit userspace on a 64-bit kernel Matthew Wilcox
2009-07-13 15:08 ` Arjan van de Ven
2009-08-06 12:05 ` Ozan Çağlayan [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=4A7AC6FD.6080600@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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