Eric Lee / smarc-fsl-linux-kernel

29 Apr, 2010

3 commits

20 Apr, 2010

9 commits

  • 01bf0b645   Linux 2.6.34-rc5 Browse Code »
    Linus Torvalds
     
  • e8a03feb5   rmap: add exclusively owned pages to the newest anon_vma ... Browse Code »

    The recent anon_vma fixes cause many anonymous pages to end up
    in the parent process anon_vma, even when the page is exclusively
    owned by the current process.

    Adding exclusively owned anonymous pages to the top anon_vma
    reduces rmap scanning overhead, especially in workloads with
    forking servers.

    This patch adds a parameter to __page_set_anon_rmap that can
    be used to indicate whether or not the added page is exclusively
    owned by the current process.

    Pages added through page_add_new_anon_rmap are exclusively
    owned by the current process, and can be added to the top
    anon_vma.

    Pages added through page_add_anon_rmap can be either shared
    or exclusively owned, so we do the conservative thing and
    add it to the oldest anon_vma.

    A next step would be to add the exclusive parameter to
    page_add_anon_rmap, to be used from functions where we do
    know for sure whether a page is exclusively owned.

    Signed-off-by: Rik van Riel
    Reviewed-by: Johannes Weiner
    Lightly-tested-by: Borislav Petkov
    Reviewed-by: Minchan Kim
    [ Edited to look nicer - Linus ]
    Signed-off-by: Linus Torvalds

    Rik van Riel
     
  • 9b030e200   Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ecryptfs/ecryptfs-2.6 ... Browse Code »

    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ecryptfs/ecryptfs-2.6:
    eCryptfs: Turn lower lookup error messages into debug messages
    eCryptfs: Copy lower directory inode times and size on link
    ecryptfs: fix use with tmpfs by removing d_drop from ecryptfs_destroy_inode
    ecryptfs: fix error code for missing xattrs in lower fs
    eCryptfs: Decrypt symlink target for stat size
    eCryptfs: Strip metadata in xattr flag in encrypted view
    eCryptfs: Clear buffer before reading in metadata xattr
    eCryptfs: Rename ecryptfs_crypt_stat.num_header_bytes_at_front
    eCryptfs: Fix metadata in xattr feature regression

    Linus Torvalds
     
  • 9f37622f8   eCryptfs: Turn lower lookup error messages into debug messages ... Browse Code »

    Vaugue warnings about ENAMETOOLONG errors when looking up an encrypted
    file name have caused many users to become concerned about their data.
    Since this is a rather harmless condition, I'm moving this warning to
    only be printed when the ecryptfs_verbosity module param is 1.

    Signed-off-by: Tyler Hicks

    Tyler Hicks
     
  • 3a8380c07   eCryptfs: Copy lower directory inode times and size on link ... Browse Code »

    The timestamps and size of a lower inode involved in a link() call was
    being copied to the upper parent inode. Instead, we should be
    copying lower parent inode's timestamps and size to the upper parent
    inode. I discovered this bug using the POSIX test suite at Tuxera.

    Signed-off-by: Tyler Hicks

    Tyler Hicks
     
  • 133b8f9d6   ecryptfs: fix use with tmpfs by removing d_drop from ecryptfs_destroy_inode ... Browse Code »

    Since tmpfs has no persistent storage, it pins all its dentries in memory
    so they have d_count=1 when other file systems would have d_count=0.
    ->lookup is only used to create new dentries. If the caller doesn't
    instantiate it, it's freed immediately at dput(). ->readdir reads
    directly from the dcache and depends on the dentries being hashed.

    When an ecryptfs mount is mounted, it associates the lower file and dentry
    with the ecryptfs files as they're accessed. When it's umounted and
    destroys all the in-memory ecryptfs inodes, it fput's the lower_files and
    d_drop's the lower_dentries. Commit 4981e081 added this and a d_delete in
    2008 and several months later commit caeeeecf removed the d_delete. I
    believe the d_drop() needs to be removed as well.

    The d_drop effectively hides any file that has been accessed via ecryptfs
    from the underlying tmpfs since it depends on it being hashed for it to
    be accessible. I've removed the d_drop on my development node and see no
    ill effects with basic testing on both tmpfs and persistent storage.

    As a side effect, after ecryptfs d_drops the dentries on tmpfs, tmpfs
    BUGs on umount. This is due to the dentries being unhashed.
    tmpfs->kill_sb is kill_litter_super which calls d_genocide to drop
    the reference pinning the dentry. It skips unhashed and negative dentries,
    but shrink_dcache_for_umount_subtree doesn't. Since those dentries
    still have an elevated d_count, we get a BUG().

    This patch removes the d_drop call and fixes both issues.

    This issue was reported at:
    https://bugzilla.novell.com/show_bug.cgi?id=567887

    Reported-by: Árpád Bíró
    Signed-off-by: Jeff Mahoney
    Cc: Dustin Kirkland
    Cc: stable@kernel.org
    Signed-off-by: Tyler Hicks

    Jeff Mahoney
     
  • cfce08c6b   ecryptfs: fix error code for missing xattrs in lower fs ... Browse Code »

    If the lower file system driver has extended attributes disabled,
    ecryptfs' own access functions return -ENOSYS instead of -EOPNOTSUPP.
    This breaks execution of programs in the ecryptfs mount, since the
    kernel expects the latter error when checking for security
    capabilities in xattrs.

    Signed-off-by: Christian Pulvermacher
    Cc: stable@kernel.org
    Signed-off-by: Tyler Hicks

    Christian Pulvermacher
     
  • 3a60a1686   eCryptfs: Decrypt symlink target for stat size ... Browse Code »

    Create a getattr handler for eCryptfs symlinks that is capable of
    reading the lower target and decrypting its path. Prior to this patch,
    a stat's st_size field would represent the strlen of the encrypted path,
    while readlink() would return the strlen of the decrypted path. This
    could lead to confusion in some userspace applications, since the two
    values should be equal.

    https://bugs.launchpad.net/bugs/524919

    Reported-by: Loïc Minier
    Cc: stable@kernel.org
    Signed-off-by: Tyler Hicks

    Tyler Hicks
     
  • 76e506a75   Fix ISDN/Gigaset build failure ... Browse Code »

    Commit b91ecb00 ("gigaset: include cleanup cleanup") removed an implicit
    sched.h inclusion that came in via slab.h, and caused various compile
    problems as a result.

    This should fix it.

    Reported-by: Ingo Molnar
    Signed-off-by: Linus Torvalds

    Linus Torvalds
     

