scott/blockinator
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

Fix possible SEGVs by changing the nByte parameter of sqlite3_prepare_v2().

Browse source 
Segmentation Faults reported and observed under high traffic.  For some reason this is a previously seen issue with the nBytes parameter of sqlite3_prepare_v2().  Not sure why, but it seems to fix the issue.
This commit is contained in:
Scott Wallace 2012-12-19 15:27:41 +00:00
parent af891a04d3
commit 5b5aad08cb
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
apache/mod_blockinator.c
View file

@ -77,7 +77,7 @@ static int mod_blockinator_method_handler(request_rec *r)
statement = sqlite3_mprintf("SELECT * FROM blocklist WHERE remote_ip = '%q' AND (forwarded_ip = 'ANY' OR forwarded_ip = '%q') AND (useragent = 'ANY' OR useragent = '%q')", remote_ip, forwarded_ip, useragent);
/* Prepare the statement */
sqlite3_rc = sqlite3_prepare_v2(db, statement, BUFSIZ, &sqlite3_statement, NULL);
sqlite3_rc = sqlite3_prepare_v2(db, statement, -1, &sqlite3_statement, NULL);
if (sqlite3_rc != SQLITE_OK) {
/* SQLite error. Allow. */
ap_log_rerror(APLOG_MARK, APLOG_ERR, 0, r, "SQLite error (%s). Allow traffic from %s by default.", sqlite3_errmsg(db), remote_ip);