[MDEV-10940] plugins.pam still fails in buildbot with valgrind Created: 2016-10-02  Updated: 2017-05-24  Resolved: 2017-05-24

Status: Closed
Project: MariaDB Server
Component/s: Plugin - pam, Tests
Affects Version/s: 10.1, 10.2
Fix Version/s: 10.1.24, 10.2.7

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled
relates to MDEV-10889 plugins.pam_cleartext fails in buildb... Closed
relates to MDEV-10890 plugins.pam fails in buildbot with va... Closed

 Description   

MDEV-10889 and MDEV-10890 are closed as fixed in 10.1.18, but plugins.pam still fails as of September 29, with the version already bumped to 10.1.19:
http://buildbot.askmonty.org/buildbot/builders/work-amd64-valgrind/builds/9388/steps/test/logs/stdio

plugins.pam                              w1 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2016-10-02 03:47:31
line
==27479== Thread 7:
==27479== Invalid read of size 1
==27479==    at 0x4C27F72: strlen (vg_replace_strmem.c:454)
==27479==    by 0x62700DF: vfprintf (in /lib64/libc-2.9.so)
==27479==    by 0x627131F: ??? (in /lib64/libc-2.9.so)
==27479==    by 0x626C6C5: vfprintf (in /lib64/libc-2.9.so)
==27479==    by 0x62764A7: fprintf (in /lib64/libc-2.9.so)
==27479==    by 0xE1DC23D: pam_auth (auth_pam.c:168)
==27479==    by 0x5FC245: do_auth_once(THD*, st_mysql_lex_string const*, MPVIO_EXT*) (sql_acl.cc:12282)
==27479==    by 0x60D6AC: acl_authenticate(THD*, unsigned int) (sql_acl.cc:12394)
==27479==    by 0x7BB6A7: check_connection(THD*) (sql_connect.cc:1023)
==27479==    by 0x7BC34A: login_connection(THD*) (sql_connect.cc:1091)
==27479==    by 0x7BC429: thd_prepare_connection(THD*) (sql_connect.cc:1270)
==27479==    by 0x7BCB9E: do_handle_one_connection(THD*) (sql_connect.cc:1341)
==27479==  Address 0xd279910 is 0 bytes inside a block of size 9 free'd
==27479==    at 0x4C261C8: free (vg_replace_malloc.c:530)
==27479==    by 0xE6155A9: pam_end (in /lib64/libpam.so.0.81.12)
==27479==    by 0xE1DC210: pam_auth (auth_pam.c:167)
==27479==    by 0x5FC245: do_auth_once(THD*, st_mysql_lex_string const*, MPVIO_EXT*) (sql_acl.cc:12282)
==27479==    by 0x60D6AC: acl_authenticate(THD*, unsigned int) (sql_acl.cc:12394)
==27479==    by 0x7BB6A7: check_connection(THD*) (sql_connect.cc:1023)
==27479==    by 0x7BC34A: login_connection(THD*) (sql_connect.cc:1091)
==27479==    by 0x7BC429: thd_prepare_connection(THD*) (sql_connect.cc:1270)
==27479==    by 0x7BCB9E: do_handle_one_connection(THD*) (sql_connect.cc:1341)
==27479==    by 0x7BCD2D: handle_one_connection (sql_connect.cc:1262)
==27479==    by 0xC2ECBB: pfs_spawn_thread (pfs.cc:1860)
==27479==    by 0x4E3806F: start_thread (in /lib64/libpthread-2.9.so)
==27479==  Block was alloc'd at
==27479==    at 0x4C267EE: malloc (vg_replace_malloc.c:299)
==27479==    by 0xE618797: ??? (in /lib64/libpam.so.0.81.12)
==27479==    by 0xE617DF5: pam_set_item (in /lib64/libpam.so.0.81.12)
==27479==    by 0xEA39A04: ???
==27479==    by 0xE615001: ??? (in /lib64/libpam.so.0.81.12)
==27479==    by 0xE6148C1: pam_authenticate (in /lib64/libpam.so.0.81.12)
==27479==    by 0xE1DC136: pam_auth (auth_pam.c:154)
==27479==    by 0x5FC245: do_auth_once(THD*, st_mysql_lex_string const*, MPVIO_EXT*) (sql_acl.cc:12282)
==27479==    by 0x60D6AC: acl_authenticate(THD*, unsigned int) (sql_acl.cc:12394)
==27479==    by 0x7BB6A7: check_connection(THD*) (sql_connect.cc:1023)
==27479==    by 0x7BC34A: login_connection(THD*) (sql_connect.cc:1091)
==27479==    by 0x7BC429: thd_prepare_connection(THD*) (sql_connect.cc:1270)
^ Found warnings in /mnt/data/buildot/maria-slave/work-opensuse-amd64/build/mysql-test/var/1/log/mysqld.1.err
ok



 Comments   
Comment by Elena Stepanova [ 2017-05-08 ]

Recent occurrence on 10.2:
http://buildbot.askmonty.org/buildbot/builders/work-amd64-valgrind/builds/10030/steps/test/logs/stdio

Comment by Sergei Golubchik [ 2017-05-20 ]

It was only present in debug builds, release binaries were safe. Anyway, fixed.

Generated at Thu Feb 08 07:46:05 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.