Fix to bit shift errors

[ayushr2]

As corrected in this PR, at many instances in the code a 32-bit or 16-bit number was being left shifted by 32. The numeric values were too small for that to be a valid shift.

I have just moved the shifts outside of the uint64 cast which should fix this issue.

[coveralls]

Pull Request Test Coverage Report for Build 17

• 4 of 5 (80.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 61.03%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
block_group_descriptor.go	1	2	50.0%

Totals
Change from base Build 16:	0.0%
Covered Lines:	711
Relevant Lines:	1165

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 17

• 4 of 5 (80.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 61.03%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
block_group_descriptor.go	1	2	50.0%

Totals
Change from base Build 16:	0.0%
Covered Lines:	711
Relevant Lines:	1165

---

💛 - Coveralls

[dsoprea]

Thanks for catching this.

I'd really like one of us to reproduce the issue in a unit-test. Would you be willing to add one, or would you prefer that I do?

[ayushr2]

Thanks for responding! I do not understand ext4 that well yet to unit test this bug.
Please feel free to hop on and add tests if you like. I have added you as a collaborator.

[dsoprea]

Did you actually experience the failures, or merely just observe the bugs while looking at the code? If the former, where in the code did it fail for you?

[ayushr2]

I just observed the bugs. Did not actually get it to cause any failure.

[dsoprea]

Good catch.

…

On Mon, May 27, 2019, 14:19 Ayush Ranjan ***@***.*** wrote: I just observed the bugs. Did not actually get it to cause any failure. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AAFOW2UX6RCRVUBXGWTYMSLPXQQ3TA5CNFSM4HPS2WS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKKC4Y#issuecomment-496279923>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFOW2UYVABNH5COOA7TPC3PXQQ3TANCNFSM4HPS2WSQ> .

[dsoprea]

In lieu of the fact that we don't have a failure case that we can write a test for, I'll just merge it. Thanks.