Eric Lee / smarc-fsl-linux-kernel

21 May, 2011

8 commits

17 May, 2011

7 commits

  • c1d10d18c   Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6 ... Browse Code »

    * git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6:
    net: Change netdev_fix_features messages loglevel
    vmxnet3: Fix inconsistent LRO state after initialization
    sfc: Fix oops in register dump after mapping change
    IPVS: fix netns if reading ip_vs_* procfs entries
    bridge: fix forwarding of IPv6

    Linus Torvalds
     
  • 477de0de4   Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc ... Browse Code »

    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc:
    Revert "mmc: fix a race between card-detect rescan and clock-gate work instances"

    Linus Torvalds
     
  • b5e6ab589   mm: fix kernel-doc warning in page_alloc.c ... Browse Code »

    Fix new kernel-doc warning in mm/page_alloc.c:

    Warning(mm/page_alloc.c:2370): No description found for parameter 'nid'

    Signed-off-by: Randy Dunlap
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     
  • 93d2175d3   PCI: Clear bridge resource flags if requested size is 0 ... Browse Code »

    During pci remove/rescan testing found:

    pci 0000:c0:03.0: PCI bridge to [bus c4-c9]
    pci 0000:c0:03.0: bridge window [io 0x1000-0x0fff]
    pci 0000:c0:03.0: bridge window [mem 0xf0000000-0xf00fffff]
    pci 0000:c0:03.0: bridge window [mem 0xfc180000000-0xfc197ffffff 64bit pref]
    pci 0000:c0:03.0: device not available (can't reserve [io 0x1000-0x0fff])
    pci 0000:c0:03.0: Error enabling bridge (-22), continuing
    pci 0000:c0:03.0: enabling bus mastering
    pci 0000:c0:03.0: setting latency timer to 64
    pcieport 0000:c0:03.0: device not available (can't reserve [io 0x1000-0x0fff])
    pcieport: probe of 0000:c0:03.0 failed with error -22

    This bug was caused by commit c8adf9a3e873 ("PCI: pre-allocate
    additional resources to devices only after successful allocation of
    essential resources.")

    After that commit, pci_hotplug_io_size is changed to additional_io_size
    from minium size. So it will not go through resource_size(res) != 0
    path, and will not be reset.

    The root cause is: pci_bridge_check_ranges will set RESOURCE_IO flag for
    pci bridge, and later if children do not need IO resource. those bridge
    resources will not need to be allocated. but flags is still there.
    that will confuse the the pci_enable_bridges later.

    related code:

    static void assign_requested_resources_sorted(struct resource_list *head,
    struct resource_list_x *fail_head)
    {
    struct resource *res;
    struct resource_list *list;
    int idx;

    for (list = head->next; list; list = list->next) {
    res = list->res;
    idx = res - &list->dev->resource[0];
    if (resource_size(res) && pci_assign_resource(list->dev, idx)) {
    ...
    reset_resource(res);
    }
    }
    }

    At last, We have to clear the flags in pbus_size_mem/io when requested
    size == 0 and !add_head. becasue this case it will not go through
    adjust_resources_sorted().

    Just make size1 = size0 when !add_head. it will make flags get cleared.

    At the same time when requested size == 0, add_size != 0, will still
    have in head and add_list. because we do not clear the flags for it.

    After this, we will get right result:

    pci 0000:c0:03.0: PCI bridge to [bus c4-c9]
    pci 0000:c0:03.0: bridge window [io disabled]
    pci 0000:c0:03.0: bridge window [mem 0xf0000000-0xf00fffff]
    pci 0000:c0:03.0: bridge window [mem 0xfc180000000-0xfc197ffffff 64bit pref]
    pci 0000:c0:03.0: enabling bus mastering
    pci 0000:c0:03.0: setting latency timer to 64
    pcieport 0000:c0:03.0: setting latency timer to 64
    pcieport 0000:c0:03.0: irq 160 for MSI/MSI-X
    pcieport 0000:c0:03.0: Signaling PME through PCIe PME interrupt
    pci 0000:c4:00.0: Signaling PME through PCIe PME interrupt
    pcie_pme 0000:c0:03.0:pcie01: service driver pcie_pme loaded
    aer 0000:c0:03.0:pcie02: service driver aer loaded
    pciehp 0000:c0:03.0:pcie04: Hotplug Controller:

    v3: more simple fix. also fix one typo in pbus_size_mem

    Signed-off-by: Yinghai Lu
    Reviewed-by: Ram Pai
    Cc: Jesse Barnes
    Cc: Bjorn Helgaas
    Signed-off-by: Linus Torvalds

    Yinghai Lu
     
  • 6f404e441   net: Change netdev_fix_features messages loglevel ... Browse Code »

    Those reduced to DEBUG can possibly be triggered by unprivileged processes
    and are nothing exceptional. Illegal checksum combinations can only be
    caused by driver bug, so promote those messages to WARN.

    Since GSO without SG will now only cause DEBUG message from
    netdev_fix_features(), remove the workaround from register_netdevice().

    Signed-off-by: Michał Mirosław
    Signed-off-by: David S. Miller

    Michał Mirosław
     
  • ebde6f8ac   vmxnet3: Fix inconsistent LRO state after initialization ... Browse Code »

    During initialization of vmxnet3, the state of LRO
    gets out of sync with netdev->features.

    This leads to very poor TCP performance in a IP forwarding
    setup and is hitting many VMware users.

    Simplified call sequence:
    1. vmxnet3_declare_features() initializes "adapter->lro" to true.

    2. The kernel automatically disables LRO if IP forwarding is enabled,
    so vmxnet3_set_flags() gets called. This also updates netdev->features.

    3. Now vmxnet3_setup_driver_shared() is called. "adapter->lro" is still
    set to true and LRO gets enabled again, even though
    netdev->features shows it's disabled.

    Fix it by updating "adapter->lro", too.

    The private vmxnet3 adapter flags are scheduled for removal
    in net-next, see commit a0d2730c9571aeba793cb5d3009094ee1d8fda35
    "net: vmxnet3: convert to hw_features".

    Patch applies to 2.6.37 / 2.6.38 and 2.6.39-rc6.

    Please CC: comments.

    Signed-off-by: Thomas Jarosch
    Acked-by: Stephen Hemminger
    Signed-off-by: David S. Miller

    Thomas Jarosch
     
  • 867955f56   sfc: Fix oops in register dump after mapping change ... Browse Code »
    1

    Commit 747df2258b1b9a2e25929ef496262c339c380009 ('sfc: Always map MCDI
    shared memory as uncacheable') introduced a separate mapping for the
    MCDI shared memory (MC_TREG_SMEM). This means we can no longer easily
    include it in the register dump. Since it is not particularly useful
    in debugging, substitute a recognisable dummy value.

    Signed-off-by: Ben Hutchings
    Signed-off-by: David S. Miller

    Ben Hutchings
     

16 May, 2011

8 commits

  • df8d06ade   Merge branch 'omap-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel… ... Browse Code »

    …/git/tmlind/linux-omap-2.6

    * 'omap-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6:
    OMAP3: set the core dpll clk rate in its set_rate function
    omap: iommu: Return IRQ_HANDLED in fault handler when no fault occured

    Linus Torvalds
     
  • 7c21738ef   Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6 ... Browse Code »

    * 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6:
    drm: Take lock around probes for drm_fb_helper_hotplug_event
    drm/i915: Revert i915.semaphore=1 default from 47ae63e0
    vga_switcheroo: don't toggle-switch devices
    drm/radeon/kms: add some evergreen/ni safe regs
    drm/radeon/kms: fix extended lvds info parsing
    drm/radeon/kms: fix tiling reg on fusion

    Linus Torvalds
     
  • 86f315bbb   Revert "mmc: fix a race between card-detect rescan and clock-gate work instances" ... Browse Code »

    This reverts commit 26fc8775b51484d8c0a671198639c6d5ae60533e, which has
    been reported to cause boot/resume-time crashes for some users:

    https://bbs.archlinux.org/viewtopic.php?id=118751.

    Signed-off-by: Chris Ball
    Cc:

    Chris Ball
     
  • 752d2635e   drm: Take lock around probes for drm_fb_helper_hotplug_event ... Browse Code »

    We need to hold the dev->mode_config.mutex whilst detecting the output
    status. But we also need to drop it for the call into
    drm_fb_helper_single_fb_probe(), which indirectly acquires the lock when
    attaching the fbcon.

    Failure to do so exposes a race with normal output probing. Detected by
    adding some warnings that the mutex is held to the backend detect routines:

    [ 17.772456] WARNING: at drivers/gpu/drm/i915/intel_crt.c:471 intel_crt_detect+0x3e/0x373 [i915]()
    [ 17.772458] Hardware name: Latitude E6400
    [ 17.772460] Modules linked in: ....
    [ 17.772582] Pid: 11, comm: kworker/0:1 Tainted: G W 2.6.38.4-custom.2 #8
    [ 17.772584] Call Trace:
    [ 17.772591] [] ? warn_slowpath_common+0x78/0x8c
    [ 17.772603] [] ? intel_crt_detect+0x3e/0x373 [i915]
    [ 17.772612] [] ? drm_helper_probe_single_connector_modes+0xbf/0x2af [drm_kms_helper]
    [ 17.772619] [] ? drm_fb_helper_probe_connector_modes+0x39/0x4d [drm_kms_helper]
    [ 17.772625] [] ? drm_fb_helper_hotplug_event+0xa5/0xc3 [drm_kms_helper]
    [ 17.772633] [] ? output_poll_execute+0x146/0x17c [drm_kms_helper]
    [ 17.772638] [] ? cfq_init_queue+0x247/0x345
    [ 17.772644] [] ? output_poll_execute+0x0/0x17c [drm_kms_helper]
    [ 17.772648] [] ? process_one_work+0x193/0x28e
    [ 17.772652] [] ? worker_thread+0xef/0x172
    [ 17.772655] [] ? worker_thread+0x0/0x172
    [ 17.772658] [] ? worker_thread+0x0/0x172
    [ 17.772663] [] ? kthread+0x7a/0x82
    [ 17.772668] [] ? kernel_thread_helper+0x4/0x10
    [ 17.772671] [] ? kthread+0x0/0x82
    [ 17.772674] [] ? kernel_thread_helper+0x0/0x10

    Reported-by: Frederik Himpe
    References: https://bugs.freedesktop.org/show_bug.cgi?id=36394
    Signed-off-by: Chris Wilson
    Signed-off-by: Dave Airlie

    Chris Wilson
     
  • 8eea1be17   drm/i915: Revert i915.semaphore=1 default from 47ae63e0 ... Browse Code »

    My Q67 / i7-2600 box has rev09 Sandy Bridge graphics. It hangs
    instantly when GNOME loads and it hangs so hard the reset button
    doesn't work. Setting i915.semaphore=0 fixes it.

    Semaphores were disabled in a1656b9090f7008d2941c314f5a64724bea2ae37
    in 2.6.38 and were re-enabled by

    commit 47ae63e0c2e5fdb582d471dc906eb29be94c732f
    Merge: c59a333 467cffb
    Author: Chris Wilson
    Date: Mon Mar 7 12:32:44 2011 +0000

    Merge branch 'drm-intel-fixes' into drm-intel-next

    Apply the trivial conflicting regression fixes, but keep GPU semaphores
    enabled.

    Conflicts:
    drivers/gpu/drm/i915/i915_drv.h
    drivers/gpu/drm/i915/i915_gem_execbuffer.c

    (It's worth noting that the offending change is i915_drv.c,
    which is not a conflict.)

    Signed-off-by: Andy Lutomirski
    Acked-by: Keith Packard
    Signed-off-by: Dave Airlie

    Andy Lutomirski
     
  • a67b8887c   vga_switcheroo: don't toggle-switch devices ... Browse Code »

    If the requested device is already active, ignore the request.

    This restores the original behaviour of the interface. The change was
    probably an unintended side effect of

    commit 66b37c6777c4 vga_switcheroo: split switching into two stages

    which did not take into account to duplicate the !active check in the split-off
    stage2.

    Fix this by factoring that check out of stage1 into the debugfs_write routine.

    References: https://bugzilla.kernel.org/show_bug.cgi?id=34252
    Reported-by: Igor Murzov
    Tested-by: Igor Murzov
    Signed-off-by: Florian Mickler
    Signed-off-by: Dave Airlie

    Florian Mickler
     
  • 0e3d32c3a   Merge branch 'pablo/nf-2.6-updates' of git://1984.lsi.us.es/net-2.6 Browse Code »
    David S. Miller
     
  • eed631e0d   Merge git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable ... Browse Code »

    * git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable:
    Btrfs: fix FS_IOC_SETFLAGS ioctl
    Btrfs: fix FS_IOC_GETFLAGS ioctl
    fs: remove FS_COW_FL
    Btrfs: fix easily get into ENOSPC in mixed case
    Prevent oopsing in posix_acl_valid()

    Linus Torvalds
     

15 May, 2011

15 commits

  • 0f08190fe   IPVS: fix netns if reading ip_vs_* procfs entries ... Browse Code »

    Without this patch every access to ip_vs in procfs will increase
    the netns count i.e. an unbalanced get_net()/put_net().
    (ipvsadm commands also use procfs.)
    The result is you can't exit a netns if reading ip_vs_* procfs entries.

    Signed-off-by: Hans Schillstrom
    Signed-off-by: Pablo Neira Ayuso

    Hans Schillstrom
     
  • d8083deb4   bridge: fix forwarding of IPv6 ... Browse Code »

    The commit 6b1e960fdbd75dcd9bcc3ba5ff8898ff1ad30b6e
    bridge: Reset IPCB when entering IP stack on NF_FORWARD
    broke forwarding of IPV6 packets in bridge because it would
    call bp_parse_ip_options with an IPV6 packet.

    Reported-by: Noah Meyerhans
    Signed-off-by: Stephen Hemminger
    Reviewed-by: Eric Dumazet
    Signed-off-by: David S. Miller
    Signed-off-by: Pablo Neira Ayuso

    Stephen Hemminger
     
  • bd1a643e1   Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client ... Browse Code »

    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client:
    rbd: fix split bio handling
    rbd: fix leak of ops struct

    Linus Torvalds
     
  • ebcb904df   Btrfs: fix FS_IOC_SETFLAGS ioctl ... Browse Code »

    Steps to reproduce the bug:

    - Call FS_IOC_SETLFAGS ioctl with flags=FS_COMPR_FL
    - Call FS_IOC_SETFLAGS ioctl with flags=0
    - Call FS_IOC_GETFLAGS ioctl, and you'll see FS_COMPR_FL is still set!

    Signed-off-by: Li Zefan
    Signed-off-by: Chris Mason

    Li Zefan
     
  • d0092bdda   Btrfs: fix FS_IOC_GETFLAGS ioctl ... Browse Code »

    As we've added per file compression/cow support.

    Signed-off-by: Li Zefan
    Signed-off-by: Chris Mason

    Li Zefan
     
  • e1e8fb6a1   fs: remove FS_COW_FL ... Browse Code »

    FS_COW_FL and FS_NOCOW_FL were newly introduced to control per file
    COW in btrfs, but FS_NOCOW_FL is sufficient.

    The fact is we don't have corresponding BTRFS_INODE_COW flag.

    COW is default, and FS_NOCOW_FL can be used to switch off COW for
    a single file.

    If we mount btrfs with nodatacow, a newly created file will be set with
    the FS_NOCOW_FL flag. So to turn on COW for it, we can just clear the
    FS_NOCOW_FL flag.

    Signed-off-by: Li Zefan
    Signed-off-by: Chris Mason

    Li Zefan
     
  • 1aba86d67   Btrfs: fix easily get into ENOSPC in mixed case ... Browse Code »

    When a btrfs disk is created by mixed data & metadata option, it will have no
    pure data or pure metadata space info.

    In btrfs's for-linus branch, commit 78b1ea13838039cd88afdd62519b40b344d6c920
    (Btrfs: fix OOPS of empty filesystem after balance) initializes space infos at
    the very beginning. The problem is this initialization does not take the mixed
    case into account, which will cause btrfs will easily get into ENOSPC in mixed
    case.

    Signed-off-by: Liu Bo
    Signed-off-by: Chris Mason

    liubo
     
  • f5de93914   Prevent oopsing in posix_acl_valid() ... Browse Code »

    If posix_acl_from_xattr() returns an error code, a negative address is
    dereferenced causing an oops; fix by checking for error code first.

    Signed-off-by: Daniel J Blueman
    Reviewed-by: Josef Bacik
    Signed-off-by: Chris Mason

    Daniel J Blueman
     
  • 9f6bd36c4   Merge branch 'upstream-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev ... Browse Code »

    * 'upstream-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev:
    libata: fix oops when LPM is used with PMP

    Linus Torvalds
     
  • 05bf86b4c   tmpfs: fix race between swapoff and writepage ... Browse Code »

    Shame on me! Commit b1dea800ac39 "tmpfs: fix race between umount and
    writepage" fixed the advertized race, but introduced another: as even
    its comment makes clear, we cannot safely rely on a peek at list_empty()
    while holding no lock - until info->swapped is set, shmem_unuse_inode()
    may delete any formerly-swapped inode from the shmem_swaplist, which
    in this case would leave a swap area impossible to swapoff.

    Although I don't relish taking the mutex every time, I don't care much
    for the alternatives either; and at least the peek at list_empty() in
    shmem_evict_inode() (a hotter path since most inodes would never have
    been swapped) remains safe, because we already truncated the whole file.

    Signed-off-by: Hugh Dickins
    Cc: stable@kernel.org
    Signed-off-by: Linus Torvalds

    Hugh Dickins
     
  • 5f6f12ccf   libata: fix oops when LPM is used with PMP ... Browse Code »

    ae01b2493c (libata: Implement ATA_FLAG_NO_DIPM and apply it to mcp65)
    added ATA_FLAG_NO_DIPM and made ata_eh_set_lpm() check the flag.
    However, @ap is NULL if @link points to a PMP link and thus the
    unconditional @ap->flags dereference leads to the following oops.

    BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
    IP: [] ata_eh_recover+0x9a1/0x1510
    ...
    Pid: 295, comm: scsi_eh_4 Tainted: P 2.6.38.5-core2 #1 System76, Inc. Serval Professional/Serval Professional
    RIP: 0010:[] [] ata_eh_recover+0x9a1/0x1510
    RSP: 0018:ffff880132defbf0 EFLAGS: 00010246
    RAX: 0000000000000000 RBX: ffff880132f40000 RCX: 0000000000000000
    RDX: ffff88013377c000 RSI: ffff880132f40000 RDI: 0000000000000000
    RBP: ffff880132defce0 R08: ffff88013377dc58 R09: ffff880132defd98
    R10: 0000000000000000 R11: 00000000ffffffff R12: 0000000000000000
    R13: 0000000000000000 R14: ffff88013377c000 R15: 0000000000000000
    FS: 0000000000000000(0000) GS:ffff8800bf700000(0000) knlGS:0000000000000000
    CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    CR2: 0000000000000018 CR3: 0000000001a03000 CR4: 00000000000406e0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Process scsi_eh_4 (pid: 295, threadinfo ffff880132dee000, task ffff880133b416c0)
    Stack:
    0000000000000000 ffff880132defcc0 0000000000000000 ffff880132f42738
    ffffffff813ee8f0 ffffffff813eefe0 ffff880132defd98 ffff88013377f190
    ffffffffa00b3e30 ffffffff813ef030 0000000032defc60 ffff880100000000
    Call Trace:
    [] sata_pmp_error_handler+0x607/0xc30
    [] ahci_error_handler+0x1f/0x70 [libahci]
    [] ata_scsi_error+0x5be/0x900
    [] scsi_error_handler+0x124/0x650
    [] kthread+0x96/0xa0
    [] kernel_thread_helper+0x4/0x10
    Code: 8b 95 70 ff ff ff b8 00 00 00 00 48 3b 9a 10 2e 00 00 48 0f 44 c2 48 89 85 70 ff ff ff 48 8b 8d 70 ff ff ff f6 83 69 02 00 00 01 8b 41 18 0f 85 48 01 00 00 48 85 c9 74 12 48 8b 51 08 48 83
    RIP [] ata_eh_recover+0x9a1/0x1510
    RSP
    CR2: 0000000000000018

    Fix it by testing @link->ap->flags instead.

    stable: ATA_FLAG_NO_DIPM was added during 2.6.39 cycle but was
    backported to 2.6.37 and 38. This is a fix for that and thus
    also applicable to 2.6.37 and 38.

    Signed-off-by: Tejun Heo
    Reported-by: "Nathan A. Mourey II"
    LKML-Reference:
    Cc: Connor H
    Cc: stable@kernel.org
    Signed-off-by: Jeff Garzik

    Tejun Heo
     
  • afa49791c   Merge branch 'fbmem' ... Browse Code »

    * fbmem:
    Further fbcon sanity checking
    fbmem: fix remove_conflicting_framebuffers races

    Linus Torvalds
     
  • 22fe9446e   Revert "libata: ahci_start_engine compliant to AHCI spec" ... Browse Code »

    This reverts commit 270dac35c26433d06a89150c51e75ca0181ca7e4.

    The commits causes command timeouts on AC plug/unplug. It isn't yet
    clear why. As the commit was for a single rather obscure controller,
    revert the change for now.

    The problem was reported and bisected by Gu Rui in bug#34692.

    https://bugzilla.kernel.org/show_bug.cgi?id=34692

    Also, reported by Rafael and Michael in the following thread.

    http://thread.gmane.org/gmane.linux.kernel/1138771

    Signed-off-by: Tejun Heo
    Reported-by: Gu Rui
    Reported-by: Rafael J. Wysocki
    Reported-by: Michael Leun
    Cc: Jian Peng
    Cc: Jeff Garzik
    Signed-off-by: Linus Torvalds

    Tejun Heo
     
  • c590cece7   Further fbcon sanity checking ... Browse Code »

    This moves the

    if (num_registered_fb == FB_MAX)
    return -ENXIO;

    check _AFTER_ the call to do_remove_conflicting_framebuffers() as this
    would (now in a safe way) allow a native driver to replace the
    conflicting one even if all slots in registered_fb[] are taken.

    This also prevents unregistering a framebuffer that is no longer
    registered (vga16f will unregister at module unload time even if the
    frame buffer had been unregistered earlier due to being found
    conflicting).

    Signed-off-by: Bruno Prémont
    Signed-off-by: Linus Torvalds

    Bruno Prémont
     
  • 712f3147a   fbmem: fix remove_conflicting_framebuffers races ... Browse Code »

    When a register_framebuffer() call results in us removing old
    conflicting framebuffers, the new registration_lock doesn't protect that
    situation. And we can't just add the same locking to the function,
    because these functions call each other: register_framebuffer() calls
    remove_conflicting_framebuffers, which in turn calls
    unregister_framebuffer for any conflicting entry.

    In order to fix it, this just creates wrapper functions around all three
    functions and makes the versions that actually do the work be called
    "do_xxx()", leaving just the wrapper that gets the lock and calls the
    worker function.

    So the rule becomes simply that "do_xxxx()" has to be called with the
    lock held, and now do_register_framebuffer() can just call
    do_remove_conflicting_framebuffers(), and that in turn can call
    _do_unregister_framebuffer(), and there is no deadlock, and we can hold
    the registration lock over the whole sequence, fixing the races.

    It also makes error cases simpler, and fixes one situation where we
    would return from unregister_framebuffer() without releasing the lock,
    pointed out by Bruno Prémont.

    Tested-by: Bruno Prémont
    Tested-by: Anca Emanuel
    Signed-off-by: Linus Torvalds

    Linus Torvalds
     

14 May, 2011

2 commits