Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: v2.6.33-rc6-gi…
Commits on Feb 5, 2010
  1. @torvalds

    Merge master.kernel.org:/home/rmk/linux-2.6-arm

    torvalds authored
    * master.kernel.org:/home/rmk/linux-2.6-arm:
      ARM: Fix wrong register in proc-arm6_7.S data abort handler
      ARM: 5909/1: ARM: Correct the FPSCR bits setting when raising exceptions
      ARM: 5904/1: ARM: Always generate the IT instruction when compiling for Thumb-2
      ARM: 5907/1: ARM: Fix the reset on the RealView PBX Development board
      mx35: add a missing comma in a pad definition
      mx25: make the FEC AHB clk secondary of the IPG
      mx25: fix time accounting
      mx25: properly initialize clocks
      mx25: remove unused mx25_clocks_init() argument
      i.MX25: implement secondary clocks for uarts and fec
      i.MX25: Allow secondary clocks in DEFINE_CLOCK
      ARM: MX3: Fixed typo in declared enum type name.
      MXC: Add AUDMUXv2 register decode to debugfs
      mx31ads: Provide an IRQ range to the WM835x on the 1133-EV1 module
      mx31ads: Provide a name for EXPIO interrupt chip
      mx31ads: Allow enable/disable of switchable supplies
  2. @torvalds

    Merge branch 'omap-fixes-for-linus' of git://git.kernel.org/pub/scm/l…

    torvalds authored
    …inux/kernel/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:
      omap: Disable serial port autoidle by default
      omap: Fix access to already released memory in clk_debugfs_register_one()
      omap: Fix arch/arm/mach-omap2/mux.c: Off by one error
      omap: Fix 3630 mux errors
      OMAP2/3: GPMC: ensure valid clock pointer
      OMAP2/3: IRQ: ensure valid base address
      ARCH OMAP : enable ARCH_HAS_HOLES_MEMORYMODEL for OMAP
      omap: Remove old unused defines for OMAP_32KSYNCT_BASE
      omap: define _toggle_gpio_edge_triggering only for OMAP1
  3. @torvalds

    Merge branch 'bugfixes' of git://git.linux-nfs.org/projects/trondmy/n…

    torvalds authored
    …fs-2.6
    
    * 'bugfixes' of git://git.linux-nfs.org/projects/trondmy/nfs-2.6:
      NFS: Don't clobber the attribute type in nfs_update_inode()
      NFS: Fix a umount race
      NFS: Fix an Oops when truncating a file
      NFS: Ensure that we handle NFS4ERR_STALE_STATEID correctly
      NFSv4.1: Don't call nfs4_schedule_state_recovery() unnecessarily
      NFSv4: Don't allow posix locking against servers that don't support it
      NFSv4: Ensure that the NFSv4 locking can recover from stateid errors
      NFS: Avoid warnings when CONFIG_NFS_V4=n
      NFS: Make nfs_commitdata_release static
      NFS: Try to commit unstable writes in nfs_release_page()
      NFS: Fix a reference leak in nfs_wb_cancel_page()
  4. @torvalds

    Merge branch 'core-fixes-for-linus' of git://git.kernel.org/pub/scm/l…

    torvalds authored
    …inux/kernel/git/tip/linux-2.6-tip
    
    * 'core-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
      futex: Handle futex value corruption gracefully
      futex: Handle user space corruption gracefully
      futex_lock_pi() key refcnt fix
      softlockup: Add sched_clock_tick() to avoid kernel warning on kgdb resume
  5. @torvalds

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-fixes

    torvalds authored
    * git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-fixes:
      GFS2: Extend umount wait coverage to full glock lifetime
      GFS2: Wait for unlock completion on umount
  6. @torvalds

    idr: revert misallocation bug fix

    Tejun Heo authored torvalds committed
    Commit 859ddf0 tried to fix
    misallocation bug but broke full bit marking by not clearing
    pa[idp->layers] and also is causing X failures due to lookup failure
    in drm code.  The cause of the latter hasn't been found yet.  Revert
    the fix for now.
    
    Signed-off-by: Tejun Heo <tj@kernel.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Commits on Feb 4, 2010
  1. @torvalds

    Merge branch 'for-linus' of git://git.monstr.eu/linux-2.6-microblaze

    torvalds authored
    * 'for-linus' of git://git.monstr.eu/linux-2.6-microblaze:
      microblaze: fix interrupt state restore
      microblaze: Defconfig update
  2. @torvalds

    Merge branch 'v4l_for_linus' of git://git.kernel.org/pub/scm/linux/ke…

    torvalds authored
    …rnel/git/mchehab/linux-2.6
    
    * 'v4l_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6:
      saa7146: stop DMA before de-allocating DMA scatter/gather page buffers
      V4L/DVB: saa7134: remove stray unlock_kernel
