From: Michal Hocko <mhocko@suse.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Jens Axboe <axboe@kernel.dk>,
Jinliang Zheng <alexjlzheng@tencent.com>,
Mateusz Guzik <mjguzik@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
Tycho Andersen <tandersen@netflix.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] memcg: mm_update_next_owner: kill the "retry" logic
Date: Thu, 27 Jun 2024 09:56:46 +0200 [thread overview]
Message-ID: <Zn0bPrHrBGwdrGwU@tiehlicka> (raw)
In-Reply-To: <20240626152924.GA17933@redhat.com>
On Wed 26-06-24 17:29:24, Oleg Nesterov wrote:
> @@ -446,7 +463,6 @@ void mm_update_next_owner(struct mm_struct *mm)
> {
> struct task_struct *c, *g, *p = current;
>
> -retry:
> /*
> * If the exiting or execing task is not the owner, it's
> * someone else's problem.
> @@ -468,16 +484,16 @@ void mm_update_next_owner(struct mm_struct *mm)
> * Search in the children
> */
> list_for_each_entry(c, &p->children, sibling) {
> - if (c->mm == mm)
> - goto assign_new_owner;
> + if (c->mm == mm && try_to_set_owner(c, mm))
> + goto ret;
You need to unlock tasklist_lock, right? Same for other goto ret.
Other than that the cleanup makes sense and it makes the code much more
easier to follow. It should still die but it can do so in a better
shape.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2024-06-27 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 15:28 [PATCH -mm 0/2] memcg: deuglify mm_update_next_owner() Oleg Nesterov
2024-06-26 15:29 ` [PATCH 1/2] memcg: mm_update_next_owner: kill the "retry" logic Oleg Nesterov
2024-06-27 7:56 ` Michal Hocko [this message]
2024-06-27 8:29 ` Oleg Nesterov
2024-06-27 9:02 ` Michal Hocko
2024-06-26 15:29 ` [PATCH 2/2] memcg: mm_update_next_owner: move for_each_thread() into try_to_set_owner() Oleg Nesterov
2024-06-27 9:02 ` Michal Hocko
2024-06-26 19:24 ` [PATCH -mm 0/2] memcg: deuglify mm_update_next_owner() Andrew Morton
2024-06-26 20:27 ` Oleg Nesterov
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=Zn0bPrHrBGwdrGwU@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=alexjlzheng@tencent.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=oleg@redhat.com \
--cc=tandersen@netflix.com \
--cc=willy@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 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.