Peter Eriksson b339ab1491 ciss: Don't panic on null CR ciss_dequeue_notify ... Apparently, sometimes on hot plug/unplug, a null cr comes back from ciss_dequeue_notify. This is clearly a bug, and by ignoring it we're papering over that bug. We only ever wake the thread after enqueing a notification or setting a bit about killing the thread, so once we check the bit isn't the cause, cr can't be NULL unless something else has dequeued it. Ideally, this would be fixed, rather than papered over, but this makes a very old card somewhat more useable for external enclosures. I suspect it's a race when we set CISS_THREAD_SHUT and another flag (the latter w/o ciss_mtx held), but I don't see it and w/o hardware to reproduce it would be hard to know for sure. PR: 246279 Reviewed by: imp Tested by: Marek Zarychta Differential Revision: https://reviews.freebsd.org/D25155		2024-10-13 23:37:46 -06:00
..
ciss.c	ciss: Don't panic on null CR ciss_dequeue_notify	2024-10-13 23:37:46 -06:00
cissio.h	sys: Remove $FreeBSD$: two-line .h pattern	2023-08-16 11:54:11 -06:00
cissreg.h	ciss(4): Fix a typo in a source code comment	2024-01-20 17:34:25 +01:00
cissvar.h	ciss: Add max physical target	2024-10-13 23:24:15 -06:00