public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Sima Vetter <sima@ffwll.ch>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm fixes for 6.13-rc1
Date: Fri, 29 Nov 2024 10:51:54 -0500	[thread overview]
Message-ID: <Z0njGuEof47TzpMc@sashalap> (raw)
In-Reply-To: <CAPM=9tzpFOhQN3yCb4+OpLsfYVrq4mLuUS+SP=H=gq=qSLDz7g@mail.gmail.com>

On Fri, Nov 29, 2024 at 06:42:18AM +1000, Dave Airlie wrote:
>Hi Linus,
>
>Merge window fixes, mostly amdgpu and xe, with a few other minor ones,
>all looks fairly normal,

Hi folks,

I've also started seeing the following warning after the merge into
linus-next:

[    4.495349] UBSAN: shift-out-of-bounds in ./include/linux/log2.h:57:13
[    4.501876] shift exponent 32 is too large for 32-bit type 'long unsigned int'
[    4.509101] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.0 #1
[    4.510096] Hardware name: Google Shuboz/Shuboz, BIOS Google_Shuboz.13434.780.2022_10_13_1418 09/12/2022
[    4.510096] Call Trace:
[    4.510096]  dump_stack_lvl+0x94/0xa4
[    4.510096]  dump_stack+0x12/0x18
[    4.510096]  __ubsan_handle_shift_out_of_bounds+0x156/0x320
[    4.510096]  amdgpu_vm_adjust_size.cold+0x64/0x6c
[    4.510096]  ? __lock_release.isra.0+0x5d/0x170
[    4.510096]  ? amdgpu_device_skip_hw_access.part.0+0x6a/0x70
[    4.510096]  ? gmc_v9_0_init_mem_ranges+0x14c/0x14c
[    4.510096]  gmc_v9_0_sw_init+0x436/0x7c0
[    4.510096]  ? nbio_v7_0_vcn_doorbell_range+0x74/0x74
[    4.510096]  ? gmc_v9_0_init_mem_ranges+0x14c/0x14c
[    4.510096]  amdgpu_device_ip_init+0xd4/0xa74
[    4.510096]  amdgpu_device_init+0xc4a/0x1458
[    4.510096]  amdgpu_driver_load_kms+0x19/0x9c
[    4.510096]  amdgpu_pci_probe+0x153/0x570
[    4.510096]  ? _raw_spin_unlock_irqrestore+0x2f/0x58
[    4.510096]  pci_device_probe+0x8c/0x118
[    4.510096]  ? sysfs_create_link+0x1d/0x38
[    4.510096]  really_probe+0xc2/0x2ac
[    4.510096]  ? _raw_spin_unlock_irq+0x1d/0x38
[    4.510096]  ? pm_runtime_barrier+0x52/0x90
[    4.510096]  __driver_probe_device+0x7a/0x180
[    4.510096]  ? __driver_attach+0x8e/0x188
[    4.510096]  driver_probe_device+0x23/0x108
[    4.510096]  __driver_attach+0x97/0x188
[    4.510096]  ? __device_attach_driver+0x120/0x120
[    4.510096]  bus_for_each_dev+0x71/0xc0
[    4.510096]  driver_attach+0x19/0x20
[    4.510096]  ? __device_attach_driver+0x120/0x120
[    4.510096]  bus_add_driver+0xc9/0x208
[    4.510096]  driver_register+0x52/0x10c
[    4.510096]  ? drm_sched_fence_slab_init+0x80/0x80
[    4.510096]  __pci_register_driver+0x5f/0x68
[    4.510096]  amdgpu_init+0x62/0xb0
[    4.510096]  do_one_initcall+0x63/0x2a8
[    4.510096]  ? rdinit_setup+0x40/0x40
[    4.510096]  ? parse_args+0x14b/0x3f4
[    4.510096]  do_initcalls+0xbc/0x148
[    4.510096]  ? rdinit_setup+0x40/0x40
[    4.510096]  kernel_init_freeable+0x15b/0x1fc
[    4.510096]  ? kernel_init+0x18/0x1f4
[    4.510096]  ? rest_init+0x1cc/0x1cc
[    4.510096]  kernel_init+0x18/0x1f4
[    4.510096]  ? schedule_tail+0x50/0x60
[    4.510096]  ret_from_fork+0x38/0x44
[    4.510096]  ? rest_init+0x1cc/0x1cc
[    4.510096]  ret_from_fork_asm+0x12/0x18
[    4.510096]  entry_INT80_32+0x108/0x108

-- 
Thanks,
Sasha

  parent reply	other threads:[~2024-11-29 15:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28 20:42 [git pull] drm fixes for 6.13-rc1 Dave Airlie
2024-11-29  5:11 ` Sasha Levin
2024-11-29 15:51 ` Sasha Levin [this message]
2024-11-29 21:31 ` Linus Torvalds
2024-11-29 22:59   ` Sasha Levin
2024-11-30  4:29     ` Linus Torvalds
2024-12-02 14:10   ` Alex Deucher
2024-11-29 21:33 ` pr-tracker-bot

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=Z0njGuEof47TzpMc@sashalap \
    --to=sashal@kernel.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sima@ffwll.ch \
    --cc=torvalds@linux-foundation.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