At 10/20/2016 05:20 PM, David Sterba wrote:
On Thu, Oct 20, 2016 at 09:05:34AM +0800, Qu Wenruo wrote:
At 10/19/2016 10:31 PM, David Sterba wrote:
On Fri, Sep 30, 2016 at 09:15:36AM +0800, Qu Wenruo wrote:
While the reason why qgroup reserved space may underflow is still under
On Thu, Oct 20, 2016 at 09:05:34AM +0800, Qu Wenruo wrote:
>
>
> At 10/19/2016 10:31 PM, David Sterba wrote:
> > On Fri, Sep 30, 2016 at 09:15:36AM +0800, Qu Wenruo wrote:
> >> While the reason why qgroup reserved space may underflow is still under
> >> investigation, such WARN_ON will help us
At 10/19/2016 10:31 PM, David Sterba wrote:
On Fri, Sep 30, 2016 at 09:15:36AM +0800, Qu Wenruo wrote:
While the reason why qgroup reserved space may underflow is still under
investigation, such WARN_ON will help us to expose the bug more easily,
and for end-user we can detect and avoid
On Fri, Sep 30, 2016 at 09:15:36AM +0800, Qu Wenruo wrote:
> While the reason why qgroup reserved space may underflow is still under
> investigation, such WARN_ON will help us to expose the bug more easily,
> and for end-user we can detect and avoid underflow.
>
> Signed-off-by: Qu Wenruo
On 09/29/2016 08:15 PM, Qu Wenruo wrote:
> While the reason why qgroup reserved space may underflow is still under
> investigation, such WARN_ON will help us to expose the bug more easily,
> and for end-user we can detect and avoid underflow.
>
> Signed-off-by: Qu Wenruo
While the reason why qgroup reserved space may underflow is still under
investigation, such WARN_ON will help us to expose the bug more easily,
and for end-user we can detect and avoid underflow.
Signed-off-by: Qu Wenruo
---
fs/btrfs/qgroup.c | 21 -