From: Paul Walmsley <paul.walmsley@sifive.com> To: linux-riscv@lists.infradead.org Cc: linux-kernel@vger.kernel.org, Alan Kao <alankao@andestech.com> Subject: [PATCH 8/8] riscv: fp: add missing __user pointer annotations Date: Thu, 17 Oct 2019 17:49:29 -0700 [thread overview] Message-ID: <20191018004929.3445-9-paul.walmsley@sifive.com> (raw) In-Reply-To: <20191018004929.3445-1-paul.walmsley@sifive.com> The __user annotations were removed from the {save,restore}_fp_state() function signatures by commit 007f5c358957 ("Refactor FPU code in signal setup/return procedures"), but should be present, and sparse warns when they are not applied. Add them back in. This change should have no functional impact. Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com> Fixes: 007f5c358957 ("Refactor FPU code in signal setup/return procedures") Cc: Alan Kao <alankao@andestech.com> --- arch/riscv/kernel/signal.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/riscv/kernel/signal.c b/arch/riscv/kernel/signal.c index 85c700ad47e9..9437167f463e 100644 --- a/arch/riscv/kernel/signal.c +++ b/arch/riscv/kernel/signal.c @@ -28,7 +28,7 @@ struct rt_sigframe { #ifdef CONFIG_FPU static long restore_fp_state(struct pt_regs *regs, - union __riscv_fp_state *sc_fpregs) + union __riscv_fp_state __user *sc_fpregs) { long err; struct __riscv_d_ext_state __user *state = &sc_fpregs->d; @@ -55,7 +55,7 @@ static long restore_fp_state(struct pt_regs *regs, } static long save_fp_state(struct pt_regs *regs, - union __riscv_fp_state *sc_fpregs) + union __riscv_fp_state __user *sc_fpregs) { long err; struct __riscv_d_ext_state __user *state = &sc_fpregs->d; -- 2.23.0
WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <paul.walmsley@sifive.com> To: linux-riscv@lists.infradead.org Cc: linux-kernel@vger.kernel.org, Alan Kao <alankao@andestech.com> Subject: [PATCH 8/8] riscv: fp: add missing __user pointer annotations Date: Thu, 17 Oct 2019 17:49:29 -0700 [thread overview] Message-ID: <20191018004929.3445-9-paul.walmsley@sifive.com> (raw) In-Reply-To: <20191018004929.3445-1-paul.walmsley@sifive.com> The __user annotations were removed from the {save,restore}_fp_state() function signatures by commit 007f5c358957 ("Refactor FPU code in signal setup/return procedures"), but should be present, and sparse warns when they are not applied. Add them back in. This change should have no functional impact. Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com> Fixes: 007f5c358957 ("Refactor FPU code in signal setup/return procedures") Cc: Alan Kao <alankao@andestech.com> --- arch/riscv/kernel/signal.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/riscv/kernel/signal.c b/arch/riscv/kernel/signal.c index 85c700ad47e9..9437167f463e 100644 --- a/arch/riscv/kernel/signal.c +++ b/arch/riscv/kernel/signal.c @@ -28,7 +28,7 @@ struct rt_sigframe { #ifdef CONFIG_FPU static long restore_fp_state(struct pt_regs *regs, - union __riscv_fp_state *sc_fpregs) + union __riscv_fp_state __user *sc_fpregs) { long err; struct __riscv_d_ext_state __user *state = &sc_fpregs->d; @@ -55,7 +55,7 @@ static long restore_fp_state(struct pt_regs *regs, } static long save_fp_state(struct pt_regs *regs, - union __riscv_fp_state *sc_fpregs) + union __riscv_fp_state __user *sc_fpregs) { long err; struct __riscv_d_ext_state __user *state = &sc_fpregs->d; -- 2.23.0 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-10-18 0:50 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-18 0:49 [PATCH 0/8] riscv: resolve most warnings from sparse Paul Walmsley 2019-10-18 0:49 ` Paul Walmsley 2019-10-18 0:49 ` [PATCH 1/8] riscv: add prototypes for assembly language functions from entry.S Paul Walmsley 2019-10-18 0:49 ` Paul Walmsley 2019-10-18 0:49 ` [PATCH 2/8] riscv: add prototypes for assembly language functions from head.S Paul Walmsley 2019-10-18 0:49 ` Paul Walmsley 2019-10-18 1:15 ` Paul Walmsley 2019-10-18 1:15 ` Paul Walmsley 2019-10-18 0:49 ` [PATCH 3/8] riscv: init: merge split string literals in preprocessor directive Paul Walmsley 2019-10-18 0:49 ` Paul Walmsley 2019-10-18 4:02 ` Luc Van Oostenryck 2019-10-18 4:02 ` Luc Van Oostenryck 2019-10-18 4:38 ` Paul Walmsley 2019-10-18 4:38 ` Paul Walmsley 2019-10-18 5:28 ` Luc Van Oostenryck 2019-10-18 5:28 ` Luc Van Oostenryck 2019-10-18 5:47 ` Luc Van Oostenryck 2019-10-18 5:47 ` Luc Van Oostenryck 2019-10-18 6:08 ` Paul Walmsley 2019-10-18 6:08 ` Paul Walmsley 2019-10-18 0:49 ` [PATCH 4/8] riscv: ensure RISC-V C model definitions are passed to static analyzers Paul Walmsley 2019-10-18 0:49 ` Paul Walmsley 2019-10-18 4:06 ` Luc Van Oostenryck 2019-10-18 4:06 ` Luc Van Oostenryck 2019-10-18 4:39 ` Paul Walmsley 2019-10-18 4:39 ` Paul Walmsley 2019-10-18 5:25 ` Luc Van Oostenryck 2019-10-18 5:25 ` Luc Van Oostenryck 2019-10-22 15:09 ` Palmer Dabbelt 2019-10-22 15:09 ` Palmer Dabbelt 2019-10-28 22:11 ` Luc Van Oostenryck 2019-10-28 22:11 ` Luc Van Oostenryck 2019-10-18 0:49 ` [PATCH 5/8] riscv: add missing prototypes Paul Walmsley 2019-10-18 0:49 ` Paul Walmsley 2019-10-18 4:15 ` Luc Van Oostenryck 2019-10-18 4:15 ` Luc Van Oostenryck 2019-10-18 6:06 ` Paul Walmsley 2019-10-18 6:06 ` Paul Walmsley 2019-10-18 0:49 ` [PATCH 6/8] riscv: mark some code and data as file-static Paul Walmsley 2019-10-18 0:49 ` Paul Walmsley 2019-10-18 0:49 ` [PATCH 7/8] riscv: add missing header file includes Paul Walmsley 2019-10-18 0:49 ` Paul Walmsley 2019-10-18 0:49 ` Paul Walmsley [this message] 2019-10-18 0:49 ` [PATCH 8/8] riscv: fp: add missing __user pointer annotations Paul Walmsley 2019-10-18 3:12 ` [PATCH 0/8] riscv: resolve most warnings from sparse Anup Patel 2019-10-18 3:12 ` Anup Patel
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=20191018004929.3445-9-paul.walmsley@sifive.com \ --to=paul.walmsley@sifive.com \ --cc=alankao@andestech.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ /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: linkBe 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.