{"push_id":800171262,"size":1000,"distinct_size":0,"ref":"refs/heads/master","head":"6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f","before":"807249d3ada1ff28a47c4054ca4edd479421b671","commits":[{"sha":"18b9f67962eb890da0c053e04c3cf0e91871d4fa","author":{"email":"1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.com","name":"NeilBrown"},"message":"md-cluster: remove inappropriate try_module_get from join()\n\nmd_setup_cluster already calls try_module_get(), so this\ntry_module_get isn't needed.\nAlso, there is no matching module_put (except in error patch),\nso this leaves an unbalanced module count.\n\nSigned-off-by: NeilBrown <neilb@suse.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/18b9f67962eb890da0c053e04c3cf0e91871d4fa"},{"sha":"55ce74d4bfe1b9444436264c637f39a152d1e5ac","author":{"email":"1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.com","name":"NeilBrown"},"message":"md/raid1: ensure device failure recorded before write request returns.\n\nWhen a write to one of the legs of a RAID1 fails, the failure is\nrecorded in the metadata of the other leg(s) so that after a restart\nthe data on the failed drive wont be trusted even if that drive seems\nto be working again  (maybe a cable was unplugged).\n\nSimilarly when we record a bad-block in response to a write failure,\nwe must not let the write complete until the bad-block update is safe.\n\nCurrently there is no interlock between the write request completing\nand the metadata update.  So it is possible that the write will\ncomplete, the app will confirm success in some way, and then the\nmachine will crash before the metadata update completes.\n\nThis is an extremely small hole for a racy to fit in, but it is\ntheoretically possible and so should be closed.\n\nSo:\n - set MD_CHANGE_PENDING when requesting a metadata update for a\n   failed device, so we can know with certainty when it completes\n - queue requests that experienced an error on a new queue which\n   is only processed after the metadata update completes\n - call raid_end_bio_io() on bios in that queue when the time comes.\n\nSigned-off-by: NeilBrown <neilb@suse.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/55ce74d4bfe1b9444436264c637f39a152d1e5ac"},{"sha":"95af587e95aacb9cfda4a9641069a5244a540dc8","author":{"email":"1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.com","name":"NeilBrown"},"message":"md/raid10: ensure device failure recorded before write request returns.\n\nWhen a write to one of the legs of a RAID10 fails, the failure is\nrecorded in the metadata of the other legs so that after a restart\nthe data on the failed drive wont be trusted even if that drive seems\nto be working again (maybe a cable was unplugged).\n\nCurrently there is no interlock between the write request completing\nand the metadata update.  So it is possible that the write will\ncomplete, the app will confirm success in some way, and then the\nmachine will crash before the metadata update completes.\n\nThis is an extremely small hole for a racy to fit in, but it is\ntheoretically possible and so should be closed.\n\nSo:\n - set MD_CHANGE_PENDING when requesting a metadata update for a\n   failed device, so we can know with certainty when it completes\n - queue requests that experienced an error on a new queue which\n   is only processed after the metadata update completes\n - call raid_end_bio_io() on bios in that queue when the time comes.\n\nSigned-off-by: NeilBrown <neilb@suse.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/95af587e95aacb9cfda4a9641069a5244a540dc8"},{"sha":"34a6f80e1639b124f24b5fadc1d45d69417cbace","author":{"email":"1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.com","name":"NeilBrown"},"message":"md/raid5: use bio_list for the list of bios to return.\n\nThis will make it easier to splice two lists together which will\nbe needed in future patch.\n\nSigned-off-by: NeilBrown <neilb@suse.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/34a6f80e1639b124f24b5fadc1d45d69417cbace"},{"sha":"c3cce6cda162eb2b2960a85d9c8992f4f3be85d0","author":{"email":"1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.com","name":"NeilBrown"},"message":"md/raid5: ensure device failure recorded before write request returns.\n\nWhen a write to one of the devices of a RAID5/6 fails, the failure is\nrecorded in the metadata of the other devices so that after a restart\nthe data on the failed drive wont be trusted even if that drive seems\nto be working again (maybe a cable was unplugged).\n\nSimilarly when we record a bad-block in response to a write failure,\nwe must not let the write complete until the bad-block update is safe.\n\nCurrently there is no interlock between the write request completing\nand the metadata update.  So it is possible that the write will\ncomplete, the app will confirm success in some way, and then the\nmachine will crash before the metadata update completes.\n\nThis is an extremely small hole for a racy to fit in, but it is\ntheoretically possible and so should be closed.\n\nSo:\n - set MD_CHANGE_PENDING when requesting a metadata update for a\n   failed device, so we can know with certainty when it completes\n - queue requests that completed when MD_CHANGE_PENDING is set to\n   only be processed after the metadata update completes\n - call raid_end_bio_io() on bios in that queue when the time comes.\n\n\nSigned-off-by: NeilBrown <neilb@suse.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/c3cce6cda162eb2b2960a85d9c8992f4f3be85d0"},{"sha":"7955323bdcab307bd8b1d5ef7a031e4a3d059da3","author":{"email":"aacdd228f50c574b28b524b23f12fb9d52d6e0e3@cn.fujitsu.com","name":"Zhao Lei"},"message":"btrfs: Update out-of-date \"skip parity stripe\" comment\n\nBecause btrfs support scrub raid56 parity stripe now.\n\nSigned-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>\nSigned-off-by: Chris Mason <clm@fb.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/7955323bdcab307bd8b1d5ef7a031e4a3d059da3"},{"sha":"8c204c9657c32ec5a259ebf852a767afe7efdafa","author":{"email":"aacdd228f50c574b28b524b23f12fb9d52d6e0e3@cn.fujitsu.com","name":"Zhao Lei"},"message":"btrfs: Remove noused chunk_tree and chunk_objectid from scrub_enumerate_chunks and scrub_chunk\n\nThese variables are not used from introduced version, remove them.\n\nSigned-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>\nSigned-off-by: Chris Mason <clm@fb.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/8c204c9657c32ec5a259ebf852a767afe7efdafa"},{"sha":"2c4580454fffbf184fdb9292aa19ab1ffc224add","author":{"email":"aacdd228f50c574b28b524b23f12fb9d52d6e0e3@cn.fujitsu.com","name":"Zhao Lei"},"message":"btrfs: Cleanup for btrfs_calc_num_tolerated_disk_barrier_failures\n\n1: Use ARRAY_SIZE(types) to replace a static-value variant:\n   int num_types = 4;\n\n2: Use 'continue' on condition to reduce one level tab\n   if (!XXX) {\n       code;\n       ...\n   }\n   ->\n   if (XXX)\n       continue;\n   code;\n   ...\n\n3: Put setting 'num_tolerated_disk_barrier_failures = 2' to\n   (num_tolerated_disk_barrier_failures > 2) condition to make\n   make logic neat.\n   if (num_tolerated_disk_barrier_failures > 0 && XXX)\n       num_tolerated_disk_barrier_failures = 0;\n   else if (num_tolerated_disk_barrier_failures > 1) {\n       if (XXX)\n           num_tolerated_disk_barrier_failures = 1;\n       else if (XXX)\n           num_tolerated_disk_barrier_failures = 2;\n   ->\n   if (num_tolerated_disk_barrier_failures > 0 && XXX)\n       num_tolerated_disk_barrier_failures = 0;\n   if (num_tolerated_disk_barrier_failures > 1 && XXX)\n       num_tolerated_disk_barrier_failures = ;\n   if (num_tolerated_disk_barrier_failures > 2 && XXX)\n       num_tolerated_disk_barrier_failures = 2;\n\n4: Remove comment of:\n   num_mirrors - 1: if RAID1 or RAID10 is configured and more\n   than 2 mirrors are used.\n   which is not fit with code.\n\nSigned-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>\nSigned-off-by: Chris Mason <clm@fb.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/2c4580454fffbf184fdb9292aa19ab1ffc224add"},{"sha":"943c6e9925d90dc80207322b5799d95fb90ffec0","author":{"email":"aacdd228f50c574b28b524b23f12fb9d52d6e0e3@cn.fujitsu.com","name":"Zhao Lei"},"message":"btrfs: Add raid56 support for updating\n num_tolerated_disk_barrier_failures in btrfs_balance\n\nCode for updating fs_info->num_tolerated_disk_barrier_failures in\nbtrfs_balance() lacks raid56 support.\n\nReason:\n Above code was wroten in 2012-08-01, together with\n btrfs_calc_num_tolerated_disk_barrier_failures()'s first version.\n\n Then, btrfs_calc_num_tolerated_disk_barrier_failures() got updated\n later to support raid56, but code in btrfs_balance() was not\n updated together.\n\nFix:\n Merge above similar code to a common function:\n btrfs_get_num_tolerated_disk_barrier_failures()\n and make it support both case.\n\n It can fix this bug with a bonus of cleanup, and make these code\n never in above no-sync state from now on.\n\nSuggested-by: Anand Jain <anand.jain@oracle.com>\nSigned-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>\nSigned-off-by: Chris Mason <clm@fb.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/943c6e9925d90dc80207322b5799d95fb90ffec0"},{"sha":"c6dd6ea55758cf403bdc07a51a06c2a1d474f906","author":{"email":"f41a7033a6382ce00d6b717e37d942dbe3c9a107@cn.fujitsu.com","name":"Qu Wenruo"},"message":"btrfs: async_thread: Fix workqueue 'max_active' value when initializing\n\nAt initializing time, for threshold-able workqueue, it's max_active\nof kernel workqueue should be 1 and grow if it hits threshold.\n\nBut due to the bad naming, there is both 'max_active' for kernel\nworkqueue and btrfs workqueue.\nSo wrong value is given at workqueue initialization.\n\nThis patch fixes it, and to avoid further misunderstanding, change the\nmember name of btrfs_workqueue to 'current_active' and 'limit_active'.\n\nAlso corresponding comment is added for readability.\n\nReported-by: Alex Lyakas <alex.btrfs@zadarastorage.com>\nSigned-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>\nSigned-off-by: Chris Mason <clm@fb.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/c6dd6ea55758cf403bdc07a51a06c2a1d474f906"},{"sha":"527afb4493c2892ce89fb74648e72a30b68ba120","author":{"email":"bbc079c7ff821d5e36ebf4ae2f9fd3690be38a1c@jp.fujitsu.com","name":"Tsutomu Itoh"},"message":"Btrfs: cleanup: remove unnecessary check before btrfs_free_path is called\n\nWe need not check path before btrfs_free_path() is called because\npath is checked in btrfs_free_path().\n\nSigned-off-by: Tsutomu Itoh <t-itoh@jp.fujitsu.com>\nReviewed-by: Qu Wenruo <quwenruo@cn.fujitsu.com>\nSigned-off-by: Chris Mason <clm@fb.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/527afb4493c2892ce89fb74648e72a30b68ba120"},{"sha":"0a2050d744037158de773be5c6f1fc468a551bae","author":{"email":"16a37b8b71ffafad4e89ce1ff841da282b29daf2@gmail.com","name":"Kinglong Mee"},"message":"NFSD: Store parent's stat in a separate value\n\nAfter commit ae7095a7c4 (nfsd4: helper function for getting mounted_on\nino) we ignore the return value from get_parent_attributes().\n\nAlso, the following FATTR4_WORD2_LAYOUT_BLKSIZE uses stat.blksize, so to\navoid overwriting that, use an independent value for the parent's\nattributes.\n\nSigned-off-by: Kinglong Mee <kinglongmee@gmail.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/0a2050d744037158de773be5c6f1fc468a551bae"},{"sha":"6896f15aabde505b35888039af93d1d182a0108a","author":{"email":"16a37b8b71ffafad4e89ce1ff841da282b29daf2@gmail.com","name":"Kinglong Mee"},"message":"nfsd: Fix an FS_LAYOUT_TYPES/LAYOUT_TYPES encode bug\n\nCurrently we'll respond correctly to a request for either\nFS_LAYOUT_TYPES or LAYOUT_TYPES, but not to a request for both\nattributes simultaneously.\n\nSigned-off-by: Kinglong Mee <kinglongmee@gmail.com>\nReviewed-by: Christoph Hellwig <hch@lst.de>\nCc: stable@vger.kernel.org\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/6896f15aabde505b35888039af93d1d182a0108a"},{"sha":"7d580722c9f353d19e255f929d341caa821060d6","author":{"email":"16a37b8b71ffafad4e89ce1ff841da282b29daf2@gmail.com","name":"Kinglong Mee"},"message":"nfsd: SUPPATTR_EXCLCREAT must be encoded before SECURITY_LABEL.\n\nThe encode order should be as the bitmask defined order.\n\nSigned-off-by: Kinglong Mee <kinglongmee@gmail.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/7d580722c9f353d19e255f929d341caa821060d6"},{"sha":"ead8fb8c24411722b92198b3dccd102a76cdd050","author":{"email":"16a37b8b71ffafad4e89ce1ff841da282b29daf2@gmail.com","name":"Kinglong Mee"},"message":"NFSD: Set the attributes used to store the verifier for EXCLUSIVE4_1\n\nAccording to rfc5661 18.16.4,\n\"If EXCLUSIVE4_1 was used, the client determines the attributes\n used for the verifier by comparing attrset with cva_attrs.attrmask;\"\n\nSo, EXCLUSIVE4_1 also needs those bitmask used to store the verifier.\n\nSigned-off-by: Kinglong Mee <kinglongmee@gmail.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/ead8fb8c24411722b92198b3dccd102a76cdd050"},{"sha":"75976de6556f593f6c2a18bbbcfb1e594cc7598a","author":{"email":"16a37b8b71ffafad4e89ce1ff841da282b29daf2@gmail.com","name":"Kinglong Mee"},"message":"NFSD: Return word2 bitmask if setting security label in OPEN/CREATE\n\nSecurity label can be set in OPEN/CREATE request, nfsd should set\nthe bitmask in word2 if setting success.\n\nSigned-off-by: Kinglong Mee <kinglongmee@gmail.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/75976de6556f593f6c2a18bbbcfb1e594cc7598a"},{"sha":"1f65c17e15992193f1c3f735696872cb75191517","author":{"email":"51738506c1b2ccb0761f23bdc612c93babf738ea@redhat.com","name":"J. Bruce Fields"},"message":"nfsd: Add Jeff Layton as co-maintainer\n\nJeff has been doing a lot of development (including much of the\nstate-locking rewrite just as one example) plus lots of review and other\nmiscellaneous nfsd work, so let's acknowledge the status quo.\n\nI'll continue to be the one to send regular pull requests but Jeff will\nshould be available to cover there occasionally too.\n\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/1f65c17e15992193f1c3f735696872cb75191517"},{"sha":"7fadc59cc89f207ff6ca3d0951e11265fb4f806e","author":{"email":"6f29df8e90a57f1ba61ffd63b0468c86bb6d3a99@infradead.org","name":"Randy Dunlap"},"message":"fs: fix fs/locks.c kernel-doc warning\n\nFix kernel-doc warnings in fs/locks.c:\n\nWarning(..//fs/locks.c:1577): No description found for parameter 'flags'\n\nSigned-off-by: Randy Dunlap <rdunlap@infradead.org>\nSigned-off-by: Jeff Layton <jeff.layton@primarydata.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/7fadc59cc89f207ff6ca3d0951e11265fb4f806e"},{"sha":"46cc8ba30445025f0ed3ed9f429aea573b301122","author":{"email":"ae947f3c8df96e1dc851c5e3e5a930ce6d3f1f74@windriver.com","name":"Paul Gortmaker"},"message":"nfsd: don't WARN/backtrace for invalid container deployment.\n\nThese messages, combined with the backtrace they trigger, makes it seem\nlike a serious problem, though a quick search shows distros marking\nit as a \"won't fix\" non-issue when the problem is reported by users.\n\nThe backtrace is overkill, and only really manages to show that if\nyou follow the code path, you can't really avoid it with bootargs\nor configuration settings in the container.\n\nGiven that, lets tone it down a bit and get rid of the WARN severity,\nand the associated backtrace, so people aren't needlessly alarmed.\n\nAlso, lets drop the split printk line, since they are grep unfriendly.\n\nSigned-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/46cc8ba30445025f0ed3ed9f429aea573b301122"},{"sha":"51a545685905c934237e640083bc3aa40b36dc14","author":{"email":"4376fbf8623cd7b7c0232225289bb91cedc0a27f@poochiereds.net","name":"Jeff Layton"},"message":"nfsd: allow more than one laundry job to run at a time\n\nWe can potentially have several nfs4_laundromat jobs running if there\nare multiple namespaces running nfsd on the box. Those are effectively\nseparated from one another though, so I don't see any reason to\nserialize them.\n\nAlso, create_singlethread_workqueue automatically adds the\nWQ_MEM_RECLAIM flag. Since we run this job on a timer, it's not really\ninvolved in any reclaim paths. I see no need for a rescuer thread.\n\nSigned-off-by: Jeff Layton <jeff.layton@primarydata.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>","distinct":false,"url":"https://api.github.com/repos/mmind/linux-rockchip/commits/51a545685905c934237e640083bc3aa40b36dc14"}]}