From: Jan Beulich <jbeulich@suse.com>
To: Frediano Ziglio <frediano.ziglio@cloud.com>
Cc: "Daniel P. Smith" <dpsmith@apertussolutions.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v6] Avoid crash calling PrintErrMesg from efi_multiboot2
Date: Mon, 17 Feb 2025 17:31:00 +0100 [thread overview]
Message-ID: <77eb149c-bb1e-4f77-85ba-c44b173a5c1e@suse.com> (raw)
In-Reply-To: <20250217162659.151232-1-frediano.ziglio@cloud.com>
On 17.02.2025 17:26, Frediano Ziglio wrote:
> --- a/xen/common/efi/efi-common.mk
> +++ b/xen/common/efi/efi-common.mk
> @@ -2,6 +2,7 @@ EFIOBJ-y := boot.init.o pe.init.o ebmalloc.o runtime.o
> EFIOBJ-$(CONFIG_COMPAT) += compat.o
>
> CFLAGS-y += -fshort-wchar
> +CFLAGS-y += -fno-jump-tables
> CFLAGS-y += -iquote $(srctree)/common/efi
> CFLAGS-y += -iquote $(srcdir)
Do source files other than boot.c really need this? Do any other files outside
of efi/ maybe also need this (iirc this point was made along with the v5 comment
you got)?
Jan
next prev parent reply other threads:[~2025-02-17 16:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 16:26 [PATCH v6] Avoid crash calling PrintErrMesg from efi_multiboot2 Frediano Ziglio
2025-02-17 16:31 ` Jan Beulich [this message]
2025-02-17 16:41 ` Andrew Cooper
2025-02-17 16:52 ` Frediano Ziglio
2025-02-17 16:56 ` Jan Beulich
2025-02-18 12:05 ` Frediano Ziglio
2025-02-18 12:10 ` Andrew Cooper
2025-02-19 16:34 ` Frediano Ziglio
2025-02-20 7:32 ` Jan Beulich
2025-02-20 9:23 ` Frediano Ziglio
2025-02-21 20:20 ` Marek Marczykowski-Górecki
2025-02-24 12:57 ` Frediano Ziglio
2025-02-24 13:16 ` Marek Marczykowski-Górecki
2025-02-24 14:31 ` Frediano Ziglio
2025-02-26 18:54 ` Marek Marczykowski-Górecki
2025-02-27 7:54 ` Jan Beulich
2025-03-06 14:26 ` Jan Beulich
2025-03-06 15:02 ` Frediano Ziglio
2025-03-20 14:33 ` Frediano Ziglio
2025-03-20 15:15 ` Jan Beulich
2025-03-20 20:10 ` Frediano Ziglio
2025-03-21 6:47 ` 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=77eb149c-bb1e-4f77-85ba-c44b173a5c1e@suse.com \
--to=jbeulich@suse.com \
--cc=dpsmith@apertussolutions.com \
--cc=frediano.ziglio@cloud.com \
--cc=marmarek@invisiblethingslab.com \
--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.