| 2019-10-03 12:21:56 |
Colin Ian King |
bug |
|
|
added bug |
| 2019-10-03 12:22:04 |
Colin Ian King |
linux (Ubuntu): status |
New |
In Progress |
|
| 2019-10-03 12:22:06 |
Colin Ian King |
linux (Ubuntu): importance |
Undecided |
High |
|
| 2019-10-03 12:22:08 |
Colin Ian King |
linux (Ubuntu): assignee |
|
Colin Ian King (colin-king) |
|
| 2019-10-03 12:27:05 |
Colin Ian King |
description |
== SRU Justifucation Eoan ==
Now that 5.4 contains a fix to the bootup regression due to the lack of entropy at bootable we should apply this fix and also revert the revert of commit "Revert "ext4: make __ext4_get_inode_loc plug"".
== Fix ==
So, to clarify, apply the two upstream 5.4-rc commits:
commit 50ee7529ec4500c88f8664560770a7a1b65db72b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat Sep 28 16:53:52 2019 -0700
random: try to actively add entropy rather than passively wait for it
commit 02f03c4206c1b2a7451d3b3546f86c9c783eac13
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun Sep 29 17:59:23 2019 -0700
Revert "Revert "ext4: make __ext4_get_inode_loc plug""
I've benchmarked the Eoan kernel with these two patches and found the following speed improvements:
git grep of the kernel: 0.14%
building fwts: 0.40%
build stress-ng 0.45%
tar up kernel source: 7.6%
boot time of eoan cloud image: 10.5%
So I think this justifies the speed improvements.
== Regression potential ==
minor change to ext4, which has been regression tested, so risk here is small. The entropy change will alter the random number generation, but I believe this does not change the cryptographical security of the random numbers being generated, so think this change is not security risk.
originally the ext4 change caused boot time user space regressions because of the entropy change of this fix, but the random fix addresses this, so I believe this risk is now zero. |
== SRU Justification Eoan ==
Now that 5.4 contains a fix to the bootup regression due to the lack of entropy at bootable we should apply this fix and also revert the revert of commit "Revert "ext4: make __ext4_get_inode_loc plug"".
== Fix ==
So, to clarify, apply the two upstream 5.4-rc commits:
commit 50ee7529ec4500c88f8664560770a7a1b65db72b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat Sep 28 16:53:52 2019 -0700
random: try to actively add entropy rather than passively wait for it
commit 02f03c4206c1b2a7451d3b3546f86c9c783eac13
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun Sep 29 17:59:23 2019 -0700
Revert "Revert "ext4: make __ext4_get_inode_loc plug""
I've benchmarked the Eoan kernel with these two patches and found the following speed improvements:
git grep of the kernel: 0.14%
building fwts: 0.40%
build stress-ng 0.45%
tar up kernel source: 7.6%
boot time of eoan cloud image: 10.5%
So I think this justifies the speed improvements.
== Regression potential ==
minor change to ext4, which has been regression tested, so risk here is small. The entropy change will alter the random number generation, but I believe this does not change the cryptographical security of the random numbers being generated, so think this change is not security risk.
originally the ext4 change caused boot time user space regressions because of the entropy change of this fix, but the random fix addresses this, so I believe this risk is now zero. |
|
| 2019-10-03 12:28:17 |
Colin Ian King |
description |
== SRU Justification Eoan ==
Now that 5.4 contains a fix to the bootup regression due to the lack of entropy at bootable we should apply this fix and also revert the revert of commit "Revert "ext4: make __ext4_get_inode_loc plug"".
== Fix ==
So, to clarify, apply the two upstream 5.4-rc commits:
commit 50ee7529ec4500c88f8664560770a7a1b65db72b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat Sep 28 16:53:52 2019 -0700
random: try to actively add entropy rather than passively wait for it
commit 02f03c4206c1b2a7451d3b3546f86c9c783eac13
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun Sep 29 17:59:23 2019 -0700
Revert "Revert "ext4: make __ext4_get_inode_loc plug""
I've benchmarked the Eoan kernel with these two patches and found the following speed improvements:
git grep of the kernel: 0.14%
building fwts: 0.40%
build stress-ng 0.45%
tar up kernel source: 7.6%
boot time of eoan cloud image: 10.5%
So I think this justifies the speed improvements.
== Regression potential ==
minor change to ext4, which has been regression tested, so risk here is small. The entropy change will alter the random number generation, but I believe this does not change the cryptographical security of the random numbers being generated, so think this change is not security risk.
originally the ext4 change caused boot time user space regressions because of the entropy change of this fix, but the random fix addresses this, so I believe this risk is now zero. |
== SRU Justification Eoan ==
Now that 5.4 contains a fix to the bootup regression due to the lack of entropy at bootable we should apply this fix and also revert the revert of commit "Revert "ext4: make __ext4_get_inode_loc plug"".
== Fix ==
So, to clarify, apply the two upstream 5.4-rc commits:
commit 50ee7529ec4500c88f8664560770a7a1b65db72b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat Sep 28 16:53:52 2019 -0700
random: try to actively add entropy rather than passively wait for it
commit 02f03c4206c1b2a7451d3b3546f86c9c783eac13
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun Sep 29 17:59:23 2019 -0700
Revert "Revert "ext4: make __ext4_get_inode_loc plug""
I've benchmarked the Eoan kernel with these two patches and found the following speed improvements:
git grep of the kernel: 0.14%
building fwts: 0.40%
build stress-ng 0.45%
tar up kernel source: 7.6%
boot time of eoan cloud image: 10.5%
So I think the speed improvements justify the SRU.
== Regression potential ==
minor change to ext4, which has been regression tested, so risk here is small. The entropy change will alter the random number generation, but I believe this does not change the cryptographical security of the random numbers being generated, so think this change is not security risk.
originally the ext4 change caused boot time user space regressions because of the entropy change of this fix, but the random fix addresses this, so I believe this risk is now zero. |
|
| 2019-10-03 13:08:27 |
Colin Ian King |
description |
== SRU Justification Eoan ==
Now that 5.4 contains a fix to the bootup regression due to the lack of entropy at bootable we should apply this fix and also revert the revert of commit "Revert "ext4: make __ext4_get_inode_loc plug"".
== Fix ==
So, to clarify, apply the two upstream 5.4-rc commits:
commit 50ee7529ec4500c88f8664560770a7a1b65db72b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat Sep 28 16:53:52 2019 -0700
random: try to actively add entropy rather than passively wait for it
commit 02f03c4206c1b2a7451d3b3546f86c9c783eac13
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun Sep 29 17:59:23 2019 -0700
Revert "Revert "ext4: make __ext4_get_inode_loc plug""
I've benchmarked the Eoan kernel with these two patches and found the following speed improvements:
git grep of the kernel: 0.14%
building fwts: 0.40%
build stress-ng 0.45%
tar up kernel source: 7.6%
boot time of eoan cloud image: 10.5%
So I think the speed improvements justify the SRU.
== Regression potential ==
minor change to ext4, which has been regression tested, so risk here is small. The entropy change will alter the random number generation, but I believe this does not change the cryptographical security of the random numbers being generated, so think this change is not security risk.
originally the ext4 change caused boot time user space regressions because of the entropy change of this fix, but the random fix addresses this, so I believe this risk is now zero. |
== SRU Justification Eoan ==
Now that 5.4 contains a fix to the bootup regression due to the lack of entropy at bootable we should apply this fix and also revert the revert of commit "Revert "ext4: make __ext4_get_inode_loc plug"".
== Fix ==
So, to clarify, apply the two upstream 5.4-rc commits:
commit 50ee7529ec4500c88f8664560770a7a1b65db72b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat Sep 28 16:53:52 2019 -0700
random: try to actively add entropy rather than passively wait for it
commit 02f03c4206c1b2a7451d3b3546f86c9c783eac13
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun Sep 29 17:59:23 2019 -0700
Revert "Revert "ext4: make __ext4_get_inode_loc plug""
I've benchmarked the Eoan kernel with these two patches and found theo
following speed improvements on an i7-3770 CPU @ 3.40GHz with 8GB and a
WDC WD10EZEX-21WN4A HDD (7200RPM, 64MB cache).
git grep of the kernel: 0.14%
building fwts: 0.40%
build stress-ng 0.45%
tar up kernel source: 7.6%
boot time of eoan cloud image: 10.5%
So I think the speed improvements justify the SRU.
== Regression potential ==
minor change to ext4, which has been regression tested, so risk here is small. The entropy change will alter the random number generation, but I believe this does not change the cryptographical security of the random numbers being generated, so think this change is not security risk.
originally the ext4 change caused boot time user space regressions because of the entropy change of this fix, but the random fix addresses this, so I believe this risk is now zero. |
|
| 2019-10-16 16:33:16 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-10-16 16:33:16 |
Kleber Sacilotto de Souza |
bug task added |
|
linux (Ubuntu Eoan) |
|
| 2019-10-24 16:02:46 |
Ubuntu Kernel Bot |
tags |
|
verification-needed-eoan |
|
| 2019-11-04 11:06:47 |
Colin Ian King |
tags |
verification-needed-eoan |
verification-done-eoan |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
linux (Ubuntu Eoan): status |
In Progress |
Fix Released |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2018-12207 |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2019-0154 |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2019-0155 |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2019-11135 |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2019-15793 |
|
| 2019-11-12 22:18:04 |
Launchpad Janitor |
cve linked |
|
2019-17666 |
|
| 2019-11-13 23:05:06 |
Colin Ian King |
linux (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2019-11-13 23:05:09 |
Colin Ian King |
linux (Ubuntu): status |
Fix Committed |
Fix Released |
|
