1. 11 Nov, 2018 3 commits
  2. 10 Nov, 2018 10 commits
  3. 09 Nov, 2018 23 commits
  4. 08 Nov, 2018 4 commits
    • Linus Torvalds's avatar
      Merge tag 'xfs-4.20-fixes-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux · 24ccea7e
      Linus Torvalds authored
      Pull xfs fixes from Darrick Wong:
       - fix incorrect dropping of error code from bmap
       - print buffer offsets instead of useless hashed pointers when dumping
         corrupt metadata
       - fix integer overflow in attribute verifier
      * tag 'xfs-4.20-fixes-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
        xfs: fix overflow in xfs_attr3_leaf_verify
        xfs: print buffer offsets when dumping corrupt buffers
        xfs: Fix error code in 'xfs_ioc_getbmap()'
    • Linus Torvalds's avatar
      Merge tag 'led-fixes-for-4.20-rc2' of... · 6a1ac56c
      Linus Torvalds authored
      Merge tag 'led-fixes-for-4.20-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds
      Pull LED fixes from Jacek Anaszewski:
       "All three fixes are related to the newly added pattern trigger:
         - remove mutex_lock() from timer callback, which would trigger
           problems related to sleeping in atomic context, the removal is
           harmless since mutex protection turned out to be redundant in this
         - fix pattern parsing to properly handle intervals with brightness == 0
         - fix typos in the ABI documentation"
      * tag 'led-fixes-for-4.20-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds:
        Documentation: ABI: led-trigger-pattern: Fix typos
        leds: trigger: Fix sleeping function called from invalid context
        Fix pattern handling optimalization
    • Linus Torvalds's avatar
      Merge tag 'sound-4.20-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound · d464572a
      Linus Torvalds authored
      Pull sound fixes from Takashi Iwai:
       "Two small regression fixes for HD-audio: one about vga_switcheroo and
        runtime PM, and another about Oops on some Thinkpads"
      * tag 'sound-4.20-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound:
        ALSA: hda - Fix incorrect clearance of thinkpad_acpi hooks
        vga_switcheroo: Fix missing gpu_bound call at audio client registration
    • John Garry's avatar
      of, numa: Validate some distance map rules · 89c38422
      John Garry authored
      Currently the NUMA distance map parsing does not validate the distance
      table for the distance-matrix rules 1-2 in [1].
      However the arch NUMA code may enforce some of these rules, but not all.
      Such is the case for the arm64 port, which does not enforce the rule that
      the distance between separates nodes cannot equal LOCAL_DISTANCE.
      The patch adds the following rules validation:
      - distance of node to self equals LOCAL_DISTANCE
      - distance of separate nodes > LOCAL_DISTANCE
      This change avoids a yet-unresolved crash reported in [2].
      A note on dealing with symmetrical distances between nodes:
      Validating symmetrical distances between nodes is difficult. If it were
      mandated in the bindings that every distance must be recorded in the
      table, then it would be easy. However, it isn't.
      In addition to this, it is also possible to record [b, a] distance only
      (and not [a, b]). So, when processing the table for [b, a], we cannot
      assert that current distance of [a, b] != [b, a] as invalid, as [a, b]
      distance may not be present in the table and current distance would be
      default at REMOTE_DISTANCE.
      As such, we maintain the policy that we overwrite distance [a, b] = [b, a]
      for b > a. This policy is different to kernel ACPI SLIT validation, which
      allows non-symmetrical distances (ACPI spec SLIT rules allow it). However,
      the distance debug message is dropped as it may be misleading (for a distance
      which is later overwritten).
      Some final notes on semantics:
      - It is implied that it is the responsibility of the arch NUMA code to
        reset the NUMA distance map for an error in distance map parsing.
      - It is the responsibility of the FW NUMA topology parsing (whether OF or
        ACPI) to enforce NUMA distance rules, and not arch NUMA code.
      [1] Documents/devicetree/bindings/numa.txt
      [2] https://www.spinics.net/lists/arm-kernel/msg683304.html
      Cc: stable@vger.kernel.org # 4.7
      Signed-off-by: default avatarJohn Garry <john.garry@huawei.com>
      Acked-by: default avatarWill Deacon <will.deacon@arm.com>
      Signed-off-by: default avatarRob Herring <robh@kernel.org>