From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@linux-foundation.org, lance.yang@linux.dev,
mhiramat@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/hung_task: unexport sysctl_hung_task_timeout_secs
Date: Wed, 5 Nov 2025 08:44:37 +0900 [thread overview]
Message-ID: <20251105084437.b601327ddbaf3ed149c9b2a5@kernel.org> (raw)
In-Reply-To: <20251104121920.2430568-1-hch@lst.de>
On Tue, 4 Nov 2025 07:19:20 -0500
Christoph Hellwig <hch@lst.de> wrote:
> This was added by the bcachefs pull requests despite various
> objections, and with bcachefs removed is now unused.
>
> This reverts commit 5c3273ec3c6af356b29ff50a654f0dc33bf25a83.
>
Looks good to me.
Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thanks!
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> kernel/hung_task.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kernel/hung_task.c b/kernel/hung_task.c
> index b2c1f14b8129..1dfb9bc1bdef 100644
> --- a/kernel/hung_task.c
> +++ b/kernel/hung_task.c
> @@ -50,7 +50,6 @@ static unsigned long __read_mostly sysctl_hung_task_detect_count;
> * Zero means infinite timeout - no checking done:
> */
> unsigned long __read_mostly sysctl_hung_task_timeout_secs = CONFIG_DEFAULT_HUNG_TASK_TIMEOUT;
> -EXPORT_SYMBOL_GPL(sysctl_hung_task_timeout_secs);
>
> /*
> * Zero (default value) means use sysctl_hung_task_timeout_secs:
> --
> 2.47.3
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2025-11-04 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 12:19 [PATCH] kernel/hung_task: unexport sysctl_hung_task_timeout_secs Christoph Hellwig
2025-11-04 12:56 ` Lance Yang
2025-11-04 23:44 ` Masami Hiramatsu [this message]
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=20251105084437.b601327ddbaf3ed149c9b2a5@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.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