From: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
To: Waiman Long <longman@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Vladimir Davydov <vdavydov.dev@gmail.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel@openvz.org
Subject: Re: [PATCH] mm/memcontrol: stop resize loop if limit was changed again
Date: Thu, 21 Mar 2024 13:15:51 +0800 [thread overview]
Message-ID: <18c39901-d1bb-45ab-86ae-1a74c3ff8060@virtuozzo.com> (raw)
In-Reply-To: <be05a470-bb31-47ef-b786-557c347de429@redhat.com>
On 21/03/2024 01:09, Waiman Long wrote:
>
> On 3/20/24 06:03, Pavel Tikhomirov wrote:
>> In memory_max_write() we first set memcg->memory.max and only then
>> try to enforce it in loop. What if while we are in loop someone else
>> have changed memcg->memory.max but we are still trying to enforce
>> the old value? I believe this can lead to nasty consequence like getting
>> an oom on perfectly fine cgroup within it's limits or excess reclaim.
>
> Concurrent write to the same cgroup control file is not possible as the
> underlying kernfs_open_file structure has a mutex that serialize access
> to the file. Concurrent write to different cgroup control files is
> possible, though.
Thanks for pointing this out, now I see it, in kernfs_fop_write_iter()
we take of->mutex before ops->write() -> cgroup_file_write(). That means
patch is not needed.
>
> Cheers,
> Longman
>
>>
>> We also have exactly the same thing in memory_high_write().
>>
>> So let's stop enforcing old limits if we already have a new ones.
>>
>> Signed-off-by: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
>> ---
>> mm/memcontrol.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>> index 61932c9215e7..81b303728491 100644
>> --- a/mm/memcontrol.c
>> +++ b/mm/memcontrol.c
>> @@ -6769,6 +6769,9 @@ static ssize_t memory_high_write(struct
>> kernfs_open_file *of,
>> unsigned long nr_pages = page_counter_read(&memcg->memory);
>> unsigned long reclaimed;
>> + if (memcg->memory.high != high)
>> + break;
>> +
>> if (nr_pages <= high)
>> break;
>> @@ -6817,6 +6820,9 @@ static ssize_t memory_max_write(struct
>> kernfs_open_file *of,
>> for (;;) {
>> unsigned long nr_pages = page_counter_read(&memcg->memory);
>> + if (memcg->memory.max != max)
>> + break;
>> +
>> if (nr_pages <= max)
>> break;
>
--
Best regards, Tikhomirov Pavel
Senior Software Developer, Virtuozzo.
prev parent reply other threads:[~2024-03-21 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 10:03 Pavel Tikhomirov
2024-03-20 10:28 ` Michal Hocko
2024-03-20 10:55 ` Pavel Tikhomirov
2024-03-20 12:09 ` Michal Hocko
2024-03-20 22:38 ` Roman Gushchin
2024-03-20 17:09 ` Waiman Long
2024-03-20 17:12 ` Michal Hocko
2024-03-20 17:38 ` Michal Hocko
2024-03-21 5:15 ` Pavel Tikhomirov [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=18c39901-d1bb-45ab-86ae-1a74c3ff8060@virtuozzo.com \
--to=ptikhomirov@virtuozzo.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=vdavydov.dev@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