From: Greg KH <gregkh@linuxfoundation.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: catalin.marinas@arm.com, will.deacon@arm.com,
mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4.19] arm64: fix a concurrency issue in emulation_proc_handler()
Date: Tue, 31 Oct 2023 12:18:17 +0100 [thread overview]
Message-ID: <2023103103-revision-gigantic-cc05@gregkh> (raw)
In-Reply-To: <20231030063709.2443546-1-ruanjinjie@huawei.com>
On Mon, Oct 30, 2023 at 06:37:09AM +0000, Jinjie Ruan wrote:
> In linux-6.1, the related code is refactored in commit 124c49b1b5d9
> ("arm64: armv8_deprecated: rework deprected instruction handling") and this
> issue was incidentally fixed. I have adapted the patch set to linux stable
> 5.10. However, 4.19 and 5.10 are too different and the patch set is
> hard to adapt to 4.19.
This is also needed for 5.4.y, right? Now queued up for both.
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: catalin.marinas@arm.com, will.deacon@arm.com,
mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4.19] arm64: fix a concurrency issue in emulation_proc_handler()
Date: Tue, 31 Oct 2023 12:18:17 +0100 [thread overview]
Message-ID: <2023103103-revision-gigantic-cc05@gregkh> (raw)
In-Reply-To: <20231030063709.2443546-1-ruanjinjie@huawei.com>
On Mon, Oct 30, 2023 at 06:37:09AM +0000, Jinjie Ruan wrote:
> In linux-6.1, the related code is refactored in commit 124c49b1b5d9
> ("arm64: armv8_deprecated: rework deprected instruction handling") and this
> issue was incidentally fixed. I have adapted the patch set to linux stable
> 5.10. However, 4.19 and 5.10 are too different and the patch set is
> hard to adapt to 4.19.
This is also needed for 5.4.y, right? Now queued up for both.
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-31 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 6:37 [PATCH v4.19] arm64: fix a concurrency issue in emulation_proc_handler() Jinjie Ruan
2023-10-30 6:37 ` Jinjie Ruan
2023-10-31 11:18 ` Greg KH [this message]
2023-10-31 11:18 ` Greg KH
2023-10-31 11:52 ` Jinjie Ruan
2023-10-31 11:52 ` Jinjie Ruan
2023-10-31 11:18 ` Patch "arm64: fix a concurrency issue in emulation_proc_handler()" has been added to the 4.19-stable tree gregkh
2023-10-31 11:18 ` Patch "arm64: fix a concurrency issue in emulation_proc_handler()" has been added to the 5.4-stable tree gregkh
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=2023103103-revision-gigantic-cc05@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ruanjinjie@huawei.com \
--cc=will.deacon@arm.com \
/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 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.