From: Borislav Petkov <bp@suse.de>
To: unknown <weidonghui@allwinnertech.com>, akpm@linux-foundation.org
Cc: maz@misterjones.org, will@kernel.org, rabin@rab.in,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] scripts/decodecode: fix faulting instruction no print when opps.file is DOS format
Date: Fri, 8 Oct 2021 12:35:31 +0200 [thread overview]
Message-ID: <YWAe81Ny7E1HhLGQ@zn.tnic> (raw)
In-Reply-To: <20211008064712.926-1-weidonghui@allwinnertech.com>
On Fri, Oct 08, 2021 at 02:47:12PM +0800, unknown wrote:
> From: weidonghui <weidonghui@allwinnertech.com>
>
> If opps.file is in DOS format, faulting instruction cannot be printed:
> / # ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-
> / # ./scripts/decodecode < oops.file
> [ 0.734345] Code: d0002881 912f9c21 94067e68 d2800001 (b900003f)
> aarch64-linux-gnu-strip: '/tmp/tmp.5Y9eybnnSi.o': No such file
> aarch64-linux-gnu-objdump: '/tmp/tmp.5Y9eybnnSi.o': No such file
> All code
> ========
> 0: d0002881 adrp x1, 0x512000
> 4: 912f9c21 add x1, x1, #0xbe7
> 8: 94067e68 bl 0x19f9a8
> c: d2800001 mov x1, #0x0 // #0
> 10: b900003f str wzr, [x1]
>
> Code starting with the faulting instruction
> ===========================================
>
> Background: The compilation environment is Ubuntu,
> and the test environment is Windows.
> Most logs are generated in the Windows environment.
> In this way, CR (carriage return) will inevitably appear,
> which will affect the use of decodecode in the Ubuntu environment.
> The repaired effect is as follows:
> / # ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-
> / # ./scripts/decodecode < oops.file
> [ 0.734345] Code: d0002881 912f9c21 94067e68 d2800001 (b900003f)
> All code
> ========
> 0: d0002881 adrp x1, 0x512000
> 4: 912f9c21 add x1, x1, #0xbe7
> 8: 94067e68 bl 0x19f9a8
> c: d2800001 mov x1, #0x0 // #0
> 10:* b900003f str wzr, [x1] <-- trapping instruction
>
> Code starting with the faulting instruction
> ===========================================
> 0: b900003f str wzr, [x1]
>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Marc Zyngier <maz@misterjones.org>
> Cc: Will Deacon <will@kernel.org>
> Cc: Rabin Vincent <rabin@rab.in>
> Cc: lkml <linux-kernel@vger.kernel.org>
> Signed-off-by: weidonghui <weidonghui@allwinnertech.com>
> ---
> scripts/decodecode | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/decodecode b/scripts/decodecode
> index 31d884e35f2f..c711a196511c 100755
> --- a/scripts/decodecode
> +++ b/scripts/decodecode
> @@ -126,7 +126,7 @@ if [ $marker -ne 0 ]; then
> fi
> echo Code starting with the faulting instruction > $T.aa
> echo =========================================== >> $T.aa
> -code=`echo $code | sed -e 's/ [<(]/ /;s/[>)] / /;s/ /,0x/g; s/[>)]$//'`
> +code=`echo $code | sed -e 's/\r//;s/ [<(]/ /;s/[>)] / /;s/ /,0x/g; s/[>)]$//'`
> echo -n " .$type 0x" > $T.s
> echo $code >> $T.s
> disas $T 0
> --
Acked-by: Borislav Petkov <bp@suse.de>
Andrew, you could clean up that commit message when applying.
Thx.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
prev parent reply other threads:[~2021-10-08 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 6:47 unknown
2021-10-08 10:35 ` Borislav Petkov [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=YWAe81Ny7E1HhLGQ@zn.tnic \
--to=bp@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@misterjones.org \
--cc=rabin@rab.in \
--cc=weidonghui@allwinnertech.com \
--cc=will@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
all inboxes | Powered by JetHome®