public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 215445] AMDGPU -- UBSAN: invalid-load in amdgpu_dm.c:5882:84 - load of value 32 is not a valid value for type '_Bool'
Date: Tue, 11 Jan 2022 11:42:46 +0000	[thread overview]
Message-ID: <bug-215445-2300-bCkAD5r6Zj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215445-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215445

talktome7468@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |talktome7468@gmail.com

--- Comment #6 from talktome7468@gmail.com ---
UBSAN is enabled for the 5.15 kernels since 5.15.8. It is not enabled for the
5.16 kernels. Check the build log files to confirm that ubsan.o is linked into
the kernel for 5.15, but not 5.16.


Also check out the discussion in
https://gitlab.freedesktop.org/drm/amd/-/issues/1779.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-01-11 11:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  3:34 [Bug 215445] New: UBSAN: invalid-load in amdgpu_dm.c:5882:84 - load of value 32 is not a valid value for type '_Bool' bugzilla-daemon
2022-01-03  3:38 ` [Bug 215445] " bugzilla-daemon
2022-01-03  3:41 ` bugzilla-daemon
2022-01-03  3:54 ` [Bug 215445] AMDGPU -- " bugzilla-daemon
2022-01-05 12:45 ` bugzilla-daemon
2022-01-06 22:05 ` bugzilla-daemon
2022-01-11 10:25 ` bugzilla-daemon
2022-01-11 11:42 ` bugzilla-daemon [this message]
2022-01-12 20:23 ` bugzilla-daemon
2022-01-13  2:50 ` bugzilla-daemon

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-215445-2300-bCkAD5r6Zj@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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