From: Florian Weimer <fweimer@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 3/4] sunrpc: Test case for clnt_create "unix" buffer overflow (bug 22542)
Date: Mon, 17 Jan 2022 10:32:12 +0100 [thread overview]
Message-ID: <87fspmoggz.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <d1a0bcfc-efa1-93b2-4c01-aae85a67dba6@gotplt.org> (Siddhesh Poyarekar's message of "Mon, 17 Jan 2022 15:00:43 +0530")
* Siddhesh Poyarekar:
> On 17/01/2022 14:45, Florian Weimer wrote:
>> It has in linkobj/libc.so:
>> $ eu-readelf --symbols=.dynsym linkobj/libc.so | grep clnt_create
>> 3126: 000387a0 465 FUNC GLOBAL DEFAULT 14 clnt_create@@GLIBC_2.0
>
> That's weird, shouldn't it be non-default given that it is deprecated?
> Why is it needed for internal linking? For tests?
Yes. linkobj/libc.so and libc.so are different. It's a compatibility
symbol in libc.so.
Thanks,
Florian
next prev parent reply other threads:[~2022-01-17 9:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 8:23 [PATCH v2 0/4] CVE-2022-23218, CVE-2022-23219: sunrpc buffer overflows Florian Weimer
2022-01-14 8:23 ` [PATCH 1/4] socket: Add the __sockaddr_un_set function Florian Weimer
2022-01-17 3:28 ` Siddhesh Poyarekar
2022-01-14 8:24 ` [PATCH v2 2/4] CVE-2022-23219: Buffer overflow in sunrpc clnt_create for "unix" (bug 22542) Florian Weimer
2022-01-17 3:29 ` Siddhesh Poyarekar
2022-01-14 8:24 ` [PATCH 3/4] sunrpc: Test case for clnt_create "unix" buffer overflow " Florian Weimer
2022-01-17 3:31 ` Siddhesh Poyarekar
2022-01-17 3:35 ` Siddhesh Poyarekar
2022-01-17 9:15 ` Florian Weimer
2022-01-17 9:30 ` Siddhesh Poyarekar
2022-01-17 9:32 ` Florian Weimer [this message]
2022-01-17 9:42 ` Siddhesh Poyarekar
2022-01-14 8:24 ` [PATCH v2 4/4] CVE-2022-23218: Buffer overflow in sunrpc svcunix_create (bug 28768) Florian Weimer
2022-01-17 9:43 ` Siddhesh Poyarekar
-- strict thread matches above, loose matches on Subject: below --
2022-01-12 17:00 [PATCH 0/4] Fix two sunrpc buffer overflows Florian Weimer
2022-01-12 17:01 ` [PATCH 3/4] sunrpc: Test case for clnt_create "unix" buffer overflow (bug 22542) 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=87fspmoggz.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).