Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Greg Kroah-Hartman
On Thu, Oct 03, 2013 at 06:16:20PM -0600, Shuah Khan wrote:
> On 10/02/2013 10:04 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.0.99 release.
> >There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
> >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.0/stable-review/patch-3.0.99-rc1.gz
> >and the diffstat can be found below.
> >
> >thanks,
> >
> >greg k-h
> >
> 
> Patch testing: 3.0.99-rc1 patch applied with white-space warnings
> and 3.0.99-rc2 applied cleanly.
> 
> Tested 3.0.99-rc1 and 3.0.99-rc2
> Compile testing: 3.0.99-rc1 and 3.0.99-rc2 Passed
> Boot testing: 3.0.99-rc1 and 3.0.99-rc2 Passed
> dmesg regression testing: passed. dmesgs look good. No regressions
> compared to the previous dmesgs for this release. dmesg emerg, crit,
> alert, err are clean. No regressions in warn.

Thanks for testing both of these, sorry for the mess with -rc2.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Shuah Khan

On 10/02/2013 10:04 PM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 3.0.99 release.
There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
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.0/stable-review/patch-3.0.99-rc1.gz
and the diffstat can be found below.

thanks,

greg k-h



Patch testing: 3.0.99-rc1 patch applied with white-space warnings and 
3.0.99-rc2 applied cleanly.


Tested 3.0.99-rc1 and 3.0.99-rc2
Compile testing: 3.0.99-rc1 and 3.0.99-rc2 Passed
Boot testing: 3.0.99-rc1 and 3.0.99-rc2 Passed
dmesg regression testing: passed. dmesgs look good. No regressions 
compared to the previous dmesgs for this release. dmesg emerg, crit, 
alert, err are clean. No regressions in warn.


Test systems

Samsung Series 9 900X4C Intel Corei5 (3.4 and later)
HP ProBook 6475b AMD A10-4600M APU with Radeon(tm) HD Graphics
HP Compaq dc7700 SFF desktop: x86-64 Intel Core-i2 (cross-compile
testing)

Cross-compile tests results

alpha   defconfig   Passed
arm defconfig   Passed
arm64   defconfig   Not applicable
blackfin defconfig  Passed
c6x defconfig   Not applicable
mipsdefconfig   Passed
mipsel  defconfig   Passed
powerpc wii_defconfig   Passed
sh  defconfig   Passed
sparc   defconfig   Passed
tiletilegx_defconfig Passed

-- Shuah

--
Shuah Khan
Senior Linux Kernel Developer - Open Source Group
Samsung Research America(Silicon Valley)
shuah...@samsung.com | (970) 672-0658
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Guenter Roeck
On Thu, Oct 03, 2013 at 11:40:48AM -0700, Greg Kroah-Hartman wrote:
> On Wed, Oct 02, 2013 at 10:53:39PM -0700, Guenter Roeck wrote:
> > On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 3.0.99 release.
> > > There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
> > > 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.0/stable-review/patch-3.0.99-rc1.gz
> > > and the diffstat can be found below.
> > >
> > 
> > Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.
> > 
> > mm/built-in.o: In function `__put_compound_page':
> > slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
> > mm/built-in.o: In function `put_compound_page':
> > slab.c:(.text+0xaab0): undefined reference to `PageHuge'
> > mm/built-in.o: In function `__get_page_tail':
> > slab.c:(.text+0xb178): undefined reference to `PageHuge'
> > make: *** [.tmp_vmlinux1] Error 1
> > 
> > More tomorrow.
> 
> Should now be fixed, if not, please let me know.
> 
Yes, much better:
total: 98 pass: 71 skipped: 16 fail: 11
This matches the results from the previous release.

qemu tests also pass.

Details are at http://server.roeck-us.net:8010/builders, as usual.

Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Khalid Aziz

On 10/03/2013 01:15 PM, Christoph Biedl wrote:

Khalid Aziz wrote...


Better yet, just pull this patch from stable from now. I will redo
the patch and send another one for the next round.


FYI, after patching mm/swap.c accordingly, all the 3.0 and 3.4
configurations I use do build. Some boot tests will follow, I'll
follow up only if I see unusual behaviour.

 Christoph



Thanks for testing, Christoph. I will create a v2 of this patch with 
this change for the next round of stable kernels.


--
Khalid

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Christoph Biedl
Khalid Aziz wrote...

> Better yet, just pull this patch from stable from now. I will redo
> the patch and send another one for the next round.

FYI, after patching mm/swap.c accordingly, all the 3.0 and 3.4
configurations I use do build. Some boot tests will follow, I'll
follow up only if I see unusual behaviour.

Christoph
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Greg Kroah-Hartman
On Wed, Oct 02, 2013 at 10:53:39PM -0700, Guenter Roeck wrote:
> On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.0.99 release.
> > There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
> > 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.0/stable-review/patch-3.0.99-rc1.gz
> > and the diffstat can be found below.
> >
> 
> Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.
> 
> mm/built-in.o: In function `__put_compound_page':
> slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
> mm/built-in.o: In function `put_compound_page':
> slab.c:(.text+0xaab0): undefined reference to `PageHuge'
> mm/built-in.o: In function `__get_page_tail':
> slab.c:(.text+0xb178): undefined reference to `PageHuge'
> make: *** [.tmp_vmlinux1] Error 1
> 
> More tomorrow.

