1. 23 Feb, 2009 2 commits
  2. 21 Feb, 2009 7 commits
  3. 20 Feb, 2009 3 commits
  4. 19 Feb, 2009 5 commits
  5. 17 Feb, 2009 3 commits
  6. 12 Feb, 2009 1 commit
  7. 11 Feb, 2009 4 commits
  8. 10 Feb, 2009 11 commits
  9. 09 Feb, 2009 4 commits
    • Mats Kindahl's avatar
      Merging with 5.1-bugteam. · 8a98664d
      Mats Kindahl authored
      8a98664d
    • Davi Arnaut's avatar
      Merge 5.1-bugteam into main. · c99a6ce2
      Davi Arnaut authored
      c99a6ce2
    • Davi Arnaut's avatar
      Merge from upstream 5.1-bugteam. · 86a11e6a
      Davi Arnaut authored
      86a11e6a
    • Davi Arnaut's avatar
      Bug#42634: % character in query can cause mysqld signal 11 segfault · bab4ff1a
      Davi Arnaut authored
      The problem is that a unfiltered user query was being passed as
      the format string parameter of sql_print_warning which later
      performs printf-like formatting, leading to crashes if the user
      query contains formatting instructions (ie: %s). Also, it was
      using THD::query as the source of the user query, but this
      variable is not meaningful in some situations -- in a delayed
      insert, it points to the table name.
      
      The solution is to pass the user query as a parameter for the
      format string and use the function parameter query_arg as the
      source of the user query.
      
      mysql-test/suite/binlog/r/binlog_unsafe.result:
        Add test case result for Bug#42634
      mysql-test/suite/binlog/t/binlog_unsafe.test:
        Add test case for Bug#42634
      sql/sql_class.cc:
        Don't pass the user query as a format string.
      bab4ff1a