Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Oct 22, 2009
  1. @gregkh


    gregkh authored
    Signed-off-by: Greg Kroah-Hartman <>
  2. @jhovold @gregkh

    USB: digi_acceleport: Fix broken unthrottle.

    jhovold authored gregkh committed
    commit ba6b702 upstream.
    This patch fixes a regression introduced in
    Signed-off-by: Johan Hovold <>
    Acked-by: Oliver Neukum <>
    Signed-off-by: Greg Kroah-Hartman <>
  3. @gregkh

    SCSI: Fix protection scsi_data_buffer leak

    Martin K. Petersen authored gregkh committed
    commit b4c2554 upstream.
    We would leak a scsi_data_buffer if the free_list command was of the
    protected variety.
    Reported-by: Boaz Harrosh <>
    Signed-off-by: Martin K. Petersen <>
    Signed-off-by: James Bottomley <>
    Signed-off-by: Greg Kroah-Hartman <>
  4. @gregkh

    usb-serial: fix crash when sub-driver updates firmware

    Alan Stern authored gregkh committed
    commit 0a3c854 upstream.
    This patch (as1244) fixes a crash in usb-serial that occurs when a
    sub-driver returns a positive value from its attach method, indicating
    that new firmware was loaded and the device will disconnect and
    reconnect.  The usb-serial core then skips the step of registering the
    port devices; when the disconnect occurs, the attempt to unregister
    the ports fails dramatically.
    This problem shows up with Keyspan devices and it might affect others
    as well.
    When the attach method returns a positive value, the patch sets
    num_ports to 0.  This tells usb_serial_disconnect() not to try
    unregistering any of the ports; instead they are cleaned up by
    Signed-off-by: Alan Stern <>
    Tested-by: Benjamin Herrenschmidt <>
    Signed-off-by: Greg Kroah-Hartman <>
