Hi all,
Changes since 20180731:
The pci tree gained a conflict against the pci-current tree.
The net-next tree gained a conflict against the bpf tree.
The block tree lost its build failure.
The staging tree still had its build failure due to an interaction with
the vfs tree for which I disabled CONFIG_EROFS_FS.
The kspp tree lost its build failure.
Non-merge commits (relative to Linus' tree): 10070
9137 files changed, 417605 insertions(+), 179996 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 286 trees (counting Linus' and 65 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 (c1d61e7fe376 Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi)
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 (9d3cce1e8b85 Linux 4.18-rc5)
Merging arc-current/for-curr (ec837d620c75 arc: fix type warnings in arc/mm/cache.c)
Merging arm-current/fixes (afc9f65e01cd ARM: 8781/1: Fix Thumb-2 syscall return for binutils 2.29+)
Merging arm64-fixes/for-next/fixes (c7513c2a2714 crypto/arm64: aes-ce-gcm - add missing kernel_neon_begin/end pair)
Merging m68k-current/for-linus (b12c8a70643f m68k: Set default dma mask for platform devices)
Merging powerpc-fixes/fixes (b03897cf318d powerpc/powernv: Fix save/restore of SPRG3 on entry/exit from stop (idle))
Merging sparc/master (c1d61e7fe376 Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi)
Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2)
Merging net/master (e39eb599998a Merge tag 'mlx5-fixes-2018-07-31' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux)
Merging bpf/master (2d55d614fcf5 net: xsk: don't return frames via the allocator on error)
Merging ipsec/master (25432eba9cd8 openvswitch: meter: Fix setting meter id for new entries)
Merging netfilter/master (101f0cd4f221 net: ena: Fix use of uninitialized DMA address bits field)
Merging ipvs/master (0026129c8629 rhashtable: add restart routine in rhashtable_free_and_destroy())
Merging wireless-drivers/master (299b6365a3b7 brcmfmac: fix regression in parsing NVRAM for multiple devices)
Merging mac80211/master (e31f6456c01c cfg80211: never ignore user regulatory hint)
Merging rdma-fixes/for-rc (addb8a6559f0 RDMA/uverbs: Expand primary and alt AV port checks)
Merging sound-current/for-linus (f59cf9a0551d ALSA: hda - Sleep for 10ms after entering D3 on Conexant codecs)
Merging sound-asoc-fixes/for-linus (3e4b165997cb Merge branch 'asoc-4.18' into asoc-linus)
Merging regmap-fixes/for-linus (d72e90f33aa4 Linux 4.18-rc6)
Merging regulator-fixes/for-linus (61b0049c348c Merge branch 'regulator-4.18' into regulator-linus)
Merging spi-fixes/for-linus (56e72c1eca32 Merge branch 'spi-4.18' into spi-linus)
Merging pci-current/for-linus (44bda4b7d26e PCI: Fix is_added/is_busmaster race condition)
Merging driver-core.current/driver-core-linus (acb1872577b3 Linux 4.18-rc7)
Merging tty.current/tty-linus (021c91791a5e Linux 4.18-rc3)
Merging usb.current/usb-linus (acb1872577b3 Linux 4.18-rc7)
Merging usb-gadget-fixes/fixes (acb1872577b3 Linux 4.18-rc7)
Merging usb-serial-fixes/usb-linus (9d3cce1e8b85 Linux 4.18-rc5)
Merging usb-chipidea-fixes/ci-for-usb-stable (a930d8bd94d8 usb: chipidea: Always build ULPI code)
Merging phy/fixes (ad5003300b07 phy: mapphone-mdm6600: Fix wrong enum used for status lines)
Merging staging.current/staging-linus (acb1872577b3 Linux 4.18-rc7)
Merging char-misc.current/char-misc-linus (9d3cce1e8b85 Linux 4.18-rc5)
Merging input-current/for-linus (384cf4285b34 Input: i8042 - add Lenovo LaVie Z to the i8042 reset list)
Merging crypto-current/master (46d8c4b28652 crypto: padlock-aes - Fix Nano workaround data corruption)
Merging ide/master (1aaccb5fa0ea Merge tag 'rtc-4.18' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux)
Merging vfio-fixes/for-linus (0e714d27786c vfio/pci: Fix potential Spectre v1)
Merging kselftest-fixes/fixes (ce397d215ccd Linux 4.18-rc1)
Merging modules-fixes/modules-linus (be71eda5383f module: Fix display of wrong module .text address)
Merging slave-dma-fixes/fixes (1e4b044d2251 Linux 4.18-rc4)
Merging backlight-fixes/for-backlight-fixes (ce397d215ccd Linux 4.18-rc1)
Merging mtd-fixes/master (aa7eee8a143a mtd: spi-nor: cadence-quadspi: Fix direct mode write timeouts)
Merging nand-fixes/nand/fixes (ee02f73e04c0 mtd: nand: atmel: Fix EDO mode check)
Merging spi-nor-fixes/spi-nor/fixes (7928b2cbe55b Linux 4.16-rc1)
Merging mfd-fixes/for-mfd-fixes (ce397d215ccd Linux 4.18-rc1)
Merging v4l-dvb-fixes/fixes (8eb0e6421958 media: v4l: vsp1: Fix deadlock in VSPDL DRM pipelines)
Merging reset-fixes/reset/fixes (26fce0557fa6 reset: imx7: Fix always writing bits as 0)
Merging mips-fixes/mips-fixes (d5ea019f8a38 Revert "MIPS: BCM47XX: Enable 74K Core ExternalSync for PCIe erratum")
Merging omap-fixes/fixes (d3f6daede246 ARM: dts: omap4-droid4: fix dts w.r.t. pwm)
Merging kvm-fixes/master (63aff65573d7 kvm: x86: vmx: fix vpid leak)
Merging kvms390-fixes/master (f4a551b72358 KVM: s390: vsie: fix < 8k check for the itdba)
Merging hwmon-fixes/hwmon (1e4b044d2251 Linux 4.18-rc4)
Merging nvdimm-fixes/libnvdimm-fixes (ee6581ceba7f nfit: fix unchecked dereference in acpi_nfit_ctl)
Merging btrfs-fixes/next-fixes (0b7162742121 Merge branch 'for-next-current-v4.18-20180717' into next-fixes)
Merging vfs-fixes/fixes (9ba546c01976 aio: don't expose __aio_sigset in uapi)
Merging dma-mapping-fixes/for-linus (7ec916f82c48 Revert "iommu/intel-iommu: Enable CONFIG_DMA_DIRECT_OPS=y and clean up intel_{alloc,free}_coherent()")
Merging drivers-x86-fixes/fixes (2502e5a02593 platform/x86: dell-laptop: Fix backlight detection)
Merging samsung-krzk-fixes/fixes (ce397d215ccd Linux 4.18-rc1)
Merging pinctrl-samsung-fixes/pinctrl-fixes (ce397d215ccd Linux 4.18-rc1)
Merging devicetree-fixes/dt/linus (b9952b5218ad of: overlay: update phandle cache on overlay apply and remove)
Merging scsi-fixes/fixes (15d258674b5c scsi: qedi: Fix a potential buffer overflow)
Merging drm-fixes/drm-fixes (acb1872577b3 Linux 4.18-rc7)
Merging drm-intel-fixes/for-linux-next-fixes (0ca9488193e6 drm/i915/glk: Add Quirk for GLK NUC HDMI port issues.)
Merging mmc-fixes/fixes (3b1074bf9817 mmc: mxcmmc: Fix missing parentheses and brace)
Merging rtc-fixes/rtc-fixes (fd6792bb022e rtc: fix alarm read and set offset)
Merging drm-misc-fixes/for-linux-next-fixes (a6a00918d4ad drm/vc4: Reset ->{x, y}_scaling[1] when dealing with uniplanar formats)
Merging kbuild/for-next (b56884dbdd97 Merge branch 'kconfig' into for-next)
Merging leaks/leaks-next (9f84a0f7f1a6 leaking_addresses: check if file name contains address)
Merging uuid/for-next (c0020756315e efi: switch to use new generic UUID API)
Merging dma-mapping/for-next (4d8bde883bfb OF: Don't set default coherent DMA mask)
Merging asm-generic/master (a71e7c44ffb7 io: change writeX_relaxed() to remove barriers)
Merging arc/for-next (4fbd8d194f06 Linux 4.15-rc1)
Merging arm/for-next (c705dcbf409c Merge branches 'clkdev', 'fixes', 'misc' and 'spectre' into for-next)
Merging arm-perf/for-next/perf (809092dc3e60 drivers/perf: arm-ccn: Use devm_ioremap_resource() to map memory)
Merging arm-soc/for-next (17f076bc11e5 ARM: Document merges)
Merging actions/for-next (35afadd11222 Merge branch 'v4.19/drivers' into next)
Merging alpine/alpine/for-next (7928b2cbe55b Linux 4.16-rc1)
Merging amlogic/for-next (47a99ae970bb Merge branch 'v4.19/dt64' into tmp/aml-rebuild)
Merging aspeed/for-next (c224edaa4a46 Merge branches 'defconfig-for-v4.19' and 'dt-for-v4.19' into for-next)
Merging at91/at91-next (f45853da06e3 Merge tag 'at91-ab-4.19-soc' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux into at91-next)
Merging bcm2835/for-next (5997adb14985 Merge branch anholt/bcm2835-defconfig-64-next into for-next)
CONFLICT (content): Merge conflict in drivers/hwmon/Kconfig
CONFLICT (content): Merge conflict in drivers/firmware/raspberrypi.c
Merging imx-mxs/for-next (7586f152bcad Merge branch 'imx/defconfig' into for-next)
Merging keystone/next (ed3bf0f321b9 Merge branch 'for_4.19/drivers-soc' into next)
Merging mediatek/for-next (b75253e66bc5 Merge branch 'v4.18-next/soc' into for-next)
Merging mvebu/for-next (23b7c60b80f6 Merge branch 'mvebu/dt64' into mvebu/for-next)
Merging omap/for-next (d356801075c5 Merge branch 'omap-for-v4.19/dt' into for-next)
Merging reset/reset/next (d903779b58be reset: meson: add meson audio arb driver)
Merging qcom/for-next (76b9e7f947f1 Merge tag 'qcom-defconfig-for-4.19' into all-for-4.19)
Merging realtek/for-next (2b6286eb7ab8 Merge branch 'v4.15/dt64' into next)
Merging renesas/next (7e58fb78c672 Merge branches 'fixes-for-v4.18', 'arm-defconfig-for-v4.19', 'arm-soc-for-v4.19', 'arm-dt-for-v4.19', 'arm64-defconfig-for-v4.19', 'arm64-dt-for-v4.19' and 'dt-bindings-for-v4.19' into next)
Merging rockchip/for-next (ed8fcd5d1466 Merge branch 'v4.19-armsoc/dts64' into for-next)
Merging samsung/for-next (bebc6082da0a Linux 4.14)
Merging samsung-krzk/for-next (babb70ce9674 Merge branch 'next/soc' into for-next)
Merging sunxi/sunxi/for-next (51c756fe7803 Merge branch 'sunxi/dt64-for-4.19' into sunxi/for-next)
Merging tegra/for-next (f29cfb31cf00 Merge branch for-4.19/arm64/dt into for-next)
Merging arm64/for-next/core (dcab90d90935 arm64: kexec: Add comment to explain use of __flush_icache_range())
CONFLICT (content): Merge conflict in arch/arm64/Makefile
Merging clk/clk-next (bbfbe38ec527 Merge branch 'clk-mvebu-periph-parent' into clk-next)
Merging clk-samsung/for-next (e8cf870f253b clk: samsung: simplify getting .drvdata)
Merging c6x/for-linux-next (31b02fe54206 c6x: switch to NO_BOOTMEM)
Merging h8300/h8300-next (54692056a201 h8300: Correct signature of test_bit())
Merging m68k/for-next (71a896687b85 m68k/defconfig: Update defconfigs for v4.18-rc6)
Merging m68knommu/for-next (58064e1f46b1 m68knommu: Fix typos in Coldfire 5272 DMA debug code)
Merging microblaze/next (9fe37714c13c microblaze: delete wrong comment about machine_early_init)
Merging mips/mips-next (84a7f564fa14 mips: dts: mscc: enable spi and NOR flash support on ocelot PCB123)
CONFLICT (content): Merge conflict in arch/mips/kernel/process.c
Merging nds32/next (d2516b16bcbc nds32: fix logic for module)
Merging nios2/for-next (3d9644ef9a0f nios2: Use read_persistent_clock64() instead of read_persistent_clock())
Merging openrisc/for-next (5600779ea5f3 openrisc: use generic dma_noncoherent_ops)
Merging parisc-hd/for-next (0fbd47b92b06 parisc: Add HAVE_REGS_AND_STACK_ACCESS_API feature)
Merging powerpc/next (cca3d5290ede tty: hvc: remove unexplained "just in case" spin delay)
CONFLICT (content): Merge conflict in drivers/vfio/vfio_iommu_spapr_tce.c
Merging hvc/topic/hvc (9f65b81f36e3 tty: hvc: introduce the hv_ops.flush operation for hvc drivers)
Merging fsl/next (c095ff93f901 powerpc/sysdev: change CPM GPIO to platform_device)
Merging risc-v/for-next (d72e90f33aa4 Linux 4.18-rc6)
Merging s390/features (05bb9f57357c s390/numa: move initial setup of node_to_cpumask_map)
Merging sparc-next/master (1aaccb5fa0ea Merge tag 'rtc-4.18' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux)
Merging sh/for-next (ac21fc2dcb40 sh: switch to NO_BOOTMEM)
Merging uml/linux-next (5ec9121195a4 um: Fix raw interface options)
Merging xtensa/xtensa-for-next (cb6db64ef5a9 Merge branch 'xtensa-dma-fixes' into xtensa-for-next)
Merging fscrypt/master (e1cc40e5d42a fscrypt: log the crypto algorithm implementations)
Merging befs/for-next (55d945e2e4aa fs: befs: btree: Fixed some coding standard issues)
Merging btrfs/next (29dcea88779c Linux 4.17)
Merging btrfs-kdave/for-next (2e68fcb12d4e Merge branch 'for-next-next-v4.19-20180724' into for-next-20180724)
Merging ceph/master (8b8f53af1ed9 ceph: fix dentry leak in splice_dentry())
Merging cifs/for-next (91dbee7e66f0 smb3: display bytes_read and bytes_written in smb3 stats)
Merging configfs/for-next (cc57c07343bd configfs: fix registered group removal)
Merging ecryptfs/next (5dcea554d5ce eCryptfs: fix a couple type promotion bugs)
Merging ext3/for_next (6aee47d7f61e Pull in fsnotify cleanups from Amir and new inotify IN_MASK_CREATE flag support.)
Merging ext4/dev (f4a79b7b4ab5 ext4: fix warning message in ext4_enable_quotas())
Merging f2fs/dev (715a33545d83 f2fs: fix to restrict mount condition when without CONFIG_QUOTA)
Merging fuse/for-next (963545357202 fuse: reduce allocation size for splice_write)
Merging jfs/jfs-next (bd646104ac5a jfs: use time64_t for otime)
Merging nfs/linux-next (a61246c96195 Fix error code in nfs_lookup_verify_inode())
Merging nfs-anna/linux-next (8e22b011b242 NFSv4: Mark the inode change attribute up to date in update_changeattr())
Merging nfsd/nfsd-next (32620db998a5 NFSD stop ongoing async copies on client shutdown)
Merging orangefs/for-next (f35cf2ab06b6 orangefs: remove redundant pointer orangefs_inode)
Merging overlayfs/overlayfs-next (989974c80457 ovl: Enable metadata only feature)
Merging ubifs/linux-next (f5a926dd5298 mtd: ubi: Update ubi-media.h to dual license)
Merging v9fs/9p-next (76450279848d 9p: fix whitespace issues)
Merging xfs/for-next (e666aa37f433 xfs: avoid COW fork extent lookups in writeback if the fork didn't change)
Merging file-locks/locks-next (1cf8e5de4055 fs/lock: show locks taken by processes from another pidns)
Merging vfs/for-next (334990db5207 Merge branches 'work.dcache', 'work.mount', 'work.misc' and 'work.mkdir' into for-next)
CONFLICT (content): Merge conflict in include/linux/fs.h
Merging vfs-miklos/next (0eb8af4916a5 vfs: use helper for calling f_op->fsync())
Merging printk/for-next (7973c51853f8 Merge branch 'for-4.19-nmi' into for-next)
Merging pci/next (a8de4147048a Merge branch 'remotes/lorenzo/pci/vmd')
CONFLICT (content): Merge conflict in drivers/pci/pci.h
CONFLICT (content): Merge conflict in drivers/pci/controller/pci-aardvark.c
Merging pstore/for-next/pstore (e698aaf37f9f pstore: fix crypto dependencies without compression)
Merging hid/for-next (4e9544262a93 Merge branch 'for-4.19/cougar' into for-next)
Merging i2c/i2c/for-next (9bb27593878f Merge branch 'i2c/for-4.19' into i2c/for-next)
Merging dmi/master (7f73745fec52 firmware: dmi: Add access to the SKU ID string)
Merging hwmon-staging/hwmon-next (12005ec33f3a hwmon: (iio_hwmon) Use devm functions)
Merging jc_docs/docs-next (d1634e1aedbc Documentation: vm.txt: Adding 'nr_hugepages_mempolicy' parameter description.)
Merging v4l-dvb/master (1d06352e18ef media: tvp5150: add g_std callback)
Merging v4l-dvb-next/master (f10379aad39e media: include/video/omapfb_dss.h: use IS_ENABLED())
Merging fbdev/fbdev-for-next (044e7ca20496 fbdev: omap2: omapfb: fix ifnullfree.cocci warnings)
Merging pm/linux-next (f5549675fa90 Merge branch 'pm-cpufreq-fixes' into linux-next)
Merging cpupower/cpupower (ce397d215ccd Linux 4.18-rc1)
Merging idle/next (8a5776a5f498 Linux 4.14-rc4)
Merging opp/opp/linux-next (c5c2a97b3ac7 PM / OPP: Update voltage in case freq == old_freq)
Merging thermal/next (5043f06ecec6 MAINTAINERS: Add Daniel Lezcano as designated reviewer for thermal)
Merging thermal-soc/next (542cdf406804 thermal: rcar_thermal: avoid NULL dereference in absence of IRQ resources)
Merging ieee1394/for-next (188775181bc0 firewire-ohci: work around oversized DMA reads on JMicron controllers)
Merging dlm/next (da3627c30d22 dlm: remove O_NONBLOCK flag in sctp_connect_to_sock)
Merging swiotlb/linux-next (4855c92dbb7b xen-swiotlb: fix the check condition for xen_swiotlb_free_coherent)
Merging rdma/for-next (854633165164 RDMA/core: Prefix _ib to IB/RoCE specific functions)
CONFLICT (content): Merge conflict in drivers/infiniband/core/uverbs_cmd.c
Merging net-next/master (e6476c21447c net: remove bogus RCU annotations on socket.wq)
CONFLICT (content): Merge conflict in tools/lib/bpf/btf.h
CONFLICT (content): Merge conflict in tools/lib/bpf/btf.c
CONFLICT (content): Merge conflict in tools/bpf/bpftool/map.c
CONFLICT (content): Merge conflict in net/smc/smc_ib.c
CONFLICT (content): Merge conflict in net/smc/smc_core.c
CONFLICT (content): Merge conflict in drivers/net/virtio_net.c
Merging bpf-next/master (fbeb1603bf4e bpf: verifier: MOV64 don't mark dst reg unbounded)
Merging ipsec-next/master (3f6bcc5162a1 act_bpf: Use kmemdup instead of duplicating it in tcf_bpf_init_from_ops)
Merging mlx5-next/mlx5-next (664000b6bb43 net/mlx5: Add support for flow table destination number)
Merging netfilter-next/master (4ed8eb6570a4 netfilter: nf_tables: Add native tproxy support)
Merging nfc-next/master (1f008cfec5d5 NFC: fdp: Fix unused variable warnings)
Merging ipvs-next/master (66c524acfb51 netfilter: conntrack: remove l3proto abstraction)
CONFLICT (content): Merge conflict in net/netfilter/Makefile
CONFLICT (content): Merge conflict in net/netfilter/Kconfig
CONFLICT (content): Merge conflict in net/ipv6/netfilter/Kconfig
Merging wireless-drivers-next/master (24ebfcbdd1ba rt2x00: remove redundant functions rt2x00mac_sta_{add/remove})
Merging bluetooth/master (b3cadaa485f0 Bluetooth: hidp: Fix handling of strncpy for hid->name information)
Merging mac80211-next/master (133bf90dbb8b mac80211: restrict delayed tailroom needed decrement)
Merging gfs2/for-next (3f30f929bb17 gfs2: cleanup: call gfs2_rgrp_ondisk2lvb from gfs2_rgrp_out)
Merging mtd/mtd/next (76a832254ab0 mtd: partitions: use DT info for parsing partitions with "compatible" prop)
Merging nand/nand/next (238e4f9e2f90 MAINTAINERS: drop Wenyou Yang from Atmel NAND driver support)
Merging spi-nor/spi-nor/next (69edac4ef4d1 mtd: spi-nor: cadence-quadspi: fix timeout handling)
Merging crypto/master (a47890899379 crypto: rmd320 - use swap macro in rmd320_transform)
CONFLICT (content): Merge conflict in drivers/net/ethernet/freescale/fs_enet/mac-fec.c
CONFLICT (content): Merge conflict in drivers/net/ethernet/freescale/fec_main.c
Merging drm/drm-next (15da09500a70 Merge branch 'drm-armada-devel' of git://git.armlinux.org.uk/~rmk/linux-arm into drm-next)
Applying: drm/i915/kvmgt: merge fixup for "Check the pfn got from vfio_pin_pages"
Merging drm-panel/drm/panel/for-next (e4bac408b084 drm/panel: simple: Add support for Winstar WF35LTIACD)
Merging drm-intel/for-linux-next (60548c554be2 drm/i915: Interactive RPS mode)
Merging drm-tegra/drm/tegra/for-next (6134534ca24f drm/tegra: Add kerneldoc for UAPI)
Merging drm-misc/for-linux-next (2ead1be54b22 drm/vkms: Fix connector leak at the module removal)
Merging drm-msm/msm-next (3e91a8b5c158 drm/msm/disp/dpu: fix two spelling mistakes)
Merging hdlcd/for-upstream/hdlcd (d664b851eb2b drm/arm/hdlcd: Reject atomic commits that disable only the plane)
Merging mali-dp/for-upstream/mali-dp (e368fc75c190 drm/arm/malidp: Added the late system pm functions)
Merging sunxi-drm/sunxi-drm/for-next (7dafb83edd32 Merge branches 'sunxi/drm-fixes-for-4.13' and 'sunxi/drm-for-4.14' into sunxi-drm/for-next)
Merging imx-drm/imx-drm/next (81f2b25addde drm/imx: Remove unused field imx_drm_device.pipes)
Merging etnaviv/etnaviv/next (f6ffbd4fc1a1 drm/etnaviv: replace license text with SPDX tags)
Merging kconfig/for-next (bebc6082da0a Linux 4.14)
Merging regmap/for-next (0bf0f09cc45b Merge branch 'regmap-4.19' into regmap-next)
Merging sound/for-next (a0a4959eb4e9 ALSA: usb-audio: Operate UAC3 Power Domains in PCM callbacks)
Merging sound-asoc/for-next (3d59909f9cf5 Merge branch 'asoc-4.19' into asoc-next)
Merging modules/modules-next (4d58e7034d19 ARM: module: fix modsign build error)
Merging input/next (955c594ed1a7 Input: pm8941-pwrkey - add resin entry)
Merging block/for-next (d6b29ac22880 Merge branch 'for-4.19/block' into for-next)
CONFLICT (content): Merge conflict in drivers/nvme/target/rdma.c
Applying: nvme-dma: merge fix up for replacement of max_sge
Merging lightnvm/for-next (1c6286f26301 lightnvm: fix some error code in pblk-init.c)
Merging device-mapper/for-next (63c8ecb6261a dm thin: include metadata_low_watermark threshold in pool status)
Merging pcmcia/pcmcia-next (c3a5307873d4 pcmcia: Use module_pcmcia_driver for scsi drivers)
Merging mmc/next (fee1ab56663c mmc: tmio: remove unneeded variable in tmio_mmc_start_command())
Merging kgdb/kgdb-next (2cf2f0d5b91f kdb: use memmove instead of overlapping memcpy)
Merging md/for-next (08edaaa6d6fa drivers/md/raid5: Do not disable irq on release_inactive_stripe_list() call)
Merging mfd/for-mfd-next (fe8166c92a5f mfd: sec-core: Export OF module alias table)
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/intel_display.h
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/Kconfig
Merging backlight/for-backlight-next (633786736ed5 backlight: pwm_bl: Fix uninitialized variable)
Merging battery/for-next (3d779180c692 power: supply: bq27xxx: Update comments)
Merging regulator/for-next (03a05cf9d2cb Merge branch 'regulator-4.19' into regulator-next)
Merging security/next-testing (d83c732fffc3 Merge branch 'smack-for-4.19-a' of https://github.com/cschaufler/next-smack into next-testing)
Merging apparmor/apparmor-next (24b87a16fee0 apparmor: Fix failure to audit context info in build_change_hat)
Merging integrity/next-integrity (3dd0f18c70d9 EVM: fix return value check in evm_write_xattrs())
Merging keys/keys-next (1e684d3820d8 pkcs7: Set the module licence to prevent tainting)
Merging selinux/next (631d2b490569 selinux: constify write_op[])
Merging tpmdd/next (ec403d8ed08c ima: Get rid of ima_used_chip and use ima_tpm_chip != NULL instead)
Merging watchdog/master (9d3cce1e8b85 Linux 4.18-rc5)
Merging iommu/next (a6d297302f78 Merge branches 'arm/shmobile', 'arm/renesas', 'arm/msm', 'arm/smmu', 'x86/amd', 'x86/vt-d' and 'core' into next)
Merging dwmw2-iommu/master (d8a5b80568a9 Linux 4.15)
Merging vfio/next (c1abca96b252 samples: mbochs: add DMA_SHARED_BUFFER dependency)
Merging trivial/for-next (75a24b822d38 kfifo: fix inaccurate comment)
Merging audit/next (baa2a4fdd525 audit: fix use-after-free in audit_add_watch)
Merging devicetree/for-next (791d3ef2e111 dt-bindings: remove 'interrupt-parent' from bindings)
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/net/can/xilinx_can.txt
Merging mailbox/mailbox-for-next (f83d1cfc8bcd mailbox/drivers/hisi: Consolidate the Kconfig for the MAILBOX)
Merging spi/for-next (30bb019e4e6b Merge branch 'spi-4.19' into spi-next)
Merging tip/auto-latest (02eb2e750ae5 Merge branch 'x86/timers')
CONFLICT (content): Merge conflict in tools/include/uapi/linux/bpf.h
Merging clockevents/clockevents/next (6bd9549d8a7d clocksource/drivers/arc_timer: Add comments about locking while read GFRC)
Merging edac/linux_next (345fb0a9a634 Merge tag 'edac_for_4.11' of git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp)
Merging edac-amd/for-next (190bd6e98afc EDAC, sb_edac: Add support for systems with segmented PCI buses)
Merging irqchip/irq/irqchip-next (30800b3a1fb1 irqchip/gic-v3-its: Reduce minimum LPI allocation to 1 for PCI devices)
Merging ftrace/for-next (a9235b544a0a ring-buffer: Fix typo in comment)
Merging rcu/rcu/next (d57fa29ddc3c Merge LKMM and RCU commits)
CONFLICT (content): Merge conflict in kernel/sched/core.c
Merging kvm/linux-next (6f0d349d922b Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net)
Merging kvm-arm/next (245715cbe83c KVM: arm/arm64: Fix lost IRQs from emulated physcial timer when blocked)
CONFLICT (content): Merge conflict in include/uapi/linux/kvm.h
CONFLICT (content): Merge conflict in arch/arm64/include/asm/cpucaps.h
Merging kvm-mips/next (dc44abd6aad2 KVM: MIPS/Emulate: Properly implement TLBR for T&E)
Merging kvm-ppc/kvm-ppc-next (b5c6f7607b90 KVM: PPC: Book3S HV: Read kvm->arch.emul_smt_mode under kvm->lock)
Merging kvms390/next (237584619366 Merge tag 'hlp_stage1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into kvms390/next)
Merging xen-tip/linux-next (2789e83c933d xen/gntdev: don't dereference a null gntdev_dmabuf on allocation failure)
Applying: xen/gntdev: fix up for attach callback API change
Merging percpu/for-next (b3a5d1119944 percpu_ref: Update doc to dissuade users from depending on internal RCU grace periods)
Merging workqueues/for-next (66448bc274ca workqueue: move function definitions within CONFIG_SMP block)
Merging drivers-x86/for-next (5788f7795911 platform/x86: dell-laptop: Fix backlight detection)
Merging chrome-platform/for-next (40291fb75123 Merge tag 'ib-platform-chrome-mfd-move-cros-ec-transport-for-4.19' into working-branch-for-4.19)
Merging hsi/for-next (ce397d215ccd Linux 4.18-rc1)
Merging leds/for-next (6f7b0bad8839 usb: simplify usbport trigger)
Merging ipmi/for-next (a4fb7ddc6356 ipmi: kcs_bmc: don't change device name)
Merging driver-core/driver-core-next (d2fc88a61b4e Merge 4.18-rc7 into driver-core-next)
CONFLICT (content): Merge conflict in fs/sysfs/group.c
CONFLICT (content): Merge conflict in drivers/iommu/ipmmu-vmsa.c
Merging usb/usb-next (479af3216315 usb: renesas_usbhs: Kconfig: convert to SPDX identifiers)
Merging usb-gadget/next (4ea438da76f4 usb: dwc3: gadget: Check MaxPacketSize from descriptor)
Merging usb-serial/usb-next (c8acfe0aadbe USB: serial: cp210x: implement GPIO support for CP2102N)
Merging usb-chipidea-next/ci-for-usb-next (ba0ab35a81de usb: chipidea: tegra: Use aligned DMA on Tegra114/124)
Merging phy-next/next (ec14b83a1ee4 phy: mvebu-cp110-comphy: switch to SPDX identifier)
Merging tty/tty-next (286d9b8c7d2e serial: 8250: Use cached port name directly in messages)
Merging char-misc/char-misc-next (7ceb1c37533e Drivers: hv: vmbus: add numa_node to sysfs)
Merging extcon/extcon-next (8a9dbb779fe8 extcon: Release locking when sending the notification of connector state)
Merging staging/staging-next (1c58e9cc5b56 staging:rtl8192u: Refactor enum DM_CCK_Rx_Path_Method - Style)
CONFLICT (modify/delete): drivers/staging/skein/skein_generic.c deleted in staging/staging-next and modified in HEAD. Version HEAD of drivers/staging/skein/skein_generic.c left in tree.
CONFLICT (content): Merge conflict in MAINTAINERS
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/iio/pressure/bmp085.txt
$ git rm -f drivers/staging/skein/skein_generic.c
Applying: disable erofs for now
Merging mux/for-next (23f13d082c17 Merge branch 'i2c-mux/for-next' into for-next)
CONFLICT (content): Merge conflict in MAINTAINERS
Merging slave-dma/next (fe2309127e8c Merge branch 'topic/renesas' into next)
Merging cgroup/for-next (e4f8d81c738d cgroup/tracing: Move taking of spin lock out of trace event handlers)
Merging scsi/for-next (103c7b7e0184 Merge branch 'misc' into for-next)
CONFLICT (modify/delete): lib/percpu_ida.c deleted in scsi/for-next and modified in HEAD. Version HEAD of lib/percpu_ida.c left in tree.
CONFLICT (content): Merge conflict in MAINTAINERS
$ git rm -f lib/percpu_ida.c
Merging scsi-mkp/for-next (c8a75afbf72e Revert "scsi: target/iscsi: Reduce number of __iscsit_free_cmd() callers")
Merging target-updates/for-next (1c130ae00b76 iscsi-target: make sure to wake up sleeping login worker)
Merging target-bva/for-next (60cc43fc8884 Linux 4.17-rc1)
Merging libata/for-next (ac41b3f0cec0 Merge branch 'for-4.19' into for-next)
Applying: Revert "ata: ahci_platform: allow disabling of hotplug to save power"
Merging vhost/linux-next (89da619bc18d virtio_balloon: fix another race between migration and ballooning)
Merging rpmsg/for-next (02c801b2fc28 Merge branches 'hwspinlock-next', 'rpmsg-next' and 'rproc-next' into for-next)
Merging gpio/for-next (aa3dc721a35a Merge branch 'devel' into for-next)
Merging pinctrl/for-next (e10382e245d4 Merge branch 'devel' into for-next)
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.txt
Merging pinctrl-samsung/for-next (b3793159249b dt-bindings: pinctrl: samsung: Add SPDX license identifier)
Merging pwm/for-next (19ad2b75c643 pwm: mxs: Switch to SPDX identifier)
Merging userns/for-next (04035aa33a12 proc: Don't change mount options on remount failure.)
CONFLICT (content): Merge conflict in fs/proc/root.c
CONFLICT (content): Merge conflict in fs/proc/internal.h
CONFLICT (content): Merge conflict in fs/proc/inode.c
Merging ktest/for-next (6cd110a91f52 ktest: Take submenu into account for grub2 menus)
Merging random/dev (b34fbaa92893 random: remove preempt disabled region)
Merging aio/master (2a8a98673c13 fs: aio: fix the increment of aio-nr and counting against aio-max-nr)
Merging kselftest/next (d2d49495b5c0 selftests: vDSO - fix to return KSFT_SKIP when test couldn't be run)
Merging y2038/y2038 (e264abeaf9da pstore: Remove bogus format string definition)
Merging livepatching/for-next (c72a7f515329 Merge branch 'for-4.18/upstream' into for-next)
Merging coresight/next (ad2a7edcccf5 dts: juno: Update coresight bindings)
CONFLICT (content): Merge conflict in include/linux/coresight.h
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/arm/coresight.txt
Merging rtc/rtc-next (ec9cf1b7a6af rtc: pcf85063: preserve control register value between stop and start)
Merging nvdimm/libnvdimm-for-next (64742dbc88dc Merge branch 'for-4.19/dax-memory-failure' into libnvdimm-for-next)
CONFLICT (content): Merge conflict in arch/x86/kernel/cpu/mcheck/mce.c
Merging at24/at24/for-next (a2b3bf4846e5 eeprom: at24: Add support for address-width property)
Merging ntb/ntb-next (b1ce023ae8a2 ntb_netdev: fix sleep time mismatch)
Merging kspp/for-next/kspp (163f88362143 Merge branch 'for-next/gcc-plugins' into for-next/kspp)
Merging init_task/init_task (e1e871aff3de Expand INIT_STRUCT_PID and remove)
Merging cisco/for-next (ce397d215ccd Linux 4.18-rc1)
Merging xarray/xarray (f039e3979325 radix tree: Remove radix_tree_clear_tags)
CONFLICT (content): Merge conflict in MAINTAINERS
Merging fsi/master (9840fcd8cc43 fsi: Prevent multiple concurrent rescans)
Merging siox/siox/next (1e4b044d2251 Linux 4.18-rc4)
Merging ida/ida (d69dd7ae5cd8 ida: Convert to XArray)
Merging akpm-current/current (5149c8506d15 ipc/util.c: update return value of ipc_getref from int to bool)
CONFLICT (content): Merge conflict in kernel/cgroup/cgroup.c
CONFLICT (content): Merge conflict in include/linux/sched.h
CONFLICT (content): Merge conflict in include/linux/bitops.h
CONFLICT (content): Merge conflict in fs/f2fs/data.c
CONFLICT (content): Merge conflict in drivers/xen/gntdev.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c
CONFLICT (content): Merge conflict in drivers/firmware/efi/libstub/Makefile
Applying: fixup for bit.h/bitops.h merge
$ git checkout -b akpm remotes/origin/akpm/master
Applying: drivers/hwtracing/intel_th/msu.c: change return type to vm_fault_t
Applying: fs/afs: use new return type vm_fault_t
Applying: treewide: correct "differenciate" and "instanciate" typos
Applying: fs/proc/vmcore.c: hide vmcoredd_mmap_dumps() for nommu builds
Applying: drivers/gpu/drm/gma500/: change return type to vm_fault_t
Applying: treewide: convert ISO_8859-1 text comments to utf-8
Applying: s390: ebcdic: convert comments to UTF-8
Applying: lib/fonts: convert comments to utf-8
Applying: mm: Change return type int to vm_fault_t for fault handlers
Applying: mm-change-return-type-int-to-vm_fault_t-for-fault-handlers-fix
Applying: vfs: replace current_kernel_time64 with ktime equivalent
Applying: drivers/media/platform/sti/delta/delta-ipc.c: fix read buffer overflow
Merging akpm/master (f05ffe68c365 drivers/media/platform/sti/delta/delta-ipc.c: fix read buffer overflow)
On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180731:
>
> The pci tree gained a conflict against the pci-current tree.
>
> The net-next tree gained a conflict against the bpf tree.
>
> The block tree lost its build failure.
>
> The staging tree still had its build failure due to an interaction with
> the vfs tree for which I disabled CONFIG_EROFS_FS.
>
> The kspp tree lost its build failure.
>
> Non-merge commits (relative to Linus' tree): 10070
> 9137 files changed, 417605 insertions(+), 179996 deletions(-)
>
> ----------------------------------------------------------------------------
>
The widespread kernel hang issues are still seen. I managed
to bisect it after working around the transient build failures.
Bisect log is attached below. Unfortunately, it doesn't help much.
The culprit is reported as:
2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
The preceding merge,
453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
checks out fine, as does the tip of scsi-next (commit 103c7b7e0184,
"Merge branch 'misc' into for-next"). No idea how to proceed.
Guenter
---
bisect (mips:malta_defconfig and i386):
# bad: [d9bd94c0bcaa42d9cace337590718afd22c47bcc] Add linux-next specific files for 20180801
# good: [acb1872577b346bd15ab3a3f8dff780d6cca4b70] Linux 4.18-rc7
git bisect start 'HEAD' 'v4.18-rc7'
# good: [f7952a1210bce43e88d69f371c6226aed481f307] Merge remote-tracking branch 'spi-nor/spi-nor/next'
git bisect good f7952a1210bce43e88d69f371c6226aed481f307
# good: [fa3bb608cd0d41a02583a7ceb3d162c4dee7e0e4] Merge remote-tracking branch 'spi/for-next'
git bisect good fa3bb608cd0d41a02583a7ceb3d162c4dee7e0e4
# good: [39c5cce976449c934b60e31cec9cea6986531b94] Merge remote-tracking branch 'char-misc/char-misc-next'
git bisect good 39c5cce976449c934b60e31cec9cea6986531b94
# good: [453f1d8211658b75542f4581759f022420bdaea8] Merge remote-tracking branch 'cgroup/for-next'
git bisect good 453f1d8211658b75542f4581759f022420bdaea8
# bad: [f11e9f9af170533e660c5deddccc4c494784c1fa] Merge remote-tracking branch 'nvdimm/libnvdimm-for-next'
git bisect bad f11e9f9af170533e660c5deddccc4c494784c1fa
# bad: [d8a758324b2e012cdba05b82ecbda6b84905f6ec] Merge remote-tracking branch 'rpmsg/for-next'
git bisect bad d8a758324b2e012cdba05b82ecbda6b84905f6ec
# good: [97fe222524f8fdbcc528b44d160d1df71d96af86] scsi: arcmsr: Fix error of resuming from hibernation for adapter type E
git bisect good 97fe222524f8fdbcc528b44d160d1df71d96af86
# bad: [2d542828c5e94490480b2900f8a0cb7a8c46afb0] Merge remote-tracking branch 'scsi/for-next'
git bisect bad 2d542828c5e94490480b2900f8a0cb7a8c46afb0
# good: [cc74e31d4147f26ead6ea06e4649d63a14edc0fe] scsi: lpfc: remove null check on nvmebuf
git bisect good cc74e31d4147f26ead6ea06e4649d63a14edc0fe
# good: [dc335a995527fb1ee9ec5649162b22cd1ce728ee] scsi: tcmu: unmap if dev is configured
git bisect good dc335a995527fb1ee9ec5649162b22cd1ce728ee
# good: [d92f5db64445ac4e2ce9a2cb7e6c929a5f4e712b] Merge branch 'misc' into for-next
git bisect good d92f5db64445ac4e2ce9a2cb7e6c929a5f4e712b
# good: [0e0d75267107e6a557ea9314d55bcff05a6ede44] scsi: tcmu: use u64 for dev_size
git bisect good 0e0d75267107e6a557ea9314d55bcff05a6ede44
# good: [c8a75afbf72ee4c16dad5339f55f62095879f207] Revert "scsi: target/iscsi: Reduce number of __iscsit_free_cmd() callers"
git bisect good c8a75afbf72ee4c16dad5339f55f62095879f207
# good: [103c7b7e01849d3c5bc998168ccd4df2c443d24b] Merge branch 'misc' into for-next
git bisect good 103c7b7e01849d3c5bc998168ccd4df2c443d24b
# first bad commit: [2d542828c5e94490480b2900f8a0cb7a8c46afb0] Merge remote-tracking branch 'scsi/for-next'
On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
> On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20180731:
> >
> > The pci tree gained a conflict against the pci-current tree.
> >
> > The net-next tree gained a conflict against the bpf tree.
> >
> > The block tree lost its build failure.
> >
> > The staging tree still had its build failure due to an interaction
> > with
> > the vfs tree for which I disabled CONFIG_EROFS_FS.
> >
> > The kspp tree lost its build failure.
> >
> > Non-merge commits (relative to Linus' tree): 10070
> > 9137 files changed, 417605 insertions(+), 179996 deletions(-)
> >
> > -----------------------------------------------------------------
> > -----------
> >
>
> The widespread kernel hang issues are still seen. I managed
> to bisect it after working around the transient build failures.
> Bisect log is attached below. Unfortunately, it doesn't help much.
> The culprit is reported as:
>
> 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
>
> The preceding merge,
>
> 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
>
> checks out fine, as does the tip of scsi-next (commit 103c7b7e0184,
> "Merge branch 'misc' into for-next"). No idea how to proceed.
This sounds like you may have a problem with this patch:
commit d5038a13eca72fb216c07eb717169092e92284f1
Author: Johannes Thumshirn <[email protected]>
Date: Wed Jul 4 10:53:56 2018 +0200
scsi: core: switch to scsi-mq by default
To verify, boot with the additional kernel parameter
scsi_mod.use_blk_mq=0
Which will reverse the effect of the above patch.
We already have one report of this patch causing boot failures:
https://marc.info/?t=153305327000002
So I've added linux-scsi to see if they want any more information.
James
>
> Guenter
>
> ---
> bisect (mips:malta_defconfig and i386):
>
> # bad: [d9bd94c0bcaa42d9cace337590718afd22c47bcc] Add linux-next
> specific files for 20180801
> # good: [acb1872577b346bd15ab3a3f8dff780d6cca4b70] Linux 4.18-rc7
> git bisect start 'HEAD' 'v4.18-rc7'
> # good: [f7952a1210bce43e88d69f371c6226aed481f307] Merge remote-
> tracking branch 'spi-nor/spi-nor/next'
> git bisect good f7952a1210bce43e88d69f371c6226aed481f307
> # good: [fa3bb608cd0d41a02583a7ceb3d162c4dee7e0e4] Merge remote-
> tracking branch 'spi/for-next'
> git bisect good fa3bb608cd0d41a02583a7ceb3d162c4dee7e0e4
> # good: [39c5cce976449c934b60e31cec9cea6986531b94] Merge remote-
> tracking branch 'char-misc/char-misc-next'
> git bisect good 39c5cce976449c934b60e31cec9cea6986531b94
> # good: [453f1d8211658b75542f4581759f022420bdaea8] Merge remote-
> tracking branch 'cgroup/for-next'
> git bisect good 453f1d8211658b75542f4581759f022420bdaea8
> # bad: [f11e9f9af170533e660c5deddccc4c494784c1fa] Merge remote-
> tracking branch 'nvdimm/libnvdimm-for-next'
> git bisect bad f11e9f9af170533e660c5deddccc4c494784c1fa
> # bad: [d8a758324b2e012cdba05b82ecbda6b84905f6ec] Merge remote-
> tracking branch 'rpmsg/for-next'
> git bisect bad d8a758324b2e012cdba05b82ecbda6b84905f6ec
> # good: [97fe222524f8fdbcc528b44d160d1df71d96af86] scsi: arcmsr: Fix
> error of resuming from hibernation for adapter type E
> git bisect good 97fe222524f8fdbcc528b44d160d1df71d96af86
> # bad: [2d542828c5e94490480b2900f8a0cb7a8c46afb0] Merge remote-
> tracking branch 'scsi/for-next'
> git bisect bad 2d542828c5e94490480b2900f8a0cb7a8c46afb0
> # good: [cc74e31d4147f26ead6ea06e4649d63a14edc0fe] scsi: lpfc: remove
> null check on nvmebuf
> git bisect good cc74e31d4147f26ead6ea06e4649d63a14edc0fe
> # good: [dc335a995527fb1ee9ec5649162b22cd1ce728ee] scsi: tcmu: unmap
> if dev is configured
> git bisect good dc335a995527fb1ee9ec5649162b22cd1ce728ee
> # good: [d92f5db64445ac4e2ce9a2cb7e6c929a5f4e712b] Merge branch
> 'misc' into for-next
> git bisect good d92f5db64445ac4e2ce9a2cb7e6c929a5f4e712b
> # good: [0e0d75267107e6a557ea9314d55bcff05a6ede44] scsi: tcmu: use
> u64 for dev_size
> git bisect good 0e0d75267107e6a557ea9314d55bcff05a6ede44
> # good: [c8a75afbf72ee4c16dad5339f55f62095879f207] Revert "scsi:
> target/iscsi: Reduce number of __iscsit_free_cmd() callers"
> git bisect good c8a75afbf72ee4c16dad5339f55f62095879f207
> # good: [103c7b7e01849d3c5bc998168ccd4df2c443d24b] Merge branch
> 'misc' into for-next
> git bisect good 103c7b7e01849d3c5bc998168ccd4df2c443d24b
> # first bad commit: [2d542828c5e94490480b2900f8a0cb7a8c46afb0] Merge
> remote-tracking branch 'scsi/for-next'
>
On Wed, 2018-08-01 at 15:52 -0700, James Bottomley wrote:
> On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
> > On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20180731:
> > >
> > > The pci tree gained a conflict against the pci-current tree.
> > >
> > > The net-next tree gained a conflict against the bpf tree.
> > >
> > > The block tree lost its build failure.
> > >
> > > The staging tree still had its build failure due to an
> > > interaction
> > > with
> > > the vfs tree for which I disabled CONFIG_EROFS_FS.
> > >
> > > The kspp tree lost its build failure.
> > >
> > > Non-merge commits (relative to Linus' tree): 10070
> > > 9137 files changed, 417605 insertions(+), 179996 deletions(-)
> > >
> > > -----------------------------------------------------------------
> > > -----------
> > >
> >
> > The widespread kernel hang issues are still seen. I managed
> > to bisect it after working around the transient build failures.
> > Bisect log is attached below. Unfortunately, it doesn't help much.
> > The culprit is reported as:
> >
> > 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
> >
> > The preceding merge,
> >
> > 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
> >
> > checks out fine, as does the tip of scsi-next (commit 103c7b7e0184,
> > "Merge branch 'misc' into for-next"). No idea how to proceed.
So what seems to be happening to cause this is that there's a patch
somewhere between the merge base of my scsi-next series and the next
tree and the patch just before scsi-next was actually merged that
actually causes a boot failure with blk-mq enabled. Could you try to
find this patch? I think the way to do it is to try to bisect this
range of linux-next using the command line
scsi_mod.use_blk_mq=1
Which forces block mq to be the default and seeing where the first boot
failure is (you don't need my scsi-next tree merged to do this because
all the offending patch does is flip the default state of the above
flag).
James
On Wed, Aug 01, 2018 at 03:52:45PM -0700, James Bottomley wrote:
> On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
> > On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20180731:
> > >
> > > The pci tree gained a conflict against the pci-current tree.
> > >
> > > The net-next tree gained a conflict against the bpf tree.
> > >
> > > The block tree lost its build failure.
> > >
> > > The staging tree still had its build failure due to an interaction
> > > with
> > > the vfs tree for which I disabled CONFIG_EROFS_FS.
> > >
> > > The kspp tree lost its build failure.
> > >
> > > Non-merge commits (relative to Linus' tree): 10070
> > > ?9137 files changed, 417605 insertions(+), 179996 deletions(-)
> > >
> > > -----------------------------------------------------------------
> > > -----------
> > >
> >
> > The widespread kernel hang issues are still seen. I managed
> > to bisect it after working around the transient build failures.
> > Bisect log is attached below. Unfortunately, it doesn't help much.
> > The culprit is reported as:
> >
> > 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
> >
> > The preceding merge,
> >
> > 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
> >
> > checks out fine, as does the tip of scsi-next (commit 103c7b7e0184,
> > "Merge branch 'misc' into for-next"). No idea how to proceed.
>
> This sounds like you may have a problem with this patch:
>
> ????commit d5038a13eca72fb216c07eb717169092e92284f1
> ?????Author: Johannes Thumshirn <[email protected]>
> ?????Date:???Wed Jul 4 10:53:56 2018 +0200
>
> ?????????scsi: core: switch to scsi-mq by default
>
> To verify, boot with the additional kernel parameter
>
> scsi_mod.use_blk_mq=0
>
> Which will reverse the effect of the above patch.
>
Yes, that fixes the problem.
Guenter
> We already have one report of this patch causing boot failures:
>
> https://marc.info/?t=153305327000002
>
> So I've added linux-scsi to see if they want any more information.
>
> James
>
> >
> > Guenter
> >
> > ---
> > bisect (mips:malta_defconfig and i386):
> >
> > # bad: [d9bd94c0bcaa42d9cace337590718afd22c47bcc] Add linux-next
> > specific files for 20180801
> > # good: [acb1872577b346bd15ab3a3f8dff780d6cca4b70] Linux 4.18-rc7
> > git bisect start 'HEAD' 'v4.18-rc7'
> > # good: [f7952a1210bce43e88d69f371c6226aed481f307] Merge remote-
> > tracking branch 'spi-nor/spi-nor/next'
> > git bisect good f7952a1210bce43e88d69f371c6226aed481f307
> > # good: [fa3bb608cd0d41a02583a7ceb3d162c4dee7e0e4] Merge remote-
> > tracking branch 'spi/for-next'
> > git bisect good fa3bb608cd0d41a02583a7ceb3d162c4dee7e0e4
> > # good: [39c5cce976449c934b60e31cec9cea6986531b94] Merge remote-
> > tracking branch 'char-misc/char-misc-next'
> > git bisect good 39c5cce976449c934b60e31cec9cea6986531b94
> > # good: [453f1d8211658b75542f4581759f022420bdaea8] Merge remote-
> > tracking branch 'cgroup/for-next'
> > git bisect good 453f1d8211658b75542f4581759f022420bdaea8
> > # bad: [f11e9f9af170533e660c5deddccc4c494784c1fa] Merge remote-
> > tracking branch 'nvdimm/libnvdimm-for-next'
> > git bisect bad f11e9f9af170533e660c5deddccc4c494784c1fa
> > # bad: [d8a758324b2e012cdba05b82ecbda6b84905f6ec] Merge remote-
> > tracking branch 'rpmsg/for-next'
> > git bisect bad d8a758324b2e012cdba05b82ecbda6b84905f6ec
> > # good: [97fe222524f8fdbcc528b44d160d1df71d96af86] scsi: arcmsr: Fix
> > error of resuming from hibernation for adapter type E
> > git bisect good 97fe222524f8fdbcc528b44d160d1df71d96af86
> > # bad: [2d542828c5e94490480b2900f8a0cb7a8c46afb0] Merge remote-
> > tracking branch 'scsi/for-next'
> > git bisect bad 2d542828c5e94490480b2900f8a0cb7a8c46afb0
> > # good: [cc74e31d4147f26ead6ea06e4649d63a14edc0fe] scsi: lpfc: remove
> > null check on nvmebuf
> > git bisect good cc74e31d4147f26ead6ea06e4649d63a14edc0fe
> > # good: [dc335a995527fb1ee9ec5649162b22cd1ce728ee] scsi: tcmu: unmap
> > if dev is configured
> > git bisect good dc335a995527fb1ee9ec5649162b22cd1ce728ee
> > # good: [d92f5db64445ac4e2ce9a2cb7e6c929a5f4e712b] Merge branch
> > 'misc' into for-next
> > git bisect good d92f5db64445ac4e2ce9a2cb7e6c929a5f4e712b
> > # good: [0e0d75267107e6a557ea9314d55bcff05a6ede44] scsi: tcmu: use
> > u64 for dev_size
> > git bisect good 0e0d75267107e6a557ea9314d55bcff05a6ede44
> > # good: [c8a75afbf72ee4c16dad5339f55f62095879f207] Revert "scsi:
> > target/iscsi: Reduce number of __iscsit_free_cmd() callers"
> > git bisect good c8a75afbf72ee4c16dad5339f55f62095879f207
> > # good: [103c7b7e01849d3c5bc998168ccd4df2c443d24b] Merge branch
> > 'misc' into for-next
> > git bisect good 103c7b7e01849d3c5bc998168ccd4df2c443d24b
> > # first bad commit: [2d542828c5e94490480b2900f8a0cb7a8c46afb0] Merge
> > remote-tracking branch 'scsi/for-next'
> >
>
On Thu, Aug 2, 2018 at 7:47 AM, Guenter Roeck <[email protected]> wrote:
> On Wed, Aug 01, 2018 at 03:52:45PM -0700, James Bottomley wrote:
>> On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
>> > On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell wrote:
>> > > Hi all,
>> > >
>> > > Changes since 20180731:
>> > >
>> > > The pci tree gained a conflict against the pci-current tree.
>> > >
>> > > The net-next tree gained a conflict against the bpf tree.
>> > >
>> > > The block tree lost its build failure.
>> > >
>> > > The staging tree still had its build failure due to an interaction
>> > > with
>> > > the vfs tree for which I disabled CONFIG_EROFS_FS.
>> > >
>> > > The kspp tree lost its build failure.
>> > >
>> > > Non-merge commits (relative to Linus' tree): 10070
>> > > 9137 files changed, 417605 insertions(+), 179996 deletions(-)
>> > >
>> > > -----------------------------------------------------------------
>> > > -----------
>> > >
>> >
>> > The widespread kernel hang issues are still seen. I managed
>> > to bisect it after working around the transient build failures.
>> > Bisect log is attached below. Unfortunately, it doesn't help much.
>> > The culprit is reported as:
>> >
>> > 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
>> >
>> > The preceding merge,
>> >
>> > 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
>> >
>> > checks out fine, as does the tip of scsi-next (commit 103c7b7e0184,
>> > "Merge branch 'misc' into for-next"). No idea how to proceed.
>>
>> This sounds like you may have a problem with this patch:
>>
>> commit d5038a13eca72fb216c07eb717169092e92284f1
>> Author: Johannes Thumshirn <[email protected]>
>> Date: Wed Jul 4 10:53:56 2018 +0200
>>
>> scsi: core: switch to scsi-mq by default
>>
>> To verify, boot with the additional kernel parameter
>>
>> scsi_mod.use_blk_mq=0
>>
>> Which will reverse the effect of the above patch.
>>
> Yes, that fixes the problem.
That may not the root cause, given this issue is only started to
see from next-20180731, but d5038a13eca7 (scsi: core: switch to
scsi-mq by default)
has been in -next for quite a while.
Seems something new causes this issue.
Thanks,
Ming Lei
On Thu, 2018-08-02 at 07:57 +0800, Ming Lei wrote:
> On Thu, Aug 2, 2018 at 7:47 AM, Guenter Roeck <[email protected]>
> wrote:
> > On Wed, Aug 01, 2018 at 03:52:45PM -0700, James Bottomley wrote:
> > > On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
> > > > On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell
> > > > wrote:
> > > > > Hi all,
> > > > >
> > > > > Changes since 20180731:
> > > > >
> > > > > The pci tree gained a conflict against the pci-current tree.
> > > > >
> > > > > The net-next tree gained a conflict against the bpf tree.
> > > > >
> > > > > The block tree lost its build failure.
> > > > >
> > > > > The staging tree still had its build failure due to an
> > > > > interaction
> > > > > with
> > > > > the vfs tree for which I disabled CONFIG_EROFS_FS.
> > > > >
> > > > > The kspp tree lost its build failure.
> > > > >
> > > > > Non-merge commits (relative to Linus' tree): 10070
> > > > > 9137 files changed, 417605 insertions(+), 179996 deletions(-
> > > > > )
> > > > >
> > > > > -----------------------------------------------------------
> > > > > ------
> > > > > -----------
> > > > >
> > > >
> > > > The widespread kernel hang issues are still seen. I managed
> > > > to bisect it after working around the transient build failures.
> > > > Bisect log is attached below. Unfortunately, it doesn't help
> > > > much.
> > > > The culprit is reported as:
> > > >
> > > > 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
> > > >
> > > > The preceding merge,
> > > >
> > > > 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
> > > >
> > > > checks out fine, as does the tip of scsi-next (commit
> > > > 103c7b7e0184,
> > > > "Merge branch 'misc' into for-next"). No idea how to proceed.
> > >
> > > This sounds like you may have a problem with this patch:
> > >
> > > commit d5038a13eca72fb216c07eb717169092e92284f1
> > > Author: Johannes Thumshirn <[email protected]>
> > > Date: Wed Jul 4 10:53:56 2018 +0200
> > >
> > > scsi: core: switch to scsi-mq by default
> > >
> > > To verify, boot with the additional kernel parameter
> > >
> > > scsi_mod.use_blk_mq=0
> > >
> > > Which will reverse the effect of the above patch.
> > >
> >
> > Yes, that fixes the problem.
>
> That may not the root cause, given this issue is only started to
> see from next-20180731, but d5038a13eca7 (scsi: core: switch to
> scsi-mq by default)
> has been in -next for quite a while.
>
> Seems something new causes this issue.
Read my other email about how to find this.
https://marc.info/?l=linux-scsi&m=153316446223676
Now that we've confirmed the issue, Gunter, could you attempt to bisect
it as that email describes?
Thanks,
James
Hi all,
On Wed, 01 Aug 2018 16:00:54 -0700 James Bottomley <[email protected]> wrote:
>
> So what seems to be happening to cause this is that there's a patch
> somewhere between the merge base of my scsi-next series and the next
> tree and the patch just before scsi-next was actually merged that
> actually causes a boot failure with blk-mq enabled. Could you try to
> find this patch? I think the way to do it is to try to bisect this
> range of linux-next using the command line
>
> scsi_mod.use_blk_mq=1
>
> Which forces block mq to be the default and seeing where the first boot
> failure is (you don't need my scsi-next tree merged to do this because
> all the offending patch does is flip the default state of the above
> flag).
So this means using v4.8-rc1 as the first good commit and 453f1d821165
("Merge remote-tracking branch 'cgroup/for-next'") as the first bad
(assuming that this latter fails to boot with "scsi_mod.use_blk_mq=1").
--
Cheers,
Stephen Rothwell
On 08/01/2018 04:57 PM, Ming Lei wrote:
> On Thu, Aug 2, 2018 at 7:47 AM, Guenter Roeck <[email protected]> wrote:
>> On Wed, Aug 01, 2018 at 03:52:45PM -0700, James Bottomley wrote:
>>> On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
>>>> On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell wrote:
>>>>> Hi all,
>>>>>
>>>>> Changes since 20180731:
>>>>>
>>>>> The pci tree gained a conflict against the pci-current tree.
>>>>>
>>>>> The net-next tree gained a conflict against the bpf tree.
>>>>>
>>>>> The block tree lost its build failure.
>>>>>
>>>>> The staging tree still had its build failure due to an interaction
>>>>> with
>>>>> the vfs tree for which I disabled CONFIG_EROFS_FS.
>>>>>
>>>>> The kspp tree lost its build failure.
>>>>>
>>>>> Non-merge commits (relative to Linus' tree): 10070
>>>>> 9137 files changed, 417605 insertions(+), 179996 deletions(-)
>>>>>
>>>>> -----------------------------------------------------------------
>>>>> -----------
>>>>>
>>>>
>>>> The widespread kernel hang issues are still seen. I managed
>>>> to bisect it after working around the transient build failures.
>>>> Bisect log is attached below. Unfortunately, it doesn't help much.
>>>> The culprit is reported as:
>>>>
>>>> 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
>>>>
>>>> The preceding merge,
>>>>
>>>> 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
>>>>
>>>> checks out fine, as does the tip of scsi-next (commit 103c7b7e0184,
>>>> "Merge branch 'misc' into for-next"). No idea how to proceed.
>>>
>>> This sounds like you may have a problem with this patch:
>>>
>>> commit d5038a13eca72fb216c07eb717169092e92284f1
>>> Author: Johannes Thumshirn <[email protected]>
>>> Date: Wed Jul 4 10:53:56 2018 +0200
>>>
>>> scsi: core: switch to scsi-mq by default
>>>
>>> To verify, boot with the additional kernel parameter
>>>
>>> scsi_mod.use_blk_mq=0
>>>
>>> Which will reverse the effect of the above patch.
>>>
>> Yes, that fixes the problem.
>
> That may not the root cause, given this issue is only started to
> see from next-20180731, but d5038a13eca7 (scsi: core: switch to
> scsi-mq by default)
> has been in -next for quite a while.
>
> Seems something new causes this issue.
>
Agreed. I should have said "fixes the symptom". I'll try to bisect
with scsi_mod.use_blk_mq=1 as suggested by James.
Guenter
On 08/01/2018 05:03 PM, James Bottomley wrote:
> On Thu, 2018-08-02 at 07:57 +0800, Ming Lei wrote:
>> On Thu, Aug 2, 2018 at 7:47 AM, Guenter Roeck <[email protected]>
>> wrote:
>>> On Wed, Aug 01, 2018 at 03:52:45PM -0700, James Bottomley wrote:
>>>> On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
>>>>> On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell
>>>>> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Changes since 20180731:
>>>>>>
>>>>>> The pci tree gained a conflict against the pci-current tree.
>>>>>>
>>>>>> The net-next tree gained a conflict against the bpf tree.
>>>>>>
>>>>>> The block tree lost its build failure.
>>>>>>
>>>>>> The staging tree still had its build failure due to an
>>>>>> interaction
>>>>>> with
>>>>>> the vfs tree for which I disabled CONFIG_EROFS_FS.
>>>>>>
>>>>>> The kspp tree lost its build failure.
>>>>>>
>>>>>> Non-merge commits (relative to Linus' tree): 10070
>>>>>> 9137 files changed, 417605 insertions(+), 179996 deletions(-
>>>>>> )
>>>>>>
>>>>>> -----------------------------------------------------------
>>>>>> ------
>>>>>> -----------
>>>>>>
>>>>>
>>>>> The widespread kernel hang issues are still seen. I managed
>>>>> to bisect it after working around the transient build failures.
>>>>> Bisect log is attached below. Unfortunately, it doesn't help
>>>>> much.
>>>>> The culprit is reported as:
>>>>>
>>>>> 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
>>>>>
>>>>> The preceding merge,
>>>>>
>>>>> 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
>>>>>
>>>>> checks out fine, as does the tip of scsi-next (commit
>>>>> 103c7b7e0184,
>>>>> "Merge branch 'misc' into for-next"). No idea how to proceed.
>>>>
>>>> This sounds like you may have a problem with this patch:
>>>>
>>>> commit d5038a13eca72fb216c07eb717169092e92284f1
>>>> Author: Johannes Thumshirn <[email protected]>
>>>> Date: Wed Jul 4 10:53:56 2018 +0200
>>>>
>>>> scsi: core: switch to scsi-mq by default
>>>>
>>>> To verify, boot with the additional kernel parameter
>>>>
>>>> scsi_mod.use_blk_mq=0
>>>>
>>>> Which will reverse the effect of the above patch.
>>>>
>>>
>>> Yes, that fixes the problem.
>>
>> That may not the root cause, given this issue is only started to
>> see from next-20180731, but d5038a13eca7 (scsi: core: switch to
>> scsi-mq by default)
>> has been in -next for quite a while.
>>
>> Seems something new causes this issue.
>
> Read my other email about how to find this.
>
> https://marc.info/?l=linux-scsi&m=153316446223676
>
> Now that we've confirmed the issue, Gunter, could you attempt to bisect
> it as that email describes?
>
Already working on it.
Guenter
On 08/01/2018 05:05 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 01 Aug 2018 16:00:54 -0700 James Bottomley <[email protected]> wrote:
>>
>> So what seems to be happening to cause this is that there's a patch
>> somewhere between the merge base of my scsi-next series and the next
>> tree and the patch just before scsi-next was actually merged that
>> actually causes a boot failure with blk-mq enabled. Could you try to
>> find this patch? I think the way to do it is to try to bisect this
>> range of linux-next using the command line
>>
>> scsi_mod.use_blk_mq=1
>>
>> Which forces block mq to be the default and seeing where the first boot
>> failure is (you don't need my scsi-next tree merged to do this because
>> all the offending patch does is flip the default state of the above
>> flag).
>
> So this means using v4.8-rc1 as the first good commit and 453f1d821165
> ("Merge remote-tracking branch 'cgroup/for-next'") as the first bad
> (assuming that this latter fails to boot with "scsi_mod.use_blk_mq=1").
>
Puzzled. Same results. 453f1d821165 works with both scsi_mod.use_blk_mq=0
and scsi_mod.use_blk_mq=1. next-20180801 works with scsi_mod.use_blk_mq=0
and fails with scsi_mod.use_blk_mq=1. Bisect still points to the same commit
(which just changes the default) as culprit. I know that doesn't make sense.
I'll need to think about it.
Guenter
On 08/01/2018 05:03 PM, James Bottomley wrote:
> On Thu, 2018-08-02 at 07:57 +0800, Ming Lei wrote:
>> On Thu, Aug 2, 2018 at 7:47 AM, Guenter Roeck <[email protected]>
>> wrote:
>>> On Wed, Aug 01, 2018 at 03:52:45PM -0700, James Bottomley wrote:
>>>> On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
>>>>> On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell
>>>>> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Changes since 20180731:
>>>>>>
>>>>>> The pci tree gained a conflict against the pci-current tree.
>>>>>>
>>>>>> The net-next tree gained a conflict against the bpf tree.
>>>>>>
>>>>>> The block tree lost its build failure.
>>>>>>
>>>>>> The staging tree still had its build failure due to an
>>>>>> interaction
>>>>>> with
>>>>>> the vfs tree for which I disabled CONFIG_EROFS_FS.
>>>>>>
>>>>>> The kspp tree lost its build failure.
>>>>>>
>>>>>> Non-merge commits (relative to Linus' tree): 10070
>>>>>> 9137 files changed, 417605 insertions(+), 179996 deletions(-
>>>>>> )
>>>>>>
>>>>>> -----------------------------------------------------------
>>>>>> ------
>>>>>> -----------
>>>>>>
>>>>>
>>>>> The widespread kernel hang issues are still seen. I managed
>>>>> to bisect it after working around the transient build failures.
>>>>> Bisect log is attached below. Unfortunately, it doesn't help
>>>>> much.
>>>>> The culprit is reported as:
>>>>>
>>>>> 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
>>>>>
>>>>> The preceding merge,
>>>>>
>>>>> 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
>>>>>
>>>>> checks out fine, as does the tip of scsi-next (commit
>>>>> 103c7b7e0184,
>>>>> "Merge branch 'misc' into for-next"). No idea how to proceed.
>>>>
>>>> This sounds like you may have a problem with this patch:
>>>>
>>>> commit d5038a13eca72fb216c07eb717169092e92284f1
>>>> Author: Johannes Thumshirn <[email protected]>
>>>> Date: Wed Jul 4 10:53:56 2018 +0200
>>>>
>>>> scsi: core: switch to scsi-mq by default
>>>>
>>>> To verify, boot with the additional kernel parameter
>>>>
>>>> scsi_mod.use_blk_mq=0
>>>>
>>>> Which will reverse the effect of the above patch.
>>>>
>>>
>>> Yes, that fixes the problem.
>>
>> That may not the root cause, given this issue is only started to
>> see from next-20180731, but d5038a13eca7 (scsi: core: switch to
>> scsi-mq by default)
>> has been in -next for quite a while.
>>
>> Seems something new causes this issue.
>
> Read my other email about how to find this.
>
> https://marc.info/?l=linux-scsi&m=153316446223676
>
> Now that we've confirmed the issue, Gunter, could you attempt to bisect
> it as that email describes?
>
So, I am more and more baffled.
I ran another round of bisect, this time each test executing twice,
once with "scsi_mod.use_blk_mq=1" and once with "scsi_mod.use_blk_mq=0",
requiring both to pass. Bisect still points to the merge as culprit.
Ok, one step further: Actually _revert_ commit d5038a13eca72 before running
each test, meaning the default is use_blk_mq=0. Still run both tests.
Bisect _still_ points to the merge of scsi-next as culprit.
So, to me it looks like the problem is triggered by _something_ in
scsi-next, combined with _something_ in -next prior to the merge,
not specifically associated with use_blk_mq=[0|1] or d5038a13eca72,
but to a combination of some patch in scsi-next and some other patch.
I am running out of ideas. Any thoughts on how to track this down further ?
Guenter
On Wed, 2018-08-01 at 21:58 -0700, Guenter Roeck wrote:
+AD4- I am running out of ideas. Any thoughts on how to track this down further ?
Is a shell available when the hang occurs? If so, it would be helpful if you
could provide a dump of the information in /sys/kernel/debug/block. There is
namely detailed information in that directory about pending commands.
Bart.
On Thu, Aug 2, 2018 at 12:58 PM, Guenter Roeck <[email protected]> wrote:
> On 08/01/2018 05:03 PM, James Bottomley wrote:
>>
>> On Thu, 2018-08-02 at 07:57 +0800, Ming Lei wrote:
>>>
>>> On Thu, Aug 2, 2018 at 7:47 AM, Guenter Roeck <[email protected]>
>>> wrote:
>>>>
>>>> On Wed, Aug 01, 2018 at 03:52:45PM -0700, James Bottomley wrote:
>>>>>
>>>>> On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
>>>>>>
>>>>>> On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Changes since 20180731:
>>>>>>>
>>>>>>> The pci tree gained a conflict against the pci-current tree.
>>>>>>>
>>>>>>> The net-next tree gained a conflict against the bpf tree.
>>>>>>>
>>>>>>> The block tree lost its build failure.
>>>>>>>
>>>>>>> The staging tree still had its build failure due to an
>>>>>>> interaction
>>>>>>> with
>>>>>>> the vfs tree for which I disabled CONFIG_EROFS_FS.
>>>>>>>
>>>>>>> The kspp tree lost its build failure.
>>>>>>>
>>>>>>> Non-merge commits (relative to Linus' tree): 10070
>>>>>>> 9137 files changed, 417605 insertions(+), 179996 deletions(-
>>>>>>> )
>>>>>>>
>>>>>>> -----------------------------------------------------------
>>>>>>> ------
>>>>>>> -----------
>>>>>>>
>>>>>>
>>>>>> The widespread kernel hang issues are still seen. I managed
>>>>>> to bisect it after working around the transient build failures.
>>>>>> Bisect log is attached below. Unfortunately, it doesn't help
>>>>>> much.
>>>>>> The culprit is reported as:
>>>>>>
>>>>>> 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
>>>>>>
>>>>>> The preceding merge,
>>>>>>
>>>>>> 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
>>>>>>
>>>>>> checks out fine, as does the tip of scsi-next (commit
>>>>>> 103c7b7e0184,
>>>>>> "Merge branch 'misc' into for-next"). No idea how to proceed.
>>>>>
>>>>>
>>>>> This sounds like you may have a problem with this patch:
>>>>>
>>>>> commit d5038a13eca72fb216c07eb717169092e92284f1
>>>>> Author: Johannes Thumshirn <[email protected]>
>>>>> Date: Wed Jul 4 10:53:56 2018 +0200
>>>>>
>>>>> scsi: core: switch to scsi-mq by default
>>>>>
>>>>> To verify, boot with the additional kernel parameter
>>>>>
>>>>> scsi_mod.use_blk_mq=0
>>>>>
>>>>> Which will reverse the effect of the above patch.
>>>>>
>>>>
>>>> Yes, that fixes the problem.
>>>
>>>
>>> That may not the root cause, given this issue is only started to
>>> see from next-20180731, but d5038a13eca7 (scsi: core: switch to
>>> scsi-mq by default)
>>> has been in -next for quite a while.
>>>
>>> Seems something new causes this issue.
>>
>>
>> Read my other email about how to find this.
>>
>> https://marc.info/?l=linux-scsi&m=153316446223676
>>
>> Now that we've confirmed the issue, Gunter, could you attempt to bisect
>> it as that email describes?
>>
>
> So, I am more and more baffled.
>
> I ran another round of bisect, this time each test executing twice,
> once with "scsi_mod.use_blk_mq=1" and once with "scsi_mod.use_blk_mq=0",
> requiring both to pass. Bisect still points to the merge as culprit.
>
> Ok, one step further: Actually _revert_ commit d5038a13eca72 before running
> each test, meaning the default is use_blk_mq=0. Still run both tests.
> Bisect _still_ points to the merge of scsi-next as culprit.
>
> So, to me it looks like the problem is triggered by _something_ in
> scsi-next, combined with _something_ in -next prior to the merge,
> not specifically associated with use_blk_mq=[0|1] or d5038a13eca72,
> but to a combination of some patch in scsi-next and some other patch.
Today I am a bit busy, and not trace it much.
So far, I found the code hangs in scsi_test_unit_ready()
<-get_capabilities()<-sr_probe(), and scsi_queue_rq()/ata_scsi_queuecmd()
has queued the command successfully, but never completed.
Also tried to revert commits merged to ata tree on 30th, 31th,
but no difference.
Thanks,
Ming Lei
On 08/01/2018 10:04 PM, Bart Van Assche wrote:
> On Wed, 2018-08-01 at 21:58 -0700, Guenter Roeck wrote:
>> I am running out of ideas. Any thoughts on how to track this down further ?
>
> Is a shell available when the hang occurs? If so, it would be helpful if you
> could provide a dump of the information in /sys/kernel/debug/block. There is
> namely detailed information in that directory about pending commands.
>
No, it hangs hard early in the boot process. See various logs at
http://kerneltests.org/builders/, in the 'next' column.
Here is some interesting information from the x86_64 boot tests.
Building x86_64:q35:Broadwell-noTSX:defconfig:smp:sata:rootfs ... running .................................. failed (timeout)
Building x86_64:q35:IvyBridge:defconfig:smp:nvme:rootfs ... running .................................. failed (timeout)
Building x86_64:q35:SandyBridge:defconfig:smp:usb:rootfs ... running .................................. failed (timeout)
Building x86_64:q35:Haswell:defconfig:smp:usb-uas:rootfs ... running ...... passed
Building x86_64:q35:Skylake-Client:defconfig:smp:mmc:rootfs ... running .................................. failed (timeout)
Building x86_64:q35:Conroe:defconfig:smp:scsi[DC395]:rootfs ... running ........ passed
Building x86_64:q35:Nehalem:defconfig:smp:scsi[AM53C974]:rootfs ... running ...... passed
Building x86_64:q35:Westmere-IBRS:defconfig:smp:scsi[53C810]:rootfs ... running ....... passed
Building x86_64:q35:Skylake-Server:defconfig:smp:scsi[53C895A]:rootfs ... running ....... passed
Building x86_64:pc:EPYC:defconfig:smp:scsi[MEGASAS]:rootfs ... running ...... passed
Building x86_64:q35:EPYC-IBPB:defconfig:smp:scsi[MEGASAS2]:rootfs ... running ....... passed
Building x86_64:q35:Opteron_G5:defconfig:smp:scsi[FUSION]:rootfs ... running ....... passed
Building x86_64:pc:phenom:defconfig:smp:initrd ... running .................................. failed (timeout)
Building x86_64:q35:Opteron_G1:defconfig:smp:initrd ... running .................................. failed (timeout)
Building x86_64:pc:Opteron_G2:defconfig:smp:sata:rootfs ... running .................................. failed (timeout)
Building x86_64:q35:core2duo:defconfig:smp:usb:rootfs ... running .................................. failed (timeout)
Building x86_64:pc:Opteron_G3:defconfig:nosmp:usb:rootfs ... running .................................. failed (timeout)
Building x86_64:q35:Opteron_G4:defconfig:nosmp:sata:rootfs ... running .................................. failed (timeout)
This is consistent across multiple test runs. In summary,
- Boot from initrd fails
- Boot from SATA drive fails (this is with CONFIG_ATA)
- Boot from NVME fails
- Boot from USB drive fails
- Boot from MMC (SD) fails
- Boot from USB UAS drive passes
- Boot from various real SCSI drives passes
Platform (pc,q35), CPU type, or SMP/NOSMP does not seem to make a difference.
Guenter
On Thu, Aug 02, 2018 at 05:46:19AM -0700, Guenter Roeck wrote:
> This is consistent across multiple test runs. In summary,
>
> - Boot from initrd fails
> - Boot from SATA drive fails (this is with CONFIG_ATA)
> - Boot from NVME fails
> - Boot from USB drive fails
> - Boot from MMC (SD) fails
> - Boot from USB UAS drive passes
> - Boot from various real SCSI drives passes
>
> Platform (pc,q35), CPU type, or SMP/NOSMP does not seem to make a difference.
OK. I try to bisect between next-20180727 (known good) and
next-20180731 (known bad) with forced scsi_mod.use_blk_mq=1, but so
far the only bad I've seen is next-20180731.
Byte,
Johannes
--
Johannes Thumshirn Storage
[email protected] +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
On 08/02/2018 05:51 AM, Johannes Thumshirn wrote:
> On Thu, Aug 02, 2018 at 05:46:19AM -0700, Guenter Roeck wrote:
>> This is consistent across multiple test runs. In summary,
>>
>> - Boot from initrd fails
>> - Boot from SATA drive fails (this is with CONFIG_ATA)
>> - Boot from NVME fails
>> - Boot from USB drive fails
>> - Boot from MMC (SD) fails
>> - Boot from USB UAS drive passes
>> - Boot from various real SCSI drives passes
>>
>> Platform (pc,q35), CPU type, or SMP/NOSMP does not seem to make a difference.
>
> OK. I try to bisect between next-20180727 (known good) and
> next-20180731 (known bad) with forced scsi_mod.use_blk_mq=1, but so
> far the only bad I've seen is next-20180731.
>
Per my logs, next-20180730 is the first bad, next-20180727 is the last good.
Guenter
On 08/02/2018 04:35 AM, Ming Lei wrote:
> On Thu, Aug 2, 2018 at 12:58 PM, Guenter Roeck <[email protected]> wrote:
>> On 08/01/2018 05:03 PM, James Bottomley wrote:
>>>
>>> On Thu, 2018-08-02 at 07:57 +0800, Ming Lei wrote:
>>>>
>>>> On Thu, Aug 2, 2018 at 7:47 AM, Guenter Roeck <[email protected]>
>>>> wrote:
>>>>>
>>>>> On Wed, Aug 01, 2018 at 03:52:45PM -0700, James Bottomley wrote:
>>>>>>
>>>>>> On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
>>>>>>>
>>>>>>> On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Changes since 20180731:
>>>>>>>>
>>>>>>>> The pci tree gained a conflict against the pci-current tree.
>>>>>>>>
>>>>>>>> The net-next tree gained a conflict against the bpf tree.
>>>>>>>>
>>>>>>>> The block tree lost its build failure.
>>>>>>>>
>>>>>>>> The staging tree still had its build failure due to an
>>>>>>>> interaction
>>>>>>>> with
>>>>>>>> the vfs tree for which I disabled CONFIG_EROFS_FS.
>>>>>>>>
>>>>>>>> The kspp tree lost its build failure.
>>>>>>>>
>>>>>>>> Non-merge commits (relative to Linus' tree): 10070
>>>>>>>> 9137 files changed, 417605 insertions(+), 179996 deletions(-
>>>>>>>> )
>>>>>>>>
>>>>>>>> -----------------------------------------------------------
>>>>>>>> ------
>>>>>>>> -----------
>>>>>>>>
>>>>>>>
>>>>>>> The widespread kernel hang issues are still seen. I managed
>>>>>>> to bisect it after working around the transient build failures.
>>>>>>> Bisect log is attached below. Unfortunately, it doesn't help
>>>>>>> much.
>>>>>>> The culprit is reported as:
>>>>>>>
>>>>>>> 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
>>>>>>>
>>>>>>> The preceding merge,
>>>>>>>
>>>>>>> 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
>>>>>>>
>>>>>>> checks out fine, as does the tip of scsi-next (commit
>>>>>>> 103c7b7e0184,
>>>>>>> "Merge branch 'misc' into for-next"). No idea how to proceed.
>>>>>>
>>>>>>
>>>>>> This sounds like you may have a problem with this patch:
>>>>>>
>>>>>> commit d5038a13eca72fb216c07eb717169092e92284f1
>>>>>> Author: Johannes Thumshirn <[email protected]>
>>>>>> Date: Wed Jul 4 10:53:56 2018 +0200
>>>>>>
>>>>>> scsi: core: switch to scsi-mq by default
>>>>>>
>>>>>> To verify, boot with the additional kernel parameter
>>>>>>
>>>>>> scsi_mod.use_blk_mq=0
>>>>>>
>>>>>> Which will reverse the effect of the above patch.
>>>>>>
>>>>>
>>>>> Yes, that fixes the problem.
>>>>
>>>>
>>>> That may not the root cause, given this issue is only started to
>>>> see from next-20180731, but d5038a13eca7 (scsi: core: switch to
>>>> scsi-mq by default)
>>>> has been in -next for quite a while.
>>>>
>>>> Seems something new causes this issue.
>>>
>>>
>>> Read my other email about how to find this.
>>>
>>> https://marc.info/?l=linux-scsi&m=153316446223676
>>>
>>> Now that we've confirmed the issue, Gunter, could you attempt to bisect
>>> it as that email describes?
>>>
>>
>> So, I am more and more baffled.
>>
>> I ran another round of bisect, this time each test executing twice,
>> once with "scsi_mod.use_blk_mq=1" and once with "scsi_mod.use_blk_mq=0",
>> requiring both to pass. Bisect still points to the merge as culprit.
>>
>> Ok, one step further: Actually _revert_ commit d5038a13eca72 before running
>> each test, meaning the default is use_blk_mq=0. Still run both tests.
>> Bisect _still_ points to the merge of scsi-next as culprit.
>>
>> So, to me it looks like the problem is triggered by _something_ in
>> scsi-next, combined with _something_ in -next prior to the merge,
>> not specifically associated with use_blk_mq=[0|1] or d5038a13eca72,
>> but to a combination of some patch in scsi-next and some other patch.
>
> Today I am a bit busy, and not trace it much.
>
> So far, I found the code hangs in scsi_test_unit_ready()
> <-get_capabilities()<-sr_probe(), and scsi_queue_rq()/ata_scsi_queuecmd()
> has queued the command successfully, but never completed.
>
> Also tried to revert commits merged to ata tree on 30th, 31th,
> but no difference.
>
Looking at my commit logs, the problem started to happen after various DMA
changes were introduced. The boot tests fail on ppc (few), mips (all 32 bit,
most 64 bit), i386 (all), x86_64 (most). All other platform pass, even with
the same type of boot tests. Here is an example from alpha:
Building alpha:defconfig:initrd ... running .... passed
Building alpha:defconfig:sata:rootfs ... running ..... passed
Building alpha:defconfig:usb:rootfs ... running ..... passed
Building alpha:defconfig:usb-uas:rootfs ... running ...... passed
Building alpha:defconfig:scsi[AM53C974]:rootfs ... running ....... passed
Building alpha:defconfig:scsi[DC395]:rootfs ... running ....... passed
Building alpha:defconfig:scsi[MEGASAS]:rootfs ... running ...... passed
Building alpha:defconfig:scsi[MEGASAS2]:rootfs ... running ...... passed
Building alpha:defconfig:scsi[FUSION]:rootfs ... running ...... passed
Building alpha:defconfig:nvme:rootfs ... running ..... passed
arm64:
Building arm64:virt:defconfig:smp:initrd ... running ..... passed
Building arm64:virt:defconfig:smp:usb:rootfs ... running ..... passed
Building arm64:virt:defconfig:smp:usb-uas:rootfs ... running ..... passed
Building arm64:virt:defconfig:smp:virtio:rootfs ... running ..... passed
Building arm64:virt:defconfig:smp:nvme:rootfs ... running ..... passed
Building arm64:virt:defconfig:smp:mmc:rootfs ... running ..... passed
Building arm64:virt:defconfig:smp:scsi[DC395]:rootfs ... running ..... passed
Building arm64:virt:defconfig:smp:scsi[AM53C974]:rootfs ... running ..... passed
Building arm64:virt:defconfig:smp:scsi[MEGASAS]:rootfs ... running ..... passed
Building arm64:virt:defconfig:smp:scsi[MEGASAS2]:rootfs ... running ..... passed
Building arm64:virt:defconfig:smp:scsi[53C810]:rootfs ... running ...... passed
Building arm64:virt:defconfig:smp:scsi[53C895A]:rootfs ... running ...... passed
Building arm64:virt:defconfig:smp:scsi[FUSION]:rootfs ... running ...... passed
Skipping arm64:xlnx-zcu102:defconfig:smp:initrd:xilinx/zynqmp-ep108 ...
Skipping arm64:xlnx-zcu102:defconfig:smp:sd:rootfs:xilinx/zynqmp-ep108 ...
Skipping arm64:xlnx-zcu102:defconfig:smp:sata:rootfs:xilinx/zynqmp-ep108 ...
Building arm64:xlnx-zcu102:defconfig:smp:initrd:xilinx/zynqmp-zcu102-rev1.0 ... running ....... passed
Building arm64:xlnx-zcu102:defconfig:smp:sd1:rootfs:xilinx/zynqmp-zcu102-rev1.0 ... running ......... passed
Building arm64:xlnx-zcu102:defconfig:smp:sata:rootfs:xilinx/zynqmp-zcu102-rev1.0 ... running ...... passed
Building arm64:raspi3:defconfig:smp:initrd:broadcom/bcm2837-rpi-3-b ... running ..... passed
Building arm64:raspi3:defconfig:smp:sd:rootfs:broadcom/bcm2837-rpi-3-b ... running ........ passed
Building arm64:virt:defconfig:nosmp:initrd ... running ..... passed
Skipping arm64:xlnx-zcu102:defconfig:nosmp:initrd:xilinx/zynqmp-ep108 ...
Skipping arm64:xlnx-zcu102:defconfig:nosmp:sd:rootfs:xilinx/zynqmp-ep108 ...
Building arm64:xlnx-zcu102:defconfig:nosmp:initrd:xilinx/zynqmp-zcu102-rev1.0 ... running ......... passed
Building arm64:xlnx-zcu102:defconfig:nosmp:sd1:rootfs:xilinx/zynqmp-zcu102-rev1.0 ... running ......... passed
ppc:
Building powerpc:mac99:qemu_ppc_book3s_defconfig:nosmp:rootfs ... running ....... passed
Building powerpc:g3beige:qemu_ppc_book3s_defconfig:nosmp:rootfs ... running ...... passed
Building powerpc:mac99:qemu_ppc_book3s_defconfig:smp:rootfs ... running ....... passed
Building powerpc:virtex-ml507:44x/virtex5_defconfig:devtmpfs:initrd ... running .... passed
Building powerpc:mpc8544ds:mpc85xx_defconfig:initrd ... running .... passed
Building powerpc:mpc8544ds:mpc85xx_defconfig:scsi:rootfs ... running ..... passed
Building powerpc:mpc8544ds:mpc85xx_defconfig:sata:rootfs ... running .... passed
Building powerpc:mpc8544ds:mpc85xx_smp_defconfig:initrd ... running .... passed
Building powerpc:mpc8544ds:mpc85xx_smp_defconfig:scsi:rootfs ... running ..... passed
Building powerpc:mpc8544ds:mpc85xx_smp_defconfig:sata:rootfs ... running .... passed
Building powerpc:bamboo:44x/bamboo_defconfig:devtmpfs:initrd ... running .... passed
Building powerpc:bamboo:44x/bamboo_defconfig:devtmpfs:scsi[AM53C974]:rootfs ... running ..... passed
Building powerpc:bamboo:44x/bamboo_defconfig:devtmpfs:smp:initrd ... running .... passed
Building powerpc:bamboo:44x/bamboo_defconfig:devtmpfs:smp:scsi[AM53C974]:rootfs ... running ..... passed
Building powerpc:sam460ex:44x/canyonlands_defconfig:devtmpfs:initrd ... running ..... passed
Building powerpc:sam460ex:44x/canyonlands_defconfig:devtmpfs:usbdisk:rootfs ... running ...... passed
Building powerpc:mac99:pmac32_defconfig:devtmpfs:zilog:initrd ... running .................................. failed (timeout)
Building powerpc:mac99:pmac32_defconfig:devtmpfs:zilog:rootfs ... running .................................. failed (timeout)
Maybe that is a coincidence, but it is at least suspicious.
Guenter
On Thu, Aug 02, 2018 at 06:00:19AM -0700, Guenter Roeck wrote:
> Per my logs, next-20180730 is the first bad, next-20180727 is the last good.
OK, so my bisecting is correct (a bit too much but still).
--
Johannes Thumshirn Storage
[email protected] +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
On Thu, Aug 02, 2018 at 06:05:16AM -0700, Guenter Roeck wrote:
> On 08/02/2018 04:35 AM, Ming Lei wrote:
> > On Thu, Aug 2, 2018 at 12:58 PM, Guenter Roeck <[email protected]> wrote:
> > > On 08/01/2018 05:03 PM, James Bottomley wrote:
> > > >
> > > > On Thu, 2018-08-02 at 07:57 +0800, Ming Lei wrote:
> > > > >
> > > > > On Thu, Aug 2, 2018 at 7:47 AM, Guenter Roeck <[email protected]>
> > > > > wrote:
> > > > > >
> > > > > > On Wed, Aug 01, 2018 at 03:52:45PM -0700, James Bottomley wrote:
> > > > > > >
> > > > > > > On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
> > > > > > > >
> > > > > > > > On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > Changes since 20180731:
> > > > > > > > >
> > > > > > > > > The pci tree gained a conflict against the pci-current tree.
> > > > > > > > >
> > > > > > > > > The net-next tree gained a conflict against the bpf tree.
> > > > > > > > >
> > > > > > > > > The block tree lost its build failure.
> > > > > > > > >
> > > > > > > > > The staging tree still had its build failure due to an
> > > > > > > > > interaction
> > > > > > > > > with
> > > > > > > > > the vfs tree for which I disabled CONFIG_EROFS_FS.
> > > > > > > > >
> > > > > > > > > The kspp tree lost its build failure.
> > > > > > > > >
> > > > > > > > > Non-merge commits (relative to Linus' tree): 10070
> > > > > > > > > 9137 files changed, 417605 insertions(+), 179996 deletions(-
> > > > > > > > > )
> > > > > > > > >
> > > > > > > > > -----------------------------------------------------------
> > > > > > > > > ------
> > > > > > > > > -----------
> > > > > > > > >
> > > > > > > >
> > > > > > > > The widespread kernel hang issues are still seen. I managed
> > > > > > > > to bisect it after working around the transient build failures.
> > > > > > > > Bisect log is attached below. Unfortunately, it doesn't help
> > > > > > > > much.
> > > > > > > > The culprit is reported as:
> > > > > > > >
> > > > > > > > 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
> > > > > > > >
> > > > > > > > The preceding merge,
> > > > > > > >
> > > > > > > > 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
> > > > > > > >
> > > > > > > > checks out fine, as does the tip of scsi-next (commit
> > > > > > > > 103c7b7e0184,
> > > > > > > > "Merge branch 'misc' into for-next"). No idea how to proceed.
> > > > > > >
> > > > > > >
> > > > > > > This sounds like you may have a problem with this patch:
> > > > > > >
> > > > > > > commit d5038a13eca72fb216c07eb717169092e92284f1
> > > > > > > Author: Johannes Thumshirn <[email protected]>
> > > > > > > Date: Wed Jul 4 10:53:56 2018 +0200
> > > > > > >
> > > > > > > scsi: core: switch to scsi-mq by default
> > > > > > >
> > > > > > > To verify, boot with the additional kernel parameter
> > > > > > >
> > > > > > > scsi_mod.use_blk_mq=0
> > > > > > >
> > > > > > > Which will reverse the effect of the above patch.
> > > > > > >
> > > > > >
> > > > > > Yes, that fixes the problem.
> > > > >
> > > > >
> > > > > That may not the root cause, given this issue is only started to
> > > > > see from next-20180731, but d5038a13eca7 (scsi: core: switch to
> > > > > scsi-mq by default)
> > > > > has been in -next for quite a while.
> > > > >
> > > > > Seems something new causes this issue.
> > > >
> > > >
> > > > Read my other email about how to find this.
> > > >
> > > > https://marc.info/?l=linux-scsi&m=153316446223676
> > > >
> > > > Now that we've confirmed the issue, Gunter, could you attempt to bisect
> > > > it as that email describes?
> > > >
> > >
> > > So, I am more and more baffled.
> > >
> > > I ran another round of bisect, this time each test executing twice,
> > > once with "scsi_mod.use_blk_mq=1" and once with "scsi_mod.use_blk_mq=0",
> > > requiring both to pass. Bisect still points to the merge as culprit.
> > >
> > > Ok, one step further: Actually _revert_ commit d5038a13eca72 before running
> > > each test, meaning the default is use_blk_mq=0. Still run both tests.
> > > Bisect _still_ points to the merge of scsi-next as culprit.
> > >
> > > So, to me it looks like the problem is triggered by _something_ in
> > > scsi-next, combined with _something_ in -next prior to the merge,
> > > not specifically associated with use_blk_mq=[0|1] or d5038a13eca72,
> > > but to a combination of some patch in scsi-next and some other patch.
> >
> > Today I am a bit busy, and not trace it much.
> >
> > So far, I found the code hangs in scsi_test_unit_ready()
> > <-get_capabilities()<-sr_probe(), and scsi_queue_rq()/ata_scsi_queuecmd()
> > has queued the command successfully, but never completed.
> >
> > Also tried to revert commits merged to ata tree on 30th, 31th,
> > but no difference.
> >
>
> Looking at my commit logs, the problem started to happen after various DMA
> changes were introduced. The boot tests fail on ppc (few), mips (all 32 bit,
> most 64 bit), i386 (all), x86_64 (most). All other platform pass, even with
> the same type of boot tests. Here is an example from alpha:
>
> Building alpha:defconfig:initrd ... running .... passed
> Building alpha:defconfig:sata:rootfs ... running ..... passed
> Building alpha:defconfig:usb:rootfs ... running ..... passed
> Building alpha:defconfig:usb-uas:rootfs ... running ...... passed
> Building alpha:defconfig:scsi[AM53C974]:rootfs ... running ....... passed
> Building alpha:defconfig:scsi[DC395]:rootfs ... running ....... passed
> Building alpha:defconfig:scsi[MEGASAS]:rootfs ... running ...... passed
> Building alpha:defconfig:scsi[MEGASAS2]:rootfs ... running ...... passed
> Building alpha:defconfig:scsi[FUSION]:rootfs ... running ...... passed
> Building alpha:defconfig:nvme:rootfs ... running ..... passed
>
> arm64:
>
> Building arm64:virt:defconfig:smp:initrd ... running ..... passed
> Building arm64:virt:defconfig:smp:usb:rootfs ... running ..... passed
> Building arm64:virt:defconfig:smp:usb-uas:rootfs ... running ..... passed
> Building arm64:virt:defconfig:smp:virtio:rootfs ... running ..... passed
> Building arm64:virt:defconfig:smp:nvme:rootfs ... running ..... passed
> Building arm64:virt:defconfig:smp:mmc:rootfs ... running ..... passed
> Building arm64:virt:defconfig:smp:scsi[DC395]:rootfs ... running ..... passed
> Building arm64:virt:defconfig:smp:scsi[AM53C974]:rootfs ... running ..... passed
> Building arm64:virt:defconfig:smp:scsi[MEGASAS]:rootfs ... running ..... passed
> Building arm64:virt:defconfig:smp:scsi[MEGASAS2]:rootfs ... running ..... passed
> Building arm64:virt:defconfig:smp:scsi[53C810]:rootfs ... running ...... passed
> Building arm64:virt:defconfig:smp:scsi[53C895A]:rootfs ... running ...... passed
> Building arm64:virt:defconfig:smp:scsi[FUSION]:rootfs ... running ...... passed
> Skipping arm64:xlnx-zcu102:defconfig:smp:initrd:xilinx/zynqmp-ep108 ...
> Skipping arm64:xlnx-zcu102:defconfig:smp:sd:rootfs:xilinx/zynqmp-ep108 ...
> Skipping arm64:xlnx-zcu102:defconfig:smp:sata:rootfs:xilinx/zynqmp-ep108 ...
> Building arm64:xlnx-zcu102:defconfig:smp:initrd:xilinx/zynqmp-zcu102-rev1.0 ... running ....... passed
> Building arm64:xlnx-zcu102:defconfig:smp:sd1:rootfs:xilinx/zynqmp-zcu102-rev1.0 ... running ......... passed
> Building arm64:xlnx-zcu102:defconfig:smp:sata:rootfs:xilinx/zynqmp-zcu102-rev1.0 ... running ...... passed
> Building arm64:raspi3:defconfig:smp:initrd:broadcom/bcm2837-rpi-3-b ... running ..... passed
> Building arm64:raspi3:defconfig:smp:sd:rootfs:broadcom/bcm2837-rpi-3-b ... running ........ passed
> Building arm64:virt:defconfig:nosmp:initrd ... running ..... passed
> Skipping arm64:xlnx-zcu102:defconfig:nosmp:initrd:xilinx/zynqmp-ep108 ...
> Skipping arm64:xlnx-zcu102:defconfig:nosmp:sd:rootfs:xilinx/zynqmp-ep108 ...
> Building arm64:xlnx-zcu102:defconfig:nosmp:initrd:xilinx/zynqmp-zcu102-rev1.0 ... running ......... passed
> Building arm64:xlnx-zcu102:defconfig:nosmp:sd1:rootfs:xilinx/zynqmp-zcu102-rev1.0 ... running ......... passed
>
> ppc:
>
> Building powerpc:mac99:qemu_ppc_book3s_defconfig:nosmp:rootfs ... running ....... passed
> Building powerpc:g3beige:qemu_ppc_book3s_defconfig:nosmp:rootfs ... running ...... passed
> Building powerpc:mac99:qemu_ppc_book3s_defconfig:smp:rootfs ... running ....... passed
> Building powerpc:virtex-ml507:44x/virtex5_defconfig:devtmpfs:initrd ... running .... passed
> Building powerpc:mpc8544ds:mpc85xx_defconfig:initrd ... running .... passed
> Building powerpc:mpc8544ds:mpc85xx_defconfig:scsi:rootfs ... running ..... passed
> Building powerpc:mpc8544ds:mpc85xx_defconfig:sata:rootfs ... running .... passed
> Building powerpc:mpc8544ds:mpc85xx_smp_defconfig:initrd ... running .... passed
> Building powerpc:mpc8544ds:mpc85xx_smp_defconfig:scsi:rootfs ... running ..... passed
> Building powerpc:mpc8544ds:mpc85xx_smp_defconfig:sata:rootfs ... running .... passed
> Building powerpc:bamboo:44x/bamboo_defconfig:devtmpfs:initrd ... running .... passed
> Building powerpc:bamboo:44x/bamboo_defconfig:devtmpfs:scsi[AM53C974]:rootfs ... running ..... passed
> Building powerpc:bamboo:44x/bamboo_defconfig:devtmpfs:smp:initrd ... running .... passed
> Building powerpc:bamboo:44x/bamboo_defconfig:devtmpfs:smp:scsi[AM53C974]:rootfs ... running ..... passed
> Building powerpc:sam460ex:44x/canyonlands_defconfig:devtmpfs:initrd ... running ..... passed
> Building powerpc:sam460ex:44x/canyonlands_defconfig:devtmpfs:usbdisk:rootfs ... running ...... passed
> Building powerpc:mac99:pmac32_defconfig:devtmpfs:zilog:initrd ... running .................................. failed (timeout)
> Building powerpc:mac99:pmac32_defconfig:devtmpfs:zilog:rootfs ... running .................................. failed (timeout)
>
> Maybe that is a coincidence, but it is at least suspicious.
This issue can be fixed by reverting d250bf4e776ff09d5 ("blk-mq: only iterate over
inflight requests in blk_mq_tagset_busy_iter").
This patch looks wrong, because 'blk_mq_rq_state(rq) == MQ_RQ_IN_FLIGHT'
isn't completely same with 'blk_mq_request_started(req)'.
Thanks,
Ming
On Fri, 2018-08-03 at 00:50 +-0800, Ming Lei wrote:
+AD4- On Fri, Aug 3, 2018 at 12:40 AM, Bart Van Assche +ADw-Bart.VanAssche+AEA-wdc.com+AD4- wrote:
+AD4- +AD4- On Fri, 2018-08-03 at 00:27 +-0800, Ming Lei wrote:
+AD4- +AD4- +AD4- This issue can be fixed by reverting d250bf4e776ff09d5 (+ACI-blk-mq: only iterate over
+AD4- +AD4- +AD4- inflight requests in blk+AF8-mq+AF8-tagset+AF8-busy+AF8-iter+ACI-).
+AD4- +AD4- +AD4-
+AD4- +AD4- +AD4- This patch looks wrong, because 'blk+AF8-mq+AF8-rq+AF8-state(rq) +AD0APQ- MQ+AF8-RQ+AF8-IN+AF8-FLIGHT'
+AD4- +AD4- +AD4- isn't completely same with 'blk+AF8-mq+AF8-request+AF8-started(req)'.
+AD4- +AD4-
+AD4- +AD4- Please test the following change instead of reverting the commit mentioned
+AD4- +AD4- above:
+AD4- +AD4-
+AD4- +AD4- diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
+AD4- +AD4- index 09b2ee6694fb..25a0583d8b4c 100644
+AD4- +AD4- --- a/block/blk-mq-tag.c
+AD4- +AD4- +-+-+- b/block/blk-mq-tag.c
+AD4- +AD4- +AEAAQA- -271,7 +-271,7 +AEAAQA- static bool bt+AF8-tags+AF8-iter(struct sbitmap +ACo-bitmap, unsigned int bitnr, void +ACo-data)
+AD4- +AD4- +ACo- test and set the bit before assining -+AD4-rqs+AFsAXQ-.
+AD4- +AD4- +ACo-/
+AD4- +AD4- rq +AD0- tags-+AD4-rqs+AFs-bitnr+AF0AOw-
+AD4- +AD4- - if (rq +ACYAJg- blk+AF8-mq+AF8-rq+AF8-state(rq) +AD0APQ- MQ+AF8-RQ+AF8-IN+AF8-FLIGHT)
+AD4- +AD4- +- if (rq +ACYAJg- blk+AF8-mq+AF8-rq+AF8-state(rq) +ACEAPQ- MQ+AF8-RQ+AF8-IDLE)
+AD4- +AD4- iter+AF8-data-+AD4-fn(rq, iter+AF8-data-+AD4-data, reserved)+ADs-
+AD4- +AD4-
+AD4- +AD4- return true+ADs-
+AD4- +AD4-
+AD4-
+AD4- I just sent out a similar patch on list, but use blk+AF8-mq+AF8-request+AF8-started()
+AD4- instead.
+AD4-
+AD4- https://marc.info/?l+AD0-linux-scsi+ACY-m+AD0-153322823307754+ACY-w+AD0-2
Hello Ming,
Since both patches are functionally equivalent, I'm fine with either version.
Bart.
On Fri, 2018-08-03 at 00:27 +-0800, Ming Lei wrote:
+AD4- This issue can be fixed by reverting d250bf4e776ff09d5 (+ACI-blk-mq: only iterate over
+AD4- inflight requests in blk+AF8-mq+AF8-tagset+AF8-busy+AF8-iter+ACI-).
+AD4-
+AD4- This patch looks wrong, because 'blk+AF8-mq+AF8-rq+AF8-state(rq) +AD0APQ- MQ+AF8-RQ+AF8-IN+AF8-FLIGHT'
+AD4- isn't completely same with 'blk+AF8-mq+AF8-request+AF8-started(req)'.
Please test the following change instead of reverting the commit mentioned
above:
diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
index 09b2ee6694fb..25a0583d8b4c 100644
--- a/block/blk-mq-tag.c
+-+-+- b/block/blk-mq-tag.c
+AEAAQA- -271,7 +-271,7 +AEAAQA- static bool bt+AF8-tags+AF8-iter(struct sbitmap +ACo-bitmap, unsigned int bitnr, void +ACo-data)
+ACo- test and set the bit before assining -+AD4-rqs+AFsAXQ-.
+ACo-/
rq +AD0- tags-+AD4-rqs+AFs-bitnr+AF0AOw-
- if (rq +ACYAJg- blk+AF8-mq+AF8-rq+AF8-state(rq) +AD0APQ- MQ+AF8-RQ+AF8-IN+AF8-FLIGHT)
+- if (rq +ACYAJg- blk+AF8-mq+AF8-rq+AF8-state(rq) +ACEAPQ- MQ+AF8-RQ+AF8-IDLE)
iter+AF8-data-+AD4-fn(rq, iter+AF8-data-+AD4-data, reserved)+ADs-
return true+ADs-
Thanks,
Bart.
On Fri, Aug 3, 2018 at 12:40 AM, Bart Van Assche <[email protected]> wrote:
> On Fri, 2018-08-03 at 00:27 +0800, Ming Lei wrote:
>> This issue can be fixed by reverting d250bf4e776ff09d5 ("blk-mq: only iterate over
>> inflight requests in blk_mq_tagset_busy_iter").
>>
>> This patch looks wrong, because 'blk_mq_rq_state(rq) == MQ_RQ_IN_FLIGHT'
>> isn't completely same with 'blk_mq_request_started(req)'.
>
> Please test the following change instead of reverting the commit mentioned
> above:
>
> diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
> index 09b2ee6694fb..25a0583d8b4c 100644
> --- a/block/blk-mq-tag.c
> +++ b/block/blk-mq-tag.c
> @@ -271,7 +271,7 @@ static bool bt_tags_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)
> * test and set the bit before assining ->rqs[].
> */
> rq = tags->rqs[bitnr];
> - if (rq && blk_mq_rq_state(rq) == MQ_RQ_IN_FLIGHT)
> + if (rq && blk_mq_rq_state(rq) != MQ_RQ_IDLE)
> iter_data->fn(rq, iter_data->data, reserved);
>
> return true;
>
I just sent out a similar patch on list, but use blk_mq_request_started()
instead.
https://marc.info/?l=linux-scsi&m=153322823307754&w=2
Thanks,
Ming Lei