> Exactly for this reason I've made a patch, that takes a semaphore in read() > and write(). But you cant just go around taking semaphores blindly. Suppose you block in the read method and a 2nd one blocks on the semaphore - its now unkillable until the first moves on _______________________________________________ Video4linux-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/video4linux-list
- [V4L] races in v4l read + write in 2.4 Oliver Neukum
- Re: [V4L] races in v4l read + write in 2.4 Justin Schoeman
- Re: [V4L] races in v4l read + write in 2.4 Oliver Neukum
- Re: [V4L] races in v4l read + write in 2.4 Justin Schoeman
- Re: [V4L] races in v4l read + write in 2.... Alan Cox
- Re: [V4L] races in v4l read + write ... Oliver Neukum
- Re: [V4L] races in v4l read + wr... Alan Cox
- Re: [V4L] races in v4l read ... Oliver Neukum
- Re: [V4L] races in v4l read ... Alan Cox
- Re: [V4L] races in v4l read ... Oliver Neukum
- Re: [V4L] races in v4l read ... Alan Cox
- Re: [V4L] races in v4l read ... Michel Lanners
- Re: [V4L] races in v4l read ... Jeff Garzik
- Re: [V4L] races in v4l read ... Jeff Garzik
- [V4L] PATCH: file_operations... Jeff Garzik
- Re: [V4L] races in v4l read ... Alan Cox
- Re: [V4L] races in v4l read + write ... Gerd Knorr
- Re: [V4L] races in v4l read + wr... Alan Cox
- Re: [V4L] races in v4l read ... Gerd Knorr
