From: Sun YangKai <sunk67188@gmail.com>
To: dsterba@suse.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/7] More btrfs_path auto cleaning
Date: Sat, 05 Apr 2025 12:13:58 +0800 [thread overview]
Message-ID: <6162303.lOV4Wx5bFT@saltykitkat> (raw)
In-Reply-To: <cover.1743549291.git.dsterba@suse.com>
I'm new in lore, not having many experience in kernel development. I'm
currently learning by read the code and patches. I'm just wondering why we
cannot just make these `btrfs_path` become local variables so they can get
freed automatically? Is it because the size of `btrfs_path` is too large to
put them on stack?
Sorry for bothering here. I'm glad to move to else where if it is not prorate
to discuss here.
next prev parent reply other threads:[~2025-04-05 4:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 23:18 [PATCH 0/7] More btrfs_path auto cleaning David Sterba
2025-04-01 23:18 ` [PATCH 1/7] btrfs: do more trivial BTRFS_PATH_AUTO_FREE conversions David Sterba
2025-04-02 0:39 ` David Disseldorp
2025-04-02 22:02 ` David Sterba
2025-04-02 23:14 ` David Disseldorp
2025-04-02 23:45 ` David Sterba
2025-04-01 23:18 ` [PATCH 2/7] btrfs: use BTRFS_PATH_AUTO_FREE in may_destroy_subvol() David Sterba
2025-04-01 23:18 ` [PATCH 3/7] btrfs: use BTRFS_PATH_AUTO_FREE in btrfs_set_inode_index_count() David Sterba
2025-04-01 23:18 ` [PATCH 4/7] btrfs: use BTRFS_PATH_AUTO_FREE in can_nocow_extent() David Sterba
2025-04-01 23:18 ` [PATCH 5/7] btrfs: use BTRFS_PATH_AUTO_FREE in btrfs_encoded_read_inline() David Sterba
2025-04-01 23:18 ` [PATCH 6/7] btrfs: use BTRFS_PATH_AUTO_FREE in btrfs_del_inode_extref() David Sterba
2025-04-01 23:18 ` [PATCH 7/7] btrfs: use BTRFS_PATH_AUTO_FREE in btrfs_insert_inode_extref() David Sterba
2025-04-03 8:01 ` [PATCH 0/7] More btrfs_path auto cleaning Daniel Vacek
2025-04-05 4:13 ` Sun YangKai [this message]
2025-04-06 22:17 ` David Sterba
2025-04-07 22:10 ` Sun YangKai
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=6162303.lOV4Wx5bFT@saltykitkat \
--to=sunk67188@gmail.com \
--cc=dsterba@suse.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