Skip to content

L
linux
Switch branch/tag
  1. 03 Mar, 2011 1 commit
    • Tao Ma's avatar
      ext3: Fix an overflow in ext3_trim_fs. · 425fa410
      Tao Ma authored 
      In a bs=4096 volume, if we call FITRIM with the following parameter as
fstrim_range(start = 102400, len = 134144000, minlen = 10240), with the
following code:
if (len >= EXT3_BLOCKS_PER_GROUP(sb))
        len -= (EXT3_BLOCKS_PER_GROUP(sb) - first_block);
else
        last_block = first_block + len;

So if len < EXT3_BLOCKS_PER_GROUP while first_block + len >
EXT3_BLOCKS_PER_GROUP, last_block will be set to an overflow value
which exceeds EXT3_BLOCKS_PER_GROUP.

This patch fixes it and adjusts len and last_block accordingly.

Cc: Lukas Czerner <lczerner@redhat.com>
Cc: Jan Kara <jack@suse.cz>
Signed-off-by: default avatarTao Ma <boyu.mt@taobao.com>
Signed-off-by: default avatarJan Kara <jack@suse.cz>
      425fa410
  3. 28 Feb, 2011 3 commits
  5. 24 Feb, 2011 6 commits
  7. 23 Feb, 2011 27 commits
  9. 22 Feb, 2011 3 commits
    • Kevin Hilman's avatar
      i2c-omap: fix static suspend vs. runtime suspend · adf6e079
      Kevin Hilman authored 
      When runtime PM is enabled, each OMAP i2c device is suspended after
each i2c xfer.  However, there are two cases when the static suspend
methods must be used to ensure the devices are suspended:

1) runtime PM is disabled, either at compile time or dynamically
    via /sys/devices/.../power/control.
2) an i2c client driver uses i2c during it's suspend callback, thus
   leaving the i2c driver active (NOTE: runtime suspend transitions are
   disabled during system suspend, so i2c activity during system
   suspend will runtime resume the device, but not runtime (re)suspend it.)

Since the actual work to suspend the device is handled by the
subsytem, call the bus methods to take care of it.

NOTE: This takes care of a known suspend problem on OMAP3 where the
TWL RTC driver does i2c xfers during its suspend path leaving the i2c
driver in an active state (since runtime suspend transistions are
disabled.)
Signed-off-by: default avatarKevin Hilman <khilman@ti.com>
Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      adf6e079
    • Wolfram Sang's avatar
      i2c-stu300: make sure adapter-name is terminated · f10820e4
      Wolfram Sang authored 
      Use strlcpy instead of strncpy.
Signed-off-by: default avatarWolfram Sang <w.sang@pengutronix.de>
Cc: Linus Walleij <linus.walleij@stericsson.com>
Cc: Ben Dooks <ben-linux@fluff.org>
Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      f10820e4
    • Lukas Czerner's avatar
      xfs: check if device support discard in xfs_ioc_trim() · be715140
      Lukas Czerner authored 
      Right now we, are relying on the fact that when we attempt to
actually do the discard, blkdev_issue_discar() returns -EOPNOTSUPP
and the user is informed that the device does not support discard.

However, in the case where the we do not hit any suitable free
extent to trim in FITRIM code, it will finish without any error.
This is very confusing, because it seems that FITRIM was successful
even though the device does not actually supports discard.

Solution: Check for the discard support before attempt to search for
free extents.
Signed-off-by: default avatarLukas Czerner <lczerner@redhat.com>
Signed-off-by: default avatarAlex Elder <aelder@sgi.com>
      be715140
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7