From: Jinchao Wang <wangjinchao600@gmail.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Kees Cook <kees@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] exec: do not call sched_mm_cid_after_execve() on exec fail
Date: Thu, 25 Dec 2025 08:01:33 +0800 [thread overview]
Message-ID: <aUx-0YAA7QyjUbka@ndev> (raw)
In-Reply-To: <4b221d91-84f8-4600-83b6-a2aa16a02c57@efficios.com>
On Wed, Dec 24, 2025 at 08:52:16AM -0500, Mathieu Desnoyers wrote:
> On 2025-12-24 07:10, Jinchao Wang wrote:
> > On Thu, Dec 18, 2025 at 11:23:23AM +0800, Jinchao Wang wrote:
> >
> > Hi, mathieu
> >
> > Please review this patch for mm_cid.
>
> Nack. Your fix lacks context and removes a needed call in the
> common case to fix what I understand to be a init task issue.
>
> See this patch instead which addresses an issue very similar to
> yours removing the relevant sched_mm_cid_after_exec() call:
>
> https://lore.kernel.org/lkml/20251223215113.639686-1-xiyou.wangcong@gmail.com/
Yes, they are same issue and this patch works.
Thanks.
>
> I added Thomas Gleixner in CC.
>
> Thanks,
>
> Mathieu
>
> --
> Mathieu Desnoyers
> EfficiOS Inc.
> https://www.efficios.com
next prev parent reply other threads:[~2025-12-25 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 3:23 [PATCH] exec: do not call sched_mm_cid_after_execve() on exec fail Jinchao Wang
2025-12-24 12:10 ` Jinchao Wang
2025-12-24 13:52 ` Mathieu Desnoyers
2025-12-25 0:01 ` Jinchao Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-18 2:24 Jinchao 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=aUx-0YAA7QyjUbka@ndev \
--to=wangjinchao600@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.