linux-kernel - Re: [PATCH] V4L: fix retval in vivi driver for more than one device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0808241152400.2897@areia>
Date:	Sun, 24 Aug 2008 11:58:35 -0300 (BRT)
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	Hans Verkuil <hverkuil@...all.nl>
cc:	video4linux-list@...hat.com,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	Henne <henne@...htwindheim.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] V4L: fix retval in vivi driver for more than one device

> Please note that I am working on creating a much improved V4L
> infrastructure to take care of such things. It's simply nuts that v4l
> drivers need to put in all the plumbing just to be able to have
> multiple instances.
>
> In particular, all these limitations on the number of instances should
> disappear (unless you run out of minors).

If you use vivi with a large number of devs (for example, 128), you'll run 
out of minors, since we currently have only 64 for video grabber. Due to 
the videodev limits, in fact, we can allocate "only" 32 virtual devices 
per driver.

Even with the changes on V4L infrastructure, vivi driver still doesn't do 
the right thing if you use a large number of devs.

I'm currently fixing the "vivi" driver and adding some notes on it about 
the current limits.

Cheers,
Mauro.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/