[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMo8Bf+TZ_ptRjDVuKLZ2M6Bjo83ckuvj=6hCpiZ2ufJrnu80A@mail.gmail.com>
Date: Thu, 9 May 2019 11:55:31 -0700
From: Max Filippov <jcmvbkbc@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>, stable@...r.kernel.org,
Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 4.19 32/66] xtensa: fix initialization of pt_regs::syscall
in start_thread
Hello,
On Thu, May 9, 2019 at 11:48 AM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
>
> [ Upstream commit 2663147dc7465cb29040a05cc4286fdd839978b5 ]
>
> New pt_regs should indicate that there's no syscall, not that there's
> syscall #0. While at it wrap macro body in do/while and parenthesize
> macro arguments.
>
> Signed-off-by: Max Filippov <jcmvbkbc@...il.com>
> Signed-off-by: Sasha Levin <sashal@...nel.org>
> ---
> arch/xtensa/include/asm/processor.h | 21 ++++++++++++---------
> 1 file changed, 12 insertions(+), 9 deletions(-)
This patch should not be taken to any of the stable trees, except maybe
5.0.y, because NO_SYSCALL was introduced to arch/xtensa in 5.0.
This patch doesn't have any cc:stable tags, I'm curious why was it chosen
for stable and what can I do to prevent that in the future?
--
Thanks.
-- Max
Powered by blists - more mailing lists