linux-kernel - Re: 6.18/regression/bisected – BUG: sleeping function called from invalid context at ./include/linux/sched/mm.h:321 after 6d31602a9f57

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CABXGCsP-haMF=kMkfOVBr8AjQLvfGr1ncgqstHrYyDWY5ZABHA@mail.gmail.com>
Date: Mon, 13 Oct 2025 16:03:49 +0500
From: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To: "Pillai, Aurabindo" <Aurabindo.Pillai@....com>
Cc: "Kazlauskas, Nicholas" <Nicholas.Kazlauskas@....com>, "Wu, Ray" <Ray.Wu@....com>, 
	"Wheeler, Daniel" <Daniel.Wheeler@....com>, "Li, Roman" <Roman.Li@....com>, 
	"Chung, ChiaHsuan (Tom)" <ChiaHsuan.Chung@....com>, "Deucher, Alexander" <Alexander.Deucher@....com>, 
	amd-gfx list <amd-gfx@...ts.freedesktop.org>, 
	Linux List Kernel Mailing <linux-kernel@...r.kernel.org>, 
	Linux regressions mailing list <regressions@...ts.linux.dev>
Subject: Re: 6.18/regression/bisected – BUG: sleeping function called from invalid context at ./include/linux/sched/mm.h:321 after 6d31602a9f57

On Tue, Oct 7, 2025 at 10:55 PM Pillai, Aurabindo
<Aurabindo.Pillai@....com> wrote:
>
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hi Mikhail,
>
> schedule_dc_vmin_vmax() has an allocation which is incorrectly using GFP_KERNEL, which is likely the reason for the "sleeping function called from invalid context". We have a fix queued for this week's update (switching it to GFP_NOWAIT).
>

Hi Aurabindo,

6.18.0-rc1 still requires reverting commits 9d6939179491 and 6d31602a9f57
to avoid the “sleeping function called from invalid context” warnings.

The good news is that the separate WARN previously triggered at
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:138 amdgpu_vm_set_pasid()
no longer appears in recent builds.
This WARN was a merge-only side effect (interaction between drm-next
and amd-drm-next),
though it’s unclear which exact change resolved it.

Logs for both cases are attached.

-- 
Best Regards,
Mike Gavrilov.

Download attachment "dmesg-6.18.0-rc1-revert-9d6939179491-6d31602a9f57.zip" of type "application/zip" (46739 bytes)

Download attachment "dmesg-6.18.0-rc1.zip" of type "application/zip" (78012 bytes)