From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Brian Masney <masneyb@onstation.org>
Cc: robdclark@gmail.com, bjorn.andersson@linaro.org, joro@8bytes.org,
agross@kernel.org, iommu@lists.linux-foundation.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/qcom: fix NULL pointer dereference during probe deferral
Date: Wed, 1 Jan 2020 19:18:57 +0100 [thread overview]
Message-ID: <20200101181857.GB2110@latitude> (raw)
In-Reply-To: <20200101033949.755-1-masneyb@onstation.org>
[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]
On Tue, Dec 31, 2019 at 10:39:49PM -0500, Brian Masney wrote:
[...]
> (kernel_init) from ret_from_fork (arch/arm/kernel/entry-common.S:156)
> Exception stack(0xee89dfb0 to 0xee89dff8)
> dfa0: 00000000 00000000 00000000 00000000
> dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
> Code: e92d4070 e1a04000 e3a01004 e240501c (e5930014)
This looks like ARM code...
> All code
> ========
> 0: 70 40 jo 0x42
> 2: 2d e9 00 40 a0 sub $0xa04000e9,%eax
> 7: e1 04 loope 0xd
> 9: 10 a0 e3 1c 50 40 adc %ah,0x40501ce3(%rax)
> f: e2 14 loop 0x25
> 11:* 00 .byte 0x0 <-- trapping instruction
> 12: 93 xchg %eax,%ebx
> 13: e5 .byte 0xe5
... disassembled as x86 code.
I suspect that scripts/decodecode picked up the wrong architecture
somehow. Perhaps CROSS_COMPILE wasn't set?
>
> Code starting with the faulting instruction
> ===========================================
> 0: 14 00 adc $0x0,%al
> 2: 93 xchg %eax,%ebx
> 3: e5 .byte 0xe5
Greetings and a happy new year,
Jonathan Neuschäfer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Brian Masney <masneyb@onstation.org>
Cc: linux-arm-msm@vger.kernel.org, iommu@lists.linux-foundation.org,
bjorn.andersson@linaro.org, agross@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/qcom: fix NULL pointer dereference during probe deferral
Date: Wed, 1 Jan 2020 19:18:57 +0100 [thread overview]
Message-ID: <20200101181857.GB2110@latitude> (raw)
In-Reply-To: <20200101033949.755-1-masneyb@onstation.org>
[-- Attachment #1.1: Type: text/plain, Size: 1453 bytes --]
On Tue, Dec 31, 2019 at 10:39:49PM -0500, Brian Masney wrote:
[...]
> (kernel_init) from ret_from_fork (arch/arm/kernel/entry-common.S:156)
> Exception stack(0xee89dfb0 to 0xee89dff8)
> dfa0: 00000000 00000000 00000000 00000000
> dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
> Code: e92d4070 e1a04000 e3a01004 e240501c (e5930014)
This looks like ARM code...
> All code
> ========
> 0: 70 40 jo 0x42
> 2: 2d e9 00 40 a0 sub $0xa04000e9,%eax
> 7: e1 04 loope 0xd
> 9: 10 a0 e3 1c 50 40 adc %ah,0x40501ce3(%rax)
> f: e2 14 loop 0x25
> 11:* 00 .byte 0x0 <-- trapping instruction
> 12: 93 xchg %eax,%ebx
> 13: e5 .byte 0xe5
... disassembled as x86 code.
I suspect that scripts/decodecode picked up the wrong architecture
somehow. Perhaps CROSS_COMPILE wasn't set?
>
> Code starting with the faulting instruction
> ===========================================
> 0: 14 00 adc $0x0,%al
> 2: 93 xchg %eax,%ebx
> 3: e5 .byte 0xe5
Greetings and a happy new year,
Jonathan Neuschäfer
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-01-01 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 3:39 [PATCH] iommu/qcom: fix NULL pointer dereference during probe deferral Brian Masney
2020-01-01 3:39 ` Brian Masney
2020-01-01 11:44 ` Stephan Gerhold
2020-01-01 11:44 ` Stephan Gerhold
2020-01-01 18:18 ` Jonathan Neuschäfer [this message]
2020-01-01 18:18 ` Jonathan Neuschäfer
2020-01-07 13:25 ` Joerg Roedel
2020-01-07 13:25 ` Joerg Roedel
2020-01-07 14:00 ` Brian Masney
2020-01-07 14:00 ` Brian Masney
2020-01-07 15:44 ` Joerg Roedel
2020-01-07 15:44 ` Joerg Roedel
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=20200101181857.GB2110@latitude \
--to=j.neuschaefer@gmx.net \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masneyb@onstation.org \
--cc=robdclark@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.