Then this is clearly a client problem. It's not supposed to do that.
On Mon, 27 Mar 2023, Brian P Bockelman wrote:
>> So, the question is how did the thread bypass the mitigation
>
> The mitigation mentioned appears to reference the channel lock. However, the mutex causing the deadlock is not the channel lock but rather the `XrdCl::Stream` lock.
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1979#issuecomment-1485056972
> You are receiving this because you commented.
>
> Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
Message ID: <xrootd/xrootd/issues/1979/1485062581@github.com>
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1979#issuecomment-1485062581",
"url": "https://github.com/xrootd/xrootd/issues/1979#issuecomment-1485062581",
"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