linux-next: Tree for Apr 18
Hi all, News: there will be no linux-next release on Friday, Monday or Thursday April 25. Changes since 20190417: The bpf-next tree gained a build failure for which I applied a patch. The drm tree still had its build failure for which I disabled a driver. The fix is in the drm-misc tree where I reenabled the driver. The tip tree gained a conflict against the printk tree. The phy-next tree gained a conflict against the qcom tree. The akpm-current tree still had 2 build failures for which I applied patches. Non-merge commits (relative to Linus' tree): 7534 7343 files changed, 262299 insertions(+), 126469 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc and sparc64 defconfig. And finally, a simple boot test of the powerpc pseries_le_defconfig kernel in qemu (with and without kvm enabled). Below is a summary of the state of the merge. I am currently merging 298 trees (counting Linus' and 69 trees of bug fix patches pending for the current merge release). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (e53f31bffe1d Merge tag '5.1-rc5-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6) Merging fixes/master (1995fa480636 kernel/compat.c: mark expected switch fall-throughs) Merging kspp-gustavo/for-next/kspp (322b38ce3dd6 drm/nouveau/nvkm: mark expected switch fall-throughs) Merging kbuild-current/fixes (79a3aaa7b82e Linux 5.1-rc3) Merging arc-current/for-curr (55c0c4c793b5 ARC: memset: fix build with L1_CACHE_SHIFT != 6) Merging arm-current/fixes (d410a8a49e3e ARM: 8849/1: NOMMU: Fix encodings for PMSAv8's PRBAR4/PRLAR4) Merging arm64-fixes/for-next/fixes (045afc24124d arm64: futex: Fix FUTEX_WAKE_OP atomic ops with non-zero result value) Merging m68k-current/for-linus (28713169d879 m68k: Add -ffreestanding to CFLAGS) Merging powerpc-fixes/fixes (cf7cf6977f53 powerpc/mm: Define MAX_PHYSMEM_BITS for all 64-bit configs) Merging sparc/master (7d762d69145a afs: Fix manually set volume location server list) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (19fad20d15a6 ipv4: set the tcp_min_rtt_wlen range from 0 to one day) Merging bpf/master (fed68833fc53 libbpf: add binary to gitignore) Merging ipsec/master (837f74116585 xfrm: update doc about xfrm[46]_gc_thresh) Merging netfilter/master (5bdac418f33f netfilter: nat: fix icmp id randomization) Merging ipvs/master (b2e3d68d1251 netfilter: nft_compat: destroy function must not have side effects) Merging wireless-drivers/master (614c70f35cd7 bnx2x: fix spelling mistake "dicline" -> "decline") Merging mac80211/master (e9f33a8fee53 mac80211: fix RX STBC override byte order) Merging rdma-fixes/for-rc (d737b25b1ae0 IB/hfi1: Do not flush send queue in the TID RDMA second leg) Merging sound-current/for-linus (b26e36b7ef36 ALSA: hda/realtek - add two more pin configuration sets to quirk table) Merging sound-asoc-fixes/for-linus (dc4060a5dc25 Linux 5.1-rc5) Merging regmap-fixes/for-linus (dc1546f108cf Merge branch 'regmap-5.1' into regmap-linus) Merging regulator-fixes/for-linus (a90f262245ef Merge branch 'regulator-5.1' into regulator-linus) Merging spi-fixes/for-linus (8bc7a6fee4e5 Merge branch 'spi-5.1' into spi-linus) Merging pci-current/for-linus (d5bc73f34cc9 PCI: Fix issue with "pci=disable_acs_redir" parameter being ignored) Merging driver-core.current/driver-core-linus (79a3aaa7b82e Linux 5.1-rc3) Merging tty.current/tty-linus (b2ecf0063136 vt: fix cursor when clearing the screen) Merging usb.current/usb-linus (c01c348ecdc6 USB: core: Fix unterminated string returned by
linux-next: Tree for Apr 18
Hi all, Changes since 20180417: Removed tree: efi-lock-down (temporarily at maintainer's request) The netfilter tree lost its build failure. The sound-asoc tree lost its build failure but gained aonther so I have used the version from next-20180416. Non-merge commits (relative to Linus' tree): 797 915 files changed, 24509 insertions(+), 14978 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc and sparc64 defconfig. And finally, a simple boot test of the powerpc pseries_le_defconfig kernel in qemu (with and without kvm enabled). Below is a summary of the state of the merge. I am currently merging 257 trees (counting Linus' and 44 trees of bug fix patches pending for the current merge release). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (a27fc14219f2 Merge branch 'parisc-4.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux) Merging fixes/master (147a89bc71e7 Merge tag 'kconfig-v4.17' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild) Merging kbuild-current/fixes (28913ee8191a netfilter: nf_nat_snmp_basic: add correct dependency to Makefile) Merging arc-current/for-curr (661e50bc8532 Linux 4.16-rc4) Merging arm-current/fixes (fe680ca02c1e ARM: replace unnecessary perl with sed and the shell $(( )) operator) Merging arm64-fixes/for-next/fixes (800cb2e553d4 arm64: kasan: avoid pfn_to_nid() before page array is initialized) Merging m68k-current/for-linus (ecd685580c8f m68k/mac: Remove bogus "FIXME" comment) Merging powerpc-fixes/fixes (9dfbf78e4114 powerpc/64s: Default l1d_size to 64K in RFI fallback flush) Merging sparc/master (17dec0a94915 Merge branch 'userns-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (9c438d7a3a52 KEYS: DNS: limit the length of option strings) Merging bpf/master (3a38bb98d9ab bpf/tracing: fix a deadlock in perf_event_detach_bpf_prog) Merging ipsec/master (b48c05ab5d32 xfrm: Fix warning in xfrm6_tunnel_net_exit.) Merging netfilter/master (765cca91b895 netfilter: conntrack: include kmemleak.h for kmemleak_not_leak()) Merging ipvs/master (f7fb77fc1235 netfilter: nft_compat: check extension hook mask only if set) Merging wireless-drivers/master (77e30e10ee28 iwlwifi: mvm: query regdb for wmm rule if needed) Merging mac80211/master (b5dbc28762fd Merge tag 'kbuild-fixes-v4.16-3' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild) Merging rdma-fixes/for-rc (60cc43fc8884 Linux 4.17-rc1) Merging sound-current/for-linus (af52f9982e41 ALSA: hda - New VIA controller suppor no-snoop path) Merging pci-current/for-linus (60cc43fc8884 Linux 4.17-rc1) Merging driver-core.current/driver-core-linus (60cc43fc8884 Linux 4.17-rc1) Merging tty.current/tty-linus (60cc43fc8884 Linux 4.17-rc1) Merging usb.current/usb-linus (60cc43fc8884 Linux 4.17-rc1) Merging usb-gadget-fixes/fixes (c6ba5084ce0d usb: gadget: udc: renesas_usb3: add binging for r8a77965) Merging usb-serial-fixes/usb-linus (470b5d6f0cf4 USB: serial: ftdi_sio: use jtag quirk for Arrow USB Blaster) Merging usb-chipidea-fixes/ci-for-usb-stable (964728f9f407 USB: chipidea: msm: fix ulpi-node lookup) Merging phy/fixes (60cc43fc8884 Linux 4.17-rc1) Merging staging.current/staging-linus (edf5c17d866e staging: irda: remove remaining remants of irda code removal) Merging char-misc.current/char-misc-linus (60cc43fc8884 Linux 4.17-rc1) Merging input-current/for-linus (664b0bae0b87 Merge branch 'next' into for-linus)
linux-next: Tree for Apr 18
Hi all, Changes since 20180417: Removed tree: efi-lock-down (temporarily at maintainer's request) The netfilter tree lost its build failure. The sound-asoc tree lost its build failure but gained aonther so I have used the version from next-20180416. Non-merge commits (relative to Linus' tree): 797 915 files changed, 24509 insertions(+), 14978 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc and sparc64 defconfig. And finally, a simple boot test of the powerpc pseries_le_defconfig kernel in qemu (with and without kvm enabled). Below is a summary of the state of the merge. I am currently merging 257 trees (counting Linus' and 44 trees of bug fix patches pending for the current merge release). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (a27fc14219f2 Merge branch 'parisc-4.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux) Merging fixes/master (147a89bc71e7 Merge tag 'kconfig-v4.17' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild) Merging kbuild-current/fixes (28913ee8191a netfilter: nf_nat_snmp_basic: add correct dependency to Makefile) Merging arc-current/for-curr (661e50bc8532 Linux 4.16-rc4) Merging arm-current/fixes (fe680ca02c1e ARM: replace unnecessary perl with sed and the shell $(( )) operator) Merging arm64-fixes/for-next/fixes (800cb2e553d4 arm64: kasan: avoid pfn_to_nid() before page array is initialized) Merging m68k-current/for-linus (ecd685580c8f m68k/mac: Remove bogus "FIXME" comment) Merging powerpc-fixes/fixes (9dfbf78e4114 powerpc/64s: Default l1d_size to 64K in RFI fallback flush) Merging sparc/master (17dec0a94915 Merge branch 'userns-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace) Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2) Merging net/master (9c438d7a3a52 KEYS: DNS: limit the length of option strings) Merging bpf/master (3a38bb98d9ab bpf/tracing: fix a deadlock in perf_event_detach_bpf_prog) Merging ipsec/master (b48c05ab5d32 xfrm: Fix warning in xfrm6_tunnel_net_exit.) Merging netfilter/master (765cca91b895 netfilter: conntrack: include kmemleak.h for kmemleak_not_leak()) Merging ipvs/master (f7fb77fc1235 netfilter: nft_compat: check extension hook mask only if set) Merging wireless-drivers/master (77e30e10ee28 iwlwifi: mvm: query regdb for wmm rule if needed) Merging mac80211/master (b5dbc28762fd Merge tag 'kbuild-fixes-v4.16-3' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild) Merging rdma-fixes/for-rc (60cc43fc8884 Linux 4.17-rc1) Merging sound-current/for-linus (af52f9982e41 ALSA: hda - New VIA controller suppor no-snoop path) Merging pci-current/for-linus (60cc43fc8884 Linux 4.17-rc1) Merging driver-core.current/driver-core-linus (60cc43fc8884 Linux 4.17-rc1) Merging tty.current/tty-linus (60cc43fc8884 Linux 4.17-rc1) Merging usb.current/usb-linus (60cc43fc8884 Linux 4.17-rc1) Merging usb-gadget-fixes/fixes (c6ba5084ce0d usb: gadget: udc: renesas_usb3: add binging for r8a77965) Merging usb-serial-fixes/usb-linus (470b5d6f0cf4 USB: serial: ftdi_sio: use jtag quirk for Arrow USB Blaster) Merging usb-chipidea-fixes/ci-for-usb-stable (964728f9f407 USB: chipidea: msm: fix ulpi-node lookup) Merging phy/fixes (60cc43fc8884 Linux 4.17-rc1) Merging staging.current/staging-linus (edf5c17d866e staging: irda: remove remaining remants of irda code removal) Merging char-misc.current/char-misc-linus (60cc43fc8884 Linux 4.17-rc1) Merging input-current/for-linus (664b0bae0b87 Merge branch 'next' into for-linus)
linux-next: Tree for Apr 18
Hi all, Changes since 20170413: The thermal-soc tree gained a conflict against the pm tree. The net-next tree gained a conflict against the net tree. The block tree gained a build failure due to an interaction with the net-next tree for which I applied a merge fix patch. The staging tree gained build failures so I used the version from next-20170413 and applied a merge fix patch. The mux tree gained a conflict against the i2c tree. The rtc tree lost its build failure. The akpm-current tree gained a conflict against the kselftest tree. The akpm tree lost a patch that turned up elsewhere and gained a build failure due to an interaction with the tip tree for which I applied a merge fix patch. Non-merge commits (relative to Linus' tree): 9553 9232 files changed, 1110364 insertions(+), 189483 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig (with CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc and sparc64 defconfig. Below is a summary of the state of the merge. I am currently merging 258 trees (counting Linus' and 37 trees of bug fix patches pending for the current merge release). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (4f7d029b9bf0 Linux 4.11-rc7) Merging fixes/master (97da3854c526 Linux 4.11-rc3) Merging kbuild-current/fixes (9be3213b14d4 gconfig: remove misleading parentheses around a condition) Merging arc-current/for-curr (6492f09e8644 ARC: [plat-eznps] Fix build error) Merging arm-current/fixes (3872fe83a2fb Merge branch 'kprobe-fixes' of https://git.linaro.org/people/tixy/kernel into fixes) Merging m68k-current/for-linus (e3b1ebd67387 m68k: Wire up statx) Merging metag-fixes/fixes (b884a190afce metag/usercopy: Add missing fixups) Merging powerpc-fixes/fixes (4749228f0228 powerpc/crypto/crc32c-vpmsum: Fix missing preempt_disable()) Merging sparc/master (78d91a75b40f Merge branch 'for-linus' of git://git.kernel.dk/linux-block) Merging fscrypt-current/for-stable (42d97eb0ade3 fscrypt: fix renaming and linking special files) Merging net/master (acf167f3f249 Merge branch 'bpf-fixes') Merging ipsec/master (89e357d83c06 af_key: Add lock to key dump) Merging netfilter/master (fe50543c194e netfilter: ipt_CLUSTERIP: Fix wrong conntrack netns refcnt usage) Merging ipvs/master (0b9aefea8600 tcp: minimize false-positives on TCP/GRO check) Merging wireless-drivers/master (d77facb88448 brcmfmac: use local iftype avoiding use-after-free of virtual interface) Merging mac80211/master (fc9c89b19c56 Merge branch 'bridge-register-netdev-before-changelink') Merging sound-current/for-linus (dfb00a569351 ALSA: firewire-lib: fix inappropriate assignment between signed/unsigned type) Merging pci-current/for-linus (b9c1153f7a9c PCI: hisi: Fix DT binding (hisi-pcie-almost-ecam)) Merging driver-core.current/driver-core-linus (39da7c509acf Linux 4.11-rc6) Merging tty.current/tty-linus (4f7d029b9bf0 Linux 4.11-rc7) Merging usb.current/usb-linus (a71c9a1c779f Linux 4.11-rc5) Merging usb-gadget-fixes/fixes (25cd9721c2b1 usb: gadget: f_hid: fix: Don't access hidg->req without spinlock held) Merging usb-serial-fixes/usb-linus (c02ed2e75ef4 Linux 4.11-rc4) Merging usb-chipidea-fixes/ci-for-usb-stable (c7fbb09b2ea1 usb: chipidea: move the lock initialization to core file) Merging phy/fixes (1a09b6a7c10e phy: qcom-usb-hs: Add depends on EXTCON) Merging staging.current/staging-linus (39da7c509acf Linux 4.11-rc6) Merging char-misc.current/char-misc-linus (c02ed2e75ef4 Linux 4.11-rc4) Merging input-current/for-linus (537636688625 Input: xpad - add support for Razer Wildcat gamepad) Merging
linux-next: Tree for Apr 18
Hi all, Changes since 20170413: The thermal-soc tree gained a conflict against the pm tree. The net-next tree gained a conflict against the net tree. The block tree gained a build failure due to an interaction with the net-next tree for which I applied a merge fix patch. The staging tree gained build failures so I used the version from next-20170413 and applied a merge fix patch. The mux tree gained a conflict against the i2c tree. The rtc tree lost its build failure. The akpm-current tree gained a conflict against the kselftest tree. The akpm tree lost a patch that turned up elsewhere and gained a build failure due to an interaction with the tip tree for which I applied a merge fix patch. Non-merge commits (relative to Linus' tree): 9553 9232 files changed, 1110364 insertions(+), 189483 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig (with CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc and sparc64 defconfig. Below is a summary of the state of the merge. I am currently merging 258 trees (counting Linus' and 37 trees of bug fix patches pending for the current merge release). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (4f7d029b9bf0 Linux 4.11-rc7) Merging fixes/master (97da3854c526 Linux 4.11-rc3) Merging kbuild-current/fixes (9be3213b14d4 gconfig: remove misleading parentheses around a condition) Merging arc-current/for-curr (6492f09e8644 ARC: [plat-eznps] Fix build error) Merging arm-current/fixes (3872fe83a2fb Merge branch 'kprobe-fixes' of https://git.linaro.org/people/tixy/kernel into fixes) Merging m68k-current/for-linus (e3b1ebd67387 m68k: Wire up statx) Merging metag-fixes/fixes (b884a190afce metag/usercopy: Add missing fixups) Merging powerpc-fixes/fixes (4749228f0228 powerpc/crypto/crc32c-vpmsum: Fix missing preempt_disable()) Merging sparc/master (78d91a75b40f Merge branch 'for-linus' of git://git.kernel.dk/linux-block) Merging fscrypt-current/for-stable (42d97eb0ade3 fscrypt: fix renaming and linking special files) Merging net/master (acf167f3f249 Merge branch 'bpf-fixes') Merging ipsec/master (89e357d83c06 af_key: Add lock to key dump) Merging netfilter/master (fe50543c194e netfilter: ipt_CLUSTERIP: Fix wrong conntrack netns refcnt usage) Merging ipvs/master (0b9aefea8600 tcp: minimize false-positives on TCP/GRO check) Merging wireless-drivers/master (d77facb88448 brcmfmac: use local iftype avoiding use-after-free of virtual interface) Merging mac80211/master (fc9c89b19c56 Merge branch 'bridge-register-netdev-before-changelink') Merging sound-current/for-linus (dfb00a569351 ALSA: firewire-lib: fix inappropriate assignment between signed/unsigned type) Merging pci-current/for-linus (b9c1153f7a9c PCI: hisi: Fix DT binding (hisi-pcie-almost-ecam)) Merging driver-core.current/driver-core-linus (39da7c509acf Linux 4.11-rc6) Merging tty.current/tty-linus (4f7d029b9bf0 Linux 4.11-rc7) Merging usb.current/usb-linus (a71c9a1c779f Linux 4.11-rc5) Merging usb-gadget-fixes/fixes (25cd9721c2b1 usb: gadget: f_hid: fix: Don't access hidg->req without spinlock held) Merging usb-serial-fixes/usb-linus (c02ed2e75ef4 Linux 4.11-rc4) Merging usb-chipidea-fixes/ci-for-usb-stable (c7fbb09b2ea1 usb: chipidea: move the lock initialization to core file) Merging phy/fixes (1a09b6a7c10e phy: qcom-usb-hs: Add depends on EXTCON) Merging staging.current/staging-linus (39da7c509acf Linux 4.11-rc6) Merging char-misc.current/char-misc-linus (c02ed2e75ef4 Linux 4.11-rc4) Merging input-current/for-linus (537636688625 Input: xpad - add support for Razer Wildcat gamepad) Merging
linux-next: Tree for Apr 18
Hi all, Changes since 20160415: The net-next tree gained conflicts against the net tree. The tip tree still had its build failure for which I reverted a commit and gained another for which I applied a build fix. The gpio tree gained a build failure so I used the version from next-20160415. The livepatching tree gained conflicts against Linus' and the powerpc trees. The akpm-current tree still had its build failure for which I applied a patch. Non-merge commits (relative to Linus' tree): 4344 3992 files changed, 163277 insertions(+), 92002 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig (with CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig (this fails its final link) and pseries_le_defconfig and i386, sparc and sparc64 defconfig. Below is a summary of the state of the merge. I am currently merging 232 trees (counting Linus' and 35 trees of patches pending for Linus' tree). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (9d090d01e3ef Merge tag 'dm-4.6-fix-2' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm) Merging fixes/master (9735a22799b9 Linux 4.6-rc2) Merging kbuild-current/rc-fixes (3d1450d54a4f Makefile: Force gzip and xz on module install) Merging arc-current/for-curr (d01ebf06e305 ARCv2: Enable LOCKDEP) Merging arm-current/fixes (9c18fcf7ae0e ARM: 8551/2: DMA: Fix kzalloc flags in __dma_alloc) Merging m68k-current/for-linus (7b8ba82ad4ad m68k/defconfig: Update defconfigs for v4.6-rc2) Merging metag-fixes/fixes (0164a711c97b metag: Fix ioremap_wc/ioremap_cached build errors) Merging powerpc-fixes/fixes (71528d8bd7a8 powerpc: Correct used_vsr comment) Merging powerpc-merge-mpe/fixes (bc0195aad0da Linux 4.2-rc2) Merging sparc/master (5ec712934ce1 sparc: Write up preadv2/pwritev2 syscalls.) Merging net/master (ab2ed0171a50 macsec: fix crypto Kconfig dependency) Merging ipsec/master (d6af1a31cc72 vti: Add pmtu handling to vti_xmit.) Merging ipvs/master (bcf493428840 netfilter: ebtables: Fix extension lookup with identical name) Merging wireless-drivers/master (de478a61389c ath9k: ar5008_hw_cmn_spur_mitigate: add missing mask_m & mask_p initialisation) Merging mac80211/master (8f815cdde3e5 nl80211: check netlink protocol in socket release notification) Merging sound-current/for-linus (c44da62b55bb ALSA: hda - Fix inconsistent monitor_present state until repoll) Merging pci-current/for-linus (67e658794ca1 cxgb4: Set VPD size so we can read both VPD structures) Merging driver-core.current/driver-core-linus (dea5c24a1404 lib: lz4: cleanup unaligned access efficiency detection) Merging tty.current/tty-linus (bf1620068911 Linux 4.6-rc3) Merging usb.current/usb-linus (e86103a75705 usb: hcd: out of bounds access in for_each_companion) Merging usb-gadget-fixes/fixes (bf1620068911 Linux 4.6-rc3) Merging usb-serial-fixes/usb-linus (bf1620068911 Linux 4.6-rc3) Merging usb-chipidea-fixes/ci-for-usb-stable (d144dfea8af7 usb: chipidea: otg: change workqueue ci_otg as freezable) Merging staging.current/staging-linus (bf1620068911 Linux 4.6-rc3) Merging char-misc.current/char-misc-linus (053f78d35995 Merge tag 'lkdtm-4.6-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux into char-misc-linus) Merging input-current/for-linus (eda5ecc0a6b8 Input: pmic8xxx-pwrkey - fix algorithm for converting trigger delay) Merging crypto-current/master (f709b45ec461 crypto: ccp - Prevent information leakage on export) Merging ide/master (1993b176a822 Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide) Merging devicetree-current/devicetree/merge (f76502aa9140 of/dynamic: Fix test for
linux-next: Tree for Apr 18
Hi all, Changes since 20160415: The net-next tree gained conflicts against the net tree. The tip tree still had its build failure for which I reverted a commit and gained another for which I applied a build fix. The gpio tree gained a build failure so I used the version from next-20160415. The livepatching tree gained conflicts against Linus' and the powerpc trees. The akpm-current tree still had its build failure for which I applied a patch. Non-merge commits (relative to Linus' tree): 4344 3992 files changed, 163277 insertions(+), 92002 deletions(-) I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" and checkout or reset to the new master. You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig (with CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a native build of tools/perf. After the final fixups (if any), I do an x86_64 modules_install followed by builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig (this fails its final link) and pseries_le_defconfig and i386, sparc and sparc64 defconfig. Below is a summary of the state of the merge. I am currently merging 232 trees (counting Linus' and 35 trees of patches pending for Linus' tree). Stats about the size of the tree over time can be seen at http://neuling.org/linux-next-size.html . Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. -- Cheers, Stephen Rothwell $ git checkout master $ git reset --hard stable Merging origin/master (9d090d01e3ef Merge tag 'dm-4.6-fix-2' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm) Merging fixes/master (9735a22799b9 Linux 4.6-rc2) Merging kbuild-current/rc-fixes (3d1450d54a4f Makefile: Force gzip and xz on module install) Merging arc-current/for-curr (d01ebf06e305 ARCv2: Enable LOCKDEP) Merging arm-current/fixes (9c18fcf7ae0e ARM: 8551/2: DMA: Fix kzalloc flags in __dma_alloc) Merging m68k-current/for-linus (7b8ba82ad4ad m68k/defconfig: Update defconfigs for v4.6-rc2) Merging metag-fixes/fixes (0164a711c97b metag: Fix ioremap_wc/ioremap_cached build errors) Merging powerpc-fixes/fixes (71528d8bd7a8 powerpc: Correct used_vsr comment) Merging powerpc-merge-mpe/fixes (bc0195aad0da Linux 4.2-rc2) Merging sparc/master (5ec712934ce1 sparc: Write up preadv2/pwritev2 syscalls.) Merging net/master (ab2ed0171a50 macsec: fix crypto Kconfig dependency) Merging ipsec/master (d6af1a31cc72 vti: Add pmtu handling to vti_xmit.) Merging ipvs/master (bcf493428840 netfilter: ebtables: Fix extension lookup with identical name) Merging wireless-drivers/master (de478a61389c ath9k: ar5008_hw_cmn_spur_mitigate: add missing mask_m & mask_p initialisation) Merging mac80211/master (8f815cdde3e5 nl80211: check netlink protocol in socket release notification) Merging sound-current/for-linus (c44da62b55bb ALSA: hda - Fix inconsistent monitor_present state until repoll) Merging pci-current/for-linus (67e658794ca1 cxgb4: Set VPD size so we can read both VPD structures) Merging driver-core.current/driver-core-linus (dea5c24a1404 lib: lz4: cleanup unaligned access efficiency detection) Merging tty.current/tty-linus (bf1620068911 Linux 4.6-rc3) Merging usb.current/usb-linus (e86103a75705 usb: hcd: out of bounds access in for_each_companion) Merging usb-gadget-fixes/fixes (bf1620068911 Linux 4.6-rc3) Merging usb-serial-fixes/usb-linus (bf1620068911 Linux 4.6-rc3) Merging usb-chipidea-fixes/ci-for-usb-stable (d144dfea8af7 usb: chipidea: otg: change workqueue ci_otg as freezable) Merging staging.current/staging-linus (bf1620068911 Linux 4.6-rc3) Merging char-misc.current/char-misc-linus (053f78d35995 Merge tag 'lkdtm-4.6-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux into char-misc-linus) Merging input-current/for-linus (eda5ecc0a6b8 Input: pmic8xxx-pwrkey - fix algorithm for converting trigger delay) Merging crypto-current/master (f709b45ec461 crypto: ccp - Prevent information leakage on export) Merging ide/master (1993b176a822 Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide) Merging devicetree-current/devicetree/merge (f76502aa9140 of/dynamic: Fix test for
Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Sat, Apr 20, 2013 at 10:00 PM, Davidlohr Bueso wrote: > On Sat, 2013-04-20 at 02:19 +0200, Sedat Dilek wrote: >> On Sat, Apr 20, 2013 at 2:06 AM, Sedat Dilek wrote: >> > On Sat, Apr 20, 2013 at 1:02 AM, Linus Torvalds >> > wrote: >> >> On Fri, Apr 19, 2013 at 3:55 PM, Sedat Dilek >> >> wrote: >> >>> >> >>> Davidlohr pointed to this patch (tested the triplet): >> >>> >> >>> ipc, sem: do not call sem_lock when bogus sma: >> >>> https://lkml.org/lkml/2013/3/31/12 >> >>> >> >>> Is that what you mean? >> >> >> >> Yup. >> >> >> > >> > Davidlohr Bueso (1): >> > ipc, sem: do not call sem_lock when bogus sma >> > >> > Linus Torvalds (1): >> > crazy rcu double free debug hack >> > >> > With ***both*** patches applied I am able to build a Linux-kernel with >> > 4 parallel-make-jobs again. >> > David's or your patch alone are not sufficient! >> > >> >> [ Still both patches applied ] >> >> To correct myself... The 1st run was OK. >> >> The 2nd run shows a NULL-pointer-deref (excerpt): >> >> [ 178.490583] BUG: spinlock bad magic on CPU#1, sh/8066 >> [ 178.490595] lock: 0x88008b53ea18, .magic: 6b6b6b6b, .owner: >> make/8068, .owner_cpu: 3 >> [ 178.490599] BUG: unable to handle kernel NULL pointer dereference >> at (null) >> [ 178.490608] IP: [] update_queue+0x70/0x210 >> [ 178.490610] PGD 0 >> [ 178.490612] Oops: [#1] SMP >> ... > > The exit_sem() >> do_smart_update() >> update_queue() calls seem pretty > well protected. Furthermore we're asserting that sma->sem_perm.lock is > taken. This could just be a consequence of another issue. Earlier this > week Andrew pointed out a potential race in semctl_main() where > sma->sem_perm.deleted could be changed when cmd == GETALL. > > Sedat, could you try the attached patch to keep the ipc lock acquired > (on top of the three patches you're already using) and let us know how > it goes? We could also just have the RCU read lock instead of > ->sem.perm.lock for GETALL, but lets play it safe for now. > I had to refresh your patch and it contain strange ^M charachters as well. NOPE, the machine gets FROZEN (cold reboot). - Sedat - P.S.: I have attached all 4 patches against next-20130419 in case someone wants to follow. > Thanks, > Davidlohr > 0001-ipc-sem-untangle-RCU-locking-with-find_alloc_undo.patch Description: Binary data 0002-ipc-sem-fix-lockdep-false-positive.patch Description: Binary data 0003-ipc-sem-do-not-call-sem_lock-when-bogus-sma.patch Description: Binary data 0004-ipc-sem-check-if-the-ipc-lock-has-been-already-taken.patch Description: Binary data
Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Sat, 2013-04-20 at 02:19 +0200, Sedat Dilek wrote: > On Sat, Apr 20, 2013 at 2:06 AM, Sedat Dilek wrote: > > On Sat, Apr 20, 2013 at 1:02 AM, Linus Torvalds > > wrote: > >> On Fri, Apr 19, 2013 at 3:55 PM, Sedat Dilek wrote: > >>> > >>> Davidlohr pointed to this patch (tested the triplet): > >>> > >>> ipc, sem: do not call sem_lock when bogus sma: > >>> https://lkml.org/lkml/2013/3/31/12 > >>> > >>> Is that what you mean? > >> > >> Yup. > >> > > > > Davidlohr Bueso (1): > > ipc, sem: do not call sem_lock when bogus sma > > > > Linus Torvalds (1): > > crazy rcu double free debug hack > > > > With ***both*** patches applied I am able to build a Linux-kernel with > > 4 parallel-make-jobs again. > > David's or your patch alone are not sufficient! > > > > [ Still both patches applied ] > > To correct myself... The 1st run was OK. > > The 2nd run shows a NULL-pointer-deref (excerpt): > > [ 178.490583] BUG: spinlock bad magic on CPU#1, sh/8066 > [ 178.490595] lock: 0x88008b53ea18, .magic: 6b6b6b6b, .owner: > make/8068, .owner_cpu: 3 > [ 178.490599] BUG: unable to handle kernel NULL pointer dereference > at (null) > [ 178.490608] IP: [] update_queue+0x70/0x210 > [ 178.490610] PGD 0 > [ 178.490612] Oops: [#1] SMP > ... The exit_sem() >> do_smart_update() >> update_queue() calls seem pretty well protected. Furthermore we're asserting that sma->sem_perm.lock is taken. This could just be a consequence of another issue. Earlier this week Andrew pointed out a potential race in semctl_main() where sma->sem_perm.deleted could be changed when cmd == GETALL. Sedat, could you try the attached patch to keep the ipc lock acquired (on top of the three patches you're already using) and let us know how it goes? We could also just have the RCU read lock instead of ->sem.perm.lock for GETALL, but lets play it safe for now. Thanks, Davidlohr diff --git a/ipc/sem.c b/ipc/sem.c index 5711616..1dfc3c1 100644 --- a/ipc/sem.c +++ b/ipc/sem.c @@ -1243,10 +1243,11 @@ static int semctl_main(struct ipc_namespace *ns, int semid, int semnum, err = -EIDRM; goto out_free; } - sem_unlock(sma, -1); } - sem_lock(sma, NULL, -1); + /* has the ipc lock already been taken? */ + if(nsems <= SEMMSL_FAST) + sem_lock(sma, NULL, -1); for (i = 0; i < sma->sem_nsems; i++) sem_io[i] = sma->sem_base[i].semval; sem_unlock(sma, -1);
Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Sat, Apr 20, 2013 at 5:59 PM, Rik van Riel wrote: > On 04/20/2013 08:46 AM, Sedat Dilek wrote: > >> I have started a new thread "[next-20130419] ipc: sem: BROKEN", please >> use this one! >> >> Thanks for all your feedback! >> >> - Sedat - >> >> [1] http://marc.info/?l=linux-next=136646172915261=2 > > > I suspect most of us are not subscribed to the linux-next mailing list. > I know I'm not. > > If you need someone on some email thread, you need to CC them on the > email. > I dropped some irrelevant CCs from here in the new thread (as I did not know from what the root-cause was). LKML, linux-next, linux-mm MLs should be OK or am I missing someone or another ML? - Sedat - > -- > All rights reversed. -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On 04/20/2013 08:46 AM, Sedat Dilek wrote: I have started a new thread "[next-20130419] ipc: sem: BROKEN", please use this one! Thanks for all your feedback! - Sedat - [1] http://marc.info/?l=linux-next=136646172915261=2 I suspect most of us are not subscribed to the linux-next mailing list. I know I'm not. If you need someone on some email thread, you need to CC them on the email. -- All rights reversed. -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Sat, Apr 20, 2013 at 2:19 AM, Sedat Dilek wrote: > On Sat, Apr 20, 2013 at 2:06 AM, Sedat Dilek wrote: >> On Sat, Apr 20, 2013 at 1:02 AM, Linus Torvalds >> wrote: >>> On Fri, Apr 19, 2013 at 3:55 PM, Sedat Dilek wrote: Davidlohr pointed to this patch (tested the triplet): ipc, sem: do not call sem_lock when bogus sma: https://lkml.org/lkml/2013/3/31/12 Is that what you mean? >>> >>> Yup. >>> >> >> Davidlohr Bueso (1): >> ipc, sem: do not call sem_lock when bogus sma >> >> Linus Torvalds (1): >> crazy rcu double free debug hack >> >> With ***both*** patches applied I am able to build a Linux-kernel with >> 4 parallel-make-jobs again. >> David's or your patch alone are not sufficient! >> > > [ Still both patches applied ] > > To correct myself... The 1st run was OK. > > The 2nd run shows a NULL-pointer-deref (excerpt): > > [ 178.490583] BUG: spinlock bad magic on CPU#1, sh/8066 > [ 178.490595] lock: 0x88008b53ea18, .magic: 6b6b6b6b, .owner: > make/8068, .owner_cpu: 3 > [ 178.490599] BUG: unable to handle kernel NULL pointer dereference > at (null) > [ 178.490608] IP: [] update_queue+0x70/0x210 > [ 178.490610] PGD 0 > [ 178.490612] Oops: [#1] SMP > ... > > See attached full dmesg! > > Hope this helps. > > - Sedat - > > >> - Sedat - >> >>> Linus I have started a new thread "[next-20130419] ipc: sem: BROKEN", please use this one! Thanks for all your feedback! - Sedat - [1] http://marc.info/?l=linux-next=136646172915261=2 -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Sat, Apr 20, 2013 at 2:19 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Sat, Apr 20, 2013 at 2:06 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Sat, Apr 20, 2013 at 1:02 AM, Linus Torvalds torva...@linux-foundation.org wrote: On Fri, Apr 19, 2013 at 3:55 PM, Sedat Dilek sedat.di...@gmail.com wrote: Davidlohr pointed to this patch (tested the triplet): ipc, sem: do not call sem_lock when bogus sma: https://lkml.org/lkml/2013/3/31/12 Is that what you mean? Yup. Davidlohr Bueso (1): ipc, sem: do not call sem_lock when bogus sma Linus Torvalds (1): crazy rcu double free debug hack With ***both*** patches applied I am able to build a Linux-kernel with 4 parallel-make-jobs again. David's or your patch alone are not sufficient! [ Still both patches applied ] To correct myself... The 1st run was OK. The 2nd run shows a NULL-pointer-deref (excerpt): [ 178.490583] BUG: spinlock bad magic on CPU#1, sh/8066 [ 178.490595] lock: 0x88008b53ea18, .magic: 6b6b6b6b, .owner: make/8068, .owner_cpu: 3 [ 178.490599] BUG: unable to handle kernel NULL pointer dereference at (null) [ 178.490608] IP: [812bacd0] update_queue+0x70/0x210 [ 178.490610] PGD 0 [ 178.490612] Oops: [#1] SMP ... See attached full dmesg! Hope this helps. - Sedat - - Sedat - Linus I have started a new thread [next-20130419] ipc: sem: BROKEN, please use this one! Thanks for all your feedback! - Sedat - [1] http://marc.info/?l=linux-nextm=136646172915261w=2 -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On 04/20/2013 08:46 AM, Sedat Dilek wrote: I have started a new thread [next-20130419] ipc: sem: BROKEN, please use this one! Thanks for all your feedback! - Sedat - [1] http://marc.info/?l=linux-nextm=136646172915261w=2 I suspect most of us are not subscribed to the linux-next mailing list. I know I'm not. If you need someone on some email thread, you need to CC them on the email. -- All rights reversed. -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Sat, Apr 20, 2013 at 5:59 PM, Rik van Riel r...@surriel.com wrote: On 04/20/2013 08:46 AM, Sedat Dilek wrote: I have started a new thread [next-20130419] ipc: sem: BROKEN, please use this one! Thanks for all your feedback! - Sedat - [1] http://marc.info/?l=linux-nextm=136646172915261w=2 I suspect most of us are not subscribed to the linux-next mailing list. I know I'm not. If you need someone on some email thread, you need to CC them on the email. I dropped some irrelevant CCs from here in the new thread (as I did not know from what the root-cause was). LKML, linux-next, linux-mm MLs should be OK or am I missing someone or another ML? - Sedat - -- All rights reversed. -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Sat, 2013-04-20 at 02:19 +0200, Sedat Dilek wrote: On Sat, Apr 20, 2013 at 2:06 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Sat, Apr 20, 2013 at 1:02 AM, Linus Torvalds torva...@linux-foundation.org wrote: On Fri, Apr 19, 2013 at 3:55 PM, Sedat Dilek sedat.di...@gmail.com wrote: Davidlohr pointed to this patch (tested the triplet): ipc, sem: do not call sem_lock when bogus sma: https://lkml.org/lkml/2013/3/31/12 Is that what you mean? Yup. Davidlohr Bueso (1): ipc, sem: do not call sem_lock when bogus sma Linus Torvalds (1): crazy rcu double free debug hack With ***both*** patches applied I am able to build a Linux-kernel with 4 parallel-make-jobs again. David's or your patch alone are not sufficient! [ Still both patches applied ] To correct myself... The 1st run was OK. The 2nd run shows a NULL-pointer-deref (excerpt): [ 178.490583] BUG: spinlock bad magic on CPU#1, sh/8066 [ 178.490595] lock: 0x88008b53ea18, .magic: 6b6b6b6b, .owner: make/8068, .owner_cpu: 3 [ 178.490599] BUG: unable to handle kernel NULL pointer dereference at (null) [ 178.490608] IP: [812bacd0] update_queue+0x70/0x210 [ 178.490610] PGD 0 [ 178.490612] Oops: [#1] SMP ... The exit_sem() do_smart_update() update_queue() calls seem pretty well protected. Furthermore we're asserting that sma-sem_perm.lock is taken. This could just be a consequence of another issue. Earlier this week Andrew pointed out a potential race in semctl_main() where sma-sem_perm.deleted could be changed when cmd == GETALL. Sedat, could you try the attached patch to keep the ipc lock acquired (on top of the three patches you're already using) and let us know how it goes? We could also just have the RCU read lock instead of -sem.perm.lock for GETALL, but lets play it safe for now. Thanks, Davidlohr diff --git a/ipc/sem.c b/ipc/sem.c index 5711616..1dfc3c1 100644 --- a/ipc/sem.c +++ b/ipc/sem.c @@ -1243,10 +1243,11 @@ static int semctl_main(struct ipc_namespace *ns, int semid, int semnum, err = -EIDRM; goto out_free; } - sem_unlock(sma, -1); } - sem_lock(sma, NULL, -1); + /* has the ipc lock already been taken? */ + if(nsems = SEMMSL_FAST) + sem_lock(sma, NULL, -1); for (i = 0; i sma-sem_nsems; i++) sem_io[i] = sma-sem_base[i].semval; sem_unlock(sma, -1);
Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Sat, Apr 20, 2013 at 10:00 PM, Davidlohr Bueso davidlohr.bu...@hp.com wrote: On Sat, 2013-04-20 at 02:19 +0200, Sedat Dilek wrote: On Sat, Apr 20, 2013 at 2:06 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Sat, Apr 20, 2013 at 1:02 AM, Linus Torvalds torva...@linux-foundation.org wrote: On Fri, Apr 19, 2013 at 3:55 PM, Sedat Dilek sedat.di...@gmail.com wrote: Davidlohr pointed to this patch (tested the triplet): ipc, sem: do not call sem_lock when bogus sma: https://lkml.org/lkml/2013/3/31/12 Is that what you mean? Yup. Davidlohr Bueso (1): ipc, sem: do not call sem_lock when bogus sma Linus Torvalds (1): crazy rcu double free debug hack With ***both*** patches applied I am able to build a Linux-kernel with 4 parallel-make-jobs again. David's or your patch alone are not sufficient! [ Still both patches applied ] To correct myself... The 1st run was OK. The 2nd run shows a NULL-pointer-deref (excerpt): [ 178.490583] BUG: spinlock bad magic on CPU#1, sh/8066 [ 178.490595] lock: 0x88008b53ea18, .magic: 6b6b6b6b, .owner: make/8068, .owner_cpu: 3 [ 178.490599] BUG: unable to handle kernel NULL pointer dereference at (null) [ 178.490608] IP: [812bacd0] update_queue+0x70/0x210 [ 178.490610] PGD 0 [ 178.490612] Oops: [#1] SMP ... The exit_sem() do_smart_update() update_queue() calls seem pretty well protected. Furthermore we're asserting that sma-sem_perm.lock is taken. This could just be a consequence of another issue. Earlier this week Andrew pointed out a potential race in semctl_main() where sma-sem_perm.deleted could be changed when cmd == GETALL. Sedat, could you try the attached patch to keep the ipc lock acquired (on top of the three patches you're already using) and let us know how it goes? We could also just have the RCU read lock instead of -sem.perm.lock for GETALL, but lets play it safe for now. I had to refresh your patch and it contain strange ^M charachters as well. NOPE, the machine gets FROZEN (cold reboot). - Sedat - P.S.: I have attached all 4 patches against next-20130419 in case someone wants to follow. Thanks, Davidlohr 0001-ipc-sem-untangle-RCU-locking-with-find_alloc_undo.patch Description: Binary data 0002-ipc-sem-fix-lockdep-false-positive.patch Description: Binary data 0003-ipc-sem-do-not-call-sem_lock-when-bogus-sma.patch Description: Binary data 0004-ipc-sem-check-if-the-ipc-lock-has-been-already-taken.patch Description: Binary data
Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 3:55 PM, Sedat Dilek wrote: > > Davidlohr pointed to this patch (tested the triplet): > > ipc, sem: do not call sem_lock when bogus sma: > https://lkml.org/lkml/2013/3/31/12 > > Is that what you mean? Yup. Linus -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Sat, Apr 20, 2013 at 12:50 AM, Linus Torvalds wrote: > On Fri, Apr 19, 2013 at 3:34 PM, Sedat Dilek wrote: >> >> See attached dmesg. > > This still has the bug Davidlohr pointed at: > >>> This looks like what Emmanuel was/is running into: >>> https://lkml.org/lkml/2013/3/30/1 > > you need to move the "IS_ERR()" check before the sem_lock. > Davidlohr pointed to this patch (tested the triplet): ipc, sem: do not call sem_lock when bogus sma: https://lkml.org/lkml/2013/3/31/12 Is that what you mean? - Sedat - > Linus -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 3:34 PM, Sedat Dilek wrote: > > See attached dmesg. This still has the bug Davidlohr pointed at: >> This looks like what Emmanuel was/is running into: >> https://lkml.org/lkml/2013/3/30/1 you need to move the "IS_ERR()" check before the sem_lock. Linus -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 02:24:10PM -0700, Linus Torvalds wrote: > On Fri, Apr 19, 2013 at 2:09 PM, Sedat Dilek wrote: > > > > I have applied all three patches and see still call-traces. > > New are apparmor related messages. > > Can you try the crazy rcu double-free debug hack? > > See > > https://lkml.org/lkml/2013/3/30/113 > > and I'm re-attaching the ugly-ass crazy hack patch here too.. > > Linus For whatever it is worth, CONFIG_DEBUG_OBJECTS_RCU_HEAD=y is intended to detect RCU double-freeing. But if it isn't helping for whatever reason, please let me know! Thanx, Paul -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 2:09 PM, Sedat Dilek wrote: > > I have applied all three patches and see still call-traces. > New are apparmor related messages. Can you try the crazy rcu double-free debug hack? See https://lkml.org/lkml/2013/3/30/113 and I'm re-attaching the ugly-ass crazy hack patch here too.. Linus rcu-double-free-hack.patch Description: Binary data
Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, 2013-04-19 at 15:19 -0400, Rik van Riel wrote: > On 04/19/2013 02:53 PM, Sedat Dilek wrote: > > On Fri, Apr 19, 2013 at 6:43 PM, Sedat Dilek wrote: > > > >> I tried to switch from SLUB to SLAB... > >> > >> ...and also from VIRT_CPU_ACCOUNTING_GEN to TICK_CPU_ACCOUNTING. > >> > >> 2x NOPE. > >> > >> In one kernel-build I saw in my console... > >> > >> semop(1): encountered an error: Identifier removed This looks like what Emmanuel was/is running into: https://lkml.org/lkml/2013/3/30/1 > >> > >> ...if this says sth. to you. > >> > > [ CC folks from below thread ] > > > > I have found a thread called "Re: ipc,sem: sysv semaphore scalability" > > on LKML with a screenshot that shows the same call-trace. > > I followed it a bit. > > There is a patch in [3]... unconfirmed. > > > > Comments on the rcu read-lock and "sem_lock()" vs "sem_unlock()" from Linus. > > > > What's the status of this discussion? > > > > - Sedat - > > > > [1] https://lkml.org/lkml/2013/3/30/6 > > [2] http://i.imgur.com/uk6gmq1.jpg > > [3] https://lkml.org/lkml/2013/3/31/12 > > [4] https://lkml.org/lkml/2013/3/31/77 > > > I am at a conference right now, but when I get > back I will check linux-next vs. all the fixes from > the semaphore scalability email thread. I'm back from the collab. summit, so AFAICT these still need to go in linux-next: ipc,sem: untangle RCU locking with find_alloc_undo: https://lkml.org/lkml/2013/3/28/275 ipc,sem: fix lockdep false positive: https://lkml.org/lkml/2013/3/29/119 ipc, sem: do not call sem_lock when bogus sma: https://lkml.org/lkml/2013/3/31/12 Thanks, Davidlohr -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On 04/19/2013 02:53 PM, Sedat Dilek wrote: On Fri, Apr 19, 2013 at 6:43 PM, Sedat Dilek wrote: I tried to switch from SLUB to SLAB... ...and also from VIRT_CPU_ACCOUNTING_GEN to TICK_CPU_ACCOUNTING. 2x NOPE. In one kernel-build I saw in my console... semop(1): encountered an error: Identifier removed ...if this says sth. to you. [ CC folks from below thread ] I have found a thread called "Re: ipc,sem: sysv semaphore scalability" on LKML with a screenshot that shows the same call-trace. I followed it a bit. There is a patch in [3]... unconfirmed. Comments on the rcu read-lock and "sem_lock()" vs "sem_unlock()" from Linus. What's the status of this discussion? - Sedat - [1] https://lkml.org/lkml/2013/3/30/6 [2] http://i.imgur.com/uk6gmq1.jpg [3] https://lkml.org/lkml/2013/3/31/12 [4] https://lkml.org/lkml/2013/3/31/77 I am at a conference right now, but when I get back I will check linux-next vs. all the fixes from the semaphore scalability email thread. I will gather up the not-yet-in-linux-next fixes, and will send them to Andrew for inclusion. No guarantee that those fixes are related to your problem, of course :) -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 6:43 PM, Sedat Dilek wrote: > On Fri, Apr 19, 2013 at 12:27 PM, Sedat Dilek wrote: >> On Fri, Apr 19, 2013 at 12:19 PM, Sedat Dilek wrote: >>> On Thu, Apr 18, 2013 at 11:59 PM, Sedat Dilek wrote: On Thu, Apr 18, 2013 at 9:48 PM, Daniel Vetter wrote: > On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek > wrote: >> On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell >> wrote: >>> Hi all, >>> >>> Changes since 20130417: >>> >>> New Trees: rpmsg (actually added yesterday) >>> ppc-temp (replacing powerpc for this week) >>> >>> The ceph tree gained a conflict against Linus' tree. >>> >>> The net-next tree gained a conflict against the infiniband tree. >>> >>> The usb tree gained a build failure so I used the version from >>> next-20130417. >>> >>> I added two merge fix patches after the gen-gpio tree. >>> >>> The ppc-temp tree gained a conflict against the metag tree. >>> >>> The akpm tree lost a patch that turned up elsewhere. >>> >>> >>> >> >> Not sure what the root-cause for this call-trace is (see screenshot). >> >> This is reproducible when running my kernel build-script (4 >> parallel-make-jobs). >> >> Any hints welcome! > > The panic handlers in our modeset code are pretty decent fubar - they > take mutexes all over the place. So I think the backtrace you see > there is actually a secondary effect. I've looked into fixing this up, > but the issue is that drivers themselves have tons of state protected > with mutexes, which all potentially affects the panic handler. So I've > given up on that for now ... Thanks for taking care. On suspicion [1] I have reverted [2]... NOPE. - Sedat - [1] http://marc.info/?l=linux-kernel=136631921208895=2 [2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=5a90d1a95356de7a32acb2e5309ac579a891af8f >>> >>> Hmmm, the issue seems to be gone with today's Linux-Next (next-20130419). >>> My kernel-build is still running with no call-trace... >>> >> >> NO, It's no good. >> > > I tried to switch from SLUB to SLAB... > > ...and also from VIRT_CPU_ACCOUNTING_GEN to TICK_CPU_ACCOUNTING. > > 2x NOPE. > > In one kernel-build I saw in my console... > > semop(1): encountered an error: Identifier removed > > ...if this says sth. to you. > [ CC folks from below thread ] I have found a thread called "Re: ipc,sem: sysv semaphore scalability" on LKML with a screenshot that shows the same call-trace. I followed it a bit. There is a patch in [3]... unconfirmed. Comments on the rcu read-lock and "sem_lock()" vs "sem_unlock()" from Linus. What's the status of this discussion? - Sedat - [1] https://lkml.org/lkml/2013/3/30/6 [2] http://i.imgur.com/uk6gmq1.jpg [3] https://lkml.org/lkml/2013/3/31/12 [4] https://lkml.org/lkml/2013/3/31/77 > - Sedat - > > - Sedat - > >> - Sedat - >> >> [1] http://www.youtube.com/watch?v=LwicaralvS0 >> >>> - Sedat - >>> > -Daniel > -- > Daniel Vetter > Software Engineer, Intel Corporation > +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 12:27 PM, Sedat Dilek wrote: > On Fri, Apr 19, 2013 at 12:19 PM, Sedat Dilek wrote: >> On Thu, Apr 18, 2013 at 11:59 PM, Sedat Dilek wrote: >>> On Thu, Apr 18, 2013 at 9:48 PM, Daniel Vetter >>> wrote: On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek wrote: > On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell > wrote: >> Hi all, >> >> Changes since 20130417: >> >> New Trees: rpmsg (actually added yesterday) >> ppc-temp (replacing powerpc for this week) >> >> The ceph tree gained a conflict against Linus' tree. >> >> The net-next tree gained a conflict against the infiniband tree. >> >> The usb tree gained a build failure so I used the version from >> next-20130417. >> >> I added two merge fix patches after the gen-gpio tree. >> >> The ppc-temp tree gained a conflict against the metag tree. >> >> The akpm tree lost a patch that turned up elsewhere. >> >> >> > > Not sure what the root-cause for this call-trace is (see screenshot). > > This is reproducible when running my kernel build-script (4 > parallel-make-jobs). > > Any hints welcome! The panic handlers in our modeset code are pretty decent fubar - they take mutexes all over the place. So I think the backtrace you see there is actually a secondary effect. I've looked into fixing this up, but the issue is that drivers themselves have tons of state protected with mutexes, which all potentially affects the panic handler. So I've given up on that for now ... >>> >>> Thanks for taking care. >>> >>> On suspicion [1] I have reverted [2]... NOPE. >>> >>> - Sedat - >>> >>> [1] http://marc.info/?l=linux-kernel=136631921208895=2 >>> [2] >>> http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=5a90d1a95356de7a32acb2e5309ac579a891af8f >>> >> >> Hmmm, the issue seems to be gone with today's Linux-Next (next-20130419). >> My kernel-build is still running with no call-trace... >> > > NO, It's no good. > I tried to switch from SLUB to SLAB... ...and also from VIRT_CPU_ACCOUNTING_GEN to TICK_CPU_ACCOUNTING. 2x NOPE. In one kernel-build I saw in my console... semop(1): encountered an error: Identifier removed ...if this says sth. to you. - Sedat - - Sedat - > - Sedat - > > [1] http://www.youtube.com/watch?v=LwicaralvS0 > >> - Sedat - >> -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Thu, Apr 18, 2013 at 11:59 PM, Sedat Dilek wrote: > On Thu, Apr 18, 2013 at 9:48 PM, Daniel Vetter wrote: >> On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek wrote: >>> On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell >>> wrote: Hi all, Changes since 20130417: New Trees: rpmsg (actually added yesterday) ppc-temp (replacing powerpc for this week) The ceph tree gained a conflict against Linus' tree. The net-next tree gained a conflict against the infiniband tree. The usb tree gained a build failure so I used the version from next-20130417. I added two merge fix patches after the gen-gpio tree. The ppc-temp tree gained a conflict against the metag tree. The akpm tree lost a patch that turned up elsewhere. >>> >>> Not sure what the root-cause for this call-trace is (see screenshot). >>> >>> This is reproducible when running my kernel build-script (4 >>> parallel-make-jobs). >>> >>> Any hints welcome! >> >> The panic handlers in our modeset code are pretty decent fubar - they >> take mutexes all over the place. So I think the backtrace you see >> there is actually a secondary effect. I've looked into fixing this up, >> but the issue is that drivers themselves have tons of state protected >> with mutexes, which all potentially affects the panic handler. So I've >> given up on that for now ... > > Thanks for taking care. > > On suspicion [1] I have reverted [2]... NOPE. > > - Sedat - > > [1] http://marc.info/?l=linux-kernel=136631921208895=2 > [2] > http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=5a90d1a95356de7a32acb2e5309ac579a891af8f > Hmmm, the issue seems to be gone with today's Linux-Next (next-20130419). My kernel-build is still running with no call-trace... - Sedat - >> -Daniel >> -- >> Daniel Vetter >> Software Engineer, Intel Corporation >> +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Thu, Apr 18, 2013 at 11:59 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Thu, Apr 18, 2013 at 9:48 PM, Daniel Vetter daniel.vet...@ffwll.ch wrote: On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130417: New Trees: rpmsg (actually added yesterday) ppc-temp (replacing powerpc for this week) The ceph tree gained a conflict against Linus' tree. The net-next tree gained a conflict against the infiniband tree. The usb tree gained a build failure so I used the version from next-20130417. I added two merge fix patches after the gen-gpio tree. The ppc-temp tree gained a conflict against the metag tree. The akpm tree lost a patch that turned up elsewhere. Not sure what the root-cause for this call-trace is (see screenshot). This is reproducible when running my kernel build-script (4 parallel-make-jobs). Any hints welcome! The panic handlers in our modeset code are pretty decent fubar - they take mutexes all over the place. So I think the backtrace you see there is actually a secondary effect. I've looked into fixing this up, but the issue is that drivers themselves have tons of state protected with mutexes, which all potentially affects the panic handler. So I've given up on that for now ... Thanks for taking care. On suspicion [1] I have reverted [2]... NOPE. - Sedat - [1] http://marc.info/?l=linux-kernelm=136631921208895w=2 [2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=5a90d1a95356de7a32acb2e5309ac579a891af8f Hmmm, the issue seems to be gone with today's Linux-Next (next-20130419). My kernel-build is still running with no call-trace... - Sedat - -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 12:27 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 19, 2013 at 12:19 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Thu, Apr 18, 2013 at 11:59 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Thu, Apr 18, 2013 at 9:48 PM, Daniel Vetter daniel.vet...@ffwll.ch wrote: On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130417: New Trees: rpmsg (actually added yesterday) ppc-temp (replacing powerpc for this week) The ceph tree gained a conflict against Linus' tree. The net-next tree gained a conflict against the infiniband tree. The usb tree gained a build failure so I used the version from next-20130417. I added two merge fix patches after the gen-gpio tree. The ppc-temp tree gained a conflict against the metag tree. The akpm tree lost a patch that turned up elsewhere. Not sure what the root-cause for this call-trace is (see screenshot). This is reproducible when running my kernel build-script (4 parallel-make-jobs). Any hints welcome! The panic handlers in our modeset code are pretty decent fubar - they take mutexes all over the place. So I think the backtrace you see there is actually a secondary effect. I've looked into fixing this up, but the issue is that drivers themselves have tons of state protected with mutexes, which all potentially affects the panic handler. So I've given up on that for now ... Thanks for taking care. On suspicion [1] I have reverted [2]... NOPE. - Sedat - [1] http://marc.info/?l=linux-kernelm=136631921208895w=2 [2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=5a90d1a95356de7a32acb2e5309ac579a891af8f Hmmm, the issue seems to be gone with today's Linux-Next (next-20130419). My kernel-build is still running with no call-trace... NO, It's no good. I tried to switch from SLUB to SLAB... ...and also from VIRT_CPU_ACCOUNTING_GEN to TICK_CPU_ACCOUNTING. 2x NOPE. In one kernel-build I saw in my console... semop(1): encountered an error: Identifier removed ...if this says sth. to you. - Sedat - - Sedat - - Sedat - [1] http://www.youtube.com/watch?v=LwicaralvS0 - Sedat - -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 6:43 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 19, 2013 at 12:27 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Apr 19, 2013 at 12:19 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Thu, Apr 18, 2013 at 11:59 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Thu, Apr 18, 2013 at 9:48 PM, Daniel Vetter daniel.vet...@ffwll.ch wrote: On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130417: New Trees: rpmsg (actually added yesterday) ppc-temp (replacing powerpc for this week) The ceph tree gained a conflict against Linus' tree. The net-next tree gained a conflict against the infiniband tree. The usb tree gained a build failure so I used the version from next-20130417. I added two merge fix patches after the gen-gpio tree. The ppc-temp tree gained a conflict against the metag tree. The akpm tree lost a patch that turned up elsewhere. Not sure what the root-cause for this call-trace is (see screenshot). This is reproducible when running my kernel build-script (4 parallel-make-jobs). Any hints welcome! The panic handlers in our modeset code are pretty decent fubar - they take mutexes all over the place. So I think the backtrace you see there is actually a secondary effect. I've looked into fixing this up, but the issue is that drivers themselves have tons of state protected with mutexes, which all potentially affects the panic handler. So I've given up on that for now ... Thanks for taking care. On suspicion [1] I have reverted [2]... NOPE. - Sedat - [1] http://marc.info/?l=linux-kernelm=136631921208895w=2 [2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=5a90d1a95356de7a32acb2e5309ac579a891af8f Hmmm, the issue seems to be gone with today's Linux-Next (next-20130419). My kernel-build is still running with no call-trace... NO, It's no good. I tried to switch from SLUB to SLAB... ...and also from VIRT_CPU_ACCOUNTING_GEN to TICK_CPU_ACCOUNTING. 2x NOPE. In one kernel-build I saw in my console... semop(1): encountered an error: Identifier removed ...if this says sth. to you. [ CC folks from below thread ] I have found a thread called Re: ipc,sem: sysv semaphore scalability on LKML with a screenshot that shows the same call-trace. I followed it a bit. There is a patch in [3]... unconfirmed. Comments on the rcu read-lock and sem_lock() vs sem_unlock() from Linus. What's the status of this discussion? - Sedat - [1] https://lkml.org/lkml/2013/3/30/6 [2] http://i.imgur.com/uk6gmq1.jpg [3] https://lkml.org/lkml/2013/3/31/12 [4] https://lkml.org/lkml/2013/3/31/77 - Sedat - - Sedat - - Sedat - [1] http://www.youtube.com/watch?v=LwicaralvS0 - Sedat - -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On 04/19/2013 02:53 PM, Sedat Dilek wrote: On Fri, Apr 19, 2013 at 6:43 PM, Sedat Dilek sedat.di...@gmail.com wrote: I tried to switch from SLUB to SLAB... ...and also from VIRT_CPU_ACCOUNTING_GEN to TICK_CPU_ACCOUNTING. 2x NOPE. In one kernel-build I saw in my console... semop(1): encountered an error: Identifier removed ...if this says sth. to you. [ CC folks from below thread ] I have found a thread called Re: ipc,sem: sysv semaphore scalability on LKML with a screenshot that shows the same call-trace. I followed it a bit. There is a patch in [3]... unconfirmed. Comments on the rcu read-lock and sem_lock() vs sem_unlock() from Linus. What's the status of this discussion? - Sedat - [1] https://lkml.org/lkml/2013/3/30/6 [2] http://i.imgur.com/uk6gmq1.jpg [3] https://lkml.org/lkml/2013/3/31/12 [4] https://lkml.org/lkml/2013/3/31/77 I am at a conference right now, but when I get back I will check linux-next vs. all the fixes from the semaphore scalability email thread. I will gather up the not-yet-in-linux-next fixes, and will send them to Andrew for inclusion. No guarantee that those fixes are related to your problem, of course :) -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, 2013-04-19 at 15:19 -0400, Rik van Riel wrote: On 04/19/2013 02:53 PM, Sedat Dilek wrote: On Fri, Apr 19, 2013 at 6:43 PM, Sedat Dilek sedat.di...@gmail.com wrote: I tried to switch from SLUB to SLAB... ...and also from VIRT_CPU_ACCOUNTING_GEN to TICK_CPU_ACCOUNTING. 2x NOPE. In one kernel-build I saw in my console... semop(1): encountered an error: Identifier removed This looks like what Emmanuel was/is running into: https://lkml.org/lkml/2013/3/30/1 ...if this says sth. to you. [ CC folks from below thread ] I have found a thread called Re: ipc,sem: sysv semaphore scalability on LKML with a screenshot that shows the same call-trace. I followed it a bit. There is a patch in [3]... unconfirmed. Comments on the rcu read-lock and sem_lock() vs sem_unlock() from Linus. What's the status of this discussion? - Sedat - [1] https://lkml.org/lkml/2013/3/30/6 [2] http://i.imgur.com/uk6gmq1.jpg [3] https://lkml.org/lkml/2013/3/31/12 [4] https://lkml.org/lkml/2013/3/31/77 I am at a conference right now, but when I get back I will check linux-next vs. all the fixes from the semaphore scalability email thread. I'm back from the collab. summit, so AFAICT these still need to go in linux-next: ipc,sem: untangle RCU locking with find_alloc_undo: https://lkml.org/lkml/2013/3/28/275 ipc,sem: fix lockdep false positive: https://lkml.org/lkml/2013/3/29/119 ipc, sem: do not call sem_lock when bogus sma: https://lkml.org/lkml/2013/3/31/12 Thanks, Davidlohr -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 2:09 PM, Sedat Dilek sedat.di...@gmail.com wrote: I have applied all three patches and see still call-traces. New are apparmor related messages. Can you try the crazy rcu double-free debug hack? See https://lkml.org/lkml/2013/3/30/113 and I'm re-attaching the ugly-ass crazy hack patch here too.. Linus rcu-double-free-hack.patch Description: Binary data
Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 02:24:10PM -0700, Linus Torvalds wrote: On Fri, Apr 19, 2013 at 2:09 PM, Sedat Dilek sedat.di...@gmail.com wrote: I have applied all three patches and see still call-traces. New are apparmor related messages. Can you try the crazy rcu double-free debug hack? See https://lkml.org/lkml/2013/3/30/113 and I'm re-attaching the ugly-ass crazy hack patch here too.. Linus For whatever it is worth, CONFIG_DEBUG_OBJECTS_RCU_HEAD=y is intended to detect RCU double-freeing. But if it isn't helping for whatever reason, please let me know! Thanx, Paul -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 3:34 PM, Sedat Dilek sedat.di...@gmail.com wrote: See attached dmesg. This still has the bug Davidlohr pointed at: This looks like what Emmanuel was/is running into: https://lkml.org/lkml/2013/3/30/1 you need to move the IS_ERR() check before the sem_lock. Linus -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Sat, Apr 20, 2013 at 12:50 AM, Linus Torvalds torva...@linux-foundation.org wrote: On Fri, Apr 19, 2013 at 3:34 PM, Sedat Dilek sedat.di...@gmail.com wrote: See attached dmesg. This still has the bug Davidlohr pointed at: This looks like what Emmanuel was/is running into: https://lkml.org/lkml/2013/3/30/1 you need to move the IS_ERR() check before the sem_lock. Davidlohr pointed to this patch (tested the triplet): ipc, sem: do not call sem_lock when bogus sma: https://lkml.org/lkml/2013/3/31/12 Is that what you mean? - Sedat - Linus -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Fri, Apr 19, 2013 at 3:55 PM, Sedat Dilek sedat.di...@gmail.com wrote: Davidlohr pointed to this patch (tested the triplet): ipc, sem: do not call sem_lock when bogus sma: https://lkml.org/lkml/2013/3/31/12 Is that what you mean? Yup. Linus -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Thu, Apr 18, 2013 at 9:48 PM, Daniel Vetter wrote: > On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek wrote: >> On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell >> wrote: >>> Hi all, >>> >>> Changes since 20130417: >>> >>> New Trees: rpmsg (actually added yesterday) >>> ppc-temp (replacing powerpc for this week) >>> >>> The ceph tree gained a conflict against Linus' tree. >>> >>> The net-next tree gained a conflict against the infiniband tree. >>> >>> The usb tree gained a build failure so I used the version from >>> next-20130417. >>> >>> I added two merge fix patches after the gen-gpio tree. >>> >>> The ppc-temp tree gained a conflict against the metag tree. >>> >>> The akpm tree lost a patch that turned up elsewhere. >>> >>> >>> >> >> Not sure what the root-cause for this call-trace is (see screenshot). >> >> This is reproducible when running my kernel build-script (4 >> parallel-make-jobs). >> >> Any hints welcome! > > The panic handlers in our modeset code are pretty decent fubar - they > take mutexes all over the place. So I think the backtrace you see > there is actually a secondary effect. I've looked into fixing this up, > but the issue is that drivers themselves have tons of state protected > with mutexes, which all potentially affects the panic handler. So I've > given up on that for now ... Thanks for taking care. On suspicion [1] I have reverted [2]... NOPE. - Sedat - [1] http://marc.info/?l=linux-kernel=136631921208895=2 [2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=5a90d1a95356de7a32acb2e5309ac579a891af8f > -Daniel > -- > Daniel Vetter > Software Engineer, Intel Corporation > +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek wrote: > On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell > wrote: >> Hi all, >> >> Changes since 20130417: >> >> New Trees: rpmsg (actually added yesterday) >> ppc-temp (replacing powerpc for this week) >> >> The ceph tree gained a conflict against Linus' tree. >> >> The net-next tree gained a conflict against the infiniband tree. >> >> The usb tree gained a build failure so I used the version from >> next-20130417. >> >> I added two merge fix patches after the gen-gpio tree. >> >> The ppc-temp tree gained a conflict against the metag tree. >> >> The akpm tree lost a patch that turned up elsewhere. >> >> >> > > Not sure what the root-cause for this call-trace is (see screenshot). > > This is reproducible when running my kernel build-script (4 > parallel-make-jobs). > > Any hints welcome! The panic handlers in our modeset code are pretty decent fubar - they take mutexes all over the place. So I think the backtrace you see there is actually a secondary effect. I've looked into fixing this up, but the issue is that drivers themselves have tons of state protected with mutexes, which all potentially affects the panic handler. So I've given up on that for now ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130417: New Trees: rpmsg (actually added yesterday) ppc-temp (replacing powerpc for this week) The ceph tree gained a conflict against Linus' tree. The net-next tree gained a conflict against the infiniband tree. The usb tree gained a build failure so I used the version from next-20130417. I added two merge fix patches after the gen-gpio tree. The ppc-temp tree gained a conflict against the metag tree. The akpm tree lost a patch that turned up elsewhere. Not sure what the root-cause for this call-trace is (see screenshot). This is reproducible when running my kernel build-script (4 parallel-make-jobs). Any hints welcome! The panic handlers in our modeset code are pretty decent fubar - they take mutexes all over the place. So I think the backtrace you see there is actually a secondary effect. I've looked into fixing this up, but the issue is that drivers themselves have tons of state protected with mutexes, which all potentially affects the panic handler. So I've given up on that for now ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
On Thu, Apr 18, 2013 at 9:48 PM, Daniel Vetter daniel.vet...@ffwll.ch wrote: On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Changes since 20130417: New Trees: rpmsg (actually added yesterday) ppc-temp (replacing powerpc for this week) The ceph tree gained a conflict against Linus' tree. The net-next tree gained a conflict against the infiniband tree. The usb tree gained a build failure so I used the version from next-20130417. I added two merge fix patches after the gen-gpio tree. The ppc-temp tree gained a conflict against the metag tree. The akpm tree lost a patch that turned up elsewhere. Not sure what the root-cause for this call-trace is (see screenshot). This is reproducible when running my kernel build-script (4 parallel-make-jobs). Any hints welcome! The panic handlers in our modeset code are pretty decent fubar - they take mutexes all over the place. So I think the backtrace you see there is actually a secondary effect. I've looked into fixing this up, but the issue is that drivers themselves have tons of state protected with mutexes, which all potentially affects the panic handler. So I've given up on that for now ... Thanks for taking care. On suspicion [1] I have reverted [2]... NOPE. - Sedat - [1] http://marc.info/?l=linux-kernelm=136631921208895w=2 [2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=5a90d1a95356de7a32acb2e5309ac579a891af8f -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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/
