2103  * For the read side it is ok to hold sd_lock across calling this (and the
2105  * But for the write side strwakeq might be invoked and it acquires sd_lock.
2115 	ASSERT((q->q_flag & QREADR) || MUTEX_NOT_HELD(&STREAM(q)->sd_lock));  in qbackenable()
3562 	mutex_enter(&stp->sd_lock);  in strwakeq()
3573 		mutex_exit(&stp->sd_lock);  in strwakeq()
3575 		mutex_enter(&stp->sd_lock);  in strwakeq()
3587 		mutex_exit(&stp->sd_lock);  in strwakeq()
3589 		mutex_enter(&stp->sd_lock);  in strwakeq()
3603 		mutex_exit(&stp->sd_lock);  in strwakeq()
3605 		mutex_enter(&stp->sd_lock);  in strwakeq()
3610 	mutex_exit(&stp->sd_lock);  in strwakeq()
3638 	 * This has been done to avoid holding the sd_lock which is  in struioget()
3765 	 * Prevent q_next from changing by holding sd_lock until acquiring  in rwnext()
3767 	 * already have sd_lock acquired. In either case sd_lock is always  in rwnext()
3770 	 * The streamhead read-side holding sd_lock when calling rwnext is  in rwnext()
3773 	 * down-call. In this case sd_lock acts as the streamhead perimeter.  in rwnext()
3777 		mutex_enter(&stp->sd_lock);  in rwnext()
3783 			mutex_enter(&stp->sd_lock);  in rwnext()
3792 		mutex_exit(&stp->sd_lock);  in rwnext()
3797 		mutex_exit(&stp->sd_lock);  in rwnext()
3803 	mutex_exit(&stp->sd_lock);  in rwnext()
3952 	 * Prevent q_next from changing by holding sd_lock until  in infonext()
3955 	mutex_enter(&stp->sd_lock);  in infonext()
3963 		mutex_exit(&stp->sd_lock);  in infonext()
3968 	mutex_exit(&stp->sd_lock);  in infonext()
4159 		mutex_enter(&stp->sd_lock);  in create_putlocks()
4161 			mutex_exit(&stp->sd_lock);  in create_putlocks()
4168 			 * sd_lock. if it is not NULL putnext assumes  in create_putlocks()
4174 			mutex_exit(&stp->sd_lock);  in create_putlocks()