Re: [PATCH 3.18 00/21] 3.18.113-stable review
On 06/19/2018 05:36 PM, Kevin Hilman wrote: Guenter Roeck writes: On Wed, Jun 13, 2018 at 05:09:11PM -0700, Kevin Hilman wrote: Greg Kroah-Hartman writes: On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote: stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 offline, 5 conflicts (v3.18.112-22-gb0582263e3c9) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ Tree: stable-rc Branch: linux-3.18.y Git Describe: v3.18.112-22-gb0582263e3c9 Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 24 unique boards, 12 SoC families, 13 builds out of 183 [...] That is a lot of new failures, did the whole lab fail, or is this really a problem in v3.18.112 here? Whole lab failure (more precisely, lab operator failure) ;) gak, I updated the rootfs images to the latest buildroot, which forced me to upgrade the kernel headers used to build the rootfs from v3.10 to v4.4. So I guess it's no surprise that every single board panic'd as soon as it hit userspace. I build my root file systems with buildroot, and had a similar problem. My fix was to patch buildroot to let me use older linux headers. Could you share the patch? Try g...@github.com:groeck/buildroot.git branch local-2018.05. Guenter
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On 06/19/2018 05:36 PM, Kevin Hilman wrote: Guenter Roeck writes: On Wed, Jun 13, 2018 at 05:09:11PM -0700, Kevin Hilman wrote: Greg Kroah-Hartman writes: On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote: stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 offline, 5 conflicts (v3.18.112-22-gb0582263e3c9) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ Tree: stable-rc Branch: linux-3.18.y Git Describe: v3.18.112-22-gb0582263e3c9 Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6 Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Tested: 24 unique boards, 12 SoC families, 13 builds out of 183 [...] That is a lot of new failures, did the whole lab fail, or is this really a problem in v3.18.112 here? Whole lab failure (more precisely, lab operator failure) ;) gak, I updated the rootfs images to the latest buildroot, which forced me to upgrade the kernel headers used to build the rootfs from v3.10 to v4.4. So I guess it's no surprise that every single board panic'd as soon as it hit userspace. I build my root file systems with buildroot, and had a similar problem. My fix was to patch buildroot to let me use older linux headers. Could you share the patch? Try g...@github.com:groeck/buildroot.git branch local-2018.05. Guenter
Re: [PATCH 3.18 00/21] 3.18.113-stable review
Guenter Roeck writes: > On Wed, Jun 13, 2018 at 05:09:11PM -0700, Kevin Hilman wrote: >> Greg Kroah-Hartman writes: >> >> > On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote: >> >> stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 >> >> offline, 5 conflicts (v3.18.112-22-gb0582263e3c9) >> >> >> >> Full Boot Summary: >> >> https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ >> >> Full Build Summary: >> >> https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ >> >> >> >> Tree: stable-rc >> >> Branch: linux-3.18.y >> >> Git Describe: v3.18.112-22-gb0582263e3c9 >> >> Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6 >> >> Git URL: >> >> http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> >> Tested: 24 unique boards, 12 SoC families, 13 builds out of 183 >> >> [...] >> >> > >> > That is a lot of new failures, did the whole lab fail, or is this really >> > a problem in v3.18.112 here? >> >> Whole lab failure (more precisely, lab operator failure) ;) >> >> gak, I updated the rootfs images to the latest buildroot, which forced >> me to upgrade the kernel headers used to build the rootfs from v3.10 to >> v4.4. So I guess it's no surprise that every single board panic'd as >> soon as it hit userspace. >> > I build my root file systems with buildroot, and had a similar problem. My fix > was to patch buildroot to let me use older linux headers. Could you share the patch? I was lazy and just rolled back the buildroot release. Thanks, Kevin
Re: [PATCH 3.18 00/21] 3.18.113-stable review
Guenter Roeck writes: > On Wed, Jun 13, 2018 at 05:09:11PM -0700, Kevin Hilman wrote: >> Greg Kroah-Hartman writes: >> >> > On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote: >> >> stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 >> >> offline, 5 conflicts (v3.18.112-22-gb0582263e3c9) >> >> >> >> Full Boot Summary: >> >> https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ >> >> Full Build Summary: >> >> https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ >> >> >> >> Tree: stable-rc >> >> Branch: linux-3.18.y >> >> Git Describe: v3.18.112-22-gb0582263e3c9 >> >> Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6 >> >> Git URL: >> >> http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> >> Tested: 24 unique boards, 12 SoC families, 13 builds out of 183 >> >> [...] >> >> > >> > That is a lot of new failures, did the whole lab fail, or is this really >> > a problem in v3.18.112 here? >> >> Whole lab failure (more precisely, lab operator failure) ;) >> >> gak, I updated the rootfs images to the latest buildroot, which forced >> me to upgrade the kernel headers used to build the rootfs from v3.10 to >> v4.4. So I guess it's no surprise that every single board panic'd as >> soon as it hit userspace. >> > I build my root file systems with buildroot, and had a similar problem. My fix > was to patch buildroot to let me use older linux headers. Could you share the patch? I was lazy and just rolled back the buildroot release. Thanks, Kevin
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Wed, Jun 13, 2018 at 05:09:11PM -0700, Kevin Hilman wrote: > Greg Kroah-Hartman writes: > > > On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote: > >> stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 > >> offline, 5 conflicts (v3.18.112-22-gb0582263e3c9) > >> > >> Full Boot Summary: > >> https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ > >> Full Build Summary: > >> https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ > >> > >> Tree: stable-rc > >> Branch: linux-3.18.y > >> Git Describe: v3.18.112-22-gb0582263e3c9 > >> Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6 > >> Git URL: > >> http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >> Tested: 24 unique boards, 12 SoC families, 13 builds out of 183 > > [...] > > > > > That is a lot of new failures, did the whole lab fail, or is this really > > a problem in v3.18.112 here? > > Whole lab failure (more precisely, lab operator failure) ;) > > gak, I updated the rootfs images to the latest buildroot, which forced > me to upgrade the kernel headers used to build the rootfs from v3.10 to > v4.4. So I guess it's no surprise that every single board panic'd as > soon as it hit userspace. > I build my root file systems with buildroot, and had a similar problem. My fix was to patch buildroot to let me use older linux headers. Guenter > I downgraded the rootfs, and re-ran all those boot tests, and now things > are 100% passing in my lab. > > Sorry for the noise, > > Kevin
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Wed, Jun 13, 2018 at 05:09:11PM -0700, Kevin Hilman wrote: > Greg Kroah-Hartman writes: > > > On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote: > >> stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 > >> offline, 5 conflicts (v3.18.112-22-gb0582263e3c9) > >> > >> Full Boot Summary: > >> https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ > >> Full Build Summary: > >> https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ > >> > >> Tree: stable-rc > >> Branch: linux-3.18.y > >> Git Describe: v3.18.112-22-gb0582263e3c9 > >> Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6 > >> Git URL: > >> http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > >> Tested: 24 unique boards, 12 SoC families, 13 builds out of 183 > > [...] > > > > > That is a lot of new failures, did the whole lab fail, or is this really > > a problem in v3.18.112 here? > > Whole lab failure (more precisely, lab operator failure) ;) > > gak, I updated the rootfs images to the latest buildroot, which forced > me to upgrade the kernel headers used to build the rootfs from v3.10 to > v4.4. So I guess it's no surprise that every single board panic'd as > soon as it hit userspace. > I build my root file systems with buildroot, and had a similar problem. My fix was to patch buildroot to let me use older linux headers. Guenter > I downgraded the rootfs, and re-ran all those boot tests, and now things > are 100% passing in my lab. > > Sorry for the noise, > > Kevin
Re: [PATCH 3.18 00/21] 3.18.113-stable review
Greg Kroah-Hartman writes: > On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote: >> stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 offline, >> 5 conflicts (v3.18.112-22-gb0582263e3c9) >> >> Full Boot Summary: >> https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ >> Full Build Summary: >> https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ >> >> Tree: stable-rc >> Branch: linux-3.18.y >> Git Describe: v3.18.112-22-gb0582263e3c9 >> Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6 >> Git URL: >> http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> Tested: 24 unique boards, 12 SoC families, 13 builds out of 183 [...] > > That is a lot of new failures, did the whole lab fail, or is this really > a problem in v3.18.112 here? Whole lab failure (more precisely, lab operator failure) ;) gak, I updated the rootfs images to the latest buildroot, which forced me to upgrade the kernel headers used to build the rootfs from v3.10 to v4.4. So I guess it's no surprise that every single board panic'd as soon as it hit userspace. I downgraded the rootfs, and re-ran all those boot tests, and now things are 100% passing in my lab. Sorry for the noise, Kevin
Re: [PATCH 3.18 00/21] 3.18.113-stable review
Greg Kroah-Hartman writes: > On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote: >> stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 offline, >> 5 conflicts (v3.18.112-22-gb0582263e3c9) >> >> Full Boot Summary: >> https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ >> Full Build Summary: >> https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ >> >> Tree: stable-rc >> Branch: linux-3.18.y >> Git Describe: v3.18.112-22-gb0582263e3c9 >> Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6 >> Git URL: >> http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git >> Tested: 24 unique boards, 12 SoC families, 13 builds out of 183 [...] > > That is a lot of new failures, did the whole lab fail, or is this really > a problem in v3.18.112 here? Whole lab failure (more precisely, lab operator failure) ;) gak, I updated the rootfs images to the latest buildroot, which forced me to upgrade the kernel headers used to build the rootfs from v3.10 to v4.4. So I guess it's no surprise that every single board panic'd as soon as it hit userspace. I downgraded the rootfs, and re-ran all those boot tests, and now things are 100% passing in my lab. Sorry for the noise, Kevin
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Wed, Jun 13, 2018 at 04:58:15PM +0200, Greg Kroah-Hartman wrote: > On Wed, Jun 13, 2018 at 04:09:57PM +0200, Greg Kroah-Hartman wrote: > > On Wed, Jun 13, 2018 at 06:48:05AM -0700, Guenter Roeck wrote: > > > On 06/12/2018 09:51 AM, Greg Kroah-Hartman wrote: > > > > This is the start of the stable review cycle for the 3.18.113 release. > > > > There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > > > > Anything received after that time might be too late. > > > > > > > > > > Build results: > > > total: 138 pass: 136 fail: 2 > > > Failed builds: > > > i386:tools/perf > > > x86_64:tools/perf > > > Qemu test results: > > > total: 127 pass: 127 fail: 0 > > > > > > The perf test only fails because I run "make tools/perf" instead of > > > "(cd tools/perf; make)". Fixing this requires the following two patches. > > > > > > 379a9a28a1b4 tools build: No need to make libapi for perf explicitly > > > 16671c1e1cac tools build: Fix Makefile(s) to properly invoke tools build > > > > Thanks for this, and the other 3 results. I'll just add these commits > > to the next kernel as this is not a new failure. > > I've queued these up now, but I still can't build perf for 3.18. Given > that no one has reported a problem with it so far, I'm guessing that no > one cares, so I'll just leave it as-is for now. > Ah, I should have waited for the test build to complete after applying the patches. Sorry for that. Apparently there are additional dependencies. (cd tools/perf; make) does work. I'll switch to use that for v3.16 (which has the same problem) and v3.18. Guenter
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Wed, Jun 13, 2018 at 04:58:15PM +0200, Greg Kroah-Hartman wrote: > On Wed, Jun 13, 2018 at 04:09:57PM +0200, Greg Kroah-Hartman wrote: > > On Wed, Jun 13, 2018 at 06:48:05AM -0700, Guenter Roeck wrote: > > > On 06/12/2018 09:51 AM, Greg Kroah-Hartman wrote: > > > > This is the start of the stable review cycle for the 3.18.113 release. > > > > There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > > > > Anything received after that time might be too late. > > > > > > > > > > Build results: > > > total: 138 pass: 136 fail: 2 > > > Failed builds: > > > i386:tools/perf > > > x86_64:tools/perf > > > Qemu test results: > > > total: 127 pass: 127 fail: 0 > > > > > > The perf test only fails because I run "make tools/perf" instead of > > > "(cd tools/perf; make)". Fixing this requires the following two patches. > > > > > > 379a9a28a1b4 tools build: No need to make libapi for perf explicitly > > > 16671c1e1cac tools build: Fix Makefile(s) to properly invoke tools build > > > > Thanks for this, and the other 3 results. I'll just add these commits > > to the next kernel as this is not a new failure. > > I've queued these up now, but I still can't build perf for 3.18. Given > that no one has reported a problem with it so far, I'm guessing that no > one cares, so I'll just leave it as-is for now. > Ah, I should have waited for the test build to complete after applying the patches. Sorry for that. Apparently there are additional dependencies. (cd tools/perf; make) does work. I'll switch to use that for v3.16 (which has the same problem) and v3.18. Guenter
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Wed, Jun 13, 2018 at 04:09:57PM +0200, Greg Kroah-Hartman wrote: > On Wed, Jun 13, 2018 at 06:48:05AM -0700, Guenter Roeck wrote: > > On 06/12/2018 09:51 AM, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 3.18.113 release. > > > There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > > > Anything received after that time might be too late. > > > > > > > Build results: > > total: 138 pass: 136 fail: 2 > > Failed builds: > > i386:tools/perf > > x86_64:tools/perf > > Qemu test results: > > total: 127 pass: 127 fail: 0 > > > > The perf test only fails because I run "make tools/perf" instead of > > "(cd tools/perf; make)". Fixing this requires the following two patches. > > > > 379a9a28a1b4 tools build: No need to make libapi for perf explicitly > > 16671c1e1cac tools build: Fix Makefile(s) to properly invoke tools build > > Thanks for this, and the other 3 results. I'll just add these commits > to the next kernel as this is not a new failure. I've queued these up now, but I still can't build perf for 3.18. Given that no one has reported a problem with it so far, I'm guessing that no one cares, so I'll just leave it as-is for now. thanks, greg k-h
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Wed, Jun 13, 2018 at 04:09:57PM +0200, Greg Kroah-Hartman wrote: > On Wed, Jun 13, 2018 at 06:48:05AM -0700, Guenter Roeck wrote: > > On 06/12/2018 09:51 AM, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 3.18.113 release. > > > There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > > > Anything received after that time might be too late. > > > > > > > Build results: > > total: 138 pass: 136 fail: 2 > > Failed builds: > > i386:tools/perf > > x86_64:tools/perf > > Qemu test results: > > total: 127 pass: 127 fail: 0 > > > > The perf test only fails because I run "make tools/perf" instead of > > "(cd tools/perf; make)". Fixing this requires the following two patches. > > > > 379a9a28a1b4 tools build: No need to make libapi for perf explicitly > > 16671c1e1cac tools build: Fix Makefile(s) to properly invoke tools build > > Thanks for this, and the other 3 results. I'll just add these commits > to the next kernel as this is not a new failure. I've queued these up now, but I still can't build perf for 3.18. Given that no one has reported a problem with it so far, I'm guessing that no one cares, so I'll just leave it as-is for now. thanks, greg k-h
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Wed, Jun 13, 2018 at 06:48:05AM -0700, Guenter Roeck wrote: > On 06/12/2018 09:51 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.113 release. > > There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > > Anything received after that time might be too late. > > > > Build results: > total: 138 pass: 136 fail: 2 > Failed builds: > i386:tools/perf > x86_64:tools/perf > Qemu test results: > total: 127 pass: 127 fail: 0 > > The perf test only fails because I run "make tools/perf" instead of > "(cd tools/perf; make)". Fixing this requires the following two patches. > > 379a9a28a1b4 tools build: No need to make libapi for perf explicitly > 16671c1e1cac tools build: Fix Makefile(s) to properly invoke tools build Thanks for this, and the other 3 results. I'll just add these commits to the next kernel as this is not a new failure. greg k-h
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Wed, Jun 13, 2018 at 06:48:05AM -0700, Guenter Roeck wrote: > On 06/12/2018 09:51 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.113 release. > > There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > > Anything received after that time might be too late. > > > > Build results: > total: 138 pass: 136 fail: 2 > Failed builds: > i386:tools/perf > x86_64:tools/perf > Qemu test results: > total: 127 pass: 127 fail: 0 > > The perf test only fails because I run "make tools/perf" instead of > "(cd tools/perf; make)". Fixing this requires the following two patches. > > 379a9a28a1b4 tools build: No need to make libapi for perf explicitly > 16671c1e1cac tools build: Fix Makefile(s) to properly invoke tools build Thanks for this, and the other 3 results. I'll just add these commits to the next kernel as this is not a new failure. greg k-h
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On 06/12/2018 09:51 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 3.18.113 release. There are 21 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 Thu Jun 14 16:48:15 UTC 2018. Anything received after that time might be too late. Build results: total: 138 pass: 136 fail: 2 Failed builds: i386:tools/perf x86_64:tools/perf Qemu test results: total: 127 pass: 127 fail: 0 The perf test only fails because I run "make tools/perf" instead of "(cd tools/perf; make)". Fixing this requires the following two patches. 379a9a28a1b4 tools build: No need to make libapi for perf explicitly 16671c1e1cac tools build: Fix Makefile(s) to properly invoke tools build Details are available at http://kerneltests.org/builders/. Guenter
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On 06/12/2018 09:51 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 3.18.113 release. There are 21 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 Thu Jun 14 16:48:15 UTC 2018. Anything received after that time might be too late. Build results: total: 138 pass: 136 fail: 2 Failed builds: i386:tools/perf x86_64:tools/perf Qemu test results: total: 127 pass: 127 fail: 0 The perf test only fails because I run "make tools/perf" instead of "(cd tools/perf; make)". Fixing this requires the following two patches. 379a9a28a1b4 tools build: No need to make libapi for perf explicitly 16671c1e1cac tools build: Fix Makefile(s) to properly invoke tools build Details are available at http://kerneltests.org/builders/. Guenter
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote: > stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 offline, 5 > conflicts (v3.18.112-22-gb0582263e3c9) > > Full Boot Summary: > https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ > Full Build Summary: > https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ > > Tree: stable-rc > Branch: linux-3.18.y > Git Describe: v3.18.112-22-gb0582263e3c9 > Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6 > Git URL: > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > Tested: 24 unique boards, 12 SoC families, 13 builds out of 183 > > Boot Regressions Detected: > > arm: > > bcm2835_defconfig: > bcm2835-rpi-b: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > davinci_all_defconfig: > dm365evm,legacy: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > exynos_defconfig: > exynos5800-peach-pi: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > imx_v6_v7_defconfig: > imx6dl-wandboard_dual: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > imx6dl-wandboard_solo: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > imx6q-wandboard: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > multi_v7_defconfig: > am335x-boneblack: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > armada-xp-openblocks-ax3-4: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > exynos5800-peach-pi: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > imx6dl-wandboard_dual: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > imx6dl-wandboard_solo: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > imx6q-wandboard: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap3-beagle: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap3-beagle-xm: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap4-panda: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > sun4i-a10-cubieboard: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > sun7i-a20-cubietruck: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > tegra124-jetson-tk1: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > tegra20-iris-512: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > tegra30-beaver: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > zynq-zc702: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > mvebu_v7_defconfig: > armada-xp-openblocks-ax3-4: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > omap2plus_defconfig: > am335x-boneblack: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap3-beagle: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap3-beagle-xm: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap3-beagle-xm,legacy: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap4-panda: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > sama5_defconfig: > at91-sama5d4ek: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > sunxi_defconfig: > sun4i-a10-cubieboard: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > sun7i-a20-cubietruck: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > tegra_defconfig: > tegra124-jetson-tk1: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > tegra20-iris-512: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > tegra30-beaver: > lab-baylibre-seattle: new failure (last pass: v3.18.112) That is a lot of new failures, did the whole lab fail, or is this really a problem in v3.18.112 here? thanks, greg k-h
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Tue, Jun 12, 2018 at 03:08:12PM -0700, kernelci.org bot wrote: > stable-rc/linux-3.18.y boot: 52 boots: 28 failed, 18 passed with 1 offline, 5 > conflicts (v3.18.112-22-gb0582263e3c9) > > Full Boot Summary: > https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ > Full Build Summary: > https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.112-22-gb0582263e3c9/ > > Tree: stable-rc > Branch: linux-3.18.y > Git Describe: v3.18.112-22-gb0582263e3c9 > Git Commit: b0582263e3c9810fd887ca92d19cb9ff30a4d9f6 > Git URL: > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > Tested: 24 unique boards, 12 SoC families, 13 builds out of 183 > > Boot Regressions Detected: > > arm: > > bcm2835_defconfig: > bcm2835-rpi-b: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > davinci_all_defconfig: > dm365evm,legacy: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > exynos_defconfig: > exynos5800-peach-pi: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > imx_v6_v7_defconfig: > imx6dl-wandboard_dual: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > imx6dl-wandboard_solo: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > imx6q-wandboard: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > multi_v7_defconfig: > am335x-boneblack: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > armada-xp-openblocks-ax3-4: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > exynos5800-peach-pi: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > imx6dl-wandboard_dual: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > imx6dl-wandboard_solo: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > imx6q-wandboard: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap3-beagle: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap3-beagle-xm: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap4-panda: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > sun4i-a10-cubieboard: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > sun7i-a20-cubietruck: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > tegra124-jetson-tk1: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > tegra20-iris-512: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > tegra30-beaver: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > zynq-zc702: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > mvebu_v7_defconfig: > armada-xp-openblocks-ax3-4: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > omap2plus_defconfig: > am335x-boneblack: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap3-beagle: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap3-beagle-xm: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap3-beagle-xm,legacy: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > omap4-panda: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > sama5_defconfig: > at91-sama5d4ek: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > sunxi_defconfig: > sun4i-a10-cubieboard: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > sun7i-a20-cubietruck: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > > tegra_defconfig: > tegra124-jetson-tk1: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > tegra20-iris-512: > lab-baylibre-seattle: new failure (last pass: v3.18.112) > tegra30-beaver: > lab-baylibre-seattle: new failure (last pass: v3.18.112) That is a lot of new failures, did the whole lab fail, or is this really a problem in v3.18.112 here? thanks, greg k-h
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On 06/12/2018 10:51 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.113 release. > There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > > https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-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 > Compiled and booted on my test system. No dmesg regressions. thanks, -- Shuah
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On 06/12/2018 10:51 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.113 release. > There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > > https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-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 > Compiled and booted on my test system. No dmesg regressions. thanks, -- Shuah
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Tue, Jun 12, 2018 at 11:50:36PM +0530, Harsh Shandilya wrote: > On 12 June 2018 10:21:57 PM IST, Greg Kroah-Hartman > wrote: > >This is the start of the stable review cycle for the 3.18.113 release. > >There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > >Anything received after that time might be too late. > > > >The whole patch series can be found in one patch at: > > > > https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-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 > Merged, compiled and flashed on the OnePlus 3T, no immediate > regressions noticed. Thanks for the update! Great, thanks for testing and letting me know. greg k-h
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Tue, Jun 12, 2018 at 11:50:36PM +0530, Harsh Shandilya wrote: > On 12 June 2018 10:21:57 PM IST, Greg Kroah-Hartman > wrote: > >This is the start of the stable review cycle for the 3.18.113 release. > >There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > >Anything received after that time might be too late. > > > >The whole patch series can be found in one patch at: > > > > https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-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 > Merged, compiled and flashed on the OnePlus 3T, no immediate > regressions noticed. Thanks for the update! Great, thanks for testing and letting me know. greg k-h
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On 12 June 2018 10:21:57 PM IST, Greg Kroah-Hartman wrote: >This is the start of the stable review cycle for the 3.18.113 release. >There are 21 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 Thu Jun 14 16:48:15 UTC 2018. >Anything received after that time might be too late. > >The whole patch series can be found in one patch at: > > https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-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 Merged, compiled and flashed on the OnePlus 3T, no immediate regressions noticed. Thanks for the update! -- Harsh Shandilya, PRJKT Development LLC
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On 12 June 2018 10:21:57 PM IST, Greg Kroah-Hartman wrote: >This is the start of the stable review cycle for the 3.18.113 release. >There are 21 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 Thu Jun 14 16:48:15 UTC 2018. >Anything received after that time might be too late. > >The whole patch series can be found in one patch at: > > https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-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 Merged, compiled and flashed on the OnePlus 3T, no immediate regressions noticed. Thanks for the update! -- Harsh Shandilya, PRJKT Development LLC
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Tue, Jun 12, 2018 at 06:51:57PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.113 release. > There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > > https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-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 > Merged, compiled with -Werror, and installed on my Pixel XL. No initial issues noticed in dmesg or general usage. Thanks! Nathan
Re: [PATCH 3.18 00/21] 3.18.113-stable review
On Tue, Jun 12, 2018 at 06:51:57PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.113 release. > There are 21 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 Thu Jun 14 16:48:15 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > > https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-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 > Merged, compiled with -Werror, and installed on my Pixel XL. No initial issues noticed in dmesg or general usage. Thanks! Nathan
[PATCH 3.18 00/21] 3.18.113-stable review
This is the start of the stable review cycle for the 3.18.113 release. There are 21 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 Thu Jun 14 16:48:15 UTC 2018. Anything received after that time might be too late. The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-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 - Pseudo-Shortlog of commits: Greg Kroah-Hartman Linux 3.18.113-rc1 Eric Dumazet rtnetlink: validate attributes in do_setlink() Dan Carpenter team: use netdev_features_t instead of u32 Jack Morgenstein net/mlx4: Fix irq-unsafe spinlock usage Daniele Palmas net: usb: cdc_mbim: add flag FLAG_SEND_ZLP Eric Dumazet net/packet: refine check for priv area size Wenwen Wang isdn: eicon: fix a missing-check bug Sabrina Dubroca ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds Govindarajulu Varadarajan enic: set DMA mask to 47 bit Alexey Kodanev dccp: don't free ccid2_hc_tx_sock struct in dccp_disconnect() Julia Lawall bnx2x: use the right constant Dave Airlie drm: set FMODE_UNSIGNED_OFFSET for drm files Linus Torvalds mmap: relax file size limit for regular files Linus Torvalds mmap: introduce sane default mmap limits Hugh Dickins mm: fix the NULL mapping case in __isolate_lru_page() Al Viro fix io_destroy()/aio_complete() race Ondrej Zary drm/i915: Disable LVDS on Radiant P845 Maciej W. Rozycki MIPS: ptrace: Fix PTRACE_PEEKUSR requests for 64-bit FGRs Eric Dumazet tcp: avoid integer overflows in tcp_rcv_space_adjust() Eric Biggers cfg80211: further limit wiphy names to 64 bytes Sachin Grover selinux: KASAN: slab-out-of-bounds in xattr_getsecurity Steven Rostedt (VMware) tracing: Fix crash when freeing instances with event triggers - Diffstat: Makefile | 4 +-- arch/mips/kernel/ptrace.c| 2 +- arch/mips/kernel/ptrace32.c | 2 +- drivers/gpu/drm/drm_fops.c | 1 + drivers/gpu/drm/i915/intel_lvds.c| 8 ++ drivers/isdn/hardware/eicon/diva.c | 22 ++-- drivers/isdn/hardware/eicon/diva.h | 5 ++-- drivers/isdn/hardware/eicon/divasmain.c | 18 +++-- drivers/net/ethernet/broadcom/bnx2x/bnx2x_link.c | 2 +- drivers/net/ethernet/cisco/enic/enic_main.c | 8 +++--- drivers/net/ethernet/mellanox/mlx4/qp.c | 4 +-- drivers/net/team/team.c | 3 ++- drivers/net/usb/cdc_mbim.c | 2 +- fs/aio.c | 3 +-- include/linux/tcp.h | 2 +- include/uapi/linux/nl80211.h | 2 +- kernel/trace/trace_events_trigger.c | 5 ++-- mm/mmap.c| 32 mm/vmscan.c | 2 +- net/core/rtnetlink.c | 8 +++--- net/dccp/proto.c | 2 -- net/ipv4/tcp_input.c | 10 +--- net/ipv6/ip6mr.c | 3 ++- net/packet/af_packet.c | 2 +- security/selinux/ss/services.c | 2 +- 25 files changed, 105 insertions(+), 49 deletions(-)
[PATCH 3.18 00/21] 3.18.113-stable review
This is the start of the stable review cycle for the 3.18.113 release. There are 21 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 Thu Jun 14 16:48:15 UTC 2018. Anything received after that time might be too late. The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.113-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 - Pseudo-Shortlog of commits: Greg Kroah-Hartman Linux 3.18.113-rc1 Eric Dumazet rtnetlink: validate attributes in do_setlink() Dan Carpenter team: use netdev_features_t instead of u32 Jack Morgenstein net/mlx4: Fix irq-unsafe spinlock usage Daniele Palmas net: usb: cdc_mbim: add flag FLAG_SEND_ZLP Eric Dumazet net/packet: refine check for priv area size Wenwen Wang isdn: eicon: fix a missing-check bug Sabrina Dubroca ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds Govindarajulu Varadarajan enic: set DMA mask to 47 bit Alexey Kodanev dccp: don't free ccid2_hc_tx_sock struct in dccp_disconnect() Julia Lawall bnx2x: use the right constant Dave Airlie drm: set FMODE_UNSIGNED_OFFSET for drm files Linus Torvalds mmap: relax file size limit for regular files Linus Torvalds mmap: introduce sane default mmap limits Hugh Dickins mm: fix the NULL mapping case in __isolate_lru_page() Al Viro fix io_destroy()/aio_complete() race Ondrej Zary drm/i915: Disable LVDS on Radiant P845 Maciej W. Rozycki MIPS: ptrace: Fix PTRACE_PEEKUSR requests for 64-bit FGRs Eric Dumazet tcp: avoid integer overflows in tcp_rcv_space_adjust() Eric Biggers cfg80211: further limit wiphy names to 64 bytes Sachin Grover selinux: KASAN: slab-out-of-bounds in xattr_getsecurity Steven Rostedt (VMware) tracing: Fix crash when freeing instances with event triggers - Diffstat: Makefile | 4 +-- arch/mips/kernel/ptrace.c| 2 +- arch/mips/kernel/ptrace32.c | 2 +- drivers/gpu/drm/drm_fops.c | 1 + drivers/gpu/drm/i915/intel_lvds.c| 8 ++ drivers/isdn/hardware/eicon/diva.c | 22 ++-- drivers/isdn/hardware/eicon/diva.h | 5 ++-- drivers/isdn/hardware/eicon/divasmain.c | 18 +++-- drivers/net/ethernet/broadcom/bnx2x/bnx2x_link.c | 2 +- drivers/net/ethernet/cisco/enic/enic_main.c | 8 +++--- drivers/net/ethernet/mellanox/mlx4/qp.c | 4 +-- drivers/net/team/team.c | 3 ++- drivers/net/usb/cdc_mbim.c | 2 +- fs/aio.c | 3 +-- include/linux/tcp.h | 2 +- include/uapi/linux/nl80211.h | 2 +- kernel/trace/trace_events_trigger.c | 5 ++-- mm/mmap.c| 32 mm/vmscan.c | 2 +- net/core/rtnetlink.c | 8 +++--- net/dccp/proto.c | 2 -- net/ipv4/tcp_input.c | 10 +--- net/ipv6/ip6mr.c | 3 ++- net/packet/af_packet.c | 2 +- security/selinux/ss/services.c | 2 +- 25 files changed, 105 insertions(+), 49 deletions(-)
