Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Marcos Paulo de Souza <marcos.souza.org@gmail.com>
To:     linux-kernel@vger.kernel.org
Cc:     dsterba@suse.com, linux-btrfs@vger.kernel.org,
        anand.jain@oracle.com, Marcos Paulo de Souza <mpdesouza@suse.com>
Subject: [PATCH 0/2] btrfs qgroup cleanup
Date:   Mon, 25 Nov 2019 21:58:49 -0300
Message-Id: <20191126005851.11813-1-marcos.souza.org@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Marcos Paulo de Souza <mpdesouza@suse.com>

While reading the qgroup code and doing some tests, I found some two things
that I would like to change:
* Remove some useless code that was being set only to check if
  fs_info->quota_root was not NULL
* Check why creating a qgroup was returning EINVAL

The answer to the second point was: EINVAL is returned when a user tries to
create/delete/list/assign a qgroup to a subvolume, but this subvolume does
not have quota enabled. Talking with David, he suggested to change it to
ENOTCONN, following what is currently being used in balance and scrub.

So here are the changes. Please take a look!

Marcos Paulo de Souza (2):
  btrfs: qgroup: Cleanup quota_root checks
  btrfs: qgroup: Return -ENOTCONN instead of -EINVAL

 fs/btrfs/qgroup.c | 44 +++++++++++++++-----------------------------
 1 file changed, 15 insertions(+), 29 deletions(-)

-- 
2.23.0