{"push_id":798544895,"size":75,"distinct_size":1,"ref":"refs/heads/topics/dt/ipaccess-boards","head":"51766a6cfec89e5fc337f957bb99e1892110b42b","before":"f44725dab6a4487eda032ac96810c458f0496e6f","commits":[{"sha":"5014c311baa2b21384321fa4a9f617a92e3e56f0","author":{"email":"cd8c6775e60d6f67a6984377324e5290df3d5358@fb.com","name":"Jens Axboe"},"message":"block: fix bogus compiler warnings in blk-merge.c\n\nThe compiler can't figure out that bvprv is initialized whenever 'prev'\nis set to 1 as well. Use a pointer to bvprv instead, setting it to NULL\ninitially, and get rid of the 'prev' tracking. This dumbs it down\nenough that gcc is happy.\n\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/5014c311baa2b21384321fa4a9f617a92e3e56f0"},{"sha":"de65d2d26f81f7f84c7258b3a137f20e8fa5bb6a","author":{"email":"77666125932addc6fc525b281b518fd8fd2203d8@lightnvm.io","name":"Matias Bjørling"},"message":"null_blk: fix memory leak on cleanup\n\nDriver was not freeing the memory allocated for internal nullb queues.\nThis patch frees the memory during driver unload.\n\nSigned-off-by: Matias Bjørling <mb@lightnvm.io>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/de65d2d26f81f7f84c7258b3a137f20e8fa5bb6a"},{"sha":"5fdb7e1b976dc9d18aff8c711e51d17c4c324a0e","author":{"email":"6b0d31c0d563223024da45691584643ac78c96e8@bjorling.me","name":"Matias Bjørling"},"message":"null_blk: fix wrong capacity when bs is not 512 bytes\n\nset_capacity() sets device's capacity using 512 bytes sectors.\nnull_blk calculates the number of sectors by size / bs, which\nset_capacity is called with. This led to null_blk exposing the\nwrong number of sectors when bs is not 512 bytes.\n\nSigned-off-by: Matias Bjørling <m@bjorling.me>\nReviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/5fdb7e1b976dc9d18aff8c711e51d17c4c324a0e"},{"sha":"5e7c4274a70aa2d6f485996d0ca1dad52d0039ca","author":{"email":"cd8c6775e60d6f67a6984377324e5290df3d5358@fb.com","name":"Jens Axboe"},"message":"block: Check for gaps on front and back merges\n\nWe are checking for gaps to previous bio_vec, which can\nonly detect back merges gaps. Moreover, at the point where\nwe check for a gap, we don't know if we will attempt a back\nor a front merge. Thus, check for gap to prev in a back merge\nattempt and check for a gap to next in a front merge attempt.\n\nSigned-off-by: Jens Axboe <axboe@fb.com>\n[sagig: Minor rename change]\nSigned-off-by: Sagi Grimberg <sagig@mellanox.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/5e7c4274a70aa2d6f485996d0ca1dad52d0039ca"},{"sha":"f47ff87f79a0f65db6af5b6bebd67b8f011994d1","author":{"email":"828c1a17681e8566a17a1a4801ea67306010b273@osg.samsung.com","name":"Javier Martinez Canillas"},"message":"PM / devfreq: event: Remove incorrect property in exynos-ppmu DT binding\n\nThe exynos-ppmu driver is only a clock consumer and not a clock provider\nbut its Device Tree binding listed #clock-cells as an optional property.\n\nSigned-off-by: Javier Martinez Canillas <javier@osg.samsung.com>\nReviewed-by: Chanwoo Choi <cw00.choi@samsung.com>\nSigned-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/f47ff87f79a0f65db6af5b6bebd67b8f011994d1"},{"sha":"77fe46a301a75795cf1d43ed2988a15c1600d1b5","author":{"email":"42eed19c0f56a8d487deac90c6d19d6364b7ba73@samsung.com","name":"Chanwoo Choi"},"message":"PM / devfreq: exynos-ppmu: Add the support of PPMUv2 for Exynos5433\n\nThis patch adds the support for PPMU (Platform Performance Monitoring Unit)\nversion 2.0 for Exynos5433 SoC. Exynos5433 SoC must need PPMUv2 which is\nquite different from PPMUv1.1. The exynos-ppmu.c driver supports both PPMUv1.1\nand PPMUv2.\n\nCc: MyungJoo Ham <myungjoo.ham@samsung.com>\nCc: Kyungmin Park <kyungmin.park@samsung.com>\nSigned-off-by: Chanwoo Choi <cw00.choi@samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/77fe46a301a75795cf1d43ed2988a15c1600d1b5"},{"sha":"d80f02231a1ee891f56f06ee6e4646db6ba28836","author":{"email":"42eed19c0f56a8d487deac90c6d19d6364b7ba73@samsung.com","name":"Chanwoo Choi"},"message":"PM / devfreq: exynos-ppmu: Update documentation to support PPMUv2\n\nThis patch updates the documentation to include the information of PPMUv2.\nThe PPMUv2 is used for Exynos5433 and Exynos7420 to monitor the performance\nof each IP in Exynos SoC.\n\nCc: MyungJoo Ham <myungjoo.ham@samsung.com>\nCc: Kyungmin Park <kyungmin.park@samsung.com>\nSigned-off-by: Chanwoo Choi <cw00.choi@samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/d80f02231a1ee891f56f06ee6e4646db6ba28836"},{"sha":"86fa4cdb0f1e16d7e27278e29e4f0b9ba22f1a9b","author":{"email":"84146178f7c201fa3079bfc93fccba71d81dffe3@samsung.com","name":"MyungJoo Ham"},"message":"PM / devfreq: exynos-ppmu: bit-wise operation bugfix.\n\nMake it u64 before left-shifting 32bits.\n\nSigned-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/86fa4cdb0f1e16d7e27278e29e4f0b9ba22f1a9b"},{"sha":"9348da2f1c2ca8e064d4907cdc5b3a19477df933","author":{"email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","name":"Viresh Kumar"},"message":"PM / devfreq: Drop unlikely before IS_ERR(_OR_NULL)\n\nIS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and there\nis no need to do that again from its callers. Drop it.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/9348da2f1c2ca8e064d4907cdc5b3a19477df933"},{"sha":"08e75e754a6d9838e490b74551d19fc04d0fd6f9","author":{"email":"cc0c468e3dcd5ee425259d298d905a60f8330bcf@arm.com","name":"Javi Merino"},"message":"PM / devfreq: cache the last call to get_dev_status()\n\nThe return value of get_dev_status() can be reused.  Cache it so that\nother parts of the kernel can reuse it instead of having to call the\nsame function again.\n\nCc: Kyungmin Park <kyungmin.park@samsung.com>\nSigned-off-by: Javi Merino <javi.merino@arm.com>\nSigned-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/08e75e754a6d9838e490b74551d19fc04d0fd6f9"},{"sha":"d3b7e1745c0d1be2add1bb58065eef142c5a098f","author":{"email":"cc0c468e3dcd5ee425259d298d905a60f8330bcf@arm.com","name":"Javi Merino"},"message":"PM / devfreq: drop comment about thermal setting max_freq\n\nThe thermal infrastructure should use the devfreq cooling device, which\nuses the OPP library to disable OPPs as necessary.\n\nFix a couple of typos in the same comment while we are at it.\n\nSigned-off-by: Javi Merino <javi.merino@arm.com>\nSigned-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/d3b7e1745c0d1be2add1bb58065eef142c5a098f"},{"sha":"d54cdf3fc91aae3780433471d15d73413a845bc0","author":{"email":"84146178f7c201fa3079bfc93fccba71d81dffe3@samsung.com","name":"MyungJoo Ham"},"message":"PM / devfreq: comments for get_dev_status usage updated\n\nWith the introduction of devfreq_update_stats(), governors\nare not recommended to use get_dev_status() directly.\n\nSigned-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/d54cdf3fc91aae3780433471d15d73413a845bc0"},{"sha":"14de3903181ca41dde73d57ad4f7a79a314ee6bf","author":{"email":"84146178f7c201fa3079bfc93fccba71d81dffe3@samsung.com","name":"MyungJoo Ham"},"message":"PM / devfreq: tegra: Update governor to use devfreq_update_stats()\n\nDirect invocation of get_dev_status() is no more recommended.\n\nSigned-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/14de3903181ca41dde73d57ad4f7a79a314ee6bf"},{"sha":"5f25f066f75a67835abb5e400471a27abd09395b","author":{"email":"882f949284518c6629430e71ade91307b006bf2f@marvell.com","name":"Xiaolong Ye"},"message":"PM / devfreq: Fix incorrect type issue.\n\ntime_in_state in struct devfreq is defined as unsigned long, so\ndevm_kzalloc should use sizeof(unsigned long) as argument instead\nof sizeof(unsigned int), otherwise it will cause unexpected result\nin 64bit system.\n\nSigned-off-by: Xiaolong Ye <yexl@marvell.com>\nSigned-off-by: Kevin Liu <kliu5@marvell.com>\nSigned-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/5f25f066f75a67835abb5e400471a27abd09395b"},{"sha":"7f39add3b08cbbdb99abe50e6d7c342e6800d684","author":{"email":"380ce2a82d3d08e67ab163b51dc6d30288ad3f13@mellanox.com","name":"Sagi Grimberg"},"message":"block: Refuse request/bio merges with gaps in the integrity payload\n\nIf a driver sets the block queue virtual boundary mask, it means that\nit cannot handle gaps so we must not allow those in the integrity\npayload as well.\n\nSigned-off-by: Sagi Grimberg <sagig@mellanox.com>\n\nFixed up by me to have duplicate integrity merge functions, depending\non whether block integrity is enabled or not. Fixes a compilations\nissue with CONFIG_BLK_DEV_INTEGRITY unset.\n\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/7f39add3b08cbbdb99abe50e6d7c342e6800d684"},{"sha":"87a816df537e096d404add543ef47b796906c130","author":{"email":"380ce2a82d3d08e67ab163b51dc6d30288ad3f13@mellanox.com","name":"Sagi Grimberg"},"message":"block: Refuse adding appending a gapped integrity page to a bio\n\nThis is only theoretical at the moment given that the only\nsubsystems that generate integrity payloads are the block layer\nitself and the scsi target (which generate well aligned integrity\npayloads). But when we will expose integrity meta-data to user-space,\nwe'll need to refuse appending a page with a gap (if the queue\nvirtual boundary is set).\n\nSigned-off-by: Sagi Grimberg <sagig@mellanox.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/87a816df537e096d404add543ef47b796906c130"},{"sha":"46348456c1791053dcbe5a9e21825b10a3c8a8fb","author":{"email":"380ce2a82d3d08e67ab163b51dc6d30288ad3f13@mellanox.com","name":"Sagi Grimberg"},"message":"block: Copy a user iovec if it includes gaps\n\nFor drivers that don't support gaps in the SG lists handed to\nthem we must bounce (copy the user buffers) and pass a bio that\ndoes not include gaps. This doesn't matter for any current user,\nbut will help to allow iser which can't handle gaps to use the\nblock virtual boundary instead of using driver-local bounce\nbuffering when handling SG_IO commands.\n\nSigned-off-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Sagi Grimberg <sagig@mellanox.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/46348456c1791053dcbe5a9e21825b10a3c8a8fb"},{"sha":"6fe810bda0bd9a5d7674fc671fac27b8aa8ec243","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"block: blkg_destroy_all() should clear q->root_blkg and ->root_rl.blkg\n\nWhile making the root blkg unconditional, ec13b1d6f0a0 (\"blkcg: always\ncreate the blkcg_gq for the root blkcg\") removed the part which clears\nq->root_blkg and ->root_rl.blkg during q exit.  This leaves the two\npointers dangling after blkg_destroy_all().  blk-throttle exit path\nperforms blkg traversals and dereferences ->root_blkg and can lead to\nthe following oops.\n\n BUG: unable to handle kernel NULL pointer dereference at 0000000000000558\n IP: [<ffffffff81389746>] __blkg_lookup+0x26/0x70\n ...\n task: ffff88001b4e2580 ti: ffff88001ac0c000 task.ti: ffff88001ac0c000\n RIP: 0010:[<ffffffff81389746>]  [<ffffffff81389746>] __blkg_lookup+0x26/0x70\n ...\n Call Trace:\n  [<ffffffff8138d14a>] blk_throtl_drain+0x5a/0x110\n  [<ffffffff8138a108>] blkcg_drain_queue+0x18/0x20\n  [<ffffffff81369a70>] __blk_drain_queue+0xc0/0x170\n  [<ffffffff8136a101>] blk_queue_bypass_start+0x61/0x80\n  [<ffffffff81388c59>] blkcg_deactivate_policy+0x39/0x100\n  [<ffffffff8138d328>] blk_throtl_exit+0x38/0x50\n  [<ffffffff8138a14e>] blkcg_exit_queue+0x3e/0x50\n  [<ffffffff8137016e>] blk_release_queue+0x1e/0xc0\n ...\n\nWhile the bug is a straigh-forward use-after-free bug, it is tricky to\nreproduce because blkg release is RCU protected and the rest of exit\npath usually finishes before RCU grace period.\n\nThis patch fixes the bug by updating blkg_destro_all() to clear\nq->root_blkg and ->root_rl.blkg.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nReported-by: \"Richard W.M. Jones\" <rjones@redhat.com>\nReported-by: Josh Boyer <jwboyer@fedoraproject.org>\nLink: http://lkml.kernel.org/g/CA+5PVA5rzQ0s4723n5rHBcxQa9t0cW8BPPBekr_9aMRoWt2aYg@mail.gmail.com\nFixes: ec13b1d6f0a0 (\"blkcg: always create the blkcg_gq for the root blkcg\")\nCc: stable@vger.kernel.org # v4.2+\nTested-by: Richard W.M. Jones <rjones@redhat.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/6fe810bda0bd9a5d7674fc671fac27b8aa8ec243"},{"sha":"380528f742796e1244e931c51e77c9ed664f566c","author":{"email":"9ab5f52a1ca0bcf4f70d6d9008e02f6134b5b8f2@sntech.de","name":"Heiko Stübner"},"message":"clk: rockchip: add critical clock for rk3368\n\nAgain a result of the gpio-clock-liberation the rk3368 needs the\npclk_pd_pmu marked as critical, to boot successfully.\n\nReported-by: Mark Rutland <mark.rutland@arm.com>\nSigned-off-by: Heiko Stuebner <heiko@sntech.de>\nTested-by: Mark Rutland <mark.rutland@arm.com>\nSigned-off-by: Stephen Boyd <sboyd@codeaurora.org>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/380528f742796e1244e931c51e77c9ed664f566c"},{"sha":"7ef7cc9fdf9853b3027c55b9481991695ad5e5b2","author":{"email":"836dd6e3e19dedf5f6942cbdbceecde111ecd1be@huawei.com","name":"Zhang Zhen"},"message":"seltests/zram: fix syntax error\n\nNot all shells define a variable UID. This is a bash and zsh feature only.\nIn other shells, the UID variable is not defined, so here test command\nexpands to [ != 0 ] which is a syntax error.\n\nWithout this patch:\nroot@HGH1000007090:/opt/work/linux/tools/testing/selftests/zram# sh zram.sh\nzram.sh: 8: [: !=: unexpected operator\nzram.sh : No zram.ko module or /dev/zram0 device file not found\nzram.sh : CONFIG_ZRAM is not set\n\nWith this patch:\nroot@HGH1000007090:/opt/work/linux/tools/testing/selftests/zram# sh ./zram.sh\nzram.sh : No zram.ko module or /dev/zram0 device file not found\nzram.sh : CONFIG_ZRAM is not set\n\nSigned-off-by: Zhang Zhen <zhenzhang.zhang@huawei.com>\nSigned-off-by: Shuah Khan <shuahkh@osg.samsung.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/7ef7cc9fdf9853b3027c55b9481991695ad5e5b2"}]}