Activity log for bug #1789131

Date Who What changed Old value New value Message
2018-08-26 20:33:36 Sarah Newman bug added bug
2018-08-26 21:00:05 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2018-08-26 22:02:07 Sarah Newman linux (Ubuntu): status Incomplete Confirmed
2018-08-26 23:14:20 Matt Nordhoff bug added subscriber Matt Nordhoff
2018-08-27 09:39:25 Msd bug added subscriber Msd
2018-08-27 18:12:48 Joseph Salisbury linux (Ubuntu): importance Undecided High
2018-08-27 18:13:36 Joseph Salisbury nominated for series Ubuntu Trusty
2018-08-27 18:13:36 Joseph Salisbury bug task added linux (Ubuntu Trusty)
2018-08-27 18:13:42 Joseph Salisbury linux (Ubuntu Trusty): importance Undecided High
2018-08-27 18:13:44 Joseph Salisbury linux (Ubuntu Trusty): status New Incomplete
2018-08-27 18:13:47 Joseph Salisbury linux (Ubuntu): status Confirmed Incomplete
2018-08-27 18:13:56 Joseph Salisbury tags kernel-key trusty
2018-08-27 20:22:05 Joseph Salisbury linux (Ubuntu Trusty): status Incomplete Triaged
2018-08-27 20:22:07 Joseph Salisbury linux (Ubuntu): status Incomplete Triaged
2018-08-28 16:10:41 Joseph Salisbury linux (Ubuntu): assignee Joseph Salisbury (jsalisbury)
2018-08-28 16:10:45 Joseph Salisbury linux (Ubuntu Trusty): assignee Joseph Salisbury (jsalisbury)
2018-08-28 16:10:51 Joseph Salisbury linux (Ubuntu): status Triaged In Progress
2018-08-28 16:10:54 Joseph Salisbury linux (Ubuntu Trusty): status Triaged In Progress
2018-08-28 16:12:00 Joseph Salisbury linux (Ubuntu): importance High Critical
2018-08-28 16:12:03 Joseph Salisbury linux (Ubuntu Trusty): importance High Critical
2018-08-28 17:35:07 Tyler Hicks bug added subscriber Tyler Hicks
2018-08-29 07:28:31 Jochen Barth bug added subscriber Jochen Barth
2018-08-29 09:38:49 Niko Klanecek bug added subscriber Niko Klanecek
2018-08-29 12:53:44 gagzou bug added subscriber gagzou
2018-08-29 14:11:32 gagzou cve linked 2018-1093
2018-08-31 14:06:00 Joseph Salisbury description A customer reported on all of their ext3 and none of their ext4 systems that the file system was in read-only mode, I believe after rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output of tune2fs -l for one of the file systems: tune2fs 1.42.12 (29-Aug-2014) Last mounted on: / Filesystem UUID: 748f503a-443d-4769-8dd2-45ff46b48555 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 1966080 Block count: 7863296 Reserved block count: 393164 Free blocks: 4568472 Free inodes: 1440187 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1022 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width: 512 Filesystem created: Thu Feb 25 21:54:24 2016 Last mount time: Fri Aug 24 07:40:51 2018 Last write time: Fri Aug 24 07:40:51 2018 Mount count: 1 Maximum mount count: 25 Last checked: Fri Aug 24 07:38:54 2018 Check interval: 15552000 (6 months) Next check after: Wed Feb 20 07:38:54 2019 Lifetime writes: 7381 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: d6564a54-cd2a-4804-ad94-1e4e0e47933a Journal backup: inode blocks FS Error count: 210 First error time: Fri Aug 24 07:40:51 2018 First error function: ext4_validate_block_bitmap First error line #: 376 First error inode #: 0 First error block #: 0 Last error time: Sun Aug 26 19:35:16 2018 Last error function: ext4_remount Last error line #: 4833 Last error inode #: 0 Last error block #: 0 == SRU Justification == Mainline commit 7dac4a1726a9 introduced a regression in v4.17-rc1, which made it's way into Trusty via upstream stable updates. This regression is resolved by mainline commit 22be37acce25. This commit has been cc'd to upstream stable, but has not made it's way into Trusty as of yet. == Fix == 22be37acce25 ("ext4: fix bitmap position validation") == Regression Potential == Low. This commit has been cc'd to upstream stable, so it has had additional upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. A customer reported on all of their ext3 and none of their ext4 systems that the file system was in read-only mode, I believe after rebooting into 3.13.0-157.207 from 3.13.0-156.206. Here is the output of tune2fs -l for one of the file systems: tune2fs 1.42.12 (29-Aug-2014) Last mounted on: / Filesystem UUID: 748f503a-443d-4769-8dd2-45ff46b48555 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 1966080 Block count: 7863296 Reserved block count: 393164 Free blocks: 4568472 Free inodes: 1440187 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1022 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width: 512 Filesystem created: Thu Feb 25 21:54:24 2016 Last mount time: Fri Aug 24 07:40:51 2018 Last write time: Fri Aug 24 07:40:51 2018 Mount count: 1 Maximum mount count: 25 Last checked: Fri Aug 24 07:38:54 2018 Check interval: 15552000 (6 months) Next check after: Wed Feb 20 07:38:54 2019 Lifetime writes: 7381 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: d6564a54-cd2a-4804-ad94-1e4e0e47933a Journal backup: inode blocks FS Error count: 210 First error time: Fri Aug 24 07:40:51 2018 First error function: ext4_validate_block_bitmap First error line #: 376 First error inode #: 0 First error block #: 0 Last error time: Sun Aug 26 19:35:16 2018 Last error function: ext4_remount Last error line #: 4833 Last error inode #: 0 Last error block #: 0
2018-09-05 14:34:34 Kleber Sacilotto de Souza linux (Ubuntu Trusty): status In Progress Fix Committed
2018-09-13 11:03:22 Brad Figg tags kernel-key trusty kernel-key trusty verification-needed-trusty
2018-09-13 14:21:22 Msd tags kernel-key trusty verification-needed-trusty kernel-key trusty verification-done-trusty
2018-10-01 16:02:51 Launchpad Janitor linux (Ubuntu Trusty): status Fix Committed Fix Released
2018-10-01 16:02:51 Launchpad Janitor cve linked 2018-14633
2018-10-01 16:02:51 Launchpad Janitor cve linked 2018-14634
2018-10-01 16:02:51 Launchpad Janitor cve linked 2018-15572
2018-10-01 16:02:51 Launchpad Janitor cve linked 2018-15594
2018-10-01 16:02:51 Launchpad Janitor cve linked 2018-3620
2018-10-01 16:02:51 Launchpad Janitor cve linked 2018-3646
2018-10-01 16:02:51 Launchpad Janitor cve linked 2018-6554
2018-10-01 16:02:51 Launchpad Janitor cve linked 2018-6555
2018-11-09 17:34:06 Joseph Salisbury linux (Ubuntu): status In Progress Fix Released
2019-07-24 20:18:51 Brad Figg tags kernel-key trusty verification-done-trusty cscc kernel-key trusty verification-done-trusty