Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-17 Thread Greg Kroah-Hartman 
On Mon, Apr 17, 2017 at 12:18:19PM -0600, Shuah Khan wrote:
> On 04/16/2017 04:48 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.18.49 release.
> > There are 145 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.
> > 
> > -
> > Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
> > rot on the side of the road?  Yes, it was, but unfortunately, there's a
> > few million or so devices out there in the wild that still rely on this
> > kernel.  Now, some of their manufacturers and SoC vendors might not be
> > keeping their kernels up to date very well, but some do actually care
> > about security and their users, so this release is for them.  If you
> > happen to have a vendor that does not care about their users, go
> > complain, as odds are, your device is very insecure right now...
> > 
> > Because of this strange situation, and thanks to some vendors backing
> > the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
> > releases every once in a while to keep it up to date and working well
> > based on what is happening in other more well-maintained stable kernels
> > (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
> > switch vendors, it's the only way they will learn...)  I don't know how
> > long I'll keep doing this, so if you care about 3.18, please contact me
> > to let me know the expected lifespan of your device.
> > 
> > And finally, due to the delay from the last 3.18-stable kernel release,
> > there is a large backlog of patches, this is about 1/2 of the pending
> > ones so far.  I'll be working on catching up to the rest of them over
> > the next few weeks, and then the updates should be smaller than this
> > one.
> > 
> > ok, back to your normal form-letter stable -rc release notice:
> > -
> > 
> > Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
> > 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/v3.x/stable-review/patch-3.18.49-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-3.18.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> > [1] Google's android-common-3.18 will be tracking these releases for
> > those of you caring about a working android kernel based on 3.18, I
> > recommend using this tree:
> > https://android.googlesource.com/kernel/common/+/android-3.18
> > 
> 
> Compiled and booted on my test system. I don't have old dmesg logs to
> compare. I removed 3.18 and history from my test system. I will keep
> 3.10.49 logs for the next release.

Ah, thanks for this.  Please don't feel like you have to test 3.18 on
your system if you don't want to, I know it's a very old kernel...

greg k-h

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-17 Thread Greg Kroah-Hartman 
On Mon, Apr 17, 2017 at 12:18:19PM -0600, Shuah Khan wrote:
> On 04/16/2017 04:48 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.18.49 release.
> > There are 145 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.
> > 
> > -
> > Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
> > rot on the side of the road?  Yes, it was, but unfortunately, there's a
> > few million or so devices out there in the wild that still rely on this
> > kernel.  Now, some of their manufacturers and SoC vendors might not be
> > keeping their kernels up to date very well, but some do actually care
> > about security and their users, so this release is for them.  If you
> > happen to have a vendor that does not care about their users, go
> > complain, as odds are, your device is very insecure right now...
> > 
> > Because of this strange situation, and thanks to some vendors backing
> > the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
> > releases every once in a while to keep it up to date and working well
> > based on what is happening in other more well-maintained stable kernels
> > (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
> > switch vendors, it's the only way they will learn...)  I don't know how
> > long I'll keep doing this, so if you care about 3.18, please contact me
> > to let me know the expected lifespan of your device.
> > 
> > And finally, due to the delay from the last 3.18-stable kernel release,
> > there is a large backlog of patches, this is about 1/2 of the pending
> > ones so far.  I'll be working on catching up to the rest of them over
> > the next few weeks, and then the updates should be smaller than this
> > one.
> > 
> > ok, back to your normal form-letter stable -rc release notice:
> > -
> > 
> > Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
> > 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/v3.x/stable-review/patch-3.18.49-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-3.18.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> > [1] Google's android-common-3.18 will be tracking these releases for
> > those of you caring about a working android kernel based on 3.18, I
> > recommend using this tree:
> > https://android.googlesource.com/kernel/common/+/android-3.18
> > 
> 
> Compiled and booted on my test system. I don't have old dmesg logs to
> compare. I removed 3.18 and history from my test system. I will keep
> 3.10.49 logs for the next release.

Ah, thanks for this.  Please don't feel like you have to test 3.18 on
your system if you don't want to, I know it's a very old kernel...

greg k-h

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-17 Thread Shuah Khan 
On 04/16/2017 04:48 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.49 release.
> There are 145 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.
> 
> -
> Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
> rot on the side of the road?  Yes, it was, but unfortunately, there's a
> few million or so devices out there in the wild that still rely on this
> kernel.  Now, some of their manufacturers and SoC vendors might not be
> keeping their kernels up to date very well, but some do actually care
> about security and their users, so this release is for them.  If you
> happen to have a vendor that does not care about their users, go
> complain, as odds are, your device is very insecure right now...
> 
> Because of this strange situation, and thanks to some vendors backing
> the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
> releases every once in a while to keep it up to date and working well
> based on what is happening in other more well-maintained stable kernels
> (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
> switch vendors, it's the only way they will learn...)  I don't know how
> long I'll keep doing this, so if you care about 3.18, please contact me
> to let me know the expected lifespan of your device.
> 
> And finally, due to the delay from the last 3.18-stable kernel release,
> there is a large backlog of patches, this is about 1/2 of the pending
> ones so far.  I'll be working on catching up to the rest of them over
> the next few weeks, and then the updates should be smaller than this
> one.
> 
> ok, back to your normal form-letter stable -rc release notice:
> -
> 
> Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
> 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/v3.x/stable-review/patch-3.18.49-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-3.18.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 
> [1] Google's android-common-3.18 will be tracking these releases for
> those of you caring about a working android kernel based on 3.18, I
> recommend using this tree:
>   https://android.googlesource.com/kernel/common/+/android-3.18
> 

Compiled and booted on my test system. I don't have old dmesg logs to
compare. I removed 3.18 and history from my test system. I will keep
3.10.49 logs for the next release.

thanks,
-- Shuah

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-17 Thread Shuah Khan 
On 04/16/2017 04:48 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.49 release.
> There are 145 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.
> 
> -
> Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
> rot on the side of the road?  Yes, it was, but unfortunately, there's a
> few million or so devices out there in the wild that still rely on this
> kernel.  Now, some of their manufacturers and SoC vendors might not be
> keeping their kernels up to date very well, but some do actually care
> about security and their users, so this release is for them.  If you
> happen to have a vendor that does not care about their users, go
> complain, as odds are, your device is very insecure right now...
> 
> Because of this strange situation, and thanks to some vendors backing
> the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
> releases every once in a while to keep it up to date and working well
> based on what is happening in other more well-maintained stable kernels
> (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
> switch vendors, it's the only way they will learn...)  I don't know how
> long I'll keep doing this, so if you care about 3.18, please contact me
> to let me know the expected lifespan of your device.
> 
> And finally, due to the delay from the last 3.18-stable kernel release,
> there is a large backlog of patches, this is about 1/2 of the pending
> ones so far.  I'll be working on catching up to the rest of them over
> the next few weeks, and then the updates should be smaller than this
> one.
> 
> ok, back to your normal form-letter stable -rc release notice:
> -
> 
> Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
> 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/v3.x/stable-review/patch-3.18.49-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-3.18.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 
> [1] Google's android-common-3.18 will be tracking these releases for
> those of you caring about a working android kernel based on 3.18, I
> recommend using this tree:
>   https://android.googlesource.com/kernel/common/+/android-3.18
> 

Compiled and booted on my test system. I don't have old dmesg logs to
compare. I removed 3.18 and history from my test system. I will keep
3.10.49 logs for the next release.

thanks,
-- Shuah

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-17 Thread Greg Kroah-Hartman 
On Mon, Apr 17, 2017 at 01:37:00PM +0530, Amit Pundir wrote:
> On 17 April 2017 at 12:26, Greg Kroah-Hartman
>  wrote:
> > On Sun, Apr 16, 2017 at 04:30:32PM -0700, Guenter Roeck wrote:
> >> On 04/16/2017 03:48 AM, Greg Kroah-Hartman wrote:
> >> > This is the start of the stable review cycle for the 3.18.49 release.
> >> > There are 145 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.
> >> >
> >> > -
> >> > Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
> >> > rot on the side of the road?  Yes, it was, but unfortunately, there's a
> >> > few million or so devices out there in the wild that still rely on this
> >> > kernel.  Now, some of their manufacturers and SoC vendors might not be
> >> > keeping their kernels up to date very well, but some do actually care
> >> > about security and their users, so this release is for them.  If you
> >> > happen to have a vendor that does not care about their users, go
> >> > complain, as odds are, your device is very insecure right now...
> >> >
> >> > Because of this strange situation, and thanks to some vendors backing
> >> > the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
> >> > releases every once in a while to keep it up to date and working well
> >> > based on what is happening in other more well-maintained stable kernels
> >> > (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
> >> > switch vendors, it's the only way they will learn...)  I don't know how
> >> > long I'll keep doing this, so if you care about 3.18, please contact me
> >> > to let me know the expected lifespan of your device.
> >> >
> >> > And finally, due to the delay from the last 3.18-stable kernel release,
> >> > there is a large backlog of patches, this is about 1/2 of the pending
> >> > ones so far.  I'll be working on catching up to the rest of them over
> >> > the next few weeks, and then the updates should be smaller than this
> >> > one.
> >> >
> >> > ok, back to your normal form-letter stable -rc release notice:
> >> > -
> >> >
> >> > Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
> >> > Anything received after that time might be too late.
> >> >
> >>
> >> Build results:
> >>   total: 140 pass: 139 fail: 1
> >> Failed builds:
> >>   parisc:allmodconfig
> >>
> >> Qemu test results:
> >>   total: 111 pass: 111 fail: 0
> >>
> >> Fixing the build failure requires commit 6c8afa88adce ("Input: gscps2 - fix
> >> MODULE_DEVICE_TABLE invocation").
> >
> > Ah, nice!  I'm pretty amazed that there was only one failure, thanks for
> > testing all of these and letting me know.  I've also queued up this last
> > patch for 3.18.
> 
> Can you please pick this one
> https://www.spinics.net/lists/stable/msg166162.html as well. It fixes
> ARCH=arm + CONFIG_SMP=n + CONFIG_ARM_PSCI=y builds.

It's in my long-pending queue for 3.18 patches, I'll catch it the next
release.  Give me a chance to catch up with everything (again, I have
well over 200+ patches left to dig through), before you start sending me
new 3.18-stable patches please :)

thanks,

greg k-h

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-17 Thread Greg Kroah-Hartman 
On Mon, Apr 17, 2017 at 01:37:00PM +0530, Amit Pundir wrote:
> On 17 April 2017 at 12:26, Greg Kroah-Hartman
>  wrote:
> > On Sun, Apr 16, 2017 at 04:30:32PM -0700, Guenter Roeck wrote:
> >> On 04/16/2017 03:48 AM, Greg Kroah-Hartman wrote:
> >> > This is the start of the stable review cycle for the 3.18.49 release.
> >> > There are 145 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.
> >> >
> >> > -
> >> > Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
> >> > rot on the side of the road?  Yes, it was, but unfortunately, there's a
> >> > few million or so devices out there in the wild that still rely on this
> >> > kernel.  Now, some of their manufacturers and SoC vendors might not be
> >> > keeping their kernels up to date very well, but some do actually care
> >> > about security and their users, so this release is for them.  If you
> >> > happen to have a vendor that does not care about their users, go
> >> > complain, as odds are, your device is very insecure right now...
> >> >
> >> > Because of this strange situation, and thanks to some vendors backing
> >> > the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
> >> > releases every once in a while to keep it up to date and working well
> >> > based on what is happening in other more well-maintained stable kernels
> >> > (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
> >> > switch vendors, it's the only way they will learn...)  I don't know how
> >> > long I'll keep doing this, so if you care about 3.18, please contact me
> >> > to let me know the expected lifespan of your device.
> >> >
> >> > And finally, due to the delay from the last 3.18-stable kernel release,
> >> > there is a large backlog of patches, this is about 1/2 of the pending
> >> > ones so far.  I'll be working on catching up to the rest of them over
> >> > the next few weeks, and then the updates should be smaller than this
> >> > one.
> >> >
> >> > ok, back to your normal form-letter stable -rc release notice:
> >> > -
> >> >
> >> > Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
> >> > Anything received after that time might be too late.
> >> >
> >>
> >> Build results:
> >>   total: 140 pass: 139 fail: 1
> >> Failed builds:
> >>   parisc:allmodconfig
> >>
> >> Qemu test results:
> >>   total: 111 pass: 111 fail: 0
> >>
> >> Fixing the build failure requires commit 6c8afa88adce ("Input: gscps2 - fix
> >> MODULE_DEVICE_TABLE invocation").
> >
> > Ah, nice!  I'm pretty amazed that there was only one failure, thanks for
> > testing all of these and letting me know.  I've also queued up this last
> > patch for 3.18.
> 
> Can you please pick this one
> https://www.spinics.net/lists/stable/msg166162.html as well. It fixes
> ARCH=arm + CONFIG_SMP=n + CONFIG_ARM_PSCI=y builds.

It's in my long-pending queue for 3.18 patches, I'll catch it the next
release.  Give me a chance to catch up with everything (again, I have
well over 200+ patches left to dig through), before you start sending me
new 3.18-stable patches please :)

thanks,

greg k-h

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-17 Thread Amit Pundir 
On 17 April 2017 at 12:26, Greg Kroah-Hartman
 wrote:
> On Sun, Apr 16, 2017 at 04:30:32PM -0700, Guenter Roeck wrote:
>> On 04/16/2017 03:48 AM, Greg Kroah-Hartman wrote:
>> > This is the start of the stable review cycle for the 3.18.49 release.
>> > There are 145 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.
>> >
>> > -
>> > Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
>> > rot on the side of the road?  Yes, it was, but unfortunately, there's a
>> > few million or so devices out there in the wild that still rely on this
>> > kernel.  Now, some of their manufacturers and SoC vendors might not be
>> > keeping their kernels up to date very well, but some do actually care
>> > about security and their users, so this release is for them.  If you
>> > happen to have a vendor that does not care about their users, go
>> > complain, as odds are, your device is very insecure right now...
>> >
>> > Because of this strange situation, and thanks to some vendors backing
>> > the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
>> > releases every once in a while to keep it up to date and working well
>> > based on what is happening in other more well-maintained stable kernels
>> > (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
>> > switch vendors, it's the only way they will learn...)  I don't know how
>> > long I'll keep doing this, so if you care about 3.18, please contact me
>> > to let me know the expected lifespan of your device.
>> >
>> > And finally, due to the delay from the last 3.18-stable kernel release,
>> > there is a large backlog of patches, this is about 1/2 of the pending
>> > ones so far.  I'll be working on catching up to the rest of them over
>> > the next few weeks, and then the updates should be smaller than this
>> > one.
>> >
>> > ok, back to your normal form-letter stable -rc release notice:
>> > -
>> >
>> > Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
>> > Anything received after that time might be too late.
>> >
>>
>> Build results:
>>   total: 140 pass: 139 fail: 1
>> Failed builds:
>>   parisc:allmodconfig
>>
>> Qemu test results:
>>   total: 111 pass: 111 fail: 0
>>
>> Fixing the build failure requires commit 6c8afa88adce ("Input: gscps2 - fix
>> MODULE_DEVICE_TABLE invocation").
>
> Ah, nice!  I'm pretty amazed that there was only one failure, thanks for
> testing all of these and letting me know.  I've also queued up this last
> patch for 3.18.

Can you please pick this one
https://www.spinics.net/lists/stable/msg166162.html as well. It fixes
ARCH=arm + CONFIG_SMP=n + CONFIG_ARM_PSCI=y builds.

Regards,
Amit Pundir

>
> thanks,
>
> greg k-h

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-17 Thread Amit Pundir 
On 17 April 2017 at 12:26, Greg Kroah-Hartman
 wrote:
> On Sun, Apr 16, 2017 at 04:30:32PM -0700, Guenter Roeck wrote:
>> On 04/16/2017 03:48 AM, Greg Kroah-Hartman wrote:
>> > This is the start of the stable review cycle for the 3.18.49 release.
>> > There are 145 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.
>> >
>> > -
>> > Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
>> > rot on the side of the road?  Yes, it was, but unfortunately, there's a
>> > few million or so devices out there in the wild that still rely on this
>> > kernel.  Now, some of their manufacturers and SoC vendors might not be
>> > keeping their kernels up to date very well, but some do actually care
>> > about security and their users, so this release is for them.  If you
>> > happen to have a vendor that does not care about their users, go
>> > complain, as odds are, your device is very insecure right now...
>> >
>> > Because of this strange situation, and thanks to some vendors backing
>> > the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
>> > releases every once in a while to keep it up to date and working well
>> > based on what is happening in other more well-maintained stable kernels
>> > (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
>> > switch vendors, it's the only way they will learn...)  I don't know how
>> > long I'll keep doing this, so if you care about 3.18, please contact me
>> > to let me know the expected lifespan of your device.
>> >
>> > And finally, due to the delay from the last 3.18-stable kernel release,
>> > there is a large backlog of patches, this is about 1/2 of the pending
>> > ones so far.  I'll be working on catching up to the rest of them over
>> > the next few weeks, and then the updates should be smaller than this
>> > one.
>> >
>> > ok, back to your normal form-letter stable -rc release notice:
>> > -
>> >
>> > Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
>> > Anything received after that time might be too late.
>> >
>>
>> Build results:
>>   total: 140 pass: 139 fail: 1
>> Failed builds:
>>   parisc:allmodconfig
>>
>> Qemu test results:
>>   total: 111 pass: 111 fail: 0
>>
>> Fixing the build failure requires commit 6c8afa88adce ("Input: gscps2 - fix
>> MODULE_DEVICE_TABLE invocation").
>
> Ah, nice!  I'm pretty amazed that there was only one failure, thanks for
> testing all of these and letting me know.  I've also queued up this last
> patch for 3.18.

Can you please pick this one
https://www.spinics.net/lists/stable/msg166162.html as well. It fixes
ARCH=arm + CONFIG_SMP=n + CONFIG_ARM_PSCI=y builds.

Regards,
Amit Pundir

>
> thanks,
>
> greg k-h

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-17 Thread Greg Kroah-Hartman 
On Sun, Apr 16, 2017 at 04:30:32PM -0700, Guenter Roeck wrote:
> On 04/16/2017 03:48 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.18.49 release.
> > There are 145 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.
> > 
> > -
> > Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
> > rot on the side of the road?  Yes, it was, but unfortunately, there's a
> > few million or so devices out there in the wild that still rely on this
> > kernel.  Now, some of their manufacturers and SoC vendors might not be
> > keeping their kernels up to date very well, but some do actually care
> > about security and their users, so this release is for them.  If you
> > happen to have a vendor that does not care about their users, go
> > complain, as odds are, your device is very insecure right now...
> > 
> > Because of this strange situation, and thanks to some vendors backing
> > the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
> > releases every once in a while to keep it up to date and working well
> > based on what is happening in other more well-maintained stable kernels
> > (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
> > switch vendors, it's the only way they will learn...)  I don't know how
> > long I'll keep doing this, so if you care about 3.18, please contact me
> > to let me know the expected lifespan of your device.
> > 
> > And finally, due to the delay from the last 3.18-stable kernel release,
> > there is a large backlog of patches, this is about 1/2 of the pending
> > ones so far.  I'll be working on catching up to the rest of them over
> > the next few weeks, and then the updates should be smaller than this
> > one.
> > 
> > ok, back to your normal form-letter stable -rc release notice:
> > -
> > 
> > Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
> > Anything received after that time might be too late.
> > 
> 
> Build results:
>   total: 140 pass: 139 fail: 1
> Failed builds:
>   parisc:allmodconfig
> 
> Qemu test results:
>   total: 111 pass: 111 fail: 0
> 
> Fixing the build failure requires commit 6c8afa88adce ("Input: gscps2 - fix
> MODULE_DEVICE_TABLE invocation").

Ah, nice!  I'm pretty amazed that there was only one failure, thanks for
testing all of these and letting me know.  I've also queued up this last
patch for 3.18.

thanks,

greg k-h

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-17 Thread Greg Kroah-Hartman 
On Sun, Apr 16, 2017 at 04:30:32PM -0700, Guenter Roeck wrote:
> On 04/16/2017 03:48 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.18.49 release.
> > There are 145 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.
> > 
> > -
> > Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
> > rot on the side of the road?  Yes, it was, but unfortunately, there's a
> > few million or so devices out there in the wild that still rely on this
> > kernel.  Now, some of their manufacturers and SoC vendors might not be
> > keeping their kernels up to date very well, but some do actually care
> > about security and their users, so this release is for them.  If you
> > happen to have a vendor that does not care about their users, go
> > complain, as odds are, your device is very insecure right now...
> > 
> > Because of this strange situation, and thanks to some vendors backing
> > the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
> > releases every once in a while to keep it up to date and working well
> > based on what is happening in other more well-maintained stable kernels
> > (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
> > switch vendors, it's the only way they will learn...)  I don't know how
> > long I'll keep doing this, so if you care about 3.18, please contact me
> > to let me know the expected lifespan of your device.
> > 
> > And finally, due to the delay from the last 3.18-stable kernel release,
> > there is a large backlog of patches, this is about 1/2 of the pending
> > ones so far.  I'll be working on catching up to the rest of them over
> > the next few weeks, and then the updates should be smaller than this
> > one.
> > 
> > ok, back to your normal form-letter stable -rc release notice:
> > -
> > 
> > Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
> > Anything received after that time might be too late.
> > 
> 
> Build results:
>   total: 140 pass: 139 fail: 1
> Failed builds:
>   parisc:allmodconfig
> 
> Qemu test results:
>   total: 111 pass: 111 fail: 0
> 
> Fixing the build failure requires commit 6c8afa88adce ("Input: gscps2 - fix
> MODULE_DEVICE_TABLE invocation").

Ah, nice!  I'm pretty amazed that there was only one failure, thanks for
testing all of these and letting me know.  I've also queued up this last
patch for 3.18.

thanks,

greg k-h

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-16 Thread Guenter Roeck 

On 04/16/2017 03:48 AM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 3.18.49 release.
There are 145 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.

-
Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
rot on the side of the road?  Yes, it was, but unfortunately, there's a
few million or so devices out there in the wild that still rely on this
kernel.  Now, some of their manufacturers and SoC vendors might not be
keeping their kernels up to date very well, but some do actually care
about security and their users, so this release is for them.  If you
happen to have a vendor that does not care about their users, go
complain, as odds are, your device is very insecure right now...

Because of this strange situation, and thanks to some vendors backing
the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
releases every once in a while to keep it up to date and working well
based on what is happening in other more well-maintained stable kernels
(hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
switch vendors, it's the only way they will learn...)  I don't know how
long I'll keep doing this, so if you care about 3.18, please contact me
to let me know the expected lifespan of your device.

And finally, due to the delay from the last 3.18-stable kernel release,
there is a large backlog of patches, this is about 1/2 of the pending
ones so far.  I'll be working on catching up to the rest of them over
the next few weeks, and then the updates should be smaller than this
one.

ok, back to your normal form-letter stable -rc release notice:
-

Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
Anything received after that time might be too late.



Build results:
total: 140 pass: 139 fail: 1
Failed builds:
parisc:allmodconfig

Qemu test results:
total: 111 pass: 111 fail: 0

Fixing the build failure requires commit 6c8afa88adce ("Input: gscps2 - fix
MODULE_DEVICE_TABLE invocation").

Details are available at http://kerneltests.org/builders.

Guenter

Re: [PATCH 3.18 000/145] 3.18.49-stable review

2017-04-16 Thread Guenter Roeck 

On 04/16/2017 03:48 AM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 3.18.49 release.
There are 145 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.

-
Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
rot on the side of the road?  Yes, it was, but unfortunately, there's a
few million or so devices out there in the wild that still rely on this
kernel.  Now, some of their manufacturers and SoC vendors might not be
keeping their kernels up to date very well, but some do actually care
about security and their users, so this release is for them.  If you
happen to have a vendor that does not care about their users, go
complain, as odds are, your device is very insecure right now...

Because of this strange situation, and thanks to some vendors backing
the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
releases every once in a while to keep it up to date and working well
based on what is happening in other more well-maintained stable kernels
(hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
switch vendors, it's the only way they will learn...)  I don't know how
long I'll keep doing this, so if you care about 3.18, please contact me
to let me know the expected lifespan of your device.

And finally, due to the delay from the last 3.18-stable kernel release,
there is a large backlog of patches, this is about 1/2 of the pending
ones so far.  I'll be working on catching up to the rest of them over
the next few weeks, and then the updates should be smaller than this
one.

ok, back to your normal form-letter stable -rc release notice:
-

Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
Anything received after that time might be too late.



Build results:
total: 140 pass: 139 fail: 1
Failed builds:
parisc:allmodconfig

Qemu test results:
total: 111 pass: 111 fail: 0

Fixing the build failure requires commit 6c8afa88adce ("Input: gscps2 - fix
MODULE_DEVICE_TABLE invocation").

Details are available at http://kerneltests.org/builders.

Guenter

[PATCH 3.18 000/145] 3.18.49-stable review

2017-04-16 Thread Greg Kroah-Hartman 
This is the start of the stable review cycle for the 3.18.49 release.
There are 145 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.

-
Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
rot on the side of the road?  Yes, it was, but unfortunately, there's a
few million or so devices out there in the wild that still rely on this
kernel.  Now, some of their manufacturers and SoC vendors might not be
keeping their kernels up to date very well, but some do actually care
about security and their users, so this release is for them.  If you
happen to have a vendor that does not care about their users, go
complain, as odds are, your device is very insecure right now...

Because of this strange situation, and thanks to some vendors backing
the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
releases every once in a while to keep it up to date and working well
based on what is happening in other more well-maintained stable kernels
(hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
switch vendors, it's the only way they will learn...)  I don't know how
long I'll keep doing this, so if you care about 3.18, please contact me
to let me know the expected lifespan of your device.

And finally, due to the delay from the last 3.18-stable kernel release,
there is a large backlog of patches, this is about 1/2 of the pending
ones so far.  I'll be working on catching up to the rest of them over
the next few weeks, and then the updates should be smaller than this
one.

ok, back to your normal form-letter stable -rc release notice:
-

Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
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/v3.x/stable-review/patch-3.18.49-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-3.18.y
and the diffstat can be found below.

thanks,

greg k-h

[1] Google's android-common-3.18 will be tracking these releases for
those of you caring about a working android kernel based on 3.18, I
recommend using this tree:
https://android.googlesource.com/kernel/common/+/android-3.18

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman 
Linux 3.18.49-rc1

Hannes Frederic Sowa 
dccp: fix memory leak during tear-down of unsuccessful connection request

Jon Maxwell 
dccp/tcp: fix routing redirect race

Dmitry V. Levin 
uapi: fix linux/packet_diag.h userspace compilation error

Eric Dumazet 
net: fix socket refcounting in skb_complete_tx_timestamp()

Eric Dumazet 
net: fix socket refcounting in skb_complete_wifi_ack()

Eric Dumazet 
tcp: fix various issues for sockets morphing to listen state

Ilya Dryomov 
libceph: don't set weight to IN when OSD is destroyed

Ravi Bangoria 
powerpc: Emulation support for load/store instructions on LE

Ralf Baechle 
MIPS: DEC: Avoid la pseudo-instruction in delay slots

Arnd Bergmann 
MIPS: ip22: Fix ip28 build for modern gcc

Arnd Bergmann 
MIPS: ip27: Disable qlge driver in defconfig

Alan Stern 
USB: fix linked-list corruption in rh_call_control()

Guenter Roeck 
usb: hub: Fix crash after failure to read BOS descriptor

Johan Hovold 
USB: wusbcore: fix NULL-deref at probe

Johan Hovold 
USB: idmouse: fix NULL-deref at probe

Johan Hovold 
USB: lvtest: fix NULL-deref at probe

Johan Hovold 
USB: uss720: fix NULL-deref at probe

Samuel Thibault 
usb-core: Add LINEAR_FRAME_INTR_BINTERVAL USB quirk

Roger Quadros 
usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's wBytesPerInterval

Bjørn Mork 
USB: serial: qcserial: add Dell DW5811e

Janosch Frank 
KVM: s390: Fix guest migration for huge guests resulting in panic

Heiko Carstens 
s390: use correct input data address for setup_randomness

Heiko Carstens 
s390: make setup_randomness work

Martin Schwidefsky 
s390: TASK_SIZE for kernel threads

Julian Wiedmann 
s390/qdio: clear DSCI prior to scanning multiple input queues

Wang, Rui Y 
crypto: ghash-clmulni - Fix load failure

Jiri Slaby 
crypto: algif_hash - avoid zero-sized array

Wang, Rui Y

[PATCH 3.18 000/145] 3.18.49-stable review

2017-04-16 Thread Greg Kroah-Hartman 
This is the start of the stable review cycle for the 3.18.49 release.
There are 145 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.

-
Wait, what?  3.18?  Wasn't that kernel dead and forgotten and left to
rot on the side of the road?  Yes, it was, but unfortunately, there's a
few million or so devices out there in the wild that still rely on this
kernel.  Now, some of their manufacturers and SoC vendors might not be
keeping their kernels up to date very well, but some do actually care
about security and their users, so this release is for them.  If you
happen to have a vendor that does not care about their users, go
complain, as odds are, your device is very insecure right now...

Because of this strange situation, and thanks to some vendors backing
the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing
releases every once in a while to keep it up to date and working well
based on what is happening in other more well-maintained stable kernels
(hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so,
switch vendors, it's the only way they will learn...)  I don't know how
long I'll keep doing this, so if you care about 3.18, please contact me
to let me know the expected lifespan of your device.

And finally, due to the delay from the last 3.18-stable kernel release,
there is a large backlog of patches, this is about 1/2 of the pending
ones so far.  I'll be working on catching up to the rest of them over
the next few weeks, and then the updates should be smaller than this
one.

ok, back to your normal form-letter stable -rc release notice:
-

Responses should be made by Tue Apr 18 08:01:19 UTC 2017.
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/v3.x/stable-review/patch-3.18.49-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-3.18.y
and the diffstat can be found below.

thanks,

greg k-h

[1] Google's android-common-3.18 will be tracking these releases for
those of you caring about a working android kernel based on 3.18, I
recommend using this tree:
https://android.googlesource.com/kernel/common/+/android-3.18

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman 
Linux 3.18.49-rc1

Hannes Frederic Sowa 
dccp: fix memory leak during tear-down of unsuccessful connection request

Jon Maxwell 
dccp/tcp: fix routing redirect race

Dmitry V. Levin 
uapi: fix linux/packet_diag.h userspace compilation error

Eric Dumazet 
net: fix socket refcounting in skb_complete_tx_timestamp()

Eric Dumazet 
net: fix socket refcounting in skb_complete_wifi_ack()

Eric Dumazet 
tcp: fix various issues for sockets morphing to listen state

Ilya Dryomov 
libceph: don't set weight to IN when OSD is destroyed

Ravi Bangoria 
powerpc: Emulation support for load/store instructions on LE

Ralf Baechle 
MIPS: DEC: Avoid la pseudo-instruction in delay slots

Arnd Bergmann 
MIPS: ip22: Fix ip28 build for modern gcc

Arnd Bergmann 
MIPS: ip27: Disable qlge driver in defconfig

Alan Stern 
USB: fix linked-list corruption in rh_call_control()

Guenter Roeck 
usb: hub: Fix crash after failure to read BOS descriptor

Johan Hovold 
USB: wusbcore: fix NULL-deref at probe

Johan Hovold 
USB: idmouse: fix NULL-deref at probe

Johan Hovold 
USB: lvtest: fix NULL-deref at probe

Johan Hovold 
USB: uss720: fix NULL-deref at probe

Samuel Thibault 
usb-core: Add LINEAR_FRAME_INTR_BINTERVAL USB quirk

Roger Quadros 
usb: gadget: f_uvc: Fix SuperSpeed companion descriptor's wBytesPerInterval

Bjørn Mork 
USB: serial: qcserial: add Dell DW5811e

Janosch Frank 
KVM: s390: Fix guest migration for huge guests resulting in panic

Heiko Carstens 
s390: use correct input data address for setup_randomness

Heiko Carstens 
s390: make setup_randomness work

Martin Schwidefsky 
s390: TASK_SIZE for kernel threads

Julian Wiedmann 
s390/qdio: clear DSCI prior to scanning multiple input queues

Wang, Rui Y 
crypto: ghash-clmulni - Fix load failure

Jiri Slaby 
crypto: algif_hash - avoid zero-sized array

Wang, Rui Y 
crypto: mcryptd - Fix load failure

Wang, Rui Y 
crypto: cryptd - Assign statesize properly

Peter Zijlstra 
futex: Add missing error handling to FUTEX_REQUEUE_PI

Peter Zijlstra 
futex: Fix potential use-after-free in FUTEX_REQUEUE_PI

Jack Morgenstein 
net/mlx4_core: Fix when to save some qp context flags for dynamic VST to 
VGT transitions

Jack Morgenstein 
net/mlx4_core: Fix racy CQ (Completion Queue) free

Eugenia Emantayev 
net/mlx4_en: Fix bad WQE issue

Guenter Roeck 
usb: hub: Wait for connection to be reestablished after port reset

Andrey Konovalov 
net/packet: fix