17 Oct, 2013

2 commits

  • Pull device-mapper fix from Alasdair Kergon:
    "A patch to avoid data corruption in a device-mapper snapshot.

    This is primarily a data corruption bug that all users of
    device-mapper snapshots will want to fix. The CVE is due to a data
    leak under specific circumstances if, for example, the snapshot is
    presented to a virtual machine: a block written as data inside the VM
    can get interpreted incorrectly on the host outside the VM as
    metadata, causing the host to provide the VM with access to blocks it
    would not otherwise see. This is likely to affect few, if any,
    people"

    * tag 'dm-3.12-fix-cve' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm:
    dm snapshot: fix data corruption

    Linus Torvalds
     
  • Pull gpio fixes from Linus Walleij:
    "Three GPIO fixes for the v3.12 series:
    - A fix to the Lynxpoint IRQ handler
    - Two late fixes to fallout from the gpiod refactoring"

    * tag 'gpio-v3.12-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio:
    gpiolib: let gpiod_request() return -EPROBE_DEFER
    gpiolib: safer implementation of desc_to_gpio()
    gpio/lynxpoint: check if the interrupt is enabled in IRQ handler

    Linus Torvalds
     

16 Oct, 2013

3 commits

  • This patch fixes a particular type of data corruption that has been
    encountered when loading a snapshot's metadata from disk.

    When we allocate a new chunk in persistent_prepare, we increment
    ps->next_free and we make sure that it doesn't point to a metadata area
    by further incrementing it if necessary.

    When we load metadata from disk on device activation, ps->next_free is
    positioned after the last used data chunk. However, if this last used
    data chunk is followed by a metadata area, ps->next_free is positioned
    erroneously to the metadata area. A newly-allocated chunk is placed at
    the same location as the metadata area, resulting in data or metadata
    corruption.

    This patch changes the code so that ps->next_free skips the metadata
    area when metadata are loaded in function read_exceptions.

    The patch also moves a piece of code from persistent_prepare_exception
    to a separate function skip_metadata to avoid code duplication.

    CVE-2013-4299

    Signed-off-by: Mikulas Patocka
    Cc: stable@vger.kernel.org
    Cc: Mike Snitzer
    Signed-off-by: Alasdair G Kergon

    Mikulas Patocka
     
  • Pull device tree fixes and reverts from Grant Likely:
    "One bug fix and three reverts. The reverts back out the slightly
    controversial feeding the entire device tree into the random pool and
    the reserved-memory binding which isn't fully baked yet. Expect the
    reserved-memory patches at least to resurface for v3.13.

    The bug fixes removes a scary but harmless warning on SPARC that was
    introduced in the v3.12 merge window. v3.13 will contain a proper fix
    that makes the new code work on SPARC.

    On the plus side, the diffstat looks *awesome*. I love removing lines
    of code"

    * tag 'devicetree-for-linus' of git://git.secretlab.ca/git/linux:
    Revert "drivers: of: add initialization code for dma reserved memory"
    Revert "ARM: init: add support for reserved memory defined by device tree"
    Revert "of: Feed entire flattened device tree into the random pool"
    of: fix unnecessary warning on missing /cpus node

    Linus Torvalds
     
  • Pull Xen fixes from Stefano Stabellini:
    "A small fix for Xen on x86_32 and a build fix for xen-tpmfront on
    arm64"

    * tag 'stable/for-linus-3.12-rc4-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip:
    xen: Fix possible user space selector corruption
    tpm: xen-tpmfront: fix missing declaration of xen_domain

    Linus Torvalds
     

15 Oct, 2013