Should now be fixed, if not, please let me know.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Greg Kroah-Hartman
On Wed, Oct 02, 2013 at 09:04:25PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.0.99 release.
> There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
> 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.0/stable-review/patch-3.0.99-rc1.gz
> and the diffstat can be found below.

Due to build problems in -rc1, I've dropped one patch and now have
posted a -rc2 patch:

kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.0.99-rc2.gz

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Greg Kroah-Hartman
On Thu, Oct 03, 2013 at 09:12:47AM -0600, Khalid Aziz wrote:
> On 10/03/2013 08:56 AM, Khalid Aziz wrote:
> >
> > Greg, please apply the patch Christoph had included in his earlier post.
> >
> > Ben, this will apply to 3.2 as well.
> >
> 
> Better yet, just pull this patch from stable from now. I will redo the 
> patch and send another one for the next round.

Now removed from 3.0 and I'll drop it from 3.4 as well, thanks.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Guenter Roeck
On Thu, Oct 03, 2013 at 07:35:35AM -0600, Khalid Aziz wrote:
> On 10/03/2013 06:47 AM, Christoph Biedl wrote:
> >Guenter Roeck wrote...
> >
> >>On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:
> >>>This is the start of the stable review cycle for the 3.0.99 release.
> >
> >>Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.
> >>
> >>mm/built-in.o: In function `__put_compound_page':
> >>slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
> >>mm/built-in.o: In function `put_compound_page':
> >>slab.c:(.text+0xaab0): undefined reference to `PageHuge'
> >>mm/built-in.o: In function `__get_page_tail':
> >>slab.c:(.text+0xb178): undefined reference to `PageHuge'
> >>make: *** [.tmp_vmlinux1] Error 1
> >
> >This is obviously due to
> >
> >| [ 11/13] mm: fix aio performance regression for database caused by THP
> >
> >and happens if CONFIG_HUGETLB_PAGE is not set.
> >
> >Looking closer, upstream commit 7cb2ef56 included linux/hugetlb.h
> >while the backport for 3.0 just defines PageHuge. Reverting that like
> >in the patch below causes the build to complete, and the resulting
> >kernel shows no anomalies here.
> >
> >However did that backport, why was it done that way? Or did I miss an
> >important point?
> 
> Thanks for tracking this down. I had not tried a configuration with
> CONFIG_HUGETLB_PAGE not set. In my config, I was getting many
> multiple definition errors for bunch of other defines from
> linux/hugetlb.h. I will look at my config again but chances are I
> had something else screwed up in my build since you did not see
> those errors. Did you compile with CONFIG_HUGETLB_PAGE set after
> including linux/hugetlb.h? If you did, including linux/hugetlb.h
> instead of importing just the definition of PageHuge in mm/swap.c
> would be the right thing to do.
> 

For my part, what I do is to compile lots of standard configurations.
I don't look into details. If you are interested, go to
http://server.roeck-us.net:8010/builders, click on any of the many
failed builds for 3.0 or 3.4, then click on "stdio" on the build page.
You'll see the build log, which also lists the names of the failed
configurations.

An easy start might be x86_64:allnoconfig or i386:allnoconfig,
both of which fail.

Thanks,
Guenter

> --
> Khalid
> 
> >
> > Christoph
> >
> >--- a/mm/swap.c
> >+++ b/mm/swap.c
> >@@ -31,6 +31,7 @@
> >  #include 
> >  #include 
> >  #include 
> >+#include 
> >
> >  #include "internal.h"
> >
> >@@ -41,8 +42,6 @@
> >  static DEFINE_PER_CPU(struct pagevec, lru_rotate_pvecs);
> >  static DEFINE_PER_CPU(struct pagevec, lru_deactivate_pvecs);
> >
> >-int PageHuge(struct page *page);
> >-
> >  /*
> >   * This path almost never happens for VM activity - pages are normally
> >   * freed via pagevecs.  But it gets used by networking.
> >
> 
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Khalid Aziz

On 10/03/2013 08:56 AM, Khalid Aziz wrote:


Greg, please apply the patch Christoph had included in his earlier post.

Ben, this will apply to 3.2 as well.



Better yet, just pull this patch from stable from now. I will redo the 
patch and send another one for the next round.


Thanks,
Khalid

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Khalid Aziz

On 10/03/2013 08:41 AM, Christoph Biedl wrote:

Khalid Aziz wrote...


Thanks for tracking this down. I had not tried a configuration with
CONFIG_HUGETLB_PAGE not set. In my config, I was getting many
multiple definition errors for bunch of other defines from
linux/hugetlb.h. I will look at my config again but chances are I
had something else screwed up in my build since you did not see
those errors. Did you compile with CONFIG_HUGETLB_PAGE set after
including linux/hugetlb.h? If you did, including linux/hugetlb.h
instead of importing just the definition of PageHuge in mm/swap.c
would be the right thing to do.


Yes, one of my configurations has CONFIG_HUGETLB_PAGE, also
CONFIG_NUMA=y, and the kernel built. Could not test it, though.

There still might be other configuration settings that caused the
error messages you've seen. Manually picking both PageHuge definitions
from linux/hugetlb.h should be a safe alternative then, but that's
ugly.

 Christoph



Including linux/hugetlb.h is the right thing to do here. I cleaned up my 
build directories and started from scratch again. I tested with the old 
config where I had seen errors and I did not see errors again. I must 
have had something messed up in my old build directories.


Greg, please apply the patch Christoph had included in his earlier post.

Ben, this will apply to 3.2 as well.

Thanks,
Khalid
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Christoph Biedl
Khalid Aziz wrote...

> Thanks for tracking this down. I had not tried a configuration with
> CONFIG_HUGETLB_PAGE not set. In my config, I was getting many
> multiple definition errors for bunch of other defines from
> linux/hugetlb.h. I will look at my config again but chances are I
> had something else screwed up in my build since you did not see
> those errors. Did you compile with CONFIG_HUGETLB_PAGE set after
> including linux/hugetlb.h? If you did, including linux/hugetlb.h
> instead of importing just the definition of PageHuge in mm/swap.c
> would be the right thing to do.

Yes, one of my configurations has CONFIG_HUGETLB_PAGE, also
CONFIG_NUMA=y, and the kernel built. Could not test it, though.

There still might be other configuration settings that caused the
error messages you've seen. Manually picking both PageHuge definitions
from linux/hugetlb.h should be a safe alternative then, but that's
ugly.

Christoph
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Khalid Aziz

On 10/03/2013 06:47 AM, Christoph Biedl wrote:

Guenter Roeck wrote...


On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 3.0.99 release.



Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.

mm/built-in.o: In function `__put_compound_page':
slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
mm/built-in.o: In function `put_compound_page':
slab.c:(.text+0xaab0): undefined reference to `PageHuge'
mm/built-in.o: In function `__get_page_tail':
slab.c:(.text+0xb178): undefined reference to `PageHuge'
make: *** [.tmp_vmlinux1] Error 1


