From: Florian Weimer <fw@deneb.enyo.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 3/5] Linux: Emulate fchmodat with AT_SYMLINK_NOFOLLOW using O_PATH [BZ #14578]
Date: Sun, 09 Feb 2020 10:33:00 -0000 [thread overview]
Message-ID: <87lfpcnj9e.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <47b703f6-fb1d-4cae-b874-6ec8b6d8df4e@cs.ucla.edu> (Paul Eggert's message of "Sun, 9 Feb 2020 02:06:07 -0800")
* Paul Eggert:
> On 2/9/20 12:57 AM, Florian Weimer wrote:
>> What do you think about introducing new symbol versions vs keeping
>> things as they are in the patch today?
>
> I'm not quite following the relationship between the two
> alternatives. Isn't the symbol version independent of whether we
> keep things as they are now, or install the patch that you proposed,
> or install that patch with my further suggestions? That is, I don't
> see why the patch (or patch variant) would require us to change
> symbol versions.
If these functions are now going to be used widely, introducing a new
symbol version at the time of the bug fix ensures that applications do
not accidentally run on glibc versions which lack this change, where
they might fail in obscure ways.
next prev parent reply other threads:[~2020-02-09 10:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 20:03 [PATCH 0/5] Linux: lchmod and AT_SYMLINK_NOFOLLOW support for fchmodat Florian Weimer
2020-01-22 20:03 ` [PATCH 1/5] support: Add the xlstat function Florian Weimer
2020-01-22 20:03 ` [PATCH 3/5] Linux: Emulate fchmodat with AT_SYMLINK_NOFOLLOW using O_PATH [BZ #14578] Florian Weimer
2020-02-09 8:31 ` Paul Eggert
2020-02-09 8:58 ` Florian Weimer
2020-02-09 10:06 ` Paul Eggert
2020-02-09 10:33 ` Florian Weimer [this message]
2020-02-11 15:25 ` Florian Weimer
2020-02-12 1:37 ` Paul Eggert
2020-01-22 20:03 ` [PATCH 2/5] io: Implement lchmod using fchmodat " Florian Weimer
2020-01-22 20:04 ` [PATCH 4/5] io: Add io/tst-lchmod covering lchmod and fchmodat Florian Weimer
2020-02-11 15:27 ` Florian Weimer
2020-02-12 18:52 ` Adhemerval Zanella
2020-02-12 18:55 ` Florian Weimer
2020-02-12 19:41 ` Adhemerval Zanella
2020-02-12 20:01 ` Florian Weimer
2020-02-12 20:28 ` Florian Weimer
2020-01-22 20:27 ` [PATCH 5/5] Linux: Add op/tst-o_path-locks Florian Weimer
2020-07-21 9:46 ` [PATCH 0/5] Linux: lchmod and AT_SYMLINK_NOFOLLOW support for fchmodat Andreas Schwab
2020-07-21 9:54 ` Florian Weimer
2020-08-17 15:46 ` Dmitry V. Levin
2020-08-25 10:21 ` Andreas Schwab
2020-08-25 10:24 ` Florian Weimer
2020-08-25 10:53 ` Andreas Schwab
2020-08-25 11:04 ` Florian Weimer
2020-08-25 11:08 ` Andreas Schwab
2020-08-25 11:09 ` Florian Weimer
2020-08-25 11:15 ` Andreas Schwab
2020-08-25 11:16 ` Florian Weimer
2020-08-25 11:22 ` Andreas Schwab
2020-08-25 11:28 ` Florian Weimer
2020-08-25 12:13 ` Andreas Schwab
2020-08-25 12:16 ` 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=87lfpcnj9e.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=eggert@cs.ucla.edu \
--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).