[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2110240622100.45807@angie.orcam.me.uk>
Date: Sun, 24 Oct 2021 06:24:17 +0200 (CEST)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>,
Al Viro <viro@...IV.linux.org.uk>,
Kees Cook <keescook@...omium.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
linux-mips@...r.kernel.org
Subject: Re: [PATCH 05/20] signal/mips: Update (_save|_restore)_fp_context
to fail with -EFAULT
On Wed, 20 Oct 2021, Eric W. Biederman wrote:
> When an instruction to save or restore a register from the stack fails
> in _save_fp_context or _restore_fp_context return with -EFAULT. This
> change was made to r2300_fpu.S[1] but it looks like it got lost with
> the introduction of EX2[2]. This is also what the other implementation
> of _save_fp_context and _restore_fp_context in r4k_fpu.S does, and
> what is needed for the callers to be able to handle the error.
Umm, right, good catch, thanks! I think this ought to be backported.
Acked-by: Maciej W. Rozycki <macro@...am.me.uk>
Maciej
Powered by blists - more mailing lists