{"push_id":2934748065,"size":203,"distinct_size":203,"ref":"refs/heads/test-1","head":"9949b9473fb88bee59eb0bf8104406428296a9be","before":"9b8fe9754c070b7a774fde8ac0087bf9c5e8388f","commits":[{"sha":"38bcd1dabb4bdf253d7bd0d79b9827742192762c","author":{"name":"Peter Zijlstra","email":"3fddac958924aef220f202ca567388ddab3f14a8@infradead.org"},"message":"perf: Do not double free\n\nIn case of: err_file: fput(event_file), we'll end up calling\nperf_release() which in turn will free the event.\n\nDo not then free the event _again_.\n\nChange-Id: Ic1de33d0e29e577a1fc2e00c35bf44df26d96ab6\nTested-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nReviewed-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: dvyukov@google.com\nCc: eranian@google.com\nCc: oleg@redhat.com\nCc: panand@redhat.com\nCc: sasha.levin@oracle.com\nCc: vince@deater.net\nLink: http://lkml.kernel.org/r/20160224174947.697350349@infradead.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\n[bwh: Backported to 3.2: adjust context]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/38bcd1dabb4bdf253d7bd0d79b9827742192762c"},{"sha":"b484b549a9e9e4473e51cb4dd29d77feaa1f12dc","author":{"name":"Alexander Shishkin","email":"0125b3d2989cefbb754a245b989e89659aa67db8@linux.intel.com"},"message":"perf/core: Don't leak event in the syscall error path\n\nIn the error path, event_file not being NULL is used to determine\nwhether the event itself still needs to be free'd, so fix it up to\navoid leaking.\n\nReported-by: Leon Yu <chianglungyu@gmail.com>\nSigned-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Arnaldo Carvalho de Melo <acme@kernel.org>\nCc: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Vince Weaver <vincent.weaver@maine.edu>\nFixes: 130056275ade (\"perf: Do not double free\")\nLink: http://lkml.kernel.org/r/87twk06yxp.fsf@ashishki-desk.ger.corp.intel.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/b484b549a9e9e4473e51cb4dd29d77feaa1f12dc"},{"sha":"f850a8fba817b0a46a738ac3b5a71644152ed4a8","author":{"name":"Naveen Kaje","email":"4518c7bd309b7828292441ffce16ced7cb33eedd@codeaurora.org"},"message":"msm_serial_hs: disable interrupts cleanly in shutdown\n\nClear and disable the interrupts when the port is closed\nsuch that the interrupt state and the flags are consistent\nand eliminate potential race condition.\n\nChange-Id: I25310b30e236a990460127eddb1c3b4e7ade1550\nSigned-off-by: Naveen Kaje <nkaje@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/f850a8fba817b0a46a738ac3b5a71644152ed4a8"},{"sha":"b3b44fa26d3788f03a97c07f4581acd17e93f012","author":{"name":"Girish Mahadevan","email":"84763c76b75560eea6e756c4871a8d0d2cc76116@codeaurora.org"},"message":"serial: msm_serial_hs: Change the wakeup interrupt enable sequence\n\nThe wakeup variable keeps track of the 2 edge interrupts needed to detect\nwakeup from deep sleep, when the second edge interrupt is detected the\nwake byte is injected into the tty buffer.\nOn some boards due to noisy GPIO pins an interrupt is detected as soon as\nthe wakeup irq is enabled and before the variable is reset leading to\nbogus wakeup bytes being injected into the serial buffer.\nTo protect against this, make sure the wakeup interrupt is enabled after\nall the state variables are reset to protect against spurious wakeups.\n\nChange-Id: I8002a67d8d9cb41709049ff34f35717f3dd0acd0\nAcked-by: Yijiang Yuan <yijiangy@qti.qualcomm.com>\nSigned-off-by: Girish Mahadevan <girishm@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/b3b44fa26d3788f03a97c07f4581acd17e93f012"},{"sha":"f4e360b93c763c80a0761724b6d4123c34516d29","author":{"name":"Philip Cuadra","email":"36a976435e6fca8127da3e8f55e5656a770e7945@google.com"},"message":"Make msm_serial_hs RT to improve bluetooth performance\n\nmsm_serial_hs threads for RX and TX are responsible for passing key\nbluetooth buffers, such as bluetooth audio, between the Bluetooth HW and\nthe upper layers of the stack.  These threads are therefore on the\ncritical path for bluetooth audio latency, and should be scheduled as\nRT threads in order to ensure that they meet audio deadlines.\n\nBug 36106419\n\nTest:  Play bluetooth audio, confirm msm_serial_hs_0 threads are\nscheduled as RT threads via systrace\nChange-Id: I078dbcbab189a03bdc5fdfde6ec8c41c79c11610\nSigned-off-by: Philip Cuadra <philipcuadra@google.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/f4e360b93c763c80a0761724b6d4123c34516d29"},{"sha":"fbbbfcd874e32eeed06c35e9190e448acf410fe7","author":{"name":"Yaroslav Furman","email":"313e4eef4a79219b001c4fd77cc7084a76b73a13@gmail.com"},"message":"msm_serial_hs: actually check if msm_serial_hs_tx_work failed to init\n\nJust a small typo.\n\nSigned-off-by: Yaroslav Furman <yaro330@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/fbbbfcd874e32eeed06c35e9190e448acf410fe7"},{"sha":"2a6a4361c6a71efcb4fd1ea77221a6cfbe193193","author":{"name":"Wang Han","email":"905137cc292e70962a93775555f7a11377f028ff@qq.com"},"message":"power: Introduce Oneplus 3 fingerprintd thaw hack\n\nTaken from Oneplus 3, this hack will make fingerprintd recovery\nfrom suspend quickily.","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/2a6a4361c6a71efcb4fd1ea77221a6cfbe193193"},{"sha":"5972f5a6432f687631120579040aff04c40cd23f","author":{"name":"mortezadadgar","email":"758c33313807b59ca7c04a1b06f46eec4f52c52f@gmail.com"},"message":"fpc1020: Adapt fingerprint process for oreo\n\nSigned-off-by: mortezadadgar <mortezadadgar97@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/5972f5a6432f687631120579040aff04c40cd23f"},{"sha":"b37083e68e21fda415a19f3fa732ad7630470ac4","author":{"name":"Lianwei Wang","email":"d79fadde9de82c838211e8a952123da40fe360c0@motorola.com"},"message":"proc: stat: fix idle time jump\n\nPropagate from (CR).\n\nWe saw the idle time report from /proc/stat is weird jump just\nafter cpu hotplug.\n\n  User 150 + Nice 0 + Sys 141 + Idle -44061 + IOW -1492 + IRQ 0 + SIRQ 4 = -45258\n\nThere are two reasons to cause this issue.\n\n1. All the ts history data are cleaned by below patch.\n    4b0c0f2 tick: Cleanup NOHZ per cpu data on cpu down\n\nWe don't need to clean all the ts data to fix the cpu hotplug race,\nbut just clean the inidle and tick_stopped, and keep all the other\nts data to record the history idle/iowait time data.\n\n2. The idle/iowait time is read from different place by below patch.\n    7386cdb \"nohz: Fix idle ticks in cpu summary line of /proc/stat\"\n\nThe idle/iowait time is read from get_cpu_idle/iowait_time_us when\ncpu is online, but is read from cpustat when cpu is offline. So we\nmay compare the data with different base and get wrong result.\n\nSince the off time is no longer counted as idle time, it is safe to\nrevert it now.\n\nChange-Id: Ic1f6c587e81b87a92a3c95587868e050317b1697\nSigned-off-by: Lianwei Wang <a22439@motorola.com>\nReviewed-on: http://gerrit.mot.com/727324\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nSME-Granted: SME Approvals Granted\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Igor Kovalenko <igork@motorola.com>\nSubmit-Approved: Jira Key <jirakey@motorola.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/b37083e68e21fda415a19f3fa732ad7630470ac4"},{"sha":"12cd593af47b319461176ee5259cc286318f3046","author":{"name":"Lianwei Wang","email":"d79fadde9de82c838211e8a952123da40fe360c0@motorola.com"},"message":"tick: don't update idle time if cpu offline\n\nPropagate from (CR).\n\nAn offline cpu still has ts->idle_active == 1, that cause\noff time is counted as idle time, and hence cause cpu load\ncalculated wrongly.\n\nCheck the cpu online status before updating the idle time to\nfix it.\n\nChange-Id: I8c3213105601efca037eb23ad724811b5f46d437\nSigned-off-by: Lianwei Wang <a22439@motorola.com>\nReviewed-on: http://gerrit.mot.com/727323\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nSME-Granted: SME Approvals Granted\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Igor Kovalenko <igork@motorola.com>\nSubmit-Approved: Jira Key <jirakey@motorola.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/12cd593af47b319461176ee5259cc286318f3046"},{"sha":"84ae06dc2345ffaff59331fbc719b1974abedfe3","author":{"name":"Oleg Nesterov","email":"20b70f0af00562e63758b9ee42012ecc96c58590@redhat.com"},"message":"epoll: fix race between ep_poll_callback(POLLFREE) and ep_free()/ep_remove()\n\ncommit 138e4ad67afd5c6c318b056b4d17c17f2c0ca5c0 upstream.\n\nThe race was introduced by me in commit 971316f0503a (\"epoll:\nep_unregister_pollwait() can use the freed pwq->whead\").  I did not\nrealize that nothing can protect eventpoll after ep_poll_callback() sets\n->whead = NULL, only whead->lock can save us from the race with\nep_free() or ep_remove().\n\nMove ->whead = NULL to the end of ep_poll_callback() and add the\nnecessary barriers.\n\nTODO: cleanup the ewake/EPOLLEXCLUSIVE logic, it was confusing even\nbefore this patch.\n\nHopefully this explains use-after-free reported by syzcaller:\n\n\tBUG: KASAN: use-after-free in debug_spin_lock_before\n\t...\n\t _raw_spin_lock_irqsave+0x4a/0x60 kernel/locking/spinlock.c:159\n\t ep_poll_callback+0x29f/0xff0 fs/eventpoll.c:1148\n\nthis is spin_lock(eventpoll->lock),\n\n\t...\n\tFreed by task 17774:\n\t...\n\t kfree+0xe8/0x2c0 mm/slub.c:3883\n\t ep_free+0x22c/0x2a0 fs/eventpoll.c:865\n\nFixes: 971316f0503a (\"epoll: ep_unregister_pollwait() can use the freed pwq->whead\")\nReported-by: 范龙飞 <long7573@126.com>\nSigned-off-by: Oleg Nesterov <oleg@redhat.com>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/84ae06dc2345ffaff59331fbc719b1974abedfe3"},{"sha":"4edc3956d37a922cc53fab954abf82de2f791752","author":{"name":"Eric Dumazet","email":"312c7d941f03386814be517ffdb3e0eb6624e275@google.com"},"message":"epoll: add a reschedule point in ep_free()\n\nep_free() might iterate on a huge set of epitems and hold cpu too long.\nAdd two cond_resched() in order to yield cpu to other tasks.  This is safe\nas we only hold mutexes in this function.\n\nSigned-off-by: Eric Dumazet <edumazet@google.com>\nCc: Al Viro <viro@ZenIV.linux.org.uk>\nCc: Theodore Ts'o <tytso@mit.edu>\nAcked-by: Eric Wong <normalperson@yhbt.net>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/4edc3956d37a922cc53fab954abf82de2f791752"},{"sha":"dc2dffa64d240ad1806be47d034d45e9f1654357","author":{"name":"Chris Mason","email":"e2e8c5702d8ed5f565988a1cf5bb35c9ce199e5e@fb.com"},"message":"eventfd: don't take the spinlock in eventfd_poll\n\nThe spinlock in eventfd_poll is trying to protect the count of events so\nit can decide if it should return POLLIN, POLLERR, or POLLOUT.  But,\nbecause of the way we drop the lock after calling poll_wait, and drop it\nagain before returning, we have the same pile of races with the lock as\nwe do with a single read of ctx->count().\n\nThis replaces the lock with a read barrier and single read.\n\neventfd_write does a single bump of ctx->count, so this should not add\nnew races with adding events.  eventfd_read is similar, it will do a\nsingle decrement with the lock held, and so we're making the race with\nconcurrent readers slightly larger.\n\nThis spinlock is the top CPU user in kernel code during one of our\nworkloads.  Removing it gives us a ~2% boost.\n\n[arnd@arndb.de: avoid unused variable warning]\n[dan.carpenter@oracle.com: type bug in eventfd_poll()]\nSigned-off-by: Chris Mason <clm@fb.com>\nCc: Davide Libenzi <davidel@xmailserver.org>\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/dc2dffa64d240ad1806be47d034d45e9f1654357"},{"sha":"7f30d88d227057303324f06693cb83cc5a8f0fa5","author":{"name":"Colin Cross","email":"380081620a7947c89c11153c5513f34019caa923@android.com"},"message":"epoll: use freezable blocking call\n\nAvoid waking up every thread sleeping in an epoll_wait call during\nsuspend and resume by calling a freezable blocking call.  Previous\npatches modified the freezer to avoid sending wakeups to threads\nthat are blocked in freezable blocking calls.\n\nThis call was selected to be converted to a freezable call because\nit doesn't hold any locks or release any resources when interrupted\nthat might be needed by another freezing task or a kernel driver\nduring suspend, and is a common site where idle userspace tasks are\nblocked.\n\nChange-Id: I848d08d28c89302fd42bbbdfa76489a474ab27bf\nAcked-by: Tejun Heo <tj@kernel.org>\nSigned-off-by: Colin Cross <ccross@android.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/7f30d88d227057303324f06693cb83cc5a8f0fa5"},{"sha":"39ab7017123193f9cc56d4a3145f979b0a335b92","author":{"name":"Christophe JAILLET","email":"aa5b4d6ac057e7b0849afbbced06a03fc6c87d45@wanadoo.fr"},"message":"driver core: bus: Fix a potential double free\n\ncommit 0f9b011d3321ca1079c7a46c18cb1956fbdb7bcb upstream.\n\nThe .release function of driver_ktype is 'driver_release()'.\nThis function frees the container_of this kobject.\n\nSo, this memory must not be freed explicitly in the error handling path of\n'bus_add_driver()'. Otherwise a double free will occur.\n\nSigned-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/39ab7017123193f9cc56d4a3145f979b0a335b92"},{"sha":"0ce22b2d6c6bf77a87396ae9c3e0f91c2fc3dfa9","author":{"name":"Alexander Martinz","email":"a1418a03e3f7813c1fd3f97ab13f9d68ba5a9ac2@gmail.com"},"message":"include: asm-generic: do not hard code HZ to 100\n\nUse the defconfig value instead\n\nChange-Id: I529d08cf06d64f1e3976c0cd876f40b7efefa222\nSigned-off-by: Alexander Martinz <eviscerationls@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/0ce22b2d6c6bf77a87396ae9c3e0f91c2fc3dfa9"},{"sha":"3e21405d58bd73e4609b579b54c3cb8c745dc183","author":{"name":"Richard Larocque","email":"67464b0a1b9319fe97206a991263fab600ec871e@google.com"},"message":"alarmtimer: Return relative times in timer_gettime\n\ncommit e86fea764991e00a03ff1e56409ec9cacdbda4c9 upstream.\n\nReturns the time remaining for an alarm timer, rather than the time at\nwhich it is scheduled to expire.  If the timer has already expired or it\nis not currently scheduled, the it_value's members are set to zero.\n\nThis new behavior matches that of the other posix-timers and the POSIX\nspecifications.\n\nThis is a change in user-visible behavior, and may break existing\napplications.  Hopefully, few users rely on the old incorrect behavior.\n\nChange-Id: I254c98e00b2fc54bfff596dbcfd989d4afcb6d98\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Richard Cochran <richardcochran@gmail.com>\nCc: Prarit Bhargava <prarit@redhat.com>\nCc: Sharvil Nanavati <sharvil@google.com>\nSigned-off-by: Richard Larocque <rlarocque@google.com>\n[jstultz: minor style tweak]\nSigned-off-by: John Stultz <john.stultz@linaro.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/3e21405d58bd73e4609b579b54c3cb8c745dc183"},{"sha":"5d77a3f768289ca4506c303f9067f940315f77db","author":{"name":"Thomas Gleixner","email":"00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de"},"message":"alarmtimer: Rate limit periodic intervals\n\ncommit ff86bf0c65f14346bf2440534f9ba5ac232c39a0 upstream.\n\nThe alarmtimer code has another source of potentially rearming itself too\nfast. Interval timers with a very samll interval have a similar CPU hog\neffect as the previously fixed overflow issue.\n\nThe reason is that alarmtimers do not implement the normal protection\nagainst this kind of problem which the other posix timer use:\n\n  timer expires -> queue signal -> deliver signal -> rearm timer\n\nThis scheme brings the rearming under scheduler control and prevents\npermanently firing timers which hog the CPU.\n\nBringing this scheme to the alarm timer code is a major overhaul because it\nlacks all the necessary mechanisms completely.\n\nSo for a quick fix limit the interval to one jiffie. This is not\nproblematic in practice as alarmtimers are usually backed by an RTC for\nsuspend which have 1 second resolution. It could be therefor argued that\nthe resolution of this clock should be set to 1 second in general, but\nthat's outside the scope of this fix.\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Kostya Serebryany <kcc@google.com>\nCc: syzkaller <syzkaller@googlegroups.com>\nCc: John Stultz <john.stultz@linaro.org>\nCc: Dmitry Vyukov <dvyukov@google.com>\nLink: http://lkml.kernel.org/r/20170530211655.896767100@linutronix.de\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/5d77a3f768289ca4506c303f9067f940315f77db"},{"sha":"b8680243336971509dd4b2d4f28e915fa485db92","author":{"name":"Greg Hackmann","email":"e4b32643abc22f0015f12596bd9b0c46cec422aa@google.com"},"message":"alarmtimer: don't rate limit one-shot timers\n\nCommit ff86bf0c65f1 (\"alarmtimer: Rate limit periodic intervals\") sets a\nminimum bound on the alarm timer interval.  This minimum bound shouldn't\nbe applied if the interval is 0.  Otherwise, one-shot timers will be\nconverted into periodic ones.\n\nFixes: ff86bf0c65f1 (\"alarmtimer: Rate limit periodic intervals\")\nReported-by: Ben Fennema <fennema@google.com>\nSigned-off-by: Greg Hackmann <ghackmann@google.com>\nCc: stable@vger.kernel.org\nCc: John Stultz <john.stultz@linaro.org>\nReviewed-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/b8680243336971509dd4b2d4f28e915fa485db92"},{"sha":"67003c9f8b4110d3a857a365eb248702da628b4b","author":{"name":"Thomas Gleixner","email":"00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de"},"message":"alarmtimer: Prevent overflow of relative timers\n\ncommit f4781e76f90df7aec400635d73ea4c35ee1d4765 upstream.\n\nAndrey reported a alartimer related RCU stall while fuzzing the kernel with\nsyzkaller.\n\nThe reason for this is an overflow in ktime_add() which brings the\nresulting time into negative space and causes immediate expiry of the\ntimer. The following rearm with a small interval does not bring the timer\nback into positive space due to the same issue.\n\nThis results in a permanent firing alarmtimer which hogs the CPU.\n\nUse ktime_add_safe() instead which detects the overflow and clamps the\nresult to KTIME_SEC_MAX.\n\nReported-by: Andrey Konovalov <andreyknvl@google.com>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Kostya Serebryany <kcc@google.com>\nCc: syzkaller <syzkaller@googlegroups.com>\nCc: John Stultz <john.stultz@linaro.org>\nCc: Dmitry Vyukov <dvyukov@google.com>\nLink: http://lkml.kernel.org/r/20170530211655.802921648@linutronix.de\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/67003c9f8b4110d3a857a365eb248702da628b4b"}]}
{"actor":{"display_login":"mortezadadgar"}}