Tags

Tags give the ability to mark specific points in history as being important
  • ASB-2018-11-05_3.18-n-release

    https://source.android.com/security/bulletin/2018-11-01
    
    No kernel security patches for ASB-2018-11, however there
    were some from previous ASBs that are now upstream and in
    android common kernels
    
    CVE-2018-9363 from ASB-2018-06
    CVE-2017-0749 from ASB-2017-08
    CVE-2017-0627 from ASB-2017-05
    CVE-2017-0564 from ASB-2017-04
    CVE-2017-13293 from ASB-2018-04
  • ASB-2018-11-05_3.18

    https://source.android.com/security/bulletin/2018-11-01
    
    No kernel security patches for ASB-2018-11, however there
    were some from previous ASBs that are now upstream and in
    android common kernels
    
    CVE-2018-9363 from ASB-2018-06
    CVE-2017-0749 from ASB-2017-08
    CVE-2017-0627 from ASB-2017-05
    CVE-2017-0564 from ASB-2017-04
    CVE-2017-13293 from ASB-2018-04
  • v4.20-rc1

    65102238 · Linux 4.20-rc1 ·
    Linux 4.20-rc1
    
  • v4.14.79

    50961e48 · Linux 4.14.79 ·
    This is the 4.14.79 stable release
    
  • v4.18.17

    2237effd · Linux 4.18.17 ·
    This is the 4.18.17 stable release
    
  • v4.19.1

    07a03b97 · Linux 4.19.1 ·
    This is the 4.19.1 stable release
    
  • xfs-4.20-merge-2

    vfs: rework data cloning infrastructure
    
    Rework the vfs_clone_file_range and vfs_dedupe_file_range infrastructure to use
    a common .remap_file_range method and supply generic bounds and sanity checking
    functions that are shared with the data write path. The current VFS
    infrastructure has problems with rlimit, LFS file sizes, file time stamps,
    maximum filesystem file sizes, stripping setuid bits, etc and so they are
    addressed in these commits.
    
    We also introduce the ability for the ->remap_file_range methods to return short
    clones so that clones for vfs_copy_file_range() don't get rejected if the entire
    range can't be cloned. It also allows filesystems to sliently skip deduplication
    of partial EOF blocks if they are not capable of doing so without requiring
    errors to be thrown to userspace.
    
    All existing filesystems are converted to user the new .remap_file_range method,
    and both XFS and ocfs2 are modified to make use of the new generic checking
    infrastructure.
    
  • media/v4.20-2

    media updates for v4.20-rc1
    
  • pm-4.20-rc1-2

    More power management updates for 4.20-rc1
    
     - Fix build regression in the intel_pstate driver that doesn't
       build without CONFIG_ACPI after recent changes (Dominik Brodowski).
    
     - One of the heuristics in the menu cpuidle governor is based on a
       function returning 0 most of the time, so drop it and clean up
       the scheduler code related to it (Daniel Lezcano).
    
     - Prevent the arm_big_little cpufreq driver from being used on ARM64
       which is not suitable for it and drop the arm_big_little_dt driver
       that is not used any more (Sudeep Holla).
    
     - Prevent the hung task watchdog from triggering during resume from
       system-wide sleep states by disabling it before freezing tasks and
       enabling it again after they have been thawed (Vitaly Kuznetsov).
    
  • acpi-4.20-rc1-2

    More ACPI updates for 4.20-rc1
    
    Rework the handling of the P-unit semaphore on Intel Baytrail and
    Cherrytrail systems to avoid race conditions and excessive overhead
    related to it (Hans de Goede).
    
  • media/v4.20-1

    media updates for v4.20-rc1
    
  • xfs-4.20-merge-1

    xfs: Changes for 4.20
    
    - only support filesystems with unwritten extents
    - add definition for statfs XFS magic number
    - remove unused parameters around reflink code
    - more debug for dangling delalloc extents
    - cancel COW extents on extent swap targets
    - fix quota stats output and clean up the code
    - refactor some of the attribute code in preparation for parent pointers
    - fix several buffer handling bugs
    
  • gpio-v4.20-1

    This is the bulk of GPIO changes for the v4.20 series:
    
    Core changes:
    
    - A patch series from Hans Verkuil to make it possible to
      enable/disable IRQs on a GPIO line at runtime and drive GPIO
      lines as output without having to put/get them from scratch.
      The irqchip callbacks have been improved so that they can
      use only the fastpatch callbacks to enable/disable irqs
      like any normal irqchip, especially the gpiod_lock_as_irq()
      has been improved to be callable in fastpath context.
      A bunch of rework had to be done to achieve this but it is
      a big win since I never liked to restrict this to slowpath.
      The only call requireing slowpath was try_module_get() and
      this is kept at the .request_resources() slowpath callback.
      In the GPIO CEC driver this is a big win sine a single
      line is used for both outgoing and incoming traffic, and
      this needs to use IRQs for incoming traffic while actively
      driving the line for outgoing traffic.
    
    - Janusz Krzysztofik improved the GPIO array API to pass a
      "cookie" (struct gpio_array) and a bitmap for setting or
      getting multiple GPIO lines at once. This improvement
      orginated in a specific need to speed up an OMAP1 driver and
      has led to a much better API and real performance gains
      when the state of the array can be used to bypass a lot
      of checks and code when we want things to go really fast.
      The previous code would minimize the number of calls
      down to the driver callbacks assuming the CPU speed was
      orders of magnitude faster than the I/O latency, but this
      assumption was wrong on several platforms: what we needed
      to do was to profile and improve the speed on the hot
      path of the array functions and this change is now
      completed.
    
    - Clean out the painful and hard to grasp BNF experiments
      from the device tree bindings. Future approaches are looking
      into using JSON schema for this purpose. (Rob Herring
      is floating a patch series.)
    
    New drivers:
    
    - The RCAR driver now supports r8a774a1 (RZ/G2M).
    
    - Synopsys GPIO via CREGs driver.
    
    Major improvements:
    
    - Modernization of the EP93xx driver to use irqdomain and
      other contemporary concepts.
    
    - The ingenic driver has been merged into the Ingenic pin
      control driver and removed from the GPIO subsystem.
    
    - Debounce support in the ftgpio010 driver.