linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Anders Roxell <anders.roxell@linaro.org>, mpe@ellerman.id.au
Cc: stable@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/3] powerpc: lib: sstep: fix 'sthcx' instruction
Date: Thu, 24 Feb 2022 12:40:57 +1000	[thread overview]
Message-ID: <1645670438.z6ynuisobl.astroid@bobo.none> (raw)
In-Reply-To: <20220223135820.2252470-1-anders.roxell@linaro.org>

Excerpts from Anders Roxell's message of February 23, 2022 11:58 pm:
> Looks like there been a copy paste mistake when added the instruction
> 'stbcx' twice and one was probably meant to be 'sthcx'.
> Changing to 'sthcx' from 'stbcx'.
> 
> Cc: <stable@vger.kernel.org> # v4.13+
> Fixes: 350779a29f11 ("powerpc: Handle most loads and stores in instruction emulation code")
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>

Good catch.

Reviewed-by: Nicholas Piggin <npiggin@gmail.com>

> ---
>  arch/powerpc/lib/sstep.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/powerpc/lib/sstep.c b/arch/powerpc/lib/sstep.c
> index bd3734d5be89..d2d29243fa6d 100644
> --- a/arch/powerpc/lib/sstep.c
> +++ b/arch/powerpc/lib/sstep.c
> @@ -3389,7 +3389,7 @@ int emulate_loadstore(struct pt_regs *regs, struct instruction_op *op)
>  			__put_user_asmx(op->val, ea, err, "stbcx.", cr);
>  			break;
>  		case 2:
> -			__put_user_asmx(op->val, ea, err, "stbcx.", cr);
> +			__put_user_asmx(op->val, ea, err, "sthcx.", cr);
>  			break;
>  #endif
>  		case 4:
> -- 
> 2.34.1
> 
> 

      parent reply	other threads:[~2022-02-24  8:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 13:58 [PATCH 1/3] powerpc: lib: sstep: fix 'sthcx' instruction Anders Roxell
2022-02-23 13:58 ` [PATCH 2/3] powerpc: fix build errors Anders Roxell
2022-02-23 15:21   ` Segher Boessenkool
2022-02-24  2:54   ` Nicholas Piggin
2022-02-24  5:05     ` Nicholas Piggin
2022-02-24  8:55       ` Arnd Bergmann
2022-02-24 10:11         ` Nicholas Piggin
2022-02-24 10:20           ` Arnd Bergmann
2022-02-24 11:13             ` Nicholas Piggin
2022-02-24 17:29               ` Segher Boessenkool
2022-02-25  0:23                 ` Nicholas Piggin
2022-02-25 22:28                   ` Segher Boessenkool
2022-02-26  0:07                     ` Nicholas Piggin
2022-02-24 17:12       ` Segher Boessenkool
2022-02-25  0:32         ` Nicholas Piggin
2022-02-25  8:33           ` Arnd Bergmann
2022-02-25 10:51             ` Nicholas Piggin
2022-02-25 22:33           ` Segher Boessenkool
2022-02-24 12:39   ` Michael Ellerman
2022-02-24 16:12     ` Anders Roxell
2022-02-24 17:37     ` Segher Boessenkool
2022-02-23 13:58 ` [PATCH 3/3] powerpc: lib: sstep: " Anders Roxell
2022-02-23 15:27   ` Segher Boessenkool
2022-02-24  2:40 ` Nicholas Piggin [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=1645670438.z6ynuisobl.astroid@bobo.none \
    --to=npiggin@gmail.com \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).