[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167293236954.1466313.6328356338655300899.b4-ty@kernel.org>
Date: Thu, 5 Jan 2023 18:03:57 +0000
From: Will Deacon <will@...nel.org>
To: guo.ziliang@....com.cn
Cc: catalin.marinas@....com, kernel-team@...roid.com,
Will Deacon <will@...nel.org>, lkp@...el.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
huang.junhua@....com.cn
Subject: Re: [PATCH] arm64/uprobes: change the uprobe_opcode_t typedef to fix the sparse warning
On Wed, 28 Dec 2022 09:54:12 +0800 (CST), guo.ziliang@....com.cn wrote:
> From: junhua huang <huang.junhua@....com.cn>
>
> After we fixed the uprobe inst endian in aarch_be, the sparse check report
> the following warning info:
>
> sparse warnings: (new ones prefixed by >>)
> >> kernel/events/uprobes.c:223:25: sparse: sparse: restricted __le32 degrades to integer
> >> kernel/events/uprobes.c:574:56: sparse: sparse: incorrect type in argument 4 (different base types)
> @@ expected unsigned int [addressable] [usertype] opcode @@ got restricted __le32 [usertype] @@
> kernel/events/uprobes.c:574:56: sparse: expected unsigned int [addressable] [usertype] opcode
> kernel/events/uprobes.c:574:56: sparse: got restricted __le32 [usertype]
> >> kernel/events/uprobes.c:1483:32: sparse: sparse: incorrect type in initializer (different base types)
> @@ expected unsigned int [usertype] insn @@ got restricted __le32 [usertype] @@
> kernel/events/uprobes.c:1483:32: sparse: expected unsigned int [usertype] insn
> kernel/events/uprobes.c:1483:32: sparse: got restricted __le32 [usertype]
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64/uprobes: change the uprobe_opcode_t typedef to fix the sparse warning
https://git.kernel.org/arm64/c/ef08c0fadd8a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists