public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: mojha@codeaurora.org
To: devel@edk2.groups.io, discuss@edk2.groups.io
Subject: [edk2-devel] : Query regarding IsTextShdr inside Basetools
Date: Tue, 10 Nov 2020 18:37:14 +0530	[thread overview]
Message-ID: <dad12425-acbb-802e-3d76-2468fca67415@codeaurora.org> (raw)

Hi All,

I have a doubt about the check we have put inside IsTextShdr() .

STATIC
BOOLEAN
IsTextShdr (
   Elf_Shdr *Shdr
   )
{
   return (BOOLEAN) ((Shdr->sh_flags & (SHF_WRITE | SHF_ALLOC)) == 
SHF_ALLOC);
}


We are observing one issue where while generate EFI using GenFW in EDK2 
because test/data section offset is different than calculated 
mCoffSectionsOffset when scanning sections.
I run GenFW with a failure dll in my local after adding some logs into 
GenFW. and found that “mCoffSectionsOffset” for data section seems not 
to have expected value due to
“.note.gnu.property” size. Because compiled dll has “.note.gnu.property” 
section with alloc flag and GenFW thinks that it’s a text section if 
alloc flag is set.
So its size is added to the mCoffSectionsOffset.

Could you please give us an advice whether we can fix IsTextShdr() 
function like below ?


--- a/BaseTools/Source/C/GenFw/Elf64Convert.c
+++ b/BaseTools/Source/C/GenFw/Elf64Convert.c
@@ -229,7 +229,7 @@ IsTextShdr (
    Elf_Shdr *Shdr
    )
{
-  return (BOOLEAN) ((Shdr->sh_flags & (SHF_WRITE | SHF_ALLOC)) == 
SHF_ALLOC);
+  return (BOOLEAN) ((Shdr->sh_flags & (SHF_EXECINSTR | SHF_WRITE | 
SHF_ALLOC)) == (SHF_ALLOC | SHF_EXECINSTR));^


Thanks,
Mukesh

             reply	other threads:[~2020-11-10 13:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 13:07 mojha [this message]
2020-11-11 22:40 ` [edk2-devel] : Query regarding IsTextShdr inside Basetools Laszlo Ersek
2020-11-11 22:41   ` Laszlo Ersek
2020-11-12  8:23     ` Ard Biesheuvel
     [not found] <164632B1BC861BDB.31324@groups.io>
2020-11-11  7:07 ` Mukesh Ojha

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-list 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=dad12425-acbb-802e-3d76-2468fca67415@codeaurora.org \
    --to=devel@edk2.groups.io \
    /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