public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/5] btrfs: add helper to get fs_info from struct inode pointer
Date: Wed, 31 Jan 2024 08:23:08 +0100	[thread overview]
Message-ID: <20240131072308.GJ31555@twin.jikos.cz> (raw)
In-Reply-To: <edd12dabd0ce57ba84a4c2b82c51becd64fd7a6f.1706553080.git.dsterba@suse.com>

On Mon, Jan 29, 2024 at 07:33:18PM +0100, David Sterba wrote:
> @@ -5211,7 +5211,7 @@ static struct btrfs_trans_handle *evict_refill_and_join(struct btrfs_root *root,
>  
>  void btrfs_evict_inode(struct inode *inode)
>  {
> -	struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb);
> +	struct btrfs_fs_info *fs_info = inode_to_fs_info(inode);

This leads to a crash in btrfs/232, happened twice:

  BUG: KASAN: null-ptr-deref in btrfs_evict_inode+0xac/0x6b0 [btrfs]
  BUG: kernel NULL pointer dereference, address: 0000000000000208
  Read of size 8 at addr 0000000000000208 by task fsstress/21264
  #PF: supervisor read access in kernel mode
  
  CPU: 3 PID: 21264 Comm: fsstress Not tainted 6.8.0-rc2-default+ #2288
  #PF: error_code(0x0000) - not-present page
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014
  PGD 683f8067 
  Call Trace:
  P4D 683f8067 
   <TASK>
   dump_stack_lvl+0x46/0x70
   kasan_report+0x123/0x150
   ? btrfs_evict_inode+0xac/0x6b0 [btrfs]
   ? btrfs_evict_inode+0xac/0x6b0 [btrfs]
   btrfs_evict_inode+0xac/0x6b0 [btrfs]
   ? local_clock_noinstr+0x11/0xc0
   ? btrfs_rmdir+0x380/0x380 [btrfs]
   ? reacquire_held_locks+0x280/0x280
   ? wake_up_var+0x120/0x120
   evict+0x17f/0x2d0
  
   btrfs_create_common+0xe4/0x1c0 [btrfs]
   ? btrfs_tmpfile+0x2b0/0x2b0 [btrfs]
   ? init_special_inode+0xb9/0xe0
   vfs_mknod+0x25c/0x320
   do_mknodat+0x2fd/0x360
   ? kern_path_create+0x50/0x50
   ? getname_flags+0xb5/0x220
   __x64_sys_mknodat+0x5d/0x70
   do_syscall_64+0x6f/0x140
   entry_SYSCALL_64_after_hwframe+0x46/0x4e

The new macro does BTRFS_I(inode)->root->fs_info while the old one uses
fs_info in the super block. From the context I don't see why a root
pointer would be NULL or how would anyone see that right away and not
introduce such crashes by using the helpers.

  parent reply	other threads:[~2024-01-31  7:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 18:33 [PATCH 0/5] Struct to fs_info helpers David Sterba
2024-01-29 18:33 ` [PATCH 1/5] btrfs: tests: allocate dummy fs_info and root in test_find_delalloc() David Sterba
2024-01-29 18:33 ` [PATCH 2/5] btrfs: add helpers to get inode from page/folio pointers David Sterba
2024-01-30 11:42   ` Johannes Thumshirn
2024-01-30 19:29     ` David Sterba
2024-01-31  9:33       ` Johannes Thumshirn
2024-01-31 17:19         ` David Sterba
2024-01-29 18:33 ` [PATCH 3/5] btrfs: add helpers to get fs_info " David Sterba
2024-01-30 11:58   ` Johannes Thumshirn
2024-01-30 19:32     ` David Sterba
2024-01-29 18:33 ` [PATCH 4/5] btrfs: add helper to get fs_info from struct inode pointer David Sterba
2024-01-30 11:49   ` Johannes Thumshirn
2024-01-30 19:31     ` David Sterba
2024-01-31  7:23   ` David Sterba [this message]
2024-01-31  8:43     ` Qu Wenruo
2024-01-31 18:04       ` David Sterba
2024-01-29 18:33 ` [PATCH 5/5] btrfs: hoist fs_info out of loops in end_bbio_data_write and end_bbio_data_read David Sterba
  -- strict thread matches above, loose matches on Subject: below --
2024-02-01 18:02 [PATCH 0/5 v2] Struct to fs_info helpers David Sterba
2024-02-01 18:02 ` [PATCH 4/5] btrfs: add helper to get fs_info from struct inode pointer David Sterba
2024-02-02 11:34   ` Johannes Thumshirn
2024-02-02 12:07     ` David Sterba
2024-02-02 12:09       ` Johannes Thumshirn

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=20240131072308.GJ31555@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --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