Activity log for bug #209346

Date Who What changed Old value New value Message
2008-03-30 19:11:55 sam tygier bug added bug
2008-04-04 22:50:50 Leann Ogasawara linux: status New Incomplete
2009-01-17 00:18:11 Leann Ogasawara linux: status Incomplete Won't Fix
2009-01-17 00:18:11 Leann Ogasawara linux: statusexplanation Hi Sam, Just curious if you are able to consistently reproduce this issue or if it was a random occurrence? Also care to comment which specific version of the kernel you were using (cat /proc/version_signature)? I know 2.6.24-15 was recently released. Thanks.
2009-03-17 06:07:54 Fumihito YOSHIDA linux: status Won't Fix New
2009-03-17 06:07:54 Fumihito YOSHIDA linux: statusexplanation Hi, I found this related information at Red Hat EL 4.8's RHSA-2009:0331-14. The problem caused by race conditions, It is not hardware trouble. I could not reproduce yet, but source code said "problem stills in Jaunty"(maybe). Jaunty's linux/fs/buffer.c::void unlock_buffer is : { clear_bit_unlock(BH_Lock, &bh->b_state); smp_mb__after_clear_bit(); wake_up_bit(&bh->b_state, BH_Lock); Information from Red Hat: * http://rhn.redhat.com/errata/RHSA-2009-0331.html * => https://bugzilla.redhat.com/show_bug.cgi?id=476533 (published info, link from RHSA-2009:0331-14) * => https://bugzilla.redhat.com/show_bug.cgi?id=460179 (this is Red Hat's private) * Red Hat's patchname:linux-2.6.9-fs-fix-it-already-cleared-for-block-errors.patch linux/fs/buffer.c::void unlock_buffer is : { + smp_mb__before_clear_bit(); clear_bit_unlock(BH_Lock, &bh->b_state); smp_mb__after_clear_bit(); wake_up_bit(&bh->b_state, BH_Lock); They said, > a misplaced memory barrier at unlock_buffer() could lead to a concurrent > h_refcounter update which produced a reference counter leak and, later, a > double free in ext3_xattr_release_block(). Consequent to the double free, > ext3 reported an error > > ext3_free_blocks_sb: bit already cleared for block [block number] > > and mounted itself as read-only. With this update, the memory barrier is > now placed before the buffer head lock bit, forcing the write order and > preventing the double free. (BZ#476533) // I cant understand that why Red Hat does not distribute this info.... Related info are: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497562
2009-03-17 06:10:13 Fumihito YOSHIDA bug assigned to linux-2.6 (Debian)
2009-03-17 06:25:31 Bug Watch Updater linux-2.6: status Unknown New
2009-05-04 13:10:56 Fantix King removed subscriber Fantix King
2009-05-12 08:00:12 muchasuerte attachment added lspci_dmesg.log http://launchpadlibrarian.net/26626106/lspci_dmesg.log
2009-05-12 08:10:20 Petter Eklund removed subscriber Petter Eklund
2009-06-19 20:59:01 Leann Ogasawara bug task added linux (Ubuntu Jaunty)
2009-06-19 21:07:45 Leann Ogasawara linux (Ubuntu): status New Fix Released
2009-06-19 21:08:12 Leann Ogasawara linux (Ubuntu Jaunty): importance Undecided High
2009-06-19 21:08:12 Leann Ogasawara linux (Ubuntu Jaunty): status New Triaged
2009-07-09 17:30:49 Manoj Iyer linux (Ubuntu Jaunty): assignee Manoj Iyer (manjo)
2009-07-09 18:01:36 Manoj Iyer linux (Ubuntu Jaunty): status Triaged Incomplete
2011-07-18 18:11:46 Leann Ogasawara linux (Ubuntu Jaunty): status Incomplete Won't Fix
2013-06-04 07:32:40 Bug Watch Updater linux-2.6 (Debian): status New Fix Released