12 Aug, 2019

2 commits


11 Aug, 2019

9 commits

  • Pull RISC-V updates from Paul Walmsley:
    "A few minor RISC-V updates for v5.3-rc4:

    - Remove __udivdi3() from the 32-bit Linux port, converting the only
    upstream user to use do_div(), per Linux policy

    - Convert the RISC-V standard clocksource away from per-cpu data
    structures, since only one is used by Linux, even on a multi-CPU
    system

    - A set of DT binding updates that remove an obsolete text binding in
    favor of a YAML binding, fix a bogus compatible string in the
    schema (thus fixing a "make dtbs_check" warning), and clarifies the
    future values expected in one of the RISC-V CPU properties"

    * tag 'riscv/for-v5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux:
    dt-bindings: riscv: fix the schema compatible string for the HiFive Unleashed board
    dt-bindings: riscv: remove obsolete cpus.txt
    RISC-V: Remove udivdi3
    riscv: delay: use do_div() instead of __udivdi3()
    dt-bindings: Update the riscv,isa string description
    RISC-V: Remove per cpu clocksource

    Linus Torvalds
     
  • Pull objtool warning fix from Thomas Gleixner:
    "The recent objtool fixes/enhancements unearthed a unbalanced CLAC in
    the i915 driver.

    Chris asked me to pick the fix up and route it through"

    * 'core-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
    drm/i915: Remove redundant user_access_end() from __copy_from_user() error path

    Linus Torvalds
     
  • Pull char/misc driver fixes Greg KH:
    "Here are some small char/misc driver fixes for 5.3-rc4.

    Two of these are for the habanalabs driver for issues found when
    running on a big-endian system (are they still alive?) The others are
    tiny fixes reported by people, and a MAINTAINERS update about the
    location of the fpga development tree.

    All of these have been in linux-next for a while with no reported
    issues"

    * tag 'char-misc-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc:
    coresight: Fix DEBUG_LOCKS_WARN_ON for uninitialized attribute
    MAINTAINERS: Move linux-fpga tree to new location
    nvmem: Use the same permissions for eeprom as for nvmem
    habanalabs: fix host memory polling in BE architecture
    habanalabs: fix F/W download in BE architecture

    Linus Torvalds
     
  • Pull driver core fixes from Greg KH:
    "Here are two small fixes for some driver core issues that have been
    reported. There is also a kernfs "fix" here, which was then reverted
    because it was found to cause problems in linux-next.

    The driver core fixes both resolve reported issues, one with gpioint
    stuff that showed up in 5.3-rc1, and the other finally (and hopefully)
    resolves a very long standing race when removing glue directories.
    It's nice to get that issue finally resolved and the developers
    involved should be applauded for the persistence it took to get this
    patch finally accepted.

    All of these have been in linux-next for a while with no reported
    issues. Well, the one reported issue, hence the revert :)"

    * tag 'driver-core-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
    Revert "kernfs: fix memleak in kernel_ops_readdir()"
    kernfs: fix memleak in kernel_ops_readdir()
    driver core: Fix use-after-free and double free on glue directory
    driver core: platform: return -ENXIO for missing GpioInt

    Linus Torvalds
     
  • Pull tty fix from Greg KH:
    "Here is a single tty kgdb fix for 5.3-rc4.

    It fixes an annoying log message that has caused kdb to become
    useless. It's another fallout from commit ddde3c18b700 ("vt: More
    locking checks") which tries to enforce locking checks more strictly
    in the tty layer, unfortunatly when kdb is stopped, there's no need
    for locks :)

    This patch has been linux-next for a while with no reported issues"

    * tag 'tty-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:
    kgdboc: disable the console lock when in kgdb

    Linus Torvalds
     
  • Pull staging / IIO driver fixes from Greg KH:
    "Here are some small staging and IIO driver fixes for 5.3-rc4.

    Nothing major, just resolutions for a number of small reported issues,
    full details in the shortlog.

    All have been in linux-next for a while with no reported issues"

    * tag 'staging-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging:
    iio: adc: gyroadc: fix uninitialized return code
    docs: generic-counter.rst: fix broken references for ABI file
    staging: android: ion: Bail out upon SIGKILL when allocating memory.
    Staging: fbtft: Fix GPIO handling
    staging: unisys: visornic: Update the description of 'poll_for_irq()'
    staging: wilc1000: flush the workqueue before deinit the host
    staging: gasket: apex: fix copy-paste typo
    Staging: fbtft: Fix reset assertion when using gpio descriptor
    Staging: fbtft: Fix probing of gpio descriptor
    iio: imu: mpu6050: add missing available scan masks
    iio: cros_ec_accel_legacy: Fix incorrect channel setting
    IIO: Ingenic JZ47xx: Set clock divider on probe
    iio: adc: max9611: Fix misuse of GENMASK macro

    Linus Torvalds
     
  • Pull USB fixes from Greg KH:
    "Here are some small USB fixes for 5.3-rc4.

    The "biggest" one here is moving code from one file to another in
    order to fix a long-standing race condition with the creation of sysfs
    files for USB devices. Turns out that there are now userspace tools
    out there that are hitting this long-known bug, so it's time to fix
    them. Thankfully the tool-maker in this case fixed the issue :)

    The other patches in here are all fixes for reported issues. Now that
    syzbot knows how to fuzz USB drivers better, and is starting to now
    fuzz the userspace facing side of them at the same time, there will be
    more and more small fixes like these coming, which is a good thing.

    All of these have been in linux-next with no reported issues"

    * tag 'usb-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb:
    usb: setup authorized_default attributes using usb_bus_notify
    usb: iowarrior: fix deadlock on disconnect
    Revert "USB: rio500: simplify locking"
    usb: usbfs: fix double-free of usb memory upon submiturb error
    usb: yurex: Fix use-after-free in yurex_delete
    usb: typec: tcpm: Ignore unsupported/unknown alternate mode requests
    xhci: Fix NULL pointer dereference at endpoint zero reset.
    usb: host: xhci-rcar: Fix timeout in xhci_suspend()
    usb: typec: ucsi: ccg: Fix uninitilized symbol error
    usb: typec: tcpm: remove tcpm dir if no children
    usb: typec: tcpm: free log buf memory when remove debug file
    usb: typec: tcpm: Add NULL check before dereferencing config

    Linus Torvalds
     
  • Pull pin control fixes from Linus Walleij:

    - Delay acquisition of regmaps in the Aspeed G5 driver.

    - Make a symbol static to reduce compiler noise.

    * tag 'pinctrl-v5.3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl:
    pinctrl: aspeed: Make aspeed_pinmux_ips static
    pinctrl: aspeed-g5: Delay acquisition of regmaps

    Linus Torvalds
     
  • …kernel/git/gustavoars/linux

    Pull fall-through fixes from Gustavo A. R. Silva:
    "Mark more switch cases where we are expecting to fall through, fixing
    fall-through warnings in arm, sparc64, mips, i386 and s390"

    * tag 'Wimplicit-fallthrough-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux:
    ARM: ep93xx: Mark expected switch fall-through
    scsi: fas216: Mark expected switch fall-throughs
    pcmcia: db1xxx_ss: Mark expected switch fall-throughs
    video: fbdev: omapfb_main: Mark expected switch fall-throughs
    watchdog: riowd: Mark expected switch fall-through
    s390/net: Mark expected switch fall-throughs
    crypto: ux500/crypt: Mark expected switch fall-throughs
    watchdog: wdt977: Mark expected switch fall-through
    watchdog: scx200_wdt: Mark expected switch fall-through
    watchdog: Mark expected switch fall-throughs
    ARM: signal: Mark expected switch fall-through
    mfd: omap-usb-host: Mark expected switch fall-throughs
    mfd: db8500-prcmu: Mark expected switch fall-throughs
    ARM: OMAP: dma: Mark expected switch fall-throughs
    ARM: alignment: Mark expected switch fall-throughs
    ARM: tegra: Mark expected switch fall-through
    ARM/hw_breakpoint: Mark expected switch fall-throughs

    Linus Torvalds
     

