{"push_id":947341709,"size":21,"distinct_size":21,"ref":"refs/heads/cm-11.0-old-base","head":"b918d7b2db5fa20888a09a56141f7d9c7da8041e","before":"b960b0911ea5c249902f8da30bd2151cc1b0c2c9","commits":[{"sha":"560e6bb61c851782c4321156e3748c6d3bc66f3c","author":{"email":"0cc5db7488e13b393f245aa6263acec5e92fdcc5@samsung.com","name":"Chao Yu"},"message":"f2fs: reduce searching region of segmap when free section\n\nIn __set_test_and_free we will check whether all segment are free in one section\nWhen free one segment, in order to set section to free status.\nBut the searching region of segmap is from start segno to last segno of f2fs,\nit's not necessary. So let's just only check all segment bitmap of target\nsection.\n\nSigned-off-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/560e6bb61c851782c4321156e3748c6d3bc66f3c"},{"sha":"c4dc7addb9d9df9e874d29f5f5724a1d5d5002e9","author":{"email":"b1ed892af366400004b51f70e40351e33707b6c4@intel.com","name":"Huang Ying"},"message":"f2fs: add f2fs_balance_fs for direct IO\n\nOtherwise, if a large amount of direct IO writes were done, the\nsegment allocation may be failed because no enough segments are gced.\n\nChanges:\n\nv2: add f2fs_balance_fs into __get_data_block instead of f2fs_direct_IO.\n\nSigned-off-by: Huang, Ying <ying.huang@intel.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/c4dc7addb9d9df9e874d29f5f5724a1d5d5002e9"},{"sha":"61b9b8249ab35f4cc680273935ee7392df6411aa","author":{"email":"0cc5db7488e13b393f245aa6263acec5e92fdcc5@samsung.com","name":"Chao Yu"},"message":"f2fs: fix to put root inode in error path of fill_super\n\nWe should put root inode correctly in error path of fill_super, otherwise we\nmay encounter a leak case of inode resource.\n\nSigned-off-by: Chao Yu <chao2.yu@samsung.com>\nReviewed-by: Gu Zheng <guz.fnst@cn.fujitsu.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/61b9b8249ab35f4cc680273935ee7392df6411aa"},{"sha":"a6b27711ae1172ee7da8be920700bb5ef9dc6b16","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: add nobarrier mount option\n\nThis patch adds a mount option, nobarrier, in f2fs.\nThe assumption in here is that file system keeps the IO ordering, but\ndoesn't care about cache flushes inside the storages.\n\nReviewed-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>\n\nConflicts:\n\tDocumentation/filesystems/f2fs.txt\n\nChange-Id: I2947cb10128efcf5647eff432d5fd959b2d2f5bc","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/a6b27711ae1172ee7da8be920700bb5ef9dc6b16"},{"sha":"08d7033e14338471c588fbec8f861b5fa68ea5a9","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: punch the core function for inode management\n\nThis patch punches out the core functions to manage the inode numbers.\n\nReviewed-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/08d7033e14338471c588fbec8f861b5fa68ea5a9"},{"sha":"108e994763b169423f1ffbdbc0971d99a26221a1","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: add infra for ino management\n\nThis patch changes the naming of orphan-related data structures to use as\ninode numbers managed globally.\nLater, we can use this facility for managing any inode number lists.\n\nReviewed-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/108e994763b169423f1ffbdbc0971d99a26221a1"},{"sha":"1225ce058c963b18c2bcf460c0bc42be351b3d7f","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: use radix_tree for ino management\n\nFor better ino management, this patch replaces the data structure from list\nto radix tree.\n\nReviewed-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/1225ce058c963b18c2bcf460c0bc42be351b3d7f"},{"sha":"7a04c13edec020eaf1c0f9e8473644f1d2f3b858","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: add info of appended or updated data writes\n\nThis patch introduces a inode number list in which represents inodes having\nappended data writes or updated data writes after last checkpoint.\nThis will be used at fsync to determine whether the recovery information\nshould be written or not.\n\nReviewed-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>\n\nConflicts:\n\tfs/f2fs/inode.c\n\nChange-Id: I94293cce161b66f4ac5f66dea230b9613aa9d68a","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/7a04c13edec020eaf1c0f9e8473644f1d2f3b858"},{"sha":"578b89a3425c42a1d48e7d26698672ecd9949379","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: skip unnecessary data writes during fsync\n\nThis patch intends to improve the fsync performance by skipping remaining the\nrecovery information, only when there is no data that we should recover.\n\nReviewed-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/578b89a3425c42a1d48e7d26698672ecd9949379"},{"sha":"b735caba6b0d10b670893f70d9be0984c273eda5","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: enable in-place-update for fdatasync\n\nThis patch enforces in-place-updates only when fdatasync is requested.\nIf we adopt this in-place-updates for the fdatasync, we can skip to write the\nrecovery information.\n\nReviewed-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/b735caba6b0d10b670893f70d9be0984c273eda5"},{"sha":"50d37f96b00020adf24f82cb7c6ab71d0c3d0b2e","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: fix wrong condition for unlikely\n\nThis patch fixes the wrongly used unlikely condition.\n\nReviewed-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/50d37f96b00020adf24f82cb7c6ab71d0c3d0b2e"},{"sha":"50ea9d5d43d240815c5770abf0cf0176d67597a0","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: test before set/clear bits\n\nIf the bit is already set, we don't need to reset it, and vice versa.\nBecause we don't need to make the caches dirty for that.\n\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/50ea9d5d43d240815c5770abf0cf0176d67597a0"},{"sha":"eb437266f2655a7ea50b8c90825c565c33619fcc","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: add tracepoint for f2fs_issue_flush\n\nThis patch adds a tracepoint for f2fs_issue_flush.\n\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/eb437266f2655a7ea50b8c90825c565c33619fcc"},{"sha":"60692ce84590c987189b4f1fb908ffe388370cd6","author":{"email":"a1284fb821e09a3210731cd21fb918d248a2b8f4@samsung.com","name":"Dongho Sim"},"message":"f2fs: remove redundant lines in allocate_data_block\n\nThere are redundant lines in allocate_data_block.\n\nIn this function, we call refresh_sit_entry with old seg and old curseg.\nAfter that, we call locate_dirty_segment with old curseg.\n\nBut, the new address is always allocated from old curseg and\nwe call locate_dirty_segment with old curseg in refresh_sit_entry.\nSo, we do not need to call locate_dirty_segment with old curseg again.\n\nWe've discussed like below:\n\nJaegeuk said:\n \"When considering SSR, we need to take care of the following scenario.\n  - old segno : X\n  - new address : Z\n  - old curseg : Y\n  This means, a new block is supposed to be written to Z from X.\n  And Z is newly allocated in the same path from Y.\n\n  In that case, we should trigger locate_dirty_segment for Y, since\n  it was a current_segment and can be dirty owing to SSR.\n  But that was not included in the dirty list.\"\n\nChangman said:\n \"We already choosed old curseg(Y) and then we allocate new address(Z) from old\n  curseg(Y). After that we call refresh_sit_entry(old address, new address).\n  In the funcation, we call locate_dirty_segment with old seg and old curseg.\n  So calling locate_dirty_segment after refresh_sit_entry again is redundant.\"\n\nJaegeuk said:\n \"Right. The new address is always allocated from old_curseg.\"\n\nReviewed-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Dongho Sim <dh.sim@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/60692ce84590c987189b4f1fb908ffe388370cd6"},{"sha":"19c31ff553867b9dc63f433c4b520751d565e5fa","author":{"email":"71255387a32c360dfbe6dfb7aaeb123bf1dc8cb6@kernel.org","name":"Jaegeuk Kim"},"message":"f2fs: fix coding style\n\nThis patch fixes wrong coding style.\n\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/19c31ff553867b9dc63f433c4b520751d565e5fa"},{"sha":"dbbd9f67b2ee0b49c5af27b57551ea502f7e1636","author":{"email":"0cc5db7488e13b393f245aa6263acec5e92fdcc5@samsung.com","name":"Chao Yu"},"message":"f2fs: reduce competition among node page writes\n\nWe do not need to block on ->node_write among different node page writers e.g.\nfsync/flush, unless we have a node page writer from write_checkpoint.\nSo it's better use rw_semaphore instead of mutex type for ->node_write to\npromote performance.\n\nSigned-off-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/dbbd9f67b2ee0b49c5af27b57551ea502f7e1636"},{"sha":"d9049b4f6d244c678a1d79f7d6adce5549479b6f","author":{"email":"0cc5db7488e13b393f245aa6263acec5e92fdcc5@samsung.com","name":"Chao Yu"},"message":"f2fs: add tracepoint for f2fs_direct_IO\n\nThis patch adds a tracepoint for f2fs_direct_IO.\n\nSigned-off-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>\n\nConflicts:\n\tfs/f2fs/data.c\n\nChange-Id: I4153a8bd8bd5fb46c42c2917ec3405e3b4a4dce8","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/d9049b4f6d244c678a1d79f7d6adce5549479b6f"},{"sha":"cc61202ebd81c8dbc35044804b350f34716523f6","author":{"email":"0cc5db7488e13b393f245aa6263acec5e92fdcc5@samsung.com","name":"Chao Yu"},"message":"f2fs: avoid skipping recover_inline_xattr after recover_inline_data\n\nWhen we recover data of inode in roll-forward procedure, and the inode has both\ninline data and inline xattr. We may skip recovering inline xattr if we recover\ninline data form node page first.\nThis patch will fix the problem that we lost inline xattr data in above\nscenario.\n\nSigned-off-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/cc61202ebd81c8dbc35044804b350f34716523f6"},{"sha":"20cadc236b5ef32d8dca6e36a6cc47f8a4a9db5e","author":{"email":"0cc5db7488e13b393f245aa6263acec5e92fdcc5@samsung.com","name":"Chao Yu"},"message":"f2fs: invalidate xattr node page when evict inode\n\nWhen inode is evicted, all the page cache belong to this inode should be\nreleased including the xattr node page. But previously we didn't do this, this\npatch fixed this issue.\n\nv2:\n o reposition invalidate_mapping_pages() to the right place suggested by\nJaegeuk Kim.\n\nSigned-off-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/20cadc236b5ef32d8dca6e36a6cc47f8a4a9db5e"},{"sha":"b4e089f96b470167565a9896b947d645c3f1df0f","author":{"email":"0cc5db7488e13b393f245aa6263acec5e92fdcc5@samsung.com","name":"Chao Yu"},"message":"f2fs: add f2fs_balance_fs for expand_inode_data\n\nThis patch adds f2fs_balance_fs in expand_inode_data to avoid allocation failure\nwith segment.\n\nSigned-off-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>","distinct":true,"url":"https://api.github.com/repos/xsynergy510x/GPE_Kernel/commits/b4e089f96b470167565a9896b947d645c3f1df0f"}]}