zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Marcus Müller" <marcus_zsh@hostalia.de>
Cc: Philippe Troin <phil@fifi.org>, zsh-workers@zsh.org
Subject: Re: [Bug] modules zsh/tcp, zsh/zftp unloadable, probably affecting most modern Linuxes
Date: Mon, 5 Jun 2023 13:07:40 -0700	[thread overview]
Message-ID: <CAH+w=7b3L+ZQ5P6xnxsJ-gG_Mx74jpn-UkTZt8P3ZYj1xc1bZg@mail.gmail.com> (raw)
In-Reply-To: <227fe72b-7441-935c-55a7-421945da54b3@hostalia.de>

On Mon, Jun 5, 2023 at 12:35 PM Marcus Müller <marcus_zsh@hostalia.de> wrote:
>
> Ah, so we're exporting and thus overwriting a symbol that overwrites a
> pointer by the name of an existing libc function with a "overrides
> potentially unowned memory" one?

As I understand it that symbol will only be defined by tcp.c if it's
not available from libc or other linked library, so it's not actually
overwriting an identically-named symbol.

Or at least that's the intention, the #ifdef's that are meant to
accomplish it may need refinement for more recent library changes.


  reply	other threads:[~2023-06-05 20:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-04 13:51 Marcus Müller
2023-06-04 20:37 ` Marcus Müller
2023-06-04 21:17   ` Philippe Troin
2023-06-05 19:35     ` Marcus Müller
2023-06-05 20:07       ` Bart Schaefer [this message]
2023-06-06  6:42         ` Jun T
2023-06-06  9:05           ` Peter Stephenson
2023-06-06 14:38             ` Jun. T
2023-06-06 15:01               ` Peter Stephenson
2023-06-06 16:37                 ` Philippe Troin
2023-06-06 17:54                   ` Mikael Magnusson
2023-06-07  2:05                     ` Jun T
2023-06-07  2:35                       ` Jun T
2023-06-07 14:40                         ` Jun. T
2023-06-23 13:41                           ` Jun. T
2023-06-07  9:25         ` Marcus Müller
2023-06-04 22:41   ` Axel Beckert

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='CAH+w=7b3L+ZQ5P6xnxsJ-gG_Mx74jpn-UkTZt8P3ZYj1xc1bZg@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=marcus_zsh@hostalia.de \
    --cc=phil@fifi.org \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).