Re: V4L2 to-do list, No.2

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



> Looking at your patch, I see no reason not to add it. If nobody wants to
> use it, then fine. But if someone is creating a application/driver pair
> and has a compelling reason to use it, then there is a standardized way.

read() is surely the standard way 

> I just wonder if there is a system vulerability created by it. If a
> malicious or broken app frees buffers while the driver is still hodling
> them.

kiobufs handle the locking and refcounting, so providing the driver handles
its on pci posting/freeing order correctly all will be fine





[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux