[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1db851cc-f1a8-4de6-a01e-37ec091094ce@redhat.com>
Date: Sat, 27 Dec 2025 18:18:34 -0600
From: Eric Sandeen <sandeen@...hat.com>
To: kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com,
Christian Brauner <brauner@...nel.org>, linux-fsdevel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [linux-next:master] [fs] 51a146e059:
BUG:kernel_hang_in_boot_stage
On 12/26/25 2:01 PM, Eric Sandeen wrote:
> On 12/22/25 8:36 PM, kernel test robot wrote:
>>
>>
>> Hello,
>>
>>
>> we don't have enough knowledge to analyze the connection between the issue and
>> this change. just observed the issue is quite persistent on 51a146e059 and
>> clean on its parent.
>
> Odd. Not much to go on, and I don't see any obvious connection either, but
> I'll see if i can reproduce.
I can more or less reproduce, I think, though I am not getting the hung task
warning.
Oddly if I just put the
struct dentry *(*mount) ...
member back in struct file_system_type it seems to resolve the problem.
Even if I give it a different symbol name (like mount_foo).
I'm confused.
-Eric
Powered by blists - more mailing lists