mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Levi Yun <yeoreum.yun@arm.com>
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2] trace/pid_list: Change gfp flags in pid_list_fill_irq()
Date: Fri, 5 Jul 2024 23:11:12 +0900	[thread overview]
Message-ID: <20240705231112.4097fd46656778115acf7da1@kernel.org> (raw)
In-Reply-To: <20240704150226.1359936-1-yeoreum.yun@arm.com>

On Thu,  4 Jul 2024 16:02:26 +0100
Levi Yun <yeoreum.yun@arm.com> wrote:

> From: "levi.yun" <yeoreum.yun@arm.com>
> 
> pid_list_fill_irq() runs via irq_work.
> When CONFIG_PREEMPT_RT is disabled, it would run in irq_context.
> so it shouldn't sleep while memory allocation.
> 
> Change gfp flags from GFP_KERNEL to GFP_NOWAIT to prevent sleep in
> irq_work.
> 
> This change wouldn't impact functionality in practice because the worst-size
> is 2K.
> 

Looks good to me.

Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

and 

Fixes: 8d6e90983ade ("tracing: Create a sparse bitmask for pid filtering")

Thank you,

> Signed-off-by: levi.yun <yeoreum.yun@arm.com>
> ---
>  kernel/trace/pid_list.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/pid_list.c b/kernel/trace/pid_list.c
> index 95106d02b32d..85de221c0b6f 100644
> --- a/kernel/trace/pid_list.c
> +++ b/kernel/trace/pid_list.c
> @@ -354,7 +354,7 @@ static void pid_list_refill_irq(struct irq_work *iwork)
>  	while (upper_count-- > 0) {
>  		union upper_chunk *chunk;
> 
> -		chunk = kzalloc(sizeof(*chunk), GFP_KERNEL);
> +		chunk = kzalloc(sizeof(*chunk), GFP_NOWAIT);
>  		if (!chunk)
>  			break;
>  		*upper_next = chunk;
> @@ -365,7 +365,7 @@ static void pid_list_refill_irq(struct irq_work *iwork)
>  	while (lower_count-- > 0) {
>  		union lower_chunk *chunk;
> 
> -		chunk = kzalloc(sizeof(*chunk), GFP_KERNEL);
> +		chunk = kzalloc(sizeof(*chunk), GFP_NOWAIT);
>  		if (!chunk)
>  			break;
>  		*lower_next = chunk;
> --
> LEVI:{C3F47F37-75D8-414A-A8BA-3980EC8A46D7}
> 
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2024-07-05 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04 15:02 Levi Yun
2024-07-05 14:11 ` 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=20240705231112.4097fd46656778115acf7da1@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.org \
    --cc=yeoreum.yun@arm.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

all inboxes | Powered by JetHome®