Re: [REQUEST FOR VOTES] snmpd: Call fclose() after fdopen() but not close()
Bart Van Assche <[email protected]>
| Newsgroups | gmane.network.net-snmp.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2020-08-10 10:51, Wes Hardaker wrote: > Bart Van Assche <[email protected]> writes: > >> That's a great question. This fix only affects pass-persist on Unix >> platforms and Cygwin but neither affects the MSVC build nor any of the >> MinGW builds since the affected code was already disabled for the >> latter two platforms. > > Thanks. Follow-on: do we have any clue which OSes actually crash as a > result of the double close? (which I admit is something that should > never have been done) Hi Wes, My understanding is that the crashes triggered by the double close() calls only occur on Windows systems and also that these crashes were fixed a long time ago. For Unix systems this patch fixes the race condition described in https://github.com/net-snmp/net-snmp/issues/157. Bart.