All of lore.kernel.org
 help / color / mirror / Atom feed
From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Julien Grall" <julien@xen.org>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Bertrand Marquis" <bertrand.marquis@arm.com>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v3 0/3] Add stack protector
Date: Thu, 12 Dec 2024 00:13:33 +0000	[thread overview]
Message-ID: <87pllx3gib.fsf@epam.com> (raw)
In-Reply-To: <f1e86e0e-985a-41ae-a94c-979288275257@suse.com> (Jan Beulich's message of "Wed, 11 Dec 2024 08:46:37 +0100")


Hello Jan,

Jan Beulich <jbeulich@suse.com> writes:

> On 11.12.2024 03:04, Volodymyr Babchuk wrote:
>> Both GCC and Clang support -fstack-protector feature, which add stack
>> canaries to functions where stack corruption is possible. This series
>> makes possible to use this feature in Xen. I tested this on ARM64 and
>> it is working as intended. Tested both with GCC and Clang.
>> 
>> It is hard to enable this feature on x86, as GCC stores stack canary
>> in %fs:40 by default, but Xen can't use %fs for various reasons. It is
>> possibly to change stack canary location new newer GCC versions, but
>> this will change minimal GCC requirement, which is also hard due to
>> various reasons. So, this series focus mostly on ARM and RISCV.
>
> Why exactly would it not be possible to offer the feature when new enough
> gcc is in use?

It is possible to use this feature with a modern enough GCC, yes. Are
you suggesting to make HAS_STACK_PROTECTOR dependent on GCC_VERSION for
x86 platform?

-- 
WBR, Volodymyr

  reply	other threads:[~2024-12-12  0:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  2:04 [PATCH v3 0/3] Add stack protector Volodymyr Babchuk
2024-12-11  2:04 ` [PATCH v3 3/3] xen: arm: enable stack protector feature Volodymyr Babchuk
2024-12-11  2:04 ` [PATCH v3 1/3] common: remove -fno-stack-protector from EMBEDDED_EXTRA_CFLAGS Volodymyr Babchuk
2024-12-11  7:49   ` Jan Beulich
2024-12-12  1:08   ` Andrew Cooper
2024-12-11  2:04 ` [PATCH v3 2/3] xen: common: add ability to enable stack protector Volodymyr Babchuk
2024-12-11  8:16   ` Jan Beulich
2024-12-12  0:47     ` Volodymyr Babchuk
2024-12-12 10:58       ` Jan Beulich
2024-12-12  0:52     ` Andrew Cooper
2024-12-12 10:45       ` Jan Beulich
2025-01-15 12:49   ` Yann Dirson
2024-12-11  7:46 ` [PATCH v3 0/3] Add " Jan Beulich
2024-12-12  0:13   ` Volodymyr Babchuk [this message]
2024-12-12  1:17     ` Andrew Cooper
2024-12-12  1:19       ` Andrew Cooper
2024-12-12 14:30       ` Jan Beulich
2024-12-12 16:52         ` Jan Beulich
2024-12-19  0:20           ` Andrew Cooper
2024-12-19  7:39             ` Jan Beulich
2025-01-14 13:22       ` Jan Beulich
2025-01-14 13:28         ` Andrew Cooper
2025-01-14 13:47           ` Jan Beulich
2025-01-14 14:15             ` Andrew Cooper
2024-12-12 10:30     ` Jan Beulich

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=87pllx3gib.fsf@epam.com \
    --to=volodymyr_babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=bertrand.marquis@arm.com \
    --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.