Skip to content
Permalink
Tree: 43151d6c3f
Commits on Apr 24, 2019
  1. vhost, kcov: annotate vhost_worker

    xairy committed Jan 17, 2019
    Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
  2. usb, kcov: annotate hub_event

    xairy committed Jan 17, 2019
    Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
  3. kcov: remote coverage support

    xairy committed Jan 17, 2019
    Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
Commits on Apr 19, 2019
  1. USB: core: Fix bug caused by duplicate interface PM usage counter

    AlanStern authored and gregkh committed Apr 19, 2019
    The syzkaller fuzzer reported a bug in the USB hub driver which turned
    out to be caused by a negative runtime-PM usage counter.  This allowed
    a hub to be runtime suspended at a time when the driver did not expect
    it.  The symptom is a WARNING issued because the hub's status URB is
    submitted while it is already active:
    
    	URB 0000000031fb463e submitted while active
    	WARNING: CPU: 0 PID: 2917 at drivers/usb/core/urb.c:363
    
    The negative runtime-PM usage count was caused by an unfortunate
    design decision made when runtime PM was first implemented for USB.
    At that time, USB class drivers were allowed to unbind from their
    interfaces without balancing the usage counter (i.e., leaving it with
    a positive count).  The core code would take care of setting the
    counter back to 0 before allowing another driver to bind to the
    interface.
    
    Later on when runtime PM was implemented for the entire kernel, the
    opposite decision was made: Drivers were required to balance their
    runtime-PM get and put calls.  In order to maintain backward
    compatibility, however, the USB subsystem adapted to the new
    implementation by keeping an independent usage counter for each
    interface and using it to automatically adjust the normal usage
    counter back to 0 whenever a driver was unbound.
    
    This approach involves duplicating information, but what is worse, it
    doesn't work properly in cases where a USB class driver delays
    decrementing the usage counter until after the driver's disconnect()
    routine has returned and the counter has been adjusted back to 0.
    Doing so would cause the usage counter to become negative.  There's
    even a warning about this in the USB power management documentation!
    
    As it happens, this is exactly what the hub driver does.  The
    kick_hub_wq() routine increments the runtime-PM usage counter, and the
    corresponding decrement is carried out by hub_event() in the context
    of the hub_wq work-queue thread.  This work routine may sometimes run
    after the driver has been unbound from its interface, and when it does
    it causes the usage counter to go negative.
    
    It is not possible for hub_disconnect() to wait for a pending
    hub_event() call to finish, because hub_disconnect() is called with
    the device lock held and hub_event() acquires that lock.  The only
    feasible fix is to reverse the original design decision: remove the
    duplicate interface-specific usage counter and require USB drivers to
    balance their runtime PM gets and puts.  As far as I know, all
    existing drivers currently do this.
    
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Reported-and-tested-by: syzbot+7634edaea4d0b341c625@syzkaller.appspotmail.com
    CC: <stable@vger.kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  2. USB: dummy-hcd: Fix failure to give back unlinked URBs

    AlanStern authored and gregkh committed Apr 18, 2019
    The syzkaller USB fuzzer identified a failure mode in which dummy-hcd
    would never give back an unlinked URB.  This causes usb_kill_urb() to
    hang, leading to WARNINGs and unkillable threads.
    
    In dummy-hcd, all URBs are given back by the dummy_timer() routine as
    it scans through the list of pending URBS.  Failure to give back URBs
    can be caused by failure to start or early exit from the scanning
    loop.  The code currently has two such pathways: One is triggered when
    an unsupported bus transfer speed is encountered, and the other by
    exhausting the simulated bandwidth for USB transfers during a frame.
    
    This patch removes those two paths, thereby allowing all unlinked URBs
    to be given back in a timely manner.  It adds a check for the bus
    speed when the gadget first starts running, so that dummy_timer() will
    never thereafter encounter an unsupported speed.  And it prevents the
    loop from exiting as soon as the total bandwidth has been used up (the
    scanning loop continues, giving back unlinked URBs as they are found,
    but not transferring any more data).
    
    Thanks to Andrey Konovalov for manually running the syzkaller fuzzer
    to help track down the source of the bug.
    
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Reported-and-tested-by: syzbot+d919b0f29d7b5a4994b9@syzkaller.appspotmail.com
    CC: <stable@vger.kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Commits on Apr 16, 2019
  1. USB: core: Fix unterminated string returned by usb_string()

    AlanStern authored and gregkh committed Apr 15, 2019
    Some drivers (such as the vub300 MMC driver) expect usb_string() to
    return a properly NUL-terminated string, even when an error occurs.
    (In fact, vub300's probe routine doesn't bother to check the return
    code from usb_string().)  When the driver goes on to use an
    unterminated string, it leads to kernel errors such as
    stack-out-of-bounds, as found by the syzkaller USB fuzzer.
    
    An out-of-range string index argument is not at all unlikely, given
    that some devices don't provide string descriptors and therefore list
    0 as the value for their string indexes.  This patch makes
    usb_string() return a properly terminated empty string along with the
    -EINVAL error code when an out-of-range index is encountered.
    
    And since a USB string index is a single-byte value, indexes >= 256
    are just as invalid as values of 0 or below.
    
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Reported-by: syzbot+b75b85111c10b8d680f1@syzkaller.appspotmail.com
    CC: <stable@vger.kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Commits on Mar 31, 2019
  1. Linux 5.1-rc3

    torvalds committed Mar 31, 2019
  2. Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm

    torvalds committed Mar 31, 2019
    Pull KVM fixes from Paolo Bonzini:
     "A collection of x86 and ARM bugfixes, and some improvements to
      documentation.
    
      On top of this, a cleanup of kvm_para.h headers, which were exported
      by some architectures even though they not support KVM at all. This is
      responsible for all the Kbuild changes in the diffstat"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm: (28 commits)
      Documentation: kvm: clarify KVM_SET_USER_MEMORY_REGION
      KVM: doc: Document the life cycle of a VM and its resources
      KVM: selftests: complete IO before migrating guest state
      KVM: selftests: disable stack protector for all KVM tests
      KVM: selftests: explicitly disable PIE for tests
      KVM: selftests: assert on exit reason in CR4/cpuid sync test
      KVM: x86: update %rip after emulating IO
      x86/kvm/hyper-v: avoid spurious pending stimer on vCPU init
      kvm/x86: Move MSR_IA32_ARCH_CAPABILITIES to array emulated_msrs
      KVM: x86: Emulate MSR_IA32_ARCH_CAPABILITIES on AMD hosts
      kvm: don't redefine flags as something else
      kvm: mmu: Used range based flushing in slot_handle_level_range
      KVM: export <linux/kvm_para.h> and <asm/kvm_para.h> iif KVM is supported
      KVM: x86: remove check on nr_mmu_pages in kvm_arch_commit_memory_region()
      kvm: nVMX: Add a vmentry check for HOST_SYSENTER_ESP and HOST_SYSENTER_EIP fields
      KVM: SVM: Workaround errata#1096 (insn_len maybe zero on SMAP violation)
      KVM: Reject device ioctls from processes other than the VM's creator
      KVM: doc: Fix incorrect word ordering regarding supported use of APIs
      KVM: x86: fix handling of role.cr4_pae and rename it to 'gpte_size'
      KVM: nVMX: Do not inherit quadrant and invalid for the root shadow EPT
      ...
  3. Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/l…

    torvalds committed Mar 31, 2019
    …inux/kernel/git/tip/tip
    
    Pull x86 fixes from Thomas Gleixner:
     "A pile of x86 updates:
    
       - Prevent exceeding he valid physical address space in the /dev/mem
         limit checks.
    
       - Move all header content inside the header guard to prevent compile
         failures.
    
       - Fix the bogus __percpu annotation in this_cpu_has() which makes
         sparse very noisy.
    
       - Disable switch jump tables completely when retpolines are enabled.
    
       - Prevent leaking the trampoline address"
    
    * 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/realmode: Make set_real_mode_mem() static inline
      x86/cpufeature: Fix __percpu annotation in this_cpu_has()
      x86/mm: Don't exceed the valid physical address space
      x86/retpolines: Disable switch jump tables when retpolines are enabled
      x86/realmode: Don't leak the trampoline kernel address
      x86/boot: Fix incorrect ifdeffery scope
      x86/resctrl: Remove unused variable
  4. Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/…

    torvalds committed Mar 31, 2019
    …linux/kernel/git/tip/tip
    
    Pull perf tooling fixes from Thomas Gleixner:
     "Core libraries:
       - Fix max perf_event_attr.precise_ip detection.
       - Fix parser error for uncore event alias
       - Fixup ordering of kernel maps after obtaining the main kernel map
         address.
    
      Intel PT:
       - Fix TSC slip where A TSC packet can slip past MTC packets so that
         the timestamp appears to go backwards.
       - Fixes for exported-sql-viewer GUI conversion to python3.
    
      ARM coresight:
       - Fix the build by adding a missing case value for enumeration value
         introduced in newer library, that now is the required one.
    
      tool headers:
       - Syncronize kernel headers with the kernel, getting new io_uring and
         pidfd_send_signal syscalls so that 'perf trace' can handle them"
    
    * 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      perf pmu: Fix parser error for uncore event alias
      perf scripts python: exported-sql-viewer.py: Fix python3 support
      perf scripts python: exported-sql-viewer.py: Fix never-ending loop
      perf machine: Update kernel map address and re-order properly
      tools headers uapi: Sync powerpc's asm/kvm.h copy with the kernel sources
      tools headers: Update x86's syscall_64.tbl and uapi/asm-generic/unistd
      tools headers uapi: Update drm/i915_drm.h
      tools arch x86: Sync asm/cpufeatures.h with the kernel sources
      tools headers uapi: Sync linux/fcntl.h to get the F_SEAL_FUTURE_WRITE addition
      tools headers uapi: Sync asm-generic/mman-common.h and linux/mman.h
      perf evsel: Fix max perf_event_attr.precise_ip detection
      perf intel-pt: Fix TSC slip
      perf cs-etm: Add missing case value
  5. Merge branch 'smp-urgent-for-linus' of git://git.kernel.org/pub/scm/l…

    torvalds committed Mar 31, 2019
    …inux/kernel/git/tip/tip
    
    Pull CPU hotplug fixes from Thomas Gleixner:
     "Two SMT/hotplug related fixes:
    
       - Prevent crash when HOTPLUG_CPU is disabled and the CPU bringup
         aborts. This is triggered with the 'nosmt' command line option, but
         can happen by any abort condition. As the real unplug code is not
         compiled in, prevent the fail by keeping the CPU in zombie state.
    
       - Enforce HOTPLUG_CPU for SMP on x86 to avoid the above situation
         completely. With 'nosmt' being a popular option it's required to
         unplug the half brought up sibling CPUs (due to the MCE wreckage)
         completely"
    
    * 'smp-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/smp: Enforce CONFIG_HOTPLUG_CPU when SMP=y
      cpu/hotplug: Prevent crash when CPU bringup fails on CONFIG_HOTPLUG_CPU=n
  6. Merge branch 'locking-urgent-for-linus' of git://git.kernel.org/pub/s…

    torvalds committed Mar 31, 2019
    …cm/linux/kernel/git/tip/tip
    
    Pull locking fixlet from Thomas Gleixner:
     "Trivial update to the maintainers file"
    
    * 'locking-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      MAINTAINERS: Remove deleted file from futex file pattern
  7. Merge branch 'core-urgent-for-linus' of git://git.kernel.org/pub/scm/…

    torvalds committed Mar 31, 2019
    …linux/kernel/git/tip/tip
    
    Pull core fixes from Thomas Gleixner:
     "A small set of core updates:
    
       - Make the watchdog respect the selected CPU mask again. That was
         broken by the rework of the watchdog thread management and caused
         inconsistent state and NMI watchdog being unstoppable.
    
       - Ensure that the objtool build can find the libelf location.
    
       - Remove dead kcore stub code"
    
    * 'core-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      watchdog: Respect watchdog cpumask on CPU hotplug
      objtool: Query pkg-config for libelf location
      proc/kcore: Remove unused kclist_add_remap()
  8. Merge tag 'powerpc-5.1-4' of git://git.kernel.org/pub/scm/linux/kerne…

    torvalds committed Mar 31, 2019
    …l/git/powerpc/linux
    
    Pull powerpc fixes from Michael Ellerman:
     "Three non-regression fixes.
    
       - Our optimised memcmp could read past the end of one of the buffers
         and potentially trigger a page fault leading to an oops.
    
       - Some of our code to read energy management data on PowerVM had an
         endian bug leading to bogus results.
    
       - When reporting a machine check exception we incorrectly reported
         TLB multihits as D-Cache multhits due to a missing entry in the
         array of causes.
    
      Thanks to: Chandan Rajendra, Gautham R. Shenoy, Mahesh Salgaonkar,
      Segher Boessenkool, Vaidyanathan Srinivasan"
    
    * tag 'powerpc-5.1-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
      powerpc/pseries/mce: Fix misleading print for TLB mutlihit
      powerpc/pseries/energy: Use OF accessor functions to read ibm,drc-indexes
      powerpc/64: Fix memcmp reading past the end of src/dest
  9. Merge tag 'dmaengine-fix-5.1-rc3' of git://git.infradead.org/users/vk…

    torvalds committed Mar 31, 2019
    …oul/slave-dma
    
    Pull dmaengine fixes from Vinod Koul:
    
     - Revert "dmaengine: stm32-mdma: Add a check on read_u32_array" as that
       caused regression
    
     - Fix MAINTAINER file uniphier-mdmac.c file path
    
    * tag 'dmaengine-fix-5.1-rc3' of git://git.infradead.org/users/vkoul/slave-dma:
      MAINTAINERS: Fix uniphier-mdmac.c file path
      dmaengine: stm32-mdma: Revert "dmaengine: stm32-mdma: Add a check on read_u32_array"