Commits on Oct 12, 2009
  1. @gregkh


    gregkh authored
  2. @gregkh

    time: catch xtime_nsec underflows and fix them

    john stultz authored gregkh committed
    commit 6c9bacb upstream.
    Impact: fix time warp bug
    Alex Shi, along with Yanmin Zhang have been noticing occasional time
    inconsistencies recently. Through their great diagnosis, they found that
    the xtime_nsec value used in update_wall_time was occasionally going
    negative. After looking through the code for awhile, I realized we have
    the possibility for an underflow when three conditions are met in
      1) We have accumulated a second's worth of nanoseconds, so we
         incremented xtime.tv_sec and appropriately decrement xtime_nsec.
         (This doesn't cause xtime_nsec to go negative, but it can cause it
          to be small).
      2) The remaining offset value is large, but just slightly less then
      3) clocksource_adjust() is speeding up the clock, causing a
         corrective amount (compensating for the increase in the multiplier
         being multiplied against the unaccumulated offset value) to be
         subtracted from xtime_nsec.
    This can cause xtime_nsec to underflow.
    Unfortunately, since we notify the NTP subsystem via second_overflow()
    whenever we accumulate a full second, and this effects the error
    accumulation that has already occured, we cannot simply revert the
    accumulated second from xtime nor move the second accumulation to after
    the clocksource_adjust call without a change in behavior.
    This leaves us with (at least) two options:
    1) Simply return from clocksource_adjust() without making a change if we
       notice the adjustment would cause xtime_nsec to go negative.
    This would work, but I'm concerned that if a large adjustment was needed
    (due to the error being large), it may be possible to get stuck with an
    ever increasing error that becomes too large to correct (since it may
    always force xtime_nsec negative). This may just be paranoia on my part.
    2) Catch xtime_nsec if it is negative, then add back the amount its
       negative to both xtime_nsec and the error.
    This second method is consistent with how we've handled earlier rounding
    issues, and also has the benefit that the error being added is always in
    the oposite direction also always equal or smaller then the correction
    being applied. So the risk of a corner case where things get out of
    control is lessened.
    This patch fixes bug 11970, as tested by Yanmin Zhang
    Signed-off-by: John Stultz <>
    Acked-by: Yanmin Zhang <>
    Tested-by: Yanmin Zhang <>
    Signed-off-by: Ingo Molnar <>
    Signed-off-by: Greg Kroah-Hartman <>
  3. @gregkh

    hpwdt.c: Add new HP BMC controller.

    Thomas Mingarelli authored gregkh committed
    commit d8100c3 upstream.
    Add the PCI-ID for the upcoming new BMC controller for HP hardware.
    Signed-off-by: Thomas Mingarelli <>
    Signed-off-by: Wim Van Sebroeck <>
    Signed-off-by: Greg Kroah-Hartman <>
  4. @jan-kiszka @gregkh

    KVM: x86: Disallow hypercalls for guest callers in rings > 0 [CVE-200…

    jan-kiszka authored gregkh committed
    [ backport to 2.6.27 by Chuck Ebbert <> ]
    commit 07708c4 upstream.
    So far unprivileged guest callers running in ring 3 can issue, e.g., MMU
    hypercalls. Normally, such callers cannot provide any hand-crafted MMU
    command structure as it has to be passed by its physical address, but
    they can still crash the guest kernel by passing random addresses.
    To close the hole, this patch considers hypercalls valid only if issued
    from guest ring 0. This may still be relaxed on a per-hypercall base in
    the future once required.
    Signed-off-by: Jan Kiszka <>
    Signed-off-by: Avi Kivity <>
    Cc: Chuck Ebbert <>
    Signed-off-by: Greg Kroah-Hartman <>
  5. @gregkh

    x86: Increase MIN_GAP to include randomized stack

    Michal Hocko authored gregkh committed
    [ trivial backport to 2.6.27: Chuck Ebbert <> ]
    commit 8093833 upstream.
    Currently we are not including randomized stack size when calculating
    mmap_base address in arch_pick_mmap_layout for topdown case. This might
    cause that mmap_base starts in the stack reserved area because stack is
    randomized by 1GB for 64b (8MB for 32b) and the minimum gap is 128MB.
    If the stack really grows down to mmap_base then we can get silent mmap
    region overwrite by the stack values.
    Let's include maximum stack randomization size into MIN_GAP which is
    used as the low bound for the gap in mmap.
    Signed-off-by: Michal Hocko <>
    LKML-Reference: <>
    Acked-by: Jiri Kosina <>
    Signed-off-by: H. Peter Anvin <>
    Cc: Chuck Ebbert <>
    Signed-off-by: Greg Kroah-Hartman <>
  6. @gregkh

    eCryptfs: Prevent lower dentry from going negative during unlink (CVE…

    Tyler Hicks authored gregkh committed
    commit 9c2d205 upstream.
    When calling vfs_unlink() on the lower dentry, d_delete() turns the
    dentry into a negative dentry when the d_count is 1.  This eventually
    caused a NULL pointer deref when a read() or write() was done and the
    negative dentry's d_inode was dereferenced in
    ecryptfs_read_update_atime() or ecryptfs_getxattr().
    Placing mutt's tmpdir in an eCryptfs mount is what initially triggered
    the oops and I was able to reproduce it with the following sequence:
    open("/tmp/upper/foo", O_RDWR|O_CREAT|O_EXCL|O_NOFOLLOW, 0600) = 3
    link("/tmp/upper/foo", "/tmp/upper/bar") = 0
    unlink("/tmp/upper/foo")                = 0
    open("/tmp/upper/bar", O_RDWR|O_CREAT|O_NOFOLLOW, 0600) = 4
    unlink("/tmp/upper/bar")                = 0
    write(4, "eCryptfs test\n"..., 14 <unfinished ...>
    +++ killed by SIGKILL +++
    Reported-by: Loïc Minier <>
    Cc: Serge Hallyn <>
    Cc: Dave Kleikamp <>
    Signed-off-by: Tyler Hicks <>
    Cc: Chuck Ebbert <>
    Signed-off-by: Greg Kroah-Hartman <>
  7. @gregkh

    x86: Don't leak 64-bit kernel register values to 32-bit processes

    Jan Beulich authored gregkh committed
    commit 24e3580 upstream
    x86: Don't leak 64-bit kernel register values to 32-bit processes
    While 32-bit processes can't directly access R8...R15, they can
    gain access to these registers by temporarily switching themselves
    into 64-bit mode.
    Therefore, registers not preserved anyway by called C functions
    (i.e. R8...R11) must be cleared prior to returning to user mode.
    Signed-off-by: Jan Beulich <>
    LKML-Reference: <>
    Signed-off-by: Ingo Molnar <>
    Cc: Chuck Ebbert <>
    Signed-off-by: Greg Kroah-Hartman <>
  8. @gregkh

    x86-64: slightly stream-line 32-bit syscall entry code

    Jan Beulich authored gregkh committed
    commit 295286a upstream
    x86-64: slightly stream-line 32-bit syscall entry code
    [ required for following patch to apply properly ]
    Avoid updating registers or memory twice as well as needlessly loading
    or copying registers.
    Signed-off-by: Jan Beulich <>
    Signed-off-by: Ingo Molnar <>
    Cc: Chuck Ebbert <>
    Signed-off-by: Greg Kroah-Hartman <>
  9. @gregkh

    net: Fix wrong sizeof

    Jean Delvare authored gregkh committed
    commit b607bd9 upstream.
    Which is why I have always preferred sizeof(struct foo) over
    Signed-off-by: Jean Delvare <>
    Acked-by: Randy Dunlap <>
    Signed-off-by: David S. Miller <>
    Signed-off-by: Greg Kroah-Hartman <>
Commits on Oct 5, 2009
  1. @gregkh


    gregkh authored
  2. @gregkh

    mmap: avoid unnecessary anon_vma lock acquisition in vma_adjust()

    Lee Schermerhorn authored gregkh committed
    commit 252c5f9 upstream.
    We noticed very erratic behavior [throughput] with the AIM7 shared
    workload running on recent distro [SLES11] and mainline kernels on an
    8-socket, 32-core, 256GB x86_64 platform.  On the SLES11 kernel
    [] with Barcelona processors, as we increased the load [10s of
    thousands of tasks], the throughput would vary between two "plateaus"--one
    at ~65K jobs per minute and one at ~130K jpm.  The simple patch below
    causes the results to smooth out at the ~130k plateau.
    But wait, there's more:
    We do not see this behavior on smaller platforms--e.g., 4 socket/8 core.
    This could be the result of the larger number of cpus on the larger
    platform--a scalability issue--or it could be the result of the larger
    number of interconnect "hops" between some nodes in this platform and how
    the tasks for a given load end up distributed over the nodes' cpus and
    memories--a stochastic NUMA effect.
    The variability in the results are less pronounced [on the same platform]
    with Shanghai processors and with mainline kernels.  With 31-rc6 on
    Shanghai processors and 288 file systems on 288 fibre attached storage
    volumes, the curves [jpm vs load] are both quite flat with the patched
    kernel consistently producing ~3.9% better throughput [~80K jpm vs ~77K
    jpm] than the unpatched kernel.
    Profiling indicated that the "slow" runs were incurring high[er]
    contention on an anon_vma lock in vma_adjust(), apparently called from the
    sbrk() system call.
    The patch:
    A comment in mm/mmap.c:vma_adjust() suggests that we don't really need the
    anon_vma lock when we're only adjusting the end of a vma, as is the case
    for brk().  The comment questions whether it's worth while to optimize for
    this case.  Apparently, on the newer, larger x86_64 platforms, with
    interesting NUMA topologies, it is worth while--especially considering
    that the patch [if correct!] is quite simple.
    We can detect this condition--no overlap with next vma--by noting a NULL
    "importer".  The anon_vma pointer will also be NULL in this case, so
    simply avoid loading vma->anon_vma to avoid the lock.
    However, we DO need to take the anon_vma lock when we're inserting a vma
    ['insert' non-NULL] even when we have no overlap [NULL "importer"], so we
    need to check for 'insert', as well.  And Hugh points out that we should
    also take it when adjusting vm_start (so that rmap.c can rely upon
    vma_address() while it holds the anon_vma lock).
    akpm: Zhang Yanmin reprts a 150% throughput improvement with aim7, so it
    might be -stable material even though thiss isn't a regression: "this
    issue is not clear on dual socket Nehalem machine (2*4*2 cpu), but is
    severe on large machine (4*8*2 cpu)"
    [ test vma start too]
    Signed-off-by: Lee Schermerhorn <>
    Signed-off-by: Hugh Dickins <>
    Cc: Nick Piggin <>
    Cc: Eric Whitney <>
    Tested-by: "Zhang, Yanmin" <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  3. @gregkh

    mm: fix anonymous dirtying

    Hugh Dickins authored gregkh committed
    commit 1ac0cb5 upstream.
    do_anonymous_page() has been wrong to dirty the pte regardless.
    If it's not going to mark the pte writable, then it won't help
    to mark it dirty here, and clogs up memory with pages which will
    need swap instead of being thrown away.  Especially wrong if no
    overcommit is chosen, and this vma is not yet VM_ACCOUNTed -
    we could exceed the limit and OOM despite no overcommit.
    Signed-off-by: Hugh Dickins <>
    Acked-by: Rik van Riel <>
    Cc: KAMEZAWA Hiroyuki <>
    Cc: KOSAKI Motohiro <>
    Cc: Nick Piggin <>
    Cc: Mel Gorman <>
    Cc: Minchan Kim <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  4. @gregkh

    hugetlb: restore interleaving of bootmem huge pages (2.6.31)

    Lee Schermerhorn authored gregkh committed
    Not upstream as it is fixed differently in .32
    I noticed that alloc_bootmem_huge_page() will only advance to the next
    node on failure to allocate a huge page.  I asked about this on linux-mm
    and linux-numa, cc'ing the usual huge page suspects.  Mel Gorman
    	I strongly suspect that the same node being used until allocation
    	failure instead of round-robin is an oversight and not deliberate
    	at all. It appears to be a side-effect of a fix made way back in
    	commit 63b4613 ["hugetlb: fix
    	hugepage allocation with memoryless nodes"]. Prior to that patch
    	it looked like allocations would always round-robin even when
    	allocation was successful.
    Andy Whitcroft countered that the existing behavior looked like Andi
    Kleen's original implementation and suggested that we ask him.  We did and
    Andy replied that his intention was to interleave the allocations.  So,
    This patch moves the advance of the hstate next node from which to
    allocate up before the test for success of the attempted allocation.  This
    will unconditionally advance the next node from which to alloc,
    interleaving successful allocations over the nodes with sufficient
    contiguous memory, and skipping over nodes that fail the huge page
    allocation attempt.
    Note that alloc_bootmem_huge_page() will only be called for huge pages of
    order > MAX_ORDER.
    Signed-off-by: Lee Schermerhorn <>
    Reviewed-by: Andi Kleen <>
    Cc: Mel Gorman <>
    Cc: David Rientjes <>
    Cc: Adam Litke <>
    Cc: Andy Whitcroft <>
    Cc: Eric Whitney <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Greg Kroah-Hartman <>
  5. @kaber @gregkh

    netfilter: bridge: refcount fix

    kaber authored gregkh committed
    netfilter: bridge: refcount fix
    Upstream commit f3abc9b:
    commit f216f08
    ([NETFILTER]: bridge netfilter: deal with martians correctly)
    added a refcount leak on in_dev.
    Instead of using in_dev_get(), we can use __in_dev_get_rcu(),
    as netfilter hooks are running under rcu_read_lock(), as pointed
    by Patrick.
    Signed-off-by: Eric Dumazet <>
    Signed-off-by: Patrick McHardy <>
    Signed-off-by: Greg Kroah-Hartman <>
  6. @fenrus75 @gregkh

    net: Make the copy length in af_packet sockopt handler unsigned

    fenrus75 authored gregkh committed
    fixed upstream in commit b705884 in a different way
    The length of the to-copy data structure is currently stored in
    a signed integer. However many comparisons are done with sizeof(..)
    which is unsigned. It's more suitable for this variable to be unsigned
    to make these comparisons more naturally right.
    Signed-off-by: Arjan van de Ven <>
    Cc: David S. Miller <>
    Cc: Ingo Molnar <>
    Cc: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  7. @fenrus75 @gregkh

    net ax25: Fix signed comparison in the sockopt handler

    fenrus75 authored gregkh committed
    fixed upstream in commit b705884 in a different way
    The ax25 code tried to use
            if (optlen < sizeof(int))
                    return -EINVAL;
    as a security check against optlen being negative (or zero) in the
    set socket option.
    Unfortunately, "sizeof(int)" is an unsigned property, with the
    result that the whole comparison is done in unsigned, letting
    negative values slip through.
    This patch changes this to
            if (optlen < (int)sizeof(int))
                    return -EINVAL;
    so that the comparison is done as signed, and negative values
    get properly caught.
    Signed-off-by: Arjan van de Ven <>
    Cc: David S. Miller <>
    Cc: Ingo Molnar <>
    Cc: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
  8. @gregkh

    Fix incorrect stable backport to bas_gigaset

    Tilman Schmidt authored gregkh committed
    bas_gigaset: correctly allocate USB interrupt transfer buffer
    [ Upstream commit 170ebf8 ]
    This incorrect backport to placed some code into the probe function
    which used a pointer before it was initialized. Moving this to the correct
    place (as it is in upstream).
    Signed-off-by: Stefan Bader <>
    Acked-by: Tim Gardner <>
    Acked-by: Steve Conklin <>
    Signed-off-by: Greg Kroah-Hartman <>
  9. @gregkh

    pcnet_cs: Fix misuse of the equality operator.

    Cord Walter authored gregkh committed
    commit a9d3a14 upstream.
    Signed-off-by: Cord Walter <>
    Signed-off-by: Komuro <>
    Signed-off-by: David S. Miller <>
    Cc: Christoph Biedl <>
    Signed-off-by: Greg Kroah-Hartman <>
  10. @baruchsiach @gregkh

    enc28j60: fix RX buffer overflow

    baruchsiach authored gregkh committed
    commit 2269201 upstream.
    The enc28j60 driver doesn't check whether the length of the packet as reported
    by the hardware fits into the preallocated buffer. When stressed, the hardware
    may report insanely large packets even tough the "Receive OK" bit is set. Fix
    Signed-off-by: Baruch Siach <>
    Signed-off-by: David S. Miller <>
    Signed-off-by: Greg Kroah-Hartman <>
  11. @chunkeey @gregkh

    p54usb: add Zcomax XG-705A usbid

    chunkeey authored gregkh committed
    commit f7f7117 upstream.
    This patch adds a new usbid for Zcomax XG-705A to the device table.
    Reported-by: Jari Jaakola <>
    Signed-off-by: Christian Lamparter <>
    Signed-off-by: John W. Linville <>
    Signed-off-by: Greg Kroah-Hartman <>
  12. @jankara @gregkh

    fs: make sure data stored into inode is properly seen before unlockin…

    jankara authored gregkh committed
    …g new inode
    commit 580be08 upstream.
    In theory it could happen that on one CPU we initialize a new inode but
    clearing of I_NEW | I_LOCK gets reordered before some of the
    initialization.  Thus on another CPU we return not fully uptodate inode
    from iget_locked().
    This seems to fix a corruption issue on ext3 mounted over NFS.
    [ add some commentary]
    Signed-off-by: Jan Kara <>
    Cc: Christoph Hellwig <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
Commits on Sep 24, 2009
  1. @gregkh


    gregkh authored
  2. @gregkh

    nfsd: fix hung up of nfs client while sync write data to nfs server

    Wei Yongjun authored gregkh committed
    commit a0d24b2 upstream.
    nfsd: fix hung up of nfs client while sync write data to nfs server
    Commit 'Short write in nfsd becomes a full write to the client'
    (31dec25) broken the sync write.
    With the following commands to reproduce:
      $ mount -t nfs -o sync /mnt
      $ cd /mnt
      $ echo aaaa > temp.txt
    Then nfs client is hung up.
    In SYNC mode the server alaways return the write count 0 to the
    client. This is because the value of host_err in nfsd_vfs_write()
    will be overwrite in SYNC mode by 'host_err=nfsd_sync(file);',
    and then we return host_err(which is now 0) as write count.
    This patch fixed the problem.
    Signed-off-by: Wei Yongjun <>
    Signed-off-by: J. Bruce Fields <>
    Cc: Chuck Ebbert <>
    Signed-off-by: Greg Kroah-Hartman <>
  3. @dmshaw @gregkh

    Short write in nfsd becomes a full write to the client

    dmshaw authored gregkh committed
    commit 31dec25 upstream.
    Short write in nfsd becomes a full write to the client
    If a filesystem being written to via NFS returns a short write count
    (as opposed to an error) to nfsd, nfsd treats that as a success for
    the entire write, rather than the short count that actually succeeded.
    For example, given a 8192 byte write, if the underlying filesystem
    only writes 4096 bytes, nfsd will ack back to the nfs client that all
    8192 bytes were written.  The nfs client does have retry logic for
    short writes, but this is never called as the client is told the
    complete write succeeded.
    There are probably other ways it could happen, but in my case it
    happened with a fuse (filesystem in userspace) filesystem which can
    rather easily have a partial write.
    Here is a patch to properly return the short write count to the
    Signed-off-by: David Shaw <>
    Signed-off-by: J. Bruce Fields <>
    Cc: Chuck Ebbert <>
    Signed-off-by: Greg Kroah-Hartman <>
  4. @cladisch @gregkh

    sound: oxygen: work around MCE when changing volume

    cladisch authored gregkh committed
    commit f1bc07a upstream.
    When the volume is changed continuously (e.g., when the user drags a
    volume slider with the mouse), the driver does lots of I2C writes.
    Apparently, the sound chip can get confused when we poll the I2C status
    register too much, and fails to complete a read from it.  On the PCI-E
    models, the PCI-E/PCI bridge gets upset by this and generates a machine
    check exception.
    To avoid this, this patch replaces the polling with an unconditional
    wait that is guaranteed to be long enough.
    Signed-off-by: Clemens Ladisch <>
    Tested-by: Johann Messner <johann.messner at>
    Signed-off-by: Takashi Iwai <>
    Signed-off-by: Greg Kroah-Hartman <>
  5. @gregkh

    powerpc/pseries: Fix to handle slb resize across migration

    Brian King authored gregkh committed
    commit 46db2f8 upstream.
    The SLB can change sizes across a live migration, which was not
    being handled, resulting in possible machine crashes during
    migration if migrating to a machine which has a smaller max SLB
    size than the source machine. Fix this by first reducing the
    SLB size to the minimum possible value, which is 32, prior to
    migration. Then during the device tree update which occurs after
    migration, we make the call to ensure the SLB gets updated. Also
    add the slb_size to the lparcfg output so that the migration
    tools can check to make sure the kernel has this capability
    before allowing migration in scenarios where the SLB size will change.
    BenH: Fixed #include <asm/mmu-hash64.h> -> <asm/mmu.h> to avoid
          breaking ppc32 build
    Signed-off-by: Brian King <>
    Signed-off-by: Benjamin Herrenschmidt <>
    Signed-off-by: Greg Kroah-Hartman <>
  6. @htejun @gregkh

    libata: fix off-by-one error in ata_tf_read_block()

    htejun authored gregkh committed
    commit ac8672e upstream.
    ata_tf_read_block() has off-by-one error when converting CHS address
    to LBA.  The bug isn't very visible because ata_tf_read_block() is
    used only when generating sense data for a failed RW command and CHS
    addressing isn't used too often these days.
    This problem was spotted by Atsushi Nemoto.
    Signed-off-by: Tejun Heo <>
    Reported-by: Atsushi Nemoto <>
    Signed-off-by: Jeff Garzik <>
    Signed-off-by: Greg Kroah-Hartman <>
  7. @gregkh

    ALSA: cs46xx - Fix minimum period size

    Sophie Hamilton authored gregkh committed
    commit 6148b13 upstream.
    Fix minimum period size for cs46xx cards. This fixes a problem in the
    case where neither a period size nor a buffer size is passed to ALSA;
    this is the case in Audacious, OpenAL, and others.
    Signed-off-by: Sophie Hamilton <>
    Signed-off-by: Takashi Iwai <>
    Signed-off-by: Greg Kroah-Hartman <>
  8. @jankara @gregkh

    udf: Use device size when drive reported bogus number of written blocks

    jankara authored gregkh committed
    commit 24a5d59 upstream.
    Some drives report 0 as the number of written blocks when there are some blocks
    recorded. Use device size in such case so that we can automagically mount such
    Signed-off-by: Jan Kara <>
    Signed-off-by: Greg Kroah-Hartman <>
  9. @jgunthorpe @gregkh

    TPM: Fixup boot probe timeout for tpm_tis driver

    jgunthorpe authored gregkh committed
    commit ec57935 upstream.
    When probing the device in tpm_tis_init the call request_locality
    uses timeout_a, which wasn't being initalized until after
    request_locality. This results in request_locality falsely timing
    out if the chip is still starting. Move the initialization to before
    This probably only matters for embedded cases (ie mine), a BIOS likely
    gets the TPM into a state where this code path isn't necessary.
    Signed-off-by: Jason Gunthorpe <>
    Acked-by: Rajiv Andrade <>
    Signed-off-by: James Morris <>
    Signed-off-by: Greg Kroah-Hartman <>
  10. @gregkh

    powerpc/ps3: Workaround for flash memory I/O error

    Geoff Levand authored gregkh committed
    commit bc00351 upstream.
    A workaround for flash memory I/O errors when the PS3 internal
    hard disk has not been formatted for OtherOS use.
    This error condition mainly effects 'Live CD' users who have not
    formatted the PS3's internal hard disk for OtherOS.
    Fixes errors similar to these when using the ps3-flash-util
    or ps3-boot-game-os programs:
      ps3flash read failed 0x2050000
      os_area_header_read: read error: os_area_header: Input/output error
      main:627: os_area_read_hp error.
      ERROR: can't change boot flag
    Signed-off-by: Geoff Levand <>
    Signed-off-by: Benjamin Herrenschmidt <>
    Signed-off-by: Greg Kroah-Hartman <>
Something went wrong with that request. Please try again.