Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: "oe-kbuild@lists.linux.dev" <oe-kbuild@lists.linux.dev>,
	"fdmanana@kernel.org" <fdmanana@kernel.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	"lkp@intel.com" <lkp@intel.com>,
	"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>
Subject: Re: [PATCH] btrfs: use the btrfs_block_group_end() helper everywhere
Date: Mon, 19 Jan 2026 10:27:56 +0300	[thread overview]
Message-ID: <aW3c_HzQw-dfQUeg@stanley.mountain> (raw)
In-Reply-To: <9398ca7c-f114-47f9-ac22-8fd8f67214a7@wdc.com>

On Mon, Jan 19, 2026 at 06:49:34AM +0000, Johannes Thumshirn wrote:
> On 1/19/26 7:40 AM, Dan Carpenter wrote:
> > d4452bc526c431 Chris Mason     2014-05-19  1202  	u64 start, extent_start, extent_end, len;
> > 7fc5a6968403c7 Filipe Manana   2026-01-16 @1203  	const u64 block_group_end = btrfs_block_group_end(block_group);
> >                                                                                                            ^^^^^^^^^^^^
> > Dereferenced.
> >
> > d4452bc526c431 Chris Mason     2014-05-19  1204  	struct extent_io_tree *unpin = NULL;
> > d4452bc526c431 Chris Mason     2014-05-19  1205  	int ret;
> > 43be21462d8c26 Josef Bacik     2011-04-01  1206
> > 5349d6c3ffead2 Miao Xie        2014-06-19 @1207  	if (!block_group)
> >                                                               ^^^^^^^^^^^
> > Too late.
> 
> I _think_ this check is bogus.
> 
> On one hand  write_pinned_extent_entries() gets called by 
> __btrfs_write_out_cache(), which has the following comment at the top:
> 
> /*
>   * Write out cached info to an inode.
>   *
>   * @inode:       freespace inode we are writing out
>   * @ctl:         free space cache we are going to write out
>   * @block_group: block_group for this cache if it belongs to a block_group
> 
> but then __btrfs_write_out_cache() is only called by 
> btrfs_write_out_cache() which looks like this:
> 
>      ret = __btrfs_write_out_cache(inode, ctl, block_group,
>                        &block_group->io_ctl, trans);
> 
> so iff block_group really is NULL, we'd have a NULL pointer dereference 
> when accessing block_group::io_ctl.
> 
> 
> Same for all the if (block_group) constructs in __btrfs_write_out_cache().
> 

The zero day bot can't use cross function analysis because it doesn't
scale to the number of trees which the bot tests...  Otherwise, sure,
Smatch would silence this warning.

If we remove the NULL check here, should we also remove the NULL checking
in __btrfs_write_out_cache()?  Otherwise there is still a potential that
something will complain about inconsistent NULL checking.

regards,
dan carpenter



  reply	other threads:[~2026-01-19  7:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 10:32 [PATCH] btrfs: use the btrfs_block_group_end() helper everywhere fdmanana
2026-01-16 12:02 ` Johannes Thumshirn
2026-01-19  6:39 ` Dan Carpenter
2026-01-19  6:49   ` Johannes Thumshirn
2026-01-19  7:27     ` Dan Carpenter [this message]
2026-01-19  7:29       ` Dan Carpenter

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=aW3c_HzQw-dfQUeg@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=oe-kbuild@lists.linux.dev \
    /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