lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 10 Oct 2021 00:20:11 +0000
Subject: [Bug 214665] security bug:using "truncate" bypass disk quotas limit

Theodore Tso ( changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |
         Resolution|---                         |INVALID

--- Comment #1 from Theodore Tso ( ---
This is not a bug, but rather things working as expected.   This is because
truncate does not actually allocate any disk blocks.   It merely sets the
i_size of the inode to be the specified quantity.   If i_size is less than
where blocks currently are allocated and assigned to the inode at those logical
offsets, then those blocks will be deallocated.   But truncate never allocates
any additional data blocks.

Try running "du id", and see how much disk space the file takes.  Or try using
"ls -s", which will show the disk space used by the file --- which is different
from the size of the file.   If this puzzles you, look up the definition of
"sparse file".

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

Powered by blists - more mailing lists