Print

Print


Thanks David!

I would recommend turning monitoring off until we can get this fix rolled 
out. Yes, the monitoring people will be upset but better that we don't 
crash. As for the fix, we would ned to develop a new one for 3.3.x as the 
head fix doesn't back port.

Andy

On Thu, 5 Dec 2013, smithdh wrote:

> Hi,
>
> Some dpm-xrootd sites have reported crashes of their redirector xrootd 3.3.3 daemon (seen once at one SL5 site, and frequently at one SL6 site). (core dumps available, generally they are crashes in XrdScheduler methods because of corrupt XrdJob objects).
>
> I've done some investigation, initially to check if the dpm/dmlite components were at fault. In this case I think there is a problem in XrdXrootdMonitor::Redirect. This copy:
>
> [XrdXrootdMonitor.cc:788]
> strcpy(dest, hName); dest += hLen; *dest++ = ':';
>
> can overwrite past the end of the space allocated for the MonRdrBuff, e.g. if hName is somewhat more than 256 characters longer than Path and the starting point for the entry is close enough to the end of the buffer. I think this condition is now avoided in the master branch, after ipv6 related changes. Would it be cover this situation in 3.3.x ?
>
> Thanks,
> David
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/64

---
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/64#issuecomment-30026992

########################################################################
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