Re: process substitution fd lifetime race condition

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: process substitution fd lifetime race condition
Date	2020-04-20 18:08 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.845.1587420522.3066.bug-bash@gnu.org> (permalink)
References	(3 earlier) <e6560e95-7d3f-4651-ebbb-147c82c2dbd8@case.edu> <CAHmME9pSGcv6-b6oDjJzDi5ar7a6o19-MKBix4UofQn=khRvKg@mail.gmail.com> <01e85de9-95ef-20fd-7221-a54a0a2a304a@case.edu> <CAHmME9rRU5PAwoDrpdX-2JhwEB16S+w1QZQLJ1NKb4+AkguWyw@mail.gmail.com> <0fd24573-e788-a8eb-8050-14c603a3817f@case.edu>

Show all headers | View raw

On 4/20/20 6:02 PM, Jason A. Donenfeld wrote:

> It seems like process substitution fifo lifetime is really tricky. You
> can't really reference track, since the path is just a string that
> could be manipulated. So how do you know when it's safe to clean up
> that fd and that nobody is using it? 

In general, you clean up a procsub fd, and remove any named pipes from the
file system, when the block that uses it (or created it) ends. That is, as
you noticed, sometimes tricky.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: process substitution fd lifetime race condition Chet Ramey <chet.ramey@case.edu> - 2020-04-20 18:08 -0400

csiph-web