From: David Sterba <dsterba@suse.cz>
To: Defang Bo <bodefang@126.com>
Cc: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] fs/btrfs: avoid null pointer dereference if reloc control has not been initialized
Date: Mon, 4 Jan 2021 16:11:13 +0100 [thread overview]
Message-ID: <20210104151113.GG6430@twin.jikos.cz> (raw)
In-Reply-To: <1609080931-4048864-1-git-send-email-bodefang@126.com>
On Sun, Dec 27, 2020 at 10:55:31PM +0800, Defang Bo wrote:
> Similar to commmit<389305b2>,
Please use full commit reference like 389305b2aa68 ("btrfs: relocation:
Only remove reloc rb_trees if reloc control has been initialized")
> it turns out that fs_info::reloc_ctl can be NULL ,
Please describe how the NULL can get there.
next prev parent reply other threads:[~2021-01-04 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 14:55 [PATCH 3/3] fs/btrfs: avoid null pointer dereference if reloc control has not been initialized Defang Bo
2021-01-04 15:11 ` David Sterba [this message]
[not found] ` <125f3257.193a.176d084a633.Coremail.bodefang@126.com>
2021-01-05 11:38 ` [PATCH v2] " 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=20210104151113.GG6430@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=bodefang@126.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.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;
as well as URLs for NNTP newsgroup(s).