Skip to content
Commits on Sep 21, 2011
  1. Merge branch 'configs-3.0' into pf-3.0

    Oleksandr Natalenko committed Sep 21, 2011
  2. configs-3.0: update kernel version

    Oleksandr Natalenko committed Sep 21, 2011
  3. Merge branch 'version-3.0' into pf-3.0

    Oleksandr Natalenko committed Sep 21, 2011
  4. version-3.0: bump to v3.0.4-pf

    Oleksandr Natalenko committed Sep 21, 2011
  5. Merge branch 'bfq-3.0-incr' into pf-3.0

    Oleksandr Natalenko committed Sep 21, 2011
  6. bfq-3.0-incr: update BFQ to v3

    Oleksandr Natalenko committed Sep 21, 2011
Commits on Aug 31, 2011
  1. Merge branch 'configs-3.0' into pf-3.0

    Oleksandr Natalenko committed Aug 31, 2011
  2. configs-3.0: enable ext4 security extensions for Dell Inspiron 1525

    Oleksandr Natalenko committed Aug 31, 2011
  3. Merge branch 'version-3.0' into pf-3.0

    Oleksandr Natalenko committed Aug 31, 2011
  4. version-3.0: bump to version 3.0.3-pf

    Oleksandr Natalenko committed Aug 31, 2011
