{"push_id":2137790649,"size":75,"distinct_size":75,"ref":"refs/heads/caf/aosp-common/upstream-f2fs-stable-linux-4.9.y","head":"5b2b7f7dd87f36477599a7feda7cda5dfbb865bc","before":"8c9f3066a99bb63793b04326fa1f0aaea83b3f9d","commits":[{"sha":"c19928e660fbe021bf650553ca4ff88e5180e3ec","author":{"name":"Yunlong Song","email":"7108849fa5369d74ce1e809d043225672bdfb817@huawei.com"},"message":"Revert \"f2fs: node segment is prior to data segment selected victim\"\n\nThis reverts commit b9cd20619e359d199b755543474c3d853c8e3415.\n\nThat patch causes much fewer node segments (which can be used for SSR)\nthan before, and in the corner case (e.g. create and delete *.txt files in\none same directory, there will be very few node segments but many data\nsegments), if the reserved free segments are all used up during gc, then\nthe write_checkpoint can still flush dentry pages to data ssr segments,\nbut will probably fail to flush node pages to node ssr segments, since\nthere are not enough node ssr segments left (the left ones are all\nfull).\n\nSo revert this patch to give a fair chance to let node segments remain\nfor SSR, which provides more robustness for corner cases.\n\nConflicts:\n\tfs/f2fs/gc.c\n\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/c19928e660fbe021bf650553ca4ff88e5180e3ec"},{"sha":"127faa71f6a6e5dc795250daf759d8ac3b5314f9","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"Revert \"f2fs: reuse nids more aggressively\"\n\nCommit 268344664603 (\"f2fs: reuse nids more aggressively\") tries to\nreuse nids as many as possilbe, in order to mitigate producing obsolete\nnode pages in page cache.\n\nBut acutally, before we reuse the nids and related node page cache,\nwe will always invalidate that node page, so there will be not any\nobsolete node pages in cache.\n\nLet's just revert previous commit, so that nm_i::next_scan_nid can be\nincreased ascendingly, making __build_free_nids traverses all NAT pages\nmore easily, finally, free nid bitmap cache can be enabled as soon as\npossible.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/127faa71f6a6e5dc795250daf759d8ac3b5314f9"},{"sha":"126221de375bfafecfc9d195a1d23c05c21166c4","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: introduce read_inline_xattr\n\nCommit ba38c27eb93e (\"f2fs: enhance lookup xattr\") introduces\nlookup_all_xattrs duplicating from read_all_xattrs, which leaves\nlots of similar codes in between them, so introduce new help\nread_inline_xattr to clean up redundant codes.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/126221de375bfafecfc9d195a1d23c05c21166c4"},{"sha":"20ef20fbf78e50d865a8ffa36f4b9c1c32a19c10","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: introduce read_xattr_block\n\nCommit ba38c27eb93e (\"f2fs: enhance lookup xattr\") introduces\nlookup_all_xattrs duplicating from read_all_xattrs, which leaves\nlots of similar codes in between them, so introduce new help\nread_xattr_block to clean up redundant codes.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/20ef20fbf78e50d865a8ffa36f4b9c1c32a19c10"},{"sha":"2f0df25e6529201e5e464f576ba226023cc09672","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: show flush list status in sysfs\n\nThis patch adds to show flush list status in sysfs.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/2f0df25e6529201e5e464f576ba226023cc09672"},{"sha":"3f01af786c84eccdc6b77cca76105a81765a4fe1","author":{"name":"Hsiang Kao","email":"d3ec0978bb8414fadfb9a07d6c4f9fdad699d4c4@aol.com"},"message":"f2fs: allow readpages with NULL file pointer\n\nKeep in line with the other Linux file system implementations\nsince page_cache_sync_readahead supports NULL file pointer,\nand thus we can readahead data by f2fs itself without file opening\n(something like the btrfs behavior).\n\nSigned-off-by: Gao Xiang <gaoxiang25@huawei.com>\nReviewed-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/3f01af786c84eccdc6b77cca76105a81765a4fe1"},{"sha":"8456d343780d634a6e1a68883afe1e1ef5e7a6cf","author":{"name":"Weichao Guo","email":"eda93f25a3b8af7df17ec911111f28fb2cfdf82c@huawei.com"},"message":"f2fs: convert inline data for direct I/O & FI_NO_PREALLOC\n\nIn FI_NO_PREALLOC cases, direct I/O path may allocate blocks for an\ninode but keep its inline data flag. This inconsistency may trigger\nvfs clear_inode nrpages bug_on when evicting the inode. We should\nconvert inline data first in this case.\n\nSigned-off-by: Weichao Guo <guoweichao@huawei.com>\nReviewed-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/8456d343780d634a6e1a68883afe1e1ef5e7a6cf"},{"sha":"84af6aeceb49868181751252387505309babcf28","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: obsolete ALLOC_NID_LIST list\n\nAs Fan Li reported, there is no user traversing nid_list[ALLOC_NID_LIST]\nwhich is used for tracking preallocated nids. Let's drop it, and only\ntrack preallocated nids in free_nid_root radix-tree.\n\nReported-by: Fan Li <fanofcode.li@samsung.com>\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/84af6aeceb49868181751252387505309babcf28"},{"sha":"cacc1ed0c46a3a16a63028e5fdd16f7749477bb2","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: drop FI_UPDATE_WRITE tag after f2fs_issue_flush\n\nIf we failed to issue flush in ->fsync, we need to keep FI_UPDATE_WRITE\nflag to make sure triggering flush in next ->fsync.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/cacc1ed0c46a3a16a63028e5fdd16f7749477bb2"},{"sha":"0597a6e4bdcde2f12a6a0fe9e8ede9c573f36827","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: fix to show ino management cache size correctly\n\nIt needs to stat size of ino management cache with all type instead of\norphan ino type.\n\nFixes: 652be55162dc (\"f2fs: show # of orphan inodes\")\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/0597a6e4bdcde2f12a6a0fe9e8ede9c573f36827"},{"sha":"f014be822ce7372bd3cb14044e3e320211e68c22","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: enhance multiple device flush\n\nWhen multiple device feature is enabled, during ->fsync we will issue\nflush in all devices to make sure node/data of the file being persisted\ninto storage. But some flushes of device could be unneeded as file's\ndata may be not writebacked into those devices. So this patch adds and\nmanage bitmap per inode in global cache to indicate which device is\ndirty and it needs to issue flush during ->fsync, hence, we could improve\nperformance of fsync in scenario of multiple device.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/f014be822ce7372bd3cb14044e3e320211e68c22"},{"sha":"fd6422ea9264f1d1c9dad3d103fdc777163e1a0c","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: fix to flush multiple device in checkpoint\n\nIf f2fs manages multiple devices, in checkpoint, we need to issue flush\nin those devices which contain dirty data/node in their cache before\nwe write checkpoint region, otherwise, filesystem metadata could be\ncorrupted if hitting SPO after checkpoint.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/fd6422ea9264f1d1c9dad3d103fdc777163e1a0c"},{"sha":"28e1023e8e8ae06454c6fdec27730d89443158a6","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: support issuing/waiting discard in range\n\nFstrim intends to trim invalid blocks of filesystem only with specified\nrange and granularity, but actually, it will issue all previous cached\ndiscard commands which may be out-of-range and be with unmatched\ngranularity, it's unneeded.\n\nIn order to fix above issues, this patch introduces new helps to support\nto issue and wait discard in range and adds a new fstrim_list for tracking\nin-flight discard from ->fstrim.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/28e1023e8e8ae06454c6fdec27730d89443158a6"},{"sha":"69a596797adf633c193045cc8ef3d570c7ddd154","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: wrap discard policy\n\nThis patch wraps scattered optional parameters into discard policy as\nbelow, later, with it we expect that we can adjust these parameters with\nproper strategy in different scenario.\n\nstruct discard_policy {\n\tunsigned int min_interval;\t/* used for candidates exist */\n\tunsigned int max_interval;\t/* used for candidates not exist */\n\tunsigned int max_requests;\t/* # of discards issued per round */\n\tunsigned int io_aware_gran;\t/* minimum granularity discard not be aware of I/O */\n\tbool io_aware;\t\t\t/* issue discard in idle time */\n\tbool sync;\t\t\t/* submit discard with REQ_SYNC flag */\n};\n\nThis patch doesn't change any logic of codes.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/69a596797adf633c193045cc8ef3d570c7ddd154"},{"sha":"daf437d37cffd44d5fb5c1294a286d3fae6e22a9","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: split discard policy\n\nThere are many different scenarios such as fstrim, umount, urgent or\nbackground where we will issue discards, actually, they need use\ndifferent policy in aspect of io aware, discard granularity, delay\ninterval and so on. But now they just share one common discard policy,\nso there will be race when changing policy in between these scenarios,\nthe interference of changing discard policy will be very serious.\n\nThis patch changes to split discard policy for different scenarios.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/daf437d37cffd44d5fb5c1294a286d3fae6e22a9"},{"sha":"6c46b37d9b431be856fa9f28a1c25739823570da","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: reduce cmd_lock coverage in __issue_discard_cmd\n\n__submit_discard_cmd may lead long latency due to exhaustion of I/O\nrequest resource in block layer, so issuing all discard under cmd_lock\nmay lead to hangtask, in order to avoid that, let's reduce it's coverage.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/6c46b37d9b431be856fa9f28a1c25739823570da"},{"sha":"8258fd3054c10ed408ce36c6026705db10dd8bc7","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: trace f2fs_remove_discard\n\nThis patch adds tracepoint to trace f2fs_remove_discard.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/8258fd3054c10ed408ce36c6026705db10dd8bc7"},{"sha":"1e5305afa81e62ecac104f5fa3037726148707a3","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: give up CP_TRIMMED_FLAG if it drops discards\n\nIn ->umount, once we drop remained discard entries, we should not\nset CP_TRIMMED_FLAG with another checkpoint.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/1e5305afa81e62ecac104f5fa3037726148707a3"},{"sha":"595046758d8e69c440ea2f25d6a3014fa099a0ca","author":{"name":"Thomas Meyer","email":"5f919b14acad347486cfcc925fe5476cb2791020@m3y3r.de"},"message":"f2fs: Fix bool initialization/comparison\n\nBool initializations should use true and false. Bool tests don't need\ncomparisons.\n\nSigned-off-by: Thomas Meyer <thomas@m3y3r.de>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/595046758d8e69c440ea2f25d6a3014fa099a0ca"},{"sha":"33fdebbb0e7e83fd0096ca636a08c8ca1452143d","author":{"name":"Chao Yu","email":"7390b2c96c78abe47d370032752094fadd04c91d@huawei.com"},"message":"f2fs: fix to avoid race when accessing last_disk_size\n\nlast_disk_size could be wrong due to concurrently updating, so using\ni_sem semaphore to make last_disk_size updating exclusive to fix this\nissue.\n\nSigned-off-by: Chao Yu <yuchao0@huawei.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.10/commits/33fdebbb0e7e83fd0096ca636a08c8ca1452143d"}]}
{"actor":{"display_login":"akhilnarang"}}