This is obviously due to

| [ 11/13] mm: fix aio performance regression for database caused by THP

and happens if CONFIG_HUGETLB_PAGE is not set.

Looking closer, upstream commit 7cb2ef56 included linux/hugetlb.h
while the backport for 3.0 just defines PageHuge. Reverting that like
in the patch below causes the build to complete, and the resulting
kernel shows no anomalies here.

However did that backport, why was it done that way? Or did I miss an
important point?


Thanks for tracking this down. I had not tried a configuration with 
CONFIG_HUGETLB_PAGE not set. In my config, I was getting many multiple 
definition errors for bunch of other defines from linux/hugetlb.h. I 
will look at my config again but chances are I had something else 
screwed up in my build since you did not see those errors. Did you 
compile with CONFIG_HUGETLB_PAGE set after including linux/hugetlb.h? If 
you did, including linux/hugetlb.h instead of importing just the 
definition of PageHuge in mm/swap.c would be the right thing to do.


--
Khalid



 Christoph

--- a/mm/swap.c
+++ b/mm/swap.c
@@ -31,6 +31,7 @@
  #include 
  #include 
  #include 
+#include 

  #include "internal.h"

@@ -41,8 +42,6 @@
  static DEFINE_PER_CPU(struct pagevec, lru_rotate_pvecs);
  static DEFINE_PER_CPU(struct pagevec, lru_deactivate_pvecs);

