omfs: fix potential integer overflow in allocator
authorBob Copeland <me@bobcopeland.com>
Thu, 28 May 2015 22:44:37 +0000 (15:44 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Fri, 29 May 2015 01:25:19 +0000 (18:25 -0700)
commit5a6b2b36a8249ec9dfb2a714acadad86d9cc0aee
treef3878e295f5eaa25ecee2925481e4c0d9182f5a0
parentc0345ee57d461343586b5e1e2f9c3c3766d07fe6
omfs: fix potential integer overflow in allocator

Both 'i' and 'bits_per_entry' are signed integers but the result is a
u64 block number.  Cast i to u64 to avoid truncation on 32-bit targets.

Found by Coverity (CID 200679).

Signed-off-by: Bob Copeland <me@bobcopeland.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
fs/omfs/bitmap.c