6 commits

  • This reverts commit 9d8eab7af79cb4ce2de5de39f82c455b1f796963. There is
    still no consensus on the bindings for the reserved memory and various
    drawbacks of the proposed solution has been shown, so the best now is to
    revert it completely and start again from scratch later.

    Signed-off-by: Marek Szyprowski
    Signed-off-by: Grant Likely

    Marek Szyprowski
     
  • Pull vfio fix from Alex Williamson:
    "Fix an incorrect break out of nested loop in iommu mapping code"

    * tag 'vfio-v3.12-rc5' of git://github.com/awilliam/linux-vfio:
    VFIO: vfio_iommu_type1: fix bug caused by break in nested loop

    Linus Torvalds
     
  • Pull infiniband updates from Roland Dreier:
    "Last batch of IB changes for 3.12: many mlx5 hardware driver fixes
    plus one trivial semicolon cleanup"

    * tag 'rdma-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband:
    IB: Remove unnecessary semicolons
    IB/mlx5: Ensure proper synchronization accessing memory
    IB/mlx5: Fix alignment of reg umr gather buffers
    IB/mlx5: Fix eq names to display nicely in /proc/interrupts
    mlx5: Fix error code translation from firmware to driver
    IB/mlx5: Fix opt param mask according to firmware spec
    mlx5: Fix opt param mask for sq err to rts transition
    IB/mlx5: Disable atomic operations
    mlx5: Fix layout of struct mlx5_init_seg
    mlx5: Keep polling to reclaim pages while any returned
    IB/mlx5: Avoid async events on invalid port number
    IB/mlx5: Decrease memory consumption of mr caches
    mlx5: Remove checksum on command interface commands
    IB/mlx5: Fix memory leak in mlx5_ib_create_srq
    IB/mlx5: Flush cache workqueue before destroying it
    IB/mlx5: Fix send work queue size calculation

    Linus Torvalds
     
  • Roland Dreier
     
  • These aren't necessary after switch blocks.

    Signed-off-by: Joe Perches
    Signed-off-by: Roland Dreier

    Joe Perches
     
  • Pull ACPI and power management fixes from Rafael Wysocki:
    "These fix two recent bugs in ACPIPHP (ACPI-based PCI hotplug) and
    update a bunch of web links and e-mail addresses in MAINTAINERS, docs
    and Kconfig that either are stale or will expire soon.

    Specifics:

    - The WARN_ON() in acpiphp_enumerate_slots() triggers as a false
    positive in some cases, so drop it.

    - Add a missing pci_dev_put() to an error code path in
    acpiphp_enumerate_slots().

    - Replace my old e-mail address that's going to expire with a new
    one.

    - Update ACPI web links and git tree information in MAINTAINERS.

    - Update links to the Linux-ACPI project's page in MAINTAINERS.

    - Update some stale links and e-mail addresses under Documentation
    and in the ACPI Kconfig file"

    * tag 'pm+acpi-3.12-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
    ACPI / hotplug / PCI: Drop WARN_ON() from acpiphp_enumerate_slots()
    ACPI / hotplug / PCI: Fix error code path in acpiphp_enumerate_slots()
    ACPI / PM / Documentation: Replace outdated project links and addresses
    MAINTAINERS / ACPI: Update links to the Linux-ACPI project web page
    MAINTAINERS / ACPI: Update links and git tree information
    MAINTAINERS / Documentation: Update Rafael's e-mail address

    Linus Torvalds
     

14 Oct, 2013

