lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 19 Apr 2023 12:49:02 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Peng Zhang <zhangpeng.00@...edance.com>
Cc:     Liam.Howlett@...cle.com, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, maple-tree@...ts.infradead.org
Subject: Re: [PATCH] maple_tree: Fix allocation in mas_sparse_area()

On Wed, 19 Apr 2023 17:36:25 +0800 Peng Zhang <zhangpeng.00@...edance.com> wrote:

> In the case of reverse allocation, mas->index and mas->last do not point
> to the correct allocation range, which will cause users to get incorrect
> allocation results, so fix it. If the user does not use it in a specific
> way, this bug will not be triggered.

Please describe the user-visible effects of the bug.  I assume "none",
because there are presently no callers which can trigger it?

> Also re-checks whether the size is still satisfied after the lower bound
> was increased, which is a corner case and is incorrect in previous versions.

Again, what are the user-visible effects of the bug?


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