From: Markus Elfring <Markus.Elfring@web.de>
To: Aditya Pakki <pakki001@umn.edu>, linux-btrfs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Chris Mason <clm@fb.com>,
David Sterba <dsterba@suse.com>,
Josef Bacik <josef@toxicpanda.com>, Kangjie Lu <kjlu@umn.edu>
Subject: Re: [PATCH] btrfs: Fix incorrect check
Date: Sun, 15 Dec 2019 20:56:07 +0100 [thread overview]
Message-ID: <944244bb-92c5-2c71-84de-ec5e402ecd24@web.de> (raw)
In-Reply-To: <20191215173226.29149-1-pakki001@umn.edu>
> The patch fixes this issue by returning an error if state is NULL
> and then assigns fs_info.
Please improve the change message (besides avoiding a typo in the subject).
Would you like to add the tag “Fixes”?
Regards,
Markus
next prev parent reply other threads:[~2019-12-15 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 17:32 [PATCH] btrfs: Fix incorrect check causing NULL pointer derefernce Aditya Pakki
2019-12-15 19:56 ` Markus Elfring [this message]
2019-12-16 16:16 ` 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=944244bb-92c5-2c71-84de-ec5e402ecd24@web.de \
--to=markus.elfring@web.de \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kjlu@umn.edu \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pakki001@umn.edu \
/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