From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: error path fixes for btrfs_link() and a cleanup
Date: Mon, 28 Jul 2025 10:39:45 +0100 [thread overview]
Message-ID: <cover.1753469762.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Fix a couple bugs in the error paths for btrfs_link() and a cleanup to make
it more simple.
Filipe Manana (3):
btrfs: abort transaction on failure to add link to inode
btrfs: fix inode leak on failure to add link to inode
btrfs: simplify error handling logic for btrfs_link()
fs/btrfs/inode.c | 43 +++++++++++++++++++++----------------------
1 file changed, 21 insertions(+), 22 deletions(-)
--
2.47.2
next reply other threads:[~2025-07-28 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 9:39 fdmanana [this message]
2025-07-28 9:39 ` [PATCH 1/3] btrfs: abort transaction on failure to add link to inode fdmanana
2025-07-28 14:42 ` Johannes Thumshirn
2025-07-28 9:39 ` [PATCH 2/3] btrfs: fix inode leak " fdmanana
2025-07-28 14:43 ` Johannes Thumshirn
2025-07-28 9:39 ` [PATCH 3/3] btrfs: simplify error handling logic for btrfs_link() fdmanana
2025-07-28 14:42 ` Johannes Thumshirn
2025-07-28 16:43 ` Filipe Manana
2025-07-29 5:48 ` Johannes Thumshirn
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=cover.1753469762.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--cc=linux-btrfs@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