Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Tue, Jan 2, 2018 at 3:08 PM, Greg KHwrote: > On Tue, Jan 02, 2018 at 02:11:25PM -0500, Neal Cardwell wrote: ... >> Thanks, Greg and David. Looks like these 2 patches will cherry-pick >> cleanly if cherry-picked in the following sequence, on top of >> 4.9.74-rc1, which already has 6c9e73ef9aa7 ("tcp_bbr: record "full bw >> reached" decision in new full_bw_reached bit"): >> >> $ git checkout linux-stable-rc/linux-4.9.y >> >> $ git cherry-pick 2f6c498e4f15 >> Performing inexact rename detection: 100% (17803152/17803152), done. >> [detached HEAD 0982234c57e1] tcp_bbr: reset full pipe detection on >> loss recovery undo >> Date: Thu Dec 7 12:43:31 2017 -0500 >> 1 file changed, 4 insertions(+) >> >> $ git cherry-pick 600647d467c6 >> Performing inexact rename detection: 100% (17803152/17803152), done. >> [detached HEAD 7e866eccd083] tcp_bbr: reset long-term bandwidth >> sampling on loss recovery undo >> Date: Thu Dec 7 12:43:32 2017 -0500 >> 1 file changed, 1 insertion(+) >> >> $ git log --oneline --decorate | head -3 >> 7e866eccd083 (HEAD) tcp_bbr: reset long-term bandwidth sampling on >> loss recovery undo >> 0982234c57e1 tcp_bbr: reset full pipe detection on loss recovery undo >> 79070be7f1ae (linux-stable-rc/linux-4.9.y) Linux 4.9.74-rc1 >> >> I verified that this compiles without warnings, and boots, and BBR works. >> >> Shall I prepare another version of these 2 patches, or do we think >> this recipe will be sufficient? (Sorry I am not more familiar with the >> backport-to-stable process.) > > That works, those two patches are now queued up for the next stable > release, thanks! > > greg k-h Great. Thank you, Greg and David! neal
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Tue, Jan 2, 2018 at 3:08 PM, Greg KH wrote: > On Tue, Jan 02, 2018 at 02:11:25PM -0500, Neal Cardwell wrote: ... >> Thanks, Greg and David. Looks like these 2 patches will cherry-pick >> cleanly if cherry-picked in the following sequence, on top of >> 4.9.74-rc1, which already has 6c9e73ef9aa7 ("tcp_bbr: record "full bw >> reached" decision in new full_bw_reached bit"): >> >> $ git checkout linux-stable-rc/linux-4.9.y >> >> $ git cherry-pick 2f6c498e4f15 >> Performing inexact rename detection: 100% (17803152/17803152), done. >> [detached HEAD 0982234c57e1] tcp_bbr: reset full pipe detection on >> loss recovery undo >> Date: Thu Dec 7 12:43:31 2017 -0500 >> 1 file changed, 4 insertions(+) >> >> $ git cherry-pick 600647d467c6 >> Performing inexact rename detection: 100% (17803152/17803152), done. >> [detached HEAD 7e866eccd083] tcp_bbr: reset long-term bandwidth >> sampling on loss recovery undo >> Date: Thu Dec 7 12:43:32 2017 -0500 >> 1 file changed, 1 insertion(+) >> >> $ git log --oneline --decorate | head -3 >> 7e866eccd083 (HEAD) tcp_bbr: reset long-term bandwidth sampling on >> loss recovery undo >> 0982234c57e1 tcp_bbr: reset full pipe detection on loss recovery undo >> 79070be7f1ae (linux-stable-rc/linux-4.9.y) Linux 4.9.74-rc1 >> >> I verified that this compiles without warnings, and boots, and BBR works. >> >> Shall I prepare another version of these 2 patches, or do we think >> this recipe will be sufficient? (Sorry I am not more familiar with the >> backport-to-stable process.) > > That works, those two patches are now queued up for the next stable > release, thanks! > > greg k-h Great. Thank you, Greg and David! neal
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On 01/01/2018 07:31 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.74 release. > There are 75 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.9.y > and the diffstat can be found below. > > thanks, > > greg k-h > Compiled and booted on my test system. No dmesg regressions. thanks, -- Shuah
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On 01/01/2018 07:31 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.74 release. > There are 75 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.9.y > and the diffstat can be found below. > > thanks, > > greg k-h > Compiled and booted on my test system. No dmesg regressions. thanks, -- Shuah
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Tue, Jan 02, 2018 at 02:11:25PM -0500, Neal Cardwell wrote: > On Tue, Jan 2, 2018 at 1:32 PM, David Millerwrote: > > From: Neal Cardwell > > Date: Tue, 2 Jan 2018 11:57:59 -0500 > > > >> On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman > >> wrote: > >>> This is the start of the stable review cycle for the 4.9.74 release. > >>> There are 75 patches in this series, all will be posted as a response > >>> to this one. If anyone has any issues with these being applied, please > >>> let me know. > >>> > >>> Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > >>> Anything received after that time might be too late. > >>> > >>> The whole patch series can be found in one patch at: > >>> kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz > >>> or in the git tree and branch at: > >>> > >>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >>> linux-4.9.y > >>> and the diffstat can be found below. > >> > >> Hi Greg, > >> > >> In looking at the 4.9 and 4.14 patches yesterday, I noticed there were > >> two TCP BBR fixes that made it into 4.14 but not 4.9. Doing an > >> inventory of the TCP BBR fixes, AFAICT we have: > >> > >> c589e69b508d tcp_bbr: record "full bw reached" decision in new > >> full_bw_reached bit > >> - in 4.9 and 4.14 (great) > >> > >> 2f6c498e4f15 tcp_bbr: reset full pipe detection on loss recovery undo > >> - in 4.14 (but not 4.9) > >> > >> 600647d467c6 tcp_bbr: reset long-term bandwidth sampling on loss recovery > >> undo > >> - in 4.14 (but not 4.9) > >> > >> Lacking the second and third patches in 4.9 will not cause any new > >> problems, but it will miss out on some nice fixes. If it's possible to > >> get 2f6c498e4f15 and 600647d467c6 either into 4.9.74 or 4.9.75, I > >> would be very grateful. > > > > These were not straight-forward to backport and I felt the risk outweighed > > the gains. > > > > If you want to do the backport yourself and you feel confident in it, > > feel free. > > Thanks, Greg and David. Looks like these 2 patches will cherry-pick > cleanly if cherry-picked in the following sequence, on top of > 4.9.74-rc1, which already has 6c9e73ef9aa7 ("tcp_bbr: record "full bw > reached" decision in new full_bw_reached bit"): > > $ git checkout linux-stable-rc/linux-4.9.y > > $ git cherry-pick 2f6c498e4f15 > Performing inexact rename detection: 100% (17803152/17803152), done. > [detached HEAD 0982234c57e1] tcp_bbr: reset full pipe detection on > loss recovery undo > Date: Thu Dec 7 12:43:31 2017 -0500 > 1 file changed, 4 insertions(+) > > $ git cherry-pick 600647d467c6 > Performing inexact rename detection: 100% (17803152/17803152), done. > [detached HEAD 7e866eccd083] tcp_bbr: reset long-term bandwidth > sampling on loss recovery undo > Date: Thu Dec 7 12:43:32 2017 -0500 > 1 file changed, 1 insertion(+) > > $ git log --oneline --decorate | head -3 > 7e866eccd083 (HEAD) tcp_bbr: reset long-term bandwidth sampling on > loss recovery undo > 0982234c57e1 tcp_bbr: reset full pipe detection on loss recovery undo > 79070be7f1ae (linux-stable-rc/linux-4.9.y) Linux 4.9.74-rc1 > > I verified that this compiles without warnings, and boots, and BBR works. > > Shall I prepare another version of these 2 patches, or do we think > this recipe will be sufficient? (Sorry I am not more familiar with the > backport-to-stable process.) That works, those two patches are now queued up for the next stable release, thanks! greg k-h
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Tue, Jan 02, 2018 at 02:11:25PM -0500, Neal Cardwell wrote: > On Tue, Jan 2, 2018 at 1:32 PM, David Miller wrote: > > From: Neal Cardwell > > Date: Tue, 2 Jan 2018 11:57:59 -0500 > > > >> On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman > >> wrote: > >>> This is the start of the stable review cycle for the 4.9.74 release. > >>> There are 75 patches in this series, all will be posted as a response > >>> to this one. If anyone has any issues with these being applied, please > >>> let me know. > >>> > >>> Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > >>> Anything received after that time might be too late. > >>> > >>> The whole patch series can be found in one patch at: > >>> kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz > >>> or in the git tree and branch at: > >>> > >>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >>> linux-4.9.y > >>> and the diffstat can be found below. > >> > >> Hi Greg, > >> > >> In looking at the 4.9 and 4.14 patches yesterday, I noticed there were > >> two TCP BBR fixes that made it into 4.14 but not 4.9. Doing an > >> inventory of the TCP BBR fixes, AFAICT we have: > >> > >> c589e69b508d tcp_bbr: record "full bw reached" decision in new > >> full_bw_reached bit > >> - in 4.9 and 4.14 (great) > >> > >> 2f6c498e4f15 tcp_bbr: reset full pipe detection on loss recovery undo > >> - in 4.14 (but not 4.9) > >> > >> 600647d467c6 tcp_bbr: reset long-term bandwidth sampling on loss recovery > >> undo > >> - in 4.14 (but not 4.9) > >> > >> Lacking the second and third patches in 4.9 will not cause any new > >> problems, but it will miss out on some nice fixes. If it's possible to > >> get 2f6c498e4f15 and 600647d467c6 either into 4.9.74 or 4.9.75, I > >> would be very grateful. > > > > These were not straight-forward to backport and I felt the risk outweighed > > the gains. > > > > If you want to do the backport yourself and you feel confident in it, > > feel free. > > Thanks, Greg and David. Looks like these 2 patches will cherry-pick > cleanly if cherry-picked in the following sequence, on top of > 4.9.74-rc1, which already has 6c9e73ef9aa7 ("tcp_bbr: record "full bw > reached" decision in new full_bw_reached bit"): > > $ git checkout linux-stable-rc/linux-4.9.y > > $ git cherry-pick 2f6c498e4f15 > Performing inexact rename detection: 100% (17803152/17803152), done. > [detached HEAD 0982234c57e1] tcp_bbr: reset full pipe detection on > loss recovery undo > Date: Thu Dec 7 12:43:31 2017 -0500 > 1 file changed, 4 insertions(+) > > $ git cherry-pick 600647d467c6 > Performing inexact rename detection: 100% (17803152/17803152), done. > [detached HEAD 7e866eccd083] tcp_bbr: reset long-term bandwidth > sampling on loss recovery undo > Date: Thu Dec 7 12:43:32 2017 -0500 > 1 file changed, 1 insertion(+) > > $ git log --oneline --decorate | head -3 > 7e866eccd083 (HEAD) tcp_bbr: reset long-term bandwidth sampling on > loss recovery undo > 0982234c57e1 tcp_bbr: reset full pipe detection on loss recovery undo > 79070be7f1ae (linux-stable-rc/linux-4.9.y) Linux 4.9.74-rc1 > > I verified that this compiles without warnings, and boots, and BBR works. > > Shall I prepare another version of these 2 patches, or do we think > this recipe will be sufficient? (Sorry I am not more familiar with the > backport-to-stable process.) That works, those two patches are now queued up for the next stable release, thanks! greg k-h
Re: [PATCH 4.9 00/75] 4.9.74-stable review
From: Neal CardwellDate: Tue, 2 Jan 2018 14:11:25 -0500 > Looks like these 2 patches will cherry-pick cleanly if cherry-picked > in the following sequence, on top of 4.9.74-rc1, which already has > 6c9e73ef9aa7 ("tcp_bbr: record "full bw reached" decision in new > full_bw_reached bit"): > > $ git checkout linux-stable-rc/linux-4.9.y > > $ git cherry-pick 2f6c498e4f15 > Performing inexact rename detection: 100% (17803152/17803152), done. > [detached HEAD 0982234c57e1] tcp_bbr: reset full pipe detection on > loss recovery undo > Date: Thu Dec 7 12:43:31 2017 -0500 > 1 file changed, 4 insertions(+) > > $ git cherry-pick 600647d467c6 > Performing inexact rename detection: 100% (17803152/17803152), done. > [detached HEAD 7e866eccd083] tcp_bbr: reset long-term bandwidth > sampling on loss recovery undo > Date: Thu Dec 7 12:43:32 2017 -0500 > 1 file changed, 1 insertion(+) > > $ git log --oneline --decorate | head -3 > 7e866eccd083 (HEAD) tcp_bbr: reset long-term bandwidth sampling on > loss recovery undo > 0982234c57e1 tcp_bbr: reset full pipe detection on loss recovery undo > 79070be7f1ae (linux-stable-rc/linux-4.9.y) Linux 4.9.74-rc1 > > I verified that this compiles without warnings, and boots, and BBR works. > > Shall I prepare another version of these 2 patches, or do we think > this recipe will be sufficient? (Sorry I am not more familiar with the > backport-to-stable process.) If this works and Greg is OK with it, I am fine with it too.
Re: [PATCH 4.9 00/75] 4.9.74-stable review
From: Neal Cardwell Date: Tue, 2 Jan 2018 14:11:25 -0500 > Looks like these 2 patches will cherry-pick cleanly if cherry-picked > in the following sequence, on top of 4.9.74-rc1, which already has > 6c9e73ef9aa7 ("tcp_bbr: record "full bw reached" decision in new > full_bw_reached bit"): > > $ git checkout linux-stable-rc/linux-4.9.y > > $ git cherry-pick 2f6c498e4f15 > Performing inexact rename detection: 100% (17803152/17803152), done. > [detached HEAD 0982234c57e1] tcp_bbr: reset full pipe detection on > loss recovery undo > Date: Thu Dec 7 12:43:31 2017 -0500 > 1 file changed, 4 insertions(+) > > $ git cherry-pick 600647d467c6 > Performing inexact rename detection: 100% (17803152/17803152), done. > [detached HEAD 7e866eccd083] tcp_bbr: reset long-term bandwidth > sampling on loss recovery undo > Date: Thu Dec 7 12:43:32 2017 -0500 > 1 file changed, 1 insertion(+) > > $ git log --oneline --decorate | head -3 > 7e866eccd083 (HEAD) tcp_bbr: reset long-term bandwidth sampling on > loss recovery undo > 0982234c57e1 tcp_bbr: reset full pipe detection on loss recovery undo > 79070be7f1ae (linux-stable-rc/linux-4.9.y) Linux 4.9.74-rc1 > > I verified that this compiles without warnings, and boots, and BBR works. > > Shall I prepare another version of these 2 patches, or do we think > this recipe will be sufficient? (Sorry I am not more familiar with the > backport-to-stable process.) If this works and Greg is OK with it, I am fine with it too.
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Tue, Jan 2, 2018 at 1:32 PM, David Millerwrote: > From: Neal Cardwell > Date: Tue, 2 Jan 2018 11:57:59 -0500 > >> On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman >> wrote: >>> This is the start of the stable review cycle for the 4.9.74 release. >>> There are 75 patches in this series, all will be posted as a response >>> to this one. If anyone has any issues with these being applied, please >>> let me know. >>> >>> Responses should be made by Wed Jan 3 14:00:03 UTC 2018. >>> Anything received after that time might be too late. >>> >>> The whole patch series can be found in one patch at: >>> kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz >>> or in the git tree and branch at: >>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >>> linux-4.9.y >>> and the diffstat can be found below. >> >> Hi Greg, >> >> In looking at the 4.9 and 4.14 patches yesterday, I noticed there were >> two TCP BBR fixes that made it into 4.14 but not 4.9. Doing an >> inventory of the TCP BBR fixes, AFAICT we have: >> >> c589e69b508d tcp_bbr: record "full bw reached" decision in new >> full_bw_reached bit >> - in 4.9 and 4.14 (great) >> >> 2f6c498e4f15 tcp_bbr: reset full pipe detection on loss recovery undo >> - in 4.14 (but not 4.9) >> >> 600647d467c6 tcp_bbr: reset long-term bandwidth sampling on loss recovery >> undo >> - in 4.14 (but not 4.9) >> >> Lacking the second and third patches in 4.9 will not cause any new >> problems, but it will miss out on some nice fixes. If it's possible to >> get 2f6c498e4f15 and 600647d467c6 either into 4.9.74 or 4.9.75, I >> would be very grateful. > > These were not straight-forward to backport and I felt the risk outweighed > the gains. > > If you want to do the backport yourself and you feel confident in it, > feel free. Thanks, Greg and David. Looks like these 2 patches will cherry-pick cleanly if cherry-picked in the following sequence, on top of 4.9.74-rc1, which already has 6c9e73ef9aa7 ("tcp_bbr: record "full bw reached" decision in new full_bw_reached bit"): $ git checkout linux-stable-rc/linux-4.9.y $ git cherry-pick 2f6c498e4f15 Performing inexact rename detection: 100% (17803152/17803152), done. [detached HEAD 0982234c57e1] tcp_bbr: reset full pipe detection on loss recovery undo Date: Thu Dec 7 12:43:31 2017 -0500 1 file changed, 4 insertions(+) $ git cherry-pick 600647d467c6 Performing inexact rename detection: 100% (17803152/17803152), done. [detached HEAD 7e866eccd083] tcp_bbr: reset long-term bandwidth sampling on loss recovery undo Date: Thu Dec 7 12:43:32 2017 -0500 1 file changed, 1 insertion(+) $ git log --oneline --decorate | head -3 7e866eccd083 (HEAD) tcp_bbr: reset long-term bandwidth sampling on loss recovery undo 0982234c57e1 tcp_bbr: reset full pipe detection on loss recovery undo 79070be7f1ae (linux-stable-rc/linux-4.9.y) Linux 4.9.74-rc1 I verified that this compiles without warnings, and boots, and BBR works. Shall I prepare another version of these 2 patches, or do we think this recipe will be sufficient? (Sorry I am not more familiar with the backport-to-stable process.) Thanks! neal
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Tue, Jan 2, 2018 at 1:32 PM, David Miller wrote: > From: Neal Cardwell > Date: Tue, 2 Jan 2018 11:57:59 -0500 > >> On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman >> wrote: >>> This is the start of the stable review cycle for the 4.9.74 release. >>> There are 75 patches in this series, all will be posted as a response >>> to this one. If anyone has any issues with these being applied, please >>> let me know. >>> >>> Responses should be made by Wed Jan 3 14:00:03 UTC 2018. >>> Anything received after that time might be too late. >>> >>> The whole patch series can be found in one patch at: >>> kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz >>> or in the git tree and branch at: >>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >>> linux-4.9.y >>> and the diffstat can be found below. >> >> Hi Greg, >> >> In looking at the 4.9 and 4.14 patches yesterday, I noticed there were >> two TCP BBR fixes that made it into 4.14 but not 4.9. Doing an >> inventory of the TCP BBR fixes, AFAICT we have: >> >> c589e69b508d tcp_bbr: record "full bw reached" decision in new >> full_bw_reached bit >> - in 4.9 and 4.14 (great) >> >> 2f6c498e4f15 tcp_bbr: reset full pipe detection on loss recovery undo >> - in 4.14 (but not 4.9) >> >> 600647d467c6 tcp_bbr: reset long-term bandwidth sampling on loss recovery >> undo >> - in 4.14 (but not 4.9) >> >> Lacking the second and third patches in 4.9 will not cause any new >> problems, but it will miss out on some nice fixes. If it's possible to >> get 2f6c498e4f15 and 600647d467c6 either into 4.9.74 or 4.9.75, I >> would be very grateful. > > These were not straight-forward to backport and I felt the risk outweighed > the gains. > > If you want to do the backport yourself and you feel confident in it, > feel free. Thanks, Greg and David. Looks like these 2 patches will cherry-pick cleanly if cherry-picked in the following sequence, on top of 4.9.74-rc1, which already has 6c9e73ef9aa7 ("tcp_bbr: record "full bw reached" decision in new full_bw_reached bit"): $ git checkout linux-stable-rc/linux-4.9.y $ git cherry-pick 2f6c498e4f15 Performing inexact rename detection: 100% (17803152/17803152), done. [detached HEAD 0982234c57e1] tcp_bbr: reset full pipe detection on loss recovery undo Date: Thu Dec 7 12:43:31 2017 -0500 1 file changed, 4 insertions(+) $ git cherry-pick 600647d467c6 Performing inexact rename detection: 100% (17803152/17803152), done. [detached HEAD 7e866eccd083] tcp_bbr: reset long-term bandwidth sampling on loss recovery undo Date: Thu Dec 7 12:43:32 2017 -0500 1 file changed, 1 insertion(+) $ git log --oneline --decorate | head -3 7e866eccd083 (HEAD) tcp_bbr: reset long-term bandwidth sampling on loss recovery undo 0982234c57e1 tcp_bbr: reset full pipe detection on loss recovery undo 79070be7f1ae (linux-stable-rc/linux-4.9.y) Linux 4.9.74-rc1 I verified that this compiles without warnings, and boots, and BBR works. Shall I prepare another version of these 2 patches, or do we think this recipe will be sufficient? (Sorry I am not more familiar with the backport-to-stable process.) Thanks! neal
Re: [PATCH 4.9 00/75] 4.9.74-stable review
From: Neal CardwellDate: Tue, 2 Jan 2018 11:57:59 -0500 > On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman > wrote: >> This is the start of the stable review cycle for the 4.9.74 release. >> There are 75 patches in this series, all will be posted as a response >> to this one. If anyone has any issues with these being applied, please >> let me know. >> >> Responses should be made by Wed Jan 3 14:00:03 UTC 2018. >> Anything received after that time might be too late. >> >> The whole patch series can be found in one patch at: >> kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz >> or in the git tree and branch at: >> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> linux-4.9.y >> and the diffstat can be found below. > > Hi Greg, > > In looking at the 4.9 and 4.14 patches yesterday, I noticed there were > two TCP BBR fixes that made it into 4.14 but not 4.9. Doing an > inventory of the TCP BBR fixes, AFAICT we have: > > c589e69b508d tcp_bbr: record "full bw reached" decision in new > full_bw_reached bit > - in 4.9 and 4.14 (great) > > 2f6c498e4f15 tcp_bbr: reset full pipe detection on loss recovery undo > - in 4.14 (but not 4.9) > > 600647d467c6 tcp_bbr: reset long-term bandwidth sampling on loss recovery undo > - in 4.14 (but not 4.9) > > Lacking the second and third patches in 4.9 will not cause any new > problems, but it will miss out on some nice fixes. If it's possible to > get 2f6c498e4f15 and 600647d467c6 either into 4.9.74 or 4.9.75, I > would be very grateful. These were not straight-forward to backport and I felt the risk outweighed the gains. If you want to do the backport yourself and you feel confident in it, feel free.
Re: [PATCH 4.9 00/75] 4.9.74-stable review
From: Neal Cardwell Date: Tue, 2 Jan 2018 11:57:59 -0500 > On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman > wrote: >> This is the start of the stable review cycle for the 4.9.74 release. >> There are 75 patches in this series, all will be posted as a response >> to this one. If anyone has any issues with these being applied, please >> let me know. >> >> Responses should be made by Wed Jan 3 14:00:03 UTC 2018. >> Anything received after that time might be too late. >> >> The whole patch series can be found in one patch at: >> kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz >> or in the git tree and branch at: >> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> linux-4.9.y >> and the diffstat can be found below. > > Hi Greg, > > In looking at the 4.9 and 4.14 patches yesterday, I noticed there were > two TCP BBR fixes that made it into 4.14 but not 4.9. Doing an > inventory of the TCP BBR fixes, AFAICT we have: > > c589e69b508d tcp_bbr: record "full bw reached" decision in new > full_bw_reached bit > - in 4.9 and 4.14 (great) > > 2f6c498e4f15 tcp_bbr: reset full pipe detection on loss recovery undo > - in 4.14 (but not 4.9) > > 600647d467c6 tcp_bbr: reset long-term bandwidth sampling on loss recovery undo > - in 4.14 (but not 4.9) > > Lacking the second and third patches in 4.9 will not cause any new > problems, but it will miss out on some nice fixes. If it's possible to > get 2f6c498e4f15 and 600647d467c6 either into 4.9.74 or 4.9.75, I > would be very grateful. These were not straight-forward to backport and I felt the risk outweighed the gains. If you want to do the backport yourself and you feel confident in it, feel free.
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Tue, Jan 02, 2018 at 08:49:05AM -0800, Guenter Roeck wrote: > On Mon, Jan 01, 2018 at 03:31:37PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.74 release. > > There are 75 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > > Anything received after that time might be too late. > > > > Note: This is for v4.9.73-77-g79070be. Good! I snuck a i386 UP build fix in there :) > > Build results: > total: 145 pass: 145 fail: 0 > Qemu test results: > total: 126 pass: 126 fail: 0 > > Details are available at http://kerneltests.org/builders. Thanks for testing all of these and letting me know. greg k-h
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Tue, Jan 02, 2018 at 08:49:05AM -0800, Guenter Roeck wrote: > On Mon, Jan 01, 2018 at 03:31:37PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.74 release. > > There are 75 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > > Anything received after that time might be too late. > > > > Note: This is for v4.9.73-77-g79070be. Good! I snuck a i386 UP build fix in there :) > > Build results: > total: 145 pass: 145 fail: 0 > Qemu test results: > total: 126 pass: 126 fail: 0 > > Details are available at http://kerneltests.org/builders. Thanks for testing all of these and letting me know. greg k-h
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Tue, Jan 02, 2018 at 11:57:59AM -0500, Neal Cardwell wrote: > On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman >wrote: > > This is the start of the stable review cycle for the 4.9.74 release. > > There are 75 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > linux-4.9.y > > and the diffstat can be found below. > > Hi Greg, > > In looking at the 4.9 and 4.14 patches yesterday, I noticed there were > two TCP BBR fixes that made it into 4.14 but not 4.9. Doing an > inventory of the TCP BBR fixes, AFAICT we have: > > c589e69b508d tcp_bbr: record "full bw reached" decision in new > full_bw_reached bit > - in 4.9 and 4.14 (great) > > 2f6c498e4f15 tcp_bbr: reset full pipe detection on loss recovery undo > - in 4.14 (but not 4.9) > > 600647d467c6 tcp_bbr: reset long-term bandwidth sampling on loss recovery undo > - in 4.14 (but not 4.9) > > Lacking the second and third patches in 4.9 will not cause any new > problems, but it will miss out on some nice fixes. If it's possible to > get 2f6c498e4f15 and 600647d467c6 either into 4.9.74 or 4.9.75, I > would be very grateful. I go with the set of backported patches from DaveM, so I just assume he didn't include these in the 4.9 set of patches for a good reason. You can ask on netdev@ about this and cc: me, to make it go a bit faster, if I get an ACK from DaveM, I can queue them up directly. thanks, greg k-h
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Tue, Jan 02, 2018 at 11:57:59AM -0500, Neal Cardwell wrote: > On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.9.74 release. > > There are 75 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > linux-4.9.y > > and the diffstat can be found below. > > Hi Greg, > > In looking at the 4.9 and 4.14 patches yesterday, I noticed there were > two TCP BBR fixes that made it into 4.14 but not 4.9. Doing an > inventory of the TCP BBR fixes, AFAICT we have: > > c589e69b508d tcp_bbr: record "full bw reached" decision in new > full_bw_reached bit > - in 4.9 and 4.14 (great) > > 2f6c498e4f15 tcp_bbr: reset full pipe detection on loss recovery undo > - in 4.14 (but not 4.9) > > 600647d467c6 tcp_bbr: reset long-term bandwidth sampling on loss recovery undo > - in 4.14 (but not 4.9) > > Lacking the second and third patches in 4.9 will not cause any new > problems, but it will miss out on some nice fixes. If it's possible to > get 2f6c498e4f15 and 600647d467c6 either into 4.9.74 or 4.9.75, I > would be very grateful. I go with the set of backported patches from DaveM, so I just assume he didn't include these in the 4.9 set of patches for a good reason. You can ask on netdev@ about this and cc: me, to make it go a bit faster, if I get an ACK from DaveM, I can queue them up directly. thanks, greg k-h
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartmanwrote: > This is the start of the stable review cycle for the 4.9.74 release. > There are 75 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.9.y > and the diffstat can be found below. Hi Greg, In looking at the 4.9 and 4.14 patches yesterday, I noticed there were two TCP BBR fixes that made it into 4.14 but not 4.9. Doing an inventory of the TCP BBR fixes, AFAICT we have: c589e69b508d tcp_bbr: record "full bw reached" decision in new full_bw_reached bit - in 4.9 and 4.14 (great) 2f6c498e4f15 tcp_bbr: reset full pipe detection on loss recovery undo - in 4.14 (but not 4.9) 600647d467c6 tcp_bbr: reset long-term bandwidth sampling on loss recovery undo - in 4.14 (but not 4.9) Lacking the second and third patches in 4.9 will not cause any new problems, but it will miss out on some nice fixes. If it's possible to get 2f6c498e4f15 and 600647d467c6 either into 4.9.74 or 4.9.75, I would be very grateful. Thanks! neal
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Mon, Jan 1, 2018 at 9:31 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.74 release. > There are 75 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.9.y > and the diffstat can be found below. Hi Greg, In looking at the 4.9 and 4.14 patches yesterday, I noticed there were two TCP BBR fixes that made it into 4.14 but not 4.9. Doing an inventory of the TCP BBR fixes, AFAICT we have: c589e69b508d tcp_bbr: record "full bw reached" decision in new full_bw_reached bit - in 4.9 and 4.14 (great) 2f6c498e4f15 tcp_bbr: reset full pipe detection on loss recovery undo - in 4.14 (but not 4.9) 600647d467c6 tcp_bbr: reset long-term bandwidth sampling on loss recovery undo - in 4.14 (but not 4.9) Lacking the second and third patches in 4.9 will not cause any new problems, but it will miss out on some nice fixes. If it's possible to get 2f6c498e4f15 and 600647d467c6 either into 4.9.74 or 4.9.75, I would be very grateful. Thanks! neal
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Mon, Jan 01, 2018 at 03:31:37PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.74 release. > There are 75 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > Anything received after that time might be too late. > Note: This is for v4.9.73-77-g79070be. Build results: total: 145 pass: 145 fail: 0 Qemu test results: total: 126 pass: 126 fail: 0 Details are available at http://kerneltests.org/builders. Guenter
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On Mon, Jan 01, 2018 at 03:31:37PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.74 release. > There are 75 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > Anything received after that time might be too late. > Note: This is for v4.9.73-77-g79070be. Build results: total: 145 pass: 145 fail: 0 Qemu test results: total: 126 pass: 126 fail: 0 Details are available at http://kerneltests.org/builders. Guenter
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On 1 January 2018 at 20:01, Greg Kroah-Hartmanwrote: > This is the start of the stable review cycle for the 4.9.74 release. > There are 75 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.9.y > and the diffstat can be found below. > > thanks, > > greg k-h Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.9.74-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: b59b0bd326dce09081ffaa96d821f66b9dd4c8d6 git describe: v4.9.73-76-gb59b0bd326dc Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.73-76-gb59b0bd326dc No regressions (compared to build v4.9.73) Boards, architectures and test suites: - hi6220-hikey - arm64 * boot - pass: 20, * kselftest - pass: 39, skip: 23 * libhugetlbfs - pass: 90, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 21, skip: 1 * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 14, * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 983, skip: 121 * ltp-timers-tests - pass: 12, juno-r2 - arm64 * boot - pass: 20, * kselftest - pass: 40, skip: 23 * libhugetlbfs - pass: 90, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 22, * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 14, * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 987, skip: 121 * ltp-timers-tests - pass: 12, x15 - arm * boot - pass: 20, * kselftest - pass: 37, skip: 25 * libhugetlbfs - pass: 87, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 20, skip: 2 * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 13, skip: 1 * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 1037, skip: 66 * ltp-timers-tests - pass: 12, x86_64 * boot - pass: 20, * kselftest - pass: 53, skip: 26 * libhugetlbfs - pass: 90, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 61, skip: 1 * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 22, * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 9, skip: 1 * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 1005, skip: 116 * ltp-timers-tests - pass: 12, Documentation - https://collaborate.linaro.org/display/LKFT/Email+Reports Tested-by: Naresh Kamboju
Re: [PATCH 4.9 00/75] 4.9.74-stable review
On 1 January 2018 at 20:01, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.74 release. > There are 75 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Wed Jan 3 14:00:03 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.9.y > and the diffstat can be found below. > > thanks, > > greg k-h Results from Linaro’s test farm. No regressions on arm64, arm and x86_64. Summary kernel: 4.9.74-rc1 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git git branch: linux-4.9.y git commit: b59b0bd326dce09081ffaa96d821f66b9dd4c8d6 git describe: v4.9.73-76-gb59b0bd326dc Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.73-76-gb59b0bd326dc No regressions (compared to build v4.9.73) Boards, architectures and test suites: - hi6220-hikey - arm64 * boot - pass: 20, * kselftest - pass: 39, skip: 23 * libhugetlbfs - pass: 90, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 21, skip: 1 * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 14, * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 983, skip: 121 * ltp-timers-tests - pass: 12, juno-r2 - arm64 * boot - pass: 20, * kselftest - pass: 40, skip: 23 * libhugetlbfs - pass: 90, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 22, * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 14, * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 987, skip: 121 * ltp-timers-tests - pass: 12, x15 - arm * boot - pass: 20, * kselftest - pass: 37, skip: 25 * libhugetlbfs - pass: 87, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 60, * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 20, skip: 2 * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 13, skip: 1 * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 1037, skip: 66 * ltp-timers-tests - pass: 12, x86_64 * boot - pass: 20, * kselftest - pass: 53, skip: 26 * libhugetlbfs - pass: 90, skip: 1 * ltp-cap_bounds-tests - pass: 2, * ltp-containers-tests - pass: 64, * ltp-fcntl-locktests-tests - pass: 2, * ltp-filecaps-tests - pass: 2, * ltp-fs-tests - pass: 61, skip: 1 * ltp-fs_bind-tests - pass: 2, * ltp-fs_perms_simple-tests - pass: 19, * ltp-fsx-tests - pass: 2, * ltp-hugetlb-tests - pass: 22, * ltp-io-tests - pass: 3, * ltp-ipc-tests - pass: 9, * ltp-math-tests - pass: 11, * ltp-nptl-tests - pass: 2, * ltp-pty-tests - pass: 4, * ltp-sched-tests - pass: 9, skip: 1 * ltp-securebits-tests - pass: 4, * ltp-syscalls-tests - pass: 1005, skip: 116 * ltp-timers-tests - pass: 12, Documentation - https://collaborate.linaro.org/display/LKFT/Email+Reports Tested-by: Naresh Kamboju
[PATCH 4.9 00/75] 4.9.74-stable review
This is the start of the stable review cycle for the 4.9.74 release. There are 75 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed Jan 3 14:00:03 UTC 2018. Anything received after that time might be too late. The whole patch series can be found in one patch at: kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.9.y and the diffstat can be found below. thanks, greg k-h - Pseudo-Shortlog of commits: Greg Kroah-HartmanLinux 4.9.74-rc1 Johan Hovold tty: fix tty_ldisc_receive_buf() documentation Linus Torvalds n_tty: fix EXTPROC vs ICANON interaction with TIOCINQ (aka FIONREAD) Thomas Gleixner x86/smpboot: Remove stale TLB flush invocations Thomas Gleixner nohz: Prevent a timer interrupt storm in tick_nohz_stop_sched_tick() Thomas Gleixner timers: Reinitialize per cpu bases on hotplug Thomas Gleixner timers: Invoke timer_start_debug() where it makes sense Anna-Maria Gleixner timers: Use deferrable base independent of base::nohz_active Daniel Thompson usb: xhci: Add XHCI_TRUST_TX_LENGTH for Renesas uPD720201 Mathias Nyman USB: Fix off by one in type-specific length check of BOS SSP capability Oliver Neukum usb: add RESET_RESUME for ELSA MicroLink 56K Dmitry Fleytman Dmitry Fleytman usb: Add device quirk for Logitech HD Pro Webcam C925e SZ Lin (林上智) USB: serial: option: adding support for YUGA CLM920-NC5 Daniele Palmas USB: serial: option: add support for Telit ME910 PID 0x1101 Reinhard Speyerer USB: serial: qcserial: add Sierra Wireless EM7565 Max Schulze USB: serial: ftdi_sio: add id for Airbus DS P8GR Shuah Khan usbip: vhci: stop printing kernel pointer addresses in messages Shuah Khan usbip: stub: stop printing kernel pointer addresses in messages Shuah Khan usbip: prevent leaking socket pointer address in messages Juan Zea usbip: fix usbip bind writing random string after command in match_busid Julian Wiedmann s390/qeth: update takeover IPs after configuration change Julian Wiedmann s390/qeth: lock IP table while applying takeover changes Julian Wiedmann s390/qeth: don't apply takeover changes to RXIP Julian Wiedmann s390/qeth: apply takeover changes when mode is toggled Moni Shoua net/mlx5: Fix error flow in CREATE_QP command Gal Pressman net/mlx5e: Prevent possible races in VXLAN control flow Gal Pressman net/mlx5e: Add refcount to VXLAN structure Gal Pressman net/mlx5e: Fix possible deadlock of VXLAN lock Gal Pressman net/mlx5e: Fix features check of IPv6 traffic Eran Ben Elisha net/mlx5: Fix rate limit packet pacing naming and struct Yousuk Seung tcp: invalidate rate samples during SACK reneging Willem de Bruijn sock: free skb in skb_complete_tx_timestamp on error Grygorii Strashko net: phy: micrel: ksz9031: reconfigure autoneg after phy autoneg workaround Eric W. Biederman net: Fix double free and memory corruption in get_net_ns_by_id() Andrew Lunn net: fec: Allow reception of frames bigger than 1522 bytes Nikolay Aleksandrov net: bridge: fix early call to br_stp_change_bridge_id and plug newlink leaks Ido Schimmel ipv4: Fix use-after-free when flushing FIB tables Nikita V. Shirokov adding missing rcu_read_unlock in ipxip6_rcv Tonghao Zhang sctp: Replace use of sockets_allocated with specified macro. Tobias Jordan net: mvmdio: disable/unprepare clocks in EPROBE_DEFER case Mohamed Ghannam net: ipv4: fix for a race condition in raw_sendmsg Brian King tg3: Fix rx hang on MTU change with 5717/5719 Christoph Paasch tcp md5sig: Use skb's saddr when replying to an incoming segment Neal Cardwell tcp_bbr: record "full
[PATCH 4.9 00/75] 4.9.74-stable review
This is the start of the stable review cycle for the 4.9.74 release. There are 75 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed Jan 3 14:00:03 UTC 2018. Anything received after that time might be too late. The whole patch series can be found in one patch at: kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.74-rc1.gz or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.9.y and the diffstat can be found below. thanks, greg k-h - Pseudo-Shortlog of commits: Greg Kroah-Hartman Linux 4.9.74-rc1 Johan Hovold tty: fix tty_ldisc_receive_buf() documentation Linus Torvalds n_tty: fix EXTPROC vs ICANON interaction with TIOCINQ (aka FIONREAD) Thomas Gleixner x86/smpboot: Remove stale TLB flush invocations Thomas Gleixner nohz: Prevent a timer interrupt storm in tick_nohz_stop_sched_tick() Thomas Gleixner timers: Reinitialize per cpu bases on hotplug Thomas Gleixner timers: Invoke timer_start_debug() where it makes sense Anna-Maria Gleixner timers: Use deferrable base independent of base::nohz_active Daniel Thompson usb: xhci: Add XHCI_TRUST_TX_LENGTH for Renesas uPD720201 Mathias Nyman USB: Fix off by one in type-specific length check of BOS SSP capability Oliver Neukum usb: add RESET_RESUME for ELSA MicroLink 56K Dmitry Fleytman Dmitry Fleytman usb: Add device quirk for Logitech HD Pro Webcam C925e SZ Lin (林上智) USB: serial: option: adding support for YUGA CLM920-NC5 Daniele Palmas USB: serial: option: add support for Telit ME910 PID 0x1101 Reinhard Speyerer USB: serial: qcserial: add Sierra Wireless EM7565 Max Schulze USB: serial: ftdi_sio: add id for Airbus DS P8GR Shuah Khan usbip: vhci: stop printing kernel pointer addresses in messages Shuah Khan usbip: stub: stop printing kernel pointer addresses in messages Shuah Khan usbip: prevent leaking socket pointer address in messages Juan Zea usbip: fix usbip bind writing random string after command in match_busid Julian Wiedmann s390/qeth: update takeover IPs after configuration change Julian Wiedmann s390/qeth: lock IP table while applying takeover changes Julian Wiedmann s390/qeth: don't apply takeover changes to RXIP Julian Wiedmann s390/qeth: apply takeover changes when mode is toggled Moni Shoua net/mlx5: Fix error flow in CREATE_QP command Gal Pressman net/mlx5e: Prevent possible races in VXLAN control flow Gal Pressman net/mlx5e: Add refcount to VXLAN structure Gal Pressman net/mlx5e: Fix possible deadlock of VXLAN lock Gal Pressman net/mlx5e: Fix features check of IPv6 traffic Eran Ben Elisha net/mlx5: Fix rate limit packet pacing naming and struct Yousuk Seung tcp: invalidate rate samples during SACK reneging Willem de Bruijn sock: free skb in skb_complete_tx_timestamp on error Grygorii Strashko net: phy: micrel: ksz9031: reconfigure autoneg after phy autoneg workaround Eric W. Biederman net: Fix double free and memory corruption in get_net_ns_by_id() Andrew Lunn net: fec: Allow reception of frames bigger than 1522 bytes Nikolay Aleksandrov net: bridge: fix early call to br_stp_change_bridge_id and plug newlink leaks Ido Schimmel ipv4: Fix use-after-free when flushing FIB tables Nikita V. Shirokov adding missing rcu_read_unlock in ipxip6_rcv Tonghao Zhang sctp: Replace use of sockets_allocated with specified macro. Tobias Jordan net: mvmdio: disable/unprepare clocks in EPROBE_DEFER case Mohamed Ghannam net: ipv4: fix for a race condition in raw_sendmsg Brian King tg3: Fix rx hang on MTU change with 5717/5719 Christoph Paasch tcp md5sig: Use skb's saddr when replying to an incoming segment Neal Cardwell tcp_bbr: record "full bw reached" decision in new full_bw_reached bit Avinash Repaka RDS: Check cmsg_len before dereferencing CMSG_DATA Michael S. Tsirkin ptr_ring: add barriers Shaohua Li net: reevalulate autoflowlabel setting after sysctl setting Sebastian Sjoholm net: qmi_wwan: add Sierra EM7565 1199:9091 Kevin Cernekee netlink: Add netns check on taps Kevin Cernekee net: igmp: Use correct source address on IGMPv3 reports Fugang Duan net: fec: unmap the xmit buffer that are not transferred by DMA Eric Dumazet ipv6: mcast: better catch silly mtu values Eric Dumazet ipv4: igmp: guard against silly MTU values Linus Torvalds kbuild: add '-fno-stack-check' to kernel build options Andy Lutomirski x86/mm/64: Fix reboot interaction with CR4.PCIDE Andy Lutomirski x86/mm: Enable CR4.PCIDE on supported systems Andy Lutomirski x86/mm: Add the 'nopcid' boot option to turn off PCID Andy Lutomirski x86/mm: