mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yeoreum Yun <yeoreum.yun@arm.com>
To: 83b4d26.3362.19730a21115.Coremail.00107082@163.com
Cc: 00107082@163.com, peterz@infradead.org, mingo@redhat.com,
	acme@kernel.org, namhyung@kernel.org, mingo@kernel.org,
	leo.yan@arm.com, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG][6.15][perf] Kernel panic not syncing: Fatal exception in interrupt
Date: Mon, 2 Jun 2025 14:19:11 +0100	[thread overview]
Message-ID: <aD2kz52p5NHpuXk3@e129823.arm.com> (raw)
In-Reply-To: <aD2TspKH/7yvfYoO@e129823.arm.com>

Hi David,

> Before I start testing, I feel concerned about following chain:
>
> ./kernel/fork.c:
> bad_fork_cleanup_perf:
>     perf_event_free_task()
>         perf_free_event()
>             list_del_event()
>
> This patch seems changes the behavior in this callchain.
> Would this have other side-effect?

What behavior is changed you're worry about?
both error patch is handled by __perf_remove_from_context(),
There wouldn't be no problem since this patch just move the
time of disabling cgroup before changing event state.

also, the cgroup event is for only cpuctx not added in taskctx.
So, there's no effect for event attached in taskctx.

Thanks.

--
Sincerely,
Yeoreum Yun

  parent reply	other threads:[~2025-06-02 13:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 12:06 Yeoreum Yun
2025-06-02 12:33 ` David Wang
2025-06-02 13:19 ` Yeoreum Yun [this message]
2025-06-02 13:31   ` David Wang
2025-06-02 15:13   ` Yeoreum Yun
2025-06-02 15:32     ` David Wang
  -- strict thread matches above, loose matches on Subject: below --
2025-06-01 17:36 David Wang

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=aD2kz52p5NHpuXk3@e129823.arm.com \
    --to=yeoreum.yun@arm.com \
    --cc=00107082@163.com \
    --cc=83b4d26.3362.19730a21115.Coremail.00107082@163.com \
    --cc=acme@kernel.org \
    --cc=leo.yan@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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
all inboxes | Powered by JetHome®