From: ebiederm@xmission.com (Eric W. Biederman)
To: Guenter Roeck <linux@roeck-us.net>
Cc: James Hogan <jhogan@kernel.org>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH -next] signal/mips: Report FPE_FLTUNK for undiagnosed floating point exceptions
Date: Wed, 16 May 2018 20:13:10 -0500 [thread overview]
Message-ID: <87k1s3jd95.fsf@xmission.com> (raw)
In-Reply-To: <1526392247-25512-1-git-send-email-linux@roeck-us.net> (Guenter Roeck's message of "Tue, 15 May 2018 06:50:47 -0700")
Guenter Roeck <linux@roeck-us.net> writes:
> Most mips builds fail with
>
> arch/mips/kernel/traps.c: In function ‘force_fcr31_sig’:
> arch/mips/kernel/traps.c:732:2: error:
> ‘si_code’ may be used uninitialized in this function
>
> Fix the problem by initializing si_code with FPE_FLTUNK (undiagnosed
> floating point exception).
>
> Fixes: f43a54a0d916 ("signal/mips: Use force_sig_fault where appropriate")
> Cc: linux-mips@linux-mips.org
> Cc: Eric W. Biederman <ebiederm@xmission.com>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Applied. Thank you.
Eric
> ---
> Feel free to merge into the patch introducing the problem.
>
> arch/mips/kernel/traps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/kernel/traps.c b/arch/mips/kernel/traps.c
> index 66ec4b0b484d..d67fa74622ee 100644
> --- a/arch/mips/kernel/traps.c
> +++ b/arch/mips/kernel/traps.c
> @@ -716,7 +716,7 @@ asmlinkage void do_ov(struct pt_regs *regs)
> void force_fcr31_sig(unsigned long fcr31, void __user *fault_addr,
> struct task_struct *tsk)
> {
> - int si_code;
> + int si_code = FPE_FLTUNK;
>
> if (fcr31 & FPU_CSR_INV_X)
> si_code = FPE_FLTINV;
prev parent reply other threads:[~2018-05-17 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 13:50 [PATCH -next] signal/mips: Report FPE_FLTUNK for undiagnosed floating point exceptions Guenter Roeck
2018-05-17 1:13 ` Eric W. Biederman [this message]
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=87k1s3jd95.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@roeck-us.net \
--cc=ralf@linux-mips.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: 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