Permalink
Commits on Nov 8, 2009
  1. Merge branch 'pf-configs'

    Oleksandr Natalenko committed Nov 8, 2009
  2. Merge branch 'pf-version'

    Oleksandr Natalenko committed Nov 8, 2009
  3. Merge remote branch 'combined/combined'

    Oleksandr Natalenko committed Nov 8, 2009
  4. Merge remote branch 'bfq/bfq'

    Oleksandr Natalenko committed Nov 8, 2009
  5. Merge remote branch 'cfq/cfq'

    Oleksandr Natalenko committed Nov 8, 2009
  6. Merge remote branch 'zen-sched/zen-sched'

    Oleksandr Natalenko committed Nov 8, 2009
  7. added config for Dell Inspiron 1525

    Oleksandr Natalenko committed Nov 8, 2009
  8. bump to pf7

    Oleksandr Natalenko committed Nov 8, 2009
Commits on Nov 6, 2009
  1. fix typo

    Brandon Berhent committed Nov 6, 2009
  2. 2.6.32 CFQ (many fixes/updates)

    Brandon Berhent committed Nov 6, 2009
  3. bfq: few fixes

    Brandon Berhent committed Nov 6, 2009
  4. BFS 310

    Brandon Berhent committed Nov 6, 2009
Commits on Oct 31, 2009
  1. Fix detection of end of storage.

    The swap priority changes introduced a bug in our detection
    of the end of storage. We should now be looking for chain number
    being -1, not #chains. Since this #define is only used in one
    place, switch to just inlining it.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 31, 2009
  2. Combine header reservation functions.

    Combine the functions in the swap and file allocators that handle
    reserving space for the header. Put the combined function in
    block_io.c.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 31, 2009
  3. Shift code from extent.c to block_io.c.

    Shift the code that's specific to block chains to tuxonice_block_io.c.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 31, 2009
  4. Remove redundant lines in go_next_page.

    Remove a couple of lines when update variables that aren't
    subsequently used.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 31, 2009
  5. Fix headerlockations info some more.

    The previous patch fixed it for me, but apparently not well
    enough to address the issues others were seeing. Thanks to
    Francois Valenduc for telling me this and confirming that
    this patch gets things working for him.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 31, 2009
  6. Fix swap/headerlocations sysfs entry.

    I finally found the bug in the headerlocations code that was causing
    us to ignore some swap entries when telling the user what they need
    to put in resume=. Really simple - reversed logic. I must have been
    blind!
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 31, 2009
Commits on Oct 30, 2009
  1. Better checksum error reporting.

    If checksumming a page did return an error, we should really tell the
    user that it did, instead of aborting without saying why. Add a printk.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 30, 2009
  2. Fix disabling escape key.

    I received a bug report saying that the sysfs entry for disabling the
    escape key wasn't working. It was right - and for goodness knows how
    long. This patch fixes the issue.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 30, 2009
  3. Export binary signature through sysfs.

    Provide the hibernate script with a new means of getting the
    binary signature - via /sys/power/tuxonice/binary_signature.
    Some distros seem to be having problems getting the binary signature
    file into their packages.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 30, 2009
  4. Swap priority support.

    Add support for utilising swap priorities in TuxOnIce. We remove the simple
    striping that was added as a stop-gap, and add code that remembers and uses
    priorities given at swapon time.
    
    I plan to build on this in later patches, shifting a lot of the code that's
    currently duplicated in the swap and file allocators to the block I/O module.
    As part of this TuxOnIce will gain support for using both swap and a file
    in the same image (you'll be able to specify a priority for the file, too).
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 30, 2009
  5. Fix imbalance in error path in getting module refs

    In the start_anything error path, we fail to put our reference to modules
    if an error occurs afterwards. Add the put_modules call to the error path.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 30, 2009
Commits on Oct 28, 2009
  1. Use set_cpus_allowed_ptr.

    In binding the main TuxOnIce thread to cpu 0 (and undoing it), use
    set_cpus_allowed_ptr instead of set_cpus_allowed, for compatability
    with new cpumask options that don't always define set_cpus_allowed.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
    Nigel Cunningham committed Oct 28, 2009
Commits on Oct 23, 2009
  1. Merge branch 'origin' into combined

    Nigel Cunningham committed Oct 23, 2009
Commits on Oct 22, 2009
  1. Linux 2.6.31.5

    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    gregkh committed Oct 22, 2009
  2. tty: Make flush_to_ldisc() locking more robust

    commit c8e3314 upstream.
    
    The locking logic in this function is extremely subtle, and it broke
    when we started doing potentially concurrent 'flush_to_ldisc()' calls in
    commit e043e42 ("pty: avoid forcing
    'low_latency' tty flag").
    
    The code in flush_to_ldisc() used to set 'tty->buf.head' to NULL, with
    the intention that this would then cause any other concurrent calls to
    not do anything (locking note: we have to drop the buf.lock over the
    call to ->receive_buf that can block, which is why we can have
    concurrency here at all in the first place).
    
    It also used to set the TTY_FLUSHING bit, which would then cause any
    concurrent 'tty_buffer_flush()' to not free all the tty buffers and
    clear 'tty->buf.tail'.  And with 'buf.head' being NULL, and 'buf.tail'
    being non-NULL, new data would never touch 'buf.head'.
    
    Does that sound a bit too subtle? It was.  If another concurrent call to
    'flush_to_ldisc()' were to come in, the NULL buf.head would indeed cause
    it to not process the buffer list, but it would still clear TTY_FLUSHING
    afterwards, making the buffer protection against 'tty_buffer_flush()' no
    longer work.
    
    So this clears it all up.  We depend purely on TTY_FLUSHING for handling
    re-entrancy, and stop playing games with the buffer list entirely.  In
    fact, the buffer list handling is now robust enough that we could
    probably stop doing the whole "protect against 'tty_buffer_flush()'"
    thing entirely.
    
    However, Alan also points out that we would probably be better off
    simplifying the locking even further, and just take the tty ldisc_mutex
    around all the buffer flushing calls.  That seems like a good idea, but
    in the meantime this is a conceptually minimal fix (with the patch
    itself being bigger than required just to clean the code up and make it
    readable).
    
    This fixes keyboard trouble under X:
    
    	http://bugzilla.kernel.org/show_bug.cgi?id=14388
    
    Reported-and-tested-by: Frédéric Meunier <fredlwm@gmail.com>
    Reported-and-tested-by: Boyan <btanastasov@yahoo.co.uk>
    Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
    Cc: Paul Fulghum <paulkf@microgate.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    torvalds committed with gregkh Oct 14, 2009
  3. mac80211: fix vlan and optimise RX

    commit fbc44bf upstream.
    
    When receiving data frames, we can send them only to
    the interface they belong to based on transmitting
    station (this doesn't work for probe requests). Also,
    don't try to handle other frames for AP_VLAN at all
    since those interface should only receive data.
    
    Additionally, the transmit side must check that the
    station we're sending a frame to is actually on the
    interface we're transmitting on, and not transmit
    packets to functions that live on other interfaces,
    so validate that as well.
    
    Another bug fix is needed in sta_info.c where in the
    VLAN case when adding/removing stations we overwrite
    the sdata variable we still need.
    
    Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    jmberg committed with gregkh Oct 1, 2009
  4. iwlwifi: incorrect method used for finding valid OTP blocks

    commit 2facba7 upstream.
    
    The address stored in the next link address is a word address but when
    reading the OTP blocks, a byte address is used. Also if the blocks are
    full and the last link pointer is not zero, then none of the blocks are
    valid so return an error.
    
    The algorithm is simply valid blocks have a next address and that
    address's contents is zero.
    
    Using the wrong address for the next link address gets arbitrary data,
    obviously. In cases seen, the first block is considered valid when it is not.
    
    If the block has in fact been invalidated there may be old data or
    there may be no data, bad data, or partial data, there is no way of
    telling. Without this patch it is possible that a device with valid OTP data
    is unable to work.
    
    Signed-off-by: Jay Sternberg <jay.e.sternberg@intel.com>
    Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    jesternberg committed with gregkh Oct 2, 2009
  5. usb-storage: Workaround devices with bogus sense size

    commit b8430e1 upstream.
    
    usb-storage: Workaround devices with bogus sense size
    
    Some devices, such as Huawei E169, advertise more than the standard
    amount of sense data, causing us to set US_FL_SANE_SENSE, assuming
    they support it. However, they subsequently fail the request sense
    with that size.
    
    This works around it generically. When a sense request fails due to
    a device returning an error, US_FL_SANE_SENSE was set, and that sense
    request used a larger sense size, we retry with a smaller size before
    giving up.
    
    Based on an original patch by Ben Efros <ben@pc-doctor.com>
    
    Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Acked-by: Alan Stern <stern@rowland.harvard.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    ozbenh committed with gregkh Oct 13, 2009
  6. Staging: rt2860sta: prevent a panic when disabling when associated

    commit 0af4916 upstream.
    
    This fixes a panic which is triggered when the hardware "disappears" from
    beneath the driver, i.e. when wireless is toggled off via Fn-F2 on various
    EeePC models.
    
    Ref. bug report http://bugzilla.kernel.org/show_bug.cgi?id=13390
              panic http://bugzilla.kernel.org/attachment.cgi?id=21928
    
    Signed-off-by: Darren Salt <linux@youmustbejoking.demon.co.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Darren Salt committed with gregkh Oct 14, 2009
  7. sysfs: Allow sysfs_notify_dirent to be called from interrupt context.

    commit 83db93f upstream.
    
    sysfs_notify_dirent is a simple atomic operation that can be used to
    alert user-space that new data can be read from a sysfs attribute.
    
    Unfortunately it cannot currently be called from non-process context
    because of its use of spin_lock which is sometimes taken with
    interrupts enabled.
    
    So change all lockers of sysfs_open_dirent_lock to disable interrupts,
    thus making sysfs_notify_dirent safe to be called from non-process
    context (as drivers/md does in md_safemode_timeout).
    
    sysfs_get_open_dirent is (documented as being) only called from
    process context, so it uses spin_lock_irq.  Other places
    use spin_lock_irqsave.
    
    The usage for sysfs_notify_dirent in md_safemode_timeout was
    introduced in 2.6.28, so this patch is suitable for that and more
    recent kernels.
    
    Reported-by: Joel Andres Granados <jgranado@redhat.com>
    Signed-off-by: NeilBrown <neilb@suse.de>
    Signed-off-by: Dan Williams <dan.j.williams@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    neilbrown committed with gregkh Sep 15, 2009
  8. bsdacct: switch credentials for writing to the accounting file

    commit d8e180d upstream.
    
    When process accounting is enabled, every exiting process writes a log to
    the account file.  In addition, every once in a while one of the exiting
    processes checks whether there's enough free space for the log.
    
    SELinux policy may or may not allow the exiting process to stat the fs.
    So unsuspecting processes start generating AVC denials just because
    someone enabled process accounting.
    
    For these filesystem operations, the exiting process's credentials should
    be temporarily switched to that of the process which enabled accounting,
    because it's really that process which wanted to have the accounting
    information logged.
    
    Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
    Acked-by: David Howells <dhowells@redhat.com>
    Acked-by: Serge Hallyn <serue@us.ibm.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: James Morris <jmorris@namei.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    michich committed with gregkh Aug 20, 2009
  9. ALSA: Don't assume i2c device probing always succeeds

    commit 18c4078 upstream.
    
    The client->driver pointer can be NULL when i2c-device probing fails
    in i2c_new_device().  This patch adds the NULL checks for client->driver
    and return the error instead of blind assumption of driver availability.
    
    Reported-by: Tim Shepard <shep@alum.mit.edu>
    Cc: Jean Delvare <khali@linux-fr.org>
    Cc: Johannes Berg <johannes@sipsolutions.net>
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    tiwai committed with gregkh Oct 1, 2009
  10. i2c: Hide probe errors caused by ACPI resource conflicts

    commit 18669ea upstream.
    
    When an ACPI resource conflict is detected, error messages are already
    printed by ACPI. There's no point in causing the driver core to print
    more error messages, so return one of the error codes for which no
    message is printed.
    
    This fixes bug #14293:
    http://bugzilla.kernel.org/show_bug.cgi?id=14293
    
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
    Jean Delvare committed with gregkh Oct 4, 2009