1. 28 Apr, 2020 8 commits
    • John Stultz's avatar
      driver core: Ensure wait_for_device_probe() waits until the deferred_probe_timeout fires · 35a67236
      John Stultz authored
      In commit c8c43cee ("driver core: Fix
      driver_deferred_probe_check_state() logic"), we set the default
      driver_deferred_probe_timeout value to 30 seconds to allow for
      drivers that are missing dependencies to have some time so that
      the dependency may be loaded from userland after initcalls_done
      is set.
      
      However, Yoshihiro Shimoda reported that on his device that
      expects to have unmet dependencies (due to "optional links" in
      its devicetree), was failing to mount the NFS root.
      
      In digging further, it seemed the problem was that while the
      device properly probes after waiting 30 seconds for any missing
      modules to load, the ip_auto_config() had already failed,
      resulting in NFS to fail. This was due to ip_auto_config()
      calling wait_for_device_probe() which doesn't wait for the
      driver_deferred_probe_timeout to fire.
      
      This patch tries to fix the issue by creating a waitqueue
      for the driver_deferred_probe_timeout, and calling wait_event()
      to make sure driver_deferred_probe_timeout is zero in
      wait_for_device_probe() to make sure all the probing is
      finished.
      
      The downside to this solution is that kernel functionality that
      uses wait_for_device_probe(), will block until the
      driver_deferred_probe_timeout fires, regardless of if there is
      any missing dependencies.
      
      However, the previous patch reverts the default timeout value to
      zero, so this side-effect will only affect users who specify a
      driver_deferred_probe_timeout= value as a boot argument, where
      the additional delay would be beneficial to allow modules to
      load later during boot.
      
      Thanks to Geert for chasing down that ip_auto_config was why NFS
      was failing in this case!
      
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
      Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
      Cc: Jakub Kicinski <kuba@kernel.org>
      Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
      Cc: Rob Herring <robh@kernel.org>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
      Cc: Robin Murphy <robin.murphy@arm.com>
      Cc: Andy Shevchenko <andy.shevchenko@gmail.com>
      Cc: Sudeep Holla <sudeep.holla@arm.com>
      Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
      Cc: Naresh Kamboju <naresh.kamboju@linaro.org>
      Cc: Basil Eljuse <Basil.Eljuse@arm.com>
      Cc: Ferry Toth <fntoth@gmail.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Anders Roxell <anders.roxell@linaro.org>
      Cc: linux-pm@vger.kernel.org
      Reported-by: default avatarYoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
      Tested-by: default avatarGeert Uytterhoeven <geert+renesas@glider.be>
      Tested-by: default avatarYoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
      Fixes: c8c43cee ("driver core: Fix driver_deferred_probe_check_state() logic")
      Signed-off-by: default avatarJohn Stultz <john.stultz@linaro.org>
      Link: https://lore.kernel.org/r/20200422203245.83244-4-john.stultz@linaro.orgSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      35a67236
    • John Stultz's avatar
      driver core: Use dev_warn() instead of dev_WARN() for deferred_probe_timeout warnings · 4ccc03e2
      John Stultz authored
      In commit c8c43cee ("driver core: Fix
      driver_deferred_probe_check_state() logic") and following
      changes the logic was changes slightly so that if there is no
      driver to match whats found in the dtb, we wait the sepcified
      seconds for modules to be loaded by userland, and then timeout,
      where as previously we'd print "ignoring dependency for device,
      assuming no driver" and immediately return -ENODEV after
      initcall_done.
      
      However, in the timeout case (which previously existed but was
      practicaly un-used without a boot argument), the timeout message
      uses dev_WARN(). This means folks are now seeing a big backtrace
      in their boot logs if there a entry in their dts that doesn't
      have a driver.
      
      To fix this, lets use dev_warn(), instead of dev_WARN() to match
      the previous error path.
      
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
      Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
      Cc: Jakub Kicinski <kuba@kernel.org>
      Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
      Cc: Rob Herring <robh@kernel.org>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
      Cc: Robin Murphy <robin.murphy@arm.com>
      Cc: Andy Shevchenko <andy.shevchenko@gmail.com>
      Cc: Sudeep Holla <sudeep.holla@arm.com>
      Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
      Cc: Naresh Kamboju <naresh.kamboju@linaro.org>
      Cc: Basil Eljuse <Basil.Eljuse@arm.com>
      Cc: Ferry Toth <fntoth@gmail.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Anders Roxell <anders.roxell@linaro.org>
      Cc: linux-pm@vger.kernel.org
      Reviewed-by: default avatarYoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
      Fixes: c8c43cee ("driver core: Fix driver_deferred_probe_check_state() logic")
      Signed-off-by: default avatarJohn Stultz <john.stultz@linaro.org>
      Link: https://lore.kernel.org/r/20200422203245.83244-3-john.stultz@linaro.orgSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      4ccc03e2
    • John Stultz's avatar
      driver core: Revert default driver_deferred_probe_timeout value to 0 · ce68929f
      John Stultz authored
      This patch addresses a regression in 5.7-rc1+
      
      In commit c8c43cee ("driver core: Fix
      driver_deferred_probe_check_state() logic"), we both cleaned up
      the logic and also set the default driver_deferred_probe_timeout
      value to 30 seconds to allow for drivers that are missing
      dependencies to have some time so that the dependency may be
      loaded from userland after initcalls_done is set.
      
      However, Yoshihiro Shimoda reported that on his device that
      expects to have unmet dependencies (due to "optional links" in
      its devicetree), was failing to mount the NFS root.
      
      In digging further, it seemed the problem was that while the
      device properly probes after waiting 30 seconds for any missing
      modules to load, the ip_auto_config() had already failed,
      resulting in NFS to fail. This was due to ip_auto_config()
      calling wait_for_device_probe() which doesn't wait for the
      driver_deferred_probe_timeout to fire.
      
      Fixing that issue is possible, but could also introduce 30
      second delays in bootups for users who don't have any
      missing dependencies, which is not ideal.
      
      So I think the best solution to avoid any regressions is to
      revert back to a default timeout value of zero, and allow
      systems that need to utilize the timeout in order for userland
      to load any modules that supply misisng dependencies in the dts
      to specify the timeout length via the exiting documented boot
      argument.
      
      Thanks to Geert for chasing down that ip_auto_config was why NFS
      was failing in this case!
      
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
      Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
      Cc: Jakub Kicinski <kuba@kernel.org>
      Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
      Cc: Rob Herring <robh@kernel.org>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
      Cc: Robin Murphy <robin.murphy@arm.com>
      Cc: Andy Shevchenko <andy.shevchenko@gmail.com>
      Cc: Sudeep Holla <sudeep.holla@arm.com>
      Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
      Cc: Naresh Kamboju <naresh.kamboju@linaro.org>
      Cc: Basil Eljuse <Basil.Eljuse@arm.com>
      Cc: Ferry Toth <fntoth@gmail.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Anders Roxell <anders.roxell@linaro.org>
      Reported-by: default avatarYoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
      Tested-by: default avatarYoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
      Tested-by: default avatarGeert Uytterhoeven <geert+renesas@glider.be>
      Fixes: c8c43cee ("driver core: Fix driver_deferred_probe_check_state() logic")
      Signed-off-by: default avatarJohn Stultz <john.stultz@linaro.org>
      Link: https://lore.kernel.org/r/20200422203245.83244-2-john.stultz@linaro.orgSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ce68929f
    • James Hilliard's avatar
      component: Silence bind error on -EPROBE_DEFER · 7706b0a7
      James Hilliard authored
      If a component fails to bind due to -EPROBE_DEFER we should not log an
      error as this is not a real failure.
      
      Fixes messages like:
      vc4-drm soc:gpu: failed to bind 3f902000.hdmi (ops vc4_hdmi_ops): -517
      vc4-drm soc:gpu: master bind failed: -517
      Signed-off-by: default avatarJames Hilliard <james.hilliard1@gmail.com>
      Link: https://lore.kernel.org/r/20200411190241.89404-1-james.hilliard1@gmail.comSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      7706b0a7
    • Saravana Kannan's avatar
      driver core: Fix handling of fw_devlink=permissive · 00b24755
      Saravana Kannan authored
      When commit 8375e74f ("driver core: Add fw_devlink kernel
      commandline option") added fw_devlink, it didn't implement "permissive"
      mode correctly.
      
      That commit got the device links flags correct to make sure unprobed
      suppliers don't block the probing of a consumer. However, if a consumer
      is waiting for mandatory suppliers to register, that could still block a
      consumer from probing.
      
      This commit fixes that by making sure in permissive mode, all suppliers
      to a consumer are treated as a optional suppliers. So, even if a
      consumer is waiting for suppliers to register and link itself (using the
      DL_FLAG_SYNC_STATE_ONLY flag) to the supplier, the consumer is never
      blocked from probing.
      
      Fixes: 8375e74f ("driver core: Add fw_devlink kernel commandline option")
      Reported-by: default avatarMarek Szyprowski <m.szyprowski@samsung.com>
      Signed-off-by: default avatarSaravana Kannan <saravanak@google.com>
      Tested-by: default avatarMarek Szyprowski <m.szyprowski@samsung.com>
      Link: https://lore.kernel.org/r/20200331022832.209618-1-saravanak@google.comSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      00b24755
    • Luis Chamberlain's avatar
      coredump: fix crash when umh is disabled · 3740d93e
      Luis Chamberlain authored
      Commit 64e90a8a ("Introduce STATIC_USERMODEHELPER to mediate
      call_usermodehelper()") added the optiont to disable all
      call_usermodehelper() calls by setting STATIC_USERMODEHELPER_PATH to
      an empty string. When this is done, and crashdump is triggered, it
      will crash on null pointer dereference, since we make assumptions
      over what call_usermodehelper_exec() did.
      
      This has been reported by Sergey when one triggers a a coredump
      with the following configuration:
      
      ```
      CONFIG_STATIC_USERMODEHELPER=y
      CONFIG_STATIC_USERMODEHELPER_PATH=""
      kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e
      ```
      
      The way disabling the umh was designed was that call_usermodehelper_exec()
      would just return early, without an error. But coredump assumes
      certain variables are set up for us when this happens, and calls
      ile_start_write(cprm.file) with a NULL file.
      
      [    2.819676] BUG: kernel NULL pointer dereference, address: 0000000000000020
      [    2.819859] #PF: supervisor read access in kernel mode
      [    2.820035] #PF: error_code(0x0000) - not-present page
      [    2.820188] PGD 0 P4D 0
      [    2.820305] Oops: 0000 [#1] SMP PTI
      [    2.820436] CPU: 2 PID: 89 Comm: a Not tainted 5.7.0-rc1+ #7
      [    2.820680] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190711_202441-buildvm-armv7-10.arm.fedoraproject.org-2.fc31 04/01/2014
      [    2.821150] RIP: 0010:do_coredump+0xd80/0x1060
      [    2.821385] Code: e8 95 11 ed ff 48 c7 c6 cc a7 b4 81 48 8d bd 28 ff
      ff ff 89 c2 e8 70 f1 ff ff 41 89 c2 85 c0 0f 84 72 f7 ff ff e9 b4 fe ff
      ff <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 8
      0 0f 84 9c 01 00 00 44
      [    2.822014] RSP: 0000:ffffc9000029bcb8 EFLAGS: 00010246
      [    2.822339] RAX: 0000000000000000 RBX: ffff88803f860000 RCX: 000000000000000a
      [    2.822746] RDX: 0000000000000009 RSI: 0000000000000282 RDI: 0000000000000000
      [    2.823141] RBP: ffffc9000029bde8 R08: 0000000000000000 R09: ffffc9000029bc00
      [    2.823508] R10: 0000000000000001 R11: ffff88803dec90be R12: ffffffff81c39da0
      [    2.823902] R13: ffff88803de84400 R14: 0000000000000000 R15: 0000000000000000
      [    2.824285] FS:  00007fee08183540(0000) GS:ffff88803e480000(0000) knlGS:0000000000000000
      [    2.824767] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      [    2.825111] CR2: 0000000000000020 CR3: 000000003f856005 CR4: 0000000000060ea0
      [    2.825479] Call Trace:
      [    2.825790]  get_signal+0x11e/0x720
      [    2.826087]  do_signal+0x1d/0x670
      [    2.826361]  ? force_sig_info_to_task+0xc1/0xf0
      [    2.826691]  ? force_sig_fault+0x3c/0x40
      [    2.826996]  ? do_trap+0xc9/0x100
      [    2.827179]  exit_to_usermode_loop+0x49/0x90
      [    2.827359]  prepare_exit_to_usermode+0x77/0xb0
      [    2.827559]  ? invalid_op+0xa/0x30
      [    2.827747]  ret_from_intr+0x20/0x20
      [    2.827921] RIP: 0033:0x55e2c76d2129
      [    2.828107] Code: 2d ff ff ff e8 68 ff ff ff 5d c6 05 18 2f 00 00 01
      c3 0f 1f 80 00 00 00 00 c3 0f 1f 80 00 00 00 00 e9 7b ff ff ff 55 48 89
      e5 <0f> 0b b8 00 00 00 00 5d c3 66 2e 0f 1f 84 0
      0 00 00 00 00 0f 1f 40
      [    2.828603] RSP: 002b:00007fffeba5e080 EFLAGS: 00010246
      [    2.828801] RAX: 000055e2c76d2125 RBX: 0000000000000000 RCX: 00007fee0817c718
      [    2.829034] RDX: 00007fffeba5e188 RSI: 00007fffeba5e178 RDI: 0000000000000001
      [    2.829257] RBP: 00007fffeba5e080 R08: 0000000000000000 R09: 00007fee08193c00
      [    2.829482] R10: 0000000000000009 R11: 0000000000000000 R12: 000055e2c76d2040
      [    2.829727] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
      [    2.829964] CR2: 0000000000000020
      [    2.830149] ---[ end trace ceed83d8c68a1bf1 ]---
      ```
      
      Cc: <stable@vger.kernel.org> # v4.11+
      Fixes: 64e90a8a ("Introduce STATIC_USERMODEHELPER to mediate call_usermodehelper()")
      BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=199795Reported-by: default avatarTony Vroon <chainsaw@gentoo.org>
      Reported-by: default avatarSergey Kvachonok <ravenexp@gmail.com>
      Tested-by: default avatarSergei Trofimovich <slyfox@gentoo.org>
      Signed-off-by: default avatarLuis Chamberlain <mcgrof@kernel.org>
      Link: https://lore.kernel.org/r/20200416162859.26518-1-mcgrof@kernel.orgSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      3740d93e
    • Ulf Hansson's avatar
      amba: Initialize dma_parms for amba devices · f4584884
      Ulf Hansson authored
      It's currently the amba driver's responsibility to initialize the pointer,
      dma_parms, for its corresponding struct device. The benefit with this
      approach allows us to avoid the initialization and to not waste memory for
      the struct device_dma_parameters, as this can be decided on a case by case
      basis.
      
      However, it has turned out that this approach is not very practical. Not
      only does it lead to open coding, but also to real errors. In principle
      callers of dma_set_max_seg_size() doesn't check the error code, but just
      assumes it succeeds.
      
      For these reasons, let's do the initialization from the common amba bus at
      the device registration point. This also follows the way the PCI devices
      are being managed, see pci_device_add().
      Suggested-by: default avatarChristoph Hellwig <hch@lst.de>
      Cc: Russell King <linux@armlinux.org.uk>
      Cc: <stable@vger.kernel.org>
      Tested-by: default avatarHaibo Chen <haibo.chen@nxp.com>
      Reviewed-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarUlf Hansson <ulf.hansson@linaro.org>
      Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
      Link: https://lore.kernel.org/r/20200422101013.31267-1-ulf.hansson@linaro.orgSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      f4584884
    • Ulf Hansson's avatar
      driver core: platform: Initialize dma_parms for platform devices · 9495b7e9
      Ulf Hansson authored
      It's currently the platform driver's responsibility to initialize the
      pointer, dma_parms, for its corresponding struct device. The benefit with
      this approach allows us to avoid the initialization and to not waste memory
      for the struct device_dma_parameters, as this can be decided on a case by
      case basis.
      
      However, it has turned out that this approach is not very practical.  Not
      only does it lead to open coding, but also to real errors. In principle
      callers of dma_set_max_seg_size() doesn't check the error code, but just
      assumes it succeeds.
      
      For these reasons, let's do the initialization from the common platform bus
      at the device registration point. This also follows the way the PCI devices
      are being managed, see pci_device_add().
      Suggested-by: default avatarChristoph Hellwig <hch@lst.de>
      Cc: <stable@vger.kernel.org>
      Tested-by: default avatarHaibo Chen <haibo.chen@nxp.com>
      Reviewed-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarUlf Hansson <ulf.hansson@linaro.org>
      Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
      Link: https://lore.kernel.org/r/20200422100954.31211-1-ulf.hansson@linaro.orgSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      9495b7e9
  2. 26 Apr, 2020 11 commits
    • Linus Torvalds's avatar
      Linux 5.7-rc3 · 6a8b55ed
      Linus Torvalds authored
      6a8b55ed
    • Linus Torvalds's avatar
      Merge tag '5.7-rc2-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6 · d4fb4bfb
      Linus Torvalds authored
      Pull cifs fixes from Steve French:
       "Five cifs/smb3 fixes:two for DFS reconnect failover, one lease fix for
        stable and the others to fix a missing spinlock during reconnect"
      
      * tag '5.7-rc2-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6:
        cifs: fix uninitialised lease_key in open_shroot()
        cifs: ensure correct super block for DFS reconnect
        cifs: do not share tcons with DFS
        cifs: minor update to comments around the cifs_tcp_ses_lock mutex
        cifs: protect updating server->dstaddr with a spinlock
      d4fb4bfb
    • Linus Torvalds's avatar
      Merge tag 'usb-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb · e9a61afb
      Linus Torvalds authored
      Pull USB fixes from Greg KH:
       "Here are a number of USB driver fixes for 5.7-rc3.
      
        Nothing huge, just the usual collection of:
      
         - xhci fixes
      
         - gadget driver fixes
      
         - syzkaller fuzzing fixes
      
         - new device ids and DT bindings
      
         - new quirks added for broken devices
      
        A few of the gadget driver fixes show up twice here as they were
        applied to my branch, and also by Felipe to his branch which I then
        pulled in as we got out of sync a bit.
      
        All of these have been in linux-next with no reported issues"
      
      * tag 'usb-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb: (33 commits)
        USB: sisusbvga: Change port variable from signed to unsigned
        usb-storage: Add unusual_devs entry for JMicron JMS566
        USB: hub: Revert commit bd0e6c96 ("usb: hub: try old enumeration scheme first for high speed devices")
        USB: hub: Fix handling of connect changes during sleep
        usb: typec: altmode: Fix typec_altmode_get_partner sometimes returning an invalid pointer
        xhci: Don't clear hub TT buffer on ep0 protocol stall
        xhci: prevent bus suspend if a roothub port detected a over-current condition
        xhci: Fix handling halted endpoint even if endpoint ring appears empty
        usb: raw-gadget: Fix copy_to/from_user() checks
        usb: raw-gadget: fix raw_event_queue_fetch locking
        usb: gadget: udc: atmel: Fix vbus disconnect handling
        usb: dwc3: gadget: Fix request completion check
        USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair K70 RGB RAPIDFIRE
        phy: tegra: Select USB_COMMON for usb_get_maximum_speed()
        usb: typec: tcpm: Ignore CC and vbus changes in PORT_RESET change
        usb: f_fs: Clear OS Extended descriptor counts to zero in ffs_data_reset()
        cdc-acm: introduce a cool down
        cdc-acm: close race betrween suspend() and acm_softint
        UAS: fix deadlock in error handling and PM flushing work
        UAS: no use logging any details in case of ENODEV
        ...
      e9a61afb
    • Linus Torvalds's avatar
      Merge tag 'tty-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty · c5f33785
      Linus Torvalds authored
      Pull tty/serial fixes from Greg KH:
       "Here are some tty and serial driver fixes for 5.7-rc3.
      
        The "largest" in here are a number of reverts for previous changes to
        the uartps serial driver that turned out to not be a good idea at all.
      
        The others are just small fixes found by people and tools. Included in
        here is a much-reported symbol export needed by previous changes that
        happened in 5.7-rc1. All of these have been in linux-next for a while
        with no reported issues"
      
      * tag 'tty-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:
        tty: hvc: fix buffer overflow during hvc_alloc().
        tty: rocket, avoid OOB access
        tty: serial: bcm63xx: fix missing clk_put() in bcm63xx_uart
        vt: don't hardcode the mem allocation upper bound
        tty: serial: owl: add "much needed" clk_prepare_enable()
        vt: don't use kmalloc() for the unicode screen buffer
        tty/sysrq: Export sysrq_mask(), sysrq_toggle_support()
        serial: sh-sci: Make sure status register SCxSR is read in correct sequence
        serial: sunhv: Initialize lock for non-registered console
        Revert "serial: uartps: Register own uart console and driver structures"
        Revert "serial: uartps: Move Port ID to device data structure"
        Revert "serial: uartps: Change uart ID port allocation"
        Revert "serial: uartps: Do not allow use aliases >= MAX_UART_INSTANCES"
        Revert "serial: uartps: Fix error path when alloc failed"
        Revert "serial: uartps: Use the same dynamic major number for all ports"
        Revert "serial: uartps: Fix uartps_major handling"
      c5f33785
    • Linus Torvalds's avatar
      Merge tag 'char-misc-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc · f6da8bd1
      Linus Torvalds authored
      Pull char/misc driver fixes from Greg KH:
       "Here are 4 small misc driver fixes for 5.7-rc3:
      
         - mei driver fix
      
         - interconnect driver fix
      
         - two fpga driver fixes
      
        All have been in linux-next with no reported issues"
      
      * tag 'char-misc-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc:
        interconnect: qcom: Fix uninitialized tcs_cmd::wait
        mei: me: fix irq number stored in hw struct
        fpga: dfl: pci: fix return value of cci_pci_sriov_configure
        fpga: zynq: Remove clk_get error message for probe defer
      f6da8bd1
    • Linus Torvalds's avatar
      Merge tag 'staging-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging · edf17b28
      Linus Torvalds authored
      Pull staging/IIO driver fixes from Greg KH:
       "Here are some small staging and IIO driver fixes for 5.7-rc3
      
        Lots of tiny things for reported issues in staging and IIO drivers,
        including a counter driver fix as well (the iio drivers seem to be
        tied to those). Full details of the fixes are in the shortlog.
      
        All of these have been in linux-next for a while with no reported
        issues"
      
      * tag 'staging-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging: (27 commits)
        staging: vt6656: Fix calling conditions of vnt_set_bss_mode
        staging: comedi: Fix comedi_device refcnt leak in comedi_open
        staging: vt6656: Fix pairwise key entry save.
        staging: vt6656: Fix drivers TBTT timing counter.
        staging: vt6656: Don't set RCR_MULTICAST or RCR_BROADCAST by default.
        MAINTAINERS: remove Stefan Popa's email
        iio: adc: ad7192: fix null pointer de-reference crash during probe
        iio: core: remove extra semi-colon from devm_iio_device_register() macro
        iio: adc: ti-ads8344: properly byte swap value
        iio: imu: inv_mpu6050: fix suspend/resume with runtime power
        iio: st_sensors: rely on odr mask to know if odr can be set
        iio: xilinx-xadc: Make sure not exceed maximum samplerate
        iio: xilinx-xadc: Fix sequencer configuration for aux channels in simultaneous mode
        iio: xilinx-xadc: Fix clearing interrupt when enabling trigger
        iio: xilinx-xadc: Fix ADC-B powerdown
        iio: dac: ad5770r: fix off-by-one check on maximum number of channels
        iio: imu: st_lsm6dsx: flush hw FIFO before resetting the device
        iio: core: Fix handling of 'dB'
        dt-bindings: iio: adc: stm32-adc: fix id relative path
        counter: 104-quad-8: Add lock guards - generic interface
        ...
      edf17b28
    • Linus Torvalds's avatar
      Merge tag 'driver-core-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core · a8a0e2a9
      Linus Torvalds authored
      Pull driver core fixes from Greg KH:
       "Here are some small firmware/driver core/debugfs fixes for 5.7-rc3.
      
        The debugfs change is now possible as now the last users of
        debugfs_create_u32() have been fixed up in the different trees that
        got merged into 5.7-rc1, and I don't want it creeping back in.
      
        The firmware changes did cause a regression in linux-next, so the
        final patch here reverts part of that, re-exporting the symbol to
        resolve that issue. All of these patches, with the exception of the
        final one, have been in linux-next with only that one reported issue"
      
      * tag 'driver-core-5.7-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
        firmware_loader: revert removal of the fw_fallback_config export
        debugfs: remove return value of debugfs_create_u32()
        firmware_loader: remove unused exports
        firmware: imx: fix compile-testing
      a8a0e2a9
    • Linus Torvalds's avatar
      Merge tag 's390-5.7-3' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux · 749f0461
      Linus Torvalds authored
      Pull s390 fixes from Vasily Gorbik:
      
       - Add a few notrace annotations to avoid potential crashes when
         switching ftrace tracers.
      
       - Avoid setting affinity for floating irqs in pci code.
      
       - Fix build issue found by kbuild test robot.
      
      * tag 's390-5.7-3' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
        s390/protvirt: fix compilation issue
        s390/pci: do not set affinity for floating irqs
        s390/ftrace: fix potential crashes when switching tracers
      749f0461
    • Linus Torvalds's avatar
      Merge tag 'powerpc-5.7-3' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux · 670bcd79
      Linus Torvalds authored
      Pull powerpc fixes from Michael Ellerman:
      
       - One important fix for a bug in the way we find the cache-line size
         from the device tree, which was leading to the wrong size being
         reported to userspace on some platforms.
      
       - A fix for 8xx STRICT_KERNEL_RWX which was leaving TLB entries around
         leading to a window at boot when the strict mapping wasn't enforced.
      
       - A fix to enable our KUAP (kernel user access prevention) debugging on
         PPC32.
      
       - A build fix for clang in lib/mpi.
      
      Thanks to: Chris Packham, Christophe Leroy, Nathan Chancellor, Qian Cai.
      
      * tag 'powerpc-5.7-3' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
        lib/mpi: Fix building for powerpc with clang
        powerpc/mm: Fix CONFIG_PPC_KUAP_DEBUG on PPC32
        powerpc/8xx: Fix STRICT_KERNEL_RWX startup test failure
        powerpc/setup_64: Set cache-line-size based on cache-block-size
      670bcd79
    • Linus Torvalds's avatar
      Merge tag 'devicetree-fixes-for-5.7-2' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux · 58792882
      Linus Torvalds authored
      Pull more Devicetree fixes from Rob Herring:
       "A couple of schema and kbuild fixes"
      
      * tag 'devicetree-fixes-for-5.7-2' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux:
        dt-bindings: phy: qcom-qusb2: Fix defaults
        dt-bindings: Fix erroneous 'additionalProperties'
        dt-bindings: Fix command line length limit calling dt-mk-schema
        dt-bindings: Re-enable core schemas for dtbs_check
      58792882
    • Luis Chamberlain's avatar
      firmware_loader: revert removal of the fw_fallback_config export · 5a357703
      Luis Chamberlain authored
      Christoph's patch removed two unsused exported symbols, however, one
      symbol is used by the firmware_loader itself.  If CONFIG_FW_LOADER=m so
      the firmware_loader is modular but CONFIG_FW_LOADER_USER_HELPER=y we fail
      the build at mostpost.
      
      ERROR: modpost: "fw_fallback_config" [drivers/base/firmware_loader/firmware_class.ko] undefined!
      
      This happens because the variable fw_fallback_config is built into the
      kernel if CONFIG_FW_LOADER_USER_HELPER=y always, so we need to grant
      access to the firmware loader module by exporting it.
      
      Revert only one hunk from his patch.
      
      Fixes: 73960473 ("firmware_loader: remove unused exports")
      Reported-by: default avatarRandy Dunlap <rdunlap@infradead.org>
      Signed-off-by: default avatarLuis Chamberlain <mcgrof@kernel.org>
      Link: https://lore.kernel.org/r/20200424184916.22843-1-mcgrof@kernel.orgSigned-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      5a357703
  3. 25 Apr, 2020 19 commits
  4. 24 Apr, 2020 2 commits