The XrdCl::OpenFlags::Append flag is part of the XRootD client API. The flag is mapped to the kXR_open_apnd constant of the XRootD protocol. However the flag is not mapped and passed to the XrdSfsFile::open() method of the XRootD server API.

Please could the XrdCl::OpenFlags::Append flag either be completely removed from the XRootD client API or could the XRootD server map kXR_open_apnd to a dedicated server side flag and pass it through to the XrdSfsFile::open() method?

This issue is being created due to the following incident which uncovered the fact that the XRootD server does not pass kXR_open_apnd through to XrdSfsFile::open(). A client contacted an XRootD server with an "open for append" request using the XrdCl::OpenFlags::Append flag. This request should have been considered an "open for write" however the server incorrectly interpreted it as an "open for read" because "#define SFS_O_RDONLY 0 // open read/only".

—
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/1126?email_source=notifications\u0026email_token=AA7NRDRN4VHTH42RTVUHWQTRAAYPLA5CNFSM4KMSSLUKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IJHFVTA", "url": "https://github.com/xrootd/xrootd/issues/1126?email_source=notifications\u0026email_token=AA7NRDRN4VHTH42RTVUHWQTRAAYPLA5CNFSM4KMSSLUKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IJHFVTA", "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