From: Oleg Nesterov <oleg@redhat.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] exit: combine work under lock in synchronize_group_exit() and coredump_task_exit()
Date: Wed, 19 Mar 2025 19:41:20 +0100 [thread overview]
Message-ID: <20250319184119.GE26879@redhat.com> (raw)
In-Reply-To: <20250319175824.1852420-1-mjguzik@gmail.com>
On 03/19, Mateusz Guzik wrote:
>
> This happens to test to for coredumping prior to handling kcov and
> kmsan, which afaics is harmless.
>
> I however was not comfortable lifting dumping prior to it, so it still
> happens after.
Well, I'd really prefer to move synchronize_group_exit(tsk, code) down,
after kmsan_task_exit() for the start.
Then the patch and resulting code will be simpler, coredump_task_exit()
can be even folded into synchronize_group_exit().
Oleg.
prev parent reply other threads:[~2025-03-19 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 17:58 [PATCH] exit: combine work under lock in synchronize_group_exit() and coredump_task_exit() Mateusz Guzik
2025-03-19 18:41 ` Oleg Nesterov [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=20250319184119.GE26879@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.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