Skip to content
Commits on Jan 17, 2013
  1. @gregkh

    Linux 3.0.59

    gregkh committed Jan 17, 2013
  2. @ian-abbott @gregkh

    staging: comedi: Kconfig: COMEDI_NI_AT_A2150 should select COMEDI_FC

    ian-abbott committed with gregkh Jan 3, 2013
    commit 34ffb33 upstream.
    The 'ni_at_a2150' module links to `cfc_write_to_buffer` in the
    'comedi_fc' module, so selecting 'COMEDI_NI_AT_A2150' in the kernel config
    needs to also select 'COMEDI_FC'.
    Signed-off-by: Ian Abbott <>
    Signed-off-by: Greg Kroah-Hartman <>
  3. @ian-abbott @gregkh

    staging: comedi: don't hijack hardware device private data

    ian-abbott committed with gregkh Mar 30, 2012
    commit c43435d upstream.
    comedi_auto_config() associates a Comedi minor device number with an
    auto-configured hardware device and comedi_auto_unconfig() disassociates
    it.  Currently, these use the hardware device's private data pointer to
    point to some allocated storage holding the minor device number.  This
    is a bit of a waste of the hardware device's private data pointer,
    preventing it from being used for something more useful by the low-level
    comedi device drivers.  For example, it would make more sense if
    comedi_usb_auto_config() was passed a pointer to the struct
    usb_interface instead of the struct usb_device, but this cannot be done
    currently because the low-level comedi drivers already use the private
    data pointer in the struct usb_interface for something more useful.
    This patch stops the comedi core hijacking the hardware device's private
    data pointer.  Instead, comedi_auto_config() stores a pointer to the
    hardware device's struct device in the struct comedi_device_file_info
    associated with the minor device number, and comedi_auto_unconfig()
    calls new function comedi_find_board_minor() to recover the minor device
    number associated with the hardware device.
    Signed-off-by: Ian Abbott <>
    Signed-off-by: Greg Kroah-Hartman <>
  4. @danvet @gregkh

    Revert "drm/i915: no lvds quirk for Zotac ZDBOX SD ID12/ID13"

    danvet committed with gregkh Jan 7, 2013
    commit 48e8583 upstream.
    This reverts commit 9756fe3.
    The bogus lvds output is actually a lvds->hdmi bridge, which we don't
    really support. But unconditionally disabling it breaks some existing
    Reported-by: John Tapsell <>
    Signed-off-by: Daniel Vetter <>
    Cc: Luis Henriques <>
    Signed-off-by: Greg Kroah-Hartman <>
  5. @agraf @gregkh

    KVM: PPC: 44x: fix DCR read/write

    agraf committed with gregkh Oct 6, 2012
    commit e43a028 upstream.
    When remembering the direction of a DCR transaction, we should write
    to the same variable that we interpret on later when doing vcpu_run
    Signed-off-by: Alexander Graf <>
    Signed-off-by: CAI Qian <>
    Signed-off-by: Greg Kroah-Hartman <>
  6. @dwmw2 @gregkh

    intel-iommu: Free old page tables before creating superpage

    dwmw2 committed with gregkh Dec 19, 2012
    commit 6491d4d upstream.
    The dma_pte_free_pagetable() function will only free a page table page
    if it is asked to free the *entire* 2MiB range that it covers. So if a
    page table page was used for one or more small mappings, it's likely to
    end up still present in the page tables... but with no valid PTEs.
    This was fine when we'd only be repopulating it with 4KiB PTEs anyway
    but the same virtual address range can end up being reused for a
    *large-page* mapping. And in that case were were trying to insert the
    large page into the second-level page table, and getting a complaint
    from the sanity check in __domain_mapping() because there was already a
    corresponding entry. This was *relatively* harmless; it led to a memory
    leak of the old page table page, but no other ill-effects.
    Fix it by calling dma_pte_clear_range (hopefully redundant) and
    dma_pte_free_pagetable() before setting up the new large page.
    Signed-off-by: David Woodhouse <>
    Tested-by: Ravi Murty <>
    Tested-by: Sudeep Dutt <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: CAI Qian <>
    Signed-off-by: Greg Kroah-Hartman <>
  7. @gregkh

    GFS2: Test bufdata with buffer locked and gfs2_log_lock held

    Benjamin Marzinski committed with gregkh Nov 7, 2012
    commit 96e5d1d upstream.
    In gfs2_trans_add_bh(), gfs2 was testing if a there was a bd attached to the
    buffer without having the gfs2_log_lock held. It was then assuming it would
    stay attached for the rest of the function. However, without either the log
    lock being held of the buffer locked, __gfs2_ail_flush() could detach bd at any
    time.  This patch moves the locking before the test.  If there isn't a bd
    already attached, gfs2 can safely allocate one and attach it before locking.
    There is no way that the newly allocated bd could be on the ail list,
    and thus no way for __gfs2_ail_flush() to detach it.
    Signed-off-by: Benjamin Marzinski <>
    Signed-off-by: Steven Whitehouse <>
    [bwh: Backported to 3.2: adjust context]
    Signed-off-by: Ben Hutchings <>
  8. @gregkh

    xhci: Handle HS bulk/ctrl endpoints that don't NAK.

    Sarah Sharp committed with gregkh Dec 17, 2012
    commit 55c1945 upstream.
    A high speed control or bulk endpoint may have bInterval set to zero,
    which means it does not NAK.  If bInterval is non-zero, it means the
    endpoint NAKs at a rate of 2^(bInterval - 1).
    The xHCI code to compute the NAK interval does not handle the special
    case of zero properly.  The current code unconditionally subtracts one
    from bInterval and uses it as an exponent.  This causes a very large
    bInterval to be used, and warning messages like these will be printed:
    usb 1-1: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
    This may cause the xHCI host hardware to reject the Configure Endpoint
    command, which means the HS device will be unusable under xHCI ports.
    This patch should be backported to kernels as old as 2.6.31, that contain
    commit dfa49c4 "USB: xhci - fix math in
    Reported-by: Vincent Pelletier <>
    Suggested-by: Alan Stern <>
    Signed-off-by: Sarah Sharp <>
    Signed-off-by: Greg Kroah-Hartman <>
  9. @gregkh

    USB: hub: handle claim of enabled remote wakeup after reset

    Oliver Neukum committed with gregkh Nov 29, 2012
    commit 07e72b9 upstream.
    Some touchscreens have buggy firmware which claims
    remote wakeup to be enabled after a reset. They nevertheless
    crash if the feature is cleared by the host.
    Add a check for reset resume before checking for
    an enabled remote wakeup feature. On compliant
    devices the feature must be cleared after a reset anyway.
    Signed-off-by: Oliver Neukum <>
    Acked-by: Alan Stern <>
    Signed-off-by: Greg Kroah-Hartman <>
  10. @gregkh

    USB: Increase reset timeout.

    Sarah Sharp committed with gregkh Nov 14, 2012
    commit 77c7f07 upstream.
    John's NEC 0.96 xHCI host controller needs a longer timeout for a warm
    reset to complete.  The logs show it takes 650ms to complete the warm
    reset, so extend the hub reset timeout to 800ms to be on the safe side.
    This commit should be backported to kernels as old as 3.2, that contain
    the commit 75d7cf7 "usbcore: refine
    warm reset logic".
    Signed-off-by: Sarah Sharp <>
    Acked-by: Alan Stern <>
    Reported-by: John Covici <>
    Signed-off-by: Greg Kroah-Hartman <>
  11. @gregkh

    usb: gadget: dummy: fix enumeration with g_multi

    Sebastian Andrzej Siewior committed with gregkh Nov 20, 2012
    commit 1d16638 upstream.
    If we do have endpoints named like "ep-a" then bEndpointAddress is
    counted internally by the gadget framework.
    If we do have endpoints named like "ep-1" then bEndpointAddress is
    assigned from the digit after "ep-".
    If we do have both, then it is likely that after we used up the
    "generic" endpoints we will use the digits and thus assign one
    bEndpointAddress to multiple endpoints.
    This theory can be proofed by using the completely enabled g_multi.
    Without this patch, the mass storage won't enumerate and times out
    because it shares endpoints with RNDIS.
    This patch also adds fills up the endpoints list so we have in total
    endpoints 1 to 15 in + out available while some of them are restricted
    to certain types like BULK or ISO. Without this change the nokia gadget
    won't load because the system does not provide enough (BULK) endpoints
    but it did before ep-a - ep-f were removed.
    Signed-off-by: Sebastian Andrzej Siewior <>
    Acked-by: Alan Stern <>
    Signed-off-by: Felipe Balbi <>
    Signed-off-by: Greg Kroah-Hartman <>
  12. @gregkh

    USB: cdc-acm: Add support for "PSC Scanning, Magellan 800i"

    Denis N Ladin committed with gregkh Dec 26, 2012
    commit 036915a upstream.
    Adding support "PSC Scanning, Magellan 800i" in cdc-acm
    Very simple, but very necessary.
    Suitable for all versions of the kernel > 2.6
    Signed-off-by: Denis N Ladin <>
    Acked-by: Oliver Neukum <>
    Signed-off-by: Greg Kroah-Hartman <>
  13. @qdotme @gregkh

    usb: ftdi_sio: Crucible Technologies COMET Caller ID - pid added

    qdotme committed with gregkh Jan 13, 2013
    commit 8cf65dc upstream.
    Simple fix to add support for Crucible Technologies COMET Caller ID
    USB decoder - a device containing FTDI USB/Serial converter chip,
    handling 1200bps CallerID messages decoded from the phone line -
    adding correct USB PID is sufficient.
    Tested to apply cleanly and work flawlessly against 3.6.9, 3.7.0-rc8
    and 3.8.0-rc3 on both amd64 and x86 arches.
    Signed-off-by: Tomasz Mloduchowski <>
    Signed-off-by: Greg Kroah-Hartman <>
  14. @bmork @gregkh

    USB: option: add Telekom Speedstick LTE II

    bmork committed with gregkh Dec 28, 2012
    commit 5ec0085 upstream.
    also known as Alcatel One Touch L100V LTE
    The driver description files gives these names to the vendor specific
    functions on this modem:
     Application1: VID_1BBB&PID_011E&MI_00
     Application2: VID_1BBB&PID_011E&MI_01
     Modem:        VID_1BBB&PID_011E&MI_03
     Ethernet:     VID_1BBB&PID_011E&MI_04
    Reported-by: Thomas Schäfer <>
    Signed-off-by: Bjørn Mork <>
    Signed-off-by: Greg Kroah-Hartman <>
  15. @gregkh

    USB: option: Add new MEDIATEK PID support

    Quentin.Li committed with gregkh Dec 26, 2012
    commit 94a85b6 upstream.
    In option.c, add some new MEDIATEK PIDs support for MEDIATEK new products. This
    is a MEDIATEK inc. release patch.
    Signed-off-by: Quentin.Li <>
    Signed-off-by: Greg Kroah-Hartman <>
  16. @bmork @gregkh

    USB: option: blacklist network interface on ZTE MF880

    bmork committed with gregkh Dec 19, 2012
    commit fab3824 upstream.
    The driver description files gives these names to the vendor specific
    functions on this modem:
     diag: VID_19D2&PID_0284&MI_00
     nmea: VID_19D2&PID_0284&MI_01
     at:   VID_19D2&PID_0284&MI_02
     mdm:  VID_19D2&PID_0284&MI_03
     net:  VID_19D2&PID_0284&MI_04
    Signed-off-by: Bjørn Mork <>
    Signed-off-by: Greg Kroah-Hartman <>
  17. @gregkh

    USB: option: add Nexpring NP10T terminal id

    Dzianis Kahanovich committed with gregkh Dec 3, 2012
    commit ad86e58 upstream.
    Hyundai Petatel Inc. Nexpring NP10T terminal (EV-DO rev.A USB modem) ID
    Signed-off-by: Denis Kaganovich <>
    Signed-off-by: Greg Kroah-Hartman <>
  18. @jmberg @gregkh

    mac80211: use del_timer_sync for final sta cleanup timer deletion

    jmberg committed with gregkh Dec 13, 2012
    commit a56f992 upstream.
    This is a very old bug, but there's nothing that prevents the
    timer from running while the module is being removed when we
    only do del_timer() instead of del_timer_sync().
    The timer should normally not be running at this point, but
    it's not clearly impossible (or we could just remove this.)
    Tested-by: Ben Greear <>
    Signed-off-by: Johannes Berg <>
    Signed-off-by: Greg Kroah-Hartman <>
  19. @gregkh

    radeon/kms: force rn50 chip to always report connected on analog output

    Jerome Glisse committed with gregkh Jan 8, 2013
    commit 51861d4 upstream.
    Those rn50 chip are often connected to console remoting hw and load
    detection often fails with those. Just don't try to load detect and
    report connect.
    Signed-off-by: Jerome Glisse <>
    Signed-off-by: Alex Deucher <>
    Signed-off-by: Greg Kroah-Hartman <>
  20. @sthibaul @gregkh

    staging: speakup: avoid out-of-range access in synth_add()

    sthibaul committed with gregkh Jan 7, 2013
    commit 6102c48 upstream.
    Check that array index is in-bounds before accessing the synths[] array.
    Signed-off-by: Samuel Thibault <>
    Cc: Nickolai Zeldovich <>
    Signed-off-by: Greg Kroah-Hartman <>
  21. @zeldovich @gregkh

    staging: speakup: avoid out-of-range access in synth_init()

    zeldovich committed with gregkh Jan 5, 2013
    commit ae42865 upstream.
    Check that array index is in-bounds before accessing the synths[] array.
    Signed-off-by: Nickolai Zeldovich <>
    Cc: Samuel Thibault <>
    Signed-off-by: Greg Kroah-Hartman <>
  22. @lwfinger @gregkh

    staging: r8712u: Add new device ID

    lwfinger committed with gregkh Dec 29, 2012
    commit da849a9 upstream.
    The ISY IWL 1000 USB WLAN stick with USB ID 050d:11f1 is a clone of
    the Belkin F7D1101 V1 device.
    Reported-by: Thomas Hartmann <>
    Signed-off-by: Larry Finger <>
    Cc: Thomas Hartmann <>
    Signed-off-by: Greg Kroah-Hartman <>
  23. @ian-abbott @gregkh

    staging: comedi: comedi_test: fix race when cancelling command

    ian-abbott committed with gregkh Jan 4, 2013
    commit c0729ee upstream.
    Éric Piel reported a kernel oops in the "comedi_test" module.  It was a
    NULL pointer dereference within `waveform_ai_interrupt()` (actually a
    timer function) that sometimes occurred when a running asynchronous
    command is cancelled (either by the `COMEDI_CANCEL` ioctl or by closing
    the device file).
    This seems to be a race between the caller of `waveform_ai_cancel()`
    which on return from that function goes and tears down the running
    command, and the timer function which uses the command.  In particular,
    `async->cmd.chanlist` gets freed (and the pointer set to NULL) by
    `do_become_nonbusy()` in "comedi_fops.c" but a previously scheduled
    `waveform_ai_interrupt()` timer function will dereference that pointer
    regardless, leading to the oops.
    Fix it by replacing the `del_timer()` call in `waveform_ai_cancel()`
    with `del_timer_sync()`.
    Signed-off-by: Ian Abbott <>
    Reported-by: Éric Piel <>
    Signed-off-by: Greg Kroah-Hartman <>
  24. @ian-abbott @gregkh

    staging: comedi: prevent auto-unconfig of manually configured devices

    ian-abbott committed with gregkh Dec 4, 2012
    commit 7d3135a upstream.
    When a low-level comedi driver auto-configures a device, a `struct
    comedi_dev_file_info` is allocated (as well as a `struct
    comedi_device`) by `comedi_alloc_board_minor()`.  A pointer to the
    hardware `struct device` is stored as a cookie in the `struct
    comedi_dev_file_info`.  When the low-level comedi driver
    auto-unconfigures the device, `comedi_auto_unconfig()` uses the cookie
    to find the `struct comedi_dev_file_info` so it can detach the comedi
    device from the driver, clean it up and free it.
    A problem arises if the user manually unconfigures and reconfigures the
    comedi device using the `COMEDI_DEVCONFIG` ioctl so that is no longer
    associated with the original hardware device.  The problem is that the
    cookie is not cleared, so that a call to `comedi_auto_unconfig()` from
    the low-level driver will still find it, detach it, clean it up and free
    Stop this problem occurring by always clearing the `hardware_device`
    cookie in the `struct comedi_dev_file_info` whenever the
    `COMEDI_DEVCONFIG` ioctl call is successful.
    Signed-off-by: Ian Abbott <>
    Signed-off-by: Greg Kroah-Hartman <>
  25. @mike-dunn @gregkh

    ALSA: pxa27x: fix ac97 cold reset

    mike-dunn committed with gregkh Jan 7, 2013
    commit 41b645c upstream.
    Cold reset on the pxa27x currently fails and
         pxa2xx_ac97_try_cold_reset: cold reset timeout (GSR=0x44)
    appears in the kernel log.  Through trial-and-error (the pxa270 developer's
    manual is mostly incoherent on the topic of ac97 reset), I got cold reset to
    complete by setting the WARM_RST bit in the GCR register (and later noticed that
    pxa3xx does this for cold reset as well).  Also, a timeout loop is needed to
    wait for the reset to complete.
    Tested on a palm treo 680 machine.
    Signed-off-by: Mike Dunn <>
    Acked-by: Igor Grinberg <>
    Signed-off-by: Mark Brown <>
    Signed-off-by: Greg Kroah-Hartman <>
  26. @broonie @gregkh

    ASoC: wm2000: Fix sense of speech clarity enable

    broonie committed with gregkh Jan 4, 2013
    commit 267f8fa upstream.
    Signed-off-by: Mark Brown <>
    Signed-off-by: Greg Kroah-Hartman <>
  27. @gregkh

    epoll: prevent missed events on EPOLL_CTL_MOD

    Eric Wong committed with gregkh Jan 1, 2013
    commit 128dd17 upstream.
    EPOLL_CTL_MOD sets the interest mask before calling f_op->poll() to
    ensure events are not missed.  Since the modifications to the interest
    mask are not protected by the same lock as ep_poll_callback, we need to
    ensure the change is visible to other CPUs calling ep_poll_callback.
    We also need to ensure f_op->poll() has an up-to-date view of past
    events which occured before we modified the interest mask.  So this
    barrier also pairs with the barrier in wq_has_sleeper().
    This should guarantee either ep_poll_callback or f_op->poll() (or both)
    will notice the readiness of a recently-ready/modified item.
    This issue was encountered by Andreas Voellmy and Junchang(Jason) Wang in:
    Signed-off-by: Eric Wong <>
    Cc: Hans Verkuil <>
    Cc: Jiri Olsa <>
    Cc: Jonathan Corbet <>
    Cc: Al Viro <>
    Cc: Davide Libenzi <>
    Cc: Hans de Goede <>
    Cc: Mauro Carvalho Chehab <>
    Cc: David Miller <>
    Cc: Eric Dumazet <>
    Cc: Andrew Morton <>
    Cc: Andreas Voellmy <>
    Tested-by: "Junchang(Jason) Wang" <>
    Signed-off-by: Linus Torvalds <>
    [bwh: Backported to 3.2: adjust context]
    Signed-off-by: Ben Hutchings <>
    Signed-off-by: Greg Kroah-Hartman <>
  28. @gregkh

    rtnetlink: fix rtnl_calcit() and rtnl_dump_ifinfo()

    Eric Dumazet committed with gregkh Jan 4, 2013
    commit a4b64fb upstream.
    nlmsg_parse() might return an error, so test its return value before
    potential random memory accesses.
    Errors introduced in commit 115c9b8 (rtnetlink: Fix problem with
    buffer allocation)
    Signed-off-by: Eric Dumazet <>
    Acked-by: Greg Rose <>
    Signed-off-by: David S. Miller <>
    Cc: Ben Hutchings <>
    Signed-off-by: Greg Kroah-Hartman <>
  29. @gregkh

    rtnetlink: Fix problem with buffer allocation

    Greg Rose committed with gregkh Jan 4, 2013
    commit 115c9b8 upstream.
    Implement a new netlink attribute type IFLA_EXT_MASK.  The mask
    is a 32 bit value that can be used to indicate to the kernel that
    certain extended ifinfo values are requested by the user application.
    At this time the only mask value defined is RTEXT_FILTER_VF to
    indicate that the user wants the ifinfo dump to send information
    about the VFs belonging to the interface.
    This patch fixes a bug in which certain applications do not have
    large enough buffers to accommodate the extra information returned
    by the kernel with large numbers of SR-IOV virtual functions.
    Those applications will not send the new netlink attribute with
    the interface info dump request netlink messages so they will
    not get unexpectedly large request buffers returned by the kernel.
    Modifies the rtnl_calcit function to traverse the list of net
    devices and compute the minimum buffer size that can hold the
    info dumps of all matching devices based upon the filter passed
    in via the new netlink attribute filter mask.  If no filter
    mask is sent then the buffer allocation defaults to NLMSG_GOODSIZE.
    With this change it is possible to add yet to be defined netlink
    attributes to the dump request which should make it fairly extensible
    in the future.
    Signed-off-by: Greg Rose <>
    Acked-by: Greg Rose <>
    Signed-off-by: David S. Miller <>
    [bwh: Backported to 3.0:
     - Adjust context
     - Drop the change in do_setlink() that reverts commit f18da14
       ('net: RTNETLINK adjusting values of min_ifinfo_dump_size'), which
       was never applied here]
    Signed-off-by: Ben Hutchings <>
    Signed-off-by: Greg Kroah-Hartman <>
  30. @gregkh

    rtnetlink: Compute and store minimum ifinfo dump size

    Greg Rose committed with gregkh Jan 4, 2013
    commit c7ac867 upstream.
    The message size allocated for rtnl ifinfo dumps was limited to
    a single page.  This is not enough for additional interface info
    available with devices that support SR-IOV and caused a bug in
    which VF info would not be displayed if more than approximately
    40 VFs were created per interface.
    Implement a new function pointer for the rtnl_register service that will
    calculate the amount of data required for the ifinfo dump and allocate
    enough data to satisfy the request.
    Signed-off-by: Greg Rose <>
    Signed-off-by: Jeff Kirsher <>
    Cc: Ben Hutchings <>
    Signed-off-by: Greg Kroah-Hartman <>
  31. @zhang-rui @gregkh

    ACPI : do not use Lid and Sleep button for S5 wakeup

    zhang-rui committed with gregkh Dec 4, 2012
    commit b7e3830 upstream.
    When system enters power off, the _PSW of Lid device is enabled.
    But this may cause the system to reboot instead of power off.
    A proper way to fix this is to always disable lid wakeup capability for S5.
    Signed-off-by: Zhang Rui <>
    Signed-off-by: Rafael J. Wysocki <>
    Cc: Joseph Salisbury <>
    Signed-off-by: Greg Kroah-Hartman <>
  32. @aprzywar @gregkh

    x86, amd: Disable way access filter on Piledriver CPUs

    aprzywar committed with gregkh Oct 31, 2012
    commit 2bbf0a1 upstream.
    The Way Access Filter in recent AMD CPUs may hurt the performance of
    some workloads, caused by aliasing issues in the L1 cache.
    This patch disables it on the affected CPUs.
    The issue is similar to that one of last year:
    This new patch does not replace the old one, we just need another
    quirk for newer CPUs.
    The performance penalty without the patch depends on the
    circumstances, but is a bit less than the last year's 3%.
    The workloads affected would be those that access code from the same
    physical page under different virtual addresses, so different
    processes using the same libraries with ASLR or multiple instances of
    PIE-binaries. The code needs to be accessed simultaneously from both
    cores of the same compute unit.
    More details can be found here:
    CPUs affected are anything with the core known as Piledriver.
    That includes the new parts of the AMD A-Series (aka Trinity) and the
    just released new CPUs of the FX-Series (aka Vishera).
    The model numbering is a bit odd here: FX CPUs have model 2,
    A-Series has model 10h, with possible extensions to 1Fh. Hence the
    range of model ids.
    Signed-off-by: Andre Przywara <>
    Signed-off-by: H. Peter Anvin <>
    Signed-off-by: CAI Qian <>
    Signed-off-by: Greg Kroah-Hartman <>
  33. @gregkh

    thp, memcg: split hugepage for memcg oom on cow

    David Rientjes committed with gregkh May 29, 2012
    commit 1f1d06c upstream.
    On COW, a new hugepage is allocated and charged to the memcg.  If the
    system is oom or the charge to the memcg fails, however, the fault
    handler will return VM_FAULT_OOM which results in an oom kill.
    Instead, it's possible to fallback to splitting the hugepage so that the
    COW results only in an order-0 page being allocated and charged to the
    memcg which has a higher liklihood to succeed.  This is expensive
    because the hugepage must be split in the page fault handler, but it is
    much better than unnecessarily oom killing a process.
    Signed-off-by: David Rientjes <>
    Cc: Andrea Arcangeli <>
    Cc: Johannes Weiner <>
    Acked-by: KAMEZAWA Hiroyuki <>
    Cc: Michal Hocko <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  34. @namjaejeon @gregkh

    udf: don't increment lenExtents while writing to a hole

    namjaejeon committed with gregkh Oct 10, 2012
    commit fb719c5 upstream.
    Incrementing lenExtents even while writing to a hole is bad
    for performance as calls to udf_discard_prealloc and
    udf_truncate_tail_extent would not return from start if
    isize != lenExtents
    Signed-off-by: Namjae Jeon <>
    Signed-off-by: Ashish Sangwan <>
    Signed-off-by: Jan Kara <>
    Signed-off-by: Shuah Khan <>
    Signed-off-by: Greg Kroah-Hartman <>
  35. @namjaejeon @gregkh

    udf: fix memory leak while allocating blocks during write

    namjaejeon committed with gregkh Oct 10, 2012
    commit 2fb7d99 upstream.
    Need to brelse the buffer_head stored in cur_epos and next_epos.
    Signed-off-by: Namjae Jeon <>
    Signed-off-by: Ashish Sangwan <>
    Signed-off-by: Jan Kara <>
    Signed-off-by: Shuah Khan <>
    Signed-off-by: Greg Kroah-Hartman <>
Something went wrong with that request. Please try again.