7 commits

  • This reverts commit 109b6236294b53d8eaa50be7d9e9ad37079f5f7e.

    Tim Bird expressed concern that this will have a bad effect on boot
    time, and while simple tests have shown it to be okay with simple tree,
    a device tree blob can potentially be quite large and
    add_device_randomness() is not a fast function. Rather than do this for
    all platforms unconditionally, I'm reverting this patch and would like
    to see it revisited. Instead of feeding the entire tree into the random
    pool, it would probably be appropriate to hash the tree and feed the
    hash result into the pool. There really isn't a lot of randomness in a
    device tree anyway. In the majority of cases only a handful of
    properties are going to be different between machines with the same
    baseboard.

    Signed-off-by: Grant Likely

    Grant Likely
     
  • Not all DT platforms have all the cpus collected under a /cpus node.
    That just happens to be a details of FDT, ePAPR and PowerPC platforms.
    Sparc does something different, but unfortunately the current code
    complains with a warning if /cpus isn't there. This became a problem
    with commit f86e4718, "driver/core cpu: initialize of_node in cpu's
    device structure", which caused the function to get called for all
    architectures.

    This commit is a temporary fix to fail silently if the cpus node isn't
    present. A proper fix will come later to allow arch code to provide a
    custom mechanism for decoding the CPU hwid if the 'reg' property isn't
    appropriate.

    Signed-off-by: Grant Likely
    Cc: David Miller
    Cc: Sudeep KarkadaNagesha
    Cc: Rob Herring

    Grant Likely
     
  • Pull watchdog fixes from Wim Van Sebroeck:
    "This will fix a deadlock on the ts72xx_wdt driver, fix bitmasks in the
    kempld_wdt driver and fix a section mismatch in the sunxi_wdt driver"

    * git://www.linux-watchdog.org/linux-watchdog:
    watchdog: sunxi: Fix section mismatch
    watchdog: kempld_wdt: Fix bit mask definition
    watchdog: ts72xx_wdt: locking bug in ioctl

    Linus Torvalds
     
  • This driver has a section mismatch, for probe and remove functions,
    leading to the following warning during the compilation.

    WARNING: drivers/watchdog/built-in.o(.data+0x24): Section mismatch in
    reference from the variable sunxi_wdt_driver to the function
    .init.text:sunxi_wdt_probe()
    The variable sunxi_wdt_driver references
    the function __init sunxi_wdt_probe()

    Signed-off-by: Maxime Ripard
    Reviewed-by: Guenter Roeck
    Signed-off-by: Wim Van Sebroeck

    Maxime Ripard
     
  • STAGE_CFG bits are defined as [5:4] bits. However, '(((x) & 0x30) << 4)'
    handles [9:8] bits. Thus, it should be fixed in order to handle
    [5:4] bits.

    Signed-off-by: Jingoo Han
    Reviewed-by: Guenter Roeck
    Signed-off-by: Wim Van Sebroeck

    Jingoo Han
     
  • Calling the WDIOC_GETSTATUS & WDIOC_GETBOOTSTATUS and twice will cause a
    interruptible deadlock.

    Signed-off-by: Dan Carpenter
    Reviewed-by: Guenter Roeck
    Signed-off-by: Wim Van Sebroeck

    Dan Carpenter
     
  • Pull slave-dmaengine fixes from Vinod Koul:
    "Another week, time to send another fixes request taking time out of
    extended weekend for the festivities in this part of the world.

    We have two fixes from Sergei for rcar driver and one fixing memory
    leak of edma driver by Geyslan"

    * 'fixes' of git://git.infradead.org/users/vkoul/slave-dma:
    dma: edma.c: remove edma_desc leakage
    rcar-hpbdma: add parameter to set_slave() method
    rcar-hpbdma: remove shdma_free_irq() calls

    Linus Torvalds
     

13 Oct, 2013

2 commits

  • Pull i2c fixes from Wolfram Sang:
    "We had various reports of problems with deferred probing in the I2C
    subsystem, so this pull requst is a little bigger than usual.

    Most issues should be addressed now so devices will be found
    correctly. A few ususal driver bugfixes are in here, too"

    * 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux:
    i2c: i2c-mux-pinctrl: use deferred probe when adapter not found
    i2c: i2c-arb-gpio-challenge: use deferred probe when adapter not found
    i2c: i2c-mux-gpio: use deferred probing
    i2c: i2c-mux-gpio: don't ignore of_get_named_gpio errors
    i2c: omap: Clear ARDY bit twice
    i2c: Not all adapters have a parent
    i2c: i2c-stu300: replace platform_driver_probe to support deferred probing
    i2c: i2c-mxs: replace platform_driver_probe to support deferred probing
    i2c: i2c-imx: replace platform_driver_probe to support deferred probing
    i2c: i2c-designware-platdrv: replace platform_driver_probe to support deferred probing

    Linus Torvalds
     
  • Pull x86 fixes from Ingo Molnar:
    "A build fix and a reboot quirk"

    * 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
    x86/reboot: Add reboot quirk for Dell Latitude E5410
    x86, build, pci: Fix PCI_MSI build on !SMP

    Linus Torvalds
     

12 Oct, 2013