19 Apr, 2010

15 commits

18 Apr, 2010

4 commits

17 Apr, 2010

6 commits

  • 1c4f01973   packet : remove init_net restriction ... Browse Code »

    The af_packet protocol is used by Perl to do ioctls as reported by
    Stephane Riviere:

    "Net::RawIP relies on SIOCGIFADDR et SIOCGIFHWADDR to get the IP and MAC
    addresses of the network interface."

    But in a new network namespace these ioctl fail because it is disabled for
    a namespace different from the init_net_ns.

    These two lines should not be there as af_inet and af_packet are
    namespace aware since a long time now. I suppose we forget to remove these
    lines because we sent the af_packet first, before af_inet was supported.

    Signed-off-by: Daniel Lezcano
    Reported-by: Stephane Riviere
    Signed-off-by: David S. Miller

    Daniel Lezcano
     
  • 31f634a63   WAN: flush tx_queue in hdlc_ppp to prevent panic on rmmod hw_driver. ... Browse Code »

    tx_queue is used as a temporary queue when not allowed to queue skb
    directly to the hw device driver (which may sleep). Most paths flush
    it before returning, but ppp_start() currently cannot. Make sure we
    don't leave skbs pointing to a non-existent device.

    Thanks to Michael Barkowski for reporting this problem.

    Signed-off-by: Krzysztof Hałasa
    Signed-off-by: David S. Miller

    Krzysztof Halasa
     
  • bc3966921   Merge branch 'bugzilla-15749' into release Browse Code »
    Len Brown
     
  • 2060c4457   ACPI: EC: Limit burst to 64 bits ... Browse Code »

    access_bit_width field is u8 in ACPICA, thus 256 value written to it
    becomes 0, causing divide by zero later.

    Proper fix would be to remove access_bit_width at all, just because
    we already have access_byte_width, which is access_bit_width / 8.
    Limit access width to 64 bit for now.

    https://bugzilla.kernel.org/show_bug.cgi?id=15749
    fixes regression caused by the fix for:
    https://bugzilla.kernel.org/show_bug.cgi?id=14667

    Signed-off-by: Alexey Starikovskiy
    Signed-off-by: Len Brown

    Alexey Starikovskiy
     
  • f1d486a36   xfs: don't warn on EAGAIN in inode reclaim ... Browse Code »

    Any inode reclaim flush that returns EAGAIN will result in the inode
    reclaim being attempted again later. There is no need to issue a
    warning into the logs about this situation.

    Signed-off-by: Dave Chinner
    Reviewed-by: Alex Elder
    Signed-off-by: Alex Elder

    Dave Chinner
     
  • b6f8dd49d   xfs: ensure that sync updates the log tail correctly ... Browse Code »

    Updates to the VFS layer removed an extra ->sync_fs call into the
    filesystem during the sync process (from the quota code).
    Unfortunately the sync code was unknowingly relying on this call to
    make sure metadata buffers were flushed via a xfs_buftarg_flush()
    call to move the tail of the log forward in memory before the final
    transactions of the sync process were issued.

    As a result, the old code would write a very recent log tail value
    to the log by the end of the sync process, and so a subsequent crash
    would leave nothing for log recovery to do. Hence in qa test 182,
    log recovery only replayed a small handle for inode fsync
    transactions in this case.

    However, with the removal of the extra ->sync_fs call, the log tail
    was now not moved forward with the inode fsync transactions near the
    end of the sync procese the first (and only) buftarg flush occurred
    after these transactions went to disk. The result is that log
    recovery now sees a large number of transactions for metadata that
    is already on disk.

    This usually isn't a problem, but when the transactions include
    inode chunk allocation, the inode create transactions and all
    subsequent changes are replayed as we cannt rely on what is on disk
    is valid. As a result, if the inode was written and contains
    unlogged changes, the unlogged changes are lost, thereby violating
    sync semantics.

    The fix is to always issue a transaction after the buftarg flush
    occurs is the log iѕ not idle or covered. This results in a dummy
    transaction being written that contains the up-to-date log tail
    value, which will be very recent. Indeed, it will be at least as
    recent as the old code would have left on disk, so log recovery
    will behave exactly as it used to in this situation.

    Signed-off-by: Dave Chinner
    Reviewed-by: Christoph Hellwig
    Signed-off-by: Alex Elder

    Dave Chinner
     

