Re: Oops with spin_lock() in an IRQF_NO_THREAD interrupt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Matthias Klein | 2013-10-02 14:54:00 [+0000]:

>Hello,
Hi,

>i am writing a kernel module on a rt kernel where I have an
>IRQF_NO_THREAD interrupt.
I hope you know what you are doing with this.

>For sharing a "write index" between that interrupt and the process
>context (ioctl() etc.) I use a spin_lock for locking.
>
>In the IRQ I use spin_lock() & spin_unlock(), and in the process
>context I use spin_lock_irq() & spin_unlock_irq().
>
>Basically the driver and the test application are working, but after
>some time I get an oops message.
>
>Do I use the right functions for locking ? Do you have a tip why I
>get that oops message ?

You should use a the raw_spinlock here if you _really_ need
IRQF_NO_THREAD.

>Best regards,
>
>Matthias

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux