From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: [PATCH v3 0/4] btrfs: inode creation cleanups and fixes
Date: Mon, 14 Mar 2022 13:05:15 -0700 [thread overview]
Message-ID: <cover.1647288019.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
This series contains minor updates of the final four patches of my
previous series [1].
Based on misc-next with the previous version of "btrfs: allocate inode
outside of btrfs_new_inode()" removed.
Changes since v2:
- Mentioned reason for removal of btrfs_lookup_dentry() call in
create_subvol() in commit message of patch 1.
- Made btrfs_init_inode_security() also take btrfs_new_inode_args in
patch 2.
Thanks!
1: https://lore.kernel.org/linux-btrfs/cover.1646875648.git.osandov@fb.com/
Omar Sandoval (4):
btrfs: allocate inode outside of btrfs_new_inode()
btrfs: factor out common part of btrfs_{mknod,create,mkdir}()
btrfs: reserve correct number of items for inode creation
btrfs: move common inode creation code into btrfs_create_new_inode()
fs/btrfs/acl.c | 36 +--
fs/btrfs/ctree.h | 37 ++-
fs/btrfs/inode.c | 800 +++++++++++++++++++++++------------------------
fs/btrfs/ioctl.c | 140 +++++----
fs/btrfs/props.c | 40 +--
fs/btrfs/props.h | 4 -
6 files changed, 489 insertions(+), 568 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-14 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 20:05 Omar Sandoval [this message]
2022-03-14 20:05 ` [PATCH v3 1/4] btrfs: allocate inode outside of btrfs_new_inode() Omar Sandoval
2022-03-14 20:05 ` [PATCH v3 2/4] btrfs: factor out common part of btrfs_{mknod,create,mkdir}() Omar Sandoval
2022-03-14 20:05 ` [PATCH v3 3/4] btrfs: reserve correct number of items for inode creation Omar Sandoval
2022-03-14 20:05 ` [PATCH v3 4/4] btrfs: move common inode creation code into btrfs_create_new_inode() Omar Sandoval
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.1647288019.git.osandov@fb.com \
--to=osandov@osandov.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox