{"push_id":744148731,"size":431,"distinct_size":24,"ref":"refs/heads/master","head":"f8615041974363287b1a2f625253ac156341c873","before":"ebeeca843d452b2d0e4d388733366133fdc264b5","commits":[{"sha":"e16f595702831edb8ae4675a9ddde2dfdbf61d31","author":{"email":"4e624af203c18e164acadf5da06f2c9f36828cb4@canonical.com","name":"Luis Henriques"},"message":"UBUNTU: Start new release\n\nIgnore: yes\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/e16f595702831edb8ae4675a9ddde2dfdbf61d31"},{"sha":"35b59c65784a1b97a5fd6886bd45975562aad1ae","author":{"email":"50fbbd36fe0f9c8261d4a3c762c8c29ffb35e48f@redhat.com","name":"Denys Vlasenko"},"message":"x86/asm/entry/64: Fold the 'test_in_nmi' macro into its only user\n\ncommit 0784b36448a2a85b95b6eb21a69b9045c896c065 upstream.\n\nNo code changes.\n\nSigned-off-by: Denys Vlasenko <dvlasenk@redhat.com>\nAcked-by: Borislav Petkov <bp@suse.de>\nCc: Alexei Starovoitov <ast@plumgrid.com>\nCc: Andy Lutomirski <luto@amacapital.net>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Kees Cook <keescook@chromium.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: Steven Rostedt <rostedt@goodmis.org>\nCc: Will Drewry <wad@chromium.org>\nLink: http://lkml.kernel.org/r/1427899858-7165-1-git-send-email-dvlasenk@redhat.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nAcked-by: John Johansen <john.johansen@canonical.com>\nAcked-by: Andy Whitcroft <apw@canonical.com>\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/35b59c65784a1b97a5fd6886bd45975562aad1ae"},{"sha":"2d964e41e68b40bfa957c70b2a408821b47cc9f0","author":{"email":"50fbbd36fe0f9c8261d4a3c762c8c29ffb35e48f@redhat.com","name":"Denys Vlasenko"},"message":"x86/asm/entry/64: Remove a redundant jump\n\ncommit a30b0085f54efae11f6256df4e4a16af7eefc1c4 upstream.\n\nJumping to the very next instruction is not very useful:\n\n        jmp label\n    label:\n\nRemoving the jump.\n\nSigned-off-by: Denys Vlasenko <dvlasenk@redhat.com>\nCc: Alexei Starovoitov <ast@plumgrid.com>\nCc: Andy Lutomirski <luto@amacapital.net>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Brian Gerst <brgerst@gmail.com>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Kees Cook <keescook@chromium.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: Steven Rostedt <rostedt@goodmis.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Will Drewry <wad@chromium.org>\nLink: http://lkml.kernel.org/r/1428439424-7258-5-git-send-email-dvlasenk@redhat.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nAcked-by: John Johansen <john.johansen@canonical.com>\nAcked-by: Andy Whitcroft <apw@canonical.com>\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/2d964e41e68b40bfa957c70b2a408821b47cc9f0"},{"sha":"4c5b89653e876a42dc4b40a1184e2d471084a519","author":{"email":"2cc0d0d76de2e6f37b92deeb83c85cb306fc5dc1@kernel.org","name":"Andy Lutomirski"},"message":"x86/nmi: Enable nested do_nmi handling for 64-bit kernels\n\ncommit 9d05041679904b12c12421cbcf9cb5f4860a8d7b upstream.\n\n32-bit kernels handle nested NMIs in C.  Enable the exact same\nhandling on 64-bit kernels as well.  This isn't currently necessary,\nbut it will become necessary once the asm code starts allowing\nlimited nesting.\n\nThis is a prerequisite for the fix for CVE-2015-3290.\n\nCc: stable@vger.kernel.org\nReviewed-by: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Andy Lutomirski <luto@kernel.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nAcked-by: John Johansen <john.johansen@canonical.com>\nAcked-by: Andy Whitcroft <apw@canonical.com>\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/4c5b89653e876a42dc4b40a1184e2d471084a519"},{"sha":"4da27bf68b16eeae11a8f8215cb45c221c56e841","author":{"email":"2cc0d0d76de2e6f37b92deeb83c85cb306fc5dc1@kernel.org","name":"Andy Lutomirski"},"message":"x86/nmi/64: Remove asm code that saves cr2\n\ncommit 0e181bb58143cb4a2e8f01c281b0816cd0e4798e upstream.\n\nNow that do_nmi saves cr2, we don't need to save it in asm.\n\nThis is a prerequisity for the fix for CVE-2015-3290.\n\nCc: stable@vger.kernel.org\nReviewed-by: Steven Rostedt <rostedt@goodmis.org>\nAcked-by: Borislav Petkov <bp@suse.de>\nSigned-off-by: Andy Lutomirski <luto@kernel.org>\n[bwh: Backported to 4.0: adjust filename, context]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nAcked-by: John Johansen <john.johansen@canonical.com>\nAcked-by: Andy Whitcroft <apw@canonical.com>\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/4da27bf68b16eeae11a8f8215cb45c221c56e841"},{"sha":"01f9605190361bea6a2131815ab6f14cc57d1f26","author":{"email":"2cc0d0d76de2e6f37b92deeb83c85cb306fc5dc1@kernel.org","name":"Andy Lutomirski"},"message":"x86/nmi/64: Switch stacks on userspace NMI entry\n\ncommit 9b6e6a8334d56354853f9c255d1395c2ba570e0a upstream.\n\nReturning to userspace is tricky: IRET can fail, and ESPFIX can\nrearrange the stack prior to IRET.\n\nThe NMI nesting fixup relies on a precise stack layout and atomic\nIRET.  Rather than trying to teach the NMI nesting fixup to handle\nESPFIX and failed IRET, punt: run NMIs that came from user mode on\nthe normal kernel stack.\n\nThis will make some nested NMIs visible to C code, but the C code is\nokay with that.\n\nAs a side effect, this should speed up perf: it eliminates an RDMSR\nwhen NMIs come from user mode.\n\nFixes CVE-2015-3290.\n\nCc: stable@vger.kernel.org\nReviewed-by: Steven Rostedt <rostedt@goodmis.org>\nReviewed-by: Borislav Petkov <bp@suse.de>\nSigned-off-by: Andy Lutomirski <luto@kernel.org>\n[bwh: Backported to 4.0:\n - Adjust filename, context\n - s/restore_c_regs_and_iret/restore_args/\n - Use kernel_stack + KERNEL_STACK_OFFSET instead of cpu_current_top_of_stack]\n[luto: Open-coded return path to avoid dependency on partial pt_regs details]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nSigned-off-by: Andy Lutomirski <luto@kernel.org>\nAcked-by: John Johansen <john.johansen@canonical.com>\nAcked-by: Andy Whitcroft <apw@canonical.com>\nCVE-2015-3290, CVE-2015-5157\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/01f9605190361bea6a2131815ab6f14cc57d1f26"},{"sha":"386826fc53d1ad3fe33dcaf97a60da92b5821773","author":{"email":"2cc0d0d76de2e6f37b92deeb83c85cb306fc5dc1@kernel.org","name":"Andy Lutomirski"},"message":"x86/nmi/64: Improve nested NMI comments\n\ncommit 0b22930ebad563ae97ff3f8d7b9f12060b4c6e6b upstream.\n\nI found the nested NMI documentation to be difficult to follow.\nImprove the comments.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Andy Lutomirski <luto@kernel.org>\n[bwh: Backported to 4.0: adjust filename, context]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nAcked-by: John Johansen <john.johansen@canonical.com>\nAcked-by: Andy Whitcroft <apw@canonical.com>\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/386826fc53d1ad3fe33dcaf97a60da92b5821773"},{"sha":"043fafac0f877bf284fb8d4a535ce85c944f58fc","author":{"email":"2cc0d0d76de2e6f37b92deeb83c85cb306fc5dc1@kernel.org","name":"Andy Lutomirski"},"message":"x86/nmi/64: Reorder nested NMI checks\n\ncommit a27507ca2d796cfa8d907de31ad730359c8a6d06 upstream.\n\nCheck the repeat_nmi .. end_repeat_nmi special case first.  The next\npatch will rework the RSP check and, as a side effect, the RSP check\nwill no longer detect repeat_nmi .. end_repeat_nmi, so we'll need\nthis ordering of the checks.\n\nNote: this is more subtle than it appears.  The check for repeat_nmi\n.. end_repeat_nmi jumps straight out of the NMI code instead of\nadjusting the \"iret\" frame to force a repeat.  This is necessary,\nbecause the code between repeat_nmi and end_repeat_nmi sets \"NMI\nexecuting\" and then writes to the \"iret\" frame itself.  If a nested\nNMI comes in and modifies the \"iret\" frame while repeat_nmi is also\nmodifying it, we'll end up with garbage.  The old code got this\nright, as does the new code, but the new code is a bit more\nexplicit.\n\nIf we were to move the check right after the \"NMI executing\" check,\nthen we'd get it wrong and have random crashes.\n\nThis is a prerequisite for the fix for CVE-2015-3291.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Andy Lutomirski <luto@kernel.org>\n[bwh: Backported to 4.0: adjust filename, spacing]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nAcked-by: John Johansen <john.johansen@canonical.com>\nAcked-by: Andy Whitcroft <apw@canonical.com>\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/043fafac0f877bf284fb8d4a535ce85c944f58fc"},{"sha":"5330a0ff554210017d78126aacfc16585be65ee2","author":{"email":"2cc0d0d76de2e6f37b92deeb83c85cb306fc5dc1@kernel.org","name":"Andy Lutomirski"},"message":"x86/nmi/64: Use DF to avoid userspace RSP confusing nested NMI detection\n\ncommit 810bc075f78ff2c221536eb3008eac6a492dba2d upstream.\n\nWe have a tricky bug in the nested NMI code: if we see RSP pointing\nto the NMI stack on NMI entry from kernel mode, we assume that we\nare executing a nested NMI.\n\nThis isn't quite true.  A malicious userspace program can point RSP\nat the NMI stack, issue SYSCALL, and arrange for an NMI to happen\nwhile RSP is still pointing at the NMI stack.\n\nFix it with a sneaky trick.  Set DF in the region of code that the RSP\ncheck is intended to detect.  IRET will clear DF atomically.\n\n(Note: other than paravirt, there's little need for all this complexity.\n We could check RIP instead of RSP.)\n\nFixes CVE-2015-3291.\n\nCc: stable@vger.kernel.org\nReviewed-by: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Andy Lutomirski <luto@kernel.org>\n[bwh: Backported to 4.0: adjust filename, context]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nAcked-by: John Johansen <john.johansen@canonical.com>\nAcked-by: Andy Whitcroft <apw@canonical.com>\nCVE-2015-3291\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/5330a0ff554210017d78126aacfc16585be65ee2"},{"sha":"5f30707dc7c4299992b18c962e5f6d4839ca4b91","author":{"email":"d100aa70785e45ee8deab668147d941941915c21@canonical.com","name":"Colin Ian King"},"message":"UBUNTU: SAUCE: KEYS: ensure we free the assoc array edit if edit is valid\n\n__key_link_end is not freeing the associated array edit structure\nand this leads to a 512 byte memory leak each time an identical\nexisting key is added with add_key().\n\nThe reason the add_key() system call returns okay is that\nkey_create_or_update() calls __key_link_begin() before checking to see\nwhether it can update a key directly rather than adding/replacing - which\nit turns out it can.  Thus __key_link() is not called through\n__key_instantiate_and_link() and __key_link_end() must cancel the edit.\n\nCVE-2015-1333\n\nSigned-off-by: Colin Ian King <colin.king@canonical.com>\nSigned-off-by: David Howells <dhowells@redhat.com>\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/5f30707dc7c4299992b18c962e5f6d4839ca4b91"},{"sha":"60bb4f1b6b1b67d54d5e9c4f1d94dd11c8f610cf","author":{"email":"4e624af203c18e164acadf5da06f2c9f36828cb4@canonical.com","name":"Luis Henriques"},"message":"UBUNTU: Ubuntu-3.19.0-25.26\n\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/60bb4f1b6b1b67d54d5e9c4f1d94dd11c8f610cf"},{"sha":"14565d5968d4627cafcf3c4df4747550e075c205","author":{"email":"4e624af203c18e164acadf5da06f2c9f36828cb4@canonical.com","name":"Luis Henriques"},"message":"UBUNTU: Start new release\n\nIgnore: yes\nSigned-off-by: Luis Henriques <luis.henriques@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/14565d5968d4627cafcf3c4df4747550e075c205"},{"sha":"312cb1050f029079378042e06ac27121d791da5b","author":{"email":"5cc5d8d4c7115f1c96c2983ec0d0f8a0f9dab596@canonical.com","name":"Kamal Mostafa"},"message":"Revert \"tools/vm: fix page-flags build\"\n\nBugLink: http://bugs.launchpad.net/bugs/1473547\n\nThis reverts commit 3ddd7003c1769604977177ba8a3c4cb8b3c3029a\nfrom 3.19-stable.\n\nPatch is not suitable for 3.19-stable (breaks \"make -C tools/vm\").\n\nCc: Sasha Levin <sasha.levin@oracle.com>\nSigned-off-by: Kamal Mostafa <kamal@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/312cb1050f029079378042e06ac27121d791da5b"},{"sha":"059494a581f0f6523210fb1afd3773b401bc1da2","author":{"email":"43232e92d70cc7aa53504ad0397085ee47bad87f@goodmis.org","name":"Steven Rostedt"},"message":"module: Call module notifier on failure after complete_formation()\n\nBugLink: http://bugs.launchpad.net/bugs/1473547\n\ncommit 37815bf866ab6722a47550f8d25ad3f1a16a680c upstream.\n\nThe module notifier call chain for MODULE_STATE_COMING was moved up before\nthe parsing of args, into the complete_formation() call. But if the module failed\nto load after that, the notifier call chain for MODULE_STATE_GOING was\nnever called and that prevented the users of those call chains from\ncleaning up anything that was allocated.\n\nLink: http://lkml.kernel.org/r/554C52B9.9060700@gmail.com\n\nReported-by: Pontus Fuchs <pontus.fuchs@gmail.com>\nFixes: 4982223e51e8 \"module: set nx before marking module MODULE_STATE_COMING\"\nSigned-off-by: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Rusty Russell <rusty@rustcorp.com.au>\nSigned-off-by: Kamal Mostafa <kamal@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/059494a581f0f6523210fb1afd3773b401bc1da2"},{"sha":"7b7dd85ebf702ae1b089502fefc598785135047c","author":{"email":"6eab646cab2e5888a0f46fc34c03dddf1c9069ce@gmx.de","name":"Michael Brunner"},"message":"gpio: gpio-kempld: Fix get_direction return value\n\nBugLink: http://bugs.launchpad.net/bugs/1473547\n\ncommit f230e8ffc03f17bd9d6b90ea890b8252a8cc1821 upstream.\n\nThis patch fixes an inverted return value of the gpio get_direction\nfunction.\n\nThe wrong value causes the direction sysfs entry and GPIO debugfs file\nto indicate incorrect GPIO direction settings. In some cases it also\nprevents setting GPIO output values.\n\nThe problem is also present in all other stable kernel versions since\nlinux-3.12.\n\nReported-by: Jochen Henneberg <jh@henneberg-systemdesign.com>\nSigned-off-by: Michael Brunner <michael.brunner@kontron.com>\nReviewed-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>\nSigned-off-by: Kamal Mostafa <kamal@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/7b7dd85ebf702ae1b089502fefc598785135047c"},{"sha":"32a3a69e8baf1aba0b2daaeb910cfe0929c4825c","author":{"email":"bbcee05fa0d16bdfc64e49f659d2d19cc06417c3@gmail.com","name":"Philippe Reynes"},"message":"ARM: dts: imx27: only map 4 Kbyte for fec registers\n\nBugLink: http://bugs.launchpad.net/bugs/1473547\n\ncommit a29ef819f3f34f89a1b9b6a939b4c1cdfe1e85ce upstream.\n\nAccording to the imx27 documentation, fec has a 4 Kbyte\nmemory space map. Moreover, the actual 16 Kbyte mapping\noverlaps the SCC (Security Controller) memory register\nspace. So, we reduce the memory register space to 4 Kbyte.\n\nSigned-off-by: Philippe Reynes <tremyfr@gmail.com>\nAcked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>\nFixes: 9f0749e3eb88 (\"ARM i.MX27: Add devicetree support\")\nSigned-off-by: Shawn Guo <shawn.guo@linaro.org>\nSigned-off-by: Kamal Mostafa <kamal@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/32a3a69e8baf1aba0b2daaeb910cfe0929c4825c"},{"sha":"07aa583d9c041fbc80a3ede2f992b061e6fb578a","author":{"email":"1db9dd262beaa64f35756dd39531d9747b7778bb@arm.com","name":"Mark Rutland"},"message":"ARM: 8356/1: mm: handle non-pmd-aligned end of RAM\n\nBugLink: http://bugs.launchpad.net/bugs/1473547\n\ncommit 965278dcb8ab0b1f666cc47937933c4be4aea48d upstream.\n\nAt boot time we round the memblock limit down to section size in an\nattempt to ensure that we will have mapped this RAM with section\nmappings prior to allocating from it. When mapping RAM we iterate over\nPMD-sized chunks, creating these section mappings.\n\nSection mappings are only created when the end of a chunk is aligned to\nsection size. Unfortunately, with classic page tables (where PMD_SIZE is\n2 * SECTION_SIZE) this means that if a chunk is between 1M and 2M in\nsize the first 1M will not be mapped despite having been accounted for\nin the memblock limit. This has been observed to result in page tables\nbeing allocated from unmapped memory, causing boot-time hangs.\n\nThis patch modifies the memblock limit rounding to always round down to\nPMD_SIZE instead of SECTION_SIZE. For classic MMU this means that we\nwill round the memblock limit down to a 2M boundary, matching the limits\non section mappings, and preventing allocations from unmapped memory.\nFor LPAE there should be no change as PMD_SIZE == SECTION_SIZE.\n\nSigned-off-by: Mark Rutland <mark.rutland@arm.com>\nReported-by: Stefan Agner <stefan@agner.ch>\nTested-by: Stefan Agner <stefan@agner.ch>\nAcked-by: Laura Abbott <labbott@redhat.com>\nTested-by: Hans de Goede <hdegoede@redhat.com>\nCc: Catalin Marinas <catalin.marinas@arm.com>\nCc: Steve Capper <steve.capper@linaro.org>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: Kamal Mostafa <kamal@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/07aa583d9c041fbc80a3ede2f992b061e6fb578a"},{"sha":"a1040793bb57f2a89c49f1fd43ea04ecc243295c","author":{"email":"0691a664b24b6f15b20cd5aee64b72271db08be1@suse.de","name":"Borislav Petkov"},"message":"x86/mce: Fix MCE severity messages\n\nBugLink: http://bugs.launchpad.net/bugs/1473547\n\ncommit 17fea54bf0ab34fa09a06bbde2f58ed7bbdf9299 upstream.\n\nDerek noticed that a critical MCE gets reported with the wrong\nerror type description:\n\n  [Hardware Error]: CPU 34: Machine Check Exception: 5 Bank 9: f200003f000100b0\n  [Hardware Error]: RIP !INEXACT! 10:<ffffffff812e14c1> {intel_idle+0xb1/0x170}\n  [Hardware Error]: TSC 49587b8e321cb\n  [Hardware Error]: PROCESSOR 0:306e4 TIME 1431561296 SOCKET 1 APIC 29\n  [Hardware Error]: Some CPUs didn't answer in synchronization\n  [Hardware Error]: Machine check: Invalid\n\t\t\t\t   ^^^^^^^\n\nThe last line with 'Invalid' should have printed the high level\nMCE error type description we get from mce_severity, i.e.\nsomething like:\n\n  [Hardware Error]: Machine check: Action required: data load error in a user process\n\nthis happens due to the fact that mce_no_way_out() iterates over\nall MCA banks and possibly overwrites the @msg argument which is\nused in the panic printing later.\n\nChange behavior to take the message of only and the (last)\ncritical MCE it detects.\n\nReported-by: Derek <denc716@gmail.com>\nSigned-off-by: Borislav Petkov <bp@suse.de>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Tony Luck <tony.luck@intel.com>\nLink: http://lkml.kernel.org/r/1431936437-25286-3-git-send-email-bp@alien8.de\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Kamal Mostafa <kamal@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/a1040793bb57f2a89c49f1fd43ea04ecc243295c"},{"sha":"46d6e2133f382c5e51be8882c557a5448261c9ec","author":{"email":"bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com","name":"Johannes Berg"},"message":"mac80211: don't use napi_gro_receive() outside NAPI context\n\nBugLink: http://bugs.launchpad.net/bugs/1473547\n\ncommit 22d3a3c829fa9ecdb493d1f1f2838d543f8d86a3 upstream.\n\nNo matter how the driver manages its NAPI context, there's no way\nsending frames to it from a timer can be correct, since it would\ncorrupt the internal GRO lists.\n\nTo avoid that, always use the non-NAPI path when releasing frames\nfrom the timer.\n\nReported-by: Jean Trivelly <jean.trivelly@intel.com>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: Kamal Mostafa <kamal@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/46d6e2133f382c5e51be8882c557a5448261c9ec"},{"sha":"9281f7358279617ec46f78918a08e12671f8af66","author":{"email":"ea55cdcefe451c680d57a9a4a778e5f5e5aeef13@intel.com","name":"Haim Dreyfuss"},"message":"iwlwifi: mvm: Free fw_status after use to avoid memory leak\n\nBugLink: http://bugs.launchpad.net/bugs/1473547\n\ncommit 2fc863a5143d64b8f06576cc3d7fd5622c5cf3b5 upstream.\n\nfw_status is the only pointer pointing to a block of memory\nallocated above and should be freed after use.\nNote: this come from Klockwork static analyzer.\n\nFixes: 2021a89d7b8a (\"iwlwifi: mvm: treat netdetect wake up separately\")\nSigned-off-by: Haim Dreyfuss <haim.dreyfuss@intel.com>\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Kamal Mostafa <kamal@canonical.com>","distinct":false,"url":"https://api.github.com/repos/vmayoral/ubuntu-vivid/commits/9281f7358279617ec46f78918a08e12671f8af66"}]}