From: Leo Martins <loemra.dev@gmail.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH v4 0/2] btrfs: iget_path cleanup
Date: Fri, 30 Aug 2024 13:24:53 -0700 [thread overview]
Message-ID: <cover.1724970046.git.loemra.dev@gmail.com> (raw)
Updates from v3:
Previously I allocated a path in btrfs_iget and called btrfs_iget_path
with it. However, Josef pointed out that there is a case in
btrfs_iget_path where the inode was found in cache and no path
allocation was necessary. In this patch series I no longer call
btrfs_iget_path from btrfs_iget, instead I duplicated the code from
btrfs_iget_path with a path allocation.
This patch series is a cleanup of btrfs_iget_path and btrfs_iget. It
moves some cleanup and error handling from btrfs_iget_path into
read_locked_inode. In addition it also removes a conditional path
allocation that occurs in read_locked_inode, instead reworking
btrfs_iget to allocate and free the path.
Leo Martins (2):
btrfs: push btrfs_iget_path cleanup into btrfs_read_locked_inode
btrfs:
fs/btrfs/inode.c | 143 +++++++++++++++++++++++++++--------------------
1 file changed, 81 insertions(+), 62 deletions(-)
--
2.43.5
next reply other threads:[~2024-08-30 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 20:24 Leo Martins [this message]
2024-08-30 20:24 ` [PATCH v4 1/2] btrfs: push cleanup into read_locked_inode Leo Martins
2024-08-30 20:24 ` [PATCH v4 2/2] btrfs: remove conditional path allocation Leo Martins
2024-10-29 23:53 ` [PATCH v4 0/2] btrfs: iget_path cleanup David Sterba
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.1724970046.git.loemra.dev@gmail.com \
--to=loemra.dev@gmail.com \
--cc=kernel-team@fb.com \
--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 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.