[Dri-devel] Re: Recent broken locking in DRM code..

2002-12-02 Thread Michel Dänzer
On Mon, 2002-12-02 at 03:00, Linus Torvalds wrote: On 1 Dec 2002, Michel Dänzer wrote: Does that also apply to kmalloc()/kfree(), or are they safe? kfree() (or free_pages() or others of that type) is always safe. kmalloc(x, GFP_ATOMIC) works, but has problems (ie being over-eager about

[Dri-devel] Re: Recent broken locking in DRM code..

2002-12-01 Thread Michel Dänzer
On Son, 2002-12-01 at 20:40, Linus Torvalds wrote: I'm following the DRM kernel changes, and over the last few days code appeared that I really don't think should be in the kernel, and that I really don't want to merge. The problem appears to be that the DRM people are used to using

[Dri-devel] Re: Recent broken locking in DRM code..

2002-12-01 Thread Linus Torvalds
On 1 Dec 2002, Michel Dänzer wrote: Actually, I did that because I thought send_sig_info() or kfree() might not be interrupt safe. Signals are commonly sent from interrupts: kill_fasync() is quite commonly supported by many device drivers, and the resulting SIGIO is almost universally sent