1. 21 4月, 2017 30 次提交
  2. 17 4月, 2017 7 次提交
    • L
      Linux 4.11-rc7 · 4f7d029b
      Linus Torvalds 提交于
      4f7d029b
    • L
      Merge tag 'armsoc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc · 7395ca0f
      Linus Torvalds 提交于
      Pull ARM SoC fixes from Olof Johansson:
       "Again, a batch that's been sitting a couple of weeks, mostly because
        I anticipated a bit more material but it didn't show up -- which is
        good.
      
        These are all your garden variety fixes for ARM platforms.
      
        The most visible issue fixed here is probably the SMP reset issue on
        OMAP, the rest are minor stuff"
      
      * tag 'armsoc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc:
        arm64: allwinner: a64: add pmu0 regs for USB PHY
        ARM: OMAP2+: omap_device: Sync omap_device and pm_runtime after probe defer
        reset: add exported __reset_control_get, return NULL if optional
        ARM: orion5x: only call into phylib when available
        ARM: omap2+: Revert omap-smp.c changes resetting CPU1 during boot
        ARM: dts: am335x-evmsk: adjust mmc2 param to allow suspend
        ARM: dts: ti: fix PCI bus dtc warnings
        ARM: dts: am335x-baltos: disable EEE for Atheros 8035 PHY
        ARM: dts: OMAP3: Fix MFG ID EEPROM
        ARM: sun8i: a33: add operating-points-v2 property to all nodes
        ARM: sun8i: a33: remove highest OPP to fix CPU crashes
      7395ca0f
    • L
      Merge branch 'for-linus' of git://git.kernel.dk/linux-block · a86f106f
      Linus Torvalds 提交于
      Pull block fixes from Jens Axboe:
       "Four small fixes.
      
        Three of them fix the same error in NVMe, in loop, fc, and rdma
        respectively.  The last fix from Ming fixes a regression in this
        series, where our bvec gap logic was wrong and causes an oops on
        NVMe for certain conditions"
      
      * 'for-linus' of git://git.kernel.dk/linux-block:
        block: fix bio_will_gap() for first bvec with offset
        nvme-fc: Fix sqsize wrong assignment based on ctrl MQES capability
        nvme-rdma: Fix sqsize wrong assignment based on ctrl MQES capability
        nvme-loop: Fix sqsize wrong assignment based on ctrl MQES capability
      a86f106f
    • O
      Merge tag 'omap-for-v4.11/fixes-rc6-signed' of... · e2647b6d
      Olof Johansson 提交于
      Merge tag 'omap-for-v4.11/fixes-rc6-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes
      
      Regression fix for omap interconnect code for deferred probe.
      Without this fix we can get PM related warnings for devices that
      use deferred probe. If necessary, this fix can wait for the
      v4.12 merge window no problem.
      
      * tag 'omap-for-v4.11/fixes-rc6-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
        ARM: OMAP2+: omap_device: Sync omap_device and pm_runtime after probe defer
        ARM: omap2+: Revert omap-smp.c changes resetting CPU1 during boot
        ARM: dts: am335x-evmsk: adjust mmc2 param to allow suspend
        ARM: dts: ti: fix PCI bus dtc warnings
        ARM: dts: am335x-baltos: disable EEE for Atheros 8035 PHY
        ARM: dts: OMAP3: Fix MFG ID EEPROM
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      e2647b6d
    • L
      Merge branch 'for-4.11-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup · 11c994d9
      Linus Torvalds 提交于
      Pull cgroup fix from Tejun Heo:
       "Unfortunately, the commit to fix the cgroup mount race in the previous
        pull request can lead to hangs.
      
        The original bug has been around for a while and isn't too likely to
        be triggered in usual use cases. Revert the commit for now"
      
      * 'for-4.11-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup:
        Revert "cgroup: avoid attaching a cgroup root to two different superblocks"
      11c994d9
    • L
      Merge tag 'tty-4.11-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty · 032aaf3f
      Linus Torvalds 提交于
      Pull tty fix from Greg KH:
       "Here is a single tty core revert for a patch that was reported to
        cause problems.
      
        The original issue is one that we have lived with for decades, so
        trying to scramble to fix the fix in time for 4.11-final does not make
        sense due to the fragility of the tty ldisc layer. Just reverting it
        makes sense for now"
      
      * tag 'tty-4.11-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:
        Revert "tty: don't panic on OOM in tty_set_ldisc()"
      032aaf3f
    • L
      Merge tag 'trace-v4.11-rc5-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace · 48538861
      Linus Torvalds 提交于
      Pull ftrace fix from Steven Rostedt:
       "While rewriting the function probe code, I stumbled over a long
        standing bug. This bug has been there sinc function tracing was added
        way back when. But my new development depends on this bug being fixed,
        and it should be fixed regardless as it causes ftrace to disable
        itself when triggered, and a reboot is required to enable it again.
      
        The bug is that the function probe does not disable itself properly if
        there's another probe of its type still enabled. For example:
      
           # cd /sys/kernel/debug/tracing
           # echo schedule:traceoff > set_ftrace_filter
           # echo do_IRQ:traceoff > set_ftrace_filter
           # echo \!do_IRQ:traceoff > /debug/tracing/set_ftrace_filter
           # echo do_IRQ:traceoff > set_ftrace_filter
      
        The above registers two traceoff probes (one for schedule and one for
        do_IRQ, and then removes do_IRQ.
      
        But since there still exists one for schedule, it is not done
        properly. When adding do_IRQ back, the breakage in the accounting is
        noticed by the ftrace self tests, and it causes a warning and disables
        ftrace"
      
      * tag 'trace-v4.11-rc5-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
        ftrace: Fix removing of second function probe
      48538861
  3. 16 4月, 2017 3 次提交
    • T
      Revert "cgroup: avoid attaching a cgroup root to two different superblocks" · 330c4186
      Tejun Heo 提交于
      This reverts commit bfb0b80d.
      
      Andrei reports CRIU test hangs with the patch applied.  The bug fixed
      by the patch isn't too likely to trigger in actual uses.  Revert the
      patch for now.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Reported-by: NAndrei Vagin <avagin@virtuozzo.com>
      Link: http://lkml.kernel.org/r/20170414232737.GC20350@outlook.office365.com
      330c4186
    • L
      Merge branch 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm · d5ff0814
      Linus Torvalds 提交于
      Pull nvdimm fixes from Dan Williams:
       "A small crop of lockdep, sleeping while atomic, and other fixes /
        band-aids in advance of the full-blown reworks targeting the next
        merge window. The largest change here is "libnvdimm: fix blk free
        space accounting" which deletes a pile of buggy code that better
        testing would have caught before merging. The next change that is
        borderline too big for a late rc is switching the device-dax locking
        from rcu to srcu, I couldn't think of a smaller way to make that fix.
      
        The __copy_user_nocache fix will have a full replacement in 4.12 to
        move those pmem special case considerations into the pmem driver. The
        "libnvdimm: band aid btt vs clear poison locking" commit admits that
        our error clearing support for btt went in broken, so we just disable
        it in 4.11 and -stable. A replacement / full fix is in the pipeline
        for 4.12
      
        Some of these would have been caught earlier had DEBUG_ATOMIC_SLEEP
        been enabled on my development station. I wonder if we should have:
      
            config DEBUG_ATOMIC_SLEEP
              default PROVE_LOCKING
      
        ...since I mistakenly thought I got both with PROVE_LOCKING=y.
      
        These have received a build success notification from the 0day robot,
        and some have appeared in a -next release with no reported issues"
      
      * 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm:
        x86, pmem: fix broken __copy_user_nocache cache-bypass assumptions
        device-dax: switch to srcu, fix rcu_read_lock() vs pte allocation
        libnvdimm: band aid btt vs clear poison locking
        libnvdimm: fix reconfig_mutex, mmap_sem, and jbd2_handle lockdep splat
        libnvdimm: fix blk free space accounting
        acpi, nfit, libnvdimm: fix interleave set cookie calculation (64-bit comparison)
      d5ff0814
    • L
      Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi · 403a39f8
      Linus Torvalds 提交于
      Pull SCSI fixes from James Bottomley:
       "This is seven small fixes which are all for user visible issues that
        fortunately only occur in rare circumstances.
      
        The most serious is the sr one in which QEMU can cause us to read
        beyond the end of a buffer (I don't think it's exploitable, but just
        in case).
      
        The next is the sd capacity fix which means all non 512 byte sector
        drives greater than 2TB fail to be correctly sized.
      
        The rest are either in new drivers (qedf) or on error legs"
      
      * tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
        scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
        scsi: aacraid: fix PCI error recovery path
        scsi: sd: Fix capacity calculation with 32-bit sector_t
        scsi: qla2xxx: Add fix to read correct register value for ISP82xx.
        scsi: qedf: Fix crash due to unsolicited FIP VLAN response.
        scsi: sr: Sanity check returned mode data
        scsi: sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable
      403a39f8