In vfp_save_state(), don't bother trying to save the VFP registers if the

provided PCB doesn't have a pcb_fpusaved. All PCBs associated to a thread
should have one, but the dumppcb used when panic'ing doesn't.

1 files changed, 9 insertions, 0 deletions

diff --git a/sys/arm64/arm64/vfp.c b/sys/arm64/arm64/vfp.c
index 2b810eeb6339..b11e799fcdb6 100644
--- a/sys/arm64/arm64/vfp.c
+++ b/sys/arm64/arm64/vfp.c
@@ -170,6 +170,15 @@ vfp_save_state(struct thread *td, struct pcb *pcb)
 	KASSERT(pcb != NULL, ("NULL vfp pcb"));
 	KASSERT(td == NULL || td->td_pcb == pcb, ("Invalid vfp pcb"));
 
+	/* 
+	 * savectx() will be called on panic with dumppcb as an argument,
+	 * dumppcb doesn't have pcb_fpusaved set so don't make any attempt
+	 * to store the VFP registers in it, we probably don't care much
+	 * at that point, anyway.
+	 */
+	if (pcb->pcb_fpusaved == NULL)
+		return;
+
 	if (td == NULL)
 		td = curthread;