Re: [PATCH 1/6 v4] V4L: add two new ioctl()s for multi-size videobuffer management

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

 



On Tue, Aug 09, 2011 at 09:26:30AM +0200, Hans Verkuil wrote:
...
> > Wouldn't that be a security issue ? Any application with permissions to access 
> > the video device could DoS the system.
> 
> How is this any different from an application that tries to use more memory
> then there is available? It's an out-of-memory situation, that can happen at
> any time. Anyone can make an application that runs out of memory.
> 
> Out-of-memory is not a security risk AFAIK.

If you coun availability to security, then it is.

This might not be an issue in embedded systems which have a single user, but
think of the availability of the interface in e.g. a server.

Also, this memory is locked to system physical memory, making it impossible
to page it out to a block device.

> Note BTW that in practice kmalloc already has a cap (something like 16 or 32
> MB, I believe it depends on the kernel .config) and so has CMA (the size of

This is per a single allocation. A user could create any number of them.

-- 
Sakari Ailus
sakari.ailus@xxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux