Hi, all (developers, first:) )! Function sql_xlat release sql socket before strncpy() access sqlsocket->row. So, second thread my reserve this socket and change sqlsocket->row after first thread release socket but before first call strncpy(). At my sight, this situation could cause SIGSEGV. Isn't it? Of course, sql_xlat never called from rlm_sql, but when I use it (in modified rlm_sql) and give high loading for radiusd (~100 requests per second), radiusd recieved SIGSEGV in strncpy() at sql_xlat(). But when the radiusd with the same module runningas single thread, all is OK.
I wanna know, am I right or not :) -- Denis Tatarskikh [UdSU/MF] [UdSU/IC] mailto:[EMAIL PROTECTED] - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
