[NaCl SDK] kernel_wrap_tests: Setup munmap mocks before calling ki_init

[NaCl SDK] kernel_wrap_tests: Setup munmap mocks before calling ki_init

If munmap is called during ki_init() in a kernel_wrap_test, it will print a
message saying the call was unexpected. This will cause a deadlock since it is
trying to print a message inside the memory allocator.

BUG=378596
R=sbc@chromium.org
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_nacl_sdk;tryserver.chromium.mac:mac_nacl_sdk;tryserver.chromium.win:win_nacl_sdk

Committed: https://crrev.com/65d5a9e415f3f7357677ee40864d3c3d61ba5f6c
Cr-Commit-Position: refs/heads/master@{#374745}

[binji, 2016-02-10 19:56:34]

Description was changed from

==========
[NaCl SDK] kernel_wrap_tests: Setup munmap mocks before calling ki_init

If munmap is called during ki_init() in a kernel_wrap_test, it will print a
message saying the call was unexpected. This will cause a deadlock since it is
trying to print a message inside the memory allocator.

BUG=378596
R=sbc@chromium.org
==========

to

==========
[NaCl SDK] kernel_wrap_tests: Setup munmap mocks before calling ki_init

If munmap is called during ki_init() in a kernel_wrap_test, it will print a
message saying the call was unexpected. This will cause a deadlock since it is
trying to print a message inside the memory allocator.

BUG=378596
R=sbc@chromium.org
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_nacl_sdk;tryserver.chromium.mac:mac_nacl_sdk;tryserver.chromium.win:win_nacl_sdk
==========

[Sam Clegg, 2016-02-10 20:15:04]

Maybe re-enable the test that was disabled pending the fix of 378596?

otherwise lgtm

[binji, 2016-02-10 20:32:49]

On 2016/02/10 20:15:04, Sam Clegg wrote:
> Maybe re-enable the test that was disabled pending the fix of 378596?

I was going to, but thought it might be nicer to land this first, just in case
the test is still flaky for some other reason.

> 
> otherwise lgtm

[Sam Clegg, 2016-02-10 20:46:40]

lgtm

[Sam Clegg, 2016-02-10 20:46:45]

The CQ bit was checked by sbc@chromium.org

[commit-bot: I haz the power, 2016-02-10 20:48:01]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1681223004/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1681223004/1

[commit-bot: I haz the power, 2016-02-10 22:11:55]

Description was changed from

==========
[NaCl SDK] kernel_wrap_tests: Setup munmap mocks before calling ki_init

If munmap is called during ki_init() in a kernel_wrap_test, it will print a
message saying the call was unexpected. This will cause a deadlock since it is
trying to print a message inside the memory allocator.

BUG=378596
R=sbc@chromium.org
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_nacl_sdk;tryserver.chromium.mac:mac_nacl_sdk;tryserver.chromium.win:win_nacl_sdk
==========

to

==========
[NaCl SDK] kernel_wrap_tests: Setup munmap mocks before calling ki_init

If munmap is called during ki_init() in a kernel_wrap_test, it will print a
message saying the call was unexpected. This will cause a deadlock since it is
trying to print a message inside the memory allocator.

BUG=378596
R=sbc@chromium.org
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_nacl_sdk;tryserver.chromium.mac:mac_nacl_sdk;tryserver.chromium.win:win_nacl_sdk
==========

[commit-bot: I haz the power, 2016-02-10 22:11:55]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-16 22:31:37]

Description was changed from

==========
[NaCl SDK] kernel_wrap_tests: Setup munmap mocks before calling ki_init

If munmap is called during ki_init() in a kernel_wrap_test, it will print a
message saying the call was unexpected. This will cause a deadlock since it is
trying to print a message inside the memory allocator.

BUG=378596
R=sbc@chromium.org
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_nacl_sdk;tryserver.chromium.mac:mac_nacl_sdk;tryserver.chromium.win:win_nacl_sdk
==========

to

==========
[NaCl SDK] kernel_wrap_tests: Setup munmap mocks before calling ki_init

If munmap is called during ki_init() in a kernel_wrap_test, it will print a
message saying the call was unexpected. This will cause a deadlock since it is
trying to print a message inside the memory allocator.

BUG=378596
R=sbc@chromium.org
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_nacl_sdk;tryserver.chromium.mac:mac_nacl_sdk;tryserver.chromium.win:win_nacl_sdk

Committed: https://crrev.com/65d5a9e415f3f7357677ee40864d3c3d61ba5f6c
Cr-Commit-Position: refs/heads/master@{#374745}
==========

[commit-bot: I haz the power, 2016-02-16 22:31:38]

Patchset 1 (id:??) landed as
https://crrev.com/65d5a9e415f3f7357677ee40864d3c3d61ba5f6c
Cr-Commit-Position: refs/heads/master@{#374745}