From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31373] Allow systemtap to work on kernels without strlcpy (removed in the linux-6.8.0-rc3 kernels)
Date: Tue, 13 Feb 2024 14:17:39 +0000 [thread overview]
Message-ID: <bug-31373-6586-sOJwDyfhig@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31373-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31373
--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
Created attachment 15361
--> https://sourceware.org/bugzilla/attachment.cgi?id=15361&action=edit
Proposed define to map the strlcpy to strscpy
The suggestion was the approach that this patch is taking. However, there are
some places in the generated code that make use of the return value to track
the amount of buffer space used by the operation. The proposed patch adjusts
the strscpy return value to make it compatible with the existing uses of the
strlcpy return value.
The macro definition need to be placed where it is only used by the systemtap
generated module. Currently it pulled into code for code for the dyninst
target and causes the dyninst target code to not compile..
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-02-13 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 21:11 [Bug runtime/31373] New: " wcohen at redhat dot com
2024-02-12 22:58 ` [Bug runtime/31373] " fche at redhat dot com
2024-02-13 14:17 ` wcohen at redhat dot com [this message]
2024-02-13 15:31 ` wcohen at redhat dot com
2024-02-14 14:46 ` wcohen at redhat dot com
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=bug-31373-6586-sOJwDyfhig@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).