From: Kees Cook <kees@kernel.org>
To: Andrew Pinski <andrew.pinski@oss.qualcomm.com>
Cc: Indu Bhagat <indu.bhagat@oracle.com>,
Claudiu Zissulescu <claudiu.zissulescu-ianculescu@oracle.com>,
Qing Zhao <qing.zhao@oracle.com>,
gcc-patches@gcc.gnu.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v4] Fix sanitizer attribute infrastructure to use standard TREE_LIST format [PR113264]
Date: Fri, 6 Feb 2026 10:16:34 -0800 [thread overview]
Message-ID: <202602061016.DD543146B8@keescook> (raw)
In-Reply-To: <CALvbMcAMWW1ewkszu9nYEaY0iA=CsUh+JFm1pzpnkXvzp9dP5Q@mail.gmail.com>
On Fri, Feb 06, 2026 at 12:05:04AM -0800, Andrew Pinski wrote:
> On Thu, Sep 4, 2025 at 10:43 AM Kees Cook <kees@kernel.org> wrote:
> >
> > The __attribute__((__copy__)) functionality was crashing when copying
> > sanitizer-related attributes because these attributes violated the standard
> > GCC attribute infrastructure by storing INTEGER_CST values directly instead
> > of wrapping them in TREE_LIST like all other attributes.
>
> I am going to review this over the weekend. I see it was not reviewed yet.
Thanks! I'd love to get this landed (I don't have commit access).
--
Kees Cook
next prev parent reply other threads:[~2026-02-06 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 17:43 [PATCH v4] Fix sanitizer attribute infrastructure to use standard TREE_LIST format [PR113264] Kees Cook
2026-02-06 8:05 ` Andrew Pinski
2026-02-06 18:16 ` Kees Cook [this message]
2026-02-09 8:28 ` Andrew Pinski
2026-02-09 11:47 ` 答复: " hanwei (K)
2026-02-10 2:34 ` Andrew Pinski
-- strict thread matches above, loose matches on Subject: below --
2026-02-25 6:27 hanwei (K)
[not found] <cb90ec7f5d724213b164e9f849675907@h-partners.com>
2026-03-07 19:38 ` Andrew Pinski
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=202602061016.DD543146B8@keescook \
--to=kees@kernel.org \
--cc=andrew.pinski@oss.qualcomm.com \
--cc=claudiu.zissulescu-ianculescu@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=indu.bhagat@oracle.com \
--cc=linux-hardening@vger.kernel.org \
--cc=qing.zhao@oracle.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