Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on May 26, 2010
  1. @gregkh

    Linux 2.6.27.47

    gregkh authored
  2. @gregkh

    nfsd: fix vm overcommit crash fix #2

    Junjiro R. Okajima authored gregkh committed
    commit 1b79cd0 upstream.
    
    The previous patch from Alan Cox ("nfsd: fix vm overcommit crash",
    commit 731572d) fixed the problem where
    knfsd crashes on exported shmemfs objects and strict overcommit is set.
    
    But the patch forgot supporting the case when CONFIG_SECURITY is
    disabled.
    
    This patch copies a part of his fix which is mainly for detecting a bug
    earlier.
    
    Acked-by: James Morris <jmorris@namei.org>
    Signed-off-by: Alan Cox <alan@redhat.com>
    Signed-off-by: Junjiro R. Okajima <hooanon05@yahoo.co.jp>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  3. @gregkh

    nfsd: fix vm overcommit crash

    Alan Cox authored gregkh committed
    commit 731572d upstream.
    
    Junjiro R.  Okajima reported a problem where knfsd crashes if you are
    using it to export shmemfs objects and run strict overcommit.  In this
    situation the current->mm based modifier to the overcommit goes through a
    NULL pointer.
    
    We could simply check for NULL and skip the modifier but we've caught
    other real bugs in the past from mm being NULL here - cases where we did
    need a valid mm set up (eg the exec bug about a year ago).
    
    To preserve the checks and get the logic we want shuffle the checking
    around and add a new helper to the vm_ security wrappers
    
    Also fix a current->mm reference in nommu that should use the passed mm
    
    [akpm@linux-foundation.org: coding-style fixes]
    [akpm@linux-foundation.org: fix build]
    Reported-by: Junjiro R. Okajima <hooanon05@yahoo.co.jp>
    Acked-by: James Morris <jmorris@namei.org>
    Signed-off-by: Alan Cox <alan@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  4. @gregkh

    i2c-tiny-usb: Fix on big-endian systems

    Jean Delvare authored gregkh committed
    commit 1c010ff upstream.
    
    The functionality bit vector is always returned as a little-endian
    32-bit number by the device, so it must be byte-swapped to the host
    endianness.
    
    On the other hand, the delay value is handled by the USB stack, so no
    byte swapping is needed on our side.
    
    This fixes bug #15105:
    http://bugzilla.kernel.org/show_bug.cgi?id=15105
    
    Reported-by: Jens Richter <jens@richter-stutensee.de>
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
    Tested-by: Jens Richter <jens@richter-stutensee.de>
    Cc: Till Harbaum <till@harbaum.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  5. @gregkh

    i2c-i801: Don't use the block buffer for I2C block writes

    Jean Delvare authored gregkh committed
    commit c074c39 upstream.
    
    Experience has shown that the block buffer can only be used for SMBus
    (not I2C) block transactions, even though the datasheet doesn't
    mention this limitation.
    
    Reported-by: Felix Rubinstein <felixru@gmail.com>
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
    Cc: Oleg Ryjkov <oryjkov@gmail.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  6. @gregkh

    hwmon: (w83781d) Request I/O ports individually for probing

    Jean Delvare authored gregkh committed
    commit b0bcdd3 upstream.
    
    Different motherboards have different PNP declarations for
    W83781D/W83782D chips. Some declare the whole range of I/O ports (8
    ports), some declare only the useful ports (2 ports at offset 5) and
    some declare fancy ranges, for example 4 ports at offset 4. To
    properly handle all cases, request all ports individually for probing.
    After we have determined that we really have a W83781D or W83782D
    chip, the useful port range will be requested again, as a single
    block.
    
    I did not see a board which needs this yet, but I know of one for lm78
    driver and I'd like to keep the logic of these two drivers in sync.
    
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  7. @gregkh

    svc: Clean up deferred requests on transport destruction

    Tom Tucker authored gregkh committed
    commit 22945e4 upstream.
    
    A race between svc_revisit and svc_delete_xprt can result in
    deferred requests holding references on a transport that can never be
    recovered because dead transports are not enqueued for subsequent
    processing.
    
    Check for XPT_DEAD in revisit to clean up completing deferrals on a dead
    transport and sweep a transport's deferred queue to do the same for queued
    but unprocessed deferrals.
    
    Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
    Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
    Cc: roma1390 <roma1390@gmail.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  8. @gregkh

    libata: retry FS IOs even if it has failed with AC_ERR_INVALID

    Tejun Heo authored gregkh committed
    commit 534ead7 upstream.
    
    libata currently doesn't retry if a command fails with AC_ERR_INVALID
    assuming that retrying won't get it any further even if retried.
    However, a failure may be classified as invalid through hardware
    glitch (incorrect reading of the error register or firmware bug) and
    there isn't whole lot to gain by not retrying as actually invalid
    commands will be failed immediately.  Also, commands serving FS IOs
    are extremely unlikely to be invalid.  Retry FS IOs even if it's
    marked invalid.
    
    Transient and incorrect invalid failure was seen while debugging
    firmware related issue on Samsung n130 on bko#14314.
    
      http://bugzilla.kernel.org/show_bug.cgi?id=14314
    
    Signed-off-by: Tejun Heo <tj@kernel.org>
    Reported-by: Johannes Stezenbach <js@sig21.net>
    Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  9. @gregkh

    libata: ensure NCQ error result taskfile is fully initialized before …

    Jeff Garzik authored gregkh committed
    …returning it via qc->result_tf.
    
    commit a09bf4c upstream.
    
    Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  10. @gregkh

    i2c: Fix probing of FSC hardware monitoring chips

    Jean Delvare authored gregkh committed
    commit b1d4b39 upstream.
    
    Some FSC hardware monitoring chips (Syleus at least) doesn't like
    quick writes we typically use to probe for I2C chips. Use a regular
    byte read instead for the address they live at (0x73). These are the
    only known chips living at this address on PC systems.
    
    For clarity, this fix should not be needed for kernels 2.6.30 and
    later, as we started instantiating the hwmon devices explicitly based
    on DMI data. Still, this fix is valuable in the following two cases:
    * Support for recent FSC chips on older kernels. The DMI-based device
      instantiation is more difficult to backport than the device support
      itself.
    * Case where the DMI-based device instantiation fails, whatever the
      reason. We fall back to probing in that case, so it should work.
    
    This fixes kernel bug #15634:
    https://bugzilla.kernel.org/show_bug.cgi?id=15634
    
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
    Acked-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  11. @chucklever @gregkh

    NFS: rsize and wsize settings ignored on v4 mounts

    chucklever authored gregkh committed
    commit 356e76b upstream.
    
    NFSv4 mounts ignore the rsize and wsize mount options, and always use
    the default transfer size for both.  This seems to be because all
    NFSv4 mounts are now cloned, and the cloning logic doesn't copy the
    rsize and wsize settings from the parent nfs_server.
    
    I tested Fedora's 2.6.32.11-99 and it seems to have this problem as
    well, so I'm guessing that .33, .32, and perhaps older kernels have
    this issue as well.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  12. @gregkh

    nfs d_revalidate() is too trigger-happy with d_drop()

    Al Viro authored gregkh committed
    commit d9e80b7 upstream.
    
    If dentry found stale happens to be a root of disconnected tree, we
    can't d_drop() it; its d_hash is actually part of s_anon and d_drop()
    would simply hide it from shrink_dcache_for_umount(), leading to
    all sorts of fun, including busy inodes on umount and oopsen after
    that.
    
    Bug had been there since at least 2006 (commit c636eb already has it),
    so it's definitely -stable fodder.
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  13. @error27 @gregkh

    USB: fix testing the wrong variable in fs_create_by_name()

    error27 authored gregkh committed
    commit fa7fe7a upstream.
    
    There is a typo here.  We should be testing "*dentry" which was just
    assigned instead of "dentry".  This could result in dereferencing an
    ERR_PTR inside either usbfs_mkdir() or usbfs_create().
    
    Signed-off-by: Dan Carpenter <error27@gmail.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  14. @neilbrown @gregkh

    nfsd4: bug in read_buf

    neilbrown authored gregkh committed
    commit 2bc3c11 upstream.
    
    When read_buf is called to move over to the next page in the pagelist
    of an NFSv4 request, it sets argp->end to essentially a random
    number, certainly not an address within the page which argp->p now
    points to.  So subsequent calls to READ_BUF will think there is much
    more than a page of spare space (the cast to u32 ensures an unsigned
    comparison) so we can expect to fall off the end of the second
    page.
    
    We never encountered thsi in testing because typically the only
    operations which use more than two pages are write-like operations,
    which have their own decoding logic.  Something like a getattr after a
    write may cross a page boundary, but it would be very unusual for it to
    cross another boundary after that.
    
    Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  15. @gregkh

    clockevent: Prevent dead lock on clockevents_lock

    Suresh Siddha authored gregkh committed
    This is a merge of two mainline commits, intended
    for stable@kernel.org submission for 2.6.27 kernel.
    
    commit f833bab
    and
    
    commit 918aae4
    Changelog of both:
    
        Currently clockevents_notify() is called with interrupts enabled at
        some places and interrupts disabled at some other places.
    
        This results in a deadlock in this scenario.
    
        cpu A holds clockevents_lock in clockevents_notify() with irqs enabled
        cpu B waits for clockevents_lock in clockevents_notify() with irqs disabled
        cpu C doing set_mtrr() which will try to rendezvous of all the cpus.
    
        This will result in C and A come to the rendezvous point and waiting
        for B. B is stuck forever waiting for the spinlock and thus not
        reaching the rendezvous point.
    
        Fix the clockevents code so that clockevents_lock is taken with
        interrupts disabled and thus avoid the above deadlock.
    
        Also call lapic_timer_propagate_broadcast() on the destination cpu so
        that we avoid calling smp_call_function() in the clockevents notifier
        chain.
    
        This issue left us wondering if we need to change the MTRR rendezvous
        logic to use stop machine logic (instead of smp_call_function) or add
        a check in spinlock debug code to see if there are other spinlocks
        which gets taken under both interrupts enabled/disabled conditions.
    
        Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
        Cc: "Brown Len" <len.brown@intel.com>
        Cc: stable@kernel.org
        LKML-Reference: <1250544899.2709.210.camel@sbs-t61.sc.intel.com>
        Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    
        I got following warning on ia64 box:
          In function 'acpi_processor_power_verify':
          642: warning: passing argument 2 of 'smp_call_function_single' from
          incompatible pointer type
    
        This smp_call_function_single() was introduced by a commit
        f833bab:
    
        The problem is that the lapic_timer_propagate_broadcast() has 2 versions:
        One is real code that modified in the above commit, and the other is NOP
        code that used when !ARCH_APICTIMER_STOPS_ON_C3:
    
          static void lapic_timer_propagate_broadcast(struct acpi_processor *pr) { }
    
        So I got warning because of !ARCH_APICTIMER_STOPS_ON_C3.
    
        We really want to do nothing here on !ARCH_APICTIMER_STOPS_ON_C3, so
        modify lapic_timer_propagate_broadcast() of real version to use
        smp_call_function_single() in it.
    
        Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
        Acked-by: Suresh Siddha <suresh.b.siddha@intel.com>
        Signed-off-by: Len Brown <len.brown@intel.com>
    
    Signed-off-by: Thomas Renninger <trenn@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  16. @gregkh

    trace: Fix inappropriate substraction on tracing_pages_allocated in t…

    Wang Sheng-Hui authored gregkh committed
    …race_free_page()
    
    [No matching upstream git commit id as it was fixed differently due to a
    rewrite of the tracing code there.]
    
    For normal case, the code in trace_free_page() do once more substraction
    on tracing_pages_allocated, but for CONFIG_TRACER_MAX_TRACE  it doesn't
    take the freed page into account. That's not consistent with
    trace_alloc_page().  Well, for there are no message related with this,
    so we cannot observe its incorrect state when the kernel doesn't define
    "CONFIG_TRACER_MAX_TRACE". If you add some pr_info() as
    trace_alloc_page(), you may notice it.
    
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Frederic Weisbecker <fweisbec@gmail.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Li Zefan <lizf@cn.fujitsu.com>
    Signed-off-by: Wang Sheng-Hui <crosslonelyover@gmail.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  17. @gregkh

    megaraid_sas: fix for 32bit apps

    Tomas Henzl authored gregkh committed
    commit b3dc1a2 upstream.
    
    It looks like this patch -
    
    commit 7b2519a
    Author: Yang, Bo <Bo.Yang@lsi.com>
    Date:   Tue Oct 6 14:52:20 2009 -0600
    
        [SCSI] megaraid_sas: fix 64 bit sense pointer truncation
    
    has caused a problem for 32bit programs with 64bit os -
    
    http://bugzilla.kernel.org/show_bug.cgi?id=15001
    
    fix by converting the user space 32bit pointer to a 64 bit one when
    needed.
    
    [jejb: fix up some 64 bit warnings]
    Signed-off-by: Tomas Henzl <thenzl@redhat.com>
    Cc: Bo Yang <Bo.Yang@lsi.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  18. @utrace @gregkh

    tty: release_one_tty() forgets to put pids

    utrace authored gregkh committed
    commit 6da8d86 upstream.
    
    release_one_tty(tty) can be called when tty still has a reference
    to pgrp/session. In this case we leak the pid.
    
    Signed-off-by: Oleg Nesterov <oleg@redhat.com>
    Reported-by: Catalin Marinas <catalin.marinas@arm.com>
    Reported-and-tested-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Acked-by: Linus Torvalds <torvalds@linux-foundation.org>
    Acked-by: Eric W. Biederman <ebiederm@xmission.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  19. @kvaneesh @gregkh

    vfs: Remove the range_cont writeback mode.

    kvaneesh authored gregkh committed
    commit 74baaaa upstream.
    
    Ext4 was the only user of range_cont writeback mode and ext4 switched
    to a different method. So remove the range_cont mode which is not used
    in the kernel.
    
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
    CC: linux-fsdevel@vger.kernel.org
    Signed-off-by: Jayson R. King <dev@jaysonking.com>
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  20. @kvaneesh @gregkh

    ext4: Use tag dirty lookup during mpage_da_submit_io

    kvaneesh authored gregkh committed
    commit af6f029 upstream.
    
    This enables us to drop the range_cont writeback mode
    use from ext4_da_writepages.
    
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
    Signed-off-by: Jayson R. King <dev@jaysonking.com>
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  21. @kvaneesh @gregkh

    ext4: Retry block allocation if we have free blocks left

    kvaneesh authored gregkh committed
    commit df22291 upstream.
    
    When we truncate files, the meta-data blocks released are not reused
    untill we commit the truncate transaction.  That means delayed get_block
    request will return ENOSPC even if we have free blocks left.  Force a
    journal commit and retry block allocation if we get ENOSPC with free
    blocks left.
    
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
    Signed-off-by: Mingming Cao <cmm@us.ibm.com>
    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Jayson R. King <dev@jaysonking.com>
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  22. @kvaneesh @gregkh

    ext4: Retry block reservation

    kvaneesh authored gregkh committed
    commit 030ba6b upstream.
    
    During block reservation if we don't have enough blocks left, retry
    block reservation with smaller block counts.  This makes sure we try
    fallocate and DIO with smaller request size and don't fail early.  The
    delayed allocation reservation cannot try with smaller block count. So
    retry block reservation to handle temporary disk full conditions.  Also
    print free blocks details if we fail block allocation during writepages.
    
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
    Signed-off-by: Mingming Cao <cmm@us.ibm.com>
    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Jayson R. King <dev@jaysonking.com>
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  23. @kvaneesh @gregkh

    ext4: Add percpu dirty block accounting.

    kvaneesh authored gregkh committed
    commit 6bc6e63 upstream.
    
    This patch adds dirty block accounting using percpu_counters.  Delayed
    allocation block reservation is now done by updating dirty block
    counter.  In a later patch we switch to non delalloc mode if the
    filesystem free blocks is greater than 150% of total filesystem dirty
    blocks
    
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
    Signed-off-by: Mingming Cao<cmm@us.ibm.com>
    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Jayson R. King <dev@jaysonking.com>
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  24. @kvaneesh @gregkh

    ext4: Make sure all the block allocation paths reserve blocks

    kvaneesh authored gregkh committed
    commit a30d542 upstream.
    
    With delayed allocation we need to make sure block are reserved before
    we attempt to allocate them. Otherwise we get block allocation failure
    (ENOSPC) during writepages which cannot be handled. This would mean
    silent data loss (We do a printk stating data will be lost). This patch
    updates the DIO and fallocate code path to do block reservation before
    block allocation. This is needed to make sure parallel DIO and fallocate
    request doesn't take block out of delayed reserve space.
    
    When free blocks count go below a threshold we switch to a slow patch
    which looks at other CPU's accumulated percpu counter values.
    
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Jayson R. King <dev@jaysonking.com>
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  25. @gregkh

    percpu counter: clean up percpu_counter_sum_and_set()

    Mingming Cao authored gregkh committed
    commit 1f7c14c upstream.
    
    percpu_counter_sum_and_set() and percpu_counter_sum() is the same except
    the former updates the global counter after accounting.  Since we are
    taking the fbc->lock to calculate the precise value of the counter in
    percpu_counter_sum() anyway, it should simply set fbc->count too, as the
    percpu_counter_sum_and_set() does.
    
    This patch merges these two interfaces into one.
    
    Signed-off-by: Mingming Cao <cmm@us.ibm.com>
    Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Cc: <linux-ext4@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Jayson R. King <dev@jaysonking.com>
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
  26. @kvaneesh @gregkh

    ext4: invalidate pages if delalloc block allocation fails.

    kvaneesh authored gregkh committed
    commit c4a0c46 upstream.
    
    We are a bit agressive in invalidating all the pages. But
    it is ok because we really don't know why the block allocation
    failed and it is better to come of the writeback path
    so that user can look for more info.
    
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
    Signed-off-by: Jayson R. King <dev@jaysonking.com>
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  27. @error27 @gregkh

    ALSA: mixart: range checking proc file

    error27 authored gregkh committed
    commit b0cc58a upstream.
    
    The original code doesn't take into consideration that the value of
    MIXART_BA0_SIZE - pos can be less than zero which would lead to a large
    unsigned value for "count".
    
    Also I moved the check that read size is a multiple of 4 bytes below
    the code that adjusts "count".
    
    Signed-off-by: Dan Carpenter <error27@gmail.com>
    Acked-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Commits on Apr 1, 2010
  1. @gregkh

    Linux 2.6.27.46

    gregkh authored
  2. @gregkh

    hwmon: (coretemp) Add missing newline to dev_warn() message

    Dean Nelson authored gregkh committed
    commit 4d7a564 upstream.
    
    Add missing newline to dev_warn() message string. This is more of an issue
    with older kernels that don't automatically add a newline if it was missing
    from the end of the previous line.
    
    Signed-off-by: Dean Nelson <dnelson@redhat.com>
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  3. @gregkh

    USB: fix usbfs regression

    Alan Stern authored gregkh committed
    commit 7152b59 upstream.
    
    This patch (as1352) fixes a bug in the way isochronous input data is
    returned to userspace for usbfs transfers.  The entire buffer must be
    copied, not just the first actual_length bytes, because the individual
    packets will be discontiguous if any of them are short.
    
    Reported-by: Markus Rechberger <mrechberger@gmail.com>
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  4. @kosaki @gregkh

    tmpfs: cleanup mpol_parse_str()

    kosaki authored gregkh committed
    commit 926f2ae upstream.
    
    mpol_parse_str() made lots 'err' variable related bug.  Because it is ugly
    and reviewing unfriendly.
    
    This patch simplifies it.
    
    Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
    Cc: Ravikiran Thirumalai <kiran@scalex86.org>
    Cc: Christoph Lameter <cl@linux-foundation.org>
    Cc: Mel Gorman <mel@csn.ul.ie>
    Acked-by: Lee Schermerhorn <lee.schermerhorn@hp.com>
    Cc: Hugh Dickins <hugh.dickins@tiscali.co.uk>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  5. @kosaki @gregkh

    doc: add the documentation for mpol=local

    kosaki authored gregkh committed
    commit 5574169 upstream.
    
    commit 3f226aa (mempolicy: support mpol=local tmpfs mount option) added
    new mpol=local mount option.  but it didn't add a documentation.
    
    This patch does it.
    
    Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
    Cc: Ravikiran Thirumalai <kiran@scalex86.org>
    Cc: Christoph Lameter <cl@linux-foundation.org>
    Cc: Mel Gorman <mel@csn.ul.ie>
    Acked-by: Lee Schermerhorn <lee.schermerhorn@hp.com>
    Cc: Hugh Dickins <hugh.dickins@tiscali.co.uk>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  6. @kosaki @gregkh

    tmpfs: handle MPOL_LOCAL mount option properly

    kosaki authored gregkh committed
    commit 12821f5 upstream.
    
    commit 71fe804 (mempolicy: use struct mempolicy pointer in
    shmem_sb_info) added mpol=local mount option.  but its feature is broken
    since it was born.  because such code always return 1 (i.e.  mount
    failure).
    
    This patch fixes it.
    
    Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
    Cc: Ravikiran Thirumalai <kiran@scalex86.org>
    Cc: Christoph Lameter <cl@linux-foundation.org>
    Cc: Mel Gorman <mel@csn.ul.ie>
    Acked-by: Lee Schermerhorn <lee.schermerhorn@hp.com>
    Cc: Hugh Dickins <hugh.dickins@tiscali.co.uk>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  7. @kosaki @gregkh

    tmpfs: mpol=bind:0 don't cause mount error.

    kosaki authored gregkh committed
    commit d69b2e6 upstream.
    
    Currently, following mount operation cause mount error.
    
    % mount -t tmpfs -ompol=bind:0 none /tmp
    
    Because commit 71fe804 (mempolicy: use struct mempolicy pointer in
    shmem_sb_info) corrupted MPOL_BIND parse code.
    
    This patch restore the needed one.
    
    Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
    Cc: Ravikiran Thirumalai <kiran@scalex86.org>
    Cc: Christoph Lameter <cl@linux-foundation.org>
    Cc: Mel Gorman <mel@csn.ul.ie>
    Acked-by: Lee Schermerhorn <lee.schermerhorn@hp.com>
    Cc: Hugh Dickins <hugh.dickins@tiscali.co.uk>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  8. @gregkh

    tmpfs: fix oops on mounts with mpol=default

    Ravikiran G Thirumalai authored gregkh committed
    commit 413b43d upstream.
    
    Fix an 'oops' when a tmpfs mount point is mounted with the mpol=default
    mempolicy.
    
    Upon remounting a tmpfs mount point with 'mpol=default' option, the mount
    code crashed with a null pointer dereference.  The initial problem report
    was on 2.6.27, but the problem exists in mainline 2.6.34-rc as well.  On
    examining the code, we see that mpol_new returns NULL if default mempolicy
    was requested.  This 'NULL' mempolicy is accessed to store the node mask
    resulting in oops.
    
    The following patch fixes it.
    
    Signed-off-by: Ravikiran Thirumalai <kiran@scalex86.org>
    Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
    Cc: Christoph Lameter <cl@linux-foundation.org>
    Cc: Mel Gorman <mel@csn.ul.ie>
    Acked-by: Lee Schermerhorn <lee.schermerhorn@hp.com>
    Cc: Hugh Dickins <hugh.dickins@tiscali.co.uk>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Something went wrong with that request. Please try again.