From: Masami Hiramatsu <mhiramat@kernel.org>
To: Zong Li <zong.li@sifive.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv <linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 8/9] riscv: introduce interfaces to patch kernel code
Date: Thu, 2 Apr 2020 10:17:33 +0900 [thread overview]
Message-ID: <20200402101733.1ef240faeaeada6e4d38ae80@kernel.org> (raw)
In-Reply-To: <CANXhq0ra3o+mgenbYLq_q0eZY2KiXNpWmo2V0amD0cFDqCQkXw@mail.gmail.com>
Hi,
On Wed, 1 Apr 2020 15:42:30 +0800
Zong Li <zong.li@sifive.com> wrote:
> > > +
> > > +static int __kprobes riscv_insn_write(void *addr, const void *insn, size_t len)
> >
> > Why would you add "riscv_" prefix for those functions? It seems a bit odd.
>
> There is no particular reason, I just was used to adding a prefix for
> arch-related stuff. I have no preference here, it's OK to me to remove
> the prefix of these functions, do you think we need to remove them?
Yeah, it will be better, unless it can mixed up with arch-independent
functions.
> > > +{
> > > + void *waddr = addr;
> > > + bool across_pages = (((uintptr_t) addr & ~PAGE_MASK) + len) > PAGE_SIZE;
> > > + unsigned long flags = 0;
> > > + int ret;
> > > +
> > > + raw_spin_lock_irqsave(&patch_lock, flags);
> >
> > This looks a bit odd since stop_machine() is protected by its own mutex,
> > and also the irq is already disabled here.
>
> We need it because we don't always enter the riscv_patch_text_nosync()
> through stop_machine mechanism. If we call the
> riscv_patch_text_nosync() directly, we need a lock to protect the
> page.
Oh, OK, but it leads another question. Is that safe to patch the
text without sync? Would you use it for UP system?
I think it is better to clarify "in what case user can call _nosync()"
and add a comment on it.
Thank you,
>
> >
> > Thank you,
> >
> > > +
> > > + if (across_pages)
> > > + patch_map(addr + len, FIX_TEXT_POKE1);
> > > +
> > > + waddr = patch_map(addr, FIX_TEXT_POKE0);
> > > +
> > > + ret = probe_kernel_write(waddr, insn, len);
> > > +
> > > + patch_unmap(FIX_TEXT_POKE0);
> > > +
> > > + if (across_pages)
> > > + patch_unmap(FIX_TEXT_POKE1);
> > > +
> > > + raw_spin_unlock_irqrestore(&patch_lock, flags);
> > > +
> > > + return ret;
> > > +}
> > > +#else
> > > +static int __kprobes riscv_insn_write(void *addr, const void *insn, size_t len)
> > > +{
> > > + return probe_kernel_write(addr, insn, len);
> > > +}
> > > +#endif /* CONFIG_MMU */
> > > +
> > > +int __kprobes riscv_patch_text_nosync(void *addr, const void *insns, size_t len)
> > > +{
> > > + u32 *tp = addr;
> > > + int ret;
> > > +
> > > + ret = riscv_insn_write(tp, insns, len);
> > > +
> > > + if (!ret)
> > > + flush_icache_range((uintptr_t) tp, (uintptr_t) tp + len);
> > > +
> > > + return ret;
> > > +}
> > > +
> > > +static int __kprobes riscv_patch_text_cb(void *data)
> > > +{
> > > + struct riscv_insn_patch *patch = data;
> > > + int ret = 0;
> > > +
> > > + if (atomic_inc_return(&patch->cpu_count) == 1) {
> > > + ret =
> > > + riscv_patch_text_nosync(patch->addr, &patch->insn,
> > > + GET_INSN_LENGTH(patch->insn));
> > > + atomic_inc(&patch->cpu_count);
> > > + } else {
> > > + while (atomic_read(&patch->cpu_count) <= num_online_cpus())
> > > + cpu_relax();
> > > + smp_mb();
> > > + }
> > > +
> > > + return ret;
> > > +}
> > > +
> > > +int __kprobes riscv_patch_text(void *addr, u32 insn)
> > > +{
> > > + struct riscv_insn_patch patch = {
> > > + .addr = addr,
> > > + .insn = insn,
> > > + .cpu_count = ATOMIC_INIT(0),
> > > + };
> > > +
> > > + return stop_machine_cpuslocked(riscv_patch_text_cb,
> > > + &patch, cpu_online_mask);
> > > +}
> > > --
> > > 2.25.1
> > >
> >
> >
> > --
> > Masami Hiramatsu <mhiramat@kernel.org>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-04-02 1:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 16:55 [PATCH v3 0/9] Support strict kernel memory permissions for security Zong Li
2020-03-09 16:55 ` [PATCH v3 1/9] riscv: add ARCH_HAS_SET_MEMORY support Zong Li
2020-03-09 16:55 ` [PATCH v3 2/9] riscv: add ARCH_HAS_SET_DIRECT_MAP support Zong Li
2020-03-09 16:55 ` [PATCH v3 3/9] riscv: add ARCH_SUPPORTS_DEBUG_PAGEALLOC support Zong Li
2020-03-09 16:55 ` [PATCH v3 4/9] riscv: move exception table immediately after RO_DATA Zong Li
2020-03-09 16:55 ` [PATCH v3 5/9] riscv: add alignment for text, rodata and data sections Zong Li
2020-03-09 16:55 ` [PATCH v3 6/9] riscv: add STRICT_KERNEL_RWX support Zong Li
2020-03-09 16:55 ` [PATCH v3 7/9] riscv: add macro to get instruction length Zong Li
2020-03-09 16:55 ` [PATCH v3 8/9] riscv: introduce interfaces to patch kernel code Zong Li
2020-03-31 15:32 ` Masami Hiramatsu
2020-04-01 7:42 ` Zong Li
2020-04-02 1:17 ` Masami Hiramatsu [this message]
2020-04-03 9:04 ` Zong Li
2020-04-04 3:14 ` Masami Hiramatsu
2020-04-04 12:12 ` Zong Li
2020-04-06 10:36 ` Zong Li
2020-04-07 12:29 ` Masami Hiramatsu
2020-04-07 13:06 ` Zong Li
2020-03-09 16:55 ` [PATCH v3 9/9] riscv: patch code by fixmap mapping Zong Li
2020-03-31 13:32 ` [PATCH v3 0/9] Support strict kernel memory permissions for security Masami Hiramatsu
2020-04-01 7:18 ` Zong Li
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=20200402101733.1ef240faeaeada6e4d38ae80@kernel.org \
--to=mhiramat@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=zong.li@sifive.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
Powered by JetHome