16 Apr, 2010

3 commits

  • 1c1ec9c03   Merge git://git.kernel.org/pub/scm/linux/kernel/git/wim/linux-2.6-watchdog ... Browse Code »

    * git://git.kernel.org/pub/scm/linux/kernel/git/wim/linux-2.6-watchdog:
    [WATCHDOG] max63xx driver depends on ioremap()
    [WATCHDOG] max63xx: be careful when disabling the watchdog
    [WATCHDOG] fixed book E watchdog period register mask.
    [WATCHDOG] omap4: Fix WDT Kconfig

    Linus Torvalds
     
  • 1f829825f   Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6 ... Browse Code »

    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6:
    ASoC: imx-ssi: do not call hrtimer_disable in trigger function
    ALSA: hda - Add position_fix quirk for Biostar mobo
    ALSA: hda - add a quirk for Clevo M570U laptop
    ASoC: imx-ssi: increase minimum periods to 4
    ALSA: hda - Avoid invalid "Independent HP" control for VIA codecs
    ALSA: hda - Fix control element allocations in VIA codec parser
    ALSA: aaci - Fix alignment faults on ARM Cortex introduced by commit 29a4f2d3
    ALSA: hda - Add fix-up for Sony VAIO with ALC269
    ALSA: hda - Enhance fix-up table for Realtek codecs
    ALSA: usb - Fix Oops after usb-midi disconnection
    ALSA: hda - Fix initial capture source connections of ALC880/260
    ALSA: hda - Fix setup for ALC269vb amic and dmic models
    ALSA: hda - Fix auto-parser of ALC269vb for HP pin NID 0x21
    ASoC: imx-ssi: Use a hrtimer in FIQ mode
    ASoC: imx-pcm-dma-mx2: restart DMA after an error
    ASoC: imx-ssi: honor IMX_SSI_DMA flag
    ASoC: wm2000: remove unused #include
    ALSA: hda: Add support for Medion WIM2160

    Linus Torvalds
     
  • aebaec975   [WATCHDOG] max63xx driver depends on ioremap() ... Browse Code »

    Correct fix for the "ioremap() causes build failure on S390" should have been
    a dependancy on HAS_IOMEM. So we add this dependancy also (and leave the driver
    in the ARM section for now).

    Signed-off-by: Geert Uytterhoeven
    Signed-off-by: Wim Van Sebroeck

    Geert Uytterhoeven