Re: [PATCH 4.14 00/14] 4.14.230-rc1 review
On 4/10/21 2:21 AM, Naresh Kamboju wrote: > On Sat, 10 Apr 2021 at 01:43, Guenter Roeck wrote: >> >> On Fri, Apr 09, 2021 at 11:53:25AM +0200, Greg Kroah-Hartman wrote: >>> This is the start of the stable review cycle for the 4.14.230 release. >>> There are 14 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 Sun, 11 Apr 2021 09:52:52 +. >>> Anything received after that time might be too late. >>> >> >> Build results: >> total: 168 pass: 168 fail: 0 >> Qemu test results: >> total: 408 pass: 408 fail: 0 >> >> Tested-by: Guenter Roeck >> >> Having said this, I did see a spurious crash, and I see an unusual warning. >> I have seen the crash only once, but the warning happens with every boot. >> These are likely not new but exposed because I added network interface >> tests. This is all v4.14.y specific; I did not see it in other branches. >> See below for the tracebacks. Maybe someone has seen it before. > > I do not notice these warnings. > Please share the testing environment / device / setup / network interfaces > and Kernel configs and steps to reproduce. > > - Naresh > Hi Naresh, the configuration is based on aspeed_g5_defconfig (see attached configuration file) and the following qemu command line (qemu v5.2): qemu-system-arm -M romulus-bmc -kernel \ arch/arm/boot/zImage -no-reboot \ -initrd rootfs-armv5.cpio -nic user -nodefaults \ --append "panic=-1 slub_debug=FZPUA rdinit=/sbin/init console=ttyS4,115200 earlycon=uart8250,mmio32,0x1e784000,115200n8" \ -dtb arch/arm/boot/dts/aspeed-bmc-opp-romulus.dtb \ -nographic -monitor null -serial stdio It also happens with other bmc platforms using the same network interface, though it is for some reason more prevalent on romulus-bmc. The root file system is generated with buildroot. See buildone.sh / buildall.sh in branch local-2021.02 of g...@github.com:groeck/buildroot.git. The warning happens with almost every boot; the crash in maybe one of 5-10 boots. The test, if you want to call it that, uses udhcpc to get an IP address and then net_test_successful=0 ifconfig eth0 2>/dev/null | grep -q "inet addr:10.0.2.15" if [ $? -eq 0 ]; then ping -q -c 1 -s 1000 -W 1 -I eth0 10.0.2.2 >/dev/null if [ $? -eq 0 ]; then telnet 10.0.2.2:22 /dev/null 2>dev/null if [ $? -eq 0 ]; then net_test_successful=1 fi fi fi See package/busybox/run.sh in the above repository/branch. Guenter defconfig.gz Description: application/gzip
Re: [PATCH 4.14 00/14] 4.14.230-rc1 review
Hi Greg, On 4/10/21 6:15 AM, Greg Kroah-Hartman wrote: > On Fri, Apr 09, 2021 at 01:13:06PM -0700, Guenter Roeck wrote: >> On Fri, Apr 09, 2021 at 11:53:25AM +0200, Greg Kroah-Hartman wrote: >>> This is the start of the stable review cycle for the 4.14.230 release. >>> There are 14 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 Sun, 11 Apr 2021 09:52:52 +. >>> Anything received after that time might be too late. >>> >> >> Build results: >> total: 168 pass: 168 fail: 0 >> Qemu test results: >> total: 408 pass: 408 fail: 0 >> >> Tested-by: Guenter Roeck >> >> Having said this, I did see a spurious crash, and I see an unusual warning. >> I have seen the crash only once, but the warning happens with every boot. >> These are likely not new but exposed because I added network interface >> tests. This is all v4.14.y specific; I did not see it in other branches. >> See below for the tracebacks. Maybe someone has seen it before. > > Thanks for testing all of these, I'll go queue up your reported fixes > here for the next release. > You'll need one more patch to avoid yet another warning: b0949618826c net/ncsi: Avoid GFP_KERNEL in response handler Thanks, Guenter
Re: [PATCH 4.14 00/14] 4.14.230-rc1 review
On Fri, Apr 09, 2021 at 01:13:06PM -0700, Guenter Roeck wrote: > On Fri, Apr 09, 2021 at 11:53:25AM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.230 release. > > There are 14 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 Sun, 11 Apr 2021 09:52:52 +. > > Anything received after that time might be too late. > > > > Build results: > total: 168 pass: 168 fail: 0 > Qemu test results: > total: 408 pass: 408 fail: 0 > > Tested-by: Guenter Roeck > > Having said this, I did see a spurious crash, and I see an unusual warning. > I have seen the crash only once, but the warning happens with every boot. > These are likely not new but exposed because I added network interface > tests. This is all v4.14.y specific; I did not see it in other branches. > See below for the tracebacks. Maybe someone has seen it before. Thanks for testing all of these, I'll go queue up your reported fixes here for the next release. greg k-h
Re: [PATCH 4.14 00/14] 4.14.230-rc1 review
On Sat, 10 Apr 2021 at 01:43, Guenter Roeck wrote: > > On Fri, Apr 09, 2021 at 11:53:25AM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.230 release. > > There are 14 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 Sun, 11 Apr 2021 09:52:52 +. > > Anything received after that time might be too late. > > > > Build results: > total: 168 pass: 168 fail: 0 > Qemu test results: > total: 408 pass: 408 fail: 0 > > Tested-by: Guenter Roeck > > Having said this, I did see a spurious crash, and I see an unusual warning. > I have seen the crash only once, but the warning happens with every boot. > These are likely not new but exposed because I added network interface > tests. This is all v4.14.y specific; I did not see it in other branches. > See below for the tracebacks. Maybe someone has seen it before. I do not notice these warnings. Please share the testing environment / device / setup / network interfaces and Kernel configs and steps to reproduce. - Naresh
Re: [PATCH 4.14 00/14] 4.14.230-rc1 review
On Fri, 9 Apr 2021 at 15:27, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.230 release. > There are 14 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 Sun, 11 Apr 2021 09:52:52 +. > 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/v4.x/stable-review/patch-4.14.230-rc1.gz > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > linux-4.14.y > and the diffstat can be found below. > > thanks, > > greg k-h Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386. Tested-by: Linux Kernel Functional Testing ## Build * kernel: 4.14.230-rc1 * git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git * git branch: linux-4.14.y * git commit: bbc0ac1df3446fb814abe1f0486c72f81bb95577 * git describe: v4.14.229-15-gbbc0ac1df344 * test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.14.y/build/v4.14.229-15-gbbc0ac1df344 ## No regressions (compared to v4.14.229) ## No fixes (compared to v4.14.229) ## Test result summary total: 54655, pass: 45540, fail: 651, skip: 8277, xfail: 187, ## Build Summary * arm: 96 total, 96 passed, 0 failed * arm64: 23 total, 23 passed, 0 failed * dragonboard-410c: 1 total, 1 passed, 0 failed * hi6220-hikey: 1 total, 1 passed, 0 failed * i386: 13 total, 13 passed, 0 failed * juno-r2: 1 total, 1 passed, 0 failed * mips: 36 total, 36 passed, 0 failed * sparc: 9 total, 9 passed, 0 failed * x15: 1 total, 1 passed, 0 failed * x86: 1 total, 1 passed, 0 failed * x86_64: 13 total, 13 passed, 0 failed ## Test suites summary * fwts * igt-gpu-tools * install-android-platform-tools-r2600 * kselftest-android * kselftest-bpf * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-efivarfs * kselftest-filesystems * kselftest-firmware * kselftest-fpu * kselftest-futex * kselftest-gpio * kselftest-intel_pstate * kselftest-ipc * kselftest-ir * kselftest-kcmp * kselftest-kexec * kselftest-kvm * kselftest-lib * kselftest-livepatch * kselftest-lkdtm * kselftest-membarrier * kselftest-net * kselftest-netfilter * kselftest-nsfs * kselftest-ptrace * kselftest-rseq * kselftest-rtc * kselftest-seccomp * kselftest-sigaltstack * kselftest-size * kselftest-splice * kselftest-static_keys * kselftest-sync * kselftest-sysctl * kselftest-tc-testing * kselftest-timens * kselftest-timers * kselftest-tmpfs * kselftest-tpm2 * kselftest-user * kselftest-vm * kselftest-x86 * kselftest-zram * kvm-unit-tests * libhugetlbfs * linux-log-parser * ltp-cap_bounds-tests * ltp-commands-tests * ltp-containers-tests * ltp-controllers-tests * ltp-cpuhotplug-tests * ltp-crypto-tests * ltp-cve-tests * ltp-dio-tests * ltp-fcntl-locktests-tests * ltp-filecaps-tests * ltp-fs-tests * ltp-fs_bind-tests * ltp-fs_perms_simple-tests * ltp-fsx-tests * ltp-hugetlb-tests * ltp-io-tests * ltp-ipc-tests * ltp-math-tests * ltp-mm-tests * ltp-nptl-tests * ltp-open-posix-tests * ltp-pty-tests * ltp-sched-tests * ltp-securebits-tests * ltp-syscalls-tests * ltp-tracing-tests * network-basic-tests * perf * rcutorture * v4l2-compliance -- Linaro LKFT https://lkft.linaro.org
Re: [PATCH 4.14 00/14] 4.14.230-rc1 review
On Fri, Apr 09, 2021 at 01:13:06PM -0700, Guenter Roeck wrote: > On Fri, Apr 09, 2021 at 11:53:25AM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.230 release. > > There are 14 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 Sun, 11 Apr 2021 09:52:52 +. > > Anything received after that time might be too late. > > > > Build results: > total: 168 pass: 168 fail: 0 > Qemu test results: > total: 408 pass: 408 fail: 0 > > Tested-by: Guenter Roeck > > Having said this, I did see a spurious crash, and I see an unusual warning. > I have seen the crash only once, but the warning happens with every boot. > These are likely not new but exposed because I added network interface > tests. This is all v4.14.y specific; I did not see it in other branches. > See below for the tracebacks. Maybe someone has seen it before. > > Thanks, > Guenter > > --- > ftgmac100 1e66.ethernet eth0: NCSI interface down > [ cut here ] > WARNING: CPU: 0 PID: 477 at drivers/base/dma-mapping.c:325 > remap_allocator_free+0x54/0x5c > trying to free invalid coherent area: 909a1000 > Modules linked in: > CPU: 0 PID: 477 Comm: ip Not tainted 4.14.230-rc1-00015-gbbc0ac1df344 #1 > Hardware name: Generic DT based system > [<8000f8dc>] (unwind_backtrace) from [<8000d194>] (show_stack+0x10/0x14) > [<8000d194>] (show_stack) from [<805a5a80>] (__warn+0xc0/0xf4) > [<805a5a80>] (__warn) from [<800177b4>] (warn_slowpath_fmt+0x38/0x48) > [<800177b4>] (warn_slowpath_fmt) from [<80010554>] > (remap_allocator_free+0x54/0x5c) > [<80010554>] (remap_allocator_free) from [<80010e4c>] > (__arm_dma_free.constprop.0+0xec/0x13c) > [<80010e4c>] (__arm_dma_free.constprop.0) from [<80429924>] > (ftgmac100_free_rings+0x17c/0x1f8) > [<80429924>] (ftgmac100_free_rings) from [<80429a24>] > (ftgmac100_stop+0x84/0xa4) > [<80429a24>] (ftgmac100_stop) from [<804e8a70>] (__dev_close_many+0xac/0x100) > [<804e8a70>] (__dev_close_many) from [<804f0dc0>] > (__dev_change_flags+0xb4/0x1a0) > [<804f0dc0>] (__dev_change_flags) from [<804f0ec4>] > (dev_change_flags+0x18/0x48) > [<804f0ec4>] (dev_change_flags) from [<80561644>] (devinet_ioctl+0x6cc/0x808) > [<80561644>] (devinet_ioctl) from [<804d1548>] (sock_ioctl+0x188/0x2e4) > [<804d1548>] (sock_ioctl) from [<800eac80>] (do_vfs_ioctl+0x3a0/0x82c) > [<800eac80>] (do_vfs_ioctl) from [<800eb140>] (SyS_ioctl+0x34/0x60) > [<800eb140>] (SyS_ioctl) from [<8000a600>] (ret_fast_syscall+0x0/0x28) > ---[ end trace c13f2f82f69274ad ]--- > > = > > ftgmac100 1e66.ethernet eth0: NCSI interface up > Unable to handle kernel NULL pointer dereference at virtual address > pgd = 9ec84000 > [] *pgd=9f7f6831, *pte=, *ppte= > Internal error: Oops: 17 [#1] ARM > Modules linked in: > CPU: 0 PID: 397 Comm: default.script Not tainted > 4.14.230-rc1-00015-gbbc0ac1df344 #1 > Hardware name: Generic DT based system > task: 9f5cc260 task.stack: 9ecee000 > PC is at anon_vma_clone+0x64/0x19c > LR is at fs_reclaim_release+0x8/0x18 > pc : [<800c1ccc>]lr : [<80098b5c>]psr: a153 > sp : 9ecefe78 ip : fp : > r10: 01000200 r9 : 9f7e6d10 r8 : 80cb9a44 > r7 : 9f7e0da0 r6 : 9f7e6d10 r5 : 9ed0f600 r4 : 9f5a562c > r3 : 0030 r2 : 9fbdf618 r1 : 0034 r0 : 9ed0f600 > Flags: NzCv IRQs on FIQs off Mode SVC_32 ISA ARM Segment user > Control: 00c5387d Table: 9ec84008 DAC: 0055 > Process default.script (pid: 397, stack limit = 0x9ecee188) > Stack: (0x9ecefe78 to 0x9ecf) > fe60: 9f5a303c 9f5a3000 > fe80: 0002 9f7e0da0 9f7e0ab4 9f5a3000 9f77e600 9f7e0da0 9f5a3000 9f77e400 > fea0: 9f72dc64 800c1e28 9f7e0ab0 9f7e0ab4 0002 9f77e600 9f7e0da0 800161f8 > fec0: 9f5cc640 cacd966c 9f5cc260 cd397f94 80cb0afc 80016870 > fee0: 9f69f2f8 9f7e0aa8 807ca224 9f7e0aa0 9f72dc70 9f69f100 0011 > ff00: 9f77e658 9f77e458 9eceff08 9eceff08 9f5cc650 0011 7eb26888 > ff20: 9ecee000 76eff3a0 80016870 > ff40: 7eb26888 9eceff78 9ecee000 76ec4a28 7eb26888 9eceff78 > ff60: 7eb26888 0008 0008 800245e4 76efdcd0 7eb26888 > ff80: 0002 8000a704 9ecee000 80016cd4 > ffa0: 9ecee000 8000a520 76efdcd0 7eb26888 76efffcc 0001 76efe7ac > ffc0: 76efdcd0 7eb26888 0002 7eb26918 76efe000 76f00c60 76eff3a0 > ffe0: 000e0350 7eb26888 76e96b94 76e96b98 6150 76efffcc > [<800c1ccc>] (anon_vma_clone) from [<800c1e28>] (anon_vma_fork+0x24/0x138) > [<800c1e28>] (anon_vma_fork) from [<800161f8>] > (copy_process.part.0+0x12a4/0x17dc) > [<800161f8>] (copy_process.part.0) from [<80016870>] (_do_fork+0xa0/0x488) > [<80016870>]
Re: [PATCH 4.14 00/14] 4.14.230-rc1 review
On Fri, Apr 09, 2021 at 11:53:25AM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.230 release. > There are 14 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 Sun, 11 Apr 2021 09:52:52 +. > Anything received after that time might be too late. > Build results: total: 168 pass: 168 fail: 0 Qemu test results: total: 408 pass: 408 fail: 0 Tested-by: Guenter Roeck Having said this, I did see a spurious crash, and I see an unusual warning. I have seen the crash only once, but the warning happens with every boot. These are likely not new but exposed because I added network interface tests. This is all v4.14.y specific; I did not see it in other branches. See below for the tracebacks. Maybe someone has seen it before. Thanks, Guenter --- ftgmac100 1e66.ethernet eth0: NCSI interface down [ cut here ] WARNING: CPU: 0 PID: 477 at drivers/base/dma-mapping.c:325 remap_allocator_free+0x54/0x5c trying to free invalid coherent area: 909a1000 Modules linked in: CPU: 0 PID: 477 Comm: ip Not tainted 4.14.230-rc1-00015-gbbc0ac1df344 #1 Hardware name: Generic DT based system [<8000f8dc>] (unwind_backtrace) from [<8000d194>] (show_stack+0x10/0x14) [<8000d194>] (show_stack) from [<805a5a80>] (__warn+0xc0/0xf4) [<805a5a80>] (__warn) from [<800177b4>] (warn_slowpath_fmt+0x38/0x48) [<800177b4>] (warn_slowpath_fmt) from [<80010554>] (remap_allocator_free+0x54/0x5c) [<80010554>] (remap_allocator_free) from [<80010e4c>] (__arm_dma_free.constprop.0+0xec/0x13c) [<80010e4c>] (__arm_dma_free.constprop.0) from [<80429924>] (ftgmac100_free_rings+0x17c/0x1f8) [<80429924>] (ftgmac100_free_rings) from [<80429a24>] (ftgmac100_stop+0x84/0xa4) [<80429a24>] (ftgmac100_stop) from [<804e8a70>] (__dev_close_many+0xac/0x100) [<804e8a70>] (__dev_close_many) from [<804f0dc0>] (__dev_change_flags+0xb4/0x1a0) [<804f0dc0>] (__dev_change_flags) from [<804f0ec4>] (dev_change_flags+0x18/0x48) [<804f0ec4>] (dev_change_flags) from [<80561644>] (devinet_ioctl+0x6cc/0x808) [<80561644>] (devinet_ioctl) from [<804d1548>] (sock_ioctl+0x188/0x2e4) [<804d1548>] (sock_ioctl) from [<800eac80>] (do_vfs_ioctl+0x3a0/0x82c) [<800eac80>] (do_vfs_ioctl) from [<800eb140>] (SyS_ioctl+0x34/0x60) [<800eb140>] (SyS_ioctl) from [<8000a600>] (ret_fast_syscall+0x0/0x28) ---[ end trace c13f2f82f69274ad ]--- = ftgmac100 1e66.ethernet eth0: NCSI interface up Unable to handle kernel NULL pointer dereference at virtual address pgd = 9ec84000 [] *pgd=9f7f6831, *pte=, *ppte= Internal error: Oops: 17 [#1] ARM Modules linked in: CPU: 0 PID: 397 Comm: default.script Not tainted 4.14.230-rc1-00015-gbbc0ac1df344 #1 Hardware name: Generic DT based system task: 9f5cc260 task.stack: 9ecee000 PC is at anon_vma_clone+0x64/0x19c LR is at fs_reclaim_release+0x8/0x18 pc : [<800c1ccc>]lr : [<80098b5c>]psr: a153 sp : 9ecefe78 ip : fp : r10: 01000200 r9 : 9f7e6d10 r8 : 80cb9a44 r7 : 9f7e0da0 r6 : 9f7e6d10 r5 : 9ed0f600 r4 : 9f5a562c r3 : 0030 r2 : 9fbdf618 r1 : 0034 r0 : 9ed0f600 Flags: NzCv IRQs on FIQs off Mode SVC_32 ISA ARM Segment user Control: 00c5387d Table: 9ec84008 DAC: 0055 Process default.script (pid: 397, stack limit = 0x9ecee188) Stack: (0x9ecefe78 to 0x9ecf) fe60: 9f5a303c 9f5a3000 fe80: 0002 9f7e0da0 9f7e0ab4 9f5a3000 9f77e600 9f7e0da0 9f5a3000 9f77e400 fea0: 9f72dc64 800c1e28 9f7e0ab0 9f7e0ab4 0002 9f77e600 9f7e0da0 800161f8 fec0: 9f5cc640 cacd966c 9f5cc260 cd397f94 80cb0afc 80016870 fee0: 9f69f2f8 9f7e0aa8 807ca224 9f7e0aa0 9f72dc70 9f69f100 0011 ff00: 9f77e658 9f77e458 9eceff08 9eceff08 9f5cc650 0011 7eb26888 ff20: 9ecee000 76eff3a0 80016870 ff40: 7eb26888 9eceff78 9ecee000 76ec4a28 7eb26888 9eceff78 ff60: 7eb26888 0008 0008 800245e4 76efdcd0 7eb26888 ff80: 0002 8000a704 9ecee000 80016cd4 ffa0: 9ecee000 8000a520 76efdcd0 7eb26888 76efffcc 0001 76efe7ac ffc0: 76efdcd0 7eb26888 0002 7eb26918 76efe000 76f00c60 76eff3a0 ffe0: 000e0350 7eb26888 76e96b94 76e96b98 6150 76efffcc [<800c1ccc>] (anon_vma_clone) from [<800c1e28>] (anon_vma_fork+0x24/0x138) [<800c1e28>] (anon_vma_fork) from [<800161f8>] (copy_process.part.0+0x12a4/0x17dc) [<800161f8>] (copy_process.part.0) from [<80016870>] (_do_fork+0xa0/0x488) [<80016870>] (_do_fork) from [<80016cd4>] (sys_fork+0x24/0x2c) [<80016cd4>] (sys_fork) from [<8000a520>] (ret_fast_syscall+0x0/0x4c) Code: eb001f58 e2505000 0a17 e594b004 (e59b9000) ---[ end trace 6680cdd56c4514b7 ]---
[PATCH 4.14 00/14] 4.14.230-rc1 review
This is the start of the stable review cycle for the 4.14.230 release. There are 14 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 Sun, 11 Apr 2021 09:52:52 +. 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/v4.x/stable-review/patch-4.14.230-rc1.gz or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.14.y and the diffstat can be found below. thanks, greg k-h - Pseudo-Shortlog of commits: Greg Kroah-Hartman Linux 4.14.230-rc1 Masahiro Yamada init/Kconfig: make COMPILE_TEST depend on HAS_IOMEM Heiko Carstens init/Kconfig: make COMPILE_TEST depend on !S390 Piotr Krysiuk bpf, x86: Validate computation of branch displacements for x86-64 Vincent Whitchurch cifs: Silently ignore unknown oplock break handle Ronnie Sahlberg cifs: revalidate mapping when we open files for SMB1 POSIX Sergei Trofimovich ia64: mca: allocate early mca with GFP_ATOMIC Martin Wilck scsi: target: pscsi: Clean up after failure in pscsi_map_sg() Arnd Bergmann x86/build: Turn off -fcf-protection for realmode targets Esteve Varela Colominas platform/x86: thinkpad_acpi: Allow the FnLock LED to change state Rob Clark drm/msm: Ratelimit invalid-fence message Karthikeyan Kathirvel mac80211: choose first enabled channel for monitor Tong Zhang mISDN: fix crash in fritzpci Pavel Andrianov net: pxa168_eth: Fix a potential data race in pxa168_eth_remove Mans Rullgard ARM: dts: am33xx: add aliases for mmc interfaces - Diffstat: Makefile | 4 ++-- arch/arm/boot/dts/am33xx.dtsi | 3 +++ arch/ia64/kernel/mca.c| 2 +- arch/x86/Makefile | 2 +- arch/x86/net/bpf_jit_comp.c | 11 ++- drivers/gpu/drm/msm/msm_fence.c | 2 +- drivers/isdn/hardware/mISDN/mISDNipac.c | 2 +- drivers/net/ethernet/marvell/pxa168_eth.c | 2 +- drivers/platform/x86/thinkpad_acpi.c | 8 +++- drivers/target/target_core_pscsi.c| 8 fs/cifs/file.c| 1 + fs/cifs/smb2misc.c| 4 ++-- init/Kconfig | 3 +-- net/mac80211/main.c | 13 - 14 files changed, 51 insertions(+), 14 deletions(-)
