From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Anastasia Belova <abelova@astralinux.ru>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH] mm/zsmalloc: prevent integer overflow in obj_free
Date: Tue, 25 Mar 2025 12:24:41 +0900 [thread overview]
Message-ID: <cn34qjr6ozsb7sgmomgd2srdxsl5n6eruihdaqa3yhtqfsrcjn@zzq6lmghwipx> (raw)
In-Reply-To: <ad70d906-8889-40d3-9af6-6a2be68faf77@astralinux.ru>
On (25/03/20 12:12), Anastasia Belova wrote:
> If address (and unsigned long) is 64-bit, the result of multiplication
> won't fit 32-bit integer. Please correct me if I'm wrong.
Even if we'd consider s32 that should be an object offset of more
than 2B bytes within its zspage, we never have anything like this.
prev parent reply other threads:[~2025-03-25 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 11:51 Anastasia Belova
2025-03-13 14:42 ` Sergey Senozhatsky
2025-03-20 9:12 ` Anastasia Belova
2025-03-25 3:24 ` Sergey Senozhatsky [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=cn34qjr6ozsb7sgmomgd2srdxsl5n6eruihdaqa3yhtqfsrcjn@zzq6lmghwipx \
--to=senozhatsky@chromium.org \
--cc=abelova@astralinux.ru \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lvc-project@linuxtesting.org \
--cc=minchan@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox