Permalink
Commits on Aug 29, 2010
  1. Merge branch 'version-2.6.35'

    Oleksandr Natalenko committed Aug 29, 2010
  2. version-2.6.35: bump to v2.6.35-pf7

    Oleksandr Natalenko committed Aug 29, 2010
  3. Merge remote branch 'tuxonice-2.6.35/combined'

    Oleksandr Natalenko committed Aug 29, 2010
  4. Merge branch 'ck-2.6.35'

    Oleksandr Natalenko committed Aug 29, 2010
  5. ck-2.6.35: update BFS to v330

    Oleksandr Natalenko committed Aug 29, 2010
Commits on Aug 27, 2010
  1. Modify module api to allow passing virts.

    Modify the read and write page functions in the module API to
    allow virtual addresses as well as page addresses to be passed
    around. This lets us drop the memcpy that the compression
    support previously had.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Aug 27, 2010
  2. Fix missing memory_bm_test_bit export

    Address the missing export of memory_bm_test_bit, which causes
    a compilation error when building TuxOnIce as modules.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Aug 27, 2010
  3. Merge branch 'configs-2.6.35'

    Oleksandr Natalenko committed Aug 27, 2010
  4. configs-2.6.35: update Dell Inspiron 1525 laptop config

    Oleksandr Natalenko committed Aug 27, 2010
  5. Merge branch 'version-2.6.35'

    Oleksandr Natalenko committed Aug 27, 2010
  6. version-2.6.35: bump version to v2.6.35-pf6

    Oleksandr Natalenko committed Aug 27, 2010
  7. Merge remote branch 'tuxonice-2.6.35/combined'

    Oleksandr Natalenko committed Aug 27, 2010
  8. fix merge conflict

    Oleksandr Natalenko committed Aug 27, 2010
  9. Merge branch 'stable' into combined

    Nigel Cunningham committed Aug 27, 2010
