)]}' { "log": [ { "commit": "8df5a3d4a4f01a605fedc50e98e45c27fb006cd3", "tree": "9b4e086d98d5a12a78349f20fd7f2fdf58a85ddf", "parents": [ "5c944b6e917000c072a7be1e7be598defea31b8b" ], "author": { "name": "Fu, Zhonghui", "email": "zhonghui.fu@linux.intel.com", "time": "Sat Sep 19 10:40:14 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Oct 08 13:51:22 2015 -0700" }, "message": "UPSTREAM: net/wireless: enable wiphy device to suspend/resume asynchronously\n\nNow, PM core supports asynchronous suspend/resume mode for devices\nduring system suspend/resume, and the power state transition of one\ndevice may be completed in separate kernel thread. PM core ensures\nall power state transition timing dependency between devices. This\npatch enables wiphy device to suspend/resume asynchronously. This can\ntake advantage of multicore and improve system suspend/resume speed.\n\nComparison of power_Resume test results (by cywang):\nw/o patch\nseconds_system_resume_kernel{perf}\u003d0.879189\nseconds_system_resume{perf}\u003d1.31215405464\nw/ patch\nseconds_system_resume_kernel{perf}\u003d0.634252\nseconds_system_resume{perf}\u003d1.07773995399\n\nThis shows an improvement of overall resume time of ~230 ms.\n\nBUG\u003dchrome-os-partner:46185\nTEST\u003drun the power_Resume test with and without this patch and check\nthat the total wake-up time is shorter with this patch.\n\nChange-Id: I5c09b78ffcc4c315ddc698a6e95b60174b7865b5\nSigned-off-by: Zhonghui Fu \u003czhonghui.fu@linux.intel.com\u003e\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\n(cherry-picked from 9f0e13546ef5773b7059b531a667ec47a5f897ee)\nSigned-off-by: Luca Coelho \u003cluciano.coelho@intel.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/304337\nReviewed-by: Sameer Nanda \u003csnanda@chromium.org\u003e\n" }, { "commit": "5c944b6e917000c072a7be1e7be598defea31b8b", "tree": "3e09e1cadb14e1af4146222bbe236b4ee8c67aea", "parents": [ "a1820211f6751968eafb2d82664b4104dfb3b7a9" ], "author": { "name": "Haixia Shi", "email": "hshi@chromium.org", "time": "Tue Oct 06 13:48:52 2015 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Oct 06 22:57:29 2015 -0700" }, "message": "CHROMIUM: drm/exynos: enable render node on exynos.\n\nBUG\u003dchromium:539965\nTEST\u003dupdate_kernel, verify that /dev/dri/renderD128 is present\nSigned-off-by: Haixia Shi \u003chshi@chromium.org\u003e\n\nChange-Id: I8ceabfc8d0be94388b76f1b0e288e95bc836e61b\nReviewed-on: https://chromium-review.googlesource.com/304322\nCommit-Ready: Haixia Shi \u003chshi@chromium.org\u003e\nTested-by: Haixia Shi \u003chshi@chromium.org\u003e\nReviewed-by: Ilja Friedel \u003cihf@chromium.org\u003e\nReviewed-by: Dominik Behr \u003cdbehr@chromium.org\u003e\n" }, { "commit": "a1820211f6751968eafb2d82664b4104dfb3b7a9", "tree": "75bec088306722298dab155fc0d76f8d987a52e4", "parents": [ "483c3cd331bd84466bfd447f39e1955ff161a1af" ], "author": { "name": "Benson Leung", "email": "bleung@chromium.org", "time": "Tue Nov 11 13:53:44 2014 -0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Oct 06 13:56:42 2015 -0700" }, "message": "CHROMIUM: HID: usbhid: get/put around clearing needs_remote_wakeup\n\nusbhid-\u003eintf-\u003eneeds_remote_wakeup is set when a device is\nopened, and is cleared when a device is closed.\n\nWhen a usbhid device that does not support remote wake\n( i.e. !device_can_wakeup() ) is closed, we fail out of\nautosuspend_check() because the autosuspend check is called\nbefore the flag is cleared as a result of usb_kill_urb(usbhid-\u003eurbin);\n\nThe result is that a device that may otherwise autosuspend will\nfail to enter suspend again after all handles to it are closed.\n\nIn usbhid_open, usb_autopm_get_interface is called\nbefore setting the needs_remote_wakeup flag, and\nusb_autopm_put_interface is called after hid_start_in.\n\nHowever, when the device is closed in usbhid_close, the same\nprotection isn\u0027t there when clearing needs_remote_wakeup. This will\nadd that to usbhid_close as well as usbhid_stop.\n\nSigned-off-by: Benson Leung \u003cbleung@chromium.org\u003e\n\nBUG\u003dchromium:431886\nTEST\u003dWhitelist security key devices using crosreview.com/229105\nPlug in the security key. After a second, touch the device.\nVerify that it has entered suspend (doesn\u0027t light up).\nBring up a 2 factor prompt that uses security key.\nTouch the key to proceed through the prompt.\nCheck that it succeeds.\nCheck that after 2 seconds, the device returns to suspended state.\n\nReviewed-on: https://chromium-review.googlesource.com/229176\nReviewed-by: Eric Caruso \u003cejcaruso@chromium.org\u003e\nCommit-Queue: Benson Leung \u003cbleung@chromium.org\u003e\nTrybot-Ready: Benson Leung \u003cbleung@chromium.org\u003e\nTested-by: Benson Leung \u003cbleung@chromium.org\u003e\n(cherry picked from commit 96b27c117496dc8ec885e4cbff39346e7aa57a6e)\nSigned-off-by: Benson Leung \u003cbleung@chromium.org\u003e\n\nChange-Id: If462785d61b0e8f4d592ed064ce48d06c3e478b9\nReviewed-on: https://chromium-review.googlesource.com/303932\nCommit-Ready: Benson Leung \u003cbleung@chromium.org\u003e\nTested-by: Benson Leung \u003cbleung@chromium.org\u003e\nReviewed-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\n" }, { "commit": "483c3cd331bd84466bfd447f39e1955ff161a1af", "tree": "f02badd0cc94534e3e7b502c7c64e5269bd39028", "parents": [ "4a9d5c1b56e45c8d04bc257aabb2b8932b86f8af" ], "author": { "name": "Johan Hovold", "email": "johan@kernel.org", "time": "Fri Sep 05 18:08:47 2014 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Oct 06 13:56:40 2015 -0700" }, "message": "BACKPORT: HID: usbhid: add always-poll quirk\n\nAdd quirk to make sure that a device is always polled for input events\neven if it hasn\u0027t been opened.\n\nThis is needed for devices that disconnects from the bus unless the\ninterrupt endpoint has been polled at least once or when not responding\nto an input event (e.g. after having shut down X).\n\nSigned-off-by: Johan Hovold \u003cjohan@kernel.org\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\n(cherry picked from commit 0b750b3baa2d64f1b77aecc10f20deeb28efe60d)\n[bleung : pulled in this patch verbatim upstream to resolve upstream conflicts]\nSigned-off-by: Benson Leung \u003cbleung@chromium.org\u003e\n\n Conflicts:\n\tinclude/linux/hid.h\n[bleung : Minor context conflict fix]\n\nBUG\u003dchromium:431886\nTEST\u003dNone.\n\nChange-Id: I948519c4a74ab37e36f291fd3dc9c46ae9600e1d\nReviewed-on: https://chromium-review.googlesource.com/303931\nCommit-Ready: Benson Leung \u003cbleung@chromium.org\u003e\nTested-by: Benson Leung \u003cbleung@chromium.org\u003e\nReviewed-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\n" }, { "commit": "4a9d5c1b56e45c8d04bc257aabb2b8932b86f8af", "tree": "5eef6f2de2c9eb9eaa396e08a615b0bbc9974d2f", "parents": [ "0a3094154c7431ac30ba99e8d12d30e51483ca21" ], "author": { "name": "Sasha Levin", "email": "sasha.levin@oracle.com", "time": "Thu Jul 31 23:00:35 2014 -0400" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Oct 06 07:40:36 2015 -0700" }, "message": "BACKPORT: iovec: make sure the caller actually wants anything in memcpy_fromiovecend\n\nCheck for cases when the caller requests 0 bytes instead of running off\nand dereferencing potentially invalid iovecs.\n\nSigned-off-by: Sasha Levin \u003csasha.levin@oracle.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n(cherry picked from commit 06ebb06d49486676272a3c030bfeef4bd969a8e6)\nSigned-off-by: Alexander Potapenko \u003cglider@google.com\u003e\n\nBUG\u003dchromium:539371\nTEST\u003dno KASan reports in memcpy_fromiovecend\n\nChange-Id: I28ffd50c9f1c2b5b0cd12643bb5582b68294f3db\nReviewed-on: https://chromium-review.googlesource.com/303611\nCommit-Ready: Alexander Potapenko \u003cglider@chromium.org\u003e\nTested-by: Alexander Potapenko \u003cglider@chromium.org\u003e\nReviewed-by: Filipe Brandenburger \u003cfilbranden@chromium.org\u003e\n" }, { "commit": "0a3094154c7431ac30ba99e8d12d30e51483ca21", "tree": "f07879c8996b0f9889a8d9d57284df77c3141436", "parents": [ "4c5b6a1303bbceaecd44756eb153643da2421587" ], "author": { "name": "henryhsu", "email": "henryhsu@chromium.org", "time": "Mon Oct 05 19:12:17 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Oct 06 06:12:10 2015 -0700" }, "message": "devfreq: exynos542x: Bump up LV_4 to LV_6 clocks of jpeg to 300MHz\n\nBump up the clocks of jpeg from 200MHz to 300MHz can improve 30%\ndecode latency.\n\nBUG\u003dchromium:426383\nTEST\u003drun jpeg standalone test and decode latency is from 4.66ms to\n3.209 ms for 720p image.\n\nChange-Id: I7785f9a92031be1d01b522306eb0aea047d31bb6\nSigned-off-by: Heng-Ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/304063\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Arjun K V \u003carjun.kv@samsung.com\u003e\nReviewed-by: Pawel Osciak \u003cposciak@chromium.org\u003e\n" }, { "commit": "4c5b6a1303bbceaecd44756eb153643da2421587", "tree": "ae0e6c019129c1444a6f6263e1c95fc3aa5d17c2", "parents": [ "32b54477aa0a25a95e4db862ad7b255bdec22b79" ], "author": { "name": "Cheng-Yi Chiang", "email": "cychiang@chromium.org", "time": "Mon Oct 05 12:44:22 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Oct 06 01:41:06 2015 -0700" }, "message": "CHROMIUM: ASOC: samsung: daisy_max98095: Remove redundant link\n\nThere should only be one DAI link named Primary.\n\nBUG\u003dchromium:455751\nTEST\u003d`aplay -l` to check there is only one device named Primary.\nTEST\u003dCheck playback/record functions on peach_pit are fine.\n\nSigned-off-by: Cheng-Yi Chiang \u003ccychiang@chromium.org\u003e\nChange-Id: I2cd15f759a0f514cf6b63dbd91274368579bf66e\nReviewed-on: https://chromium-review.googlesource.com/303597\n" }, { "commit": "32b54477aa0a25a95e4db862ad7b255bdec22b79", "tree": "1d0d50aae84299f2561cd4e447249548cf21930a", "parents": [ "15eda4ccd3b89688919e5e26ef9b3f8600ba8079" ], "author": { "name": "Sam Leffler", "email": "sleffler@chromium.org", "time": "Thu Apr 26 16:54:35 2012 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:24 2015 -0700" }, "message": "CHROMIUM: Add CLOCK_SYSTEM_TRACE to export the trace clock to user space.\n\nAdd a new clock type CLOCK_SYSTEM_TRACE to retrieve the current trace\nclock value (if CONFIG_TRACING is not defined then CLOCK_SYSTEM_TRACE\nreturns the same value as CLOCK_MONOTONIC_RAW). This allows user event\ntracing to timestamp data with the same clock as the kernel. This is\nin-lieu of sending event data through trace_write (which is not a viable\noption when there are lots of user-space events).\n\nBUG\u003dchromium:324025\nTEST\u003dChrome tracing works\n\nSigned-off-by: Sam Leffler \u003csleffler@chromium.org\u003e\n\nChange-Id: If2167ed99291e05f8c298638f4118b10b3e710f8\nReviewed-on: https://gerrit.chromium.org/gerrit/21404\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\nCommit-Ready: Sam Leffler \u003csleffler@chromium.org\u003e\nTested-by: Sam Leffler \u003csleffler@chromium.org\u003e\n[SR: we\u0027ll need this to be in place to avoid breaking Chrome while we\n transition to monotonic clock]\nConflicts:\n\tinclude/linux/kernel.h\nReviewed-on: https://chromium-review.googlesource.com/303497\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n" }, { "commit": "15eda4ccd3b89688919e5e26ef9b3f8600ba8079", "tree": "491a61fc1eac6ab4cdeeaa9c6e1caac0fa2601f9", "parents": [ "3393f3f8053cf912d77b3636cd8fbd3c8b4a1867" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:05:25 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:22 2015 -0700" }, "message": "BACKPORT: ftrace: Provide trace clocks monotonic\n\nExpose the new NMI safe accessor to clock monotonic to the tracer.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Steven Rostedt \u003crostedt@goodmis.org\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nCc: Mathieu Desnoyers \u003cmathieu.desnoyers@efficios.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 1b3e5c0936046e7e023149ddc8946d21c2ea20eb)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: context, 3.8 doesn\u0027t have as many clock types]\nConflicts:\n\tkernel/trace/trace.c\n\nChange-Id: I39001b72a011974a6393e809a6df3fe76e933d10\nReviewed-on: https://chromium-review.googlesource.com/300784\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "3393f3f8053cf912d77b3636cd8fbd3c8b4a1867", "tree": "5b5d1956cbfd4563b7df3db0cc0eed286d17929d", "parents": [ "15e1a498a7ce2a27386c54cff33a18fd8d9b6151" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:05:23 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:20 2015 -0700" }, "message": "BACKPORT: timekeeping: Provide fast and NMI safe access to CLOCK_MONOTONIC\n\nTracers want a correlated time between the kernel instrumentation and\nuser space. We really do not want to export sched_clock() to user\nspace, so we need to provide something sensible for this.\n\nUsing separate data structures with an non blocking sequence count\nbased update mechanism allows us to do that. The data structure\nrequired for the readout has a sequence counter and two copies of the\ntimekeeping data.\n\nOn the update side:\n\n smp_wmb();\n tkf-\u003eseq++;\n smp_wmb();\n update(tkf-\u003ebase[0], tk);\n smp_wmb();\n tkf-\u003eseq++;\n smp_wmb();\n update(tkf-\u003ebase[1], tk);\n\nOn the reader side:\n\n do {\n seq \u003d tkf-\u003eseq;\n smp_rmb();\n idx \u003d seq \u0026 0x01;\n now \u003d now(tkf-\u003ebase[idx]);\n smp_rmb();\n } while (seq !\u003d tkf-\u003eseq)\n\nSo if a NMI hits the update of base[0] it will use base[1] which is\nstill consistent, but this timestamp is not guaranteed to be monotonic\nacross an update.\n\nThe timestamp is calculated by:\n\n\tnow \u003d base_mono + clock_delta * slope\n\nSo if the update lowers the slope, readers who are forced to the\nnot yet updated second array are still using the old steeper slope.\n\n tmono\n ^\n | o n\n | o n\n | u\n | o\n |o\n |12345678---\u003e reader order\n\n o \u003d old slope\n u \u003d update\n n \u003d new slope\n\nSo reader 6 will observe time going backwards versus reader 5.\n\nWhile other CPUs are likely to be able observe that, the only way\nfor a CPU local observation is when an NMI hits in the middle of\nthe update. Timestamps taken from that NMI context might be ahead\nof the following timestamps. Callers need to be aware of that and\ndeal with it.\n\nV2: Got rid of clock monotonic raw and reorganized the data\n structures. Folded in the barrier fix from Mathieu.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.10 on squawks\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nCc: Steven Rostedt \u003crostedt@goodmis.org\u003e\nCc: Mathieu Desnoyers \u003cmathieu.desnoyers@efficios.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 4396e058c52e167729729cf64ea3dfa229637086)\n[SR: conflicts from not having CONFIG_GENERIC_TIME_VSYSCALL_OLD code\n or include/linux/timekeeping.h -- instead I moved to ktime.h]\nConflicts:\n\tinclude/linux/timekeeping.h\n\tkernel/time/timekeeping.c\n\nChange-Id: Ib485185104a388fd63fdaaa55f0b15b4acef9a7b\nReviewed-on: https://chromium-review.googlesource.com/302846\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "15e1a498a7ce2a27386c54cff33a18fd8d9b6151", "tree": "76c8fb4b1134da48f13db1cd12951aac230e5006", "parents": [ "247adb84c86ea498e29af2789d7d7cdb1eca9d87" ], "author": { "name": "Mathieu Desnoyers", "email": "mathieu.desnoyers@efficios.com", "time": "Wed Jul 16 21:05:21 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:18 2015 -0700" }, "message": "UPSTREAM: seqcount: Add raw_write_seqcount_latch()\n\nFor NMI safe access to clock monotonic we use the seqcount LSB as\nindex of a timekeeper array. The update sequence looks like this:\n\n smp_wmb(); \u003c- prior stores to a[1]\n seq++;\n smp_wmb(); \u003c- seq increment before update of a[0]\n update(a[0]);\n smp_wmb(); \u003c- update of a[0]\n seq++;\n smp_wmb(); \u003c- seq increment before update of a[1]\n update(a[1]);\n\nTo avoid open coded barriers, provide a helper function.\n\n[ tglx: Split out of a combo patch against the first implementation of\n \tthe NMI safe accessor ]\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Mathieu Desnoyers \u003cmathieu.desnoyers@efficios.com\u003e\nCc: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nCc: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Steven Rostedt \u003crostedt@goodmis.org\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 9b0fd802e8c0545148324916055e7b40d97963fa)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I1f8bfd65661df5d556a53cc278aa2a6730c329dd\nReviewed-on: https://chromium-review.googlesource.com/300783\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "247adb84c86ea498e29af2789d7d7cdb1eca9d87", "tree": "5f9a3d5e337d36bb59e570ee848d9b6304444c7b", "parents": [ "483306e7ad3b8eb48cd1b39448b39a64927a27fe" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:05:20 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:16 2015 -0700" }, "message": "BACKPORT: seqcount: Provide raw_read_seqcount()\n\nraw_read_seqcount opens a read critical section of the given seqcount\nwithout any lockdep checking and without checking or masking the\nLSB. Calling code is responsible for handling that.\n\nPreparatory patch to provide a NMI safe clock monotonic accessor\nfunction.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nCc: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Mathieu Desnoyers \u003cmathieu.desnoyers@efficios.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 0ea5a520f73ca31abc4c10b6d5bc14a884a0641b)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: trivial context differences]\nConflicts:\n\tinclude/linux/seqlock.h\n\nChange-Id: I828689f442b60d33c7bea7869d816afe9e94cab0\nReviewed-on: https://chromium-review.googlesource.com/300782\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "483306e7ad3b8eb48cd1b39448b39a64927a27fe", "tree": "26ffba139d18ee0e8d8c07579a55834ad1de826b", "parents": [ "25b443aa89791e1c4b912e77623e35c4c4501c25" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:05:18 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:15 2015 -0700" }, "message": "BACKPORT: timekeeping: Use tk_read_base as argument for timekeeping_get_ns()\n\nAll the function needs is in the tk_read_base struct. No functional\nchange for the current code, just a preparatory patch for the NMI safe\naccessor to clock monotonic which will use struct tk_read_base as well.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Steven Rostedt \u003crostedt@goodmis.org\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nCc: Mathieu Desnoyers \u003cmathieu.desnoyers@efficios.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 0e5ac3a8b100469ea154f87dd57b685fbdd356f6)\n[SR: conflicts from new ktime_* functions we don\u0027t have and\n restructuring of ktime_get_update_offsets() function and\n restructuring of get_monotonic_bootime() function]\nConflicts:\n\tkernel/time/timekeeping.c\n\nChange-Id: If2b0bd3c0d1e04449cb7872f00f54e434d6be8f1\nReviewed-on: https://chromium-review.googlesource.com/300781\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "25b443aa89791e1c4b912e77623e35c4c4501c25", "tree": "308d8eb0ce3f3556abda22fbed76f419ecb40dd9", "parents": [ "80ca1a54f8b9c5a82badd95f10f66aab8418b8dc" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:05:16 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:13 2015 -0700" }, "message": "BACKPORT: timekeeping: Create struct tk_read_base and use it in struct timekeeper\n\nThe members of the new struct are the required ones for the new NMI\nsafe accessor to clcok monotonic. In order to reuse the existing\ntimekeeping code and to make the update of the fast NMI safe\ntimekeepers a simple memcpy use the struct for the timekeeper as well\nand convert all users.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nCc: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Mathieu Desnoyers \u003cmathieu.desnoyers@efficios.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit d28ede83791defee9a81e558540699dc46dbbe13)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: several non-trivial differences from refactoring timekeeping.c\n and vsyscall code in x86 vsyscall_64.c -\u003e vsyscall_gtod.c]\n[SR: 3.8: tile doesn\u0027t have vsyscall in 3.8 and fix up timekeeper_resume()]\nConflicts:\n\tarch/s390/kernel/time.c\n\tarch/tile/kernel/time.c\n\tarch/x86/kernel/vsyscall_gtod.c\n\tarch/x86/kvm/x86.c\n\tinclude/linux/timekeeper_internal.h\n\tkernel/time/timekeeping.c\n\nChange-Id: Ie11521ead23722087f03e4ec3538cbdf34dc943a\nReviewed-on: https://chromium-review.googlesource.com/300780\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "80ca1a54f8b9c5a82badd95f10f66aab8418b8dc", "tree": "c94d2fd0f7c7a1dd0cc8639ddeffddcf34345448", "parents": [ "887efbea9b98b53e7879f163430148ad3de33001" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu Apr 25 20:31:44 2013 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:11 2015 -0700" }, "message": "UPSTREAM: clocksource: Let timekeeping_notify return success/error\n\ntimekeeping_notify() can fail due cs-\u003eenable() failure. Though the\ncaller does not notice and happily keeps the wrong clocksource as the\ncurrent one.\n\nLet the caller know about failure, so the current clocksource will be\nshown correctly in sysfs.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nAcked-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: Magnus Damm \u003cmagnus.damm@gmail.com\u003e\nLink: http://lkml.kernel.org/r/20130425143435.696321912@linutronix.de\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n(cherry picked from commit ba919d1caa2e624eb8c6cae1f2ce0a253e697d45)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: Ic312eebae1bd2d8ea3f56931656c2ab13294e114\nReviewed-on: https://chromium-review.googlesource.com/300779\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "887efbea9b98b53e7879f163430148ad3de33001", "tree": "f38541ab2af045bcb58fec9050dc3936003db958", "parents": [ "1a04cb4bb2d8a46dd6b44af25ed84153c1ee73ac" ], "author": { "name": "Nathan Lynch", "email": "nathan_lynch@mentor.com", "time": "Mon Feb 03 19:48:52 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:09 2015 -0700" }, "message": "UPSTREAM: arm64: vdso: update wtm fields for CLOCK_MONOTONIC_COARSE\n\nUpdate wall-to-monotonic fields in the VDSO data page\nunconditionally. These are used to service CLOCK_MONOTONIC_COARSE,\nwhich is not guarded by use_syscall.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Nathan Lynch \u003cnathan_lynch@mentor.com\u003e\nAcked-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nCc: \u003cstable@vger.kernel.org\u003e\nSigned-off-by: Catalin Marinas \u003ccatalin.marinas@arm.com\u003e\n(cherry picked from commit d4022a335271a48cce49df35d825897914fbffe3)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: Iebce00f5aa1c53b7c15dc23677ee435f9c86a0f9\nReviewed-on: https://chromium-review.googlesource.com/300778\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "1a04cb4bb2d8a46dd6b44af25ed84153c1ee73ac", "tree": "05b5dcf29a728704180fa6f9540ec0e3b3cb1c1a", "parents": [ "e9f6e369769710be34bc4c60a4f887c4ea66a906" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:05:15 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:07 2015 -0700" }, "message": "BACKPORT: timekeeping: Restructure the timekeeper some more\n\nAccess to time requires to touch two cachelines at minimum\n\n 1) The timekeeper data structure\n\n 2) The clocksource data structure\n\nThe access to the clocksource data structure can be avoided as almost\nall clocksource implementations ignore the argument to the read\ncallback, which is a pointer to the clocksource.\n\nBut the core needs to touch it to access the members @read and @mask.\n\nSo we are better off by copying the @read function pointer and the\n@mask from the clocksource to the core data structure itself.\n\nFor the most used ktime_get() access all required data including the\n@read and @mask copies fits together with the sequence counter into a\nsingle 64 byte cacheline.\n\nFor the other time access functions we touch in the current code three\ncache lines in the worst case. But with the clocksource data copies we\ncan reduce that to two adjacent cachelines, which is more efficient\nthan disjunct cache lines.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 6d3aadf3e180e09dbefab16478c6876b584ce16e)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: fix timekeeping_resume() again due to lack of e445cf1c4]\nConflicts:\n\tkernel/time/timekeeping.c\n\nChange-Id: I628664f3c063144e1a4035a6ece33a59f403b77d\nReviewed-on: https://chromium-review.googlesource.com/300777\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "e9f6e369769710be34bc4c60a4f887c4ea66a906", "tree": "20a51f693ba5857100449751245ab937ec6e4d13", "parents": [ "79f15fc8023cb36c8500dd88ba75909433cc712a" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:05:13 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:05 2015 -0700" }, "message": "BACKPORT: clocksource: Get rid of cycle_last\n\ncycle_last was added to the clocksource to support the TSC\nvalidation. We moved that to the core code, so we can get rid of the\nextra copy.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 4a0e637738f06673725792d74eed67f8779b62c7)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: missing new code in timekeeping.c and code in vsyscall_gtod.c moved from\n vsyscall_64.c]\n[SR: 3.8: tile doesn\u0027t have vsyscall code in 3.8 and needed to fix up\n timekeeping_resume because we don\u0027t have e445cf1c4]\nConflicts:\n\tarch/tile/kernel/time.c\n\tarch/x86/kernel/vsyscall_gtod.c\n\tkernel/time/timekeeping.c\n\nChange-Id: Icc7150363704b62ddaf3321abf1d2bd98af007e4\nReviewed-on: https://chromium-review.googlesource.com/300776\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "79f15fc8023cb36c8500dd88ba75909433cc712a", "tree": "0c8275f166fd1e4b885e0eadce763c76d1175032", "parents": [ "0ed47ddd169e6c87ca5ac4a0ae49419cc463c26f" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu Apr 25 20:31:44 2013 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:03 2015 -0700" }, "message": "UPSTREAM: clocksource: Add module refcount\n\nAdd a module refcount, so the current clocksource cannot be removed\nunconditionally.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: Magnus Damm \u003cmagnus.damm@gmail.com\u003e\nLink: http://lkml.kernel.org/r/20130425143435.762417789@linutronix.de\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n(cherry picked from commit 09ac369c825d9d593404306d59062d854b321e9b)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I8bc3af42129ec8993db02e757aac2d750e7ee3a3\nReviewed-on: https://chromium-review.googlesource.com/300775\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "0ed47ddd169e6c87ca5ac4a0ae49419cc463c26f", "tree": "dc2082c551a4d1164d5c32ac2dc0da0e56e527d1", "parents": [ "0bdac54ffb60b94a98689d223cba582d082619a5" ], "author": { "name": "Martin Schwidefsky", "email": "schwidefsky@de.ibm.com", "time": "Fri Nov 22 10:04:53 2013 +0100" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:13:01 2015 -0700" }, "message": "BACKPORT: s390/time,vdso: convert to the new update_vsyscall interface\n\nSwitch to the improved update_vsyscall interface that provides\nsub-nanosecond precision for gettimeofday and clock_gettime.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\n(cherry picked from commit 79c74ecbebf76732f91b82a62ce7fc8a88326962)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: trivial context conflict in Kconfig]\nConflicts:\n\tarch/s390/Kconfig\n\nChange-Id: I88661fff354edc7f8ee1f88354b3e45e3d345a48\nReviewed-on: https://chromium-review.googlesource.com/300774\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "0bdac54ffb60b94a98689d223cba582d082619a5", "tree": "e3c1abcbd7718c12e43c626b21e7d57d6cc1f534", "parents": [ "0ed166182826f8f13e5d7ca5c0120e9543a2e24a" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:05:12 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:59 2015 -0700" }, "message": "BACKPORT: clocksource: Move cycle_last validation to core code\n\nThe only user of the cycle_last validation is the x86 TSC. In order to\nprovide NMI safe accessor functions for clock monotonic and\nmonotonic_raw we need to do that in the core.\n\nWe can\u0027t do the TSC specific\n\n if (now \u003c cycle_last)\n \t now \u003d cycle_last;\n\nfor the other wrapping around clocksources, but TSC has\nCLOCKSOURCE_MASK(64) which actually does not mask out anything so if\nnow is less than cycle_last the subtraction will give a negative\nresult. So we can check for that in clocksource_delta() and return 0\nfor that case.\n\nImplement and enable it for x86\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 09ec54429c6d10f87d1f084de53ae2c1c3a81108)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: trivial conflict in Kconfig]\n[SR: 3.10: fix conflict in timekeeping_internal.h]\n[SR: 3.8: fix context conflict in tsc.c from 82f9c080]\nConflicts:\n\tarch/x86/Kconfig\n\tarch/x86/kernel/tsc.c\n\tkernel/time/timekeeping_internal.h\n\nChange-Id: Ib980b5ef4733e9f73f8c5222221ad439f8b306f6\nReviewed-on: https://chromium-review.googlesource.com/300773\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "0ed166182826f8f13e5d7ca5c0120e9543a2e24a", "tree": "39109bd0e149c88f757deb19a3a1c26d120d4b87", "parents": [ "bede3f778de462506a3037711f2d249f8ca7defc" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:05:10 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:57 2015 -0700" }, "message": "BACKPORT: clocksource: Make delta calculation a function\n\nWe want to move the TSC sanity check into core code to make NMI safe\naccessors to clock monotonic[_raw] possible. For this we need to\nsanity check the delta calculation. Create a helper function and\nconvert all sites to use it.\n\n[ Build fix from jstultz ]\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 3a97837784acbf9fed699fc04d1799b0eb742fdf)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: added timekeeping_internal.h to 3.8 in this patch and skipped\n patch to timekeeping_resume because we don\u0027t have e445cf1c4]\nConflicts:\n\tkernel/time/clocksource.c\n\tkernel/time/timekeeping.c\n\tkernel/time/timekeeping_internal.h\n\nChange-Id: I1319957806100c460d48d8b09bd44ec67f1a4ef3\nReviewed-on: https://chromium-review.googlesource.com/300772\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "bede3f778de462506a3037711f2d249f8ca7defc", "tree": "1f2255d32e31a19f27530b4434b91500a68ebfa0", "parents": [ "016fe83ee980d2c3aed98a38ae0e79276b621446" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:04:12 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:55 2015 -0700" }, "message": "BACKPORT: timekeeping: Use ktime_t based data for ktime_get()\n\nSpeed up ktime_get() by using ktime_t based data. Text size shrinks by\n64 bytes on x8664.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit a016a5bd62e29a738531d9d4d925037a1fdb52f5)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: conflict due to 24e4a8c3e8 related to timespec64/2038 changes]\nConflicts:\n\tkernel/time/timekeeping.c\n\nChange-Id: I059234d54d9501148e3a59dee68350637922751e\nReviewed-on: https://chromium-review.googlesource.com/300771\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "016fe83ee980d2c3aed98a38ae0e79276b621446", "tree": "55f4aad213aa2639440dada32af78245208c7de8", "parents": [ "c6f5a5cd966d0ec14045774d1888746894b35b09" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:04:10 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:53 2015 -0700" }, "message": "UPSTREAM: timekeeping: Provide internal ktime_t based data\n\nThe ktime_t based interfaces are used a lot in performance critical\ncode pathes. Add ktime_t based data so the interfaces don\u0027t have to\nconvert from the xtime/timespec based data.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 7c032df5570388044b4efda3d9f4d2ffb96a3116)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I27d2c32baacd4086eb8e68bb818b89842c6eb793\nReviewed-on: https://chromium-review.googlesource.com/300770\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "c6f5a5cd966d0ec14045774d1888746894b35b09", "tree": "d1d0e025e4049a6058bf76b708181160b344d91f", "parents": [ "4eb68b40c2afcc2d6d5bd4f9895a966939af9345" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Wed Jul 16 21:04:07 2014 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:51 2015 -0700" }, "message": "BACKPORT: timekeeping: Cache optimize struct timekeeper\n\nstruct timekeeper is quite badly sorted for the hot readout path. Most\ntime access functions need to load two cache lines.\n\nRearrange it so ktime_get() and getnstimeofday() are happy with a\nsingle cache line.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 3fdb14fd1df70325e1e91e1203a699a4803ed741)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: mostly conflicts from not having timespec64]\nConflicts:\n\tinclude/linux/timekeeper_internal.h\n\tkernel/time/timekeeping.c\n\nChange-Id: If2af5962d354f02c5d2a6c801326456898b52918\nReviewed-on: https://chromium-review.googlesource.com/300769\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "4eb68b40c2afcc2d6d5bd4f9895a966939af9345", "tree": "161d5f7e07ebc67adf8e28bff956081e4f1047e3", "parents": [ "6ddb4ae993085f7c23eb70dda9fb572529a893e9" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Wed Dec 11 19:10:36 2013 -0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:49 2015 -0700" }, "message": "UPSTREAM: timekeeping: Fix missing timekeeping_update in suspend path\n\nSince 48cdc135d4840 (Implement a shadow timekeeper), we have to\ncall timekeeping_update() after any adjustment to the timekeeping\nstructure in order to make sure that any adjustments to the structure\npersist.\n\nIn the timekeeping suspend path, we udpate the timekeeper\nstructure, so we should be sure to update the shadow-timekeeper\nbefore releasing the timekeeping locks. Currently this isn\u0027t done.\n\nIn most cases, the next time related code to run would be\ntimekeeping_resume, which does update the shadow-timekeeper, but\nin an abundence of caution, this patch adds the call to\ntimekeeping_update() in the suspend path.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Sasha Levin \u003csasha.levin@oracle.com\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: stable \u003cstable@vger.kernel.org\u003e #3.10+\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 330a1617b0a6268d427aa5922c94d082b1d3e96d)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I5a94dffc3e9ff22658d6fae612efc7eeb003338a\nReviewed-on: https://chromium-review.googlesource.com/300768\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "6ddb4ae993085f7c23eb70dda9fb572529a893e9", "tree": "2ca131821e142120881b5ec3cfbd5c5ee49b9b05", "parents": [ "3d9bd9ebed5ff323fdf1e3873af8ea78b26b8d26" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Wed Dec 11 20:07:49 2013 -0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:47 2015 -0700" }, "message": "UPSTREAM: timekeeping: Fix potential lost pv notification of time change\n\nIn 780427f0e11 (Indicate that clock was set in the pvclock\ngtod notifier), logic was added to pass a CLOCK_WAS_SET\nnotification to the pvclock notifier chain.\n\nWhile that patch added a action flag returned from\naccumulate_nsecs_to_secs(), it only uses the returned value\nin one location, and not in the logarithmic accumulation.\n\nThis means if a leap second triggered during the logarithmic\naccumulation (which is most likely where it would happen),\nthe notification that the clock was set would not make it to\nthe pv notifiers.\n\nThis patch extends the logarithmic_accumulation pass down\nthat action flag so proper notification will occur.\n\nThis patch also changes the varialbe action -\u003e clock_set\nper Ingo\u0027s suggestion.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Sasha Levin \u003csasha.levin@oracle.com\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: David Vrabel \u003cdavid.vrabel@citrix.com\u003e\nCc: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: \u003cxen-devel@lists.xen.org\u003e\nCc: stable \u003cstable@vger.kernel.org\u003e #3.11+\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 5258d3f25c76f6ab86e9333abf97a55a877d3870)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: If36e6d46560e13d54bc6d126aecf561fe624b853\nReviewed-on: https://chromium-review.googlesource.com/300767\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "3d9bd9ebed5ff323fdf1e3873af8ea78b26b8d26", "tree": "7302fcf07f56115adae66a447ca18ea4e0dd36b8", "parents": [ "96a49a9103b5497082df7661684404cd7c88dc38" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Wed Dec 11 18:50:25 2013 -0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:45 2015 -0700" }, "message": "UPSTREAM: timekeeping: Fix lost updates to tai adjustment\n\nSince 48cdc135d4840 (Implement a shadow timekeeper), we have to\ncall timekeeping_update() after any adjustment to the timekeeping\nstructure in order to make sure that any adjustments to the structure\npersist.\n\nUnfortunately, the updates to the tai offset via adjtimex do not\ntrigger this update, causing adjustments to the tai offset to be\nmade and then over-written by the previous value at the next\nupdate_wall_time() call.\n\nThis patch resovles the issue by calling timekeeping_update()\nright after setting the tai offset.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Sasha Levin \u003csasha.levin@oracle.com\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: stable \u003cstable@vger.kernel.org\u003e #3.10+\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit f55c07607a38f84b5c7e6066ee1cfe433fa5643c)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: Ifb9ff7c4111a6bf303442cade90fbeeeaace46a3\nReviewed-on: https://chromium-review.googlesource.com/300766\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "96a49a9103b5497082df7661684404cd7c88dc38", "tree": "41df86d2b031d53b392ef08e00f78699b71db8be", "parents": [ "de068a13b8a822c8e68388ad662000ec0fdda186" ], "author": { "name": "David Vrabel", "email": "david.vrabel@citrix.com", "time": "Thu Jun 27 11:35:46 2013 +0100" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:43 2015 -0700" }, "message": "UPSTREAM: timekeeping: Indicate that clock was set in the pvclock gtod notifier\n\nIf the clock was set (stepped), set the action parameter to functions\nin the pvclock gtod notifier chain to non-zero. This allows the\ncallee to only do work if the clock was stepped.\n\nThis will be used on Xen as the synchronization of the Xen wallclock\nto the control domain\u0027s (dom0) system time will be done with this\nnotifier and updating on every timer tick is unnecessary and too\nexpensive.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: David Vrabel \u003cdavid.vrabel@citrix.com\u003e\nCc: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nCc: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: \u003cxen-devel@lists.xen.org\u003e\nLink: http://lkml.kernel.org/r/1372329348-20841-4-git-send-email-david.vrabel@citrix.com\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n(cherry picked from commit 780427f0e113b4c77dfff4d258c05a902cdb0eb9)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I1a684a074ef9e1ceff587261fb45e6468f985408\nReviewed-on: https://chromium-review.googlesource.com/300765\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "de068a13b8a822c8e68388ad662000ec0fdda186", "tree": "d365416e4fbadb0546f5b6854392dc486a624456", "parents": [ "cd87e8e65a385c6c790d2ca46b9e593b133f794b" ], "author": { "name": "David Vrabel", "email": "david.vrabel@citrix.com", "time": "Thu Jun 27 11:35:45 2013 +0100" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:41 2015 -0700" }, "message": "UPSTREAM: timekeeping: Pass flags instead of multiple bools to timekeeping_update()\n\nInstead of passing multiple bools to timekeeping_updated(), define\nflags and use a single \u0027action\u0027 parameter. It is then more obvious\nwhat each timekeeping_update() call does.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: David Vrabel \u003cdavid.vrabel@citrix.com\u003e\nCc: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nCc: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: \u003cxen-devel@lists.xen.org\u003e\nLink: http://lkml.kernel.org/r/1372329348-20841-3-git-send-email-david.vrabel@citrix.com\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n(cherry picked from commit 04397fe94ad65289884b9862b6a0c722ececaadf)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I70491002c5477d54f6dd5f7b36fded884e20ba0c\nReviewed-on: https://chromium-review.googlesource.com/300764\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "cd87e8e65a385c6c790d2ca46b9e593b133f794b", "tree": "c3759762ae85c77e4939f1c97e5cfdbafb36e7bc", "parents": [ "9016f82aeacb7fcaaf2a899ab56cdcbbfe25a4ee" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Wed Sep 11 16:50:56 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:39 2015 -0700" }, "message": "UPSTREAM: timekeeping: Fix HRTICK related deadlock from ntp lock changes\n\ncommit 7bd36014460f793c19e7d6c94dab67b0afcfcb7f upstream.\n\nGerlando Falauto reported that when HRTICK is enabled, it is\npossible to trigger system deadlocks. These were hard to\nreproduce, as HRTICK has been broken in the past, but seemed\nto be connected to the timekeeping_seq lock.\n\nSince seqlock/seqcount\u0027s aren\u0027t supported w/ lockdep, I added\nsome extra spinlock based locking and triggered the following\nlockdep output:\n\n[ 15.849182] ntpd/4062 is trying to acquire lock:\n[ 15.849765] (\u0026(\u0026pool-\u003elock)-\u003erlock){..-...}, at: [\u003cffffffff810aa9b5\u003e] __queue_work+0x145/0x480\n[ 15.850051]\n[ 15.850051] but task is already holding lock:\n[ 15.850051] (timekeeper_lock){-.-.-.}, at: [\u003cffffffff810df6df\u003e] do_adjtimex+0x7f/0x100\n\n\u003csnip\u003e\n\n[ 15.850051] Chain exists of: \u0026(\u0026pool-\u003elock)-\u003erlock --\u003e \u0026p-\u003epi_lock --\u003e timekeeper_lock\n[ 15.850051] Possible unsafe locking scenario:\n[ 15.850051]\n[ 15.850051] CPU0 CPU1\n[ 15.850051] ---- ----\n[ 15.850051] lock(timekeeper_lock);\n[ 15.850051] lock(\u0026p-\u003epi_lock);\n[ 15.850051] lock(timekeeper_lock);\n[ 15.850051] lock(\u0026(\u0026pool-\u003elock)-\u003erlock);\n[ 15.850051]\n[ 15.850051] *** DEADLOCK ***\n\nThe deadlock was introduced by 06c017fdd4dc48451a (\"timekeeping:\nHold timekeepering locks in do_adjtimex and hardpps\") in 3.10\n\nThis patch avoids this deadlock, by moving the call to\nschedule_delayed_work() outside of the timekeeper lock\ncritical section.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nReported-by: Gerlando Falauto \u003cgerlando.falauto@keymile.com\u003e\nTested-by: Lin Ming \u003cminggr@gmail.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: Mathieu Desnoyers \u003cmathieu.desnoyers@efficios.com\u003e\nLink: http://lkml.kernel.org/r/1378943457-27314-1-git-send-email-john.stultz@linaro.org\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n(cherry picked from commit 63946e8616205dafe39b4d88f9fc3dc7c4fd79aa)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I374ddc1fca8fd03d76d14e8062ee8dac65c8e530\nReviewed-on: https://chromium-review.googlesource.com/300763\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "9016f82aeacb7fcaaf2a899ab56cdcbbfe25a4ee", "tree": "dd2396f506db6a00392a3709fc87f326f4cfc0fc", "parents": [ "d522e1cd5c71a0366488f923201421659a528fd8" ], "author": { "name": "Zoran Markovic", "email": "zoran.markovic@linaro.org", "time": "Fri May 17 11:24:05 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:37 2015 -0700" }, "message": "UPSTREAM: timekeeping: Correct run-time detection of persistent_clock.\n\nSince commit 31ade30692dc9680bfc95700d794818fa3f754ac, timekeeping_init()\nchecks for presence of persistent clock by attempting to read a non-zero\ntime value. This is an issue on platforms where persistent_clock (instead\nis implemented as a free-running counter (instead of an RTC) starting\nfrom zero on each boot and running during suspend. Examples are some ARM\nplatforms (e.g. PandaBoard).\n\nAn attempt to read such a clock during timekeeping_init() may return zero\nvalue and falsely declare persistent clock as missing. Additionally, in\nthe above case suspend times may be accounted twice (once from\ntimekeeping_resume() and once from rtc_resume()), resulting in a gradual\ndrift of system time.\n\nThis patch does a run-time correction of the issue by doing the same check\nduring timekeeping_suspend().\n\nA better long-term solution would have to return error when trying to read\nnon-existing clock and zero when trying to read an uninitialized clock, but\nthat would require changing all persistent_clock implementations.\n\nThis patch addresses the immediate breakage, for now.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Feng Tang \u003cfeng.tang@intel.com\u003e\nCc: stable@vger.kernel.org\nSigned-off-by: Zoran Markovic \u003czoran.markovic@linaro.org\u003e\n[jstultz: Tweaked commit message and subject]\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 0d6bd9953f739dad96d9a0de65383e479ab4e10d)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: Ib0480d086e88d954afd4612d8775042bb7f84ba3\nReviewed-on: https://chromium-review.googlesource.com/300762\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "d522e1cd5c71a0366488f923201421659a528fd8", "tree": "04cfd71e4eab0ab94b867b35bb09f642a21ee944", "parents": [ "e0aad1d22f241c38eb6f39b8c2ee3595f0f475a3" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Mon Apr 22 09:37:04 2013 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:35 2015 -0700" }, "message": "BACKPORT: timekeeping: Update tk-\u003ecycle_last in resume\n\ncommit 7ec98e15aa (timekeeping: Delay update of clock-\u003ecycle_last)\nforgot to update tk-\u003ecycle_last in the resume path. This results in a\nstale value versus clock-\u003ecycle_last and prevents resume in the worst\ncase.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nReported-by: Jiri Slaby \u003cjslaby@suse.cz\u003e\nReported-and-tested-by: Borislav Petkov \u003cbp@alien8.de\u003e\nAcked-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: Linux-pm mailing list \u003clinux-pm@lists.linux-foundation.org\u003e\nLink: http://lkml.kernel.org/r/alpine.LFD.2.02.1304211648150.21884@ionos\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n(cherry picked from commit 77c675ba18836802f6b73d2d773481d06ebc0f04)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: don\u0027t have e445cf1c4 so I adapted this for the older version of the\n function that doesn\u0027t cache the value of clock-\u003eread() in variable\n cycle_now]\nChange-Id: I71f76a4a9c3f246a7968a3ec2120198a04578935\nReviewed-on: https://chromium-review.googlesource.com/300761\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "e0aad1d22f241c38eb6f39b8c2ee3595f0f475a3", "tree": "52dbe5d9f95c10007fbfd7a4787857c6153fa24f", "parents": [ "ff0617df68a60b0175c96337602219f5622d9dcb" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Wed Apr 10 12:41:49 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:33 2015 -0700" }, "message": "UPSTREAM: timekeeping: Make sure to notify hrtimers when TAI offset changes\n\nNow that we have CLOCK_TAI timers, make sure we notify hrtimer\ncode when TAI offset is changed.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\nLink: http://lkml.kernel.org/r/1365622909-953-1-git-send-email-john.stultz@linaro.org\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n(cherry picked from commit 4e8f8b34b92b6514cc070aeb94d317cadd5071d7)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: Ie29ee57073ee1efce1d39f1e374b1736b2dab287\nReviewed-on: https://chromium-review.googlesource.com/300760\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "ff0617df68a60b0175c96337602219f5622d9dcb", "tree": "866b68756f98cc8b24b558e309cacb32824b3575", "parents": [ "ba1c922492d353d6d1fbbd867f8b9aa76e8e31b0" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu Feb 21 22:51:40 2013 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:31 2015 -0700" }, "message": "UPSTREAM: timekeeping: Shorten seq_count region\n\nShorten the seqcount write hold region to the actual update of the\ntimekeeper and the related data (e.g vsyscall).\n\nOn a contemporary x86 system this reduces the maximum latencies on\nPreempt-RT from 8us to 4us on the non-timekeeping cores.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit ca4523cda429712fc135c5db50920d90eb776a6c)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: Ia773616e9c47425466935b5af41fcbb760947aee\nReviewed-on: https://chromium-review.googlesource.com/300759\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "ba1c922492d353d6d1fbbd867f8b9aa76e8e31b0", "tree": "924f4a6e80d0f61f56c5d38fe690d16d342ee834", "parents": [ "085a0c967f3f722cb621526eb483bdb5ccdcb54f" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu Feb 21 22:51:40 2013 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:29 2015 -0700" }, "message": "UPSTREAM: timekeeping: Implement a shadow timekeeper\n\nUse the shadow timekeeper to do the update_wall_time() adjustments and\nthen copy it over to the real timekeeper.\n\nKeep the shadow timekeeper in sync when updating stuff outside of\nupdate_wall_time().\n\nThis allows us to limit the timekeeper_seq hold time to the update of\nthe real timekeeper and the vsyscall data in the next patch.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 48cdc135d4840aab8efd2fc3bacb5d7dfd94a9c8)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I037ba87fda6cab98e7acdd486cc253518052e693\nReviewed-on: https://chromium-review.googlesource.com/300758\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "085a0c967f3f722cb621526eb483bdb5ccdcb54f", "tree": "db300ae3a08dbd7ce25eead2794654f55a2b2bd9", "parents": [ "e13e3e3859f45b77a68411c12e0bdcca0454b520" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu Feb 21 22:51:39 2013 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:27 2015 -0700" }, "message": "UPSTREAM: timekeeping: Delay update of clock-\u003ecycle_last\n\nFor calculating the new timekeeper values store the new cycle_last\nvalue in the timekeeper and update the clock-\u003ecycle_last just when we\nactually update the new values.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 7ec98e15aa049b7a2ca73485f31cf4f90c34e2dd)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: Ie4a58e6c14d90da2328b872fd749e2f73ddb2c8a\nReviewed-on: https://chromium-review.googlesource.com/300757\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "e13e3e3859f45b77a68411c12e0bdcca0454b520", "tree": "4d5b7c2fb27922aff2c2b026a11b41052daf27a8", "parents": [ "6164894b7d497d506115e5c4b1b76226ade5fe5b" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu Feb 21 22:51:38 2013 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:25 2015 -0700" }, "message": "UPSTREAM: timekeeping: Store cycle_last value in timekeeper struct as well\n\nFor implementing a shadow timekeeper and a split calculation/update\nregion we need to store the cycle_last value in the timekeeper and\nupdate the value in the clocksource struct only in the update region.\n\nAdd the extra storage to the timekeeper.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 14a3b6abe98c8f53a13522610c257accef7321df)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I4603ca2760aa5ae2a101a00621c1ebc499ea8f50\nReviewed-on: https://chromium-review.googlesource.com/300756\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "6164894b7d497d506115e5c4b1b76226ade5fe5b", "tree": "138fe5f1a598463d1c021b5d554430de3dd5c60a", "parents": [ "26815f708d346fa822d4420410a6135f27ea95c3" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Fri Mar 22 14:20:03 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:23 2015 -0700" }, "message": "UPSTREAM: timekeeping: Simplify tai updating from do_adjtimex\n\nSince we are taking the timekeeping locks, just go ahead\nand update any tai change directly, rather then dropping\nthe lock and calling a function that will just take it again.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 0b5154fb9040cca94e7d9893384c0e78bfe2d296)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: Ieb4885ce44f4d381b7f208a6f3862f334df5e920\nReviewed-on: https://chromium-review.googlesource.com/300755\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "26815f708d346fa822d4420410a6135f27ea95c3", "tree": "5aeeaa28a518497c4a7de3e52c421ce792c8da45", "parents": [ "663cd0e11ce2791506f81d28de0ebea9db20ce08" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Fri Mar 22 11:37:28 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:21 2015 -0700" }, "message": "UPSTREAM: timekeeping: Hold timekeepering locks in do_adjtimex and hardpps\n\nIn moving the NTP state to be protected by the timekeeping locks,\nbe sure to acquire the timekeeping locks prior to calling\nntp functions.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 06c017fdd4dc48451a29ac37fc1db4a3f86b7f40)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I2ee60cfe2a7c15981606083b23ff557845b963d2\nReviewed-on: https://chromium-review.googlesource.com/300754\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "663cd0e11ce2791506f81d28de0ebea9db20ce08", "tree": "16b71fb55e492a28cccaf1a7c3574b31f49ba50c", "parents": [ "fa47fcda3f0b8764b959c8d9ffc3b98f9bdb2c45" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Fri Mar 22 15:04:13 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:19 2015 -0700" }, "message": "UPSTREAM: timekeeping: Move ADJ_SETOFFSET to top level do_adjtimex()\n\nSince ADJ_SETOFFSET adjusts the timekeeping state, process\nit as part of the top level do_adjtimex() function in\ntimekeeping.c.\n\nThis avoids deadlocks that could occur once we change the\nntp locking rules.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit cef90377fab488bd1f959efda178fb83250cf61d)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I43a9d63862adb100b089068123fe240f6c70829e\nReviewed-on: https://chromium-review.googlesource.com/300753\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "fa47fcda3f0b8764b959c8d9ffc3b98f9bdb2c45", "tree": "aa59556df7218b726376293f225bbda2ea91bf2e", "parents": [ "82845cb4765396ef68e8fcddb737c0ead36be588" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Fri Mar 22 12:28:15 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:17 2015 -0700" }, "message": "UPSTREAM: ntp: Rework do_adjtimex to take timespec and tai arguments\n\nIn order to change the locking rules, we need to provide\nthe timespec and tai values rather then having the ntp\nlogic acquire these values itself.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 87ace39b7168bd9d352c1c52b6f5d88eb1876cf8)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I2847af458dc24ac9fcf3d46ec3ba687da05dc69b\nReviewed-on: https://chromium-review.googlesource.com/300752\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "82845cb4765396ef68e8fcddb737c0ead36be588", "tree": "76e3c6f0c29f2ccd05fb1453a20be6a0df3eb123", "parents": [ "a1d58ea1d57ca1d80bbf0023069fd6ddccd91092" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Tue Apr 10 11:14:55 2012 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:15 2015 -0700" }, "message": "UPSTREAM: ntp: Make ntp_lock raw\n\nseconds_overflow() is called from hard interrupt context even on\nPreempt-RT. This requires the lock to be a raw_spinlock.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: John Stultz \u003cjohn.stultz@linaro.org\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\n(cherry picked from commit a6c0c943a15d0b3d6ac33760cb8f95c75f395895)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I1cd542a23dd5c4cbe05bb78f427441ef5346d836\nReviewed-on: https://chromium-review.googlesource.com/300751\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "a1d58ea1d57ca1d80bbf0023069fd6ddccd91092", "tree": "0a642b5f2e62c10402b01bbdfd1adc591889176b", "parents": [ "ada7f5c0f498d65d71449c878c1d3c0e1d09a28e" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Fri Mar 22 12:08:52 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:13 2015 -0700" }, "message": "UPSTREAM: ntp: Move timex validation to timekeeping do_adjtimex call.\n\nMove logic that does not need the ntp state to be done\nin the timekeeping do_adjtimex() call.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit e4085693f629ded8ac8c35b5cdd324d20242990b)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: If05e612c4b43920aa64715b84d90196741c3f385\nReviewed-on: https://chromium-review.googlesource.com/300750\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "ada7f5c0f498d65d71449c878c1d3c0e1d09a28e", "tree": "5b0dacce59d0be8f8827da681ac6a575aa5c7fa3", "parents": [ "c0b1bcc54b37294758b174dca6e225e79925e264" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Fri Mar 22 11:31:29 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:11 2015 -0700" }, "message": "UPSTREAM: ntp: Move do_adjtimex() and hardpps() functions to timekeeping.c\n\nIn preparation for changing the ntp locking rules, move\ndo_adjtimex and hardpps accessor functions to timekeeping.c,\nbut keep the code logic in ntp.c.\n\nThis patch also introduces a ntp_internal.h file so timekeeping\nspecific interfaces of ntp.c can be more limitedly shared with\ntimekeeping.c.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit aa6f9c595d857328e5d815e5b94c0e7cd31a6b59)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: I60910c1f4ea8cffbecb58cfe594d9b887892e651\nReviewed-on: https://chromium-review.googlesource.com/300749\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "c0b1bcc54b37294758b174dca6e225e79925e264", "tree": "be897aaa929aaad688602c464a892226f760bd81", "parents": [ "039b497c76fab0cdfcd40d3d9fac44aa4737c784" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Fri Mar 22 11:59:04 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:09 2015 -0700" }, "message": "UPSTREAM: ntp: Split out timex validation from do_adjtimex\n\nSplit out the timex validation done in do_adjtimex into a separate\nfunction. This will help simplify logic in following patches.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit ad460967a2953496ad76b1c22091ea99f21b4e86)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: Ib5ad8697cffb5f0486b6ef3b8795b028b67e3715\nReviewed-on: https://chromium-review.googlesource.com/300748\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "039b497c76fab0cdfcd40d3d9fac44aa4737c784", "tree": "46408c4a4fe436c18f4b80e6ac585d84b3276a08", "parents": [ "3ebb7e7c4a0d10d0c4432fb15df46f02df475132" ], "author": { "name": "Fengguang Wu", "email": "fengguang.wu@intel.com", "time": "Mon Mar 25 12:24:24 2013 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:07 2015 -0700" }, "message": "UPSTREAM: timekeeping: __timekeeping_set_tai_offset can be static\n\nYet again, the kbuild test robot saves the day, noting\nI left out defining __timekeeping_set_tai_offset as\nstatic. It even sent me this patch.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nReported-by: Fengguang Wu \u003cfengguang.wu@intel.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit dd5d70e869f960bde6376f4447fff59f16186cf5)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n\nChange-Id: If59339cb8702069429e8ba6b567ba0f6dc7c4453\nReviewed-on: https://chromium-review.googlesource.com/300747\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "3ebb7e7c4a0d10d0c4432fb15df46f02df475132", "tree": "b214e57305d80f1e482849cc42bfcffc904eebc7", "parents": [ "800e472295e7fa3a1580896cfca77b59ad860914" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu Feb 21 22:51:38 2013 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:05 2015 -0700" }, "message": "BACKPORT: timekeeping: Split timekeeper_lock into lock and seqcount\n\nWe want to shorten the seqcount write hold time. So split the seqlock\ninto a lock and a seqcount.\n\nOpen code the seqwrite_lock in the places which matter and drop the\nsequence counter update where it\u0027s pointless.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n[jstultz: Merge fixups from CLOCK_TAI collisions]\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 9a7a71b1d0968fc2bd602b7481cde1d4872e01ff)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: missing CLOCK_TAI stuff in 3.8]\nChange-Id: I8976692f1b517ee23065ca82543de37458205846\nReviewed-on: https://chromium-review.googlesource.com/300746\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "800e472295e7fa3a1580896cfca77b59ad860914", "tree": "dbf705720e920ed04cec896dc67cac6446f98a0c", "parents": [ "2895af51a166cc78ac95dd10bcb541b77c0c46e0" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu Feb 21 22:51:37 2013 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:03 2015 -0700" }, "message": "BACKPORT: timekeeping: Move lock out of timekeeper struct\n\nMake the lock a separate entity. Preparatory patch for shadow\ntimekeeper structure.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n[Merged with CLOCK_TAI changes]\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 7e40672d930b369c1984457233ec5557aa53bfb8)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: missing CLOCK_TAI stuff in 3.8]\nChange-Id: I6caa38374063fcb6ca4051082fd2453984321c97\nReviewed-on: https://chromium-review.googlesource.com/300745\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "2895af51a166cc78ac95dd10bcb541b77c0c46e0", "tree": "c868343c0709eec8e9fd4a251e47c66df04e67fc", "parents": [ "cb91225a70264b7df4f8d16fa8fa2566be92a62c" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu Feb 21 22:51:36 2013 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:12:01 2015 -0700" }, "message": "UPSTREAM: timekeeping: Make jiffies_lock internal\n\nNothing outside of the timekeeping core needs that lock.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit eb93e4d93093615c60cb7dd3dcb24e46bd7d62d4)\nSigned-off-by: Sonny Rao \u003csonnyrao@google.com\u003e\n\nChange-Id: I525c1b0b2b9b8793c459bb5a51ffbe6cc2846d4b\nReviewed-on: https://chromium-review.googlesource.com/300742\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "cb91225a70264b7df4f8d16fa8fa2566be92a62c", "tree": "e93ab5b690633b66402301867c2ca68999190b68", "parents": [ "89e84606431aa772cf74eff421c1722d5475bb8f" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Thu Feb 21 22:51:36 2013 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:11:59 2015 -0700" }, "message": "UPSTREAM: timekeeping: Calc stuff once\n\nCalculate the cycle interval shifted value once. No functional change,\njust makes the code more readable.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 23a9537a6999fce16f06ca61fc6cac52c8fbdc86)\nSigned-off-by: Sonny Rao \u003csonnyrao@google.com\u003e\n\nChange-Id: I538953ca62ab453c9fb475870b439cb07d9f62fc\nReviewed-on: https://chromium-review.googlesource.com/300741\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "89e84606431aa772cf74eff421c1722d5475bb8f", "tree": "2a3fa4947046d6e9d98b66c4165880d731248495", "parents": [ "be697c80c281d3d8edc7fc5f6f9b4a4244a7ab55" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Thu May 03 12:30:07 2012 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:11:57 2015 -0700" }, "message": "UPSTREAM: timekeeping: Move TAI managment into timekeeping core from ntp\n\nCurrently NTP manages the TAI offset. Since there\u0027s plans for a\nCLOCK_TAI clockid, push the TAI management into the timekeeping\ncore.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCC: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCC: Eric Dumazet \u003ceric.dumazet@gmail.com\u003e\nCC: Richard Cochran \u003crichardcochran@gmail.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit cc244ddae6d4c6902ac9d7d64023534f8c44a7eb)\nSigned-off-by: Sonny Rao \u003csonnyrao@google.com\u003e\n\nChange-Id: I956705435141c2a32accb68637f9d31d6f411072\nReviewed-on: https://chromium-review.googlesource.com/300740\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "be697c80c281d3d8edc7fc5f6f9b4a4244a7ab55", "tree": "a82637a7b3479a41bb020c4c762fc307a99ae7ac", "parents": [ "8d2435dc1d19b723b6db4b8108f1ff137fc9aaa4" ], "author": { "name": "Feng Tang", "email": "feng.tang@intel.com", "time": "Wed Jan 16 00:09:47 2013 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:11:55 2015 -0700" }, "message": "UPSTREAM: timekeeping: Add persistent_clock_exist flag\n\nIn current kernel, there are several places which need to check\nwhether there is a persistent clock for the platform. Current check\nis done by calling the read_persistent_clock() and validating its\nreturn value.\n\nSo one optimization is to do the check only once in timekeeping_init(),\nand use a flag persistent_clock_exist to record it.\n\nv2: Add a has_persistent_clock() helper function, as suggested by John.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: John Stultz \u003cjohn.stultz@linaro.org\u003e\nSigned-off-by: Feng Tang \u003cfeng.tang@intel.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 31ade30692dc9680bfc95700d794818fa3f754ac)\nSigned-off-by: Sonny Rao \u003csonnyrao@google.com\u003e\n\nChange-Id: Iea1365a1ba0ab5038f9dfe198280ba418f2441ef\nReviewed-on: https://chromium-review.googlesource.com/300598\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "8d2435dc1d19b723b6db4b8108f1ff137fc9aaa4", "tree": "ed2d7d9c1a3c11460f3b64cc446c4f7378446097", "parents": [ "1ab0d8271190d0a2f7ed5d9ab7ac5028e427c732" ], "author": { "name": "Kees Cook", "email": "keescook@chromium.org", "time": "Mon Nov 19 10:26:16 2012 -0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:11:53 2015 -0700" }, "message": "UPSTREAM: time: create __getnstimeofday for WARNless calls\n\nThe pstore RAM backend can get called during resume, and must be defensive\nagainst a suspended time source. Expose getnstimeofday logic that returns\nan error instead of a WARN. This can be detected and the timestamp can\nbe zeroed out.\n\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nReported-by: Doug Anderson \u003cdianders@chromium.org\u003e\nCc: John Stultz \u003cjohnstul@us.ibm.com\u003e\nCc: Anton Vorontsov \u003canton.vorontsov@linaro.org\u003e\nSigned-off-by: Kees Cook \u003ckeescook@chromium.org\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n(cherry picked from commit 1e817fb62cd185a2232ad4302579491805609489)\nSigned-off-by: Sonny Rao \u003csonnyrao@google.com\u003e\n\nChange-Id: Ib5d063e449a30867c528ec96d5a1761f4bca46e2\nReviewed-on: https://chromium-review.googlesource.com/300597\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\nReviewed-by: Kees Cook \u003ckeescook@chromium.org\u003e\n" }, { "commit": "1ab0d8271190d0a2f7ed5d9ab7ac5028e427c732", "tree": "a9f10479015fa1a80a38d87597c88d119b49dab7", "parents": [ "6e416f477fd0934aec97041691fe41a5b7fe4370" ], "author": { "name": "Sonny Rao", "email": "sonnyrao@chromium.org", "time": "Thu Sep 17 13:55:16 2015 -0400" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 23:11:51 2015 -0700" }, "message": "Revert \"CHROMIUM: Add CLOCK_SYSTEM_TRACE to export the trace clock to user space.\"\n\nCQ-DEPEND\u003dCL:303497\nBUG\u003dchromium:324025\nTEST\u003dbuild/boot 3.8 on link\n\nThis reverts commit 8cea67ed158537c3d6cdd8ad01c4ee73bd2dbcf7.\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: trivial, conflicted with 0c3b86472c trace: allow ftrace to be\n disabled/enabled per cpu]\nConflicts:\n\tinclude/linux/kernel.h\n\nChange-Id: Iad71fd4557de16ec4f97b8f896237d01ec8d3f94\nReviewed-on: https://chromium-review.googlesource.com/300596\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\n" }, { "commit": "6e416f477fd0934aec97041691fe41a5b7fe4370", "tree": "6a8e289ce8d2b330081a6d08299955203e9f0705", "parents": [ "95873b1a4646dd2f45c1e755ab56b78da537559d" ], "author": { "name": "Shuqian Zhao", "email": "shuqianz@chromium.org", "time": "Thu Oct 01 16:14:56 2015 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 02 03:28:40 2015 -0700" }, "message": "CHROMIUM: add subsystem:all to kernel config file to skip subsystem logic\n\nChanges from kernel repo may affect everything, so add subsystem:all to\nkernel repo to skip the subsystem logic.\n\nBUG\u003dNone\nTEST\u003dNone\n\nChange-Id: Ie8133fc29017885e126fa7cda773bfd91fad7515\nReviewed-on: https://chromium-review.googlesource.com/303742\nCommit-Ready: Shuqian Zhao \u003cshuqianz@chromium.org\u003e\nTested-by: Shuqian Zhao \u003cshuqianz@chromium.org\u003e\nReviewed-by: Aviv Keshet \u003cakeshet@chromium.org\u003e\n" }, { "commit": "95873b1a4646dd2f45c1e755ab56b78da537559d", "tree": "97315b160c2a14dfd2ec43280bc50e8a57f1412e", "parents": [ "24e65352616e8e63ce1ce6664d55d441a34c1bd3" ], "author": { "name": "Vincent Palatin", "email": "vpalatin@chromium.org", "time": "Tue Sep 29 17:21:59 2015 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Oct 01 17:00:25 2015 -0700" }, "message": "CHROMIUM: usb: Add device quirk for Logitech PTZ cameras\n\nAdd device quirk for Logitech PTZ Pro Camera and its sibling the\nConferenceCam CC3000e Camera.\nThis fixes the failed camera enumeration on some boot, particularly on\nfast Haswell Core i7 Chromeboxes.\n\nSigned-off-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\n\nBUG\u003dchromium:533608\nTEST\u003dConnect a Logitech PTZ Pro Camera to Panther i7 SKU, and do some\nreboot testing while recording the kernel logs and taking camera\npicture after each boot. Before the patch, more than 7% of the boots\n(over thousand iterations) show some enumeration (and in a few of them, the\nkernel is giving up before actually enumerating the webcam. After the\npatch, the enumeration is correct on every reboot.\n\nChange-Id: I551b2e10dc3196db1542b98fca15920a191c0f4a\nReviewed-on: https://chromium-review.googlesource.com/303172\nCommit-Ready: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nTested-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nReviewed-by: Julius Werner \u003cjwerner@chromium.org\u003e\n" }, { "commit": "24e65352616e8e63ce1ce6664d55d441a34c1bd3", "tree": "761f5e8f34d6d56d014664f18e009c6cb43e5646", "parents": [ "72de0b7d275e0d523f5a381e380175355c419be2" ], "author": { "name": "Eyal Shapira", "email": "eyal@wizery.com", "time": "Mon Sep 21 20:03:22 2015 +0300" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Oct 01 17:00:14 2015 -0700" }, "message": "CHROMIUM: iwl7000: rs: fix success ratio comparison in rs_get_best_rate\n\nsuccess_ratio is actually 128 * SR in percentage while\nIWL_MVM_RS_SR_NO_DECREASE is 85%. Fix this by using RS_PERCENT().\nThis bug caused the if branch to be always executed. This in turn\nled to always selecting a rate, following a column switch, in which\nthe expected throughput would exceed the best expected current throughput.\nIn some scenarios where the success ratio isn\u0027t \u003e85% such a rate\ncould be too aggressive leading us to avoid the new column.\nThis has the potential of causing sub optimal performance.\n\nBUG\u003dN/A\nTEST\u003ddifficult to test, code observation\n\nChange-Id: Ib5abd422e48ddff31115ae17d02b4331ab1d52a3\nReported-by: Moshe Harel \u003cmoshe.harel@intel.com\u003e\nSigned-off-by: Eyal Shapira \u003ceyalx.shapira@intel.com\u003e\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/303600\nReviewed-by: Dmitry Torokhov \u003cdtor@chromium.org\u003e\n" }, { "commit": "72de0b7d275e0d523f5a381e380175355c419be2", "tree": "85383ae40eadc75f1c4147306a246a1e5321a807", "parents": [ "72041fd0e3071a8c8bb1f97c8b2ebf95ecd74e8f" ], "author": { "name": "David Herrmann", "email": "dh.herrmann@gmail.com", "time": "Tue Jul 22 17:12:26 2014 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Oct 01 15:16:00 2015 -0700" }, "message": "BACKPORT: drm: don\u0027t de-authenticate clients on master-close\n\nIf an active DRM-Master closes its device, we deauthenticate all clients\non that master. However, if an inactive DRM-Master closes its device, we\ndo nothing. This is quite inconsistent and breaks several scenarios:\n\n 1) If this was used as security mechanism, it fails horribly if a master\n closes a device while VT switched away. Furthermore, none of the few\n drivers using -\u003emaster_*() callbacks seems to require it, anyway.\n\n 2) If you spawn weston (or any other non-UMS compositor) in background\n while another compositor is active, both will get assigned to the\n same \"drm_master\" object. If the foreground compositor now exits, all\n clients of both the foreground AND background compositor will be\n de-authenticated leading to unexpected behavior.\n\nStop this non-sense and keep clients authenticated. We don\u0027t do this when\ndropping DRM-Master (i.e., switching VTs) so don\u0027t do it on active-close\neither!\n\nBUG\u003dchromium:535334\nTEST\u003drun graphics_SanAngeles on Rambi or Squawks\n\nReviewed-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nReviewed-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: David Herrmann \u003cdh.herrmann@gmail.com\u003e\n(cherry picked from commit 3cb01a980461506f9ec4e4e1dc2dab6314236fb7)\nSigned-off-by: Dominik Behr \u003cdbehr@chromium.org\u003e\n\nConflicts:\n\tdrivers/gpu/drm/drm_fops.c\n\tinclude/drm/drmP.h\n\nChange-Id: I97b33ab56e658122050c2ef814eceafedab7eb0d\n(cherry picked from commit 7fd5f2ea2c2a0eaad5e68e081684bf90853734cd)\nSigned-off-by: Dominik Behr \u003cdbehr@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/303543\nReviewed-by: Ilja Friedel \u003cihf@chromium.org\u003e\nReviewed-by: Haixia Shi \u003chshi@chromium.org\u003e\n" }, { "commit": "72041fd0e3071a8c8bb1f97c8b2ebf95ecd74e8f", "tree": "c1c240e90402a6677c095a23f2fa55f1804f11bd", "parents": [ "4e849f3c672c065ee6ce809ca82fceaef1d0b29b" ], "author": { "name": "Haixia Shi", "email": "hshi@chromium.org", "time": "Mon Sep 28 16:17:01 2015 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Sep 29 00:09:43 2015 -0700" }, "message": "CHROMIUM: drm: i915: disable PPGTT for gen6.\n\nAccording to Intel SNB HW has an issue with dereferencing resources\ncorrectly through PPGTT space, which causes HW to read through GGTT\nwhen it wasn\u0027t supposed to.\n\nBUG\u003dchromium:521249\nTEST\u003dfollow bug report and verify that GPU hang no longer happens\nSigned-off-by: Haixia Shi \u003chshi@chromium.org\u003e\n\nChange-Id: I53bfdaa9f00fc2f047b111415514251a8b98af36\nReviewed-on: https://chromium-review.googlesource.com/302850\nCommit-Ready: Haixia Shi \u003chshi@chromium.org\u003e\nTested-by: Haixia Shi \u003chshi@chromium.org\u003e\nReviewed-by: Stéphane Marchesin \u003cmarcheu@chromium.org\u003e\nReviewed-by: Sean V Kelley \u003csean.v.kelley@intel.com\u003e\n" }, { "commit": "4e849f3c672c065ee6ce809ca82fceaef1d0b29b", "tree": "0ba37e5542faeaaf7043dcc63cd5af686f9f6a3c", "parents": [ "994949a554239f76d07c38898a3e3a7cd592779a" ], "author": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Wed Sep 23 14:32:34 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 25 07:44:36 2015 -0700" }, "message": "CHROMIUM: iwl7000: mac80211: improve __rate_control_send_low warning\n\nIf there are no supported rates in the rate mask with the required\nflags, we warn, but it\u0027s not clear which part causes the warning.\n\nAdd the relevant data to the warning to understand why it happens.\n\nBUG\u003dchrome-os-partner:44539\nTEST\u003dN/A, debug patch\n\nChange-Id: Ibdff2007da55051047767fbb27dd019a7af2a17f\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/301911\nReviewed-by: Dmitry Torokhov \u003cdtor@chromium.org\u003e\n" }, { "commit": "994949a554239f76d07c38898a3e3a7cd592779a", "tree": "f745f4eef469b20332346c2e229b9a7402782746", "parents": [ "03a23b9bb738b392b7f87c5f1650532838f83c69" ], "author": { "name": "Aniket Nagarnaik", "email": "aniketn@marvell.com", "time": "Sun Sep 13 22:13:13 2015 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Sep 24 00:40:57 2015 -0700" }, "message": "CHROMIUM: mwifiex: fix NULL pointer dereference during hidden SSID scan\n\nThis NULL pointer dereference is observed during suspend resume\nstress test. All pending commands are cancelled when system goes\ninto suspend state. There a corner case in which host may receive\nresponse for last scan command after this and try to trigger extra\nactive scan for hidden SSIDs.\n\nThe issue is fixed by adding a NULL check to skip that extra scan.\n\nFixes: 2375fa2b36feaf34 (mwifiex: fix unable to connect hidden SSID..)\nSigned-off-by: Aniket Nagarnaik \u003caniketn@marvell.com\u003e\nSigned-off-by: Amitkumar Karwar \u003cakarwar@marvell.com\u003e\n\nBUG\u003dchrome-os-partner:45042\nTEST\u003dWe could recreate the crash after 100-150 iterations of suspend\nstress test on Lucas2. Test successfully completed 10000 iterations\nafter this fix\n\nChange-Id: I3030c665250eef5307d2dee596eb959ba6292bc8\nSigned-off-by: Amitkumar Karwar \u003cakarwar@marvell.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/301491\nReviewed-by: Dmitry Torokhov \u003cdtor@chromium.org\u003e\n" }, { "commit": "03a23b9bb738b392b7f87c5f1650532838f83c69", "tree": "e83ad4ee3872f6faf7168fde1b5de7ec5b2ca852", "parents": [ "c4431a817a8e805905c243cc897515578e3676f0" ], "author": { "name": "Aniket Nagarnaik", "email": "aniketn@marvell.com", "time": "Sun Sep 13 22:13:13 2015 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Sep 24 00:40:48 2015 -0700" }, "message": "CHROMIUM: mwifiex: fix NULL pointer dereference during hidden SSID scan\n\nThis NULL pointer dereference is observed during suspend resume\nstress test. All pending commands are cancelled when system goes\ninto suspend state. There a corner case in which host may receive\nresponse for last scan command after this and try to trigger extra\nactive scan for hidden SSIDs.\n\nThe issue is fixed by adding a NULL check to skip that extra scan.\n\nFixes: 2375fa2b36feaf34 (mwifiex: fix unable to connect hidden SSID..)\nSigned-off-by: Aniket Nagarnaik \u003caniketn@marvell.com\u003e\nSigned-off-by: Amitkumar Karwar \u003cakarwar@marvell.com\u003e\n\nBUG\u003dchrome-os-partner:45042\nTEST\u003dWe could recreate the crash after 100-150 iterations of suspend\nstress test on Lucas2. Test successfully completed 10000 iterations\nafter this fix\n\nChange-Id: I3f03bf7a535beb396c9584a84e4a97d4345a2d3d\nSigned-off-by: Amitkumar Karwar \u003cakarwar@marvell.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/301222\nReviewed-by: Dmitry Torokhov \u003cdtor@chromium.org\u003e\n" }, { "commit": "c4431a817a8e805905c243cc897515578e3676f0", "tree": "f41dc7fcf375baaa75f432f05618518b2266e341", "parents": [ "5e823e74b273d1b8d89fe4af8ae7a69f0f9c9ac5" ], "author": { "name": "Andrey Ryabinin", "email": "a.ryabinin@samsung.com", "time": "Fri Aug 08 14:22:07 2014 -0700" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 23 06:24:11 2015 -0700" }, "message": "BACKPORT: lib/idr.c: fix out-of-bounds pointer dereference\n\nI\u0027m working on address sanitizer project for kernel. Recently we\nstarted experiments with stack instrumentation, to detect out-of-bounds\nread/write bugs on stack.\n\nJust after booting I\u0027ve hit out-of-bounds read on stack in idr_for_each\n(and in __idr_remove_all as well):\n\n\tstruct idr_layer **paa \u003d \u0026pa[0];\n\n\twhile (id \u003e\u003d 0 \u0026\u0026 id \u003c\u003d max) {\n\t\t...\n\t\twhile (n \u003c fls(id)) {\n\t\t\tn +\u003d IDR_BITS;\n\t\t\tp \u003d *--paa; \u003c--- here we are reading pa[-1] value.\n\t\t}\n\t}\n\nDespite the fact that after this dereference we are exiting out of loop\nand never use p, such behaviour is undefined and should be avoided.\n\nFix this by moving pointer derference to the beggining of the loop,\nright before we will use it.\n\nBUG\u003dchromium:534863\nTEST\u003dboot 3.8 on link\n\nSigned-off-by: Andrey Ryabinin \u003ca.ryabinin@samsung.com\u003e\nReviewed-by: Lai Jiangshan \u003claijs@cn.fujitsu.com\u003e\nCc: Tejun Heo \u003ctj@kernel.org\u003e\nCc: Alexey Preobrazhensky \u003cpreobr@google.com\u003e\nCc: Dmitry Vyukov \u003cdvyukov@google.com\u003e\nCc: Konstantin Khlebnikov \u003ckoct9i@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n(cherry picked from commit 93b7aca35dd7bf0c3ba7ea0542b556bcfdb28e76)\nSigned-off-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\n[SR: 3.8: non-trivial conflicts due to some missing idr patches like\n 326cf0f0 idr: fix top layer handling]\nConflicts:\n\tlib/idr.c\n\nChange-Id: Ica9026f3490c182841431da146d934d23e1eeb35\nReviewed-on: https://chromium-review.googlesource.com/301594\nCommit-Ready: Sonny Rao \u003csonnyrao@chromium.org\u003e\nTested-by: Sonny Rao \u003csonnyrao@chromium.org\u003e\nReviewed-by: Alexander Potapenko \u003cglider@chromium.org\u003e\n" }, { "commit": "5e823e74b273d1b8d89fe4af8ae7a69f0f9c9ac5", "tree": "7ef291c0a3236bb414b7090feb4a4b5f708a3208", "parents": [ "e0c1cd580cb36c7ff136d31c581fac2170b7c34e" ], "author": { "name": "Tony K Nadackal", "email": "tony.kn@samsung.com", "time": "Thu Jul 30 16:06:38 2015 +0530" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Mon Sep 21 01:14:04 2015 -0700" }, "message": "s5p-jpeg: Add support for decoding 411 subsampling format\n\nAdds support for decoding 411 subsampling format.\n\nBUG\u003dchrome-os-partner:40139\nTEST\u003dRun the jpeg test with images with 411 subsampling and\nsee decoded image generated correctly.\n\nChange-Id: Ia802cc06aa581f909e3c267090eb4a8b05378f8f\nSigned-off-by: Tony K Nadackal \u003ctony.kn@samsung.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/289751\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\n" }, { "commit": "e0c1cd580cb36c7ff136d31c581fac2170b7c34e", "tree": "bb794e313243a2d958c4ea4c9ae59e2fa580d1b6", "parents": [ "97ae59d790b10c8057bc0e0dcf95fd363e018534" ], "author": { "name": "Tony K Nadackal", "email": "tony.kn@samsung.com", "time": "Thu Jul 30 16:02:06 2015 +0530" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sun Sep 20 23:33:22 2015 -0700" }, "message": "s5p-jpeg: Correct WARN_ON statement for checking subsampling\n\nCorrects the WARN_ON statement for subsampling based on the\nJPEG Hardware version.\n\nBUG\u003dchrome-os-partner:40139\nTEST\u003dRun the jpeg test with 411 subsampling and see decoded image\nis correctly generated.\n\nChange-Id: Idc64162f64c02bf3255a34df4aa9cd5f39e54afc\nSigned-off-by: Tony K Nadackal \u003ctony.kn@samsung.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/289750\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\n" }, { "commit": "97ae59d790b10c8057bc0e0dcf95fd363e018534", "tree": "9cc896a367da299cc74064b302266fb2b8aed495", "parents": [ "285f0b35f7597877b07a785ee8ef07638778b268" ], "author": { "name": "Sakari Ailus", "email": "sakari.ailus@linux.intel.com", "time": "Fri Feb 13 09:42:37 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sat Sep 19 03:50:08 2015 -0700" }, "message": "FROMLIST: vb2: Fix dma_dir setting for dma-contig mem type\n\nThe last argument of vb2_dc_get_user_pages() is of type enum\ndma_data_direction, but the caller, vb2_dc_get_userptr() passes a value\nwhich is the result of comparison dma_dir \u003d\u003d DMA_FROM_DEVICE. This results\nin the write parameter to get_user_pages() being zero in all cases, i.e.\nthat the caller has no intent to write there.\n\nThis was broken by patch \"vb2: replace \u0027write\u0027 by \u0027dma_dir\u0027\".\n\nSigned-off-by: Sakari Ailus \u003csakari.ailus@linux.intel.com\u003e\nAcked-by: Hans Verkuil \u003chans.verkuil@cisco.com\u003e\n\n(am from https://patchwork.linuxtv.org/patch/28210)\nSigned-off-by: Pawel Osciak \u003cposciak@chromium.org\u003e\n\nBUG\u003dNone\nTEST\u003dvdatest\n\nReviewed-on: https://chromium-review.googlesource.com/250722\nReviewed-by: Tomasz Figa \u003ctfiga@chromium.org\u003e\nTested-by: Pawel Osciak \u003cposciak@chromium.org\u003e\nCommit-Queue: Pawel Osciak \u003cposciak@chromium.org\u003e\nTrybot-Ready: Pawel Osciak \u003cposciak@chromium.org\u003e\n(cherry picked from commit 85945c6644201d86aad10b28db6a01174d0cb732)\n\nBUG\u003dchromium:426383\nTEST\u003dmjpeg stand alone test with iommu\n\nChange-Id: I1642f89703e00587ac5a7e871dd20c595d36cbaf\nSigned-off-by: Heng-Ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/299597\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\n" }, { "commit": "285f0b35f7597877b07a785ee8ef07638778b268", "tree": "d656efed82ff523a11cdcc529981dbb165ce35b8", "parents": [ "8a1c7c3381d853a226728059b6cf0efc52cff7f7" ], "author": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Fri Sep 18 13:22:37 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 18 20:57:49 2015 -0700" }, "message": "CHROMIUM: iwl7000: mvm: fix D3 firmware PN programming\n\nThe code to send the RX PN data (for each TID) to the firmware\nhas a devastating bug: it overwrites the data for TID 0 with\nall the TID data, leaving the remaining TIDs zeroed. This will\nallow replays to actually be accepted by the firmware, which\ncould allow waking up the system.\n\nBUG\u003dN/A\nTEST\u003dattempt to replay wakeup packet while in suspend\n\nChange-Id: I5eb36646e89afe62007ef733cf47fd553c87eb3f\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/300645\nReviewed-by: Dmitry Torokhov \u003cdtor@chromium.org\u003e\n" }, { "commit": "8a1c7c3381d853a226728059b6cf0efc52cff7f7", "tree": "efb0b7dc64618cee4356967f14c321316250b3cd", "parents": [ "80882d1d1c734c294b6c79501a7dd646d951824a" ], "author": { "name": "Brent Adam", "email": "brentadam@smarttech.com", "time": "Fri Sep 18 10:43:44 2015 -0600" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 18 16:34:22 2015 -0700" }, "message": "BACKPORT: HID: multitouch: Fix fields from pen report ID being interpreted for\nmultitouch\n\nFields like HID_DG_CONTACTCOUNT are outside of the physical collection,\nbut within the application collection and report ID. Make sure to catch\nthose fields that are not part of the mt_report_id and return 0 so they\ncan be processed with the pen. Otherwise, the wrong HID_DG_CONTACTCOUNT\nwill be applied to cc_index and result in dereferencing a null pointer in\nmt_touch_report.\n\nbackport from git.kernel.org commit 1cc1cc92c4c4891abc48a777fb9fbc69077d5673\n\nBUG\u003dchromium:485103\nTEST\u003dBackport commit above, compiled board\u003dlink and tested.\n\nChange-Id: Ic16ce2358a37c3ae40c42f63bdf36a07dd24c013\nSigned-off-by: Brent Adam \u003cbrentadam@smarttech.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/301120\nReviewed-by: Michael Spang \u003cspang@chromium.org\u003e\n" }, { "commit": "80882d1d1c734c294b6c79501a7dd646d951824a", "tree": "ffad505d0e30789aa8b855cf5de6cc2dd849f9fe", "parents": [ "158bba0fb7dc3c49074b0d77918cda316a2f6792" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Wed Aug 19 07:20:14 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Sep 17 04:54:36 2015 -0700" }, "message": "UPSTREAM: ALSA: usb-audio: Fix runtime PM unbalance\n\nThe fix for deadlock in PM in commit [1ee23fe07ee8: ALSA: usb-audio:\nFix deadlocks at resuming] introduced a new check of in_pm flag.\nHowever, the brainless patch author evaluated it in a wrong way\n(logical AND instead of logical OR), thus usb_autopm_get_interface()\nis wrongly called at probing, leading to unbalance of runtime PM\nrefcount.\n\nThis patch fixes it by correcting the logic.\n\nReported-by: Hans Yang \u003chansy@nvidia.com\u003e\nFixes: 1ee23fe07ee8 (\u0027ALSA: usb-audio: Fix deadlocks at resuming\u0027)\nCc: \u003cstable@vger.kernel.org\u003e [v3.15+]\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\n\nBUG\u003dchrmoium:530829\nBUG\u003dchromium:520917\nTEST\u003dNone\n\nChange-Id: I1d50fc84105c2245ecc3c58eb9e8216ee243938f\nSigned-off-by: Hsin-Yu Chao \u003chychao@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/299667\nCommit-Ready: Hsinyu Chao \u003chychao@chromium.org\u003e\nTested-by: Hsinyu Chao \u003chychao@chromium.org\u003e\nReviewed-by: Cheng-Yi Chiang \u003ccychiang@chromium.org\u003e\nReviewed-by: Dylan Reid \u003cdgreid@chromium.org\u003e\n" }, { "commit": "158bba0fb7dc3c49074b0d77918cda316a2f6792", "tree": "e8748625b7d20811c88bdc9e9727a1abb4776609", "parents": [ "17085849f00ab1aa916df7408c6cea65b39892e0" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Fri May 02 18:17:06 2014 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Sep 17 04:54:34 2015 -0700" }, "message": "UPSTREAM: ALSA: usb-audio: Fix deadlocks at resuming\n\nThe recent addition of the USB audio mixer suspend/resume may lead to\ndeadlocks when the driver tries to call usb_autopm_get_interface()\nrecursively, since the function tries to sync with the finish of the\nother calls. For avoiding it, introduce a flag indicating the resume\noperation and avoids the recursive usb_autopm_get_interface() calls\nduring the resume.\n\nReported-and-tested-by: Bryan Quigley \u003cgquigs@gmail.com\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\n\nBUG\u003dchrmoium:530829\nBUG\u003dchromium:520917\nTEST\u003dNone\n\nChange-Id: If6600fdf05a9e526c27bb971625f6cc516acac93\nSigned-off-by: Hsin-Yu Chao \u003chychao@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/299666\nCommit-Ready: Hsinyu Chao \u003chychao@chromium.org\u003e\nTested-by: Hsinyu Chao \u003chychao@chromium.org\u003e\nReviewed-by: Cheng-Yi Chiang \u003ccychiang@chromium.org\u003e\nReviewed-by: Dylan Reid \u003cdgreid@chromium.org\u003e\n" }, { "commit": "17085849f00ab1aa916df7408c6cea65b39892e0", "tree": "52acee4eaf8bb3fc68f7775d4a66d42f8e6656d2", "parents": [ "6864dbe97da6212b92d6086f4a31ede2095f9693" ], "author": { "name": "Tony K Nadackal", "email": "tony.kn@samsung.com", "time": "Thu Jul 23 17:31:24 2015 +0530" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 16 05:20:47 2015 -0700" }, "message": "media: s5p-jpeg: Add logic to check for Huffman Table is present\n\nAdds logic for parsing for Huffman Table in the JPEG header.\n\nBUG\u003dchrome-os-partner:40139\nTEST\u003dRun the jpeg test with images with and without jpeg header.\nSee that the driver returns error back to userspace in case of\nmissing header.\n\nChange-Id: I593e0f76aaa8a9587b6ec21b0caf01e40d018940\nSigned-off-by: Tony K Nadackal \u003ctony.kn@samsung.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/288231\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\n" }, { "commit": "6864dbe97da6212b92d6086f4a31ede2095f9693", "tree": "26229224994f70b255b7eb285e0eed20ab072260", "parents": [ "9a3e9a45b9341af6f96298e99c7c6fe7d33a776d" ], "author": { "name": "Mark Kuo", "email": "mkuo@nvidia.com", "time": "Thu Sep 10 09:34:47 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 11 19:59:21 2015 -0700" }, "message": "CHROMIUM: Input: fix lockdep complaint\n\nIn commit 9276c17 \"CHROMIUM: input: Add \"inhibited\" property for input\ndevices\", input_inhibit() and input_uninhibit() were added without\nevent_lock spinlock protection and without interrupt disabled, when\ncalling input_dev_release_keys() which expects them.\n\ninput_dev_release_keys() will call the .events() callback in evdev.c\nwhich also expects interrupt is already disabled. Since the .events()\ncallback in evdev.c holds buffer_lock in evdev_pass_values() which may\nbe acquired in hardirq context, lockdep will complain when userspace\ntries to do \"echo 1 \u003e /sys/devices/gpio-keys/input/inputX/inhibited\"\nwhich will acquire this same buffer_lock when interrupt is still\nenabled.\n\nFix by adding spin_lock_irqsave/spin_unlock_irqrestore in both\nfunctions. This will fix the following 2 lockdep complaint:\n\n [ INFO: inconsistent lock state ]\n 3.18.0-06881-g540102b #1 Tainted: G U W\n ---------------------------------\n inconsistent {IN-HARDIRQ-W} -\u003e {HARDIRQ-ON-W} usage.\n PhotonicModulat/583 [HC0[0]:SC0[0]:HE1:SE1] takes:\n (\u0026(\u0026client-\u003ebuffer_lock)-\u003erlock){?.....}, at: [\u003cffffffc000796538\u003e] evdev_pass_values+0x70/0x190\n {IN-HARDIRQ-W} state was registered at:\n [\u003cffffffc000257ddc\u003e] mark_lock+0x2dc/0x6a8\n [\u003cffffffc000259ee0\u003e] __lock_acquire+0x8c8/0x191c\n [\u003cffffffc00025b6b8\u003e] lock_acquire+0xec/0x128\n [\u003cffffffc000a8a798\u003e] _raw_spin_lock+0x2c/0x44\n [\u003cffffffc000796534\u003e] evdev_pass_values+0x6c/0x190\n [\u003cffffffc0007968e8\u003e] evdev_events+0xb0/0xe8\n...\n irq event stamp: 35847\n hardirqs last enabled at (35847): [\u003cffffffc000278e6c\u003e] ktime_mono_to_any+0x84/0xc8\n hardirqs last disabled at (35846): [\u003cffffffc000278e28\u003e] ktime_mono_to_any+0x40/0xc8\n softirqs last enabled at (35840): [\u003cffffffc000220b78\u003e] __do_softirq+0x2b4/0x330\n softirqs last disabled at (35825): [\u003cffffffc000220e98\u003e] irq_exit+0x74/0xd0\n\n other info that might help us debug this:\n Possible unsafe locking scenario:\n\n CPU0\n ----\n lock(\u0026(\u0026client-\u003ebuffer_lock)-\u003erlock);\n \u003cInterrupt\u003e\n lock(\u0026(\u0026client-\u003ebuffer_lock)-\u003erlock);\n\n *** DEADLOCK ***\n\n Call trace:\n...\n [\u003cffffffc000a8a798\u003e] _raw_spin_lock+0x2c/0x44\n [\u003cffffffc000796534\u003e] evdev_pass_values+0x6c/0x190\n...\n [\u003cffffffc00079064c\u003e] input_dev_release_keys+0x7c/0xc4\n [\u003cffffffc000790778\u003e] input_dev_store_inhibited+0x60/0x104\n\nand\n\n [ INFO: possible irq lock inversion dependency detected ]\n 3.18.0-06881-g540102b #1 Tainted: G U W\n ---------------------------------------------------------\n kworker/0:5/2661 just changed the state of lock:\n (\u0026(\u0026dev-\u003eevent_lock)-\u003erlock){-.....}, at: [\u003cffffffc000790ee8\u003e] input_event+0x40/0x74\n but this lock took another, HARDIRQ-unsafe lock in the past:\n (\u0026(\u0026client-\u003ebuffer_lock)-\u003erlock){+.+...}\n\n and interrupts could create inverse lock ordering between them.\n\n other info that might help us debug this:\n Possible interrupt unsafe locking scenario:\n\n CPU0 CPU1\n ---- ----\n lock(\u0026(\u0026client-\u003ebuffer_lock)-\u003erlock);\n local_irq_disable();\n lock(\u0026(\u0026dev-\u003eevent_lock)-\u003erlock);\n lock(\u0026(\u0026client-\u003ebuffer_lock)-\u003erlock);\n \u003cInterrupt\u003e\n lock(\u0026(\u0026dev-\u003eevent_lock)-\u003erlock);\n\n *** DEADLOCK ***\n\n Call trace:\n...\n [\u003cffffffc000a8a7ec\u003e] _raw_spin_lock_irqsave+0x3c/0x58\n [\u003cffffffc000790ee4\u003e] input_event+0x3c/0x74\n...\n [\u003cffffffc000734e88\u003e] usb_hcd_giveback_urb+0x38/0xe4\n [\u003cffffffc000762ef0\u003e] xhci_irq+0x1080/0x1234\n\nBUG\u003dnone\nTEST\u003dtest with usb mouse and suspend/resume for few loops, no more\nlockdep warnings seen in kernel\n\nChange-Id: I97fd08d661daa55b9adc18fa5eb14d98a50984a9\nSigned-off-by: Mark Kuo \u003cmkuo@nvidia.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/297686\nReviewed-by: Dmitry Torokhov \u003cdtor@chromium.org\u003e\n(cherry picked from commit 7453d62c571745da22153b1021103b4e43fcddb4)\nReviewed-on: https://chromium-review.googlesource.com/299535\nCommit-Ready: Dmitry Torokhov \u003cdtor@chromium.org\u003e\nTested-by: Dmitry Torokhov \u003cdtor@chromium.org\u003e\nReviewed-by: Benson Leung \u003cbleung@chromium.org\u003e\n" }, { "commit": "9a3e9a45b9341af6f96298e99c7c6fe7d33a776d", "tree": "501b1f1fee81a29da8353b4d606251cf919917e0", "parents": [ "7369113e6d9f734d0f0ae4bcb5bea8e0e39214c7" ], "author": { "name": "Yao-Wen Mao", "email": "yaowen@google.com", "time": "Fri Aug 28 16:33:25 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Sep 10 05:29:42 2015 -0700" }, "message": "UPSTREAM: ALSA: usb-audio: correct the value cache check.\n\nThe check of cval-\u003ecached should be zero-based (including master channel).\n\nSigned-off-by: Yao-Wen Mao \u003cyaowen@google.com\u003e\nCc: \u003cstable@vger.kernel.org\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\n(cherry picked from commit 6aa6925cad06159dc6e25857991bbc4960821242)\nSigned-off-by: Yao-Wen Mao \u003cyaowen@google.com\u003e\n\nBUG\u003dchromium:520917\nTEST\u003dNone\n\nChange-Id: Ie094fc0661f7347cc4207b1b800369263777de9f\nReviewed-on: https://chromium-review.googlesource.com/298791\nCommit-Ready: Yao-Wen Mao \u003cyaowen@google.com\u003e\nTested-by: Yao-Wen Mao \u003cyaowen@google.com\u003e\nReviewed-by: Hsinyu Chao \u003chychao@chromium.org\u003e\n" }, { "commit": "7369113e6d9f734d0f0ae4bcb5bea8e0e39214c7", "tree": "dc847f5aedefd0df6a71c2b8280dc164bd96c94d", "parents": [ "de5758394b0ea66dc7fb3afbec88ea68dc0f5b2e" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Mon Jan 20 16:51:16 2014 +0100" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Sep 10 05:29:40 2015 -0700" }, "message": "UPSTREAM: ALSA: usb-audio: Resume mixer values properly\n\nImplement reset_resume callback so that the mixer values are properly\nrestored. Still no boot quirks are called, so it might not work well\non some devices.\n\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\n(cherry picked from commit 6a4fd914069a65143e176de24c6fca421ac77e17)\nSigned-off-by: Yao-Wen Mao \u003cyaowen@google.com\u003e\n\nBUG\u003dchromium:520917\nTEST\u003dNone\n\nChange-Id: I32006a1134f85be6744259dbeab01effc0b37dae\nReviewed-on: https://chromium-review.googlesource.com/298790\nCommit-Ready: Yao-Wen Mao \u003cyaowen@google.com\u003e\nTested-by: Yao-Wen Mao \u003cyaowen@google.com\u003e\nReviewed-by: Hsinyu Chao \u003chychao@chromium.org\u003e\n" }, { "commit": "de5758394b0ea66dc7fb3afbec88ea68dc0f5b2e", "tree": "ba1cfebefe0510828b612c17ca93f21fbe7765a3", "parents": [ "c14dce735adc736c98548796e7323679bcea4fc9" ], "author": { "name": "henryhsu", "email": "henryhsu@chromium.org", "time": "Thu Aug 20 17:57:58 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 09 22:11:47 2015 -0700" }, "message": "[media] v4l: Add pixelformat change event\n\nThis event indicates that the video device has encountered a\npixelformat change during runtime. This event can be detected by a\ndecoder or a capture device.\n\nTake decoder for example, input pixelformat change may affect\noutput format change.\nThis needs to be notified to the userspace and the application must\nbe expected to get format and reallocate buffers before proceeding.\nIf multiple events occurred before application could dequeue them,\nthen the changes will have the ORed value of all the events generated.\n\nBUG\u003dchromium:426383\nTEST\u003dbuild kernel and pass\n\nChange-Id: Idb3f74adb662a4f897fb4323ab72e162d063f76a\nSigned-off-by: Henry-Ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/294147\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Tomasz Figa \u003ctfiga@chromium.org\u003e\n" }, { "commit": "c14dce735adc736c98548796e7323679bcea4fc9", "tree": "f980b81578cc6ccaf0389b72c92ee06607000bfd", "parents": [ "557f696ccbc1989c14c3d51bf83325f1afd86c2b" ], "author": { "name": "henryhsu", "email": "henryhsu@chromium.org", "time": "Thu Aug 20 13:18:27 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 09 11:17:58 2015 -0700" }, "message": "Revert \"CHROMIUM: v4l: Add resolution change event.\"\n\nThis reverts commit c4652416d7e75df41f6170912458f9109366bc10.\n\nConflicts:\n\tinclude/uapi/linux/videodev2.h\n\nBUG\u003dchromium:409725\nTEST\u003dbuild kernel and pass\n\nChange-Id: I3d28555e3ee2cb8d5ddabcd1a90ca906831302ed\nSigned-off-by: Heng-Ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/294389\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Tomasz Figa \u003ctfiga@chromium.org\u003e\n" }, { "commit": "557f696ccbc1989c14c3d51bf83325f1afd86c2b", "tree": "2596d9d8d6f42dd6ec55e6a42e22e7698209b8d0", "parents": [ "26e84201fda017f63828e394809115815cfbe590" ], "author": { "name": "henryhsu", "email": "henryhsu@chromium.org", "time": "Wed Sep 02 10:33:00 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 09 03:00:53 2015 -0700" }, "message": "CHROMIUM: v4l: Remove go2001 PCI codec driver.\n\nWe remove it since no platform in 3.8 uses this driver.\ngo2001 is used in 3.14 kernel version.\n\nBUG\u003dchromium:409725\nTEST\u003dbuidl kernel and pass\nCQ-DEPEND\u003dCL:296903\n\nChange-Id: Ia107d5d9f8bcad176e02071a79fbc6e6c849b8d9\nSigned-off-by: Heng-Ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/296861\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Pawel Osciak \u003cposciak@chromium.org\u003e\n" }, { "commit": "26e84201fda017f63828e394809115815cfbe590", "tree": "10bac73708b2d3b4a73c2da13722ca8f9ea65054", "parents": [ "6455d1788015600e089a108aeeb345231aa6652f" ], "author": { "name": "henryhsu", "email": "henryhsu@chromium.org", "time": "Tue Sep 08 13:53:13 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 09 01:06:54 2015 -0700" }, "message": "CHROMIUM: config: remove GO2001 and normalize configs.\n\nRemove GO2001 since no platform in 3.8 use this.\n\nBUG\u003dchromium:409725\nTEST\u003dbuild kernel and pass\n\nChange-Id: I7f36e6419e55980d85ab5d52e09071a472485f64\nSigned-off-by: Heng-Ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/296903\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Pawel Osciak \u003cposciak@chromium.org\u003e\n" }, { "commit": "6455d1788015600e089a108aeeb345231aa6652f", "tree": "53176ae7ad499ae425c8dbf93e9177df45678a40", "parents": [ "e485b1686bab6cde34f48e9860745e7583d900e4" ], "author": { "name": "Andrei Otcheretianski", "email": "andrei.otcheretianski@intel.com", "time": "Wed Aug 05 14:52:58 2015 +0300" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Sep 08 13:49:20 2015 -0700" }, "message": "CHROMIUM: iwl7000: mac80211: process skb_queue while scanning in HW\n\nQueued frames aren\u0027t processed during scan, which results in an inability\nto complete the BA session establishment until the scan ends. Since we\ncan\u0027t tx frames until the BA agreement setup is complete, it might result\nin a very large latency during scan.\nFix this by allowing to process queued skbs while scanning in HW. This\nshould be ok since the devices which support hw scan should be able\nto handle tx/rx while scanning.\nDuring SW scan, mac80211 drops any txed frames besides probes and NDPs,\nso it is still needed to delay processing of the queued frames till the\nSW scan is done.\n\nBUG\u003dchrome-os-partner:37530\nTEST\u003dnetwork_WiFi_OverlappingBSSScan\n\nChange-Id: Icce3b9584b806cd33b3471d09dac3d2da9619c73\nSigned-off-by: Andrei Otcheretianski \u003candrei.otcheretianski@intel.com\u003e\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/297486\nReviewed-by: Dmitry Torokhov \u003cdtor@chromium.org\u003e\n" }, { "commit": "e485b1686bab6cde34f48e9860745e7583d900e4", "tree": "fb7611c737793c938629483e4ad6a0a4e02147ab", "parents": [ "32612bfabe2e6e0eaa3f50cbea7f6c1bb1e7b773" ], "author": { "name": "Jakub Pawlowski", "email": "jpawlowski@google.com", "time": "Fri Aug 07 20:22:56 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 04 20:18:47 2015 -0700" }, "message": "UPSTREAM: Bluetooth: Enable new connection establishment procedure.\n\nCurrently, when trying to connect to already paired device that just\nrotated its RPA MAC address, old address would be used and connection\nwould fail. In order to fix that, kernel must scan and receive\nadvertisement with fresh RPA before connecting.\n\nThis patch enables new connection establishment procedure. Instead of just\nsending HCI_OP_LE_CREATE_CONN to controller, \"connect\" will add device to\nkernel whitelist and start scan. If advertisement is received, it\u0027ll be\ncompared against whitelist and then trigger connection if it matches.\nThat fixes mentioned reconnect issue for already paired devices. It also\nmake whole connection procedure more robust. We can try to connect to\nmultiple devices at same time now, even though controller allow only one.\n\nBUG\u003dchromium:495402\nTEST\u003d\u0027connect \u003cMAC_ADDR\u003e\u0027 in bluetoothctl console\n\n(cherry-picked from commit fa1422207756833096b54356a539e3a7d7edec4f from\nrepo git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git)\n\nChange-Id: I9fde9e43a696d1f598c83df3a98d458cc700d9f2\nSigned-off-by: Jakub Pawlowski \u003cjpawlowski@google.com\u003e\nSigned-off-by: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/292731\nCommit-Ready: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nTested-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nReviewed-by: Arman Uguray \u003carmansito@chromium.org\u003e\nReviewed-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\n" }, { "commit": "32612bfabe2e6e0eaa3f50cbea7f6c1bb1e7b773", "tree": "7918085857c279890dbd365b87ae6d869252f70b", "parents": [ "d2f021de9d7d5ed7058be9aae3e45f37373fef64" ], "author": { "name": "Jakub Pawlowski", "email": "jpawlowski@google.com", "time": "Fri Aug 07 20:22:55 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 04 20:18:45 2015 -0700" }, "message": "UPSTREAM: Bluetooth: timeout handling in new connect procedure\n\nCurrently, when trying to connect to already paired device that just\nrotated its RPA MAC address, old address would be used and connection\nwould fail. In order to fix that, kernel must scan and receive\nadvertisement with fresh RPA before connecting.\n\nThis patch makes sure that when new procedure is in use, and we\u0027re stuck\nin scan phase because no advertisement was received and timeout happened,\nor app decided to close socket, scan whitelist gets properly cleaned up.\n\nBUG\u003dchromium:495402\nTEST\u003d\u0027connect \u003cMAC_ADDR\u003e\u0027 in bluetoothctl console\n\n(cherry-picked from commit cc2b6911a205b327b29c1d771925f8ab2f80295f from\nrepo git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git)\n\nChange-Id: I5c7881d40d07243f660519a196797a081bbf07b4\nSigned-off-by: Jakub Pawlowski \u003cjpawlowski@google.com\u003e\nSigned-off-by: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/292730\nCommit-Ready: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nTested-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nReviewed-by: Arman Uguray \u003carmansito@chromium.org\u003e\nReviewed-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\n" }, { "commit": "d2f021de9d7d5ed7058be9aae3e45f37373fef64", "tree": "ad63337679d7711086bca0470606dbc4c7a3f33e", "parents": [ "051e73fab98d82cfe4de2d2fb5fce5193270a2ba" ], "author": { "name": "Jakub Pawlowski", "email": "jpawlowski@google.com", "time": "Fri Aug 07 20:22:54 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 04 20:18:43 2015 -0700" }, "message": "UPSTREAM: Bluetooth: advertisement handling in new connect procedure\n\nCurrently, when trying to connect to already paired device that just\nrotated its RPA MAC address, old address would be used and connection\nwould fail. In order to fix that, kernel must scan and receive\nadvertisement with fresh RPA before connecting.\n\nThis path makes sure that after advertisement is received from device that\nwe try to connect to, it is properly handled in check_pending_le_conn and\ntrigger connect attempt.\n\nIt also modifies hci_le_connect to make sure that connect attempt will be\nproperly continued.\n\nBUG\u003dchromium:495402\nTEST\u003d\u0027connect \u003cMAC_ADDR\u003e\u0027 in bluetoothctl console\n\n(cherry-picked from commit 28a667c9c279df5a6467842ee2b3b73ddf874732 from\nrepo git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git)\n\nChange-Id: I3553250584157d27f441c8aadf618c010a37b24b\nSigned-off-by: Jakub Pawlowski \u003cjpawlowski@google.com\u003e\nSigned-off-by: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/292479\nCommit-Ready: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nTested-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nReviewed-by: Arman Uguray \u003carmansito@chromium.org\u003e\nReviewed-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\n" }, { "commit": "051e73fab98d82cfe4de2d2fb5fce5193270a2ba", "tree": "71488b7c5fc8f39442f6706af41778a4113114cb", "parents": [ "a460fc061249ba28b1d6586bd83de5d20269939d" ], "author": { "name": "Jakub Pawlowski", "email": "jpawlowski@google.com", "time": "Fri Aug 07 20:22:53 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 04 20:18:41 2015 -0700" }, "message": "UPSTREAM: Bluetooth: add hci_connect_le_scan\n\nCurrently, when trying to connect to already paired device that just\nrotated its RPA MAC address, old address would be used and connection\nwould fail. In order to fix that, kernel must scan and receive\nadvertisement with fresh RPA before connecting.\n\nThis patch adds hci_connect_le_scan with dependencies, new method that\nwill be used to connect to remote LE devices. Instead of just sending\nconnect request, it adds a device to whitelist. Later patches will make\nuse of this whitelist to send conenct request when advertisement is\nreceived, and properly handle timeouts.\n\nBUG\u003dchromium:495402\nTEST\u003d\u0027connect \u003cMAC_ADDR\u003e\u0027 in bluetoothctl console\n\n(cherry-picked from commit f75113a26008980ca13834fb6573145523596776 from\nrepo git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git)\n\nChange-Id: I862c04cd7698b93b55e36d9094d5e5df3787850f\nSigned-off-by: Jakub Pawlowski \u003cjpawlowski@google.com\u003e\nSigned-off-by: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/292478\nCommit-Ready: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nTested-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nReviewed-by: Arman Uguray \u003carmansito@chromium.org\u003e\nReviewed-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\n" }, { "commit": "a460fc061249ba28b1d6586bd83de5d20269939d", "tree": "4b21fc8aed15b9d5693c7829d2257d257fa1185b", "parents": [ "95c04558fbe9920f8640523881f8f0c33dc74b93" ], "author": { "name": "Jakub Pawlowski", "email": "jpawlowski@google.com", "time": "Fri Aug 07 20:22:52 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 04 20:18:39 2015 -0700" }, "message": "UPSTREAM: Bluetooth: add hci_lookup_le_connect\n\nThis patch adds hci_lookup_le_connect method, that will be used to check\nwether outgoing le connection attempt is in progress.\n\nBUG\u003dchromium:495402\nTEST\u003d\u0027connect \u003cMAC_ADDR\u003e\u0027 in bluetoothctl console\n\n(cherry-picked from commit e7d9ab731ac7babaf2e1b7b5e2280f5f555d263f from\nrepo git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git)\n\nChange-Id: Ibe6a9f6fe03c20057c146d0657187d0465ed103c\nSigned-off-by: Jakub Pawlowski \u003cjpawlowski@google.com\u003e\nSigned-off-by: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/292477\nCommit-Ready: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nTested-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nReviewed-by: Arman Uguray \u003carmansito@chromium.org\u003e\nReviewed-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\n" }, { "commit": "95c04558fbe9920f8640523881f8f0c33dc74b93", "tree": "09ff3ee7bf92e6f5566c3e1c56a6c905b0ed2e23", "parents": [ "7636215676f6c9315d1c59c687386362c4f28307" ], "author": { "name": "Jakub Pawlowski", "email": "jpawlowski@google.com", "time": "Fri Aug 07 20:22:51 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 04 20:18:37 2015 -0700" }, "message": "UPSTREAM: Bluetooth: preparation for new connect procedure\n\nCurrently, when trying to connect to already paired device that just\nrotated its RPA MAC address, old address would be used and connection\nwould fail. In order to fix that, kernel must scan and receive\nadvertisement with fresh RPA before connecting.\n\nThis patch adds some fields to hci_conn_params, in preparation to new\nconnect procedure.\n\nexplicit_connect will be used to override any current auto_connect action,\nand connect to device when ad is received.\n\nHCI_AUTO_CONN_EXPLICIT was added to auto_connect enum. When this value\nwill be used, explicit connect is the only action, and params can be\nremoved after successful connection.\n\nHCI_CONN_SCANNING is added to hci_conn flags. When it\u0027s set, connect is\nscan phase. It gets cleared when advertisement is received, and\nHCI_OP_LE_CREATE_CONN is sent.\n\nBUG\u003dchromium:495402\nTEST\u003d\u0027connect \u003cMAC_ADDR\u003e\u0027 in bluetoothctl console\n\n(cherry-picked from commit 158e92185075184ebc5f25bab61fdd598693e28d from\nrepo git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git)\n\nChange-Id: I16f9585961aaa1ec299ecb326100782b1e03a8b9\nSigned-off-by: Jakub Pawlowski \u003cjpawlowski@google.com\u003e\nSigned-off-by: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/292476\nCommit-Ready: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nTested-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nReviewed-by: Arman Uguray \u003carmansito@chromium.org\u003e\nReviewed-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\n" }, { "commit": "7636215676f6c9315d1c59c687386362c4f28307", "tree": "256254e21619cb8748f64e338ae108a46f0bb273", "parents": [ "abef641a64da7fc181caf07cc417a02bfefe55c0" ], "author": { "name": "Jakub Pawlowski", "email": "jpawlowski@google.com", "time": "Mon Jul 20 13:12:49 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 04 20:18:35 2015 -0700" }, "message": "UPSTREAM: Bluetooth: Move IRK checking logic in preparation to new connect method\n\nMove IRK checking logic in preparation to new connect method. Also\nmake sure that MGMT_STATUS_INVALID_PARAMS is returned when non\nidentity address is passed to ADD_DEVICE. Right now MGMT_STATUS_FAILED\nis returned, which might be misleading.\n\nBUG\u003dchromium:495402\nTEST\u003d\u0027connect \u003cMAC_ADDR\u003e\u0027 in bluetoothctl console\n\n(cherry-picked from commit 9a0a8a8e852dabeda848baafac19627cb469d5e9 from\nrepo git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git)\n\nChange-Id: I32ba8469350475b2045c2be177e3941d5dccaec4\nSigned-off-by: Jakub Pawlowski \u003cjpawlowski@google.com\u003e\nSigned-off-by: Johan Hedberg \u003cjohan.hedberg@intel.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/292475\nCommit-Ready: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nTested-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\nReviewed-by: Arman Uguray \u003carmansito@chromium.org\u003e\nReviewed-by: Jakub x Jakub Pawlowski \u003cjpawlowski@chromium.org\u003e\n" }, { "commit": "abef641a64da7fc181caf07cc417a02bfefe55c0", "tree": "38a1e2fab3eb96b0895c3a8baadf04b44986803d", "parents": [ "596e8b8f986b06f7a8b9888ee2d7770c4d39102f" ], "author": { "name": "chunfan chen", "email": "jeffc@marvell.com", "time": "Wed Aug 26 14:34:16 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 02 07:01:31 2015 -0700" }, "message": "BACKPORT: mwifiex: fix unable to connect hidden SSID AP on DFS channel\n\nWe will check if any hidden SSID found in passive scan channels\nand do specific SSID active scan for those channels.\n\nSigned-off-by: chunfan chen \u003cjeffc@marvell.com\u003e\nSigned-off-by: Amitkumar Karwar \u003cakarwar@marvell.com\u003e\nSigned-off-by: Kalle Valo \u003ckvalo@codeaurora.org\u003e\n\nReviewed-on: https://chromium-review.googlesource.com/294060\nReviewed-by: Paul Stewart \u003cpstew@chromium.org\u003e\n\nBUG\u003dchrome-os-partner:40751\nTEST\u003dOn Peach-Pit, ran tests to confirm we can successfully connect\nto hidden AP on DFS/passive channels. No regressions seen\nfor auto tests.\n\nChange-Id: I83026b3fab84c43b69bb260dcf6cf76dd0b8f46f\nSigned-off-by: Amitkumar Karwar \u003cakarwar@marvell.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/296466\nReviewed-by: Paul Stewart \u003cpstew@chromium.org\u003e\n" }, { "commit": "596e8b8f986b06f7a8b9888ee2d7770c4d39102f", "tree": "00dbda8cac17b243e427fd89caee0faa8032dcd6", "parents": [ "f2cd3291044db4fd2ccb7bcec5dd43d91e61f8ad" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Fri Aug 28 20:03:53 2015 -0400" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 02 07:01:23 2015 -0700" }, "message": "CHROMIUM: config: enable fhandle syscall\n\nNewer versions of udev require this. It has very little overhead:\n - CONFIG_FHANDLE is used to build fs/fhandle.c\n - it enables CONFIG_EXPORTFS\n - CONFIG_EXPORTFS is used to build fs/exportfs/expfs.c\nIn total, it adds \u003c4KB .text and \u003c1KB .data on an x86_64 build.\n\nSecurity wise, it exposes two new syscalls:\n - name_to_handle_at\n - open_by_handle_at\n\nBUG\u003dchromium:455336\nTEST\u003dprecq passes\n\nChange-Id: I48735b797d2e5aecf60b03cc6cf04b82e37f1e70\nSigned-off-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/296100\nReviewed-by: Olof Johansson \u003colofj@chromium.org\u003e\nReviewed-by: Kees Cook \u003ckeescook@chromium.org\u003e\n" }, { "commit": "f2cd3291044db4fd2ccb7bcec5dd43d91e61f8ad", "tree": "a9e3b14f806a473dc7824a2c19fbc509da2cbe17", "parents": [ "bf3bf24b3e27390bb299143087d6ac8fa68dd20e" ], "author": { "name": "Adam Goode", "email": "agoode@chromium.org", "time": "Tue Sep 01 00:37:23 2015 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 02 07:01:14 2015 -0700" }, "message": "Revert \"UPSTREAM: ALSA: seq: Use atomic ops for autoload refcount\"\n\nThis reverts commit 5b5d27f04e378890cc7c188d8a03416d5aec5200.\n\nBUG\u003dchromium:499817\n\nChange-Id: I3cbbe4db8d605110aa62084a9c6f2a4855bbe701\nReviewed-on: https://chromium-review.googlesource.com/296601\nCommit-Ready: Adam Goode \u003cagoode@chromium.org\u003e\nTested-by: Adam Goode \u003cagoode@chromium.org\u003e\nReviewed-by: Dylan Reid \u003cdgreid@chromium.org\u003e\n" }, { "commit": "bf3bf24b3e27390bb299143087d6ac8fa68dd20e", "tree": "9310ee62b5f8f6e76d9dbbe3ba7a535ed30f0fc0", "parents": [ "e3cb8e57d0f547fa0ceba778180867320ebede9a" ], "author": { "name": "Adam Goode", "email": "agoode@chromium.org", "time": "Tue Sep 01 00:37:18 2015 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Sep 01 16:10:46 2015 -0700" }, "message": "Revert \"UPSTREAM: ALSA: seq: bind seq driver automatically\"\n\nThis reverts commit d2bed66bdaafd05d1db475370d2e94e6ade3a23c.\n\nBUG\u003dchromium:499817\n\nChange-Id: I04bfe1cb98ecead617dc6c09e9c4bbab778b69a2\nReviewed-on: https://chromium-review.googlesource.com/296584\nCommit-Ready: Adam Goode \u003cagoode@chromium.org\u003e\nTested-by: Adam Goode \u003cagoode@chromium.org\u003e\nReviewed-by: Dylan Reid \u003cdgreid@chromium.org\u003e\n" }, { "commit": "e3cb8e57d0f547fa0ceba778180867320ebede9a", "tree": "0ab68a570a0c3b46625abb88bb22761fef4d11b5", "parents": [ "2efc2bec1d309ceed959b7191532783a97d6ad6b" ], "author": { "name": "Adam Goode", "email": "agoode@chromium.org", "time": "Tue Sep 01 00:37:03 2015 +0000" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Sep 01 10:54:34 2015 -0700" }, "message": "Revert \"UPSTREAM: Subject: ALSA: seq: Remove autoload locks in driver registration\"\n\nThis reverts commit 61d4dc150714cdfda0aa7c930f09751dbbc362a1.\n\nBUG\u003dchromium:499817\n\nChange-Id: Ifebc987471a51b9ce5dbbddf19dae1e61dab396d\nReviewed-on: https://chromium-review.googlesource.com/296591\nCommit-Ready: Adam Goode \u003cagoode@chromium.org\u003e\nTested-by: Adam Goode \u003cagoode@chromium.org\u003e\nReviewed-by: Dylan Reid \u003cdgreid@chromium.org\u003e\n" }, { "commit": "2efc2bec1d309ceed959b7191532783a97d6ad6b", "tree": "665ea9a0d2419479b6e872b63a8877978e9750cf", "parents": [ "9c69f60863b24cdd236ca5cd3d27fe4d0116331e" ], "author": { "name": "henryhsu", "email": "henryhsu@chromium.org", "time": "Tue Aug 18 16:20:34 2015 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Sep 01 05:06:48 2015 -0700" }, "message": "[media] s5p-mfc: Add support for resolution change event\n\nThis commit reverted two commits and add support for resolution change\nevent for new definition from upstream.\n\nWhen a resolution change point is reached, queue an event to signal the\nuserspace that a new set of buffers is required before decoding can\ncontinue.\n\nRevert \"CHROMIUM: [media] s5p-mfc: Send event after resolution change is processed\"\nThis reverts commit f95e1b0aaa092ced021605ff1f27bc56f5bb56b7.\n\nRevert \"CHROMIUM: s5p-mfc: add support for resolution change event\"\nThis reverts commit 7a18d9c61e617e09f3c6b8a6688d20042667ba1a.\n\nBUG\u003dchromium:409725\nTEST\u003dbuild kernel and pass onm peach_pi board. Play video with\nresolution change and make sure events are posted from driver.\n\nChange-Id: Ib50c978ba5c60da5ed128c8a8a3d9fba4437d1b8\nSigned-off-by: Heng-Ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/294212\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Tomasz Figa \u003ctfiga@chromium.org\u003e\n" }, { "commit": "9c69f60863b24cdd236ca5cd3d27fe4d0116331e", "tree": "a33b74a9ba12ac4933da6cc56d57b48ef017991a", "parents": [ "06003ccdd79f8644072087afa2fcd4623a487d5c" ], "author": { "name": "Arun Kumar K", "email": "arun.kk@samsung.com", "time": "Wed May 14 03:59:42 2014 -0300" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Sep 01 05:06:47 2015 -0700" }, "message": "BACKPORT: [media] v4l: Add source change event\n\nThis event indicates that the video device has encountered\na source parameter change during runtime. This can typically be a\nresolution change detected by a video decoder OR a format change\ndetected by an input connector.\n\nThis needs to be nofified to the userspace and the application may\nbe expected to reallocate buffers before proceeding. The application\ncan subscribe to events on a specific pad or input port which\nit is interested in.\n\nSigned-off-by: Arun Kumar K \u003carun.kk@samsung.com\u003e\nAcked-by: Sylwester Nawrocki \u003cs.nawrocki@samsung.com\u003e\nSigned-off-by: Hans Verkuil \u003chans.verkuil@cisco.com\u003e\nSigned-off-by: Mauro Carvalho Chehab \u003cm.chehab@samsung.com\u003e\n(cherry picked from commit 3cbe6e5bcad0b102c06b9c6029fda75630045475)\n\nConflicts:\n\tdrivers/media/v4l2-core/v4l2-event.c\n\tinclude/media/v4l2-event.h\n\nBUG\u003dchromium:409725\nTEST\u003dbuild kernel and pass\n\nChange-Id: I958a9b65de96af89bacef32dd7d49afb9307ce58\nSigned-off-by: Heng-Ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/294039\nCommit-Ready: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nTested-by: Heng-ruey Hsu \u003chenryhsu@chromium.org\u003e\nReviewed-by: Tomasz Figa \u003ctfiga@chromium.org\u003e\n" }, { "commit": "06003ccdd79f8644072087afa2fcd4623a487d5c", "tree": "a0adb6a72d4e6ed7369a02680e7cb3c56a68bb4b", "parents": [ "83aaa7945e68e95c1952845b2965511d0520549d" ], "author": { "name": "Emmanuel Grumbach", "email": "emmanuel.grumbach@intel.com", "time": "Fri Aug 28 11:19:50 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Mon Aug 31 03:43:02 2015 -0700" }, "message": "UPSTREAM: mac80211: fix BIT position for TDLS WIDE extended cap\n\nThe bit was not according to ieee80211 specification.\nFix that.\n\nBUG\u003dN/A\nTEST\u003dN/A\n\nChange-Id: Ic43d0a507e81fce49d2186aa479ff1f7ea661617\nReviewed-by: Arik Nemtsov \u003carik@wizery.com\u003e\nSigned-off-by: Emmanuel Grumbach \u003cemmanuel.grumbach@intel.com\u003e\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/294724\nReviewed-by: Sameer Nanda \u003csnanda@chromium.org\u003e\n" }, { "commit": "83aaa7945e68e95c1952845b2965511d0520549d", "tree": "1aec5b6fae909215aaee7fbb382bc3469213d8d4", "parents": [ "b7b8db5a2fe17580bd222ee26eb9ad9adbc8e951" ], "author": { "name": "Ørjan Eide", "email": "orjan.eide@arm.com", "time": "Wed Jul 22 14:19:39 2015 +0200" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sat Aug 29 17:25:01 2015 -0700" }, "message": "MALI: Wk26_2015 r6p0-02rel0 TX011 DDK\n\nEAC release of the r6p0-02rel0 version of this part:\nTX011-SW-99002\n\nThe chromebook platform files have been updated to be compatible with\nthe r6p0.\n\nBUG\u003dchrome-os-partner:41911\nTEST\u003dBoot Daisy to UI\nTEST\u003dGeneral browsing. Run Aquarium.\nTEST\u003dRun graphics_GLBench\n\nChange-Id: I9de89d2e767119802f8e809d4197b1d9f126490c\nReviewed-on: https://chromium-review.googlesource.com/289171\nCommit-Ready: Stéphane Marchesin \u003cmarcheu@chromium.org\u003e\nTested-by: Stéphane Marchesin \u003cmarcheu@chromium.org\u003e\nReviewed-by: Stéphane Marchesin \u003cmarcheu@chromium.org\u003e\n" }, { "commit": "b7b8db5a2fe17580bd222ee26eb9ad9adbc8e951", "tree": "167f7bc7f4a5100a574c744fb696dd1f8e5ba99e", "parents": [ "9010d92d991c54ed56b8e706de66483e1ac8f0e5" ], "author": { "name": "J. Richard Barnette", "email": "jrbarnette@chromium.org", "time": "Thu Aug 27 12:00:37 2015 -0700" }, "committer": { "name": "David James", "email": "davidjames@chromium.org", "time": "Thu Aug 27 20:04:34 2015 +0000" }, "message": "CHROMIUM: COMMIT-QUEUE.ini: Use wolf instead of slippy.\n\nA recent change means that we no longer have Chrome pre-builts\nfor board \u0027slippy\u0027, but COMMIT-QUEUE.ini still relied on\nslippy-pre-cq for testing. The result was that attempts to\ncommit CLs would loop forever with slippy-pre-cq failures.\n\nThis changes \u0027slippy\u0027 to \u0027wolf\u0027, which is still supported.\n\nBUG\u003dchromium:525733\nTEST\u003dRun this through the pre-cq\n\nSigned-off-by: jrbarnette@chromium.org\nChange-Id: Ieefe38c82d46bc3fdad801bb427f0af077c81273\nReviewed-on: https://chromium-review.googlesource.com/295782\n" }, { "commit": "9010d92d991c54ed56b8e706de66483e1ac8f0e5", "tree": "f9549f2729fcbd47f9c6a31c4a74ffdb708a6bd7", "parents": [ "e54564db2947a85a5ce3919f649501c107c01e45" ], "author": { "name": "Luigi Semenzato", "email": "semenzato@chromium.org", "time": "Thu Aug 20 09:16:50 2015 -0700" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Fri Aug 21 03:46:44 2015 +0000" }, "message": "CHROMIUM: tpm: set tpm_early_savestate correctly to FALSE\n\nThe default was meant to be FALSE all along.\nAlso remove selftest from the list of commands which may change the NV state.\n\nBUG\u003dchromium:519324\nTEST\u003dnone\nBRANCH\u003dnone\nSigned-off-by: Luigi Semenzato \u003csemenzato@chromium.org\u003e\n\nChange-Id: Ib911644b7b3e994ab376278e26cf0c8fcd070424\nReviewed-on: https://chromium-review.googlesource.com/294730\nReviewed-by: Sameer Nanda \u003csnanda@chromium.org\u003e\nCommit-Queue: Luigi Semenzato \u003csemenzato@chromium.org\u003e\nTested-by: Luigi Semenzato \u003csemenzato@chromium.org\u003e\n" }, { "commit": "e54564db2947a85a5ce3919f649501c107c01e45", "tree": "56bfdc1aaad8f39ad3fe5aecf3c51a7c9eef5339", "parents": [ "d370d5c1de3c6b346866c7434eef70df5e09a5d8" ], "author": { "name": "Michael Spang", "email": "spang@chromium.org", "time": "Fri Aug 14 14:13:07 2015 -0400" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Fri Aug 21 00:49:18 2015 +0000" }, "message": "CHROMIUM: config: Enable CONFIG_HIG_KENSINGTON\n\nThis makes some Kensington trackballs work on Chrome OS.\n\nBUG\u003dchromium:383944\nTEST\u003dManual on link with Kenginston trackball.\n\nChange-Id: Iba9dc2dddd3d260f40efbb756e7e4a14a09f0e58\nSigned-off-by: Michael Spang \u003cspang@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/293850\nReviewed-by: Andrew de los Reyes \u003cadlr@chromium.org\u003e\n" }, { "commit": "d370d5c1de3c6b346866c7434eef70df5e09a5d8", "tree": "b21aa4d0bdfece7510a5ec72316baa48d1d6d567", "parents": [ "6464863c707be6db82dea6a29154a234f805144c" ], "author": { "name": "chunfan chen", "email": "jeffc@marvell.com", "time": "Fri Aug 14 21:02:28 2015 +0800" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu Aug 20 19:06:10 2015 +0000" }, "message": "BACKPORT: mwifiex: fix unable to connect hidden SSID AP on DFS channel\n\nWe will check if any hidden SSID found in passive scan channels\nand do specific SSID active scan for those channels.\n\nSigned-off-by: chunfan chen \u003cjeffc@marvell.com\u003e\nSigned-off-by: Amitkumar Karwar \u003cakarwar@marvell.com\u003e\nSigned-off-by: Kalle Valo \u003ckvalo@codeaurora.org\u003e\n\nBUG\u003dchrome-os-partner:40751\nTEST\u003dOn Daisy, ran tests to confirm we can successfully connect\nto hidden AP on DFS/passive channels. No regressions seen\nfor auto tests.\n\nChange-Id: I41ab8323d84be9f963233339439d1822a0693d02\nSigned-off-by: Amitkumar Karwar \u003cakarwar@marvell.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/294060\nReviewed-by: Paul Stewart \u003cpstew@chromium.org\u003e\n" } ], "next": "6464863c707be6db82dea6a29154a234f805144c" }