66c183f43f
If MMC_SIM_CAM_REQUEST() is successful the ccb could be running or being completed as the method returns. Modifying the ccb status could override whatever status was already set by a MMC driver. I am not sure what was the purpose of setting the status to CAM_REQ_INVALID in the success path. I assume that it was to catch a possibility that the ccb could be completed without its status explicitly set. So, I am keeping the code, it's just moved to before the MMC_SIM_CAM_REQUEST call. Without this change I was getting random and phantom EIO errors on Rock64 running off an SD card (dwmmc driver) plus occasional panics like: Memory modified after free 0xffffa00003985800(2040) val=6 @ 0xffffa00003985854 panic: Most recently used by CAM CCB MFC after: 1 week |
||
|---|---|---|
| .. | ||
| mmc_all.h | ||
| mmc_bus.h | ||
| mmc_da.c | ||
| mmc_sim_if.m | ||
| mmc_sim.c | ||
| mmc_sim.h | ||
| mmc_xpt.c | ||
| mmc.h | ||