From: Klara Modin <klarasmodin@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>,
kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, x86@kernel.org,
"Darrick J. Wong" <djwong@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [tip:locking/urgent] [jump_label] de752774f3: kernel_BUG_at_arch/x86/kernel/jump_label.c
Date: Tue, 10 Sep 2024 11:40:54 +0200 [thread overview]
Message-ID: <a0d77ee7-ff3c-4c63-903c-e7c9e2fb70c7@gmail.com> (raw)
In-Reply-To: <4a554ab4-b53b-485f-beef-96001100511a@kasm.eu>
On 2024-09-10 11:39, Klara Modin wrote:
> Hi,
>
> On 2024-09-09 12:56, Peter Zijlstra wrote:
>> On Mon, Sep 09, 2024 at 11:15:31AM +0200, Peter Zijlstra wrote:
>>> On Sun, Sep 08, 2024 at 09:06:55PM +0800, kernel test robot wrote:
>>>>
>>>>
>>>> Hello,
>>>>
>>>> kernel test robot noticed
>>>> "kernel_BUG_at_arch/x86/kernel/jump_label.c" on:
>>>>
>>>> commit: de752774f38bb766941ed1bf910ba5a9f6cc6bf7 ("jump_label: Fix
>>>> static_key_slow_dec() yet again")
>>>> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git locking/urgent
>>>>
>>>> in testcase: boot
>>>>
>>>> compiler: clang-18
>>>> test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2
>>>> -m 16G
>>>>
>>>
>>>> The kernel config and materials to reproduce are available at:
>>>> https://download.01.org/0day-ci/archive/20240908/202409082005.393050e2-oliver.sang@intel.com
>>>
>>> So the whole thing actually boots and works on my real machine, so I had
>>> to resort to using this qemu nonsense, as such I did as instructed in
>>> the reproduce file.
>>>
>>> I build the thing using clang-17 (for some reason debian is shitting
>>> itself trying to install clang-18 on this machine and I don't want to
>>> spend the day fighting that).
>>>
>>> Except, once I do:
>>>
>>> bin/lkp qemu -k /usr/src/linux-2.6/tmp-build/arch/x86/boot/bzImage
>>> -m /usr/src/linux-2.6/tmp-build/mod/modules.cgz job-script
>>>
>>> The whole thing grinds to a halt like so:
>>
>> Since I'm not able to reproduce, could you please run the thing against:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
>> locking/urgent
>>
>> and see what that does?
>>
>
> I hit this bug on today's next. Reverting
> de752774f38bb766941ed1bf910ba5a9f6cc6bf7 and applying the updated
> version (6b01e5a8c11611a3dbd3d9efd915427cbce9352a) fixed it for me.
>
> Thanks,
> Tested-by: Klara Modin <klarasmodin@gmail.com>
Sorry, this should now be from my usual email.
next prev parent reply other threads:[~2024-09-10 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 13:06 [tip:locking/urgent] [jump_label] de752774f3: kernel_BUG_at_arch/x86/kernel/jump_label.c kernel test robot
2024-09-09 9:15 ` Peter Zijlstra
2024-09-09 10:56 ` Peter Zijlstra
2024-09-10 9:39 ` Klara Modin
2024-09-10 9:40 ` Klara Modin [this message]
2024-09-11 1:27 ` Oliver Sang
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=a0d77ee7-ff3c-4c63-903c-e7c9e2fb70c7@gmail.com \
--to=klarasmodin@gmail.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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