GitHub PushEvent at 2014-12-29 17:12:05
Repository: btrfs-progs
Actor: kdave
Payload: {"shas":[["44d3ee3e1f94acf71d52016f771988196955c259","10321040b4416ef60f5e5611ae32074e89e435e7@jp.fujitsu.com","btrfs-progs fix wrong memory free on check_is_root\n\nWhen \"/\" is Btrfs, \"btrfs property <subcommand> /\" regards it\nas non-root by mistake.\n\ncheck_is_root() regards @object as a file system root if\nthe following two conditions are satisfied.\n\n a) Both @object and its parent directory are Btrfs object\n    (file system root, subvolume, inode, and device\n    used for Btrfs).\n b) fsid of the above mentioned two objects are different.\n\nIt doesn't work if @object is \"/\" because, in this case,\nfsid of \"/\" and its parent (it's also \"/\"), are the same.\n\n* Test environment\n\nTwo Btrfs file system (not subvolume) \"/\" and \"/home/sat/mnt\".\n\n* How to reproduce\n\nSubmit \"btrfs prop get\" against the above mentioned file systems.\n\n* Test Result\n\n** Actual result (without my patch)\n\n==========================\nro=false\nlabel=                 # label is displayed because it's a file system root\nro=false               # label is not displayed even if it's a file system root\n==========================\n** Expected result (with my patch)\n\n==========================\nro=false\nlabel=\nro=false\nlabel=foo            # label is displayed\n===========================\n\nSigned-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>\nReported-by: Naohiro Aota <naota@elisp.net>\nReviewed-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","Satoru Takeuchi",false],["0f38766b8fe9d8c5c77a707fa1d24824df09d18a","f41a7033a6382ce00d6b717e37d942dbe3c9a107@cn.fujitsu.com","btrfs-progs: Fix a bug in reset_nlink() which may deletes the recovered file\n\nIn reset_nlink(), we believe rec->found_link as accurate number of the\nvalid links. However it only records the number of found DIR_ITEM, so we\ncan't use it as reliable value.\n\nBefore this patch, in some case, leaf corruption recovery will believe\nthere is a valid backref but don't add_link() since it can't find any\nvalid one and don't put it into the lost+found dir.\nSo the recovered inode will be considered as an orphan item without\norphan item and repair_inode_orphan_item() will add orphan item for it,\ncausing all the filename/filetype we recovered being a waste of time.\n\nSigned-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","Qu Wenruo",false],["7d83db5bae5420d7b1c7f4e64897c25bc9a94f09","ee937cfcc16cf790ab2b37c6354b6c3019afbce8@gmail.com","btrfs-progs: Fix btrfs fi show by uuid and label\n\nCommit 8be2fff (btrfs-progs: apply realpath for btrfs fi\nshow when mount point is given) changed the behavior of\nbtrfs fi show to return an error if the call to realpath()\nfailed.  This broke the ability to specify a filesystem by\nuuid or label.\n\nSo let's not consider a failed call to realpath() as an\nerror.  If the user really specified a bad device, just\nreturn nothing like we did before.\n\nSigned-off-by: Justin Maggard <jmaggard10@gmail.com>\nReviewed-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","Justin Maggard",false],["280434ebde0e88d1e0b774a1181ab4bb9c807d3c","1c5d69841cd43aa5bd620389a9dfe310c76cb958@cn.fujitsu.com","btrfs-progs: move check_arg_type() to util.c\n\nThe check_arg_type() function does quite generic thing, move it to\nutils.c.\n\nSigned-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>\nReviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","Gui Hecheng",true],["1bad43fbe002cd3c00dd82948f19cf73c74e2b75","1c5d69841cd43aa5bd620389a9dfe310c76cb958@cn.fujitsu.com","btrfs-progs: refine btrfs-debug-tree error prompt when a mount point given\n\nNow, if exec:\n\t# btrfs-debug-tree <mount_point>\nit echos:\n\t: Superblock bytenr is larger than device size\n\nBut it is quite misleading, because it is a valid btrfs.\nIn this case, we should tell the developer to provide a block device.\n\nAfter apply:\n\t: '<mount_point>' is not a block device\n\nSigned-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>\nReviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>\nSigned-off-by: David Sterba <dsterba@suse.cz>","Gui Hecheng",true]],"size":5,"ref":"refs/heads/v3.18.x","head":"1bad43fbe002cd3c00dd82948f19cf73c74e2b75"}