U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Cole Munz <Munzzyy1@proton.me>, u-boot@lists.denx.de
Cc: Alexey Charkov <alchark@flipper.net>,
	Marek Behun <kabel@kernel.org>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v3 0/3] fs: btrfs: report file sizes from readdir
Date: Mon, 3 Aug 2026 07:38:16 +0930	[thread overview]
Message-ID: <601345a8-0b4f-44e6-a25c-e827ca79ccff@gmx.com> (raw)
In-Reply-To: <cover.1785660029.git.Munzzyy1@proton.me>



在 2026/8/2 19:05, Cole Munz 写道:
> As agreed on the v1 thread, the fix and the cleanups are now separate
> patches:
> 
> - patch 1 is the fix in the v1 shape
> - patch 2 makes btrfs_search_slot() release the path on error like
>    the kernel version does. That is where the btrfs_size() leak came
>    from. Suggested by Qu.
> - patch 3 is the dedup Alexey asked about. One helper shared by
>    btrfs_readdir() and btrfs_size().
> 
> The pending btrfs test suite still passes on top of the readdir
> series: 5 passed.
> 
> Changes in v3: split the fix from the cleanups. The release moved
> into btrfs_search_slot() itself.
> Changes in v2: helper shared with btrfs_size() plus the leak fix in
> one patch.
> 

Reviewed-by: Qu Wenruo <wqu@suse.com>

Thanks,
Qu

> Cole Munz (3):
>    fs: btrfs: report file sizes from readdir
>    fs: btrfs: release the path when btrfs_search_slot() fails
>    fs: btrfs: deduplicate the inode size lookup
> 
>   fs/btrfs/btrfs.c    | 77 +++++++++++++++++++++++++++++++--------------
>   fs/btrfs/ctree.c    | 16 +++++++---
>   fs/btrfs/ctree.h    |  3 +-
>   fs/btrfs/dir-item.c |  7 ++++-
>   4 files changed, 74 insertions(+), 29 deletions(-)
> 


  parent reply	other threads:[~2026-08-02 22:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02  5:42 [PATCH] fs: btrfs: report file sizes from readdir Cole Munz
2026-08-02  6:02 ` Alexey Charkov
2026-08-02  6:44   ` [PATCH v2] " Cole Munz
2026-08-02  6:47   ` [PATCH] " Qu Wenruo
2026-08-02  7:37     ` Cole Munz
2026-08-02  7:55       ` Qu Wenruo
2026-08-02  9:35         ` [PATCH v3 0/3] " Cole Munz
2026-08-02  9:35           ` [PATCH v3 1/3] " Cole Munz
2026-08-02  9:35           ` [PATCH v3 2/3] fs: btrfs: release the path when btrfs_search_slot() fails Cole Munz
2026-08-02  9:35           ` [PATCH v3 3/3] fs: btrfs: deduplicate the inode size lookup Cole Munz
2026-08-02 22:08           ` Qu Wenruo [this message]
2026-08-10 20:53           ` [PATCH v3 0/3] fs: btrfs: report file sizes from readdir Tom Rini

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=601345a8-0b4f-44e6-a25c-e827ca79ccff@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=Munzzyy1@proton.me \
    --cc=alchark@flipper.net \
    --cc=kabel@kernel.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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