From: Sam James <sam@gentoo.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: Siddhesh Poyarekar <siddhesh@sourceware.org>,
libc-alpha@sourceware.org, fweimer@redhat.com
Subject: Re: [PATCH] Add _FORTIFY_SOURCE implementation documentation [BZ #28998]
Date: Thu, 22 Dec 2022 13:08:01 +0000 [thread overview]
Message-ID: <6E441F3E-97B4-4A4E-B876-618D12EEDCF4@gentoo.org> (raw)
In-Reply-To: <a86c528f-4b1b-daa1-661a-29096432201a@gotplt.org>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
> On 22 Dec 2022, at 12:56, Siddhesh Poyarekar <siddhesh@gotplt.org> wrote:
>
> Ping! Any further comments other than the redundant 'See' Andreas noted?
>
It looks good & thanks for doing it.
I wonder if it's worth noting (maybe it's obvious) that tools which
make use of LD_PRELOAD may need to provide their own wrappers.
(umockdev being an example I'm thinking of here.)
> Thanks,
> Sid
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next prev parent reply other threads:[~2022-12-22 13:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 16:25 Siddhesh Poyarekar
2022-12-15 16:35 ` Andreas Schwab
2022-12-15 16:37 ` Siddhesh Poyarekar
2022-12-22 12:56 ` Siddhesh Poyarekar
2022-12-22 13:08 ` Sam James [this message]
2023-01-03 14:43 ` Siddhesh Poyarekar
2023-01-04 23:49 ` Jeff Law
2022-12-22 13:35 ` Florian Weimer
2022-12-22 14:19 ` Siddhesh Poyarekar
2022-12-22 14:22 ` Siddhesh Poyarekar
2022-12-22 15:32 ` [PATCH v2] " Siddhesh Poyarekar
2022-12-22 16:04 ` [PATCH v3] " Siddhesh Poyarekar
2023-01-03 14:29 ` [ping][PATCH " Siddhesh Poyarekar
2023-01-05 21:04 ` [PATCH " Yann Droneaud
2023-01-06 12:27 ` Siddhesh Poyarekar
2023-01-09 15:32 ` Florian Weimer
2023-01-10 13:03 ` Siddhesh Poyarekar
2023-01-11 6:45 ` Sam James
2023-01-10 13:40 ` [PATCH v4] " Siddhesh Poyarekar
2023-01-10 15:00 ` Florian Weimer
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=6E441F3E-97B4-4A4E-B876-618D12EEDCF4@gentoo.org \
--to=sam@gentoo.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.org \
--cc=siddhesh@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).