From: Jisheng Zhang <jszhang3@mail.ustc.edu.cn>
To: Vincent Chen <vincent.chen@sifive.com>
Cc: oleg@redhat.com, palmer@dabbelt.com, linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2] riscv: Ensure the value of FP registers in the core dump file is up to date
Date: Mon, 9 Aug 2021 00:47:26 +0800 [thread overview]
Message-ID: <20210809004726.583b43db@xhacker> (raw)
In-Reply-To: <1627982871-29807-1-git-send-email-vincent.chen@sifive.com>
On Tue, 3 Aug 2021 17:27:51 +0800
Vincent Chen <vincent.chen@sifive.com> wrote:
> The value of FP registers in the core dump file comes from the
> thread.fstate. However, kernel saves the FP registers to the thread.fstate
> only before scheduling out the process. If no process switch happens
> during the exception handling process, kernel will not have a chance to
> save the latest value of FP registers to thread.fstate. It will cause the
> value of FP registers in the core dump file may be incorrect. To solve this
> problem, this patch force lets kernel save the FP register into the
> thread.fstate if the target task_struct equals the current.
Nice catch! I think there's another case too: since last kernel save, the FP
registers has been modified by the userspace, we also need to force fstate_save()
This patch fixes both cases.
>
> Signed-off-by: Vincent Chen <vincent.chen@sifive.com>
Reviewed-by: Jisheng Zhang <jszhang@kernel.org>
>
> ---
> Changes since the v1 patch
> 1. Include switch_to.h to avoid compiling error.
>
> ---
> arch/riscv/kernel/ptrace.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/riscv/kernel/ptrace.c b/arch/riscv/kernel/ptrace.c
> index 1a85305720e8..9c0511119bad 100644
> --- a/arch/riscv/kernel/ptrace.c
> +++ b/arch/riscv/kernel/ptrace.c
> @@ -10,6 +10,7 @@
> #include <asm/ptrace.h>
> #include <asm/syscall.h>
> #include <asm/thread_info.h>
> +#include <asm/switch_to.h>
> #include <linux/audit.h>
> #include <linux/ptrace.h>
> #include <linux/elf.h>
> @@ -56,6 +57,9 @@ static int riscv_fpr_get(struct task_struct *target,
> {
> struct __riscv_d_ext_state *fstate = &target->thread.fstate;
>
> + if (target == current)
> + fstate_save(current, task_pt_regs(current));
> +
> membuf_write(&to, fstate, offsetof(struct __riscv_d_ext_state, fcsr));
> membuf_store(&to, fstate->fcsr);
> return membuf_zero(&to, 4); // explicitly pad
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-08-08 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 9:27 [PATCH v2] riscv: Ensure the value of FP registers in the core dump file is up to date Vincent Chen
2021-08-08 16:47 ` Jisheng Zhang [this message]
2021-08-25 4:44 ` Palmer Dabbelt
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=20210809004726.583b43db@xhacker \
--to=jszhang3@mail.ustc.edu.cn \
--cc=linux-riscv@lists.infradead.org \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=vincent.chen@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 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.