All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Community Manager <community.manager@xenproject.org>
Subject: Re: [PATCH v6 4/4] CHANGELOG.md: Mention stack-protector feature
Date: Tue, 11 Mar 2025 17:11:47 +0100	[thread overview]
Message-ID: <0ceda9aa-4e11-4a02-8f60-ea9d1247acf1@gmail.com> (raw)
In-Reply-To: <20250217024848.3059635-5-volodymyr_babchuk@epam.com>


On 2/17/25 3:49 AM, Volodymyr Babchuk wrote:
> Stack protector is meant to be enabled on all architectures, but
> currently it is tested (and enabled) only on ARM, so mention it in ARM
> section.
>
> Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>
>
> ---
>
> TODO: If this patch will not make into 4.20 - rework it by mentioning
> a correct version.
>
> Changes in v6:
>
>   - Dropped Andrew's R-b tag because there is little chance that this
>   series will be included in 4.20, so this patch should be reworked for
>   4.21
> ---
>   CHANGELOG.md | 1 +

Acked-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>

~ Oleksii

>   1 file changed, 1 insertion(+)
>
> diff --git a/CHANGELOG.md b/CHANGELOG.md
> index 1de1d1eca1..4cac4079f0 100644
> --- a/CHANGELOG.md
> +++ b/CHANGELOG.md
> @@ -23,6 +23,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>      - Basic handling for SCMI requests over SMC using Shared Memory, by allowing
>        forwarding the calls to EL3 FW if coming from hwdom.
>      - Support for LLC (Last Level Cache) coloring.
> +   - Ability to enable stack protector
>    - On x86:
>      - xl suspend/resume subcommands.
>      - `wallclock` command line option to select time source.


      reply	other threads:[~2025-03-11 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17  2:49 [PATCH v6 0/4] Add/enable stack protector Volodymyr Babchuk
2025-02-17  2:49 ` [PATCH v6 1/4] common: remove -fno-stack-protector from EMBEDDED_EXTRA_CFLAGS Volodymyr Babchuk
2025-03-04 12:57   ` Andrew Cooper
2025-02-17  2:49 ` [PATCH v6 2/4] xen: common: add ability to enable stack protector Volodymyr Babchuk
2025-02-17  9:58   ` Jan Beulich
2025-02-17  2:49 ` [PATCH v6 3/4] xen: arm: enable stack protector feature Volodymyr Babchuk
2025-02-17  2:49 ` [PATCH v6 4/4] CHANGELOG.md: Mention stack-protector feature Volodymyr Babchuk
2025-03-11 16:11   ` Oleksii Kurochko [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=0ceda9aa-4e11-4a02-8f60-ea9d1247acf1@gmail.com \
    --to=oleksii.kurochko@gmail.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=community.manager@xenproject.org \
    --cc=xen-devel@lists.xenproject.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 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.