The RCU-friendly string API used internally by BTRFS is generic enough for
common use. This doesn't add any new functionality, but instead just moves the
code and documents the existing API.
Reviewed-by: Josh Triplett j...@joshtriplett.org
Acked-by: Paul E. McKenney paul...@linux.vnet.ibm.com
Replacing a xattr consists of doing a lookup for its existing value, delete
the current value from the respective leaf, release the search path and then
finally insert the new value. This leaves a time window where readers (getxattr,
listxattrs) won't see any value for the xattr. Xattrs are used
On Sat, 2014-11-08 at 00:46 -0800, Omar Sandoval wrote:
The RCU-friendly string API used internally by BTRFS is generic enough for
common use. This doesn't add any new functionality, but instead just moves the
code and documents the existing API.
Some more trivia, can be updated later if
On 7 November 2014 18:16, David Sterba dste...@suse.cz wrote:
On Fri, Nov 07, 2014 at 10:07:43AM +0800, Gui Hecheng wrote:
The @fi_args-num_devices in @get_fs_info() does not include seed devices.
We could just correct it by searching the chunk tree and count how
many dev_items there are in
Hi Linus,
Please pull my for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
It's a one liner for an error cleanup path that leads to crashes.
Chris Mason (1) commits (+1/-1):
Btrfs: fix kfree on list_head in btrfs_lookup_csums_range error
Updating to the latest live-git btrfs-progs (on v3.17.1 tag), I chanced
across this (gentoo) warning, pointing to a gcc warning believed to be
severe:
* QA Notice: Package triggers severe warnings which indicate that it
*may exhibit random runtime failures.
*
On Sat, Nov 08, 2014 at 08:13:37AM -0800, Joe Perches wrote:
On Sat, 2014-11-08 at 00:46 -0800, Omar Sandoval wrote:
The RCU-friendly string API used internally by BTRFS is generic enough for
common use. This doesn't add any new functionality, but instead just moves
the
code and