5 commits

  • * acpi-pci-hotplug:
    ACPI / hotplug / PCI: Drop WARN_ON() from acpiphp_enumerate_slots()
    ACPI / hotplug / PCI: Fix error code path in acpiphp_enumerate_slots()

    Rafael J. Wysocki
     
  • The WARN_ON() in acpiphp_enumerate_slots() triggers unnecessarily for
    devices whose bridges are going to be handled by native PCIe hotplug
    (pciehp) and the simplest way to prevent that from happening is to
    drop the WARN_ON().

    References: https://bugzilla.kernel.org/show_bug.cgi?id=62831
    Reported-by: Steven Rostedt
    Signed-off-by: Rafael J. Wysocki

    Rafael J. Wysocki
     
  • One of the error code paths in acpiphp_enumerate_slots() is missing
    a pci_dev_put(bridge->pci_dev) call, so add it.

    Signed-off-by: Rafael J. Wysocki
    Acked-by: Bjorn Helgaas

    Rafael J. Wysocki
     
  • Pull drm fixes from Dave Airlie:
    "All over the map..

    - nouveau:
    disable MSI, needs more work, will try again next merge window
    - radeon:
    audio + uvd regression fixes, dpm fixes, reset fixes
    - i915:
    the dpms fix might fix your haswell

    And one pain in the ass revert, so we have VGA arbitration that when
    implemented 4-5 years ago really hoped that GPUs could remove
    themselves from arbitration completely once they had a kernel driver.

    It seems Intel hw designers decided that was too nice a facility to
    allow us to have so they removed it when they went on-die (so since
    Ironlake at least). Now Alex Williamson added support for VGA
    arbitration for newer GPUs however this now exposes itself to
    userspace as requireing arbitration of GPU VGA regions and the X
    server gets involved and disables things that it can't handle when VGA
    access is possibly required around every operation.

    So in order to not break userspace we just reverted things back to the
    old known broken status so maybe we can try and design out way out.

    Ville also had a patch to use stop machine for the two times Intel
    needs to access VGA space, that might be acceptable with some rework,
    but for now myself and Daniel agreed to just go back"

    * 'drm-fixes' of git://people.freedesktop.org/~airlied/linux: (23 commits)
    Revert "i915: Update VGA arbiter support for newer devices"
    Revert "drm/i915: Delay disabling of VGA memory until vgacon->fbcon handoff is done"
    drm/radeon: re-enable sw ACR support on pre-DCE4
    drm/radeon/dpm: disable bapm on TN asics
    drm/radeon: improve soft reset on CIK
    drm/radeon: improve soft reset on SI
    drm/radeon/dpm: off by one in si_set_mc_special_registers()
    drm/radeon/dpm/btc: off by one in btc_set_mc_special_registers()
    drm/radeon: forever loop on error in radeon_do_test_moves()
    drm/radeon: fix hw contexts for SUMO2 asics
    drm/radeon: fix typo in CP DMA register headers
    drm/radeon/dpm: disable multiple UVD states
    drm/radeon: use hw generated CTS/N values for audio
    drm/radeon: fix N/CTS clock matching for audio
    drm/radeon: use 64-bit math to calculate CTS values for audio (v2)
    drm/edid: catch kmalloc failure in drm_edid_to_speaker_allocation
    Revert "drm/fb-helper: don't sleep for screen unblank when an oops is in progress"
    drm/gma500: fix things after get/put page helpers
    drm/nouveau/mc: disable msi support by default, it's busted in tons of places
    drm/i915: Only apply DPMS to the encoder if enabled
    ...

    Linus Torvalds
     
  • In vfio_iommu_type1.c there is a bug in vfio_dma_do_map, when checking
    that pages are not already mapped. Since the check is being done in a
    for loop nested within the main loop, breaking out of it does not create
    the intended behavior. If the underlying IOMMU driver returns a non-NULL
    value, this will be ignored and mapping the DMA range will be attempted
    anyway, leading to unpredictable behavior.

    This interracts badly with the ARM SMMU driver issue fixed in the patch
    that was submitted with the title:
    "[PATCH 2/2] ARM: SMMU: return NULL on error in arm_smmu_iova_to_phys"
    Both fixes are required in order to use the vfio_iommu_type1 driver
    with an ARM SMMU.

    This patch refactors the function slightly, in order to also make this
    kind of bug less likely.

    Signed-off-by: Antonios Motakis
    Signed-off-by: Alex Williamson

    Antonios Motakis
     

11 Oct, 2013

