Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Jul 24, 2009
  1. @gregkh


    gregkh authored
  2. @torvalds @gregkh

    fbmon: work around compiler bug in gcc-4.2.4

    torvalds authored gregkh committed
    commit 3730793 upstream.
    There's some odd bug in gcc-4.2 where it miscompiles a simple loop whent
    he loop counter is of type 'unsigned char' and it should count to 128.
    The compiler will incorrectly decide that a trivial loop like this:
    	unsigned char i, ...
    	for (i = 0; i < 128; i++) {
    is endless, and will compile it to a single instruction that just
    branches to itself.
    This was triggered by the addition of '-fno-strict-overflow', and we
    could play games with compiler versions and go back to '-fwrapv'
    instead, but the trivial way to avoid it is to just make the loop
    induction variable be an 'int' instead.
    Thanks to Krzysztof Oledzki for reporting and testing and to Troy Moure
    for digging through assembler differences and finding it.
    Reported-and-tested-by: Krzysztof Oledzki <>
    Found-by: Troy Moure <>
    Gcc-bug-acked-by: Ian Lance Taylor <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
Commits on Jul 20, 2009
  1. @gregkh


    gregkh authored
  2. @torvalds @gregkh

    Don't use '-fwrapv' compiler option: it's buggy in gcc-4.1.x

    torvalds authored gregkh committed
    commit a137802 upstream.
    This causes kernel images that don't run init to completion with certain
    broken gcc versions.
    This fixes kernel bugzilla entry:
    I suspect the gcc problem is this:
    Fix the problem by using the -fno-strict-overflow flag instead, which
    not only does not exist in the known-to-be-broken versions of gcc (it
    was introduced later than fwrapv), but seems to be much less disturbing
    to gcc too: the difference in the generated code by -fno-strict-overflow
    are smaller (compared to using neither flag) than when using -fwrapv.
    Reported-by: Barry K. Nathan <>
    Pushed-by: Frans Pop <>
    Cc: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  3. @gregkh

    tulip: Fix for MTU problems with 802.1q tagged frames

    Tomasz Lemiech authored gregkh committed
    commit 1f8ae0a upstream.
    The original patch was submitted last year but wasn't discussed or applied
    because of missing maintainer's CCs. I only fixed some formatting errors,
    but as I saw tulip is very badly formatted and needs further work.
    Original description:
    This patch fixes MTU problem, which occurs when using 802.1q VLANs. We
    should allow receiving frames of up to 1518 bytes in length, instead of
    Based on patch written by Ben McKeegan for 2.4.x kernels. It is archived
    I've adjusted a few things to make it apply on 2.6.x kernels.
    Tested on D-Link DFE-570TX quad-fastethernet card.
    Signed-off-by: Tomasz Lemiech <>
    Signed-off-by: Ivan Vecera <>
    Signed-off-by: Ben McKeegan <>
    Acked-by: Grant Grundler <>
    Cc: Christoph Biedl <>
    Signed-off-by: David S. Miller <>
  4. @zhang-rui @gregkh

    kernel/resource.c: fix sign extension in reserve_setup()

    zhang-rui authored gregkh committed
    commit 8bc1ad7 upstream.
    When the 32-bit signed quantities get assigned to the u64 resource_size_t,
    they are incorrectly sign-extended.
    Signed-off-by: Zhang Rui <>
    Reported-by: Leann Ogasawara <>
    Cc: Pierre Ossman <>
    Reported-by: <>
    Tested-by: <>
    Cc: Jesse Barnes <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  5. @jirislaby @gregkh

    floppy: fix lock imbalance

    jirislaby authored gregkh committed
    commit 8516a50 upstream.
    A crappy macro prevents us unlocking on a fail path.
    Expand the macro and unlock appropriatelly.
    Signed-off-by: Jiri Slaby <>
    Cc: Jens Axboe <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  6. @dwmw2 @gregkh

    Fix iommu address space allocation

    dwmw2 authored gregkh committed
    commit a15a519 upstream.
    This fixes bug #13584. The IOVA code attempted to optimise
    the insertion of new ranges into the rbtree, with the unfortunate result
    that some ranges just didn't get inserted into the tree at all. Then
    those ranges would be handed out more than once, and things kind of go
    downhill from there.
    Introduced after 2.6.25 by ddf0288
    ("PCI: iova RB tree setup tweak").
    Signed-off-by: David Woodhouse <>
    Cc: mark gross <>
    Cc: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  7. @gregkh

    security: use mmap_min_addr indepedently of security models

    Christoph Lameter authored gregkh committed
    commit e0a94c2 upstream.
    This patch removes the dependency of mmap_min_addr on CONFIG_SECURITY.
    It also sets a default mmap_min_addr of 4096.
    mmapping of addresses below 4096 will only be possible for processes
    with CAP_SYS_RAWIO.
    Signed-off-by: Christoph Lameter <>
    Acked-by: Eric Paris <>
    Looks-ok-by: Linus Torvalds <>
    Signed-off-by: James Morris <>
    Signed-off-by: Greg Kroah-Hartman <>
  8. @gregkh

    personality: fix PER_CLEAR_ON_SETID (CVE-2009-1895)

    Julien Tinnes authored gregkh committed
    commit f9fabcb upstream.
    We have found that the current PER_CLEAR_ON_SETID mask on Linux doesn't
    include neither ADDR_COMPAT_LAYOUT, nor MMAP_PAGE_ZERO.
    We believe it is important to add MMAP_PAGE_ZERO, because by using this
    personality it is possible to have the first page mapped inside a
    process running as setuid root.  This could be used in those scenarios:
     - Exploiting a NULL pointer dereference issue in a setuid root binary
     - Bypassing the mmap_min_addr restrictions of the Linux kernel: by
       running a setuid binary that would drop privileges before giving us
       control back (for instance by loading a user-supplied library), we
       could get the first page mapped in a process we control.  By further
       using mremap and mprotect on this mapping, we can then completely
       bypass the mmap_min_addr restrictions.
    Less importantly, we believe ADDR_COMPAT_LAYOUT should also be added
    since on x86 32bits it will in practice disable most of the address
    space layout randomization (only the stack will remain randomized).
    Signed-off-by: Julien Tinnes <>
    Signed-off-by: Tavis Ormandy <>
    Acked-by: Christoph Hellwig <>
    Acked-by: Kees Cook <>
    Acked-by: Eugene Teo <>
    [ Shortened lines and fixed whitespace as per Christophs' suggestion ]
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  9. @gregkh

    Add '-fno-delete-null-pointer-checks' to gcc CFLAGS

    Eugene Teo authored gregkh committed
    commit a3ca86a upstream.
    Turning on this flag could prevent the compiler from optimising away
    some "useless" checks for null pointers.  Such bugs can sometimes become
    exploitable at compile time because of the -O2 optimisation.
    An example that clearly shows this 'problem' is commit 6bf6767.
     static void __devexit agnx_pci_remove(struct pci_dev *pdev)
         struct ieee80211_hw *dev = pci_get_drvdata(pdev);
    -    struct agnx_priv *priv = dev->priv;
    +    struct agnx_priv *priv;
         if (!dev)
    +    priv = dev->priv;
    By reverting this patch, and compile it with and without
    -fno-delete-null-pointer-checks flag, we can see that the check for dev
    is compiled away.
        call    printk  #
    -   testq   %r12, %r12  # dev
    -   je  .L94    #,
        movq    %r12, %rdi  # dev,
    Clearly the 'fix' is to stop using dev before it is tested, but building
    with -fno-delete-null-pointer-checks flag at least makes it harder to
    Signed-off-by: Eugene Teo <>
    Acked-by: Eric Paris <>
    Acked-by: Wang Cong <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  10. @gregkh

    Revert "dm: sysfs skip output when device is being destroyed"

    gregkh authored
    This reverts commit 9fad9f2.
    It is really commit 4d89b7b that is
    being reverted here, it's a patch that should not have been applied to
    the .27 tree.
    Signed-off-by: Greg Kroah-Hartman <>
Commits on Jul 2, 2009
  1. @gregkh


    gregkh authored
  2. @gregkh

    kbuild: fix C libary confusion in unifdef.c due to getline()

    Justin P. Mattock authored gregkh committed
    commit d15bd10 upstream.
    This fixes an error when compiling the kernel.
      CHK     include/linux/version.h
      HOSTCC  scripts/unifdef
    scripts/unifdef.c:209: error: conflicting types for 'getline'
    /usr/include/stdio.h:651: note: previous declaration of 'getline' was here
    make[1]: *** [scripts/unifdef] Error 1
    make: *** [__headers] Error 2
    Signed-off-by: Justin P. Mattock <>
    Cc:  Frederic Weisbecker <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Sam Ravnborg <>
    Cc: Gilles Espinasse <>
    Signed-off-by: Greg Kroah-Hartman <>
  3. @gregkh

    bsdacct: fix access to invalid filp in acct_on()

    Renaud Lottiaux authored gregkh committed
    commit df279ca upstream.
    The file opened in acct_on and freshly stored in the ns->bacct struct can
    be closed in acct_file_reopen by a concurrent call after we release
    acct_lock and before we call mntput(file->f_path.mnt).
    Record file->f_path.mnt in a local variable and use this variable only.
    Signed-off-by: Renaud Lottiaux <>
    Signed-off-by: Louis Rilling <>
    Cc: Al Viro <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  4. @gregkh

    dm: sysfs skip output when device is being destroyed

    Milan Broz authored gregkh committed
    commit 4d89b7b upstream.
    Do not process sysfs attributes when device is being destroyed.
    Otherwise code can cause
      BUG_ON(test_bit(DMF_FREEING, &md->flags));
    in dm_put() call.
    Signed-off-by: Milan Broz <>
    Signed-off-by: Alasdair G Kergon <>
    Signed-off-by: Greg Kroah-Hartman <>
  5. @gregkh

    dm mpath: validate table argument count

    Mikulas Patocka authored gregkh committed
    commit 0e0497c upstream.
    The parser reads the argument count as a number but doesn't check that
    sufficient arguments are supplied. This command triggers the bug:
    dmsetup create mpath --table "0 `blockdev --getsize /dev/mapper/cr0`
        multipath 0 0 2 1 round-robin 1000 0 1 1 /dev/mapper/cr0
        round-robin 0 1 1 /dev/mapper/cr1 1000"
    kernel BUG at drivers/md/dm-mpath.c:530!
    Signed-off-by: Mikulas Patocka <>
    Signed-off-by: Alasdair G Kergon <>
    Signed-off-by: Greg Kroah-Hartman <>
  6. @gregkh

    dm mpath: validate hw_handler argument count

    Mikulas Patocka authored gregkh committed
    commit e094f4f upstream.
    Fix arg count parsing error in hw handlers.
    Signed-off-by: Mikulas Patocka <>
    Signed-off-by: Alasdair G Kergon <>
    Signed-off-by: Greg Kroah-Hartman <>
  7. @gregkh

    mm: fix handling of pagesets for downed cpus

    Dimitri Sivanich authored gregkh committed
    commit 364df0e upstream.
    After downing/upping a cpu, an attempt to set
    /proc/sys/vm/percpu_pagelist_fraction results in an oops in
    If a processor is downed then we need to set the pageset pointer back to
    the boot pageset.
    Updates of the high water marks should not access pagesets of unpopulated
    zones (those pointer go to the boot pagesets which would be no longer
    functional if their size would be increased beyond zero).
    Signed-off-by: Dimitri Sivanich <>
    Signed-off-by: Christoph Lameter <>
    Reviewed-by: KOSAKI Motohiro <>
    Cc: Nick Piggin <>
    Cc: Mel Gorman <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  8. @cladisch @gregkh

    sound: seq_midi_event: fix decoding of (N)RPN events

    cladisch authored gregkh committed
    commit 6423f9e upstream.
    When decoding (N)RPN sequencer events into raw MIDI commands, the
    extra_decode_xrpn() function had accidentally swapped the MSB and LSB
    controller values of both the parameter number and the data value.
    Signed-off-by: Clemens Ladisch <>
    Signed-off-by: Takashi Iwai <>
    Signed-off-by: Greg Kroah-Hartman <>
  9. @jirislaby @gregkh

    pcmcia/cm4000: fix lock imbalance

    jirislaby authored gregkh committed
    commit 69ae59d upstream.
    Don't return from switch/case, break instead, so that we unlock BKL.
    Signed-off-by: Jiri Slaby <>
    Signed-off-by: Alan Cox <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  10. @rjwysocki @gregkh

    PCI PM: Follow PCI_PM_CTRL_NO_SOFT_RESET during transitions from D3

    rjwysocki authored gregkh committed
    commit f62795f upstream.
    According to the PCI PM specification (PCI Bus Power Management
    Interface Specification, Rev. 1.2, Section 5.4.1) we are supposed to
    reinitialize devices that have PCI_PM_CTRL_NO_SOFT_RESET clear during
    all transitions from PCI_D3hot to PCI_D0, but we only do it if the
    device's current_state field is equal to PCI_UNKNOWN.
    This may lead to problems if a device with PCI_PM_CTRL_NO_SOFT_RESET
    unset is put into PCI_D3hot at run time by its driver and
    pci_set_power_state() is used to put it back into PCI_D0, because in
    that case the device will remain uninitialized after
    pci_set_power_state() has returned.  Prevent that from happening by
    modifying pci_raw_set_power_state() to reinitialize devices with
    PCI_PM_CTRL_NO_SOFT_RESET unset during all transitions from D3 to D0.
    Signed-off-by: Rafael J. Wysocki <>
    Signed-off-by: Jesse Barnes <>
    Signed-off-by: Greg Kroah-Hartman <>
  11. @rjwysocki @gregkh

    PCI PM: Fix handling of devices without PM support by pci_target_state()

    rjwysocki authored gregkh committed
    commit d2abdf6 upstream.
    If a PCI device is not power-manageable either by the platform, or
    with the help of the native PCI PM interface, pci_target_state() will
    return either PCI_D3hot, or PCI_POWER_ERROR for it, depending on
    whether or not the device is configured to wake up the system.  Alas,
    none of these return values is correct, because each of them causes
    pci_prepare_to_sleep() to return error code, although it should
    complete successfully in such a case.
    Fix this problem by making pci_target_state() always return PCI_D0
    for devices that cannot be power managed.
    Signed-off-by: Rafael J. Wysocki <>
    Signed-off-by: Jesse Barnes <>
    Signed-off-by: Greg Kroah-Hartman <>
  12. @fujita @gregkh

    parport_pc: set properly the dma_mask for parport_pc device

    fujita authored gregkh committed
    commit dfa7c4d upstream.
    parport_pc_probe_port() creates the own 'parport_pc' device if the
    device argument is NULL. Then parport_pc_probe_port() doesn't
    initialize the dma_mask and coherent_dma_mask of the device and calls
    dma_alloc_coherent with it. dma_alloc_coherent fails because
    dma_alloc_coherent() doesn't accept the uninitialized dma_mask:
    Long ago, X86_32 and X86_64 had the own dma_alloc_coherent
    implementations; X86_32 accepted a device having dma_mask that is not
    initialized however X86_64 didn't. When we merged them, we chose to
    prohibit a device having dma_mask that is not initialized. I think
    that it's good to require drivers to set up dma_mask (and
    coherent_dma_mask) properly if the drivers want DMA.
    Signed-off-by: FUJITA Tomonori <>
    Reported-by: Malcom Blaney <>
    Tested-by: Malcom Blaney <>
    Signed-off-by: Alan Cox <>
    Acked-by: Jeff Garzik <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  13. @gregkh

    parport_pc: after superio probing restore original register values

    Jens Rottmann authored gregkh committed
    commit e2434dc upstream.
    CONFIG_PARPORT_PC_SUPERIO probes for various superio chips by writing
    byte sequences to a set of different potential I/O ranges.  But the
    probed ranges are not exclusive to parallel ports.  Some of our boards
    just happen to have a watchdog in one of them.  Took us almost a week
    to figure out why some distros reboot without warning after running
    flawlessly for 3 hours.  For exactly 170 = 0xAA minutes, that is ...
    Fixed by restoring original values after probing.  Also fixed too small
    request_region() in detect_and_report_it87().
    Signed-off-by: Jens Rottmann <>
    Signed-off-by: Alan Cox <>
    Acked-by: Jeff Garzik <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  14. @gregkh

    tcp: advertise MSS requested by user

    Tom Quetchenbach authored gregkh committed
    commit f5fff5d upstream.
    I'm trying to use the TCP_MAXSEG option to setsockopt() to set the MSS
    for both sides of a bidirectional connection.
    man tcp says: "If this option is set before connection establishment, it
    also changes the MSS value announced to the other end in the initial
    However, the kernel only uses the MTU/route cache to set the advertised
    MSS. That means if I set the MSS to, say, 500 before calling connect(),
    I will send at most 500-byte packets, but I will still receive 1500-byte
    packets in reply.
    This is a bug, either in the kernel or the documentation.
    This patch (applies to latest net-2.6) reduces the advertised value to
    that requested by the user as long as setsockopt() is called before
    connect() or accept(). This seems like the behavior that one would
    expect as well as that which is documented.
    I've tried to make sure that things that depend on the advertised MSS
    are set correctly.
    Signed-off-by: Tom Quetchenbach <>
    Signed-off-by: David S. Miller <>
    Cc: Willy Tarreau <>
    Signed-off-by: Greg Kroah-Hartman <>
  15. @djbw @gregkh

    md/raid5: add missing call to schedule() after prepare_to_wait()

    djbw authored gregkh committed
    commit 7a3ab90 upstream.
    In the unlikely event that reshape progresses past the current request
    while it is waiting for a stripe we need to schedule() before retrying
    for 2 reasons:
    1/ Prevent list corruption from duplicated list_add() calls without
       intervening list_del().
    2/ Give the reshape code a chance to make some progress to resolve the
    Signed-off-by: Dan Williams <>
    Signed-off-by: NeilBrown <>
    Signed-off-by: Greg Kroah-Hartman <>
  16. @gregkh

    lockdep: Select frame pointers on x86

    Peter Zijlstra authored gregkh committed
    commit 00540e5 upstream.
    x86 stack traces are a piece of crap without frame pointers, and its not
    like the 'performance gain' of not having stack pointers matters when you
    selected lockdep.
    Reported-by: Andrew Morton <>
    LKML-Reference: <new-submission>
    Signed-off-by: Peter Zijlstra <>
    Signed-off-by: Ingo Molnar <>
    Signed-off-by: Greg Kroah-Hartman <>
  17. @gregkh

    x86: handle initrd that extends into unusable memory

    Yinghai Lu authored gregkh committed
    commit 8c5dd8f upstream.
    On a system where system memory (according e820) is not covered by
    mtrr, mtrr_trim_memory converts a portion of memory to reserved, but
    bootloader has already put the initrd in that range.
    Thus, we need to have 64bit to use relocate_initrd too.
    [ Impact: fix using initrd when mtrr_trim_memory happen ]
    Signed-off-by: Yinghai Lu <>
    Signed-off-by: H. Peter Anvin <>
    Signed-off-by: Greg Kroah-Hartman <>
  18. @gregkh

    IB/mlx4: Add strong ordering to local inval and fast reg work requests

    Jack Morgenstein authored gregkh committed
    commit 2ac6bf4 upstream.
    The ConnectX Programmer's Reference Manual states that the "SO" bit
    must be set when posting Fast Register and Local Invalidate send work
    requests.  When this bit is set, the work request will be executed
    only after all previous work requests on the send queue have been
    executed.  (If the bit is not set, Fast Register and Local Invalidate
    WQEs may begin execution too early, which violates the defined
    semantics for these operations)
    This fixes the issue with NFS/RDMA reported in
    Signed-off-by: Jack Morgenstein <>
    Signed-off-by: Roland Dreier <>
    Signed-off-by: Greg Kroah-Hartman <>
  19. @phdm @gregkh

    floppy: request and release only the ports we actually use

    phdm authored gregkh committed
    commit 5a74db0 upstream.
    The floppy driver requests an I/O port it doesn't need, and sometimes this
    causes a conflict with a motherboard device reported by PNPBIOS.
    This patch makes the floppy driver request and release only the ports it
    actually uses.  It also factors out the request/release stuff and the
    io-ports list so they're all in one place now.
    The current floppy driver uses only these ports:
        0x3f2 (FD_DOR)
        0x3f4 (FD_STATUS)
        0x3f5 (FD_DATA)
        0x3f7 (FD_DCR/FD_DIR)
    but it requests 0x3f2-0x3f5 and 0x3f7, which includes the unused port
    Some BIOSes report 0x3f3 as a motherboard resource.  The PNP system driver
    reserves that, which causes a conflict when the floppy driver requests
    0x3f2-0x3f5 later.
    Philippe reported that this conflict broke the floppy driver between
    2.6.11 and 2.6.22.  His PNPBIOS reports these devices:
        $ cat 00:07/id 00:07/resources	# motherboard device
        state = active
        io 0x80-0x80
        io 0x10-0x1f
        io 0x22-0x3f
        io 0x44-0x5f
        io 0x90-0x9f
        io 0xa2-0xbf
        io 0x3f0-0x3f1
        io 0x3f3-0x3f3
        $ cat 00:03/id 00:03/resources	# floppy device
        state = active
        io 0x3f4-0x3f5
        io 0x3f2-0x3f2
    Signed-off-by: Bjorn Helgaas <>
    Signed-off-by: Philippe De Muyter <>
    Reported-by: Philippe De Muyter <>
    Tested-by: Philippe De Muyter <>
    Cc: Adam M Belay <>
    Cc: Robert Hancock <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  20. @gregkh

    floppy: provide a PNP device table in the module.

    Scott James Remnant authored gregkh committed
    commit 83f9ef4 upstream.
    The missing device table means that the floppy module is not auto-loaded,
    even when the appropriate PNP device (0700) is found.
    We don't actually use the table in the module, since the device doesn't
    have a struct pnp_driver, but it's sufficient to cause an alias in the
    module that udev/modprobe will use.
    Signed-off-by: Scott James Remnant <>
    Signed-off-by: Tim Gardner <>
    Cc: Bjorn Helgaas <>
    Cc: Philippe De Muyter <>
    Acked-by: Kay Sievers <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  21. @tiwai @gregkh

    ALSA: ca0106 - Add missing registrations of vmaster controls

    tiwai authored gregkh committed
    commit 601e1cc upstream.
    Although the vmaster controls are created, they aren't registered thus
    they don't appear in the real world.  Added the missing snd_ctl_add()
    Signed-off-by: Takashi Iwai <>
    Signed-off-by: Greg Kroah-Hartman <>
  22. @gregkh

    x86: quirk for reboot stalls on a Dell Optiplex 330

    Steve Conklin authored gregkh committed
    commit 093bac1 upstream.
    Dell Optiplex 330 appears to hang on reboot. This is resolved by adding
    a quirk to set bios reboot.
    Signed-off-by: Leann Ogasawara <>
    Signed-off-by: Steve Conklin <>
    Signed-off-by: Ingo Molnar <>
    Cc: Jean Delvare <>
    Signed-off-by: Greg Kroah-Hartman <>
  23. @jdelvare @gregkh

    x86: Add quirk for reboot stalls on a Dell Optiplex 360

    jdelvare authored gregkh committed
    commit 4a4aca6 upstream.
    The Dell Optiplex 360 hangs on reboot, just like the Optiplex 330, so
    the same quirk is needed.
    Signed-off-by: Jean Delvare <>
    Cc: Steve Conklin <>
    Cc: Leann Ogasawara <>
    LKML-Reference: <>
    Signed-off-by: Ingo Molnar <>
    Signed-off-by: Greg Kroah-Hartman <>
Something went wrong with that request. Please try again.