You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.Environment
[Board]: APL UP2
root@clr-b1b5101306fd4a3a803cf1050b4893f0~ # swupd info
Installed version: 30440
root@clr-19296a3ecf5b4723adce369a5c1807d2~ # uname -a
Linux clr-19296a3ecf5b4723adce369a5c1807d2 4.19.40-quilt-2e5dc0ac-dirty #1 SMP PREEMPT Mon Jul 22 03:38:56 UTC 2019 x86_64 GNU/Linux
root@clr-19296a3ecf5b4723adce369a5c1807d2~ # acrn-dm -v
DM version is: 1.2-unstable-c1b4121e-dirty (daily tag:acrn-2019w29.4-140000p), build by root@2019-07-22 03:45:04
Tools setup wiki: https://wiki.ith.intel.com/display/OTCCWPQA/syzkaller+enabling+on+ACRN
We used Syzkaller ran with hypercall unit tests to do Fuzzing test for ACRN, which ran on SOS and communicate with DM process by socket.
"enable_syscalls":[ "syz_ic_inject_msi", "syz_ic_vm_intr_monitor", "syz_ic_set_irqline","syz_ic_sos_offline_cpu","syz_ic_set_callback_vector","syz_ic_clear_vm_ioreq" ],
2. Reproduce Steps
setup env with wiki: And sync latest ACRN code and fuzzing tool code to your host
apply patch_for_fuzzing_on_dm.txt to devicemodel, and build images
modify acrn_build.sh based your own environment, and run it to rebuild syzkaller tool
flash images, and then make uos autoboot, remove sos password, crashlogctl enable
use acrn.cfg (modify the ip to your own ip) to run syzkaller cases: ./bin/syz-manager -config=acrn.cfg --debug
Expected result:
Hypervisor not crashed not hang, and SUT works well
Current result:
After run: ./bin/syz-manager -config=acrn.cfg --debug
Hypervisor hang.
The text was updated successfully, but these errors were encountered:
this patch is to fix error debug message
for invalid 'param' case, there is no string
variable for '%s' output, which will potenially
trigger hypervisor crash as it may access random
memroy address and trigger SMAP violation.
Tracked-On: projectacrn#4092
Signed-off-by: Yonghua Huang <yonghua.huang@intel.com>
this patch is to fix error debug message
for invalid 'param' case, there is no string
variable for '%s' output, which will potenially
trigger hypervisor crash as it may access random
memroy address and trigger SMAP violation.
Tracked-On: #4092
Signed-off-by: Yonghua Huang <yonghua.huang@intel.com>
1.Environment
[Board]: APL UP2
root@clr-b1b5101306fd4a3a803cf1050b4893f0~ # swupd info
Installed version: 30440
root@clr-19296a3ecf5b4723adce369a5c1807d2~ # uname -a
Linux clr-19296a3ecf5b4723adce369a5c1807d2 4.19.40-quilt-2e5dc0ac-dirty #1 SMP PREEMPT Mon Jul 22 03:38:56 UTC 2019 x86_64 GNU/Linux
root@clr-19296a3ecf5b4723adce369a5c1807d2~ # acrn-dm -v
DM version is: 1.2-unstable-c1b4121e-dirty (daily tag:acrn-2019w29.4-140000p), build by root@2019-07-22 03:45:04
Tools setup wiki: https://wiki.ith.intel.com/display/OTCCWPQA/syzkaller+enabling+on+ACRN
We used Syzkaller ran with hypercall unit tests to do Fuzzing test for ACRN, which ran on SOS and communicate with DM process by socket.
"enable_syscalls":[ "syz_ic_inject_msi", "syz_ic_vm_intr_monitor", "syz_ic_set_irqline","syz_ic_sos_offline_cpu","syz_ic_set_callback_vector","syz_ic_clear_vm_ioreq" ],
2. Reproduce Steps
setup env with wiki: And sync latest ACRN code and fuzzing tool code to your host
apply patch_for_fuzzing_on_dm.txt to devicemodel, and build images
modify acrn_build.sh based your own environment, and run it to rebuild syzkaller tool
flash images, and then make uos autoboot, remove sos password, crashlogctl enable
use acrn.cfg (modify the ip to your own ip) to run syzkaller cases: ./bin/syz-manager -config=acrn.cfg --debug
Expected result:
Hypervisor not crashed not hang, and SUT works well
Current result:
After run: ./bin/syz-manager -config=acrn.cfg --debug
Hypervisor hang.
The text was updated successfully, but these errors were encountered: