From: Carlos O'Donell <carlos@redhat.com>
To: "Florian Weimer" <fweimer@redhat.com>,
linux-man@vger.kernel.org, "Ludovic Courtès" <ludo@gnu.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] rtld-audit.7: Clarify la_version handshake
Date: Wed, 23 Sep 2020 21:30:23 -0400 [thread overview]
Message-ID: <e95f918c-2004-fc3d-044a-d66023e57cd7@redhat.com> (raw)
In-Reply-To: <874knosoyq.fsf@oldenburg2.str.redhat.com>
On 9/23/20 7:38 AM, Florian Weimer via Libc-alpha wrote:
> Returning its argument without further checks is almost always
> wrong for la_version.
What you write here is the way I understand the interface to work.
As Andreas noted there is one typo.
I suggest changing the example to match, otherwise people might
keep cribbing that code ;-)
> Signed-off-by: Florian Weimer <fweimer@redhat.com>
>
I agree that la_version should return LAV_CURRENT, that is the
expected way to implement the function, and returning less than
LAV_CURRENT is required to implement older interfaces and be
more compatible with older releases.
As an example I encouraged Ludovic to solve a Guix path problem
with LD_AUDIT and you can see it here:
https://issues.guix.gnu.org/41189
+unsigned int
+la_version (unsigned int v)
+{
+ if (v != LAV_CURRENT)
+ error (1, 0, "cannot handle interface version %u", v);
+
...
+ return v;
+}
While this is OK, in that if it's not an exact match the audit
module errors out, or if it is a match returns v which is
LAV_CURRENT.
It could have been more relaxed:
if (v < LAV_CURRENT)
error (...)
...
return LAV_CURRENT;
Your changes here int he man page would have clarified that to
some extent.
> ---
> man7/rtld-audit.7 | 31 ++++++++++++++++++++++---------
> 1 file changed, 22 insertions(+), 9 deletions(-)
>
> diff --git a/man7/rtld-audit.7 b/man7/rtld-audit.7
> index b1b7dfebc..ca8afa752 100644
> --- a/man7/rtld-audit.7
> +++ b/man7/rtld-audit.7
> @@ -70,17 +70,30 @@ the auditing library.
> When invoking this function, the dynamic linker passes, in
> .IR version ,
> the highest version of the auditing interface that the linker supports.
> -If necessary, the auditing library can check that this version
> -is sufficient for its requirements.
> .PP
> -As its function result,
> -this function should return the version of the auditing interface
> -that this auditing library expects to use (returning
> +A typical implementation of this function simply returns the constant
> +.BR LAV_CURRENT ,
> +which indicates the version of
> +.I <link.h>
> +that was used to build the audit module. If the dynamic linker does
> +not support this version of the audit interface, it will refuse to
> +activate this audit module. If the function returns zero, the dynamic
> +linker also does not activate this audit module.
> +.PP
> +In order to enable backwards compatibility with older dynamic linkers,
> +an audit module can examine the
> +.I version
> +argument and return an earlier version than
> +.BR LAV_CURRENT ,
> +assuming the module can adjust its implement to match the requirements
s/implement/implementation/g (Andreas caught this in his review)
> +of the previous version of the audit interface. The
> +.B la_version
> +function should not return the value of
> .I version
> -is acceptable).
> -If the returned value is 0,
> -or a version that is greater than that supported by the dynamic linker,
> -then the audit library is ignored.
> +without further checks because it could correspond to an interface
> +that does not match the
> +.I <link.h>
> +definitions used to build the audit module.
> .SS la_objsearch()
> \&
> .nf
>
May I additionally suggest something like this to the example?
diff --git a/man7/rtld-audit.7 b/man7/rtld-audit.7
index b1b7dfebc..8a4008b2a 100644
--- a/man7/rtld-audit.7
+++ b/man7/rtld-audit.7
@@ -510,7 +510,11 @@ la_version(unsigned int version)
{
printf("la_version(): %u\en", version);
- return version;
+ if (version > LAV_CURRENT)
+ printf ("la_version(): rtld supports newer interfaces.\n");
+
+ /* Request the version we knew about at compile time. */
+ return LAV_CURRENT;
}
char *
---
Post a v2?
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-09-24 1:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 11:38 Florian Weimer
2020-09-23 11:45 ` Andreas Schwab
2020-09-23 11:47 ` Florian Weimer
2020-09-23 11:52 ` Andreas Schwab
2020-09-23 20:15 ` Ben Coyote Woodard
2020-09-24 1:30 ` Carlos O'Donell [this message]
2020-09-25 8:45 ` Florian Weimer
2020-09-25 8:48 Florian Weimer
2020-09-25 10:47 ` Michael Kerrisk (man-pages)
2020-09-25 16:14 ` Carlos O'Donell
2020-09-25 17:17 ` Michael Kerrisk (man-pages)
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=e95f918c-2004-fc3d-044a-d66023e57cd7@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=ludo@gnu.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).