All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Julien Grall <julien@xen.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
	"Bertrand Marquis" <bertrand.marquis@arm.com>,
	"Community Manager" <community.manager@xenproject.org>
Subject: Re: [PATCH v4 for-4.20(?) 0/4] Add/enable stack protector
Date: Thu, 13 Feb 2025 15:28:34 +0100	[thread overview]
Message-ID: <fb34061e-a3eb-4ec7-ad96-29f30f982fa5@gmail.com> (raw)
In-Reply-To: <2dbe84e9-485b-47e1-8ceb-94ed9b6b13bc@xen.org>

[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]


On 2/13/25 3:24 PM, Julien Grall wrote:
> Hi,
>
> On 13/02/2025 14:21, Oleksii Kurochko wrote:
>>
>> On 2/13/25 3:07 PM, Andrew Cooper wrote:
>>> On 13/02/2025 1:54 pm, Volodymyr Babchuk wrote:
>>>> Hi Andrew,
>>>>
>>>> Andrew Cooper<andrew.cooper3@citrix.com> writes:
>>>>
>>>>> On 14/01/2025 4:25 am, Volodymyr Babchuk wrote:
>>>>>> Volodymyr Babchuk (4):
>>>>>>    common: remove -fno-stack-protector from EMBEDDED_EXTRA_CFLAGS
>>>>>>    xen: common: add ability to enable stack protector
>>>>>>    xen: arm: enable stack protector feature
>>>>>>    CHANGELOG.md: Mention stack-protector feature
>>>>> Reviewed-by: Andrew Cooper<andrew.cooper3@citrix.com>
>>>>>
>>>>> There's one minor formatting error which can be fixed on commit.
>>>>>
>>>>> ~Andrew
>>>> Thanks for the review. I noticed that this series is not committed. Is
>>>> there anything else required from my side?
>>>>
>>> You need an ARM Ack on patch 3.  [EDIT], no you don't, my R-by is good
>>> enough.
>
> I beg to differ. For low level code, you really ought to have Arm 
> folks to confirm this is correct. In fact, I don't think patch #3 it 
> is. So ...
>
>>>
>>> And at this point at rc4, you'll need to persuade Oleksii to take it 
>>> for
>>> 4.20.
>>>
>>> Personally I think it's low risk and worthwhile to take for 4.20, 
>>> and it
>>> was technically completed in time - it just fell between the cracks.
>>
>> I think the same it's low risk patch series, so we can take it for 4.20:
>>   Release-Acked-by: Oleksii Kurochko<olekskii.kurochko@gmail.com>
>
> ... I should not go to 4.20 as-is.
>
> And before someone ask why it wasn't answered early. I can't comment 
> for the other Arm maintainers, but I have been away for the past two 
> months. So still catching up on my emails.

Agree, I wrote that in follow-up reply to my initial reply.

So if the proper Ack will be received I still think we can consider to have it in 4.20.

~ Oleksii

>

[-- Attachment #2: Type: text/html, Size: 3894 bytes --]

  reply	other threads:[~2025-02-13 14:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14  4:25 [PATCH v4 0/4] Add/enable stack protector Volodymyr Babchuk
2025-01-14  4:25 ` [PATCH v4 3/4] xen: arm: enable stack protector feature Volodymyr Babchuk
2025-02-13 14:20   ` Julien Grall
2025-02-13 14:35     ` Julien Grall
2025-01-14  4:25 ` [PATCH v4 2/4] xen: common: add ability to enable stack protector Volodymyr Babchuk
2025-01-14  9:31   ` Andrew Cooper
2025-01-14  4:25 ` [PATCH v4 4/4] CHANGELOG.md: Mention stack-protector feature Volodymyr Babchuk
2025-02-13 14:18   ` Oleksii Kurochko
2025-01-14  4:25 ` [PATCH v4 1/4] common: remove -fno-stack-protector from EMBEDDED_EXTRA_CFLAGS Volodymyr Babchuk
2025-01-14  9:32 ` [PATCH v4 0/4] Add/enable stack protector Andrew Cooper
2025-02-13 13:54   ` Volodymyr Babchuk
2025-02-13 14:07     ` [PATCH v4 for-4.20(?) " Andrew Cooper
2025-02-13 14:21       ` Oleksii Kurochko
2025-02-13 14:24         ` Julien Grall
2025-02-13 14:28           ` Oleksii Kurochko [this message]
2025-02-13 14:26         ` Oleksii Kurochko
2025-02-13 14:30           ` Jan Beulich
2025-02-13 15:09             ` Andrew Cooper
2025-02-13 14:31           ` Andrew Cooper

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=fb34061e-a3eb-4ec7-ad96-29f30f982fa5@gmail.com \
    --to=oleksii.kurochko@gmail.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=bertrand.marquis@arm.com \
    --cc=community.manager@xenproject.org \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=sstabellini@kernel.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.