| created | 2022-05-02T21:09:51Z |
|---|---|
| begin | 2022-04-27T00:00:00Z |
| end | 2022-04-28T00:00:00Z |
| path | src/sys |
| commits | 3 |
| date | 2022-04-27T14:23:37Z | |||
|---|---|---|---|---|
| author | dv | |||
| files | src/sys/arch/amd64/amd64/vmm.c | log | diff | annotate |
| message |
vmm(4): dt(4) tracepoints for vm exit reporting previous exit. On Intel/VMX, the tracepoint for vm exits was before extracting the vm exit reason meaning we either reported stack garbage (on first exit) or the prior exit reason. Move the tracepoint to after extraction and refactor the logic to collect all exit info processing in one place. (We were extracting the guest RFLAGS register state before checking the exit info extraction success.) On AMD/SVM, the tracepoint was always triggered even on unsuccessful vm entry leading to garbage data. Tuck the tracepoint into the If block and merge them. ok mlarkin@ |
|||
| date | 2022-04-27T14:52:25Z | |||
|---|---|---|---|---|
| author | claudio | |||
| files | src/sys/kern/vfs_default.c | log | diff | annotate |
| message |
vgone() is vgonel() with curproc as 2nd argument. Use vgonel() like the other call in vop_generic_revoke(). OK semarie@ |
|||
| date | 2022-04-27T18:01:23Z | |||
|---|---|---|---|---|
| author | anton | |||
| files | src/sys/kern/vfs_lockf.c | log | diff | annotate |
| message |
Remove the lock if an identical overlapping one is already present. Preventing a use after free discovered by syzkaller. ok visa@ Reported-by: [email protected] Reported-by: [email protected] Reported-by: [email protected] Reported-by: [email protected] |
|||