What EBADE
uses did you notice? Grepping through the Linux kernel code, I saw:
- SCSI / multipath errors. I suppose this is possible.
- Various dedup ioctl response in XFS and btrfs filesystems. Can't see how this hits XRootD.
- Ill-formatted Ceph responses (incorrect sequence numbers in response from server). I suppose it's possible.
- A bunch of wireless drivers. Can't see how this hits XRootD.
Compared to the likelihood of an authentication error, I'd consider those all quite obscure. My preference is still to simply say "Authentication failed" unless you spotted a more likely candidate than those above.
Even then, I'd still prefer switching the order:
Authentication failure - possible invalid exchange
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/pull/1916/c1441936851@github.com>
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/pull/1916#issuecomment-1441936851",
"url": "https://github.com/xrootd/xrootd/pull/1916#issuecomment-1441936851",
"name": "View Pull Request"
},
"description": "View this Pull Request 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