From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Yang <andrew.yang@mediatek.com>
Cc: Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
wsd_upstream@mediatek.com, casper.li@mediatek.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH] zsmalloc: Fix races between modifications of fullness and isolated
Date: Wed, 26 Jul 2023 11:57:11 +0900 [thread overview]
Message-ID: <20230726025711.GI955071@google.com> (raw)
In-Reply-To: <20230726023122.GH955071@google.com>
On (23/07/26 11:31), Sergey Senozhatsky wrote:
> On (23/07/21 14:37), Andrew Yang wrote:
> >
> > Since fullness and isolated share the same unsigned int,
> > modifications of them should be protected by the same lock.
>
> Sorry, I don't think I follow. Can you please elaborate?
> What is fullness in this context?
Oh, my bad, so that's zspage's fullness:FULLNESS_BITS and
isolated:ISOLATED_BITS. I somehow thought about something
very different (page isolated, not zspage isolated).
next prev parent reply other threads:[~2023-07-26 2:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 6:37 [PATCH] zsmalloc: Fix races between modifications of fullness and isolated Andrew Yang
2023-07-21 6:37 ` Andrew Yang
2023-07-26 2:31 ` Sergey Senozhatsky
2023-07-26 2:57 ` Sergey Senozhatsky [this message]
2023-07-26 3:18 ` Sergey Senozhatsky
2023-07-26 6:59 ` Andrew Yang (楊智強)
2023-07-26 11:31 ` Sergey Senozhatsky
2023-07-26 20:18 ` Andrew Morton
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=20230726025711.GI955071@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=andrew.yang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bigeasy@linutronix.de \
--cc=casper.li@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=minchan@kernel.org \
--cc=wsd_upstream@mediatek.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 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.