Commits on Mar 30, 2019
  1. Merge tag 'led-fixes-for-5.1-rc3' of git://git.kernel.org/pub/scm/lin…

    torvalds committed Mar 30, 2019
    …ux/kernel/git/j.anaszewski/linux-leds
    
    Pull LED fixes from Jacek Anaszewski:
    
     - fix refcnt leak on interface rename
    
     - use memcpy in device_name_store() to avoid including garbage from a
       previous, longer value in the device_name
    
     - fix a potential NULL pointer dereference in case of_match_device()
       cannot find a match
    
    * tag 'led-fixes-for-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds:
      leds: trigger: netdev: use memcpy in device_name_store
      leds: pca9532: fix a potential NULL pointer dereference
      leds: trigger: netdev: fix refcnt leak on interface rename
  2. Merge tag 'gpio-v5.1-2' of git://git.kernel.org/pub/scm/linux/kernel/…

    torvalds committed Mar 30, 2019
    …git/linusw/linux-gpio
    
    Pull GPIO fixes from Linus Walleij:
     "As you can see [in the git history] I was away on leave and Bartosz
      kindly stepped in and collected a slew of fixes, I pulled them into my
      tree in two sets and merged some two more fixes (fixing my own caused
      bugs) on top.
    
      Summary:
    
       - Revert the extended use of gpio_set_config() and think about how we
         can do this properly.
    
       - Fix up the SPI CS GPIO handling so it now works properly on the SPI
         bus children, as intended.
    
       - Error paths and driver fixes"
    
    * tag 'gpio-v5.1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio:
      gpio: mockup: use simple_read_from_buffer() in debugfs read callback
      gpio: of: Fix of_gpiochip_add() error path
      gpio: of: Check for "spi-cs-high" in child instead of parent node
      gpio: of: Check propname before applying "cs-gpios" quirks
      gpio: mockup: fix debugfs read
      Revert "gpio: use new gpio_set_config() helper in more places"
      gpio: aspeed: fix a potential NULL pointer dereference
      gpio: amd-fch: Fix bogus SPDX identifier
      gpio: adnp: Fix testing wrong value in adnp_gpio_direction_input
      gpio: exar: add a check for the return value of ida_simple_get fails
  3. leds: trigger: netdev: use memcpy in device_name_store

    Villemoes authored and jacek-anaszewski committed Mar 14, 2019
    If userspace doesn't end the input with a newline (which can easily
    happen if the write happens from a C program that does write(fd,
    iface, strlen(iface))), we may end up including garbage from a
    previous, longer value in the device_name. For example
    
    # cat device_name
    
    # printf 'eth12' > device_name
    # cat device_name
    eth12
    # printf 'eth3' > device_name
    # cat device_name
    eth32
    
    I highly doubt anybody is relying on this behaviour, so switch to
    simply copying the bytes (we've already checked that size is <
    IFNAMSIZ) and unconditionally zero-terminate it; of course, we also
    still have to strip a trailing newline.
    
    This is also preparation for future patches.
    
    Fixes: 06f502f ("leds: trigger: Introduce a NETDEV trigger")
    Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
    Acked-by: Pavel Machek <pavel@ucw.cz>
    Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
  4. leds: pca9532: fix a potential NULL pointer dereference

    kengiter authored and jacek-anaszewski committed Mar 9, 2019
    In case of_match_device cannot find a match, return -EINVAL to avoid
    NULL pointer dereference.
    
    Fixes: fa4191a ("leds: pca9532: Add device tree support")
    Signed-off-by: Kangjie Lu <kjlu@umn.edu>
    Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
  5. Merge tag 'staging-5.1-rc3' of git://git.kernel.org/pub/scm/linux/ker…

    torvalds committed Mar 30, 2019
    …nel/git/gregkh/staging
    
    Pull staging driver fixes from Greg KH:
     "Here are some small staging driver fixes for 5.1-rc3, and one driver
      removal.
    
      The biggest thing here is the removal of the mt7621-eth driver as a
      "real" network driver was merged in 5.1-rc1 for this hardware, so this
      old driver can now be removed.
    
      Other than that, there are just a number of small fixes, all resolving
      reported issues and some potential corner cases for error handling
      paths.
    
      All of these have been in linux-next with no reported issues"
    
    * tag 'staging-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging:
      staging: vt6655: Remove vif check from vnt_interrupt
      staging: erofs: keep corrupted fs from crashing kernel in erofs_readdir()
      staging: octeon-ethernet: fix incorrect PHY mode
      staging: vc04_services: Fix an error code in vchiq_probe()
      staging: erofs: fix error handling when failed to read compresssed data
      staging: vt6655: Fix interrupt race condition on device start up.
      staging: rtlwifi: Fix potential NULL pointer dereference of kzalloc
      staging: rtl8712: uninitialized memory in read_bbreg_hdl()
      staging: rtlwifi: rtl8822b: fix to avoid potential NULL pointer dereference
      staging: rtl8188eu: Fix potential NULL pointer dereference of kcalloc
      staging, mt7621-pci: fix build without pci support
      staging: speakup_soft: Fix alternate speech with other synths
      staging: axis-fifo: add CONFIG_OF dependency
      staging: olpc_dcon_xo_1: add missing 'const' qualifier
      staging: comedi: ni_mio_common: Fix divide-by-zero for DIO cmdtest
      staging: erofs: fix to handle error path of erofs_vmap()
      staging: mt7621-dts: update ethernet settings.
      staging: remove mt7621-eth
  6. Merge tag 'tty-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/…

    torvalds committed Mar 30, 2019
    …git/gregkh/tty
    
    Pull tty/serial fixes from Greg KH:
     "Here are some small tty and serial driver fixes for 5.1-rc3.
    
      Nothing major here, just a number of potential problems fixes for
      error handling paths, as well as some other minor bugfixes for
      reported issues with 5.1-rc1.
    
      All of these have been in linux-next with no reported issues"
    
    * tag 'tty-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:
      tty: fix NULL pointer issue when tty_port ops is not set
      Disable kgdboc failed by echo space to /sys/module/kgdboc/parameters/kgdboc
      dt-bindings: serial: Add compatible for Mediatek MT8183
      tty/serial: atmel: RS485 HD w/DMA: enable RX after TX is stopped
      tty/serial: atmel: Add is_half_duplex helper
      serial: sh-sci: Fix setting SCSCR_TIE while transferring data
      serial: ar933x_uart: Fix build failure with disabled console
      tty: serial: qcom_geni_serial: Initialize baud in qcom_geni_console_setup
      sc16is7xx: missing unregister/delete driver on error in sc16is7xx_init()
      tty: mxs-auart: fix a potential NULL pointer dereference
      tty: atmel_serial: fix a potential NULL pointer dereference
      serial: max310x: Fix to avoid potential NULL pointer dereference
      serial: mvebu-uart: Fix to avoid a potential NULL pointer dereference
  7. Merge tag 'usb-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/…

    torvalds committed Mar 30, 2019
    …git/gregkh/usb
    
    Pull USB fixes from Greg KH:
     "Here are some small USB fixes for 5.1-rc3.
    
      Nothing major at all here, just a small collection of fixes for
      reported issues, and potential problems with error handling paths.
      Also a few new device ids, as normal.
    
      All of these have been in linux-next with no reported issues"
    
    * tag 'usb-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb: (25 commits)
      USB: serial: option: add Olicard 600
      USB: serial: cp210x: add new device id
      usb: u132-hcd: fix resource leak
      usb: cdc-acm: fix race during wakeup blocking TX traffic
      usb: mtu3: fix EXTCON dependency
      usb: usb251xb: fix to avoid potential NULL pointer dereference
      usb: core: Try generic PHY_MODE_USB_HOST if usb_phy_roothub_set_mode fails
      phy: sun4i-usb: Support set_mode to USB_HOST for non-OTG PHYs
      xhci: Don't let USB3 ports stuck in polling state prevent suspend
      usb: xhci: dbc: Don't free all memory with spinlock held
      xhci: Fix port resume done detection for SS ports with LPM enabled
      USB: serial: mos7720: fix mos_parport refcount imbalance on error path
      USB: gadget: f_hid: fix deadlock in f_hidg_write()
      usb: gadget: net2272: Fix net2272_dequeue()
      usb: gadget: net2280: Fix net2280_dequeue()
      usb: gadget: net2280: Fix overrun of OUT messages
      usb: dwc3: pci: add support for Comet Lake PCH ID
      usb: usb251xb: Remove unnecessary comparison of unsigned integer with >= 0
      usb: common: Consider only available nodes for dr_mode
      usb: typec: tcpm: Try PD-2.0 if sink does not respond to 3.0 source-caps
      ...
  8. Merge tag 'acpi-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel…

    torvalds committed Mar 30, 2019
    …/git/rafael/linux-pm
    
    Pull ACPI fix from Rafael Wysocki:
     "This corrects a previous attempt to make Linux use its own set of ACPI
      debug flags different from the upstream ACPICA's default (Erik
      Schmauss)"
    
    * tag 'acpi-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      ACPI: use different default debug value than ACPICA
  9. Merge tag 'pm-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/g…

    torvalds committed Mar 30, 2019
    …it/rafael/linux-pm
    
    Pull power management fixes from Rafael Wysocki:
     "These fix CPU base frequency reporting in the intel_pstate driver and
      a use-after-free in the scpi-cpufreq driver.
    
      Specifics:
    
       - Fix the ACPI CPPC library to actually follow the specification when
         decoding the guaranteed performance register information and make
         the intel_pstate driver to fall back to the nominal frequency when
         reporting the base frequency if the guaranteed performance register
         information is not there (Srinivas Pandruvada).
    
       - Fix use-after-free in the exit callback of the scpi-cpufreq left
         after an update during the 5.0 development cycle (Vincent Stehlé)"
    
    * tag 'pm-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      cpufreq: scpi: Fix use after free
      cpufreq: intel_pstate: Also use CPPC nominal_perf for base_frequency
      ACPI / CPPC: Fix guaranteed performance handling
  10. Merge branch 'fixes-v5.1-a' of git://git.kernel.org/pub/scm/linux/ker…

    torvalds committed Mar 30, 2019
    …nel/git/jmorris/linux-security
    
    Pull security layer fixes from James Morris:
     "Yama and LSM config fixes"
    
    * 'fixes-v5.1-a' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security:
      LSM: Revive CONFIG_DEFAULT_SECURITY_* for "make oldconfig"
      Yama: mark local symbols as static
