From: Keerthana Kalyanasundaram <keerthanak@vmware.com>
To: "keescook@chromium.org" <keescook@chromium.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Alexey Makhalov <amakhalov@vmware.com>,
Ajay Kaher <akaher@vmware.com>,
Vasavi Sirnapalli <vsirnapalli@vmware.com>
Subject: PROBLEM: Using Randomize structure layout GCC plugin doesn't generate proper debuginfo
Date: Thu, 25 May 2023 10:21:15 +0000 [thread overview]
Message-ID: <DF6066B2-35AE-40BE-A217-D3C48DBF6751@vmware.com> (raw)
Hello,
I’m reporting this bug in randomize strcture layout plugin in GCC plugins code of linux kernel tree.
When I compile the kernel with randomize structure layout GCC plugin, the resulting debuginfo does not have the randomised structures.
To reproduce this, I have a C sample program and a script to compile the program with and without randomize_layout_plugin
from linux kernel, the resulted debuginfo in both cases are same. Though the plugin shuffles the structure members, the resulting debuginfo
has unshuffled structure.
I have found an old bug in GCC reporting the same https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84052 This bug has been closed as invalid though there was a conversation between PaX maintainers and GCC devs.
I assume this issue has been there since the randomize_layout_plugin has been added in kernel. Please correct me if I’m wrong.
Please let me know, if you need more information. I hope you are able to fix this issue.
Thanks
Keerthana
next reply other threads:[~2023-05-25 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 10:21 Keerthana Kalyanasundaram [this message]
2023-05-25 10:32 ` Keerthana Kalyanasundaram
2023-05-25 15:14 ` Kees Cook
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=DF6066B2-35AE-40BE-A217-D3C48DBF6751@vmware.com \
--to=keerthanak@vmware.com \
--cc=akaher@vmware.com \
--cc=amakhalov@vmware.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vsirnapalli@vmware.com \
/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®