Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1517822 - Big quota values overflow when reading them from kernel
Summary: Big quota values overflow when reading them from kernel
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: quota
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Petr Pisar
QA Contact: Robin Hack
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-27 14:36 UTC by Petr Pisar
Modified: 2018-04-10 08:43 UTC (History)
7 users (show)

Fixed In Version: quota-4.01-17.el7
Doc Type: No Doc Update
Doc Text:
Clone Of: 1009397
Last Closed: 2018-04-10 08:42:52 UTC
Target Upstream Version:

Attachments (Terms of Use)
1st upstream patch (deleted)
2017-11-27 15:23 UTC, Petr Pisar
no flags Details | Diff
2nd upstream fix (deleted)
2017-11-27 15:23 UTC, Petr Pisar
no flags Details | Diff

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0667 None None None 2018-04-10 08:43:09 UTC

Description Petr Pisar 2017-11-27 14:36:17 UTC
+++ This bug was initially created as a clone of Bug #1009397 +++
--- Additional comment from Petr Pisar on 2013-09-18 10:47:15 GMT ---

The rpc.rquotad is addressed in bug #1007785.

This bug report is about quota tools accepting big values from kernel which then overflow due to internal representation in quota tools.


$ quota -vs
Disk quotas for user test (uid 500): 
     Filesystem  blocks   quota   limit   grace   files   quota   limit   grace
     /dev/loop0 18446744073709551612       0       0               0       0       0        
                  4096G       0       0               0       0       0        

Here you can see /dev/loop0 block usage was not abbreviated and that the same field reported over RPC (localhost:/quota) mismatches. This is due to the overflow to negative values and comparison against 0 and printing as unsigned value. This is still problem in the upstream version.

--- Additional comment from Petr Pisar on 2014-10-21 13:00:30 GMT ---

Upstream concluded kernel uses signed values internally, so user space should too. (Because used size can go into negative values on not synchronized cluster nodes. So the unsigned kernel interface is a mistake and user space should interpret the values as signed.)

Upstream fixed this issue by changing quota tools printing int input layer to consider the values as signed with these two commits:

commit 0214512479e04a3e118cbef8703aa1aec5240f3f
Author: Jan Kara <>
Date:   Thu May 1 18:08:09 2014 +0200

    Properly handle signed space and inode values
    For cluster filesystems, kernel can sometimes return negative values of
    used space or inodes (because counters are not completely synchronized
    across the cluster). Make quota tools properly print these.
    Signed-off-by: Jan Kara <>

commit 663ac451b045b4823d6d633893a5d748c09f42f2
Author: Jan Kara <>
Date:   Wed Oct 1 18:10:40 2014 +0200

    Fix handling of space and inode values
    Commit 0214512479e0 (Properly handle signed space and inode values)
    broke parsing of pure numbers in str2number() so that it would always
    complain about "Integer overflow while interpreting decimal unit". Fix
    condition checking for overflow.
    Also number2str() was buggy and wouldn't guess proper units for negative
    Signed-off-by: Jan Kara <>

--- Additional comment from Petr Pisar on 2015-01-06 13:21:54 GMT ---

How to test:
(1) Mount GFS2 file system with negative quota usage values. (You can use attachment #799336 [details] "GFS2 image with big block usage value for UID 500" from
bug #1007785.)
(2) List quotas for UID 500 by repoqota tool.
Before: Block usage is 18446744073709551612.
After: Block usage is -4.


RHEL-7 (quota-4.01-16.el7) is affected too.

Comment 2 Petr Pisar 2017-11-27 15:23:07 UTC
Created attachment 1359514 [details]
1st upstream patch

Comment 3 Petr Pisar 2017-11-27 15:23:46 UTC
Created attachment 1359518 [details]
2nd upstream fix

Comment 11 errata-xmlrpc 2018-04-10 08:42:52 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

Note You need to log in before you can comment on or make changes to this bug.