Message ID | 20190716020423.vvfjtjrtxxuogqce@kbuntu |
---|---|
State | New |
Headers | show |
Series | [Xenial,SRU] Xenial update: 4.4.184 upstream stable release | expand |
On 7/16/19 4:04 AM, Khaled Elmously wrote: > https://bugs.launchpad.net/bugs/1836667 > > All patches from this update were already present in xenial as part of the CVE-2019-11478 handling. > > -Khaled > > -- > > The following changes since commit e2c4a2f81bbe308684845b8b38e6ad4712476b77: > > Linux 4.4.183 (2019-07-15 20:51:06 -0400) > > are available in the Git repository at: > > git+ssh://git.launchpad.net/~kmously/ubuntu/+source/linux/+git/xenial update-to-4.4.184 > > for you to fetch changes up to 516be67db7f052585354a95ed8f3773c6a06f02b: > > Linux 4.4.184 (2019-07-15 20:51:32 -0400) Applied to xenial/master-next branch, with the updated sha1 (34d28e70b18a). Thanks, Kleber > > ---------------------------------------------------------------- > Greg Kroah-Hartman (1): > Linux 4.4.184 > > Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >
On 2019-07-15 22:04:24, Khaled Elmously wrote: > https://bugs.launchpad.net/bugs/1836667 > > All patches from this update were already present in xenial as part of the CVE-2019-11478 handling. Just an FYI... we should have dropped my backport and went with the backport that was provided by Eric Dumazet to upstream linux-stable. The two backports are fairly different but Eric knows more about the TCP stack than I ever will. :) I don't know if it is a good idea to always revert our backport and take upstream linux-stable's backport (there could be Ubuntu-specific changes in ours) but we should probably flag it somehow when the two backports differ. Tyler > > -Khaled > > -- > > The following changes since commit e2c4a2f81bbe308684845b8b38e6ad4712476b77: > > Linux 4.4.183 (2019-07-15 20:51:06 -0400) > > are available in the Git repository at: > > git+ssh://git.launchpad.net/~kmously/ubuntu/+source/linux/+git/xenial update-to-4.4.184 > > for you to fetch changes up to 516be67db7f052585354a95ed8f3773c6a06f02b: > > Linux 4.4.184 (2019-07-15 20:51:32 -0400) > > ---------------------------------------------------------------- > Greg Kroah-Hartman (1): > Linux 4.4.184 > > Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > > -- > kernel-team mailing list > kernel-team@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/kernel-team
On 2019-08-26 17:35:04, Tyler Hicks wrote: > On 2019-07-15 22:04:24, Khaled Elmously wrote: > > https://bugs.launchpad.net/bugs/1836667 > > > > All patches from this update were already present in xenial as part of the CVE-2019-11478 handling. > > Just an FYI... we should have dropped my backport and went with the > backport that was provided by Eric Dumazet to upstream linux-stable. The > two backports are fairly different but Eric knows more about the TCP > stack than I ever will. :) I should have mentioned that I'll be working on reverting my backport and pulling upstream's backport along with some other TCP fixes. I'll likely get the patches to the list tomorrow once I finish testing them. Tyler > > I don't know if it is a good idea to always revert our backport and take > upstream linux-stable's backport (there could be Ubuntu-specific changes > in ours) but we should probably flag it somehow when the two backports > differ. > > Tyler > > > > > -Khaled > > > > -- > > > > The following changes since commit e2c4a2f81bbe308684845b8b38e6ad4712476b77: > > > > Linux 4.4.183 (2019-07-15 20:51:06 -0400) > > > > are available in the Git repository at: > > > > git+ssh://git.launchpad.net/~kmously/ubuntu/+source/linux/+git/xenial update-to-4.4.184 > > > > for you to fetch changes up to 516be67db7f052585354a95ed8f3773c6a06f02b: > > > > Linux 4.4.184 (2019-07-15 20:51:32 -0400) > > > > ---------------------------------------------------------------- > > Greg Kroah-Hartman (1): > > Linux 4.4.184 > > > > Makefile | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > > > -- > > kernel-team mailing list > > kernel-team@lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/kernel-team