From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Linux Media Mailing List" <linux-media@vger.kernel.org>,
linaro-mm-sig@lists.linaro.org,
"Linux DRI Development" <dri-devel@lists.freedesktop.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Linux Regressions" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] BUG: KFENCE: memory corruption in drm_gem_put_pages+0x186/0x250
Date: Mon, 2 Oct 2023 17:40:43 +0700 [thread overview]
Message-ID: <ZRqeK_OgfDS4liMt@debian.me> (raw)
In-Reply-To: <13360591.uLZWGnKmhe@natalenko.name>
[-- Attachment #1: Type: text/plain, Size: 2399 bytes --]
On Sun, Oct 01, 2023 at 06:32:34PM +0200, Oleksandr Natalenko wrote:
> Hello.
>
> I've got a VM from a cloud provider, and since v6.5 I observe the following kfence splat in dmesg during boot:
>
> ```
> BUG: KFENCE: memory corruption in drm_gem_put_pages+0x186/0x250
>
> Corrupted memory at 0x00000000e173a294 [ ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ] (in kfence-#108):
> drm_gem_put_pages+0x186/0x250
> drm_gem_shmem_put_pages_locked+0x43/0xc0
> drm_gem_shmem_object_vunmap+0x83/0xe0
> drm_gem_vunmap_unlocked+0x46/0xb0
> drm_fbdev_generic_helper_fb_dirty+0x1dc/0x310
> drm_fb_helper_damage_work+0x96/0x170
> process_one_work+0x254/0x470
> worker_thread+0x55/0x4f0
> kthread+0xe8/0x120
> ret_from_fork+0x34/0x50
> ret_from_fork_asm+0x1b/0x30
>
> kfence-#108: 0x00000000cda343af-0x00000000aec2c095, size=3072, cache=kmalloc-4k
>
> allocated by task 51 on cpu 0 at 14.668667s:
> drm_gem_get_pages+0x94/0x2b0
> drm_gem_shmem_get_pages+0x5d/0x110
> drm_gem_shmem_object_vmap+0xc4/0x1e0
> drm_gem_vmap_unlocked+0x3c/0x70
> drm_client_buffer_vmap+0x23/0x50
> drm_fbdev_generic_helper_fb_dirty+0xae/0x310
> drm_fb_helper_damage_work+0x96/0x170
> process_one_work+0x254/0x470
> worker_thread+0x55/0x4f0
> kthread+0xe8/0x120
> ret_from_fork+0x34/0x50
> ret_from_fork_asm+0x1b/0x30
>
> freed by task 51 on cpu 0 at 14.668697s:
> drm_gem_put_pages+0x186/0x250
> drm_gem_shmem_put_pages_locked+0x43/0xc0
> drm_gem_shmem_object_vunmap+0x83/0xe0
> drm_gem_vunmap_unlocked+0x46/0xb0
> drm_fbdev_generic_helper_fb_dirty+0x1dc/0x310
> drm_fb_helper_damage_work+0x96/0x170
> process_one_work+0x254/0x470
> worker_thread+0x55/0x4f0
> kthread+0xe8/0x120
> ret_from_fork+0x34/0x50
> ret_from_fork_asm+0x1b/0x30
>
> CPU: 0 PID: 51 Comm: kworker/0:2 Not tainted 6.5.0-pf4 #1 8b557a4173114d86eef7240f7a080080cfc4617e
> Hardware name: Red Hat KVM, BIOS 1.11.0-2.el7 04/01/2014
> Workqueue: events drm_fb_helper_damage_work
> ```
>
> This repeats a couple of times and then stops.
>
> Currently, I'm running v6.5.5. So far, there's no impact on how VM functions for me.
>
> The VGA adapter is as follows: 00:02.0 VGA compatible controller: Cirrus Logic GD 5446
>
Thanks for the regression report. I'm adding it to regzbot:
#regzbot ^introduced: v6.4..v6.5
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-02 10:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 16:32 Oleksandr Natalenko
2023-10-01 23:45 ` Bagas Sanjaya
2023-10-02 6:20 ` Oleksandr Natalenko
2023-10-02 10:42 ` Bagas Sanjaya
2023-10-02 11:02 ` Oleksandr Natalenko
2023-10-02 14:32 ` Matthew Wilcox
2023-10-02 15:38 ` Oleksandr Natalenko
2023-10-05 7:44 ` Thomas Zimmermann
2023-10-05 7:56 ` Oleksandr Natalenko
2023-10-05 12:19 ` Matthew Wilcox
2023-10-05 12:30 ` Oleksandr Natalenko
2023-10-05 13:05 ` Matthew Wilcox
2023-10-05 13:34 ` Oleksandr Natalenko
2023-10-02 10:40 ` Bagas Sanjaya [this message]
2023-10-05 7:42 ` Thomas Zimmermann
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=ZRqeK_OgfDS4liMt@debian.me \
--to=bagasdotme@gmail.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=oleksandr@natalenko.name \
--cc=regressions@lists.linux.dev \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
/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
Powered by JetHome