Commits on Feb 3, 2010
  1. @tmlind

    omap: Disable serial port autoidle by default

    tmlind authored
    Currently the omap serial clocks are autoidled after 5 seconds.
    However, this causes lost characters on the serial ports. As this
    is considered non-standard behaviour for Linux, disable the timeout.
    
    Note that this will also cause blocking of any deeper omap sleep
    states.
    
    To enable the autoidling of the serial ports, do something like
    this for each serial port:
    
    # echo 5 > /sys/devices/platform/serial8250.0/sleep_timeout
    # echo 5 > /sys/devices/platform/serial8250.1/sleep_timeout
    ...
    
    Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>
  2. @mareksk @tmlind

    omap: Fix access to already released memory in clk_debugfs_register_o…

    mareksk authored tmlind committed
    …ne()
    
    I have found an access to already released memory in
    clk_debugfs_register_one() function.
    
    Signed-off-by: Marek Skuczynski <mareksk7@gmail.com>
    Acked-by: Paul Walmsley <paul@pwsan.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>
  3. @tmlind

    omap: Fix arch/arm/mach-omap2/mux.c: Off by one error

    tmlind authored
    David Binderman ran the sourceforge tool cppcheck over the source code of the
    new Linux kernel 2.6.33-rc6:
    
    [./arm/mach-omap2/mux.c:492]: (error) Buffer access out-of-bounds
    
    13 characters + 1 digit + 1 zero byte is more than 14 characters.
    
    Also add a comment on mode0 name length in case new omaps
    start using longer names.
    
    Reported-by: David Binderman <dcb314@hotmail.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>
  4. @tmlind

    omap: Fix 3630 mux errors

    tmlind authored
    3630 has more mux signals than 34xx. The additional pins
    exist in omap36xx_cbp_subset, but are not initialized
    as the superset is missing these offsets. This causes
    the following errors during the boot:
    
    mux: Unknown entry offset 0x236
    mux: Unknown entry offset 0x22e
    mux: Unknown entry offset 0x1ec
    mux: Unknown entry offset 0x1ee
    mux: Unknown entry offset 0x1f4
    mux: Unknown entry offset 0x1f6
    mux: Unknown entry offset 0x1f8
    mux: Unknown entry offset 0x1fa
    mux: Unknown entry offset 0x1fc
    mux: Unknown entry offset 0x22a
    mux: Unknown entry offset 0x226
    mux: Unknown entry offset 0x230
    mux: Unknown entry offset 0x22c
    mux: Unknown entry offset 0x228
    
    Fix this by adding the missing offsets to omap3 superset.
    Note that additionally the uninitialized pins need to be
    skipped on 34xx.
    
    Based on an earlier patch by Allen Pais <allen.pais@ti.com>.
    
    Reported-by: Allen Pais <allen.pais@ti.com>
    Signed-off-by: Allen Pais <allen.pais@ti.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>
  5. @khilman @tmlind

    OMAP2/3: GPMC: ensure valid clock pointer

    khilman authored tmlind committed
    Ensure valid clock pointer during GPMC init.  Fixes compiler
    warning about potential use of uninitialized variable.
    
    Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>
  6. @khilman @tmlind

    OMAP2/3: IRQ: ensure valid base address

    khilman authored tmlind committed
    Ensure valid base address during IRQ init.  Fixes compiler warning
    about potential use of uninitialized variable.
    
    Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>
  7. @tmlind

    ARCH OMAP : enable ARCH_HAS_HOLES_MEMORYMODEL for OMAP

    Sriram authored tmlind committed
    OMAP platforms(like OMAP3530) include DSP or other co-processors
    for media acceleration. when carving out memory for the
    accelerators we can end up creating a hole in the memory map
    of sort:
    <kernel memory><hole(memory for accelerator)><kernel memory>
    
    To handle such a memory configuration ARCH_HAS_HOLES_MEMORYMODEL
    has to be enabled. For further information refer discussion at:
    http://www.mail-archive.com/linux-omap@vger.kernel.org/msg15262.html.
    
    Signed-off-by: Sriramakrishnan <srk@ti.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>
  8. @tmlind

    omap: Remove old unused defines for OMAP_32KSYNCT_BASE

    tmlind authored
    Remove old unused defines for OMAP_32KSYNCT_BASE
    
    Signed-off-by: Tony Lindgren <tony@atomide.com>
  9. @torvalds

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel…

    torvalds authored
    …/git/ryusuke/nilfs2
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2:
      nilfs2: fix potential leak of dirty data on umount
  10. ARM: Fix wrong register in proc-arm6_7.S data abort handler

    Russell King authored
    Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
  11. futex: Handle futex value corruption gracefully

    Thomas Gleixner authored
    The WARN_ON in lookup_pi_state which complains about a mismatch
    between pi_state->owner->pid and the pid which we retrieved from the
    user space futex is completely bogus.
    
    The code just emits the warning and then continues despite the fact
    that it detected an inconsistent state of the futex. A conveniant way
    for user space to spam the syslog.
    
    Replace the WARN_ON by a consistency check. If the values do not match
    return -EINVAL and let user space deal with the mess it created.
    
    This also fixes the missing task_pid_vnr() when we compare the
    pi_state->owner pid with the futex value.
    
    Reported-by: Jermome Marchand <jmarchan@redhat.com>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Acked-by: Darren Hart <dvhltc@us.ibm.com>
    Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Cc: <stable@kernel.org>
  12. futex: Handle user space corruption gracefully

    Thomas Gleixner authored
    If the owner of a PI futex dies we fix up the pi_state and set
    pi_state->owner to NULL. When a malicious or just sloppy programmed
    user space application sets the futex value to 0 e.g. by calling
    pthread_mutex_init(), then the futex can be acquired again. A new
    waiter manages to enqueue itself on the pi_state w/o damage, but on
    unlock the kernel dereferences pi_state->owner and oopses.
    
    Prevent this by checking pi_state->owner in the unlock path. If
    pi_state->owner is not current we know that user space manipulated the
    futex value. Ignore the mess and return -EINVAL.
    
    This catches the above case and also the case where a task hijacks the
    futex by setting the tid value and then tries to unlock it.
    
    Reported-by: Jermome Marchand <jmarchan@redhat.com>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Acked-by: Darren Hart <dvhltc@us.ibm.com>
    Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Cc: <stable@kernel.org>
  13. futex_lock_pi() key refcnt fix

    Mikael Pettersson authored Thomas Gleixner committed
    This fixes a futex key reference count bug in futex_lock_pi(),
    where a key's reference count is incremented twice but decremented
    only once, causing the backing object to not be released.
    
    If the futex is created in a temporary file in an ext3 file system,
    this bug causes the file's inode to become an "undead" orphan,
    which causes an oops from a BUG_ON() in ext3_put_super() when the
    file system is unmounted. glibc's test suite is known to trigger this,
    see <http://bugzilla.kernel.org/show_bug.cgi?id=14256>.
    
    The bug is a regression from 2.6.28-git3, namely Peter Zijlstra's
    38d47c1 "[PATCH] futex: rely on
    get_user_pages() for shared futexes". That commit made get_futex_key()
    also increment the reference count of the futex key, and updated its
    callers to decrement the key's reference count before returning.
    Unfortunately the normal exit path in futex_lock_pi() wasn't corrected:
    the reference count is incremented by get_futex_key() and queue_lock(),
    but the normal exit path only decrements once, via unqueue_me_pi().
    The fix is to put_futex_key() after unqueue_me_pi(), since 2.6.31
    this is easily done by 'goto out_put_key' rather than 'goto out'.
    
    Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>
    Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Acked-by: Darren Hart <dvhltc@us.ibm.com>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Cc: <stable@kernel.org>
  14. NFS: Don't clobber the attribute type in nfs_update_inode()

    Trond Myklebust authored
    If the NFS_ATTR_FATTR_TYPE field isn't set in fattr->valid, then we should
    not set the S_IFMT part of inode->i_mode.
    
    Reported-by: Al Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
  15. NFS: Fix a umount race

    Trond Myklebust authored
    Ensure that we unregister the bdi before kill_anon_super() calls
    ida_remove() on our device name.
    
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Cc: stable@kernel.org
  16. NFS: Fix an Oops when truncating a file

    Trond Myklebust authored
    The VM/VFS does not allow mapping->a_ops->invalidatepage() to fail.
    Unfortunately, nfs_wb_page_cancel() may fail if a fatal signal occurs.
    Since the NFS code assumes that the page stays mapped for as long as the
    writeback is active, we can end up Oopsing (among other things).
    
    The only safe fix here is to convert nfs_wait_on_request(), so as to make
    it uninterruptible (as is already the case with wait_on_page_writeback()).
    
    
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Cc: stable@kernel.org
  17. @smagnani @michalsimek

    microblaze: fix interrupt state restore

    smagnani authored michalsimek committed
    Interrupts must be disabled while an interrupt state restore
    (prep for interrupt return) is in progress.
    Code to do this was lost in the port to the mainline kernel.
    
    Signed-off-by: Steven J. Magnani <steve@digidescorp.com>
    Signed-off-by: Michal Simek <monstr@monstr.eu>
  18. GFS2: Extend umount wait coverage to full glock lifetime

    Steven Whitehouse authored
    Although all glocks are, by the time of the umount glock wait,
    scheduled for demotion, some of them haven't made it far
    enough through the process for the original set of waiting
    code to wait for them.
    
    This extends the ref count to the whole glock lifetime in order
    to ensure that the waiting does catch all glocks. It does make
    it a bit more invasive, but it seems the only sensible solution
    at the moment.
    
    Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
  19. GFS2: Wait for unlock completion on umount

    Steven Whitehouse authored
    This patch adds a wait on umount between the point at which we
    dispose of all glocks and the point at which we unmount the
    lock protocol. This ensures that we've received all the replies
    to our unlock requests before we stop the locking.
    
    Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
    Reported-by: Fabio M. Di Nitto <fdinitto@redhat.com>
  20. @michalsimek

    microblaze: Defconfig update

    michalsimek authored
    There were several changes in Microblaze defconfig that's why
    is good to update defconfigs.
    
    Signed-off-by: Michal Simek <monstr@monstr.eu>
  21. @torvalds

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel…

    torvalds authored
    …/git/jmorris/security-testing-2.6
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6:
      kernel/cred.c: use kmem_cache_free
  22. @torvalds

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6

    torvalds authored
    * git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6: (23 commits)
      connector: Delete buggy notification code.
      be2net: use eq-id to calculate cev-isr reg offset
      Bluetooth: Use the control channel for raw HID reports
      Bluetooth: Add DFU driver for Atheros Bluetooth chipset AR3011
      Bluetooth: Redo checks in IRQ handler for shared IRQ support
      Bluetooth: Fix memory leak in L2CAP
      Bluetooth: Remove double free of SKB pointer in L2CAP
      cdc_ether: Partially revert "usbnet: Set link down initially ..."
      be2net: Fix memset() arg ordering.
      bonding: bond_open error return value
      ixgbe: if ixgbe_copy_dcb_cfg is going to fail learn about it early
      ixgbe: set the correct DCB bit for pg tx settings
      igbvf: fix issue w/ mapped_as_page being left set after unmap
      drivers/net: ks8851_mll ethernet network driver
      be2net: Bug fix to support newer generation of BE ASIC
      starfire: clean up properly if firmware loading fails
      mac80211: fix NULL pointer dereference when ftrace is enabled
      netfilter: ctnetlink: fix expectation mask dump
      ipv6: conntrack: Add member of user to nf_ct_frag6_queue structure
      ath9k: fix eeprom INI values override for 2GHz-only cards
      ...
  23. @torvalds

    pktcdvd: removing device does not remove its sysfs dir

    Thadeu Lima de Souza Cascardo authored torvalds committed
    This is the counterpart to cba7671
    ("pktcdvd: remove broken dev_t export of class devices").  Device is not
    registered using dev_t, so it should not be destroyed using device_destroy
    which looks up the device by dev_t.  This will fail and adding the device
    again will fail with the "duplicate name" error.  This is fixed using
    device_unregister instead of device_destroy.
    
    Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
    Cc: Kay Sievers <kay.sievers@vrfy.org>
    Cc: Peter Osterlund <petero2@telia.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Jens Axboe <jens.axboe@oracle.com>
    Cc: <stable@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  24. @torvalds

    memory hotplug: fix a bug on /dev/mem for 64-bit kernels

    Shaohui Zheng authored torvalds committed
    Newly added memory can not be accessed via /dev/mem, because we do not
    update the variables high_memory, max_pfn and max_low_pfn.
    
    Add a function update_end_of_memory_vars() to update these variables for
    64-bit kernels.
    
    [akpm@linux-foundation.org: simplify comment]
    Signed-off-by: Shaohui Zheng <shaohui.zheng@intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Li Haicheng <haicheng.li@intel.com>
    Reviewed-by: Wu Fengguang <fengguang.wu@intel.com>
    Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
    Cc: Ingo Molnar <mingo@elte.hu>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: "H. Peter Anvin" <hpa@zytor.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  25. @antonblanchard @torvalds

    fault injection: correct function names in documentation

    antonblanchard authored torvalds committed
    init_fault_attr_entries() should be init_fault_attr_dentries().
    
    cleanup_fault_attr_entries() should be cleanup_fault_attr_dentries().
    
    Signed-off-by: Anton Blanchard <anton@samba.org>
    Acked-by: Akinobu Mita <akinobu.mita@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  26. @jeffmahoney @torvalds

    hugetlb: fix section mismatches

    jeffmahoney authored torvalds committed
    hugetlb_sysfs_add_hstate is called by hugetlb_register_node directly
    during init and also indirectly via sysfs after init.
    
    This patch removes the __init tag from hugetlb_sysfs_add_hstate.
    
    Signed-off-by: Jeff Mahoney <jeffm@suse.com>
    Cc: Lee Schermerhorn <lee.schermerhorn@hp.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  27. @torvalds

    uartlite: fix crash when using as console

    Richard Röjfors authored torvalds committed
    Move the ulite_console_setup to the .devinit section since it might be
    called on probe, which is in devinit.  Fixes the crash below where the
    uartlite hw is probed after the .init section is freed from the kernel.
    
    uartlite: ttyUL0 at MMIO 0xc8000100 (irq = 30) is a uartlite
    BUG: unable to handle kernel NULL pointer dereference at (null)
    IP: [<c176720e>] ulite_console_setup+0x6f/0xa8
    *pdpt = 0000000036fb0001 *pde = 0000000000000000
    Oops: 0000 [#1] PREEMPT SMP
    last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/host0/uevent
    Modules linked in: puffin(+) serio_raw
    
    Pid: 151, comm: modprobe Not tainted (2.6.31.5-1.0.b1-b1 #1) POULSBO
    EIP: 0060:[<c176720e>] EFLAGS: 00010246 CPU: 0
    EIP is at ulite_console_setup+0x6f/0xa8
    EAX: c16ec824 EBX: c16ec824 ECX: c176719f EDX: 00000000
    ESI: 00000000 EDI: c17b42c4 EBP: f6fd1cf0 ESP: f6fd1cd8
     DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
    Process modprobe (pid: 151, ti=f6fd0000 task=f6fa1020 task.ti=f6fd0000)
    Stack:
     c1031f51 00000000 00000000 00000246 c182237c f7742000 f6fd1d5c c11fd316
    <0> c16ec85c f77420d4 0000001e 00000000 00000000 c1633e78 4f494d4d 63783020
    <0> 30303038 00303031 f6fd1d3c c10e0786 f6fd1d48 00000000 f6fd1d48 00000000
    Call Trace:
     [<c1031f51>] ? register_console+0xf6/0x1fc
     [<c11fd316>] ? uart_add_one_port+0x237/0x2bb
     [<c10e0786>] ? sysfs_add_one+0x13/0xd3
     [<c10e142f>] ? sysfs_do_create_link+0xba/0xfc
     [<c146f200>] ? ulite_probe+0x198/0x1eb
     [<c12064ee>] ? platform_drv_probe+0xc/0xe
     [<c120597b>] ? driver_probe_device+0x79/0x105
     [<c1205a8e>] ? __device_attach+0x28/0x30
     [<c120511f>] ? bus_for_each_drv+0x3d/0x67
     [<c1205af9>] ? device_attach+0x44/0x58
     [<c1205a66>] ? __device_attach+0x0/0x30
     [<c1204fb8>] ? bus_probe_device+0x1f/0x34
     [<c1203e68>] ? device_add+0x385/0x4c0
     [<c148491f>] ? _write_unlock+0x8/0x1f
     [<c1206aac>] ? platform_device_add+0xd9/0x11c
     [<c120c685>] ? mfd_add_devices+0x165/0x1bc
     [<f831b378>] ? puffin_probe+0x2d0/0x390 [puffin]
     [<c11a08ef>] ? pci_match_device+0xa0/0xa7
     [<c11a07bc>] ? local_pci_probe+0xe/0x10
     [<c11a11db>] ? pci_device_probe+0x43/0x66
     [<c120597b>] ? driver_probe_device+0x79/0x105
     [<c1205a4a>] ? __driver_attach+0x43/0x5f
     [<c120535d>] ? bus_for_each_dev+0x3d/0x67
     [<c1205852>] ? driver_attach+0x14/0x16
     [<c1205a07>] ? __driver_attach+0x0/0x5f
     [<c1204dea>] ? bus_add_driver+0xf9/0x220
     [<c1205c8f>] ? driver_register+0x8b/0xeb
     [<c11a1518>] ? __pci_register_driver+0x43/0x9f
     [<c10477ef>] ? __blocking_notifier_call_chain+0x40/0x4c
     [<f831f000>] ? puffin_init+0x0/0x48 [puffin]
     [<f831f017>] ? puffin_init+0x17/0x48 [puffin]
     [<c1001139>] ? do_one_initcall+0x4c/0x131
     [<c105607b>] ? sys_init_module+0xa7/0x1b7
     [<c1002a61>] ? syscall_call+0x7/0xb
     Code: 6e 74 00 00 00 92 33 00 00 18 00 0e 01 73 79 6e 63 65 2d 72 65 67 69 73 74 72 79 0c 00 49 32
    00 00 14 00 09 01 61 6c 73 61 2d 69 <6e> 66 6f 00 00 00 42 37 00 00 10 00 07 01 6b 69 6c 6c 61 6c 6c
    EIP: [<c176720e>] ulite_console_setup+0x6f/0xa8 SS:ESP 0068:f6fd1cd8
    CR2: 0000000000000000
    
    Signed-off-by: Richard Röjfors <richard.rojfors@pelagicore.com>
    Acked-by: Peter Korsgaard <jacmet@sunsite.dk>
    Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
    Cc: <stable@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Something went wrong with that request. Please try again.