Bug #50414 valgrind warnings: invalid file descriptor -1 in syscall write()/read()
| Submitted: | 18 Jan 2010 14:06 | Modified: | 21 Jun 2010 0:47 |
|---|---|---|---|
| Reporter: | Bjørn Munch | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.1+ | OS: | Linux |
| Assigned to: | Daogang Qu | CPU Architecture: | Any |
| Tags: | valgrind | ||
[18 Jan 2010 14:06]
Bjørn Munch
[18 Jan 2010 19:44]
Sveta Smirnova
Thank you for the report. Verified as described.
[29 Jan 2010 2:42]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/98526 3339 Dao-Gang.Qu@sun.com 2010-01-29 Bug #50414 valgrind warnings: invalid file descriptor -1 in syscall write()/read() There is no certain condition that cause the valgrind warnings: invalid file descriptor -1 in syscall write()/read(), which will not cause any error and memory leak. So we should suppress the valgrind warnings globally as a number of tests failed with the valgrind warnings. To fix the problem, add the valgrind warnings to the global suppression list to suppress it. @ mysql-test/include/mtr_warnings.sql Added code to suppress valgrind warnings: invalid file descriptor -1 in syscall write()/read().
[29 Jan 2010 7:01]
Bjørn Munch
You might extend the pattern to "==[0-9]+== Warning: invalid file descriptor -1 in syscall read()" , to ensure/clarify this just covers the valgrind warning. I need to get this into the -mtr trees before I can merge those to the main trees.
[2 Feb 2010 12:23]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/98935 2886 Dao-Gang.Qu@sun.com 2010-02-02 Bug #50414 valgrind warnings: invalid file descriptor -1 in syscall write()/read() Sometimes stop/restart master or stop/restart salve can cause network error, which can cause the 'invalid file descriptor -1 in syscall write()/read()' warnings. All involved test cases except rpl_slave_load_remove_tmpfile belong to the kind of network error. So they are expected. The 'rpl_slave_load_remove_tmpfile' belongs to file error, but it is testing the file error as following code: DBUG_EXECUTE_IF("remove_slave_load_file_before_write", my_close(fd,MYF(0)); fd= -1; my_delete(fname, MYF(0));); So it's expected too. To fix the problem, add the valgrind warnings to the global suppression list to suppress it. @ mysql-test/include/mtr_warnings.sql Added code to suppress valgrind warnings: invalid file descriptor -1 in syscall write()/read().
[2 Feb 2010 12:27]
Bjørn Munch
Fix and explanation look fine, OK!
[3 Feb 2010 7:53]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/99007 2886 Dao-Gang.Qu@sun.com 2010-02-03 Bug #50414 valgrind warnings: invalid file descriptor -1 in syscall write()/read() Sometimes stop/restart master or stop/restart salve can cause network error, which can cause the 'invalid file descriptor -1 in syscall write()/read()' warnings. All involved test cases except rpl_slave_load_remove_tmpfile belong to the kind of network error. So they are expected. The 'rpl_slave_load_remove_tmpfile' belongs to file error, but it is testing the file error as following code: DBUG_EXECUTE_IF("remove_slave_load_file_before_write", my_close(fd,MYF(0)); fd= -1; my_delete(fname, MYF(0));); So it's expected too. To fix the problem, add the valgrind warnings to the global suppression list to suppress it. @ mysql-test/include/mtr_warnings.sql Added code to suppress valgrind warnings: invalid file descriptor -1 in syscall write()/read().
[3 Feb 2010 8:01]
Daogang Qu
Pushed to mysql-5.1-mtr. Bjorn, please take care of upmerge to the other -mtr trees as you recommended.
[3 Feb 2010 9:36]
Bjørn Munch
Pished to trunk-mtr, next-mr-mtr and 6.0-codebase-mtr (after verifying the fix in 6.0-codebase-mtr)
[20 Feb 2010 9:31]
Bugs System
Pushed into 6.0.14-alpha (revid:alik@sun.com-20100220092844-jh07ayojyxn8uh9p) (version source revid:bjorn.munch@sun.com-20100203093000-sm5tkanq19w5vgpx) (merge vers: 6.0.14-alpha) (pib:16)
[20 Feb 2010 9:34]
Bugs System
Pushed into 5.5.3-m2 (revid:alik@sun.com-20100220092622-wvhh1vfy5tjq4mhu) (version source revid:bjorn.munch@sun.com-20100203092553-1x855pw0aintk7yh) (merge vers: 5.5.1-m2) (pib:16)
[20 Feb 2010 9:37]
Bugs System
Pushed into mysql-next-mr (revid:alik@sun.com-20100220092730-paoo5t9gcajs5dq8) (version source revid:bjorn.munch@sun.com-20100203092817-93ablyd2s5332736) (pib:16)
[20 Feb 2010 19:20]
Paul DuBois
Changes to test suite. No changelog entry needed. Setting report to Need Merge pending push to 5.1.x.
[1 Mar 2010 8:42]
Bugs System
Pushed into 5.1.45 (revid:joro@sun.com-20100301083827-xnimmrjg6bh33o1o) (version source revid:azundris@mysql.com-20100222175719-viuh0f3gdsrkgv0r) (merge vers: 5.1.45) (pib:16)
[1 Mar 2010 13:27]
Jon Stephens
Change affects testing only. Closed without further action.
[17 Jun 2010 11:59]
Bugs System
Pushed into 5.1.47-ndb-7.0.16 (revid:martin.skold@mysql.com-20100617114014-bva0dy24yyd67697) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)
[17 Jun 2010 12:39]
Bugs System
Pushed into 5.1.47-ndb-6.2.19 (revid:martin.skold@mysql.com-20100617115448-idrbic6gbki37h1c) (version source revid:martin.skold@mysql.com-20100609140708-52rvuyq4q500sxkq) (merge vers: 5.1.45-ndb-6.2.19) (pib:16)
[17 Jun 2010 13:25]
Bugs System
Pushed into 5.1.47-ndb-6.3.35 (revid:martin.skold@mysql.com-20100617114611-61aqbb52j752y116) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.047 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.