From: Christian Brauner <brauner@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>,
Max Kellermann <max.kellermann@ionos.com>,
Paulo Alcantara <pc@manguebit.org>,
netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3 REPOST] netfs: fix reference leak
Date: Fri, 26 Sep 2025 10:14:56 +0200 [thread overview]
Message-ID: <20250926-buche-fragment-4839b9d8930c@brauner> (raw)
In-Reply-To: <936424.1758805700@warthog.procyon.org.uk>
On Thu, 25 Sep 2025 14:08:20 +0100, David Howells wrote:
> Commit 20d72b00ca81 ("netfs: Fix the request's work item to not
> require a ref") modified netfs_alloc_request() to initialize the
> reference counter to 2 instead of 1. The rationale was that the
> requet's "work" would release the second reference after completion
> (via netfs_{read,write}_collection_worker()). That works most of the
> time if all goes well.
>
> [...]
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/1] netfs: fix reference leak
https://git.kernel.org/vfs/vfs/c/4d428dca252c
prev parent reply other threads:[~2025-09-26 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 9:38 [PATCH v3] netfs: fix reference leak David Howells
2025-09-25 13:06 ` David Howells
2025-09-25 13:08 ` [PATCH v3 REPOST] " David Howells
2025-09-26 8:14 ` Christian Brauner [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=20250926-buche-fragment-4839b9d8930c@brauner \
--to=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=netfs@lists.linux.dev \
--cc=pc@manguebit.org \
--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;
as well as URLs for NNTP newsgroup(s).