Print

Print

Several crashes of EOS FSTs have been reported at CERN:
https://its.cern.ch/jira/browse/EOS-3900

It seems this is due to a race condition in xrootd client that results in a dangling pointer to the SidMgr object.

In more details: when a new message is being created, before a SID is allocated, a reference to respective SIDManager object is obtain. If at this point a TTL timeout occurs (can happen as the SID is not allocated yet) it will destroy the Channel, and as result we will end up with a dangling pointer to the old SIDManager object. This in turn, can cause a segv in ReleaseSID and AllocateSID calls.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1180", "url": "https://github.com/xrootd/xrootd/issues/1180", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1