From 7c41029a9bf28cea5c8b61993a1903c6d0f9f5d4 Mon Sep 17 00:00:00 2001 From: Dan Carpenter Date: Thu, 12 Jan 2017 11:45:34 +0300 Subject: [PATCH] db/fixup_kernel.sh: handle __kernel_write() a bit better The columns were out of order. This stuff is still really broken and doesn't make sense... But I noticed this and decided to fix it even though it's probably a useless gesture. Signed-off-by: Dan Carpenter --- smatch_data/db/fixup_kernel.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/smatch_data/db/fixup_kernel.sh b/smatch_data/db/fixup_kernel.sh index dcb9699c..40328d88 100755 --- a/smatch_data/db/fixup_kernel.sh +++ b/smatch_data/db/fixup_kernel.sh @@ -149,7 +149,7 @@ EOF # fixme: this is totally broken call_id=$(echo "select distinct call_id from caller_info where function = '__kernel_write';" | sqlite3 $db_file) for id in $call_id ; do - echo "insert into caller_info values ('fake', '', '__kernel_write', $id, 0, 1, 1003, '*\$', '0-1000000000');" | sqlite3 $db_file + echo "insert into caller_info values ('fake', '', '__kernel_write', $id, 0, 1003, 1, '*\$', '');" | sqlite3 $db_file done for i in $(echo "select distinct return from return_states where function = 'clear_user';" | sqlite3 $db_file ) ; do -- 2.11.4.GIT