Commits on Aug 26, 2010
  1. Linux 2.6.35.4

    gregkh committed Aug 26, 2010
  2. tracing: Fix timer tracing

    commit ede1b42 upstream.
    
    PowerTOP would like to be able to trace timers.
    
    Unfortunately, the current timer tracing is not very useful: the
    actual timer function is not recorded in the trace at the start
    of timer execution.
    
    Although this is recorded for timer "start" time (when it gets
    armed), this is not useful; most timers get started early, and a
    tracer like PowerTOP will never see this event, but will only
    see the actual running of the  timer.
    
    This patch just adds the function to the timer tracing; I've
    verified with PowerTOP that now it can get useful information
    about timers.
    
    Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
    Cc: xiaoguangrong@cn.fujitsu.com
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Frederic Weisbecker <fweisbec@gmail.com>
    Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
    LKML-Reference: <4C6C5FA9.3000405@linux.intel.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    fenrus75 committed with gregkh Aug 18, 2010
  3. mutex: Improve the scalability of optimistic spinning

    commit 9d0f4dc upstream.
    
    There is a scalability issue for current implementation of optimistic
    mutex spin in the kernel.  It is found on a 8 node 64 core Nehalem-EX
    system (HT mode).
    
    The intention of the optimistic mutex spin is to busy wait and spin on a
    mutex if the owner of the mutex is running, in the hope that the mutex
    will be released soon and be acquired, without the thread trying to
    acquire mutex going to sleep. However, when we have a large number of
    threads, contending for the mutex, we could have the mutex grabbed by
    other thread, and then another ……, and we will keep spinning, wasting cpu
    cycles and adding to the contention.  One possible fix is to quit
    spinning and put the current thread on wait-list if mutex lock switch to
    a new owner while we spin, indicating heavy contention (see the patch
    included).
    
    I did some testing on a 8 socket Nehalem-EX system with a total of 64
    cores. Using Ingo's test-mutex program that creates/delete files with 256
    threads (http://lkml.org/lkml/2006/1/8/50) , I see the following speed up
    after putting in the mutex spin fix:
    
     ./mutex-test V 256 10
                     Ops/sec
     2.6.34          62864
     With fix        197200
    
    Repeating the test with Aim7 fserver workload, again there is a speed up
    with the fix:
    
                     Jobs/min
     2.6.34          91657
     With fix        149325
    
    To look at the impact on the distribution of mutex acquisition time, I
    collected the mutex acquisition time on Aim7 fserver workload with some
    instrumentation.  The average acquisition time is reduced by 48% and
    number of contentions reduced by 32%.
    
                     #contentions    Time to acquire mutex (cycles)
     2.6.34          72973           44765791
     With fix        49210           23067129
    
    The histogram of mutex acquisition time is listed below.  The acquisition
    time is in 2^bin cycles.  We see that without the fix, the acquisition
    time is mostly around 2^26 cycles.  With the fix, we the distribution get
    spread out a lot more towards the lower cycles, starting from 2^13.
    However, there is an increase of the tail distribution with the fix at
    2^28 and 2^29 cycles.  It seems a small price to pay for the reduced
    average acquisition time and also getting the cpu to do useful work.
    
     Mutex acquisition time distribution (acq time = 2^bin cycles):
             2.6.34                  With Fix
     bin     #occurrence     %       #occurrence     %
     11      2               0.00%   120             0.24%
     12      10              0.01%   790             1.61%
     13      14              0.02%   2058            4.18%
     14      86              0.12%   3378            6.86%
     15      393             0.54%   4831            9.82%
     16      710             0.97%   4893            9.94%
     17      815             1.12%   4667            9.48%
     18      790             1.08%   5147            10.46%
     19      580             0.80%   6250            12.70%
     20      429             0.59%   6870            13.96%
     21      311             0.43%   1809            3.68%
     22      255             0.35%   2305            4.68%
     23      317             0.44%   916             1.86%
     24      610             0.84%   233             0.47%
     25      3128            4.29%   95              0.19%
     26      63902           87.69%  122             0.25%
     27      619             0.85%   286             0.58%
     28      0               0.00%   3536            7.19%
     29      0               0.00%   903             1.83%
     30      0               0.00%   0               0.00%
    
    I've done similar experiments with 2.6.35 kernel on smaller boxes as
    well.  One is on a dual-socket Westmere box (12 cores total, with HT).
    Another experiment is on an old dual-socket Core 2 box (4 cores total, no
    HT)
    
    On the 12-core Westmere box, I see a 250% increase for Ingo's mutex-test
    program with my mutex patch but no significant difference in aim7's
    fserver workload.
    
    On the 4-core Core 2 box, I see the difference with the patch for both
    mutex-test and aim7 fserver are negligible.
    
    So far, it seems like the patch has not caused regression on smaller
    systems.
    
    Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
    Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Cc: Linus Torvalds <torvalds@linux-foundation.org>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Frederic Weisbecker <fweisbec@gmail.com>
    LKML-Reference: <1282168827.9542.72.camel@schen9-DESK>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    pdxChen committed with gregkh Aug 18, 2010
  4. USB: ftdi_sio: add product ID for Lenz LI-USB

    commit ea233f8 upstream.
    
    Add ftdi product ID for Lenz LI-USB, a model train interface.  This
    was NOT tested against 2.6.35, but a similar patch was tested with the
    CentOS 2.6.18-194.11.1.el5 kernel.  It wasn't clear to me what
    ordering is being used in ftdi_sio.c, so I inserted the ID after another
    model train entry(SPROG_II).
    
    Signed-off-by: Galen Seitz <galens@seitzassoc.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    galenseitz committed with gregkh Aug 19, 2010
  5. USB: ftdi_sio: Add ID for Ionics PlugComputer

    commit 666cc07 upstream.
    
    Add the ID for the Ionics PlugComputer (<http://ionicsplug.com/>).
    
    Signed-off-by: Martin Michlmayr <tbm@cyrius.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    tbm committed with gregkh Aug 10, 2010
  6. USB: xhci: Remove buggy assignment in next_trb()

    commit a1669b2 upstream.
    
    The code to increment the TRB pointer has a slight ambiguity that could
    lead to a bug on different compilers.  The ANSI C specification does not
    specify the precedence of the assignment operator over the postfix
    operator.  gcc 4.4 produced the correct code (increment the pointer and
    assign the value), but a MIPS compiler that one of John's clients used
    assigned the old (unincremented) value.
    
    Remove the unnecessary assignment to make all compilers produce the
    correct assembly.
    
    Signed-off-by: John Youn <johnyoun@synopsys.com>
    Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    jysnps committed with gregkh Aug 9, 2010
  7. USB: io_ti: check firmware version before updating

    commit 0827a9f upstream.
    
    If we can't read the firmware for a device from the disk, and yet the
    device already has a valid firmware image in it, we don't want to
    replace the firmware with something invalid.  So check the version
    number to be less than the current one to verify this is the correct
    thing to do.
    
    
    Reported-by: Chris Beauchamp <chris@chillibean.tv>
    Tested-by: Chris Beauchamp <chris@chillibean.tv>
    Cc: Alan Stern <stern@rowland.harvard.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    gregkh committed Aug 17, 2010
  8. USB: ftdi_sio: fix endianess of max packet size

    commit d1ab903 upstream.
    
    The USB max packet size (always little-endian) was not being byte
    swapped on big-endian systems.
    
    Applicable since [USB: ftdi_sio: fix hi-speed device packet size calculation] approx 2.6.31
    
    Signed-off-by: Michael Wileczka <mikewileczka@yahoo.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Michael Wileczka committed with gregkh Aug 18, 2010
  9. USB: CP210x Fix Break On/Off

    commit 7291679 upstream.
    
    The definitions for BREAK_ON and BREAK_OFF are inverted, causing break
    requests to fail. This patch sets BREAK_ON and BREAK_OFF to the correct
    values.
    
    Signed-off-by: Craig Shelley <craig@microtron.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    craigshelley committed with gregkh Aug 18, 2010
  10. USB: pl2303: New vendor and product id

    commit f36ecd5 upstream.
    
    Add support for the Zeagle N2iTiON3 dive computer interface. Since
    Zeagle devices are actually manufactured by Seiko, this patch will
    support other Seiko based models as well.
    
    Signed-off-by: Jef Driesen <jefdriesen@telenet.be>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    jefdriesen committed with gregkh Aug 9, 2010
  11. USB: add device IDs for igotu to navman

    commit 0eee6a2 upstream.
    
    I recently bought a i-gotU USB GPS, and whilst hunting around for linux
    support discovered this post by you back in 2009:
    
    http://kerneltrap.org/mailarchive/linux-usb/2009/3/12/5148644
    
    >Try the navman driver instead.  You can either add the device id to the
    > driver and rebuild it, or do this before you plug the device in:
    > 	modprobe navman
    > 	echo -n "0x0df7 0x0900" > /sys/bus/usb-serial/drivers/navman/new_id
    >
    > and then plug your device in and see if that works.
    
    I can confirm that the navman driver works with the right device IDs on
    my i-gotU GT-600, which has the same device IDs.  Attached is a patch
    adding the IDs.
    
    From: Ross Burton <ross@linux.intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    rossburton committed with gregkh Aug 6, 2010
  12. USB: option: add Celot CT-650

    commit 76078dc upstream.
    
    Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Michael Tokarev committed with gregkh Aug 6, 2010
  13. powerpc: Fix typo in uImage target

    commit c686ecf upstream.
    
    Commit e32e78c
    (powerpc: fix build with make 3.82) introduced a
    typo in uImage target and broke building uImage:
    
    make: *** No rule to make target `uImage'.  Stop.
    
    Signed-off-by: Anatolij Gustschin <agust@denx.de>
    Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Anatolij Gustschin committed with gregkh Aug 15, 2010
  14. Staging: batman-adv: Don't write in not allocated packet_buff

    commit f86b998 upstream.
    
    Each net_device in a system will automatically managed as a possible
    batman_if and holds different informations like a buffer with a prepared
    originator messages. To reduce the memory usage, the packet_buff will
    only be allocated when the interface is really added/enabled for
    batman-adv.
    
    The function to update the hw address information inside the packet_buff
    just assumes that the packet_buff is always initialised and thus the
    kernel will just oops when we try to change the hw address of a not
    already fully enabled interface.
    
    We must always check if the packet_buff is allocated before we try to
    change information inside of it.
    
    Reported-by: Tim Glaremin <Tim.Glaremin@web.de>
    Reported-by: Kazuki Shimada <zukky@bb.banban.jp>
    Signed-off-by: Sven Eckelmann <sven.eckelmann@gmx.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Sven Eckelmann committed with gregkh Aug 21, 2010
  15. Staging: batman-adv: Don't use net_dev after dev_put

    commit 51a00ea upstream.
    
    dev_put allows a device to be freed when all its references are dropped.
    After that we are not allowed to access that information anymore. Access
    to the data structure of a net_device must be surrounded a dev_hold
    and ended using dev_put.
    
    batman-adv adds a device to its own management structure in
    hardif_add_interface and will release it in hardif_remove_interface.
    Thus it must hold a reference all the time between those functions to
    prevent any access to the already released net_device structure.
    
    Reported-by: Tim Glaremin <Tim.Glaremin@web.de>
    Signed-off-by: Sven Eckelmann <sven.eckelmann@gmx.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Sven Eckelmann committed with gregkh Aug 21, 2010
  16. Staging: batman-adv: Create batman_if only on register event

    commit 1189f13 upstream.
    
    We try to get all events for all net_devices to be able to add special
    sysfs folders for the batman-adv configuration. This also includes such
    events like NETDEV_POST_INIT which has no valid kobject according to
    v2.6.32-rc3-13-g7ffbe3f. This would create an oops in that situation.
    
    It is enough to create the batman_if only on NETDEV_REGISTER events
    because we will also receive those events for devices which already
    existed when we registered the notifier call.
    
    Signed-off-by: Sven Eckelmann <sven.eckelmann@gmx.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Sven Eckelmann committed with gregkh Aug 21, 2010
  17. Staging: batman-adv: unify orig_hash_lock spinlock handling to avoid …

    …deadlocks
    
    commit 9abc102 upstream.
    
    The orig_hash_lock spinlock always has to be locked with IRQs being
    disabled to avoid deadlocks between code that is being executed in
    IRQ context and code that is being executed in non-IRQ context.
    
    Reported-by: Sven Eckelmann <sven.eckelmann@gmx.de>
    Signed-off-by: Marek Lindner <lindner_marek@yahoo.de>
    Signed-off-by: Sven Eckelmann <sven.eckelmann@gmx.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Marek Lindner committed with gregkh Aug 9, 2010
  18. drm: stop information leak of old kernel stack.

    commit b9f0aee upstream.
    
    non-critical issue, CVE-2010-2803
    
    Userspace controls the amount of memory to be allocate, so it can
    get the ioctl to allocate more memory than the kernel uses, and get
    access to kernel stack. This can only be done for processes authenticated
    to the X server for DRI access, and if the user has DRI access.
    
    Fix is to just memset the data to 0 if the user doesn't copy into
    it in the first place.
    
    Reported-by: Kees Cook <kees@ubuntu.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Dave Airlie committed with gregkh Aug 17, 2010
  19. drm/radeon/kms: fix GTT/VRAM overlapping test

    commit 2cbeb4e upstream.
    
    GTT/VRAM overlapping test had a typo which leaded to not
    detecting case when vram_end > gtt_end. This patch fix the
    logic and should fix #16574
    
    Signed-off-by: Jerome Glisse <jglisse@redhat.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Jerome Glisse committed with gregkh Aug 16, 2010
  20. drm/radeon/kms: fix sideport detection on newer rs880 boards

    commit 4b80d95 upstream.
    
    The meaning of ucMemoryType changed on recent boards, however,
    ulBootUpSidePortClock should be set properly across all boards.
    
    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Alex Deucher committed with gregkh Aug 20, 2010
  21. drm/radeon/kms/DCE3+: switch pads to ddc mode when going i2c

    commit 5786e2c upstream.
    
    The pins for ddc and aux are shared so you need to switch the
    mode when doing ddc.  The ProcessAuxChannel table already sets
    the pin mode to DP.  This should fix unreliable ddc issues
    on DP ports using non-DP monitors.
    
    Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Alex Deucher committed with gregkh Aug 19, 2010