GitHub PushEvent at 2014-11-10 03:59:32
Repository: Samsung_STE_Kernel
Actor: Pieee85
Payload: {"shas":[["2fb6697f6d2d2888767789ccd9d9b66884005fac","f2ad263351ded8bf8d0b90799bb8b9622c429cf8@gmail.com","defconfigs: enable new exfat driver\n\nChange-Id: If23c2a08795416be48db1992313844a142987864","Zhao Wei Liew",true],["b25d31746c0e575deca3a265dd5bf487fe3d6b9a","a0b7b622a99434219a85e3f6ec66d9efb1743ad7@gmail.com","Reserve one more step for 1250 MHz\n\nWe enabled 100 MHz by default and we need one more step reserved to fit every freq step","Robert Rozic",true],["aac7dcc5989089ba74c245432fe7e7711dfc24b9","f2ad263351ded8bf8d0b90799bb8b9622c429cf8@gmail.com","defconfigs: enable lz4 compression support\n\nChange-Id: I79f04f3f0870d9528c5b10deb795081d92286cbb\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>","Zhao Wei Liew",true],["29815f39177242d8f485b066f2b3e8ff01e719bf","39ea6a09710987173e32e37c86918024a0f441c1@suse.de","mm: vmscan: If kswapd has been running too long, allow it to sleep\n\nUnder constant allocation pressure, kswapd can be in the situation where\nsleeping_prematurely() will always return true even if kswapd has been\nrunning a long time. Check if kswapd needs to be scheduled.\n\nSigned-off-by: Mel Gorman <mgorman@suse.de>","Mel Gorman",true],["725eb26cbab312d49067609f382ead040177c611","fdd63d6d2cf1fcca4a32e9bdba550776ff3f9f3c@motorola.com","HACK: selinux: Make sure valid sk->sk_security\n\n - check valid sk->sk_security pointer in sock_has_perm to avoid NULL\n   pointer dereference.\n\nInspired by conversation on Security Enhanced Android developers'\nmailing list:\n\nhttp://comments.gmane.org/gmane.comp.security.seandroid/1110\n\nChange-Id: I548a0a7f30b48d5bab7460ee4a9a69aa45600f0a\nSigned-off-by: Hong-Mei Li <a21834@motorola.com>\nReviewed-on: http://gerrit.pcs.mot.com/574782\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Check Patch <CHEKPACH@motorola.com>\nReviewed-by: Jeffrey Carlyle <jeff.carlyle@motorola.com>\nSubmit-Approved: Jira Key <jirakey@motorola.com>\nReviewed-on: http://gerrit.pcs.mot.com/576126","Hong-Mei Li",true],["cf3a831d9aec8cf9590f661b11f628f028138445","f2ad263351ded8bf8d0b90799bb8b9622c429cf8@gmail.com","Revert \"block: Tweak deadline and cfq tunables\"\n\nThis reverts commit 0ed66cfbbb01b7033012af0699125142235f0ef4.","Zhao Wei Liew",true],["5d8be05da4bd5441fc51f3b08af887d22bff5eb8","f2ad263351ded8bf8d0b90799bb8b9622c429cf8@gmail.com","block: tweak deadline scheduler again\n\nChange-Id: I521e5900882475cad63c7b01e74b6036781950d1\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>","Zhao Wei Liew",true],["33d308e136b5eb12b49b6419ebc5c13a40aefd60","7eae7c015abe6cfbcb55fd218cc6b352105b3f52@gmail.com","sioplus: relax sync_read_expire, tighten sync_write_expire","Boy Petersen",true],["11eb8982f2058d61514bd82bede8263c2cb201ad","7eae7c015abe6cfbcb55fd218cc6b352105b3f52@gmail.com","Revert \"sioplus: tweak writes_tarved for new memory updates\"\n\nThis reverts commit 6900fb4f27a68c5da223c744cbb30bc304c2f387.","Boy Petersen",true],["15d048b59f3e0dd49d926019321c13ebfc7cd748","c0c0c8857ed6ec93282de3ee9d47e224acf995af@fusionio.com","block: recursive merge requests\n\nIn a workload, thread 1 accesses a, a+2, ..., thread 2 accesses a+1, a+3,....\nWhen the requests are flushed to queue, a and a+1 are merged to (a, a+1), a+2\nand a+3 too to (a+2, a+3), but (a, a+1) and (a+2, a+3) aren't merged.\n\nIf we do recursive merge for such interleave access, some workloads throughput\nget improvement. A recent worload I'm checking on is swap, below change\nboostes the throughput around 5% ~ 10%.\n\nSigned-off-by: Shaohua Li <shli@fusionio.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","Shaohua Li",true],["a40ea6dd268d560693a7c13f91ab7a9579e19ca7","cd6badf7869d996b866599075536a600ed1910b5@redhat.com","iosched: prevent aliased requests from starving other I/O\n\nHi, Jens,\n\nIf you recall, I posted an RFC patch for this back in July of last year:\nhttp://lkml.org/lkml/2010/7/13/279\n\nThe basic problem is that a process can issue a never-ending stream of\nasync direct I/Os to the same sector on a device, thus starving out\nother I/O in the system (due to the way the alias handling works in both\ncfq and deadline).  The solution I proposed back then was to start\ndispatching from the fifo after a certain number of aliases had been\ndispatched.  Vivek asked why we had to treat aliases differently at all,\nand I never had a good answer.  So, I put together a simple patch which\nallows aliases to be added to the rb tree (it adds them to the right,\nthough that doesn't matter as the order isn't guaranteed anyway).  I\nthink this is the preferred solution, as it doesn't break up time slices\nin CFQ or batches in deadline.  I've tested it, and it does solve the\nstarvation issue.  Let me know what you think.\n\nCheers,\nJeff\n\nSigned-off-by: Jeff Moyer <jmoyer@redhat.com>\nSigned-off-by: Jens Axboe <jaxboe@fusionio.com>","Jeff Moyer",true],["caa44b51289083b45dee3378afb2f727fb320745","f2ad263351ded8bf8d0b90799bb8b9622c429cf8@gmail.com","cpufreq: interactive: reduce micro stuttering\n\nChange-Id: I77b330009984ebb7a540e1e84e5f8dbe772f59d2\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>","Zhao Wei Liew",true],["6b25d7f96926d5f5110cc8aac96d3ad14c1096b7","f2ad263351ded8bf8d0b90799bb8b9622c429cf8@gmail.com","Revert \"mm: Dynamic management of dirty page writebacks\"\n\nhaving a longer interval between writebacks can cause dirty pages to be swapped before being synchronised between cache and disk, thus causing data loss.\nThis reverts commit ea290e32d1d3735926747a5c464ccfe3ca927233.","Zhao Wei Liew",true],["eef6f323423002f353c1c1fa63df239f76ed5323","f2ad263351ded8bf8d0b90799bb8b9622c429cf8@gmail.com","deadline: tweak again\n\nAlso fix previous switched-up values.\n\nChange-Id: Idc227580c8308819b8e6ceb703dba2805fe458bd\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>","Zhao Wei Liew",true],["7165f3b8d1144fb468315bda2cfd31a37b32ee82","4d9e23a041ac966f5316a7481300d4ae12e806fe@redhat.com","sync: don't block the flusher thread waiting on IO\n\nWhen sync does it's WB_SYNC_ALL writeback, it issues data Io and\nthen immediately waits for IO completion. This is done in the\ncontext of the flusher thread, and hence completely ties up the\nflusher thread for the backing device until all the dirty inodes\nhave been synced. On filesystems that are dirtying inodes constantly\nand quickly, this means the flusher thread can be tied up for\nminutes per sync call and hence badly affect system level write IO\nperformance as the page cache cannot be cleaned quickly.\n\nWe already have a wait loop for IO completion for sync(2), so cut\nthis out of the flusher thread and delegate it to wait_sb_inodes().\nHence we can do rapid IO submission, and then wait for it all to\ncomplete.\n\nEffect of sync on fsmark before the patch:\n\nFSUse%        Count         Size    Files/sec     App Overhead\n.....\n     0       640000         4096      35154.6          1026984\n     0       720000         4096      36740.3          1023844\n     0       800000         4096      36184.6           916599\n     0       880000         4096       1282.7          1054367\n     0       960000         4096       3951.3           918773\n     0      1040000         4096      40646.2           996448\n     0      1120000         4096      43610.1           895647\n     0      1200000         4096      40333.1           921048\n\nAnd a single sync pass took:\n\n  real    0m52.407s\n  user    0m0.000s\n  sys     0m0.090s\n\nAfter the patch, there is no impact on fsmark results, and each\nindividual sync(2) operation run concurrently with the same fsmark\nworkload takes roughly 7s:\n\n  real    0m6.930s\n  user    0m0.000s\n  sys     0m0.039s\n\nIOWs, sync is 7-8x faster on a busy filesystem and does not have an\nadverse impact on ongoing async data write operations.\n\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\nReviewed-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n\nChange-Id: Ie5d1d7363c034fc55a942aaadc9ec751880eef7d\n[zwliew: backport]\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>","Dave Chinner",true],["1ad9391b6aada13d6d2390ab4ba0b49c0b96a9c1","596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz","writeback: fix occasional slow sync(1)\n\nIn case when system contains no dirty pages, wakeup_flusher_threads() will\nsubmit WB_SYNC_NONE writeback for 0 pages so wb_writeback() exits\nimmediately without doing anything, even though there are dirty inodes in\nthe system.  Thus sync(1) will write all the dirty inodes from a\nWB_SYNC_ALL writeback pass which is slow.\n\nFix the problem by using get_nr_dirty_pages() in wakeup_flusher_threads()\ninstead of calculating number of dirty pages manually.  That function also\ntakes number of dirty inodes into account.\n\nSigned-off-by: Jan Kara <jack@suse.cz>\nReported-by: Paul Taysom <taysom@chromium.org>\nCc: Wu Fengguang <fengguang.wu@intel.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","Jan Kara",true],["ce26d6b2a401478b8f2afe0166d298dd602e52b0","adb0658383f88ec6beb1fb7689ba0dac7c1c4882@oracle.com","writeback: fix race that cause writeback hung\n\nThere is a race between mark inode dirty and writeback thread, see the\nfollowing scenario.  In this case, writeback thread will not run though\nthere is dirty_io.\n\n__mark_inode_dirty()                                          bdi_writeback_workfn()\n\t...                                                       \t...\n\tspin_lock(&inode->i_lock);\n\t...\n\tif (bdi_cap_writeback_dirty(bdi)) {\n\t    <<< assume wb has dirty_io, so wakeup_bdi is false.\n\t    <<< the following inode_dirty also have wakeup_bdi false.\n\t    if (!wb_has_dirty_io(&bdi->wb))\n\t\t    wakeup_bdi = true;\n\t}\n\tspin_unlock(&inode->i_lock);\n\t                                                            <<< assume last dirty_io is removed here.\n\t                                                            pages_written = wb_do_writeback(wb);\n\t                                                            ...\n\t                                                            <<< work_list empty and wb has no dirty_io,\n\t                                                            <<< delayed_work will not be queued.\n\t                                                            if (!list_empty(&bdi->work_list) ||\n\t                                                                (wb_has_dirty_io(wb) && dirty_writeback_interval))\n\t                                                                queue_delayed_work(bdi_wq, &wb->dwork,\n\t                                                                    msecs_to_jiffies(dirty_writeback_interval * 10));\n\tspin_lock(&bdi->wb.list_lock);\n\tinode->dirtied_when = jiffies;\n\t<<< new dirty_io is added.\n\tlist_move(&inode->i_wb_list, &bdi->wb.b_dirty);\n\tspin_unlock(&bdi->wb.list_lock);\n\n\t<<< though there is dirty_io, but wakeup_bdi is false,\n\t<<< so writeback thread will not be waked up and\n\t<<< the new dirty_io will not be flushed.\n\tif (wakeup_bdi)\n\t    bdi_wakeup_thread_delayed(bdi);\n\nWriteback will run until there is a new flush work queued.  This may cause\na lot of dirty pages stay in memory for a long time.\n\nSigned-off-by: Junxiao Bi <junxiao.bi@oracle.com>\nReviewed-by: Jan Kara <jack@suse.cz>\nCc: Fengguang Wu <fengguang.wu@intel.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n\nChange-Id: I4853ae2173d1a529a6574b1b46f584b919647e99\n[zwliew: adapt to 3.0]\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>","Junxiao Bi",true],["7801544beeafac6b7ecb740eb8209dbfe6325114","5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","sched: Fix memory leakage in build_sched_groups()\n\nIn build_sched_groups() we don't need to call get_group() for cpus\nwhich are already covered in previous iterations. Calling get_group()\nwould mark the group used and eventually leak it since we wouldn't\nconnect it and not find it again to free it.\n\nThis will happen only in cases where sg->cpumask contained more than\none cpu (For any topology level). This patch would free sg's memory\nfor all cpus leaving the group leader as the group isn't marked used\nnow.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/7a61e955abdcbb1dfa9fe493f11a5ec53a11ddd3.1370948150.git.viresh.kumar@linaro.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\n\nChange-Id: Iec321e88e79427d1371b1bad5c1e1732b82900b4\n[zwliew: adapt to 3.0]\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>","Viresh Kumar",true],["560e42259359bba07b666e7e439f13f2c6057a6f","5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","workqueues: Introduce new flag WQ_POWER_EFFICIENT for power oriented workqueues\n\nWorkqueues can be performance or power-oriented. Currently, most workqueues are\nbound to the CPU they were created on. This gives good performance (due to cache\neffects) at the cost of potentially waking up otherwise idle cores (Idle from\nscheduler's perspective. Which may or may not be physically idle) just to\nprocess some work. To save power, we can allow the work to be rescheduled on a\ncore that is already awake.\n\nWorkqueues created with the WQ_UNBOUND flag will allow some power savings.\nHowever, we don't change the default behaviour of the system.  To enable\npower-saving behaviour, a new config option CONFIG_WQ_POWER_EFFICIENT needs to\nbe turned on. This option can also be overridden by the\nworkqueue.power_efficient boot parameter.\n\ntj: Updated config description and comments.  Renamed\n    CONFIG_WQ_POWER_EFFICIENT to CONFIG_WQ_POWER_EFFICIENT_DEFAULT.\n\nChange-Id: I13c3dc7398d6a6732d0af26a6af8ddbc48bf13ee\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nReviewed-by: Amit Kucheria <amit.kucheria@linaro.org>\nSigned-off-by: Tejun Heo <tj@kernel.org>\n[zwliew: backport]\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>","Viresh Kumar",true],["6fd4d3ea01f512b43c9c646fcc15178d3bf6ce80","5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","workqueue: Add system wide power_efficient workqueues\n\nThis patch adds system wide workqueues aligned towards power saving. This is\ndone by allocating them with WQ_UNBOUND flag if 'wq_power_efficient' is set to\n'true'.\n\ntj: updated comments a bit.\n\nChange-Id: I890a04edf137f953aee508748867a4550bad0757\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Tejun Heo <tj@kernel.org>","Viresh Kumar",true]],"size":105,"ref":"refs/heads/3.0.101-STABLE","head":"800b81e61d5fae6f9cbfb3907097e3c1f1d96573"}