{"push_id":967340810,"size":5,"distinct_size":5,"ref":"refs/heads/Elite-M-linuxdebug","head":"a3b6ea2f0e80c7ef66e4a2fad36e8738532609af","before":"9f9a29675d4f8890cfe54b0443faa468ddf4c375","commits":[{"sha":"c556c22057a9808eaced72b28c9bc38f0f74477d","author":{"email":"a781eab460d0b8de6413720f3ae4346867408d60@codeaurora.org","name":"Alok Chauhan"},"message":"msm: msm_bus: Suspected fix for deadlock\n\nmutex is not released while checking for\nnull pdata which can lead to possible deadlock\ncondition.\n\nChange-Id: I1dc3efd725df5bb75c96434a81d9a8f3f868cd0a\nSigned-off-by: Alok Chauhan <alokc@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Elite-Kernels/elite_shamu/commits/c556c22057a9808eaced72b28c9bc38f0f74477d"},{"sha":"1e685a36066fab0d6f2d0f8942944749e3e8f22a","author":{"email":"168a6a722f36cbfb19d9b32bbc952ac3ffb3b983@codeaurora.org","name":"Ujwal Patel"},"message":"msm: mdss: prevent excessive logging after shutdown requested.\n\nCurrent frame-buffer driver gets shutdown call back and it turns the\ndisplay off. Once shutdown call-back is received, any subsequent\nframe-buffer opens are rejected and an error log is generated. Now\nuser-land display clients are not aware of shutdown and they keep\nopening the frame-buffer devices repeatedly ignoring the failures and\nnotifications sent by the driver. Due to this, excessive logging is\nobserved which in turn leads to watch-dog bite and a crash. Prevent\nthis by generating error log only once and keep sending sysfs\nnotification for every rejected frame-buffer open.\n\nChange-Id: I9df6cb708a2d6c986a31324540a3d040dffbcdfc\nSigned-off-by: Ujwal Patel <ujwalp@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Elite-Kernels/elite_shamu/commits/1e685a36066fab0d6f2d0f8942944749e3e8f22a"},{"sha":"14672ab8432a5e50cb0a58bc1efe1fd8cc05a4c5","author":{"email":"10f5d60ce5fa6fe3c789dd71c5d6567abd91f3fa@google.com","name":"Tahsin Erdogan"},"message":"block: Make CFQ default to IOPS mode on SSDs\n\nCFQ idling causes reduced IOPS throughput on non-rotational disks.\nSince disk head seeking is not applicable to SSDs, it doesn't really\nhelp performance by anticipating future near-by IO requests.\n\nBy turning off idling (and switching to IOPS mode), we allow other\nprocesses to dispatch IO requests down to the driver and so increase IO\nthroughput.\n\nFollowing FIO benchmark results were taken on a cloud SSD offering with\nidling on and off:\n\nIdling     iops    avg-lat(ms)    stddev            bw\n------------------------------------------------------\n    On     7054    90.107         38.697     28217KB/s\n   Off    29255    21.836         11.730    117022KB/s\n\nfio --name=temp --size=100G --time_based --ioengine=libaio \\\n    --randrepeat=0 --direct=1 --invalidate=1 --verify=0 \\\n    --verify_fatal=0 --rw=randread --blocksize=4k --group_reporting=1 \\\n    --filename=/dev/sdb --runtime=10 --iodepth=64 --numjobs=10\n\nAnd the following is from a local SSD run:\n\nIdling     iops    avg-lat(ms)    stddev            bw\n------------------------------------------------------\n    On    19320    33.043         14.068     77281KB/s\n   Off    21626    29.465         12.662     86507KB/s\n\nfio --name=temp --size=5G --time_based --ioengine=libaio \\\n    --randrepeat=0 --direct=1 --invalidate=1 --verify=0 \\\n    --verify_fatal=0 --rw=randread --blocksize=4k --group_reporting=1 \\\n    --filename=/fio_data --runtime=10 --iodepth=64 --numjobs=10\n\nChange-Id: I2311c1b349092d5d6afe5200037f6aeccf506e04\nReviewed-by: Nauman Rafique <nauman@google.com>\nSigned-off-by: Tahsin Erdogan <tahsin@google.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/Elite-Kernels/elite_shamu/commits/14672ab8432a5e50cb0a58bc1efe1fd8cc05a4c5"},{"sha":"436f1a7bc5ae1b4b616841508d061d1b7653cdcb","author":{"email":"cd8c6775e60d6f67a6984377324e5290df3d5358@fb.com","name":"Jens Axboe"},"message":"cfq-iosched: fix the setting of IOPS mode on SSDs\n\nA previous commit wanted to make CFQ default to IOPS mode on\nnon-rotational storage, however it did so when the queue was\ninitialized and the non-rotational flag is only set later on\nin the probe.\n\nAdd an elevator hook that gets called off the add_disk() path,\nat that point we know that feature probing has finished, and\nwe can reliably check for the various flags that drivers can\nset.\n\nChange-Id: Ieaf0beed1efc0ace7e61766e725647c6509e9852\nFixes: 41c0126b (\"block: Make CFQ default to IOPS mode on SSDs\")\nTested-by: Romain Francoise <romain@orebokech.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/Elite-Kernels/elite_shamu/commits/436f1a7bc5ae1b4b616841508d061d1b7653cdcb"},{"sha":"a3b6ea2f0e80c7ef66e4a2fad36e8738532609af","author":{"email":"58d301c70203188c35d379474c26c9cc0636a189@google.com","name":"Neal Cardwell"},"message":"tcp: fix timing issue in CUBIC slope calculation\n\nThis patch fixes a bug in CUBIC that causes cwnd to increase slightly\ntoo slowly when multiple ACKs arrive in the same jiffy.\n\nIf cwnd is supposed to increase at a rate of more than once per jiffy,\nthen CUBIC was sometimes too slow. Because the bic_target is\ncalculated for a future point in time, calculated with time in\njiffies, the cwnd can increase over the course of the jiffy while the\nbic_target calculated as the proper CUBIC cwnd at time\nt=tcp_time_stamp+rtt does not increase, because tcp_time_stamp only\nincreases on jiffy tick boundaries.\n\nSo since the cnt is set to:\n\tca->cnt = cwnd / (bic_target - cwnd);\nas cwnd increases but bic_target does not increase due to jiffy\ngranularity, the cnt becomes too large, causing cwnd to increase\ntoo slowly.\n\nFor example:\n- suppose at the beginning of a jiffy, cwnd=40, bic_target=44\n- so CUBIC sets:\n   ca->cnt =  cwnd / (bic_target - cwnd) = 40 / (44 - 40) = 40/4 = 10\n- suppose we get 10 acks, each for 1 segment, so tcp_cong_avoid_ai()\n   increases cwnd to 41\n- so CUBIC sets:\n   ca->cnt =  cwnd / (bic_target - cwnd) = 41 / (44 - 41) = 41 / 3 = 13\n\nSo now CUBIC will wait for 13 packets to be ACKed before increasing\ncwnd to 42, insted of 10 as it should.\n\nThe fix is to avoid adjusting the slope (determined by ca->cnt)\nmultiple times within a jiffy, and instead skip to compute the Reno\ncwnd, the \"TCP friendliness\" code path.\n\nReported-by: Eyal Perry <eyalpe@mellanox.com>\nSigned-off-by: Neal Cardwell <ncardwell@google.com>\nSigned-off-by: Yuchung Cheng <ycheng@google.com>\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":true,"url":"https://api.github.com/repos/Elite-Kernels/elite_shamu/commits/a3b6ea2f0e80c7ef66e4a2fad36e8738532609af"}]}