From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: sysfs: fix NULL pointer dereference at btrfs_sysfs_del_qgroups()
Date: Mon, 3 Aug 2020 10:09:02 +0300 [thread overview]
Message-ID: <91008ccd-943f-d6ce-16c2-3cc201c9aa48@suse.com> (raw)
In-Reply-To: <20200803062011.17291-1-wqu@suse.com>
On 3.08.20 г. 9:20 ч., Qu Wenruo wrote:
> [BUG]
> With next-20200731 tag (079ad2fb4bf9eba8a0aaab014b49705cd7f07c66),
> unmounting a btrfs with quota disabled will cause the following NULL
> pointer dereference:
>
> BTRFS info (device dm-5): has skinny extents
> BUG: kernel NULL pointer dereference, address: 0000000000000018
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> CPU: 7 PID: 637 Comm: umount Not tainted 5.8.0-rc7-next-20200731-custom #76
> RIP: 0010:kobject_del+0x6/0x20
> Call Trace:
> btrfs_sysfs_del_qgroups+0xac/0xf0 [btrfs]
> btrfs_free_qgroup_config+0x63/0x70 [btrfs]
> close_ctree+0x1f5/0x323 [btrfs]
> btrfs_put_super+0x15/0x17 [btrfs]
> generic_shutdown_super+0x72/0x110
> kill_anon_super+0x18/0x30
> btrfs_kill_super+0x17/0x30 [btrfs]
> deactivate_locked_super+0x3b/0xa0
> deactivate_super+0x40/0x50
> cleanup_mnt+0x135/0x190
> __cleanup_mnt+0x12/0x20
> task_work_run+0x64/0xb0
> exit_to_user_mode_prepare+0x18a/0x190
> syscall_exit_to_user_mode+0x4f/0x270
> do_syscall_64+0x45/0x50
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
> ---[ end trace 37b7adca5c1d5c5d ]---
>
> [CAUSE]
> Commit 079ad2fb4bf9 ("kobject: Avoid premature parent object freeing in
> kobject_cleanup()") changed kobject_del() that it no longer accepts NULL
> pointer.
>
> Before that commit, kobject_del() and kobject_put() all accept NULL
> pointers and just ignore such NULL pointers.
>
> But that mentioned commit needs to access the parent node, killing the
> old NULL pointer behavior.
>
> Unfortunately btrfs is relying on that hidden feature thus we will
> trigger such NULL pointer dereference.
>
> [FIX]
> Instead of just saving several lines, do proper fs_info->qgroups_kobj
> check before calling kobject_del() and kobject_put().
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> fs/btrfs/sysfs.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/sysfs.c b/fs/btrfs/sysfs.c
> index 104c80caaa74..c8df2edafd85 100644
> --- a/fs/btrfs/sysfs.c
> +++ b/fs/btrfs/sysfs.c
> @@ -1565,9 +1565,11 @@ void btrfs_sysfs_del_qgroups(struct btrfs_fs_info *fs_info)
> rbtree_postorder_for_each_entry_safe(qgroup, next,
> &fs_info->qgroup_tree, node)
> btrfs_sysfs_del_one_qgroup(fs_info, qgroup);
> - kobject_del(fs_info->qgroups_kobj);
> - kobject_put(fs_info->qgroups_kobj);
> - fs_info->qgroups_kobj = NULL;
> + if (fs_info->qgroups_kobj) {
> + kobject_del(fs_info->qgroups_kobj);
> + kobject_put(fs_info->qgroups_kobj);
> + fs_info->qgroups_kobj = NULL;
> + }
> }
>
> /* Called when qgroups get initialized, thus there is no need for locking */
>
next prev parent reply other threads:[~2020-08-03 7:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 6:20 [PATCH] btrfs: sysfs: fix NULL pointer dereference at btrfs_sysfs_del_qgroups() Qu Wenruo
2020-08-03 7:09 ` Nikolay Borisov [this message]
2020-08-10 17:02 ` David Sterba
2020-08-11 2:06 ` Qu Wenruo
2020-08-11 6:46 ` 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=91008ccd-943f-d6ce-16c2-3cc201c9aa48@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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