On Sun, Feb 25 2001, Alexander Viro wrote: > Let me elaborate: the race is very narrow and takes deliberate efforts to > hit. It _can_ be triggered, unfortunately. This extra up() will mess your > life later on. What's the worst that can happen? We do an extra up, but loop_thread will still quit once we hit zero lo_pending. And loop_clr_fd is still protected by lo_ctl_mutex. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- 2.4.2-ac3: loop threads in D state Nate Eldredge
- Re: 2.4.2-ac3: loop threads in D state Nate Eldredge
- Re: 2.4.2-ac3: loop threads in D state Jens Axboe
- Re: 2.4.2-ac3: loop threads in D state Alexander Viro
- Re: 2.4.2-ac3: loop threads in D state Jens Axboe
- Re: 2.4.2-ac3: loop threads in D stat... Alexander Viro
- Re: 2.4.2-ac3: loop threads in D ... Jens Axboe
- Re: 2.4.2-ac3: loop threads i... Alexander Viro
- Re: 2.4.2-ac3: loop threads i... Alexander Viro
- Re: 2.4.2-ac3: loop threads i... Jens Axboe
- Re: 2.4.2-ac3: loop threads i... Alexander Viro
- Re: 2.4.2-ac3: loop threads i... Jens Axboe
- Re: 2.4.2-ac3: loop threads i... Jens Axboe
- Re: 2.4.2-ac3: loop threads i... Alexander Viro
- Re: 2.4.2-ac3: loop threads in D state Nate Eldredge