public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: hsimeliere.opensource@witekio.com
Cc: stable@vger.kernel.org,
	Kent Overstreet <kent.overstreet@gmail.com>,
	Bruno VERNAY <bruno.vernay@se.com>
Subject: Re: [PATCH v5.15-v5.4] lib/generic-radix-tree.c: Don't overflow in peek()
Date: Mon, 10 Feb 2025 10:30:32 +0100	[thread overview]
Message-ID: <2025021059-waking-parlor-c55d@gregkh> (raw)
In-Reply-To: <20250210091546.208211-1-hsimeliere.opensource@witekio.com>

On Mon, Feb 10, 2025 at 10:15:46AM +0100, hsimeliere.opensource@witekio.com wrote:
> From: Kent Overstreet <kent.overstreet@gmail.com>
> 
> [ Upstream commit 9492261ff2460252cf2d8de89cdf854c7e2b28a0 ]
> 
> When we started spreading new inode numbers throughout most of the 64
> bit inode space, that triggered some corner case bugs, in particular
> some integer overflows related to the radix tree code. Oops.
> 
> Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
> Signed-off-by: Bruno VERNAY <bruno.vernay@se.com>
> Signed-off-by: Hugo SIMELIERE <hsimeliere.opensource@witekio.com>
> ---
>  include/linux/generic-radix-tree.h |  7 +++++++
>  lib/generic-radix-tree.c           | 17 ++++++++++++++---
>  2 files changed, 21 insertions(+), 3 deletions(-)

Why is this needed in these older kernels?  Is there an existing
workload that triggers this that this fixes?

thanks,

greg k-h

  reply	other threads:[~2025-02-10  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10  9:15 [PATCH v5.15-v5.4] lib/generic-radix-tree.c: Don't overflow in peek() hsimeliere.opensource
2025-02-10  9:30 ` Greg KH [this message]
2025-02-10  9:39   ` hsimeliere.opensource
2025-02-10  9:55     ` Greg KH

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=2025021059-waking-parlor-c55d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bruno.vernay@se.com \
    --cc=hsimeliere.opensource@witekio.com \
    --cc=kent.overstreet@gmail.com \
    --cc=stable@vger.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