-int PageHuge(struct page *page);
-
  /*
   * This path almost never happens for VM activity - pages are normally
   * freed via pagevecs.  But it gets used by networking.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Guenter Roeck

On 10/03/2013 05:47 AM, Christoph Biedl wrote:

Guenter Roeck wrote...


On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 3.0.99 release.



Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.

mm/built-in.o: In function `__put_compound_page':
slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
mm/built-in.o: In function `put_compound_page':
slab.c:(.text+0xaab0): undefined reference to `PageHuge'
mm/built-in.o: In function `__get_page_tail':
slab.c:(.text+0xb178): undefined reference to `PageHuge'
make: *** [.tmp_vmlinux1] Error 1


This is obviously due to

| [ 11/13] mm: fix aio performance regression for database caused by THP

and happens if CONFIG_HUGETLB_PAGE is not set.



Thanks a lot for tracking this down.

Final build result is
total: 98 pass: 15 skipped: 16 fail: 67

for 3.0, which is obviously less than perfect.

All qemu tests failed as well, or rather the qemu images failed to build.

Guenter


Looking closer, upstream commit 7cb2ef56 included linux/hugetlb.h
while the backport for 3.0 just defines PageHuge. Reverting that like
in the patch below causes the build to complete, and the resulting
kernel shows no anomalies here.

However did that backport, why was it done that way? Or did I miss an
important point?

 Christoph

--- a/mm/swap.c
+++ b/mm/swap.c
@@ -31,6 +31,7 @@
  #include 
  #include 
  #include 
+#include 

  #include "internal.h"

@@ -41,8 +42,6 @@
  static DEFINE_PER_CPU(struct pagevec, lru_rotate_pvecs);
  static DEFINE_PER_CPU(struct pagevec, lru_deactivate_pvecs);

-int PageHuge(struct page *page);
-
  /*
   * This path almost never happens for VM activity - pages are normally
   * freed via pagevecs.  But it gets used by networking.





--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Christoph Biedl
Guenter Roeck wrote...

> On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.0.99 release.

> Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.
> 
> mm/built-in.o: In function `__put_compound_page':
> slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
> mm/built-in.o: In function `put_compound_page':
> slab.c:(.text+0xaab0): undefined reference to `PageHuge'
> mm/built-in.o: In function `__get_page_tail':
> slab.c:(.text+0xb178): undefined reference to `PageHuge'
> make: *** [.tmp_vmlinux1] Error 1

This is obviously due to

| [ 11/13] mm: fix aio performance regression for database caused by THP

and happens if CONFIG_HUGETLB_PAGE is not set.

Looking closer, upstream commit 7cb2ef56 included linux/hugetlb.h
while the backport for 3.0 just defines PageHuge. Reverting that like
in the patch below causes the build to complete, and the resulting
kernel shows no anomalies here.

However did that backport, why was it done that way? Or did I miss an
important point?

Christoph

--- a/mm/swap.c
+++ b/mm/swap.c
@@ -31,6 +31,7 @@
 #include 
 #include 
 #include 
+#include 

 #include "internal.h"

@@ -41,8 +42,6 @@
 static DEFINE_PER_CPU(struct pagevec, lru_rotate_pvecs);
 static DEFINE_PER_CPU(struct pagevec, lru_deactivate_pvecs);

-int PageHuge(struct page *page);
-
 /*
  * This path almost never happens for VM activity - pages are normally
  * freed via pagevecs.  But it gets used by networking.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Christoph Biedl
Guenter Roeck wrote...

 On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:
 This is the start of the stable review cycle for the 3.0.99 release.

 Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.
 
 mm/built-in.o: In function `__put_compound_page':
 slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
 mm/built-in.o: In function `put_compound_page':
 slab.c:(.text+0xaab0): undefined reference to `PageHuge'
 mm/built-in.o: In function `__get_page_tail':
 slab.c:(.text+0xb178): undefined reference to `PageHuge'
 make: *** [.tmp_vmlinux1] Error 1

This is obviously due to

| [ 11/13] mm: fix aio performance regression for database caused by THP

and happens if CONFIG_HUGETLB_PAGE is not set.

Looking closer, upstream commit 7cb2ef56 included linux/hugetlb.h
while the backport for 3.0 just defines PageHuge. Reverting that like
in the patch below causes the build to complete, and the resulting
kernel shows no anomalies here.

However did that backport, why was it done that way? Or did I miss an
important point?

Christoph

--- a/mm/swap.c
+++ b/mm/swap.c
@@ -31,6 +31,7 @@
 #include linux/backing-dev.h
 #include linux/memcontrol.h
 #include linux/gfp.h
+#include linux/hugetlb.h

 #include internal.h

@@ -41,8 +42,6 @@
 static DEFINE_PER_CPU(struct pagevec, lru_rotate_pvecs);
 static DEFINE_PER_CPU(struct pagevec, lru_deactivate_pvecs);

-int PageHuge(struct page *page);
-
 /*
  * This path almost never happens for VM activity - pages are normally
  * freed via pagevecs.  But it gets used by networking.

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Guenter Roeck

On 10/03/2013 05:47 AM, Christoph Biedl wrote:

Guenter Roeck wrote...


On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 3.0.99 release.



Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.

mm/built-in.o: In function `__put_compound_page':
slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
mm/built-in.o: In function `put_compound_page':
slab.c:(.text+0xaab0): undefined reference to `PageHuge'
mm/built-in.o: In function `__get_page_tail':
slab.c:(.text+0xb178): undefined reference to `PageHuge'
make: *** [.tmp_vmlinux1] Error 1


This is obviously due to

| [ 11/13] mm: fix aio performance regression for database caused by THP

and happens if CONFIG_HUGETLB_PAGE is not set.



Thanks a lot for tracking this down.

Final build result is
total: 98 pass: 15 skipped: 16 fail: 67

for 3.0, which is obviously less than perfect.

All qemu tests failed as well, or rather the qemu images failed to build.

Guenter


Looking closer, upstream commit 7cb2ef56 included linux/hugetlb.h
while the backport for 3.0 just defines PageHuge. Reverting that like
in the patch below causes the build to complete, and the resulting
kernel shows no anomalies here.

However did that backport, why was it done that way? Or did I miss an
important point?

 Christoph

--- a/mm/swap.c
+++ b/mm/swap.c
@@ -31,6 +31,7 @@
  #include linux/backing-dev.h
  #include linux/memcontrol.h
  #include linux/gfp.h
+#include linux/hugetlb.h

  #include internal.h

@@ -41,8 +42,6 @@
  static DEFINE_PER_CPU(struct pagevec, lru_rotate_pvecs);
  static DEFINE_PER_CPU(struct pagevec, lru_deactivate_pvecs);

-int PageHuge(struct page *page);
-
  /*
   * This path almost never happens for VM activity - pages are normally
   * freed via pagevecs.  But it gets used by networking.





--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Khalid Aziz

On 10/03/2013 06:47 AM, Christoph Biedl wrote:

Guenter Roeck wrote...


On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 3.0.99 release.



Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.

mm/built-in.o: In function `__put_compound_page':
slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
mm/built-in.o: In function `put_compound_page':
slab.c:(.text+0xaab0): undefined reference to `PageHuge'
mm/built-in.o: In function `__get_page_tail':
slab.c:(.text+0xb178): undefined reference to `PageHuge'
make: *** [.tmp_vmlinux1] Error 1


This is obviously due to

| [ 11/13] mm: fix aio performance regression for database caused by THP

and happens if CONFIG_HUGETLB_PAGE is not set.

Looking closer, upstream commit 7cb2ef56 included linux/hugetlb.h
while the backport for 3.0 just defines PageHuge. Reverting that like
in the patch below causes the build to complete, and the resulting
kernel shows no anomalies here.

However did that backport, why was it done that way? Or did I miss an
important point?


Thanks for tracking this down. I had not tried a configuration with 
CONFIG_HUGETLB_PAGE not set. In my config, I was getting many multiple 
definition errors for bunch of other defines from linux/hugetlb.h. I 
will look at my config again but chances are I had something else 
screwed up in my build since you did not see those errors. Did you 
compile with CONFIG_HUGETLB_PAGE set after including linux/hugetlb.h? If 
you did, including linux/hugetlb.h instead of importing just the 
definition of PageHuge in mm/swap.c would be the right thing to do.


--
Khalid



 Christoph

--- a/mm/swap.c
+++ b/mm/swap.c
@@ -31,6 +31,7 @@
  #include linux/backing-dev.h
  #include linux/memcontrol.h
  #include linux/gfp.h
+#include linux/hugetlb.h

  #include internal.h

@@ -41,8 +42,6 @@
  static DEFINE_PER_CPU(struct pagevec, lru_rotate_pvecs);
  static DEFINE_PER_CPU(struct pagevec, lru_deactivate_pvecs);

-int PageHuge(struct page *page);
-
  /*
   * This path almost never happens for VM activity - pages are normally
   * freed via pagevecs.  But it gets used by networking.



--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Christoph Biedl
Khalid Aziz wrote...

 Thanks for tracking this down. I had not tried a configuration with
 CONFIG_HUGETLB_PAGE not set. In my config, I was getting many
 multiple definition errors for bunch of other defines from
 linux/hugetlb.h. I will look at my config again but chances are I
 had something else screwed up in my build since you did not see
 those errors. Did you compile with CONFIG_HUGETLB_PAGE set after
 including linux/hugetlb.h? If you did, including linux/hugetlb.h
 instead of importing just the definition of PageHuge in mm/swap.c
 would be the right thing to do.

Yes, one of my configurations has CONFIG_HUGETLB_PAGE, also
CONFIG_NUMA=y, and the kernel built. Could not test it, though.

There still might be other configuration settings that caused the
error messages you've seen. Manually picking both PageHuge definitions
from linux/hugetlb.h should be a safe alternative then, but that's
ugly.

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Khalid Aziz

On 10/03/2013 08:41 AM, Christoph Biedl wrote:

Khalid Aziz wrote...


Thanks for tracking this down. I had not tried a configuration with
CONFIG_HUGETLB_PAGE not set. In my config, I was getting many
multiple definition errors for bunch of other defines from
linux/hugetlb.h. I will look at my config again but chances are I
had something else screwed up in my build since you did not see
those errors. Did you compile with CONFIG_HUGETLB_PAGE set after
including linux/hugetlb.h? If you did, including linux/hugetlb.h
instead of importing just the definition of PageHuge in mm/swap.c
would be the right thing to do.


Yes, one of my configurations has CONFIG_HUGETLB_PAGE, also
CONFIG_NUMA=y, and the kernel built. Could not test it, though.

There still might be other configuration settings that caused the
error messages you've seen. Manually picking both PageHuge definitions
from linux/hugetlb.h should be a safe alternative then, but that's
ugly.

 Christoph



Including linux/hugetlb.h is the right thing to do here. I cleaned up my 
build directories and started from scratch again. I tested with the old 
config where I had seen errors and I did not see errors again. I must 
have had something messed up in my old build directories.


Greg, please apply the patch Christoph had included in his earlier post.

Ben, this will apply to 3.2 as well.

Thanks,
Khalid
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Khalid Aziz

On 10/03/2013 08:56 AM, Khalid Aziz wrote:


Greg, please apply the patch Christoph had included in his earlier post.

Ben, this will apply to 3.2 as well.



Better yet, just pull this patch from stable from now. I will redo the 
patch and send another one for the next round.


Thanks,
Khalid

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Guenter Roeck
On Thu, Oct 03, 2013 at 07:35:35AM -0600, Khalid Aziz wrote:
 On 10/03/2013 06:47 AM, Christoph Biedl wrote:
 Guenter Roeck wrote...
 
 On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:
 This is the start of the stable review cycle for the 3.0.99 release.
 
 Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.
 
 mm/built-in.o: In function `__put_compound_page':
 slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
 mm/built-in.o: In function `put_compound_page':
 slab.c:(.text+0xaab0): undefined reference to `PageHuge'
 mm/built-in.o: In function `__get_page_tail':
 slab.c:(.text+0xb178): undefined reference to `PageHuge'
 make: *** [.tmp_vmlinux1] Error 1
 
 This is obviously due to
 
 | [ 11/13] mm: fix aio performance regression for database caused by THP
 
 and happens if CONFIG_HUGETLB_PAGE is not set.
 
 Looking closer, upstream commit 7cb2ef56 included linux/hugetlb.h
 while the backport for 3.0 just defines PageHuge. Reverting that like
 in the patch below causes the build to complete, and the resulting
 kernel shows no anomalies here.
 
 However did that backport, why was it done that way? Or did I miss an
 important point?
 
 Thanks for tracking this down. I had not tried a configuration with
 CONFIG_HUGETLB_PAGE not set. In my config, I was getting many
 multiple definition errors for bunch of other defines from
 linux/hugetlb.h. I will look at my config again but chances are I
 had something else screwed up in my build since you did not see
 those errors. Did you compile with CONFIG_HUGETLB_PAGE set after
 including linux/hugetlb.h? If you did, including linux/hugetlb.h
 instead of importing just the definition of PageHuge in mm/swap.c
 would be the right thing to do.
 

For my part, what I do is to compile lots of standard configurations.
I don't look into details. If you are interested, go to
http://server.roeck-us.net:8010/builders, click on any of the many
failed builds for 3.0 or 3.4, then click on stdio on the build page.
You'll see the build log, which also lists the names of the failed
configurations.

An easy start might be x86_64:allnoconfig or i386:allnoconfig,
both of which fail.

Thanks,
Guenter

 --
 Khalid
 
 
  Christoph
 
 --- a/mm/swap.c
 +++ b/mm/swap.c
 @@ -31,6 +31,7 @@
   #include linux/backing-dev.h
   #include linux/memcontrol.h
   #include linux/gfp.h
 +#include linux/hugetlb.h
 
   #include internal.h
 
 @@ -41,8 +42,6 @@
   static DEFINE_PER_CPU(struct pagevec, lru_rotate_pvecs);
   static DEFINE_PER_CPU(struct pagevec, lru_deactivate_pvecs);
 
 -int PageHuge(struct page *page);
 -
   /*
* This path almost never happens for VM activity - pages are normally
* freed via pagevecs.  But it gets used by networking.
 
 
 
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Greg Kroah-Hartman
On Thu, Oct 03, 2013 at 09:12:47AM -0600, Khalid Aziz wrote:
 On 10/03/2013 08:56 AM, Khalid Aziz wrote:
 
  Greg, please apply the patch Christoph had included in his earlier post.
 
  Ben, this will apply to 3.2 as well.
 
 
 Better yet, just pull this patch from stable from now. I will redo the 
 patch and send another one for the next round.

Now removed from 3.0 and I'll drop it from 3.4 as well, thanks.

greg k-h
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Greg Kroah-Hartman
On Wed, Oct 02, 2013 at 09:04:25PM -0700, Greg Kroah-Hartman wrote:
 This is the start of the stable review cycle for the 3.0.99 release.
 There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
 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.0/stable-review/patch-3.0.99-rc1.gz
 and the diffstat can be found below.

Due to build problems in -rc1, I've dropped one patch and now have
posted a -rc2 patch:

kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.0.99-rc2.gz

thanks,

greg k-h
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Greg Kroah-Hartman
On Wed, Oct 02, 2013 at 10:53:39PM -0700, Guenter Roeck wrote:
 On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:
  This is the start of the stable review cycle for the 3.0.99 release.
  There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
  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.0/stable-review/patch-3.0.99-rc1.gz
  and the diffstat can be found below.
 
 
 Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.
 
 mm/built-in.o: In function `__put_compound_page':
 slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
 mm/built-in.o: In function `put_compound_page':
 slab.c:(.text+0xaab0): undefined reference to `PageHuge'
 mm/built-in.o: In function `__get_page_tail':
 slab.c:(.text+0xb178): undefined reference to `PageHuge'
 make: *** [.tmp_vmlinux1] Error 1
 
 More tomorrow.

Should now be fixed, if not, please let me know.

thanks,

greg k-h
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Christoph Biedl
Khalid Aziz wrote...

 Better yet, just pull this patch from stable from now. I will redo
 the patch and send another one for the next round.

FYI, after patching mm/swap.c accordingly, all the 3.0 and 3.4
configurations I use do build. Some boot tests will follow, I'll
follow up only if I see unusual behaviour.

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Khalid Aziz

On 10/03/2013 01:15 PM, Christoph Biedl wrote:

Khalid Aziz wrote...


Better yet, just pull this patch from stable from now. I will redo
the patch and send another one for the next round.


FYI, after patching mm/swap.c accordingly, all the 3.0 and 3.4
configurations I use do build. Some boot tests will follow, I'll
follow up only if I see unusual behaviour.

 Christoph



Thanks for testing, Christoph. I will create a v2 of this patch with 
this change for the next round of stable kernels.


--
Khalid

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Guenter Roeck
On Thu, Oct 03, 2013 at 11:40:48AM -0700, Greg Kroah-Hartman wrote:
 On Wed, Oct 02, 2013 at 10:53:39PM -0700, Guenter Roeck wrote:
  On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:
   This is the start of the stable review cycle for the 3.0.99 release.
   There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
   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.0/stable-review/patch-3.0.99-rc1.gz
   and the diffstat can be found below.
  
  
  Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.
  
  mm/built-in.o: In function `__put_compound_page':
  slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
  mm/built-in.o: In function `put_compound_page':
  slab.c:(.text+0xaab0): undefined reference to `PageHuge'
  mm/built-in.o: In function `__get_page_tail':
  slab.c:(.text+0xb178): undefined reference to `PageHuge'
  make: *** [.tmp_vmlinux1] Error 1
  
  More tomorrow.
 
 Should now be fixed, if not, please let me know.
 
Yes, much better:
total: 98 pass: 71 skipped: 16 fail: 11
This matches the results from the previous release.

qemu tests also pass.

Details are at http://server.roeck-us.net:8010/builders, as usual.

Thanks,
Guenter
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Shuah Khan

On 10/02/2013 10:04 PM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 3.0.99 release.
There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
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.0/stable-review/patch-3.0.99-rc1.gz
and the diffstat can be found below.

thanks,

greg k-h



Patch testing: 3.0.99-rc1 patch applied with white-space warnings and 
3.0.99-rc2 applied cleanly.


Tested 3.0.99-rc1 and 3.0.99-rc2
Compile testing: 3.0.99-rc1 and 3.0.99-rc2 Passed
Boot testing: 3.0.99-rc1 and 3.0.99-rc2 Passed
dmesg regression testing: passed. dmesgs look good. No regressions 
compared to the previous dmesgs for this release. dmesg emerg, crit, 
alert, err are clean. No regressions in warn.


Test systems

Samsung Series 9 900X4C Intel Corei5 (3.4 and later)
HP ProBook 6475b AMD A10-4600M APU with Radeon(tm) HD Graphics
HP Compaq dc7700 SFF desktop: x86-64 Intel Core-i2 (cross-compile
testing)

Cross-compile tests results

alpha   defconfig   Passed
arm defconfig   Passed
arm64   defconfig   Not applicable
blackfin defconfig  Passed
c6x defconfig   Not applicable
mipsdefconfig   Passed
mipsel  defconfig   Passed
powerpc wii_defconfig   Passed
sh  defconfig   Passed
sparc   defconfig   Passed
tiletilegx_defconfig Passed

-- Shuah

--
Shuah Khan
Senior Linux Kernel Developer - Open Source Group
Samsung Research America(Silicon Valley)
shuah...@samsung.com | (970) 672-0658
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-03 Thread Greg Kroah-Hartman
On Thu, Oct 03, 2013 at 06:16:20PM -0600, Shuah Khan wrote:
 On 10/02/2013 10:04 PM, Greg Kroah-Hartman wrote:
 This is the start of the stable review cycle for the 3.0.99 release.
 There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
 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.0/stable-review/patch-3.0.99-rc1.gz
 and the diffstat can be found below.
 
 thanks,
 
 greg k-h
 
 
 Patch testing: 3.0.99-rc1 patch applied with white-space warnings
 and 3.0.99-rc2 applied cleanly.
 
 Tested 3.0.99-rc1 and 3.0.99-rc2
 Compile testing: 3.0.99-rc1 and 3.0.99-rc2 Passed
 Boot testing: 3.0.99-rc1 and 3.0.99-rc2 Passed
 dmesg regression testing: passed. dmesgs look good. No regressions
 compared to the previous dmesgs for this release. dmesg emerg, crit,
 alert, err are clean. No regressions in warn.

Thanks for testing both of these, sorry for the mess with -rc2.

greg k-h
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-02 Thread Guenter Roeck

On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 3.0.99 release.
There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
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.0/stable-review/patch-3.0.99-rc1.gz
and the diffstat can be found below.



Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.

mm/built-in.o: In function `__put_compound_page':
slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
mm/built-in.o: In function `put_compound_page':
slab.c:(.text+0xaab0): undefined reference to `PageHuge'
mm/built-in.o: In function `__get_page_tail':
slab.c:(.text+0xb178): undefined reference to `PageHuge'
make: *** [.tmp_vmlinux1] Error 1

More tomorrow.

Guenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[ 00/13] 3.0.99-stable review

2013-10-02 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.0.99 release.
There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
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.0/stable-review/patch-3.0.99-rc1.gz
and the diffstat can be found below.

thanks,

greg k-h

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman 
Linux 3.0.99-rc1

Eric Dumazet 
splice: fix racy pipe->buffers uses

Henrik Rydberg 
hwmon: (applesmc) Silence uninitialized warnings

Khalid Aziz 
mm: fix aio performance regression for database caused by THP

Henrik Rydberg 
hwmon: (applesmc) Check key count before proceeding

Jani Nikula 
drm/i915/dp: increase i2c-over-aux retry interval on AUX DEFER

Mikulas Patocka 
dm-snapshot: fix performance degradation due to small hash size

Mikulas Patocka 
dm snapshot: workaround for a false positive lockdep warning

Kurt Garloff 
usb/core/devio.c: Don't reject control message to endpoint with wrong 
direction bit

Florian Wolter 
xhci: Fix race between ep halt and URB cancellation

Mathias Nyman 
xhci: Fix oops happening after address device timeout

Malcolm Priestley 
staging: vt6656: [BUG] main_usb.c oops on device_close move flag earlier.

Josh Boyer 
x86, efi: Don't map Boot Services on i386

Masoud Sharbiani 
x86/reboot: Add quirk to make Dell C6100 use reboot=pci automatically


-

Diffstat:

 Makefile  |  4 +--
 arch/x86/kernel/reboot.c  | 16 ++
 arch/x86/platform/efi/efi.c   | 11 ---
 drivers/gpu/drm/i915/intel_dp.c   | 13 +++-
 drivers/hwmon/applesmc.c  | 19 ++--
 drivers/md/dm-snap-persistent.c   |  2 +-
 drivers/md/dm-snap.c  |  5 ++-
 drivers/staging/vt6656/main_usb.c |  3 +-
 drivers/usb/core/devio.c  | 16 ++
 drivers/usb/host/xhci-ring.c  | 14 +++--
 fs/splice.c   | 35 -
 include/linux/splice.h|  8 ++---
 kernel/relay.c|  5 +--
 kernel/trace/trace.c  |  6 ++--
 mm/swap.c | 65 ---
 net/core/skbuff.c |  3 +-
 16 files changed, 166 insertions(+), 59 deletions(-)


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[ 00/13] 3.0.99-stable review

2013-10-02 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.0.99 release.
There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
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.0/stable-review/patch-3.0.99-rc1.gz
and the diffstat can be found below.

thanks,

greg k-h

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman gre...@linuxfoundation.org
Linux 3.0.99-rc1

Eric Dumazet eduma...@google.com
splice: fix racy pipe-buffers uses

Henrik Rydberg rydb...@euromail.se
hwmon: (applesmc) Silence uninitialized warnings

Khalid Aziz khalid.a...@oracle.com
mm: fix aio performance regression for database caused by THP

Henrik Rydberg rydb...@euromail.se
hwmon: (applesmc) Check key count before proceeding

Jani Nikula jani.nik...@intel.com
drm/i915/dp: increase i2c-over-aux retry interval on AUX DEFER

Mikulas Patocka mpato...@redhat.com
dm-snapshot: fix performance degradation due to small hash size

Mikulas Patocka mpato...@redhat.com
dm snapshot: workaround for a false positive lockdep warning

Kurt Garloff k...@garloff.de
usb/core/devio.c: Don't reject control message to endpoint with wrong 
direction bit

Florian Wolter woll...@web.de
xhci: Fix race between ep halt and URB cancellation

Mathias Nyman mathias.ny...@linux.intel.com
xhci: Fix oops happening after address device timeout

Malcolm Priestley tvbox...@gmail.com
staging: vt6656: [BUG] main_usb.c oops on device_close move flag earlier.

Josh Boyer jwbo...@redhat.com
x86, efi: Don't map Boot Services on i386

Masoud Sharbiani msharbi...@twitter.com
x86/reboot: Add quirk to make Dell C6100 use reboot=pci automatically


-

Diffstat:

 Makefile  |  4 +--
 arch/x86/kernel/reboot.c  | 16 ++
 arch/x86/platform/efi/efi.c   | 11 ---
 drivers/gpu/drm/i915/intel_dp.c   | 13 +++-
 drivers/hwmon/applesmc.c  | 19 ++--
 drivers/md/dm-snap-persistent.c   |  2 +-
 drivers/md/dm-snap.c  |  5 ++-
 drivers/staging/vt6656/main_usb.c |  3 +-
 drivers/usb/core/devio.c  | 16 ++
 drivers/usb/host/xhci-ring.c  | 14 +++--
 fs/splice.c   | 35 -
 include/linux/splice.h|  8 ++---
 kernel/relay.c|  5 +--
 kernel/trace/trace.c  |  6 ++--
 mm/swap.c | 65 ---
 net/core/skbuff.c |  3 +-
 16 files changed, 166 insertions(+), 59 deletions(-)


--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: [ 00/13] 3.0.99-stable review

2013-10-02 Thread Guenter Roeck

On 10/02/2013 09:04 PM, Greg Kroah-Hartman wrote:

This is the start of the stable review cycle for the 3.0.99 release.
There are 13 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 Sat Oct  5 04:03:47 UTC 2013.
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.0/stable-review/patch-3.0.99-rc1.gz
and the diffstat can be found below.



Heads up: I am getting lots of build failures in 3.0 and 3.4 builds.

mm/built-in.o: In function `__put_compound_page':
slab.c:(.text+0xaa3c): undefined reference to `PageHuge'
mm/built-in.o: In function `put_compound_page':
slab.c:(.text+0xaab0): undefined reference to `PageHuge'
mm/built-in.o: In function `__get_page_tail':
slab.c:(.text+0xb178): undefined reference to `PageHuge'
make: *** [.tmp_vmlinux1] Error 1

More tomorrow.

Guenter

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/