public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Should legacy fstat (via __fxstat) and fstat@GLIBC_2.33 call the same syscall?
Date: Fri, 15 Jan 2021 11:29:41 +0100	[thread overview]
Message-ID: <87im7ylch6.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <b51763f7-3372-1f7b-a54f-9031a6625cfb@linaro.org> (Adhemerval Zanella's message of "Thu, 14 Jan 2021 14:46:07 -0300")

* Adhemerval Zanella:

> I think it should be feasible, I haven't done it because I would like
> to touch the compatibility as little as possible to avoid further
> breakage.

Yes, the current model preserves behavior of applications until they are
relinked.  I'm not quite decided yet whether this is a good thing or
not.  In the past, we have done this for behavior changes.  But this
isn't really changing behavior, and the change in syscall profile due to
relinking is quite confusing, too, especially when it comes to browser
sandboxes.

So maybe we should leave this in place for 2.33 and see if we can clean
this up in a future release.

Thanks,
Florian
-- 
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill


      reply	other threads:[~2021-01-15 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 12:00 Florian Weimer
2021-01-14 12:29 ` Adhemerval Zanella
2021-01-14 14:38   ` Florian Weimer
2021-01-14 16:36     ` Adhemerval Zanella
2021-01-14 16:45       ` Florian Weimer
2021-01-14 16:53         ` Adhemerval Zanella
2021-01-14 17:18           ` Florian Weimer
2021-01-14 17:46             ` Adhemerval Zanella
2021-01-15 10:29               ` Florian Weimer [this message]

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=87im7ylch6.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@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).