unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: Zachary Santer <zsanter@gmail.com>
Cc: Carl Edquist <edquist@cs.wisc.edu>, Kaz Kylheku <kaz@kylheku.com>,
	libc-alpha@sourceware.org, coreutils@gnu.org
Subject: Re: Modify buffering of standard streams via environment variables (not LD_PRELOAD)?
Date: Fri, 19 Apr 2024 13:26:05 +0100	[thread overview]
Message-ID: <c8075400-8a3d-b7ca-968c-5eb6207583ca@draigBrady.com> (raw)
In-Reply-To: <CABkLJUKT8ORiV34f76KC2bEymAmDpX+bqMuFbTjk6jpMh43XSQ@mail.gmail.com>

On 19/04/2024 12:36, Zachary Santer wrote:
> On Fri, Apr 19, 2024 at 5:32 AM Pádraig Brady <P@draigbrady.com> wrote:
>>
>> env variables are what I proposed 18 years ago now:
>> https://sourceware.org/bugzilla/show_bug.cgi?id=2457
> 
> And the "resistance to that" from the Red Hat people 24 years ago is
> listed on a website that doesn't exist anymore.
> 
> If I'm to argue with a guy from 18 years ago...
> 
> Ulrich Drepper wrote:
>> Hell, no.  Programs expect a certain buffer mode and perhaps would work
>> unexpectedly if this changes.  By setting a mode to unbuffered, for instance,
>> you can easily DoS a system.  I can think about enough other reasons why this is
>> a terrible idea.  Programs explicitly must request a buffering scheme so that it
>> matches the way the program uses the stream.
> 
> If buffering were set according to the env vars before the program
> configures buffers on its end, if it chooses to, then the env vars
> have no effect. This is how the stdbuf util works, right now. Would
> programs that expect a certain buffer mode not set that mode
> explicitly themselves? Are you allowing untrusted users to set env
> vars for important daemons or something? How is this a valid concern?
> 
> This is specific to the standard streams, 0-2. Buffering of stdout and
> stderr is already configured dynamically by libc. If it's going to a
> terminal, it's line-buffered. If it's not, it's fully buffered.

Playing devil's advocate, I guess programs may be depending
on the automatic buffering modes set.
I guess the thinking is that it was too easy to perturb
the system with env vars, though you can already do that with LD_PRELOAD.

Perhaps at this stage we should consider stdbuf ubiquitous enough to suffice,
noting that it's also supported on FreeBSD.
I'm surprised that the LD_PRELOAD setting is breaking your ada build,
and it would be interesting to determine the reason for that.

cheers,
Pádraig

  reply	other threads:[~2024-04-19 12:26 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABkLJULa8c0zr1BkzWLTpAxHBcpb15Xms0-Q2OOVCHiAHuL0uA@mail.gmail.com>
     [not found] ` <9831afe6-958a-fbd3-9434-05dd0c9b602a@draigBrady.com>
2024-03-10 15:29   ` RFE: enable buffering on null-terminated data Zachary Santer
2024-03-10 20:36     ` Carl Edquist
2024-03-11  3:48       ` Zachary Santer
2024-03-11 11:54         ` Carl Edquist
2024-03-11 15:12           ` Examples of concurrent coproc usage? Zachary Santer
2024-03-14  9:58             ` Carl Edquist
2024-03-17 19:40               ` Zachary Santer
2024-04-01 19:24               ` Chet Ramey
2024-04-01 19:31                 ` Chet Ramey
2024-04-02 16:22                   ` Carl Edquist
2024-04-03 13:54                     ` Chet Ramey
2024-04-03 14:32               ` Chet Ramey
2024-04-03 17:19                 ` Zachary Santer
2024-04-08 15:07                   ` Chet Ramey
2024-04-09  3:44                     ` Zachary Santer
2024-04-13 18:45                       ` Chet Ramey
2024-04-14  2:09                         ` Zachary Santer
2024-04-04 12:52                 ` Carl Edquist
2024-04-04 23:23                   ` Martin D Kealey
2024-04-08 19:50                     ` Chet Ramey
2024-04-09 14:46                       ` Zachary Santer
2024-04-13 18:51                         ` Chet Ramey
2024-04-09 15:58                       ` Carl Edquist
2024-04-13 20:10                         ` Chet Ramey
2024-04-14 18:43                           ` Zachary Santer
2024-04-15 18:55                             ` Chet Ramey
2024-04-15 17:01                           ` Carl Edquist
2024-04-17 14:20                             ` Chet Ramey
2024-04-20 22:04                               ` Carl Edquist
2024-04-22 16:06                                 ` Chet Ramey
2024-04-27 16:56                                   ` Carl Edquist
2024-04-28 17:50                                     ` Chet Ramey
2024-04-08 16:21                   ` Chet Ramey
2024-04-12 16:49                     ` Carl Edquist
2024-04-16 15:48                       ` Chet Ramey
2024-04-20 23:11                         ` Carl Edquist
2024-04-22 16:12                           ` Chet Ramey
2024-04-17 14:37               ` Chet Ramey
2024-04-20 22:04                 ` Carl Edquist
2024-03-12  3:34           ` RFE: enable buffering on null-terminated data Zachary Santer
2024-03-14 14:15             ` Carl Edquist
2024-03-18  0:12               ` Zachary Santer
2024-03-19  5:24                 ` Kaz Kylheku
2024-03-19 12:50                   ` Zachary Santer
2024-03-20  8:55                     ` Carl Edquist
2024-04-19  0:16                       ` Modify buffering of standard streams via environment variables (not LD_PRELOAD)? Zachary Santer
2024-04-19  9:32                         ` Pádraig Brady
2024-04-19 11:36                           ` Zachary Santer
2024-04-19 12:26                             ` Pádraig Brady [this message]
2024-04-19 16:11                               ` Zachary Santer
2024-04-20 16:00                         ` Carl Edquist
2024-04-20 20:00                           ` Zachary Santer
2024-04-20 21:45                             ` Carl Edquist

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c8075400-8a3d-b7ca-968c-5eb6207583ca@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=coreutils@gnu.org \
    --cc=edquist@cs.wisc.edu \
    --cc=kaz@kylheku.com \
    --cc=libc-alpha@sourceware.org \
    --cc=zsanter@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).