Commits on Aug 29, 2011
  1. fix merge conflict

    Oleksandr Natalenko committed Aug 30, 2011
  2. @gregkh

    Linux 3.0.4

    gregkh committed Aug 29, 2011
  3. @gregkh

    Add a personality to report 2.6.x version numbers

    commit be27425 upstream.
    I ran into a couple of programs which broke with the new Linux 3.0
    version.  Some of those were binary only.  I tried to use LD_PRELOAD to
    work around it, but it was quite difficult and in one case impossible
    because of a mix of 32bit and 64bit executables.
    For example, all kind of management software from HP doesnt work, unless
    we pretend to run a 2.6 kernel.
      $ uname -a
      Linux svivoipvnx001 3.0.0-08107-g97cd98f #1062 SMP Fri Aug 12 18:11:45 CEST 2011 i686 i686 i386 GNU/Linux
      $ hpacucli ctrl all show
      Error: No controllers detected.
      $ rpm -qf /usr/sbin/hpacucli
    Another notable case is that Python now reports "linux3" from
    sys.platform(); which in turn can break things that were checking
    sys.platform() == "linux2":
    It seems pretty clear to me though it's a bug in the apps that are using
    '==' instead of .startswith(), but this allows us to unbreak broken
    This patch adds a UNAME26 personality that makes the kernel report a
    2.6.40+x version number instead.  The x is the x in 3.x.
    I know this is somewhat ugly, but I didn't find a better workaround, and
    compatibility to existing programs is important.
    Some programs also read /proc/sys/kernel/osrelease.  This can be worked
    around in user space with mount --bind (and a mount namespace)
    To use:
      gcc -o uname26 uname26.c
      ./uname26 program
    Signed-off-by: Andi Kleen <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
    Andi Kleen committed with gregkh Aug 19, 2011
  4. @gregkh

    igb: Fix lack of flush after register write and before delay

    commit 064b433 upstream.
    Register writes followed by a delay are required to have a flush
    before the delay in order to commit the values to the register.  Without
    the flush, the code following the delay may not function correctly.
    Reported-by: Tong Ho <>
    Reported-by: Guenter Roeck <>
    Signed-off-by: Carolyn Wyborny <>
    Tested-by:  Aaron Brown <>
    Signed-off-by: Jeff Kirsher <>
    Signed-off-by: Greg Kroah-Hartman <>
    Carolyn Wyborny committed with gregkh Jun 25, 2011
  5. @gregkh

    mmc: sdhci: fix retuning timer wrongly deleted in sdhci_tasklet_finish

    commit 7886961 upstream.
    Currently, the retuning timer for retuning mode 1 will be deleted in
    function sdhci_tasklet_finish after a mmc request done, which will make
    retuning timing never trigger again. This patch fixed this problem.
    Signed-off-by: Aaron Lu <>
    Reviewed-by: Philip Rakity <>
    Signed-off-by: Chris Ball <>
    Signed-off-by: Greg Kroah-Hartman <>
    Aaron Lu committed with gregkh Jul 11, 2011
  6. @sgruszka @gregkh

    rt2x00: fix order of entry flags modification

    commit df71c9c upstream.
    In rt2800usb_work_txdone we check flags in order:
    Modify flags in separate order in rt2x00usb_interrupt_txdone, to avoid
    processing entries in _txdone with wrong flags or skip processing
    ready entries.
    Reported-by: Justin Piszcz <>
    Signed-off-by: Stanislaw Gruszka <>
    Acked-by: Ivo van Doorn <>
    Signed-off-by: John W. Linville <>
    Signed-off-by: Greg Kroah-Hartman <>
    sgruszka committed with gregkh Aug 10, 2011
  7. @gregkh

    fuse: check size of FUSE_NOTIFY_INVAL_ENTRY message

    commit c2183d1 upstream.
    FUSE_NOTIFY_INVAL_ENTRY didn't check the length of the write so the
    message processing could overrun and result in a "kernel BUG at
    Reported-by: Han-Wen Nienhuys <>
    Signed-off-by: Miklos Szeredi <>
    Signed-off-by: Greg Kroah-Hartman <>
    Miklos Szeredi committed with gregkh Aug 24, 2011
  8. @gregkh

    drm/radeon: Extended DDC Probing for Toshiba L300D Radeon Mobility X1…

    …100 HDMI-A Connector
    commit f2b6071 upstream.
    Toshiba Satellite L300D with ATI Mobility Radeon X1100 sends data
       to i2c bus for a HDMI connector that is not implemented/existent
       on the notebook's board.
       Fix by applying extented DDC probing for this connector.
       Requires [PATCH] drm/radeon: Extended DDC Probing for Connectors
       with Improperly Wired DDC Lines
       Tested for kernel 2.6.38 on Toshiba Satellite L300D notebook
    Signed-off-by: Thomas Reim <>
    Acked-by: Chris Routh <>
    Reviewed-by: Alex Deucher <>
    Signed-off-by: Dave Airlie <>
    Signed-off-by: Greg Kroah-Hartman <>
    Thomas Reim committed with gregkh Aug 17, 2011
  9. @mslusarz @gregkh

    drm/ttm: fix ttm_bo_add_ttm(user) failure path

    commit 7c4c396 upstream.
    ttm_tt_destroy kfrees passed object, so we need to nullify
    a reference to it.
    Signed-off-by: Marcin Slusarz <>
    Reviewed-by: Thomas Hellstrom <>
    Signed-off-by: Dave Airlie <>
    Signed-off-by: Greg Kroah-Hartman <>
    mslusarz committed with gregkh Aug 22, 2011
  10. @gregkh

    x86, UV: Remove UV delay in starting slave cpus

    commit 05e33fc upstream.
    Delete the 10 msec delay between the INIT and SIPI when starting
    slave cpus. I can find no requirement for this delay. BIOS also
    has similar code sequences without the delay.
    Removing the delay reduces boot time by 40 sec. Every bit helps.
    Signed-off-by: Jack Steiner <>
    Signed-off-by: Ingo Molnar <>
    Signed-off-by: Greg Kroah-Hartman <>
    Jack Steiner committed with gregkh Aug 5, 2011
  11. @gregkh

    x86-32, vdso: On system call restart after SYSENTER, use int $0x80

    commit 7ca0758 upstream.
    When we enter a 32-bit system call via SYSENTER or SYSCALL, we shuffle
    the arguments to match the int $0x80 calling convention.  This was
    probably a design mistake, but it's what it is now.  This causes
    errors if the system call as to be restarted.
    For SYSENTER, we have to invoke the instruction from the vdso as the
    return address is hardcoded.  Accordingly, we can simply replace the
    jump in the vdso with an int $0x80 instruction and use the slower
    entry point for a post-restart.
    Suggested-by: Linus Torvalds <>
    Signed-off-by: H. Peter Anvin <>
    Signed-off-by: Greg Kroah-Hartman <>
    H. Peter Anvin committed with gregkh Aug 22, 2011
  12. @gregkh

    x86, olpc: Wait for last byte of EC command to be accepted

    commit a3ea14d upstream.
    When executing EC commands, only waiting when there are still
    more bytes to write is usually fine. However, if the system
    suspends very quickly after a call to olpc_ec_cmd(), the last
    data byte may not yet be transferred to the EC, and the command
    will not complete.
    This solves a bug where the SCI wakeup mask was not correctly
    written when going into suspend.
    It means that sometimes, on XO-1.5 (but not XO-1), the
    devices that were marked as wakeup sources can't wake up
    the system. e.g. you ask for wifi wakeups, suspend, but then
    incoming wifi frames don't wake up the system as they should.
    Signed-off-by: Paul Fox <>
    Signed-off-by: Daniel Drake <>
    Acked-by: Andres Salomon <>
    Signed-off-by: Ingo Molnar <>
    Signed-off-by: Greg Kroah-Hartman <>
    Paul Fox committed with gregkh Jul 26, 2011
  13. @gregkh

    xen: Do not enable PV IPIs when vector callback not present

    commit 3c05c4b upstream.
    Fix regression for HVM case on older (<4.1.1) hypervisors caused by
      commit 99bbb3a
      Author: Stefano Stabellini <>
      Date:   Thu Dec 2 17:55:10 2010 +0000
        xen: PV on HVM: support PV spinlocks and IPIs
    This change replaced the SMP operations with event based handlers without
    taking into account that this only works when the hypervisor supports
    callback vectors. This causes unexplainable hangs early on boot for
    HVM guests with more than one CPU.
    Signed-off-by: Stefan Bader <>
    Signed-off-by: Stefano Stabellini <>
    Tested-and-Reported-by: Stefan Bader <>
    Signed-off-by: Konrad Rzeszutek Wilk <>
    Signed-off-by: Greg Kroah-Hartman <>
    Stefano Stabellini committed with gregkh Aug 17, 2011
  14. @gregkh

    xen/x86: replace order-based range checking of M2P table by linear one

    commit ccbcdf7 upstream.
    The order-based approach is not only less efficient (requiring a shift
    and a compare, typical generated code looking like this
    	mov	eax, [machine_to_phys_order]
    	mov	ecx, eax
    	shr	ebx, cl
    	test	ebx, ebx
    	jnz	...
    whereas a direct check requires just a compare, like in
    	cmp	ebx, [machine_to_phys_nr]
    	jae	...
    ), but also slightly dangerous in the 32-on-64 case - the element
    address calculation can wrap if the next power of two boundary is
    sufficiently far away from the actual upper limit of the table, and
    hence can result in user space addresses being accessed (with it being
    unknown what may actually be mapped there).
    Additionally, the elimination of the mistaken use of fls() here (should
    have been __fls()) fixes a latent issue on x86-64 that would trigger
    if the code was run on a system with memory extending beyond the 44-bit
    Signed-off-by: Jan Beulich <>
    [v1: Based on Jeremy's feedback]
    Signed-off-by: Konrad Rzeszutek Wilk <>
    Signed-off-by: Greg Kroah-Hartman <>
    Jan Beulich committed with gregkh Aug 16, 2011
  15. @gregkh

    xen-blkfront: Fix one off warning about name clash

    commit 89153b5 upstream.
    Avoid telling users to use xvde and onwards when using xvde.
    Acked-by: Stefano Stabellini <>
    Signed-off-by: Stefan Bader <>
    Signed-off-by: Konrad Rzeszutek Wilk <>
    Signed-off-by: Greg Kroah-Hartman <>
    Stefan Bader committed with gregkh Jul 14, 2011
  16. @gregkh

    xen-blkfront: Drop name and minor adjustments for emulated scsi devices

    commit 196cfe2 upstream.
    These were intended to avoid the namespace clash when representing
    emulated IDE and SCSI devices. However that seems to confuse users
    more than expected (a disk defined as sda becomes xvde).
    So for now go back to the scheme which does no adjustments. This
    will break when mixing IDE and SCSI names in the configuration of
    guests but should be by now expected.
    Acked-by: Stefano Stabellini <>
    Signed-off-by: Stefan Bader <>
    Signed-off-by: Konrad Rzeszutek Wilk <>
    Signed-off-by: Greg Kroah-Hartman <>
    Stefan Bader committed with gregkh Jul 14, 2011
  17. @tytso @gregkh

    ext4: fix nomblk_io_submit option so it correctly converts uninit blocks

    commit 9dd75f1 upstream.
    Bug discovered by Jan Kara:
    Finally, commit 1449032 returned back
    the old IO submission code but apparently it forgot to return the old
    handling of uninitialized buffers so we unconditionnaly call
    block_write_full_page() without specifying end_io function. So AFAICS
    we never convert unwritten extents to written in some cases. For
    example when I mount the fs as: mount -t ext4 -o
    nomblk_io_submit,dioread_nolock /dev/ubdb /mnt and do
            int fd = open(argv[1], O_RDWR | O_CREAT | O_TRUNC, 0600);
            char buf[1024];
            memset(buf, 'a', sizeof(buf));
            fallocate(fd, 0, 0, 16384);
            write(fd, buf, sizeof(buf));
    I get a file full of zeros (after remounting the filesystem so that
    pagecache is dropped) instead of seeing the first KB contain 'a's.
    Signed-off-by: "Theodore Ts'o" <>
    Signed-off-by: Greg Kroah-Hartman <>
    tytso committed with gregkh Aug 13, 2011
  18. @taoma-tm @gregkh

    ext4: Resolve the hang of direct i/o read in handling EXT4_IO_END_UNW…

    commit 32c80b3 upstream.
    EXT4_IO_END_UNWRITTEN flag set and the increase of i_aiodio_unwritten
    should be done simultaneously since ext4_end_io_nolock always clear
    the flag and decrease the counter in the same time.
    We don't increase i_aiodio_unwritten when setting
    EXT4_IO_END_UNWRITTEN so it will go nagative and causes some process
    to wait forever.
    Part of the patch came from Eric in his e-mail, but it doesn't fix the
    problem met by Michael actually.
    Reported-and-Tested-by: Michael Tokarev<>
    Signed-off-by: Eric Sandeen <>
    Signed-off-by: Tao Ma <>
    Signed-off-by: "Theodore Ts'o" <>
    Signed-off-by: Greg Kroah-Hartman <>
    taoma-tm committed with gregkh Aug 13, 2011
  19. @gregkh

    ext4: call ext4_ioend_wait and ext4_flush_completed_IO in ext4_evict_…

    commit 2581fdc upstream.
    Flush inode's i_completed_io_list before calling ext4_io_wait to
    prevent the following deadlock scenario: A page fault happens while
    some process is writing inode A. During page fault,
    shrink_icache_memory is called that in turn evicts another inode
    B. Inode B has some pending io_end work so it calls ext4_ioend_wait()
    that waits for inode B's i_ioend_count to become zero. However, inode
    B's ioend work was queued behind some of inode A's ioend work on the
    same cpu's ext4-dio-unwritten workqueue. As the ext4-dio-unwritten
    thread on that cpu is processing inode A's ioend work, it tries to
    grab inode A's i_mutex lock. Since the i_mutex lock of inode A is
    still hold before the page fault happened, we enter a deadlock.
    Also moves ext4_flush_completed_IO and ext4_ioend_wait from
    ext4_destroy_inode() to ext4_evict_inode(). During inode deleteion,
    ext4_evict_inode() is called before ext4_destroy_inode() and in
    ext4_evict_inode(), we may call ext4_truncate() without holding
    i_mutex lock. As a result, there is a race between flush_completed_IO
    that is called from ext4_ext_truncate() and ext4_end_io_work, which
    may cause corruption on an io_end structure. This change moves
    ext4_flush_completed_IO and ext4_ioend_wait from ext4_destroy_inode()
    to ext4_evict_inode() to resolve the race between ext4_truncate() and
    ext4_end_io_work during inode deletion.
    Signed-off-by: Jiaying Zhang <>
    Signed-off-by: "Theodore Ts'o" <>
    Signed-off-by: Greg Kroah-Hartman <>
    Jiaying Zhang committed with gregkh Aug 13, 2011
  20. @gregkh

    ext4: Fix ext4_should_writeback_data() for no-journal mode

    commit 441c850 upstream.
    ext4_should_writeback_data() had an incorrect sequence of
    tests to determine if it should return 0 or 1: in
    particular, even in no-journal mode, 0 was being returned
    for a non-regular-file inode.
    This meant that, in non-journal mode, we would use
    ext4_journalled_aops for directories, symlinks, and other
    non-regular files.  However, calling journalled aop
    callbacks when there is no valid handle, can cause problems.
    This would cause a kernel crash with Jan Kara's commit
    2d859db ("ext4: fix data corruption in inodes with
    journalled data"), because we now dereference 'handle' in
    I also added BUG_ONs to check for a valid handle in the
    obviously journal-only aops callbacks.
    I tested this running xfstests with a scratch device in
    these modes:
       - no-journal
       - data=ordered
       - data=writeback
       - data=journal
    All work fine; the data=journal run has many failures and a
    crash in xfstests 074, but this is no different from a
    vanilla kernel.
    Signed-off-by: Curt Wohlgemuth <>
    Signed-off-by: "Theodore Ts'o" <>
    Signed-off-by: Greg Kroah-Hartman <>
    Curt Wohlgemuth committed with gregkh Aug 13, 2011
  21. @crimsun @gregkh

    ALSA: ac97: Add HP Compaq dc5100 SFF(PT003AW) to Headphone Jack Sense…

    … whitelist
    commit eade7b2 upstream.
    The original reporter needs 'Headphone Jack Sense' enabled to have
    audible audio, so add his PCI SSID to the whitelist.
    Reported-and-tested-by: Muhammad Khurram Khan
    Signed-off-by: Daniel T Chen <>
    Signed-off-by: Takashi Iwai <>
    Signed-off-by: Greg Kroah-Hartman <>
    crimsun committed with gregkh Aug 14, 2011
  22. @zonque @gregkh

    ALSA: snd_usb_caiaq: track submitted output urbs

    commit da6094e upstream.
    The snd_usb_caiaq driver currently assumes that output urbs are serviced
    in time and doesn't track when and whether they are given back by the
    USB core. That usually works fine, but due to temporary limitations of
    the XHCI stack, we faced that urbs were submitted more than once with
    this approach.
    As it's no good practice to fire and forget urbs anyway, this patch
    introduces a proper bit mask to track which requests have been submitted
    and given back.
    That alone however doesn't make the driver work in case the host
    controller is broken and doesn't give back urbs at all, and the output
    stream will stop once all pre-allocated output urbs are consumed. But
    it does prevent crashes of the controller stack in such cases.
    See for more details.
    Signed-off-by: Daniel Mack <>
    Reported-and-tested-by: Matej Laitl <>
    Cc: Sarah Sharp <>
    Signed-off-by: Takashi Iwai <>
    Signed-off-by: Greg Kroah-Hartman <>
    zonque committed with gregkh Aug 14, 2011
  23. @tiwai @gregkh

    ALSA: usb-audio - Fix missing mixer dB information

    commit 38b6519 upstream.
    The recent fix for testing dB range at the mixer creation time seems
    to cause regressions in some devices.  In such devices, reading the dB
    info at probing time gives an error, thus both dBmin and dBmax are still
    zero, and TLV flag isn't set although the later read of dB info succeeds.
    This patch adds a workaround for such a case by assuming that the later
    read will succeed.  In future, a similar test should be performed in a
    case where a wrong dB range is seen even in the later read.
    Signed-off-by: Takashi Iwai <>
    Signed-off-by: Greg Kroah-Hartman <>
    tiwai committed with gregkh Aug 19, 2011
  24. @liub @gregkh

    Btrfs: fix an oops of log replay

    commit 34f3e4f upstream.
    When btrfs recovers from a crash, it may hit the oops below:
    ------------[ cut here ]------------
    kernel BUG at fs/btrfs/inode.c:4580!
    RIP: 0010:[<ffffffffa03df251>]  [<ffffffffa03df251>] btrfs_add_link+0x161/0x1c0 [btrfs]
    Call Trace:
     [<ffffffffa03e7b31>] ? btrfs_inode_ref_index+0x31/0x80 [btrfs]
     [<ffffffffa04054e9>] add_inode_ref+0x319/0x3f0 [btrfs]
     [<ffffffffa0407087>] replay_one_buffer+0x2c7/0x390 [btrfs]
     [<ffffffffa040444a>] walk_down_log_tree+0x32a/0x480 [btrfs]
     [<ffffffffa0404695>] walk_log_tree+0xf5/0x240 [btrfs]
     [<ffffffffa0406cc0>] btrfs_recover_log_trees+0x250/0x350 [btrfs]
     [<ffffffffa0406dc0>] ? btrfs_recover_log_trees+0x350/0x350 [btrfs]
     [<ffffffffa03d18b2>] open_ctree+0x1442/0x17d0 [btrfs]
    This comes from that while replaying an inode ref item, we forget to
    check those old conflicting DIR_ITEM and DIR_INDEX items in fs/file tree,
    then we will come to conflict corners which lead to BUG_ON().
    Signed-off-by: Liu Bo <>
    Tested-by: Andy Lutomirski <>
    Signed-off-by: Chris Mason <>
    Signed-off-by: Greg Kroah-Hartman <>
    liub committed with gregkh Aug 6, 2011
  25. @kaysievers @gregkh

    loop: fix deadlock when sysfs and LOOP_CLR_FD race against each other

    commit 05eb0f2 upstream.
    LOOP_CLR_FD takes lo->lo_ctl_mutex and tries to remove the loop sysfs
    files. Sysfs calls show() and waits for lo->lo_ctl_mutex. LOOP_CLR_FD
    waits for show() to finish to remove the sysfs file.
      cat /sys/class/block/loop0/loop/backing_file
        ? loop_attr_do_show_backing_file+0x2f/0xd0 [loop]
        ? loop_attr_do_show_backing_file+0x2f/0xd0 [loop]
        loop_attr_do_show_backing_file+0x2f/0xd0 [loop]
        ? sysfs_read_file+0x86/0x1a0
        ? __get_free_pages+0x12/0x50
        ? try_to_wake_up+0x2a0/0x2a0
        ? sysfs_addrm_finish+0x43/0x70
        ? sysfs_addrm_start+0x1d/0x20
        loop_clr_fd+0x1dc/0x3f0 [loop]
        lo_ioctl+0x223/0x7a0 [loop]
    Instead of taking the lo_ctl_mutex from sysfs code, take the inner
    lo->lo_lock, to protect the access to the backing_file data.
    Thanks to Tejun for help debugging and finding a solution.
    Cc: Milan Broz <>
    Cc: Tejun Heo <>
    Signed-off-by: Kay Sievers <>
    Signed-off-by: Jens Axboe <>
    Signed-off-by: Greg Kroah-Hartman <>
    kaysievers committed with gregkh Jul 31, 2011
Something went wrong with that request. Please try again.