15 commits

  • Patch be1a4b brought some improvements to the GPIO error handling code,
    but also changed the return value of gpiod_request() when called on a
    not yet initialized GPIO descriptor: it now returns -EINVAL instead of
    -EPROBE_DEFER, and this affects some drivers.

    This patch restores the original behavior for gpiod_request(). It is
    safe to do so now that desc_to_gpio() does not rely on the GPIO
    descriptor to be initialized. Other functions changed by patch be1a4b
    do not see their return value affected, so these are not reverted.

    Signed-off-by: Alexandre Courbot
    Reported-by: Dr. H. Nikolaus Schaller
    Signed-off-by: Linus Walleij

    Alexandre Courbot
     
  • The current implementation of desc_to_gpio() relies on the chip pointer
    to be set to a valid value in order to compute the GPIO number. This
    was done in the hope that we can get rid of the gpio_desc global array,
    but this is not happening anytime soon.

    This patch reimplements desc_to_gpio() in a fashion similar to that of
    gpio_to_desc(). As a result, desc_to_gpio(gpio_to_desc(gpio)) == gpio is
    now always true. This allows to call desc_to_gpio() on non-initialized
    descriptors as some error-handling code currently does.

    Signed-off-by: Alexandre Courbot
    Reported-by: Dr. H. Nikolaus Schaller
    Signed-off-by: Linus Walleij

    Alexandre Courbot
     
  • Some links to projects web pages and e-mail addresses in ACPI/PM
    documentation and Kconfig are outdated, so update them.

    Signed-off-by: Rafael J. Wysocki

    Rafael J. Wysocki
     
  • Checking LP_INT_STAT is not enough in the interrupt handler because its
    contents get updated regardless of whether the pin has interrupt enabled or
    not. This causes the driver to loop forever for GPIOs that are pulled up.

    Fix this by checking the interrupt enable bit for the pin as well.

    Cc: stable@vger.kernel.org
    Signed-off-by: Mika Westerberg
    Acked-by: Mathias Nyman
    Signed-off-by: Linus Walleij

    Mika Westerberg
     
  • This reverts commit 81b5c7bc8de3e6f63419139c2fc91bf81dea8a7d.

    Adding drm/i915 into the vga arbiter chain means that X (in a piece of
    well-meant paranoia) will do a get/put on the vga decoding around
    _every_ accel call down into the ddx. Which results in some nice
    performance disasters [1]. This really breaks userspace, by disabling
    DRI for everyone, and stops OpenGL from working, this isn't limited
    to just the i915 but both the integrated and discrete GPUs on
    multi-gpu systems, in other words this causes untold worlds of pain,

    Ville tried to come up with a Great Hack to fiddle the required VGA
    I/O ops behind everyone's back using stop_machine, but that didn't
    really work out [2]. Given that we're fairly late in the -rc stage for
    such games let's just revert this all.

    One thing we might want to keep is to delay the disabling of the vga
    decoding until the fbdev emulation and the fbcon screen is set up. If
    we kill vga mem decoding beforehand fbcon can end up with a white
    square in the top-left corner it tried to save from the vga memory for
    a seamless transition. And we have bug reports on older platforms
    which seem to match these symptoms.

    But again that's something to play around with in -next.

    References: [1] http://lists.x.org/archives/xorg-devel/2013-September/037763.html
    References: [2] http://www.spinics.net/lists/intel-gfx/msg34062.html
    Cc: Alex Williamson
    Cc: Ville Syrjälä
    Cc: Chris Wilson
    Signed-off-by: Daniel Vetter
    Signed-off-by: Dave Airlie

    Dave Airlie
     
  • This reverts commit 6e1b4fdad5157bb9e88777d525704aba24389bee.

    This is part of a revert due to a userspace breakage, better explained in the revert of 1a1a4cbf4906a13c0c377f708df5d94168e7b582.

    Signed-off-by: Daniel Vetter
    Signed-off-by: Dave Airlie

    Dave Airlie
     
  • Regression fixes for audio and UVD, several hang fixes,
    some DPM fixes.

    * 'drm-fixes-3.12' of git://people.freedesktop.org/~agd5f/linux:
    drm/radeon: re-enable sw ACR support on pre-DCE4
    drm/radeon/dpm: disable bapm on TN asics
    drm/radeon: improve soft reset on CIK
    drm/radeon: improve soft reset on SI
    drm/radeon/dpm: off by one in si_set_mc_special_registers()
    drm/radeon/dpm/btc: off by one in btc_set_mc_special_registers()
    drm/radeon: forever loop on error in radeon_do_test_moves()
    drm/radeon: fix hw contexts for SUMO2 asics
    drm/radeon: fix typo in CP DMA register headers
    drm/radeon/dpm: disable multiple UVD states
    drm/radeon: use hw generated CTS/N values for audio
    drm/radeon: fix N/CTS clock matching for audio
    drm/radeon: use 64-bit math to calculate CTS values for audio (v2)
    drm/edid: catch kmalloc failure in drm_edid_to_speaker_allocation

    Dave Airlie
     
  • Free memory allocated to edma_desc when failing to allocate slot.

    Signed-off-by: Geyslan G. Bem
    Signed-off-by: Vinod Koul

    Geyslan G. Bem
     
  • Commit 4981c4dc194efb18f0e9a02f1b43e926f2f0d2bb (DMA: shdma: switch DT mode to
    use configuration data from a match table) added a new parameter to set_slave()
    method but unfortunately got merged later than commit c4f6c41ba790bbbfcebb4c47a
    (dma: add driver for R-Car HPB-DMAC), so that the HPB-DMAC driver retained the
    old prototype which caused this warning:

    drivers/dma/sh/rcar-hpbdma.c:485: warning: initialization from incompatible
    pointer type

    The newly added parameter is used to override DMA slave address from 'struct
    hpb_dmae_slave_config', so we have to add the 'slave_addr' field to 'struct
    hpb_dmae_chan', conditionally assign it in set_slave() method, and return in
    slave_addr() method.

    Signed-off-by: Sergei Shtylyov
    Tested-by: Simon Horman
    Signed-off-by: Vinod Koul

    Sergei Shtylyov
     
  • Commit c1c63a14f4f2419d093acd7164eccdff315baa86 (DMA: shdma: switch to managed
    resource allocation) got rid of shdma_free_irq() but unfortunately got merged
    later than commit c4f6c41ba790bbbfcebb4c47a709ac8ff1fe1af9 (dma: add driver for
    R-Car HPB-DMAC), so that the HPB-DMAC driver retained the calls and got broken:

    drivers/dma/sh/rcar-hpbdma.c: In function `hpb_dmae_alloc_chan_resources':
    drivers/dma/sh/rcar-hpbdma.c:435: error: implicit declaration of function
    `shdma_free_irq'

    Fix this compilation error by removing the remaining shdma_free_irq() calls.

    Reported-by: Simon Horman
    Signed-off-by: Sergei Shtylyov
    Tested-by: Simon Horman
    Signed-off-by: Vinod Koul

    Sergei Shtylyov
     
  • Commit c0f04d88e46d ("bcache: Fix flushes in writeback mode") was fixing
    a reported data corruption bug, but it seems some last minute
    refactoring or rebasing introduced a null pointer deref.

    Signed-off-by: Kent Overstreet
    Cc: linux-stable # >= v3.10
    Reported-by: Gabriel de Perthuis
    Signed-off-by: Linus Torvalds

    Kent Overstreet
     
  • Pull hwmon fix from Guenter Roeck:
    "Fix root cause of crash/error seen in applesmc driver"

    * tag 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging:
    hwmon: (applesmc) Always read until end of data

    Linus Torvalds
     
  • Pull watchdog fix from Wim Van Sebroeck:
    "Make sure that the hpwdt driver will not load auxilary iLO devices"

    * git://www.linux-watchdog.org/linux-watchdog:
    watchdog: hpwdt: Patch to ignore auxilary iLO devices

    Linus Torvalds
     
  • This patch is to prevent hpwdt from loading on any auxilary iLO devices defined
    after the initial (or main) iLO device. All auxilary iLO devices will have a
    subsystem device ID set to 0x1979 in order for hpwdt to differentiate between
    the two types.

    Signed-off-by: Thomas Mingarelli
    Tested-by: Lisa Mitchell
    Signed-off-by: Wim Van Sebroeck

    Mingarelli, Thomas
     
  • Pull /dev/random changes from Ted Ts'o:
    "These patches are designed to enable improvements to /dev/random for
    non-x86 platforms, in particular MIPS and ARM"

    * tag 'random_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random:
    random: allow architectures to optionally define random_get_entropy()
    random: run random_int_secret_init() run after all late_initcalls

    Linus Torvalds