public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Adarsh Das <adarshdas950@gmail.com>, Chris Mason <clm@fb.com>,
	David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs: clean up two FIXMEs related to btrfs_search_slot output handling
Date: Wed, 4 Feb 2026 07:36:48 +1030	[thread overview]
Message-ID: <e2783fa0-b511-442a-baa3-145419af034a@suse.com> (raw)
In-Reply-To: <20260203172357.65383-1-adarshdas950@gmail.com>



在 2026/2/4 03:53, Adarsh Das 写道:
> Both patches fix cases where a search with offset (u64)-1 gets an
> unexpected exact match. The first silently returned success, and the
> second crashed the kernel. Both now both log an error and return -EUCLEAN.

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

Thanks,
Qu

> 
> Adarsh Das (2):
>    btrfs: handle unexpected exact match in btrfs_set_inode_index_count()
>    btrfs: replace BUG() with error handling in __btrfs_balance()
> 
>   fs/btrfs/inode.c   | 15 ++++++++++++---
>   fs/btrfs/volumes.c | 10 ++++++++--
>   2 files changed, 20 insertions(+), 5 deletions(-)
> 


  parent reply	other threads:[~2026-02-03 21:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 17:23 [PATCH 0/2] btrfs: clean up two FIXMEs related to btrfs_search_slot output handling Adarsh Das
2026-02-03 17:23 ` [PATCH 1/2] btrfs: handle unexpected exact match in btrfs_set_inode_index_count() Adarsh Das
2026-02-03 17:23 ` [PATCH 2/2] btrfs: replace BUG() with error handling in __btrfs_balance() Adarsh Das
2026-02-03 21:06 ` Qu Wenruo [this message]
2026-02-04 14:03 ` [PATCH 0/2] btrfs: clean up two FIXMEs related to btrfs_search_slot output handling 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=e2783fa0-b511-442a-baa3-145419af034a@suse.com \
    --to=wqu@suse.com \
    --cc=adarshdas950@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@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