From: Mark Rutland <mark.rutland@arm.com>
To: yalin wang <yalin.wang2010@gmail.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
"lauraa@codeaurora.org" <lauraa@codeaurora.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"zlim.lnx@gmail.com" <zlim.lnx@gmail.com>,
Punit Agrawal <Punit.Agrawal@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"wcohen@redhat.com" <wcohen@redhat.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] arm64:use set_fixmap_offset to make it more clear
Date: Fri, 24 Jul 2015 10:56:18 +0100 [thread overview]
Message-ID: <20150724095618.GB23074@leverpostej> (raw)
In-Reply-To: <9E910A45-D4AB-44F6-878F-3CB2372B3660@gmail.com>
On Fri, Jul 24, 2015 at 04:56:59AM +0100, yalin wang wrote:
>
> > On Jul 23, 2015, at 21:03, Catalin Marinas <catalin.marinas@arm.com> wrote:
> >
> > On Thu, Jul 23, 2015 at 07:45:53PM +0800, yalin wang wrote:
> >> A little change to patch_map() function,
> >> use set_fixmap_offset() to make code more clear.
> >>
> >> Signed-off-by: yalin wang <yalin.wang2010@gmail.com>
> >> ---
> >> arch/arm64/kernel/insn.c | 5 ++---
> >> 1 file changed, 2 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/arch/arm64/kernel/insn.c b/arch/arm64/kernel/insn.c
> >> index dd9671c..7dafd5a 100644
> >> --- a/arch/arm64/kernel/insn.c
> >> +++ b/arch/arm64/kernel/insn.c
> >> @@ -101,9 +101,8 @@ static void __kprobes *patch_map(void *addr, int fixmap)
> >> return addr;
> >>
> >> BUG_ON(!page);
> >> - set_fixmap(fixmap, page_to_phys(page));
> >> -
> >> - return (void *) (__fix_to_virt(fixmap) + (uintaddr & ~PAGE_MASK));
> >> + return (void *)set_fixmap_offset(fixmap, page_to_phys(page) +
> >> + (addr & ~PAGE_MASK));
> >
> > It looks fine. Do you get any compiler warning for the automatic pointer
> > to long conversion? You may want to add some explicit casts, otherwise:
> >
> > Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> i have build it, there is no warning about this change. :)
I see no warnings with defconfig, but there's an (unrelated) set of warnings if
CONFIG_DEBUG_SET_MODULE_RONX or CONFIG_DEBUG_RODATA are enabled:
----
In file included from ./arch/arm64/include/asm/fixmap.h:85:0,
from arch/arm64/kernel/insn.c:32:
arch/arm64/kernel/insn.c: In function ‘__aarch64_insn_write’:
include/asm-generic/fixmap.h:73:2: warning: ‘addr’ may be used uninitialized in this function [-Wmaybe-uninitialized]
__set_fixmap(idx, phys, flags); \
^
include/asm-generic/fixmap.h:72:16: note: ‘addr’ was declared here
unsigned long addr; \
^
include/asm-generic/fixmap.h:79:2: note: in expansion of macro ‘__set_fixmap_offset’
__set_fixmap_offset(idx, phys, FIXMAP_PAGE_NORMAL)
^
arch/arm64/kernel/insn.c:104:17: note: in expansion of macro ‘set_fixmap_offset’
return (void *)set_fixmap_offset(fixmap, page_to_phys(page) +
^
----
That seems to be due to the definition of __set_fixmap_offset in
asm-generic/fixmap.h:
/* Return a pointer with offset calculated */
#define __set_fixmap_offset(idx, phys, flags) \
({ \
unsigned long addr; \
__set_fixmap(idx, phys, flags); \
addr = fix_to_virt(idx) + ((phys) & (PAGE_SIZE - 1)); \
addr; \
})
Where that new addr variable shadows patch_map's addr argument when the call to
__set_fixmap is expanded.
Which means that this patch currently breaks CONFIG_DEBUG_SET_MODULE_RONX and
CONFIG_DEBUG_RODATA.
Thanks,
Mark.
next prev parent reply other threads:[~2015-07-24 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 11:45 [RFC] arm64:use set_fixmap_offset to make it more clear yalin wang
2015-07-23 13:03 ` Catalin Marinas
2015-07-24 3:56 ` yalin wang
2015-07-24 9:56 ` Mark Rutland [this message]
2015-07-24 10:07 ` Mark Rutland
2015-07-24 11:53 ` yalin wang
2015-07-23 15:29 ` Laura Abbott
2015-07-24 11:52 ` [RFC V2] " yalin wang
2015-07-28 6:31 ` yalin wang
2015-07-28 8:47 ` Will Deacon
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=20150724095618.GB23074@leverpostej \
--to=mark.rutland@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=Punit.Agrawal@arm.com \
--cc=Will.Deacon@arm.com \
--cc=lauraa@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wcohen@redhat.com \
--cc=yalin.wang2010@gmail.com \
--cc=zlim.lnx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox