From: Sebastian <sebastian.scherbel@fau.de>
To: clm@fb.com
Cc: josef@toxicpanda.com, dsterba@suse.com,
linux-btrfs@vger.kernel.org, linux-kernel@i4.cs.fau.de,
Sebastian Scherbel <sebastian.scherbel@fau.de>
Subject: [PATCH 0/2] btrfs: Move dereference behind null checks
Date: Sat, 7 Dec 2019 23:18:16 +0100 [thread overview]
Message-ID: <20191207221818.3641-1-sebastian.scherbel@fau.de> (raw)
From: Sebastian Scherbel <sebastian.scherbel@fau.de>
Regarding Bug 205003, points 1 and 2
This patch series moves two dereferences after the null check to avoid
a possible null pointer dereference.
Sebastian Scherbel (2):
btrfs: Move dereference behind null check in check integrity
btrfs: Move dereference behind null check in check volumes
fs/btrfs/check-integrity.c | 4 +++-
fs/btrfs/volumes.c | 4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
--
2.20.1
next reply other threads:[~2019-12-07 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 22:18 Sebastian [this message]
2019-12-07 22:18 ` [PATCH 1/2] btrfs: Move dereference behind null check in check integrity Sebastian
2019-12-07 22:18 ` [PATCH 2/2] btrfs: Move dereference behind null check in check volumes Sebastian
2019-12-09 9:30 ` [PATCH 0/2] btrfs: Move dereference behind null checks Johannes Thumshirn
2019-12-09 16:11 ` 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=20191207221818.3641-1-sebastian.scherbel@fau.de \
--to=sebastian.scherbel@fau.de \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@i4.cs.fau.de \
/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).