1. 03 3月, 2011 38 次提交
  2. 02 3月, 2011 2 次提交
    • J
      ext2: Fix link count corruption under heavy link+rename load · e8a80c6f
      Josh Hunt 提交于
      vfs_rename_other() does not lock renamed inode with i_mutex. Thus changing
      i_nlink in a non-atomic manner (which happens in ext2_rename()) can corrupt
      it as reported and analyzed by Josh.
      
      In fact, there is no good reason to mess with i_nlink of the moved file.
      We did it presumably to simulate linking into the new directory and unlinking
      from an old one. But the practical effect of this is disputable because fsck
      can possibly treat file as being properly linked into both directories without
      writing any error which is confusing. So we just stop increment-decrement
      games with i_nlink which also fixes the corruption.
      
      CC: stable@kernel.org
      CC: Al Viro <viro@ZenIV.linux.org.uk>
      Signed-off-by: NJosh Hunt <johunt@akamai.com>
      Signed-off-by: NJan Kara <jack@suse.cz>
      e8a80c6f
    • V
      mfd: Avoid tps6586x burst writes · 4b57018d
      vwadekar@nvidia.com 提交于
      tps6586 does not support burst writes. i2c writes have to be
      1 byte at a time.
      
      Cc: stable@kernel.org
      Signed-off-by: NVarun Wadekar <vwadekar@nvidia.com>
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      4b57018d