mirrors/linux
2
0
Fork 0
mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git synced 2026-09-26 04:34:28 -05:00
Code Issues Packages Projects Releases Wiki Activity
388,088 Commits 1 Branch 946 Tags
30abda170be7cbd9bce9a7026ce83ce1f74c0e7a
Commit Graph
6 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Gabriel de Perthuis cecd628d9a bcache: Refresh usage docs 
Mention udev autoregistration, symlinks.  Write down some sysfs paths.

Signed-off-by: Gabriel de Perthuis <g2p.code@gmail.com>
Signed-off-by: Kent Overstreet <koverstreet@google.com>
 2013-06-26 21:58:06 -07:00
Gabriel de Perthuis ab9e14002e bcache: Send label uevents 
Signed-off-by: Gabriel de Perthuis <g2p.code@gmail.com>
Signed-off-by: Kent Overstreet <koverstreet@google.com>
 2013-06-26 21:58:06 -07:00
Gabriel de Perthuis a25c32bede bcache: Send a uevent with a cached device's UUID 
Signed-off-by: Gabriel de Perthuis <g2p.code@gmail.com>
 2013-06-26 21:58:05 -07:00
Gabriel de Perthuis a9dd53adbb bcache: Warn when a device is already registered. 
Signed-off-by: Gabriel de Perthuis <g2p.code+bcache@gmail.com>
Signed-off-by: Kent Overstreet <koverstreet@google.com>
 2013-06-26 17:08:52 -07:00
Gabriel de Perthuis 03b71c6ca6 btrfs: don't stop searching after encountering the wrong item 
The search ioctl skips items that are too large for a result buffer, but
inline items of a certain size occuring before any search result is
found would trigger an overflow and stop the search entirely.

Bug: https://bugzilla.kernel.org/show_bug.cgi?id=57641

Cc: stable@vger.kernel.org
Signed-off-by: Gabriel de Perthuis <g2p.code+btrfs@gmail.com>
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
 2013-05-17 21:40:10 -04:00
Gabriel de Perthuis 661bec6ba8 Fix a sign bug causing invalid memory access in the ino_paths ioctl. 
To see the problem, create many hardlinks to the same file (120 should do it),
then look up paths by inode with:

  ls -i
  btrfs inspect inode-resolve -v $ino /mnt/btrfs

I noticed the memory layout of the fspath->val data had some irregularities
(some unnecessary gaps that stop appearing about halfway),
so I'm not sure there aren't any bugs left in it.
 2012-10-25 15:39:47 -04:00