All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Max Kellermann <max.kellermann@ionos.com>,
	dhowells@redhat.com, netfs@lists.linux.dev,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v6.13 v2] fs/netfs/read_collect: fix crash due to uninitialized `prev` variable
Date: Mon, 10 Mar 2025 12:51:25 +0100	[thread overview]
Message-ID: <2025031020-unframed-blast-a985@gregkh> (raw)
In-Reply-To: <a3ad0b7e8b5e16ee25cbc692798c0858e55a1b0c.camel@sipsolutions.net>

On Fri, Mar 07, 2025 at 03:27:41PM +0100, Johannes Berg wrote:
> On Fri, 2025-02-14 at 14:12 +0100, Max Kellermann wrote:
> > When checking whether the edges of adjacent subrequests touch, the
> > `prev` variable is deferenced, but it might not have been initialized.
> > This causes crashes like this one:
> 
> [...]
> 
> I believe we also need this in 6.12?

Now added, thanks.

greg k-h

      reply	other threads:[~2025-03-10 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 13:12 [PATCH v6.13 v2] fs/netfs/read_collect: fix crash due to uninitialized `prev` variable Max Kellermann
2025-02-14 13:16 ` David Howells
2025-02-14 13:21 ` kernel test robot
2025-02-14 13:30 ` Patch "fs/netfs/read_collect: fix crash due to uninitialized `prev` variable" has been added to the 6.13-stable tree gregkh
2025-03-07 14:27 ` [PATCH v6.13 v2] fs/netfs/read_collect: fix crash due to uninitialized `prev` variable Johannes Berg
2025-03-10 11:51   ` Greg Kroah-Hartman [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=2025031020-unframed-blast-a985@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dhowells@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max.kellermann@ionos.com \
    --cc=netfs@lists.linux.dev \
    --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 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.