From: Chen Zhongjin <chenzhongjin@huawei.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<catalin.marinas@arm.com>, <will@kernel.org>,
<broonie@kernel.org>, <maz@kernel.org>, <mark.rutland@arm.com>,
<anshuman.khandual@arm.com>
Subject: Re: [PATCH -next 1/3] arm64: efi-header: Mark efi header as data
Date: Thu, 22 Sep 2022 22:25:31 +0800 [thread overview]
Message-ID: <71274d7a-8a79-3954-d462-5cc8b5a5e874@huawei.com> (raw)
In-Reply-To: <CAMj1kXGSjGr_yBC_9DiFu4k3JpDRPB+BPuKdNu2XeSWT2BSZvQ@mail.gmail.com>
Hi,
On 2022/9/22 21:13, Ard Biesheuvel wrote:
> On Thu, 22 Sept 2022 at 15:08, Chen Zhongjin <chenzhongjin@huawei.com> wrote:
>> This file only contains a set of constants forming the efi header.
>>
>> Make the constants part of data symbols by wrapping them with
>> SYM_DATA.
>>
>> Signed-off-by: Julien Thierry <jthierry@redhat.com>
>> Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com>
>> Reviewed-by: Mark Brown <broonie@kernel.org>
> Why is this necessary? These are not emitted into a .text section, and
> are not even covered by the kernel's mapping of memory. So the .L
> prefixed labels are deliberate: it prevents the symbols from polluting
> the symbol namespace with symbols pointing nowhere.
>
This is basically because when I'm developing objtool and these
constants will disrupts
the instruction decoding so I just mark them as x86 did.
I tried to sent this patch set is because now the objtool patch set is
growing huge so I
want to split some independent part. But now I found you are right that
this are
meaningless. They are not even inside vmlinux. I'll discard them.
Sorry for bothering and thanks for your advise and patient!
Best,
Chen
>> ---
>> arch/arm64/kernel/efi-header.S | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/arm64/kernel/efi-header.S b/arch/arm64/kernel/efi-header.S
>> index 28d8a5dca5f1..3eacd27ab761 100644
>> --- a/arch/arm64/kernel/efi-header.S
>> +++ b/arch/arm64/kernel/efi-header.S
>> @@ -28,6 +28,7 @@
>> .macro __EFI_PE_HEADER
>> #ifdef CONFIG_EFI
>> .set .Lpe_header_offset, . - .L_head
>> +SYM_DATA_START_LOCAL(arm64_efi_header)
>> .long PE_MAGIC
>> .short IMAGE_FILE_MACHINE_ARM64 // Machine
>> .short .Lsection_count // NumberOfSections
>> @@ -160,6 +161,7 @@
>>
>> .balign SEGMENT_ALIGN
>> .Lefi_header_end:
>> +SYM_DATA_END_LABEL(arm64_efi_header, SYM_L_LOCAL, efi_header_end)
>> #else
>> .set .Lpe_header_offset, 0x0
>> #endif
>> --
>> 2.17.1
>>
next prev parent reply other threads:[~2022-09-22 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 13:04 [PATCH -next 0/3] arm64: Mark constants in .S files " Chen Zhongjin
2022-09-22 13:04 ` [PATCH -next 1/3] arm64: efi-header: Mark efi header " Chen Zhongjin
2022-09-22 13:13 ` Ard Biesheuvel
2022-09-22 14:25 ` Chen Zhongjin [this message]
2022-09-22 13:04 ` [PATCH -next 2/3] arm64: head: Mark constants " Chen Zhongjin
2022-09-22 13:17 ` Ard Biesheuvel
2022-09-22 13:04 ` [PATCH -next 3/3] arm64: crypto: Mark constant " Chen Zhongjin
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=71274d7a-8a79-3954-d462-5cc8b5a5e874@huawei.com \
--to=chenzhongjin@huawei.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®