From: Marco Elver <elver@google.com>
To: Pavankumar Kondeti <quic_pkondeti@quicinc.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Peter Zijlstra <peterz@infradead.org>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/kfence: remove hung_task cruft
Date: Mon, 14 Nov 2022 08:00:00 +0100 [thread overview]
Message-ID: <CANpmjNNYRg7sYTxKN_YCts7wqGfr-2YZbw+pwdO5nTZp_bBVfg@mail.gmail.com> (raw)
In-Reply-To: <1667986006-25420-1-git-send-email-quic_pkondeti@quicinc.com>
On Wed, 9 Nov 2022 at 10:26, Pavankumar Kondeti
<quic_pkondeti@quicinc.com> wrote:
>
> commit fdf756f71271 ("sched: Fix more TASK_state comparisons") makes
> hung_task not to monitor TASK_IDLE tasks. The special handling to
> workaround hung_task warnings is not required anymore.
>
> Signed-off-by: Pavankumar Kondeti <quic_pkondeti@quicinc.com>
Good riddance, thanks.
Reviewed-by: Marco Elver <elver@google.com>
> ---
> mm/kfence/core.c | 12 +-----------
> 1 file changed, 1 insertion(+), 11 deletions(-)
>
> diff --git a/mm/kfence/core.c b/mm/kfence/core.c
> index 1417888..08f5bd6 100644
> --- a/mm/kfence/core.c
> +++ b/mm/kfence/core.c
> @@ -26,7 +26,6 @@
> #include <linux/random.h>
> #include <linux/rcupdate.h>
> #include <linux/sched/clock.h>
> -#include <linux/sched/sysctl.h>
> #include <linux/seq_file.h>
> #include <linux/slab.h>
> #include <linux/spinlock.h>
> @@ -799,16 +798,7 @@ static void toggle_allocation_gate(struct work_struct *work)
> /* Enable static key, and await allocation to happen. */
> static_branch_enable(&kfence_allocation_key);
>
> - if (sysctl_hung_task_timeout_secs) {
> - /*
> - * During low activity with no allocations we might wait a
> - * while; let's avoid the hung task warning.
> - */
> - wait_event_idle_timeout(allocation_wait, atomic_read(&kfence_allocation_gate),
> - sysctl_hung_task_timeout_secs * HZ / 2);
> - } else {
> - wait_event_idle(allocation_wait, atomic_read(&kfence_allocation_gate));
> - }
> + wait_event_idle(allocation_wait, atomic_read(&kfence_allocation_gate));
>
> /* Disable static key and reset timer. */
> static_branch_disable(&kfence_allocation_key);
> --
> 2.7.4
>
prev parent reply other threads:[~2022-11-14 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 9:26 Pavankumar Kondeti
2022-11-14 7:00 ` Marco Elver [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=CANpmjNNYRg7sYTxKN_YCts7wqGfr-2YZbw+pwdO5nTZp_bBVfg@mail.gmail.com \
--to=elver@google.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=quic_pkondeti@quicinc.com \
/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