10 Aug, 2019

20 commits

  • Mark switch cases where we are expecting to fall through.

    Fix the following warnings (Building: rpc_defconfig arm):

    drivers/scsi/arm/fas216.c: In function ‘fas216_disconnect_intr’:
    drivers/scsi/arm/fas216.c:913:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
    if (fas216_get_last_msg(info, info->scsi.msgin_fifo) == ABORT) {
    ^
    drivers/scsi/arm/fas216.c:919:2: note: here
    default: /* huh? */
    ^~~~~~~
    drivers/scsi/arm/fas216.c: In function ‘fas216_kick’:
    drivers/scsi/arm/fas216.c:1959:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    fas216_allocate_tag(info, SCpnt);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    drivers/scsi/arm/fas216.c:1960:2: note: here
    case TYPE_OTHER:
    ^~~~
    drivers/scsi/arm/fas216.c: In function ‘fas216_busservice_intr’:
    drivers/scsi/arm/fas216.c:1413:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    fas216_stoptransfer(info);
    ^~~~~~~~~~~~~~~~~~~~~~~~~
    drivers/scsi/arm/fas216.c:1414:2: note: here
    case STATE(STAT_STATUS, PHASE_SELSTEPS):/* Sel w/ steps -> Status */
    ^~~~
    drivers/scsi/arm/fas216.c:1424:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    fas216_stoptransfer(info);
    ^~~~~~~~~~~~~~~~~~~~~~~~~
    drivers/scsi/arm/fas216.c:1425:2: note: here
    case STATE(STAT_MESGIN, PHASE_COMMAND): /* Command -> Message In */
    ^~~~
    drivers/scsi/arm/fas216.c: In function ‘fas216_funcdone_intr’:
    drivers/scsi/arm/fas216.c:1573:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
    if ((stat & STAT_BUSMASK) == STAT_MESGIN) {
    ^
    drivers/scsi/arm/fas216.c:1579:2: note: here
    default:
    ^~~~~~~
    drivers/scsi/arm/fas216.c: In function ‘fas216_handlesync’:
    drivers/scsi/arm/fas216.c:605:20: warning: this statement may fall through [-Wimplicit-fallthrough=]
    info->scsi.phase = PHASE_MSGOUT_EXPECT;
    ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
    drivers/scsi/arm/fas216.c:607:2: note: here
    case async:
    ^~~~

    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Mark switch cases where we are expecting to fall through.

    This patch fixes the following warnings (Building: db1xxx_defconfig mips):

    drivers/pcmcia/db1xxx_ss.c:257:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    drivers/pcmcia/db1xxx_ss.c:269:3: warning: this statement may fall through [-Wimplicit-fallthrough=]

    Reviewed-by: Kees Cook
    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Mark switch cases where we are expecting to fall through.

    This patch fixes the following warning (Building: omap1_defconfig arm):

    drivers/watchdog/wdt285.c:170:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    drivers/watchdog/ar7_wdt.c:237:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    drivers/video/fbdev/omap/omapfb_main.c:449:23: warning: this statement may fall through [-Wimplicit-fallthrough=]
    drivers/video/fbdev/omap/omapfb_main.c:1549:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
    drivers/video/fbdev/omap/omapfb_main.c:1547:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    drivers/video/fbdev/omap/omapfb_main.c:1545:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    drivers/video/fbdev/omap/omapfb_main.c:1543:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    drivers/video/fbdev/omap/omapfb_main.c:1540:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
    drivers/video/fbdev/omap/omapfb_main.c:1538:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    drivers/video/fbdev/omap/omapfb_main.c:1535:3: warning: this statement may fall through [-Wimplicit-fallthrough=]

    Reviewed-by: Kees Cook
    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Mark switch cases where we are expecting to fall through.

    This patch fixes the following warnings (Building: sparc64):

    drivers/watchdog/riowd.c: In function ‘riowd_ioctl’:
    drivers/watchdog/riowd.c:136:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    riowd_writereg(p, riowd_timeout, WDTO_INDEX);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    drivers/watchdog/riowd.c:139:2: note: here
    case WDIOC_GETTIMEOUT:
    ^~~~

    Reviewed-by: Kees Cook
    Reviewed-by: Guenter Roeck
    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Mark switch cases where we are expecting to fall through.

    This patch fixes the following warnings (Building: s390):

    drivers/s390/net/ctcm_fsms.c: In function ‘ctcmpc_chx_attnbusy’:
    drivers/s390/net/ctcm_fsms.c:1703:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
    if (grp->changed_side == 1) {
    ^
    drivers/s390/net/ctcm_fsms.c:1707:2: note: here
    case MPCG_STATE_XID0IOWAIX:
    ^~~~

    drivers/s390/net/ctcm_mpc.c: In function ‘ctc_mpc_alloc_channel’:
    drivers/s390/net/ctcm_mpc.c:358:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
    if (callback)
    ^
    drivers/s390/net/ctcm_mpc.c:360:2: note: here
    case MPCG_STATE_XID0IOWAIT:
    ^~~~

    drivers/s390/net/ctcm_mpc.c: In function ‘mpc_action_timeout’:
    drivers/s390/net/ctcm_mpc.c:1469:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
    if ((fsm_getstate(rch->fsm) == CH_XID0_PENDING) &&
    ^
    drivers/s390/net/ctcm_mpc.c:1472:2: note: here
    default:
    ^~~~~~~
    drivers/s390/net/ctcm_mpc.c: In function ‘mpc_send_qllc_discontact’:
    drivers/s390/net/ctcm_mpc.c:2087:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
    if (grp->estconnfunc) {
    ^
    drivers/s390/net/ctcm_mpc.c:2092:2: note: here
    case MPCG_STATE_FLOWC:
    ^~~~

    drivers/s390/net/qeth_l2_main.c: In function ‘qeth_l2_process_inbound_buffer’:
    drivers/s390/net/qeth_l2_main.c:328:7: warning: this statement may fall through [-Wimplicit-fallthrough=]
    if (IS_OSN(card)) {
    ^
    drivers/s390/net/qeth_l2_main.c:337:3: note: here
    default:
    ^~~~~~~

    Reviewed-by: Kees Cook
    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Mark switch cases where we are expecting to fall through.

    This patch fixes the following warning (Building: arm):

    drivers/crypto/ux500/cryp/cryp.c: In function ‘cryp_save_device_context’:
    drivers/crypto/ux500/cryp/cryp.c:316:16: warning: this statement may fall through [-Wimplicit-fallthrough=]
    ctx->key_4_r = readl_relaxed(&src_reg->key_4_r);
    drivers/crypto/ux500/cryp/cryp.c:318:2: note: here
    case CRYP_KEY_SIZE_192:
    ^~~~
    drivers/crypto/ux500/cryp/cryp.c:320:16: warning: this statement may fall through [-Wimplicit-fallthrough=]
    ctx->key_3_r = readl_relaxed(&src_reg->key_3_r);
    drivers/crypto/ux500/cryp/cryp.c:322:2: note: here
    case CRYP_KEY_SIZE_128:
    ^~~~
    drivers/crypto/ux500/cryp/cryp.c:324:16: warning: this statement may fall through [-Wimplicit-fallthrough=]
    ctx->key_2_r = readl_relaxed(&src_reg->key_2_r);
    drivers/crypto/ux500/cryp/cryp.c:326:2: note: here
    default:
    ^~~~~~~
    In file included from ./include/linux/io.h:13:0,
    from drivers/crypto/ux500/cryp/cryp_p.h:14,
    from drivers/crypto/ux500/cryp/cryp.c:15:
    drivers/crypto/ux500/cryp/cryp.c: In function ‘cryp_restore_device_context’:
    ./arch/arm/include/asm/io.h:92:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
    #define __raw_writel __raw_writel
    ^
    ./arch/arm/include/asm/io.h:299:29: note: in expansion of macro ‘__raw_writel’
    #define writel_relaxed(v,c) __raw_writel((__force u32) cpu_to_le32(v),c)
    ^~~~~~~~~~~~
    drivers/crypto/ux500/cryp/cryp.c:363:3: note: in expansion of macro ‘writel_relaxed’
    writel_relaxed(ctx->key_4_r, ®->key_4_r);
    ^~~~~~~~~~~~~~
    drivers/crypto/ux500/cryp/cryp.c:365:2: note: here
    case CRYP_KEY_SIZE_192:
    ^~~~
    In file included from ./include/linux/io.h:13:0,
    from drivers/crypto/ux500/cryp/cryp_p.h:14,
    from drivers/crypto/ux500/cryp/cryp.c:15:
    ./arch/arm/include/asm/io.h:92:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
    #define __raw_writel __raw_writel
    ^
    ./arch/arm/include/asm/io.h:299:29: note: in expansion of macro ‘__raw_writel’
    #define writel_relaxed(v,c) __raw_writel((__force u32) cpu_to_le32(v),c)
    ^~~~~~~~~~~~
    drivers/crypto/ux500/cryp/cryp.c:367:3: note: in expansion of macro ‘writel_relaxed’
    writel_relaxed(ctx->key_3_r, ®->key_3_r);
    ^~~~~~~~~~~~~~
    drivers/crypto/ux500/cryp/cryp.c:369:2: note: here
    case CRYP_KEY_SIZE_128:
    ^~~~
    In file included from ./include/linux/io.h:13:0,
    from drivers/crypto/ux500/cryp/cryp_p.h:14,
    from drivers/crypto/ux500/cryp/cryp.c:15:
    ./arch/arm/include/asm/io.h:92:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
    #define __raw_writel __raw_writel
    ^
    ./arch/arm/include/asm/io.h:299:29: note: in expansion of macro ‘__raw_writel’
    #define writel_relaxed(v,c) __raw_writel((__force u32) cpu_to_le32(v),c)
    ^~~~~~~~~~~~
    drivers/crypto/ux500/cryp/cryp.c:371:3: note: in expansion of macro ‘writel_relaxed’
    writel_relaxed(ctx->key_2_r, ®->key_2_r);
    ^~~~~~~~~~~~~~
    drivers/crypto/ux500/cryp/cryp.c:373:2: note: here
    default:
    ^~~~~~~

    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Mark switch cases where we are expecting to fall through.

    This patch fixes the following warning (Building: arm):

    drivers/watchdog/wdt977.c: In function ‘wdt977_ioctl’:
    LD [M] drivers/media/platform/vicodec/vicodec.o
    drivers/watchdog/wdt977.c:400:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    wdt977_keepalive();
    ^~~~~~~~~~~~~~~~~~
    drivers/watchdog/wdt977.c:403:2: note: here
    case WDIOC_GETTIMEOUT:
    ^~~~

    Reviewed-by: Kees Cook
    Reviewed-by: Guenter Roeck
    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Mark switch cases where we are expecting to fall through.

    This patch fixes the following warning (Building: i386):

    drivers/watchdog/scx200_wdt.c: In function ‘scx200_wdt_ioctl’:
    drivers/watchdog/scx200_wdt.c:188:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
    scx200_wdt_ping();
    ^~~~~~~~~~~~~~~~~
    drivers/watchdog/scx200_wdt.c:189:2: note: here
    case WDIOC_GETTIMEOUT:
    ^~~~

    Reviewed-by: Kees Cook
    Reviewed-by: Guenter Roeck
    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Mark switch cases where we are expecting to fall through.

    This patch fixes the following warnings:

    drivers/watchdog/ar7_wdt.c: warning: this statement may fall
    through [-Wimplicit-fallthrough=]: => 237:3
    drivers/watchdog/pcwd.c: warning: this statement may fall
    through [-Wimplicit-fallthrough=]: => 653:3
    drivers/watchdog/sb_wdog.c: warning: this statement may fall
    through [-Wimplicit-fallthrough=]: => 204:3
    drivers/watchdog/wdt.c: warning: this statement may fall
    through [-Wimplicit-fallthrough=]: => 391:3

    Reported-by: Geert Uytterhoeven
    Reviewed-by: Kees Cook
    Reviewed-by: Guenter Roeck
    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Mark switch cases where we are expecting to fall through.

    This patch fixes the following warnings:

    drivers/mfd/omap-usb-host.c: In function 'usbhs_runtime_resume':
    drivers/mfd/omap-usb-host.c:303:7: warning: this statement may fall through [-Wimplicit-fallthrough=]
    if (!IS_ERR(omap->hsic480m_clk[i])) {
    ^
    drivers/mfd/omap-usb-host.c:313:3: note: here
    case OMAP_EHCI_PORT_MODE_TLL:
    ^~~~
    drivers/mfd/omap-usb-host.c: In function 'usbhs_runtime_suspend':
    drivers/mfd/omap-usb-host.c:345:7: warning: this statement may fall through [-Wimplicit-fallthrough=]
    if (!IS_ERR(omap->hsic480m_clk[i]))
    ^
    drivers/mfd/omap-usb-host.c:349:3: note: here
    case OMAP_EHCI_PORT_MODE_TLL:
    ^~~~

    Reported-by: Stephen Rothwell
    Reviewed-by: Kees Cook
    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Mark switch cases where we are expecting to fall through.

    This patch fixes the following warnings:

    drivers/mfd/db8500-prcmu.c: In function 'dsiclk_rate':
    drivers/mfd/db8500-prcmu.c:1592:7: warning: this statement may fall through [-Wimplicit-fallthrough=]
    div *= 2;
    ~~~~^~~~
    drivers/mfd/db8500-prcmu.c:1593:2: note: here
    case PRCM_DSI_PLLOUT_SEL_PHI_2:
    ^~~~
    drivers/mfd/db8500-prcmu.c:1594:7: warning: this statement may fall through [-Wimplicit-fallthrough=]
    div *= 2;
    ~~~~^~~~
    drivers/mfd/db8500-prcmu.c:1595:2: note: here
    case PRCM_DSI_PLLOUT_SEL_PHI:
    ^~~~

    Reported-by: Stephen Rothwell
    Reviewed-by: Kees Cook
    Reviewed-by: Linus Walleij
    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     
  • Pull input updates from Dmitry Torokhov:

    - newer systems with Elan touchpads will be switched over to SMBus

    - HP Spectre X360 will be using SMbus/RMI4

    - checks for invalid USB descriptors in kbtab and iforce

    - build fixes for applespi driver (misconfigs)

    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
    Input: iforce - add sanity checks
    Input: applespi - use struct_size() helper
    Input: kbtab - sanity check for endpoint type
    Input: usbtouchscreen - initialize PM mutex before using it
    Input: applespi - add dependency on LEDS_CLASS
    Input: synaptics - enable RMI mode for HP Spectre X360
    Input: elantech - annotate fall-through case in elantech_use_host_notify()
    Input: elantech - enable SMBus on new (2018+) systems
    Input: applespi - fix trivial typo in struct description
    Input: applespi - select CRC16 module
    Input: applespi - fix warnings detected by sparse

    Linus Torvalds
     
  • Objtool reports:

    drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o: warning: objtool: .altinstr_replacement+0x36: redundant UACCESS disable

    __copy_from_user() already does both STAC and CLAC, so the
    user_access_end() in its error path adds an extra unnecessary CLAC.

    Fixes: 0b2c8f8b6b0c ("i915: fix missing user_access_end() in page fault exception case")
    Reported-by: Thomas Gleixner
    Reported-by: Sedat Dilek
    Signed-off-by: Josh Poimboeuf
    Signed-off-by: Thomas Gleixner
    Tested-by: Nick Desaulniers
    Tested-by: Sedat Dilek
    Acked-by: Peter Zijlstra (Intel)
    Acked-by: Chris Wilson
    Link: https://github.com/ClangBuiltLinux/linux/issues/617
    Link: https://lkml.kernel.org/r/51a4155c5bc2ca847a9cbe85c1c11918bb193141.1564086017.git.jpoimboe@redhat.com

    Josh Poimboeuf
     
  • Pull drm fixes from Dave Airlie:
    "Usual fixes roundup. Nothing too crazy or serious, one non-released
    ioctl is removed in the amdkfd driver.

    core:
    - mode parser strncpy fix

    i915:
    - GLK DSI escape clock setting
    - HDCP memleak fix

    tegra:
    - one gpiod/of regression fix

    amdgpu:
    - fix VCN to handle the latest navi10 firmware
    - fix for fan control on navi10
    - properly handle SMU metrics table on navi10
    - fix a resume regression on Stoney
    - kfd revert a GWS ioctl

    vmwgfx:
    - memory leak fix

    rockchip:
    - suspend fix"

    * tag 'drm-fixes-2019-08-09' of git://anongit.freedesktop.org/drm/drm:
    drm/vmwgfx: fix memory leak when too many retries have occurred
    Revert "drm/amdkfd: New IOCTL to allocate queue GWS"
    Revert "drm/amdgpu: fix transform feedback GDS hang on gfx10 (v2)"
    drm/amdgpu: pin the csb buffer on hw init for gfx v8
    drm/rockchip: Suspend DP late
    drm/i915: Fix wrong escape clock divisor init for GLK
    drm/i915: fix possible memory leak in intel_hdcp_auth_downstream()
    drm/modes: Fix unterminated strncpy
    drm/amd/powerplay: correct navi10 vcn powergate
    drm/amd/powerplay: honor hw limit on fetching metrics data for navi10
    drm/amd/powerplay: Allow changing of fan_control in smu_v11_0
    drm/amd/amdgpu/vcn_v2_0: Move VCN 2.0 specific dec ring test to vcn_v2_0
    drm/amd/amdgpu/vcn_v2_0: Mark RB commands as KMD commands
    drm/tegra: Fix gpiod_get_from_of_node() regression

    Linus Torvalds
     
  • Pull block fixes from Jens Axboe:

    - Revert of a bcache patch that caused an oops for some (Coly)

    - ata rb532 unused warning fix (Gustavo)

    - AoE kernel crash fix (He)

    - Error handling fixup for blkdev_get() (Jan)

    - libata read/write translation and SFF PIO fix (me)

    - Use after free and error handling fix for O_DIRECT fragments. There's
    still a nowait + sync oddity in there, we'll nail that start next
    week. If all else fails, I'll queue a revert of the NOWAIT change.
    (me)

    - Loop GFP_KERNEL -> GFP_NOIO deadlock fix (Mikulas)

    - Two BFQ regression fixes that caused crashes (Paolo)

    * tag 'for-linus-20190809' of git://git.kernel.dk/linux-block:
    bcache: Revert "bcache: use sysfs_match_string() instead of __sysfs_match_string()"
    loop: set PF_MEMALLOC_NOIO for the worker thread
    bdev: Fixup error handling in blkdev_get()
    block, bfq: handle NULL return value by bfq_init_rq()
    block, bfq: move update of waker and woken list to queue freeing
    block, bfq: reset last_completed_rq_bfqq if the pointed queue is freed
    block: aoe: Fix kernel crash due to atomic sleep when exiting
    libata: add SG safety checks in SFF pio transfers
    libata: have ata_scsi_rw_xlat() fail invalid passthrough requests
    block: fix O_DIRECT error handling for bio fragments
    ata: rb532_cf: Fix unused variable warning in rb532_pata_driver_probe

    Linus Torvalds
     
  • Pull MMC fixes from Ulf Hansson:

    - cavium: Fix DMA support

    - sdhci-sprd: Fix soft reset when runtime resuming"

    * tag 'mmc-v5.3-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc:
    mmc: cavium: Add the missing dma unmap when the dma has finished.
    mmc: cavium: Set the correct dma max segment size for mmc_host
    mmc: sdhci-sprd: Fix the incorrect soft reset operation when runtime resuming

    Linus Torvalds
     
  • …erry.reding/linux-pwm

    Pull pwm fix from Thierry Reding:
    "A single fix for a backlight brightness regression introduced in
    this merge window"

    * tag 'pwm/for-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm:
    pwm: Fallback to the static lookup-list when acpi_pwm_get fails

    Linus Torvalds
     
  • Pull media fix from Mauro Carvalho Chehab:
    "A fix at the vivid CEC support"

    * tag 'media/v5.3-3' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media:
    media: vivid: fix missing cec adapter name

    Linus Torvalds
     
  • Pull power management fix from Rafael Wysocki:
    "Revert a recent PCI power management change that caused problems to
    occur on multiple systems (Mika Westerberg)"

    * tag 'pm-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
    Revert "PCI: Add missing link delays required by the PCIe spec"

    Linus Torvalds
     
  • Pull crypto fixes from Herbert Xu:
    "Fix a number of bugs in the ccp driver"

    * 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6:
    crypto: ccp - Ignore tag length when decrypting GCM ciphertext
    crypto: ccp - Add support for valid authsize values less than 16
    crypto: ccp - Fix oops by properly managing allocated structures

    Linus Torvalds
     

09 Aug, 2019

5 commits

  • …nux-fpga into char-misc-next

    Moritz writes:

    FPGA Manager changes for 5.4-rc1

    Here is the first set of changes for the 5.4-rc1 merge window.

    They're all more or less cleanup patches:

    - Carlos' patch addresses a checkpatch warning
    - My first patch changes the return type of a function to align it with
    the fact that nothing checks the return value and it uncoditionally
    returned 0 anyways
    - My second patch somehow fell through the cracks before and cleans up
    the FPGA bridge bindings by consolidating them instead of repeating
    the same paragraph over and over again.

    All of these patches have been in the last few linux-next releases
    without issues.

    Signed-off-by: Moritz Fischer <mdf@kernel.org>

    * tag 'fpga-for-5.4' of git://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux-fpga:
    dt-bindings: fpga: Consolidate bridge properties
    fpga: altera-pr-ip: Make alt_pr_unregister function void
    fpga: altera-cvp: Fix function definition argument

    Greg Kroah-Hartman
     
  • This reverts commit 89e0341af082dbc170019f908846f4a424efc86b.

    In drivers/md/bcache/sysfs.c:bch_snprint_string_list(), NULL pointer at
    the end of list is necessary. Remove the NULL from last element of each
    lists will cause the following panic,

    [ 4340.455652] bcache: register_cache() registered cache device nvme0n1
    [ 4340.464603] bcache: register_bdev() registered backing device sdk
    [ 4421.587335] bcache: bch_cached_dev_run() cached dev sdk is running already
    [ 4421.587348] bcache: bch_cached_dev_attach() Caching sdk as bcache0 on set 354e1d46-d99f-4d8b-870b-078b80dc88a6
    [ 5139.247950] general protection fault: 0000 [#1] SMP NOPTI
    [ 5139.247970] CPU: 9 PID: 5896 Comm: cat Not tainted 4.12.14-95.29-default #1 SLE12-SP4
    [ 5139.247988] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 04/18/2019
    [ 5139.248006] task: ffff888fb25c0b00 task.stack: ffff9bbacc704000
    [ 5139.248021] RIP: 0010:string+0x21/0x70
    [ 5139.248030] RSP: 0018:ffff9bbacc707bf0 EFLAGS: 00010286
    [ 5139.248043] RAX: ffffffffa7e432e3 RBX: ffff8881c20da02a RCX: ffff0a00ffffff04
    [ 5139.248058] RDX: 3f00656863616362 RSI: ffff8881c20db000 RDI: ffffffffffffffff
    [ 5139.248075] RBP: ffff8881c20db000 R08: 0000000000000000 R09: ffff8881c20da02a
    [ 5139.248090] R10: 0000000000000004 R11: 0000000000000000 R12: ffff9bbacc707c48
    [ 5139.248104] R13: 0000000000000fd6 R14: ffffffffc0665855 R15: ffffffffc0665855
    [ 5139.248119] FS: 00007faf253b8700(0000) GS:ffff88903f840000(0000) knlGS:0000000000000000
    [ 5139.248137] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [ 5139.248149] CR2: 00007faf25395008 CR3: 0000000f72150006 CR4: 00000000007606e0
    [ 5139.248164] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [ 5139.248179] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    [ 5139.248193] PKRU: 55555554
    [ 5139.248200] Call Trace:
    [ 5139.248210] vsnprintf+0x1fb/0x510
    [ 5139.248221] snprintf+0x39/0x40
    [ 5139.248238] bch_snprint_string_list.constprop.15+0x5b/0x90 [bcache]
    [ 5139.248256] __bch_cached_dev_show+0x44d/0x5f0 [bcache]
    [ 5139.248270] ? __alloc_pages_nodemask+0xb2/0x210
    [ 5139.248284] bch_cached_dev_show+0x2c/0x50 [bcache]
    [ 5139.248297] sysfs_kf_seq_show+0xbb/0x190
    [ 5139.248308] seq_read+0xfc/0x3c0
    [ 5139.248317] __vfs_read+0x26/0x140
    [ 5139.248327] vfs_read+0x87/0x130
    [ 5139.248336] SyS_read+0x42/0x90
    [ 5139.248346] do_syscall_64+0x74/0x160
    [ 5139.248358] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
    [ 5139.248370] RIP: 0033:0x7faf24eea370
    [ 5139.248379] RSP: 002b:00007fff82d03f38 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
    [ 5139.248395] RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007faf24eea370
    [ 5139.248411] RDX: 0000000000020000 RSI: 00007faf25396000 RDI: 0000000000000003
    [ 5139.248426] RBP: 00007faf25396000 R08: 00000000ffffffff R09: 0000000000000000
    [ 5139.248441] R10: 000000007c9d4d41 R11: 0000000000000246 R12: 00007faf25396000
    [ 5139.248456] R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000fff
    [ 5139.248892] Code: ff ff ff 0f 1f 80 00 00 00 00 49 89 f9 48 89 cf 48 c7 c0 e3 32 e4 a7 48 c1 ff 30 48 81 fa ff 0f 00 00 48 0f 46 d0 48 85 ff 74 45 0f b6 02 48 8d 42 01 45 84 c0 74 38 48 01 fa 4c 89 cf eb 0e

    The simplest way to fix is to revert commit 89e0341af082 ("bcache: use
    sysfs_match_string() instead of __sysfs_match_string()").

    This bug was introduced in Linux v5.2, so this fix only applies to
    Linux v5.2 is enough for stable tree maintainer.

    Fixes: 89e0341af082 ("bcache: use sysfs_match_string() instead of __sysfs_match_string()")
    Cc: stable@vger.kernel.org
    Cc: Alexandru Ardelean
    Reported-by: Peifeng Lin
    Acked-by: Alexandru Ardelean
    Signed-off-by: Coly Li
    Signed-off-by: Jens Axboe

    Coly Li
     
  • drm/i915 fixes for v5.3-rc4:
    - Fix GLK DSI escape clock setting
    - Fix a memleak on HDCP revoked Ksv error path

    Signed-off-by: Dave Airlie
    From: Jani Nikula
    Link: https://patchwork.freedesktop.org/patch/msgid/87pnlghz79.fsf@intel.com

    Dave Airlie
     
  • drm-misc-fixes for v5.3-rc4:
    - Suspend fix for rockchip
    - Fix unterminated strncpy cmdline mode parser

    Signed-off-by: Dave Airlie

    From: Maarten Lankhorst
    Link: https://patchwork.freedesktop.org/patch/msgid/ace294a6-6bb2-d9b1-695d-3260e1d60831@linux.intel.com

    Dave Airlie
     
  • A deadlock with this stacktrace was observed.

    The loop thread does a GFP_KERNEL allocation, it calls into dm-bufio
    shrinker and the shrinker depends on I/O completion in the dm-bufio
    subsystem.

    In order to fix the deadlock (and other similar ones), we set the flag
    PF_MEMALLOC_NOIO at loop thread entry.

    PID: 474 TASK: ffff8813e11f4600 CPU: 10 COMMAND: "kswapd0"
    #0 [ffff8813dedfb938] __schedule at ffffffff8173f405
    #1 [ffff8813dedfb990] schedule at ffffffff8173fa27
    #2 [ffff8813dedfb9b0] schedule_timeout at ffffffff81742fec
    #3 [ffff8813dedfba60] io_schedule_timeout at ffffffff8173f186
    #4 [ffff8813dedfbaa0] bit_wait_io at ffffffff8174034f
    #5 [ffff8813dedfbac0] __wait_on_bit at ffffffff8173fec8
    #6 [ffff8813dedfbb10] out_of_line_wait_on_bit at ffffffff8173ff81
    #7 [ffff8813dedfbb90] __make_buffer_clean at ffffffffa038736f [dm_bufio]
    #8 [ffff8813dedfbbb0] __try_evict_buffer at ffffffffa0387bb8 [dm_bufio]
    #9 [ffff8813dedfbbd0] dm_bufio_shrink_scan at ffffffffa0387cc3 [dm_bufio]
    #10 [ffff8813dedfbc40] shrink_slab at ffffffff811a87ce
    #11 [ffff8813dedfbd30] shrink_zone at ffffffff811ad778
    #12 [ffff8813dedfbdc0] kswapd at ffffffff811ae92f
    #13 [ffff8813dedfbec0] kthread at ffffffff810a8428
    #14 [ffff8813dedfbf50] ret_from_fork at ffffffff81745242

    PID: 14127 TASK: ffff881455749c00 CPU: 11 COMMAND: "loop1"
    #0 [ffff88272f5af228] __schedule at ffffffff8173f405
    #1 [ffff88272f5af280] schedule at ffffffff8173fa27
    #2 [ffff88272f5af2a0] schedule_preempt_disabled at ffffffff8173fd5e
    #3 [ffff88272f5af2b0] __mutex_lock_slowpath at ffffffff81741fb5
    #4 [ffff88272f5af330] mutex_lock at ffffffff81742133
    #5 [ffff88272f5af350] dm_bufio_shrink_count at ffffffffa03865f9 [dm_bufio]
    #6 [ffff88272f5af380] shrink_slab at ffffffff811a86bd
    #7 [ffff88272f5af470] shrink_zone at ffffffff811ad778
    #8 [ffff88272f5af500] do_try_to_free_pages at ffffffff811adb34
    #9 [ffff88272f5af590] try_to_free_pages at ffffffff811adef8
    #10 [ffff88272f5af610] __alloc_pages_nodemask at ffffffff811a09c3
    #11 [ffff88272f5af710] alloc_pages_current at ffffffff811e8b71
    #12 [ffff88272f5af760] new_slab at ffffffff811f4523
    #13 [ffff88272f5af7b0] __slab_alloc at ffffffff8173a1b5
    #14 [ffff88272f5af880] kmem_cache_alloc at ffffffff811f484b
    #15 [ffff88272f5af8d0] do_blockdev_direct_IO at ffffffff812535b3
    #16 [ffff88272f5afb00] __blockdev_direct_IO at ffffffff81255dc3
    #17 [ffff88272f5afb30] xfs_vm_direct_IO at ffffffffa01fe3fc [xfs]
    #18 [ffff88272f5afb90] generic_file_read_iter at ffffffff81198994
    #19 [ffff88272f5afc50] __dta_xfs_file_read_iter_2398 at ffffffffa020c970 [xfs]
    #20 [ffff88272f5afcc0] lo_rw_aio at ffffffffa0377042 [loop]
    #21 [ffff88272f5afd70] loop_queue_work at ffffffffa0377c3b [loop]
    #22 [ffff88272f5afe60] kthread_worker_fn at ffffffff810a8a0c
    #23 [ffff88272f5afec0] kthread at ffffffff810a8428
    #24 [ffff88272f5aff50] ret_from_fork at ffffffff81745242

    Signed-off-by: Mikulas Patocka
    Cc: stable@vger.kernel.org
    Signed-off-by: Jens Axboe

    Mikulas Patocka
     

08 Aug, 2019

4 commits

  • Currently, the authorized_default and interface_authorized_default
    attributes for HCD are set up after the uevent has been sent to userland.
    This creates a race condition where userland may fail to access this
    file when processing the event. Move the appending of these attributes
    earlier relying on the usb_bus_notify dispatcher.

    Signed-off-by: Thiébaud Weksteen
    Cc: stable
    Link: https://lore.kernel.org/r/20190806110050.38918-1-tweek@google.com
    Signed-off-by: Greg Kroah-Hartman

    Thiébaud Weksteen
     
  • Since commit 3582dd291788 ("aoe: convert aoeblk to blk-mq"), aoedev_downdev
    has had the possibility of sleeping and causing the following crash.

    BUG: scheduling while atomic: rmmod/2242/0x00000003
    Modules linked in: aoe
    Preemption disabled at:
    [] flush+0x95/0x4a0 [aoe]
    CPU: 7 PID: 2242 Comm: rmmod Tainted: G I 5.2.3 #1
    Hardware name: Intel Corporation S5520HC/S5520HC, BIOS S5500.86B.01.10.0025.030220091519 03/02/2009
    Call Trace:
    dump_stack+0x4f/0x6a
    ? flush+0x95/0x4a0 [aoe]
    __schedule_bug.cold+0x44/0x54
    __schedule+0x44f/0x680
    schedule+0x44/0xd0
    blk_mq_freeze_queue_wait+0x46/0xb0
    ? wait_woken+0x80/0x80
    blk_mq_freeze_queue+0x1b/0x20
    aoedev_downdev+0x111/0x160 [aoe]
    flush+0xff/0x4a0 [aoe]
    aoedev_exit+0x23/0x30 [aoe]
    aoe_exit+0x35/0x948 [aoe]
    __se_sys_delete_module+0x183/0x210
    __x64_sys_delete_module+0x16/0x20
    do_syscall_64+0x4d/0x130
    entry_SYSCALL_64_after_hwframe+0x44/0xa9
    RIP: 0033:0x7f24e0043b07
    Code: 73 01 c3 48 8b 0d 89 73 0b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f
    1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 b0 00 00 00 0f 05 3d 01 f0 ff
    ff 73 01 c3 48 8b 0d 59 73 0b 00 f7 d8 64 89 01 48
    RSP: 002b:00007ffe18f7f1e8 EFLAGS: 00000206 ORIG_RAX: 00000000000000b0
    RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f24e0043b07
    RDX: 000000000000000a RSI: 0000000000000800 RDI: 0000555c3ecf87c8
    RBP: 00007ffe18f7f1f0 R08: 0000000000000000 R09: 0000000000000000
    R10: 00007f24e00b4ac0 R11: 0000000000000206 R12: 00007ffe18f7f238
    R13: 00007ffe18f7f410 R14: 00007ffe18f80e73 R15: 0000555c3ecf8760

    This patch, handling in the same way of pass two, unlocks the locks and
    restart pass one after aoedev_downdev is done.

    Fixes: 3582dd291788 ("aoe: convert aoeblk to blk-mq")
    Signed-off-by: He Zhe
    Signed-off-by: Jens Axboe

    He Zhe
     
  • Commit 4a6ef8e37c4d ("pwm: Add support referencing PWMs from ACPI")
    made pwm_get unconditionally return the acpi_pwm_get return value if
    the device passed to pwm_get has an ACPI fwnode.

    But even if the passed in device has an ACPI fwnode, it does not
    necessarily have the necessary ACPI package defining its pwm bindings,
    especially since the binding / API of this ACPI package has only been
    introduced very recently.

    Up until now X86/ACPI devices which use a separate pwm controller for
    controlling their LCD screen's backlight brightness have been relying
    on the static lookup-list to get their pwm.

    pwm_get unconditionally returning the acpi_pwm_get return value breaks
    this, breaking backlight control on these devices.

    This commit fixes this by making pwm_get fall back to the static
    lookup-list if acpi_pwm_get returns -ENOENT.

    BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=96571
    Reported-by: youling257@gmail.com
    Fixes: 4a6ef8e37c4d ("pwm: Add support referencing PWMs from ACPI")
    Cc: Nikolaus Voss
    Signed-off-by: Hans de Goede
    Reviewed-by: Andy Shevchenko
    Acked-by: Nikolaus Voss
    Signed-off-by: Thierry Reding

    Hans de Goede
     
  • We have to drop the mutex before we close() upon disconnect()
    as close() needs the lock. This is safe to do by dropping the
    mutex as intfdata is already set to NULL, so open() will fail.

    Fixes: 03f36e885fc26 ("USB: open disconnect race in iowarrior")
    Reported-by: syzbot+a64a382964bf6c71a9c0@syzkaller.appspotmail.com
    Cc: stable
    Signed-off-by: Oliver Neukum
    Link: https://lore.kernel.org/r/20190808092728.23417-1-oneukum@suse.com
    Signed-off-by: Greg Kroah-Hartman

    Oliver Neukum