This absolutely makes sense in userspace. The most important part of a spinlock in an OS is that you can yield to the scheduler instead of taking up CPU time on the core. But that defeats the purpose of using a spinlock when in userspace because you still have to syscall
A spinlock in the kernel typically only spins. You use it for the cases when you can't schedule... So it better will be for a short time only.
But the concept of short time does not even exist deterministically in userspace, usually, because it can always be preempted. So don't use pure spinlocks in userspace, unless you reallyreally know what you are doing (and that includes knowing how your kernel works in great details, in the context of how you use it).
