public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31699] UBSAN errors for systemtap map functions with Fedora Rawhide and Fedora 39 6.8.8 kernels
Date: Mon, 06 May 2024 14:11:45 +0000	[thread overview]
Message-ID: <bug-31699-6586-UZ4qeB9NYo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31699-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31699

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|systemtap at sourceware dot org    |wcohen at redhat dot com
             Status|NEW                         |ASSIGNED

--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
Created attachment 15495
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15495&action=edit
Another UBSAN fix in runtime/linux/addr-map.c

Reviewed the systemtap runtime found another struct that UBSAN checks might
flag in runtime/linux/addr-map.c:

struct addr_map
{
  size_t size;
  struct addr_map_entry entries[0];
};

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2024-05-06 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 23:39 [Bug runtime/31699] New: " wcohen at redhat dot com
2024-05-03 23:59 ` [Bug runtime/31699] " wcohen at redhat dot com
2024-05-04  2:47 ` wcohen at redhat dot com
2024-05-06 14:11 ` wcohen at redhat dot com [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=bug-31699-6586-UZ4qeB9NYo@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).