All of lore.kernel.org
 help / color / mirror / Atom feed
From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	luogengkun@huaweicloud.com,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	dianders@chromium.org, joel.granados@kernel.org, song@kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [linux-next]Build Failure: kernel/watchdog.c:936:2: error: too many arguments
Date: Wed, 30 Apr 2025 11:57:12 +0530	[thread overview]
Message-ID: <562a79d1-e8a4-4d8f-a576-47c017aadf93@linux.ibm.com> (raw)
In-Reply-To: <33aabaae-5789-4b67-bd06-06b79d03ea38@linux.ibm.com>


On 28/04/25 3:11 pm, Venkat Rao Bagalkote wrote:
>
> On 28/04/25 4:11 am, Stephen Rothwell wrote:
>> Hi all,
>>
>> On Sat, 26 Apr 2025 20:39:26 +0530 Venkat Rao Bagalkote 
>> <venkat88@linux.ibm.com> wrote:
>>> I am observing below build failure on IBM Power8 server with 
>>> linux-next-20250424 repo.
>>>
>>> This issue seems to be introduced by the below commit. After 
>>> reverting the below commit, kernel build is successful.
>>>
>>> Bad Commit: 6b07f9a0fa41 watchdog: fix watchdog may detect false 
>>> positive of softlockup
>>>
>>> Note: To hit this issue, one should first resolve this [1] 
>>> <https://lore.kernel.org/all/e8bf676e-7bf0-4896-b104-ac75e1b22d2e@linux.ibm.com/>
>>>
>>> Repo: 
>>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>> Branch: master
>>> GCC: 8.5.0 20210514
>>> ldd (GNU libc) 2.28
>>>
>>> Attached is the .config file.
>>>
>>> Errors:
>>>
>>> kernel/watchdog.c: In function 'lockup_detector_reconfigure':
>>> kernel/watchdog.c:936:2: error: too many arguments to function 
>>> '__lockup_detector_reconfigure'
>>>     __lockup_detector_reconfigure(false);
>>>     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kernel/watchdog.c:926:13: note: declared here
>>>    static void __lockup_detector_reconfigure(void)
>>>                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kernel/watchdog.c: In function 'lockup_detector_setup':
>>> kernel/watchdog.c:940:2: error: too many arguments to function 
>>> '__lockup_detector_reconfigure'
>>>     __lockup_detector_reconfigure(false);
>>>     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kernel/watchdog.c:926:13: note: declared here
>>>    static void __lockup_detector_reconfigure(void)
>>>                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kernel/watchdog.c: In function 'proc_watchdog_update':
>>> kernel/watchdog.c:962:2: error: too many arguments to function 
>>> '__lockup_detector_reconfigure'
>>>     __lockup_detector_reconfigure(thresh_changed);
>>>     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> kernel/watchdog.c:926:13: note: declared here
>>>    static void __lockup_detector_reconfigure(void)
>>>                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> If you happen to fix this, please add below tag.
>>>
>>> Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
>> Yeah, the CONFIG_SOFTLOCKUP_DETECTOR unset version of
>> __lockup_detector_reconfigure() was not updated :-(
>

Hello Stephen,


Will this be fixed, or from now on we will have to set the 
SOFTLOCKUP_DETECTOR always in the .config file.


Trying to understand the way forward.


Regards,

Venkat.

>
> After seeting CONFIG_SOFTLOCKUP_DETECTOR kernel build is successful.
>
>
> Regards,
>
> Venkat.
>
>>
>> This is now commit
>>
>>    45c4eb661074 ("watchdog: fix watchdog may detect false positive of 
>> softlockup")
>>
>> in the mm-nonmm-unstable tree.
>>

  reply	other threads:[~2025-04-30  6:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-26 15:09 [linux-next]Build Failure: kernel/watchdog.c:936:2: error: too many arguments Venkat Rao Bagalkote
2025-04-27 22:41 ` Stephen Rothwell
2025-04-28  6:13   ` Venkat Rao Bagalkote
2025-04-28  9:41   ` Venkat Rao Bagalkote
2025-04-30  6:27     ` Venkat Rao Bagalkote [this message]
2025-04-30 10:55       ` Stephen Rothwell
2025-05-02 11:11         ` [PATCH] watchdog: Fix the SOFTLOCKUP_DETECTOR=n case Nysal Jan K.A.
2025-05-02 12:00           ` Venkat Rao Bagalkote

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=562a79d1-e8a4-4d8f-a576-47c017aadf93@linux.ibm.com \
    --to=venkat88@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dianders@chromium.org \
    --cc=joel.granados@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=luogengkun@huaweicloud.com \
    --cc=maddy@linux.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=song@kernel.org \
    --cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.