> I see that these applications will stay some time in the D state. > But if the read function might block they could end up in that state anyway. You need to use down_interruptible and have a suitable error out path for a ^C _______________________________________________ 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
- Re: [V4L] races in v4l read ... Alan Cox
- Re: [V4L] races in v4l read ... Oliver Neukum