Commits on Mar 29, 2019
  1. Merge branch 'akpm' (patches from Andrew)

    torvalds committed Mar 29, 2019
    Merge misc fixes from Andrew Morton:
     "22 fixes"
    
    * emailed patches from Andrew Morton <akpm@linux-foundation.org>: (22 commits)
      fs/proc/proc_sysctl.c: fix NULL pointer dereference in put_links
      fs: fs_parser: fix printk format warning
      checkpatch: add %pt as a valid vsprintf extension
      mm/migrate.c: add missing flush_dcache_page for non-mapped page migrate
      drivers/block/zram/zram_drv.c: fix idle/writeback string compare
      mm/page_isolation.c: fix a wrong flag in set_migratetype_isolate()
      mm/memory_hotplug.c: fix notification in offline error path
      ptrace: take into account saved_sigmask in PTRACE{GET,SET}SIGMASK
      fs/proc/kcore.c: make kcore_modules static
      include/linux/list.h: fix list_is_first() kernel-doc
      mm/debug.c: fix __dump_page when mapping->host is not set
      mm: mempolicy: make mbind() return -EIO when MPOL_MF_STRICT is specified
      include/linux/hugetlb.h: convert to use vm_fault_t
      iommu/io-pgtable-arm-v7s: request DMA32 memory, and improve debugging
      mm: add support for kmem caches in DMA32 zone
      ocfs2: fix inode bh swapping mixup in ocfs2_reflink_inodes_lock
      mm/hotplug: fix offline undo_isolate_page_range()
      fs/open.c: allow opening only regular files during execve()
      mailmap: add Changbin Du
      mm/debug.c: add a cast to u64 for atomic64_read()
      ...
  2. Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/…

    torvalds committed Mar 29, 2019
    …git/arm64/linux
    
    Pull arm64 fix from Catalin Marinas:
     "Use memblock_alloc() instead of memblock_alloc_low() in
      request_standard_resources(), the latter being limited to the low 4G
      memory range on arm64"
    
    * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
      arm64: replace memblock_alloc_low with memblock_alloc
  3. Merge tag 'iommu-fixes-v5.1-rc3' of git://git.kernel.org/pub/scm/linu…

    torvalds committed Mar 29, 2019
    …x/kernel/git/joro/iommu
    
    Pull IOMMU fixes from Joerg Roedel:
    
     - Fix a bug in the AMD IOMMU driver not handling exclusion ranges
       correctly. In fact the driver did not reserve these ranges for IOVA
       allocations, so that dma-handles could be allocated in an exclusion
       range, leading to data corruption. Exclusion ranges have not been
       used by any firmware up to now, so this issue remained undiscovered
       for quite some time.
    
     - Fix wrong warning messages that the IOMMU core code prints when it
       tries to allocate the default domain for an iommu group and the
       driver does not support any of the default domain types (like Intel
       VT-d).
    
    * tag 'iommu-fixes-v5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu:
      iommu/amd: Reserve exclusion range in iova-domain
      iommu: Don't print warning when IOMMU driver only supports unmanaged domains
  4. Merge tag 'driver-core-5.1-rc3' of git://git.kernel.org/pub/scm/linux…

    torvalds committed Mar 29, 2019
    …/kernel/git/gregkh/driver-core
    
    Pull driver core fix from Greg KH:
     "Here is a single driver core patch for 5.1-rc3.
    
      After 5.1-rc1, all of the users of BUS_ATTR() are finally removed, so
      we can now drop this macro from include/linux/device.h so that no more
      new users will be created.
    
      This patch has been in linux-next for a while, with no reported
      issues"
    
    * tag 'driver-core-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
      driver core: remove BUS_ATTR()
  5. Merge tag 'char-misc-5.1-rc3' of git://git.kernel.org/pub/scm/linux/k…

    torvalds committed Mar 29, 2019
    …ernel/git/gregkh/char-misc
    
    Pull char/misc driver fixes from Greg KH:
     "Here are some binder, habanalabs, and vboxguest driver fixes for
      5.1-rc3.
    
      The Binder fixes resolve some reported issues found by testing, first
      by the selinux developers, and then earlier today by syzbot.
    
      The habanalabs fixes are all minor, resolving a number of tiny things.
    
      The vboxguest patches are a bit larger. They resolve the fact that
      virtual box decided to change their api in their latest release in a
      way that broke the existing kernel code, despite saying that they were
      never going to do that. So this is a bit of a "new feature", but is
      good to get merged so that 5.1 will work with the latest release. The
      changes are not large and of course virtual box "swears" they will not
      break this again, but no one is holding their breath here.
    
      All of these have been in linux-next for a while with no reported
      issues"
    
    * tag 'char-misc-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc:
      virt: vbox: Implement passing requestor info to the host for VirtualBox 6.0.x
      binder: fix race between munmap() and direct reclaim
      binder: fix BUG_ON found by selinux-testsuite
      habanalabs: cast to expected type
      habanalabs: prevent host crash during suspend/resume
      habanalabs: perform accounting for active CS
      habanalabs: fix mapping with page size bigger than 4KB
      habanalabs: complete user context cleanup before hard reset
      habanalabs: fix bug when mapping very large memory area
      habanalabs: fix MMU number of pages calculation
  6. Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/g…

    torvalds committed Mar 29, 2019
    …it/jejb/scsi
    
    Pull SCSI fixes from James Bottomley:
     "Thirteen fixes, seven of which are for IBM fibre channel and three
      additional for fairly serious bugs in drivers (qla2xxx, mpt3sas,
      aacraid).
    
      Of the three core fixes, the most significant is probably the missed
      run queue causing an indefinite hang. The others are fixing a
      potential use after free on device close and silencing an incorrect
      warning"
    
    * tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
      scsi: ibmvfc: Clean up transport events
      scsi: ibmvfc: Byte swap status and error codes when logging
      scsi: ibmvfc: Add failed PRLI to cmd_status lookup array
      scsi: ibmvfc: Remove "failed" from logged errors
      scsi: zfcp: reduce flood of fcrscn1 trace records on multi-element RSCN
      scsi: zfcp: fix scsi_eh host reset with port_forced ERP for non-NPIV FCP devices
      scsi: zfcp: fix rport unblock if deleted SCSI devices on Scsi_Host
      scsi: sd: Quiesce warning if device does not report optimal I/O size
      scsi: sd: Fix a race between closing an sd device and sd I/O
      scsi: core: Run queue when state is set to running after being blocked
      scsi: qla4xxx: fix a potential NULL pointer dereference
      scsi: aacraid: Insure we don't access PCIe space during AER/EEH
      scsi: mpt3sas: Fix kernel panic during expander reset
  7. Merge branch 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/…

    torvalds committed Mar 29, 2019
    …kernel/git/wsa/linux
    
    Pull i2c fixes from Wolfram Sang:
     "A new ID for the i801 driver and some Documentation fixes to make it
      easier for people to find the bindings (which is also a basis for
      further improvements in that area)"
    
    * 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux:
      i2c: wmt: make bindings file name match the driver
      i2c: sun6i-p2wi: make bindings file name match the driver
      i2c: stu300: make bindings file name match the driver
      i2c: mt65xx: make bindings file name match the driver
      i2c: iop3xx: make bindings file name match the driver
      i2c: i801: Add support for Intel Comet Lake
  8. Merge tag 'sound-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kerne…

    torvalds committed Mar 29, 2019
    …l/git/tiwai/sound
    
    Pull sound fixes from Takashi Iwai:
     "The important fixes at this time are a couple fixes in ALSA core: a
      fix for PCM is about the OOB access in PCM OSS plugins that has been
      for long time, but hasn't hit so often until now just because we
      allocated a large buffer via vmalloc(), and surfaced more often after
      switching to kvmalloc(). Another fix is for a long-standing PCM
      problem wrt racy PM resume.
    
      Others are trivial nospec coverage and usual HD-audio quirks"
    
    * tag 'sound-5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound:
      ALSA: hda/realtek - Fix speakers on Acer Predator Helios 500 Ryzen laptops
      ALSA: pcm: Don't suspend stream in unrecoverable PCM state
      ALSA: hda/ca0132 - Simplify alt firmware loading code
      ALSA: pcm: Fix possible OOB access in PCM oss plugins
      ALSA: hda/realtek: Enable headset MIC of ASUS X430UN and X512DK with ALC256
      ALSA: hda/realtek: Enable headset mic of ASUS P5440FF with ALC256
      ALSA: hda/realtek: Enable ASUS X441MB and X705FD headset MIC with ALC256
      ALSA: hda/realtek - Add support for Acer Aspire E5-523G/ES1-432 headset mic
      ALSA: hda/realtek: Enable headset MIC of Acer Aspire Z24-890 with ALC286
      ALSA: seq: oss: Fix Spectre v1 vulnerability
      ALSA: rawmidi: Fix potential Spectre v1 vulnerability
  9. Merge tag 'kbuild-fixes-v5.1' of git://git.kernel.org/pub/scm/linux/k…

    torvalds committed Mar 29, 2019
    …ernel/git/masahiroy/linux-kbuild
    
    Pull Kbuild fixes from Masahiro Yamada:
    
     - Remove harmful -Oz option of Clang
    
     - Get back the original behavior (no recursion for in-tree build) for
       GNU Make 4.x
    
     - Some minor fixes for coccinelle patches
    
     - Do not overwrite .gitignore in the output directory in case it is
       version-controlled
    
     - Fix missed record-mcount bug for dynamic ftrace
    
     - Fix endianness bug in modversions for relative CRC
    
     - Cater to '^H' key code in Kconfig ncurses programs
    
    * tag 'kbuild-fixes-v5.1' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild:
      kconfig/[mn]conf: handle backspace (^H) key
      kbuild: modversions: Fix relative CRC byte order interpretation
      scripts: coccinelle: Fix description of badty.cocci
      kbuild: strip whitespace in cmd_record_mcount findstring
      kbuild: do not overwrite .gitignore in output directory
      kbuild: skip parsing pre sub-make code for recursion
      coccinelle: put_device: reduce false positives
      kbuild: skip sub-make for in-tree build with GNU Make 4.x
      Revert "kbuild: use -Oz instead of -Os when using clang"
Older
You can’t perform that action at this time.