diff options
| author | Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | 2014-07-16 15:22:29 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-11-14 08:47:54 -0800 |
| commit | 6f1aec53eded9399e6b44cab8c9aa36c65a8f402 (patch) | |
| tree | 3b9f70938dcc21c9a292d81934d77d979421e0b5 /mm | |
| parent | 918ecf66a11bb3bdc818a264319dcaf984c11a3f (diff) | |
| download | linux-3.10-6f1aec53eded9399e6b44cab8c9aa36c65a8f402.tar.gz linux-3.10-6f1aec53eded9399e6b44cab8c9aa36c65a8f402.tar.bz2 linux-3.10-6f1aec53eded9399e6b44cab8c9aa36c65a8f402.zip | |
UBIFS: fix free log space calculation
commit ba29e721eb2df6df8f33c1f248388bb037a47914 upstream.
Hu (hujianyang <hujianyang@huawei.com>) discovered an issue in the
'empty_log_bytes()' function, which calculates how many bytes are left in the
log:
"
If 'c->lhead_lnum + 1 == c->ltail_lnum' and 'c->lhead_offs == c->leb_size', 'h'
would equalent to 't' and 'empty_log_bytes()' would return 'c->log_bytes'
instead of 0.
"
At this point it is not clear what would be the consequences of this, and
whether this may lead to any problems, but this patch addresses the issue just
in case.
Tested-by: hujianyang <hujianyang@huawei.com>
Reported-by: hujianyang <hujianyang@huawei.com>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions