mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Colin Ian King <colin.king@canonical.com>
To: Qu Wenruo <wqu@suse.com>, David Sterba <dsterba@suse.com>,
	Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	linux-btrfs@vger.kernel.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: re: btrfs: qgroup: Try our best to delete qgroup relations (bug report)
Date: Tue, 6 Aug 2019 14:48:59 +0100	[thread overview]
Message-ID: <ea7f88e7-108e-ad2a-232f-b18715607bf3@canonical.com> (raw)

Hi,

Static analysis with Coverity on linux-next picked up a potential issue
with the following commit:

commit 035087b3c256741be367747eab866505cece31fb
Author: Qu Wenruo <wqu@suse.com>
Date:   Sat Aug 3 14:45:59 2019 +0800

    btrfs: qgroup: Try our best to delete qgroup relations

The static analysis report is as follows:

1334         */

    3. Condition !member, taking true branch.
    4. var_compare_op: Comparing member to null implies that member
might be null.
    5. Condition !parent, taking false branch.

1335        if (!member && !parent)
1336                goto delete_item;
1337
1338        /* check if such qgroup relation exist firstly */


CID 85026 (#1 of 1): Dereference after null check (FORWARD_NULL)

6. var_deref_op: Dereferencing null pointer member.

1339        list_for_each_entry(list, &member->groups, next_group) {
1340                if (list->group == parent) {
1341                        found = true;
1342                        break;
1343                }
1344        }

An example of the issue that if member is NULL and parent is not null
then  the list_for_each_entry loop with dereference the NULL member
pointer.  The changed logic in the patch on line 1335 is the root cause
of this regression.  I believe it should still be:

	if (!member && !parent)
		goto delete_item;

Colin

             reply	other threads:[~2019-08-06 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 13:48 Colin Ian King [this message]
2019-08-06 13:49 ` Colin Ian King
2019-08-06 13:55   ` Qu Wenruo

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=ea7f88e7-108e-ad2a-232f-b18715607bf3@canonical.com \
    --to=colin.king@canonical.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 \
    --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

all inboxes | Powered by JetHome®