All of lore.kernel.org
 help / color / mirror / Atom feed
From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH v2 2/4] xen: common: add ability to enable stack protector
Date: Thu, 5 Dec 2024 03:34:54 +0000	[thread overview]
Message-ID: <87o71q4xb7.fsf@epam.com> (raw)
In-Reply-To: <4f2f949b-a53e-4a79-8084-d374cabc109e@citrix.com> (Andrew Cooper's message of "Tue, 3 Dec 2024 20:33:07 +0000")


Hi Andrew,

I addressed almost all your comments, but didn't get this one:

Andrew Cooper <andrew.cooper3@citrix.com> writes:

> On 30/11/2024 1:10 am, Volodymyr Babchuk wrote:

[...]


>> diff --git a/xen/common/stack-protector.c b/xen/common/stack-protector.c
>> new file mode 100644
>> index 0000000000..b258590d3a
>> --- /dev/null
>> +++ b/xen/common/stack-protector.c
>> @@ -0,0 +1,10 @@
>> +// SPDX-License-Identifier: GPL-2.0-only
>> +#include <xen/lib.h>
>> +#include <xen/random.h>
>> +
>> +unsigned long __ro_after_init __stack_chk_guard;
>> +
>> +void __stack_chk_fail(void)
>
> asmlinkage.  This MISRA check is now blocking in Eclair.

I can see what we might want to mark it as "noreturn", but I don't
understand why you want to use asmlinkage. It is not called from
assembly.


-- 
WBR, Volodymyr

  reply	other threads:[~2024-12-05  3:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-30  1:10 [PATCH v2 0/4] Add stack protector Volodymyr Babchuk
2024-11-30  1:10 ` [PATCH v2 2/4] xen: common: add ability to enable " Volodymyr Babchuk
2024-12-02  8:29   ` Jan Beulich
2024-12-03 20:33   ` Andrew Cooper
2024-12-05  3:34     ` Volodymyr Babchuk [this message]
2024-12-05 12:52       ` Andrew Cooper
2024-11-30  1:10 ` [PATCH v2 1/4] common: remove -fno-stack-protector from EMBEDDED_EXTRA_CFLAGS Volodymyr Babchuk
2024-12-02  8:06   ` Jan Beulich
2024-12-02 10:32     ` Andrew Cooper
2024-12-02 11:31     ` Jan Beulich
2024-11-30  1:10 ` [PATCH v2 3/4] xen: arm: enable stack protector feature Volodymyr Babchuk
2024-11-30 17:06   ` Julien Grall
2024-12-03 22:00   ` Andrew Cooper
2024-12-03 23:16     ` Julien Grall
2024-12-05 19:23       ` Andrew Cooper
2024-12-06  4:46         ` Volodymyr Babchuk
2024-12-09  9:36           ` Jan Beulich
2024-12-09 12:45             ` Volodymyr Babchuk
2024-11-30  1:10 ` [PATCH v2 4/4] xen: riscv: " Volodymyr Babchuk
2024-12-02  8:12   ` Jan Beulich
2024-12-02  8:54     ` oleksii.kurochko
2024-12-02  9:56     ` oleksii.kurochko
2024-12-03 19:30       ` Volodymyr Babchuk

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=87o71q4xb7.fsf@epam.com \
    --to=volodymyr_babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.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.