{"push_id":616039509,"size":55,"distinct_size":55,"ref":"refs/heads/test","head":"c8fa12696d42541fb8a37f98a5ade941136de0a3","before":"275d5f2252e451b76b85c01a438ddc26a18ed15d","commits":[{"sha":"08b8454417c81f02acd6012275903fdcdfb9ebc1","author":{"email":"695e2a2c1e39535baaa147c5eb4e5da14054d59f@intel.com","name":"Keith Busch"},"message":"NVMe: Fix uninitialized iod compiler warning\n\ncommit c7d36ab8fa04c213328119a9c0d66985fe204ee5 upstream.\n\nSigned-off-by: Keith Busch <keith.busch@intel.com>\nSigned-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/08b8454417c81f02acd6012275903fdcdfb9ebc1"},{"sha":"5055c59bc3331072f05dafc2a1006ae40ab14cd8","author":{"email":"70806a71956ed8873ecff8522779dae1401a1b4a@gmail.com","name":"Daniel Mack"},"message":"ALSA: snd-usb-caiaq: initialize card pointer\n\ncommit da185443c12f5ef7416af50293833a5654854186 upstream.\n\nFixes the following warning:\n\n  CC [M]  sound/usb/caiaq/device.o\nsound/usb/caiaq/device.c: In function ‘snd_probe’:\nsound/usb/caiaq/device.c:500:16: warning: ‘card’ may be used\nuninitialized in this function [-Wmaybe-uninitialized]\n\nSigned-off-by: Daniel Mack <zonque@gmail.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/5055c59bc3331072f05dafc2a1006ae40ab14cd8"},{"sha":"b0478f589fcb7a9f72fe7d4f9d18234e6444fb16","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"drivers/leds/leds-lp5521.c: fix lp5521_read() error handling\n\ncommit 5bc9ad774c063f6b41965e7314f2c26aa5e465a0 upstream.\n\nGcc 4.6.2 complains that:\n\n  drivers/leds/leds-lp5521.c: In function `lp5521_load_program':\n  drivers/leds/leds-lp5521.c:214:21: warning: `mode' may be used uninitialized in this function [-Wuninitialized]\n  drivers/leds/leds-lp5521.c: In function `lp5521_probe':\n  drivers/leds/leds-lp5521.c:788:5: warning: `buf' may be used uninitialized in this function [-Wuninitialized]\n  drivers/leds/leds-lp5521.c:740:6: warning: `ret' may be used uninitialized in this function [-Wuninitialized]\n\nThese are real problems if lp5521_read() returns an error.  When that\nhappens we should handle it, instead of ignoring it or doing a bitwise\nOR with all the other error codes and continuing.\n\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nCc: Milo <Milo.Kim@ti.com>\nCc: Richard Purdie <rpurdie@rpsys.net>\nCc: Bryan Wu <bryan.wu@canonical.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\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/xtrymind/android_kernel_google_msm/commits/b0478f589fcb7a9f72fe7d4f9d18234e6444fb16"},{"sha":"2bdd65912f54fd6b9eebdd46b517d3b8d1ea935f","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"mvsas: remove unused variable in mvs_task_exec()\n\ncommit cca85013ef54f66eb4616e6f3860549a96c8338b upstream.\n\nWe don't use \"dev\" any more after 07ec747a5f (\"libsas: remove\nata_port.lock management duties from lldds\") and it causes a compile\nwarning.\n\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nCc: Xiangliang Yu <yuxiangl@marvell.com>\nSigned-off-by: Dan Williams <dan.j.williams@intel.com>\nSigned-off-by: James Bottomley <JBottomley@Parallels.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/2bdd65912f54fd6b9eebdd46b517d3b8d1ea935f"},{"sha":"c4e7cbbcc67e4e0ae2987e1a872140f63de2b8ac","author":{"email":"9bf091559fc98493329f7d619638c79e91ccf029@linux.com","name":"Krzysztof Wilczynski"},"message":"scsi: aha152x: Fix sparse warning and make printing pointer address more portable.\n\ncommit b631cf1f899f9d2e449884dbccc34940637c639f upstream.\n\nThis is to change use of \"0x%08x\" in favour of \"%p\" as per ../Documentation/printk-formats.txt,\nwhich also takes care about the following warning during compilation time:\n\n  drivers/scsi/aha152x.c: In function ‘get_command’:\n  drivers/scsi/aha152x.c:2987: warning: cast from pointer to integer of different size\n\nSigned-off-by: Krzysztof Wilczynski <krzysztof.wilczynski@linux.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/c4e7cbbcc67e4e0ae2987e1a872140f63de2b8ac"},{"sha":"0eb82d344e8dd51dc71a8c8701062e84a9e65179","author":{"email":"ed0f1d78b8c21b2970494a178da4bdfa8beba2a7@lwfinger.net","name":"Larry Finger"},"message":"rtlwifi: rtl8192se: Fix gcc 4.7.x warning\n\ncommit f761b6947dde42890beea59b020e1be87491809e upstream.\n\nWith gcc 4.7.x, the following warning is issued as the routine that sets\nthe array has the possibility of not initializing the values:\n\n  CC [M]  drivers/net/wireless/rtlwifi/rtl8192se/phy.o\ndrivers/net/wireless/rtlwifi/rtl8192se/phy.c: In function ‘rtl92s_phy_set_txpower’:\ndrivers/net/wireless/rtlwifi/rtl8192se/phy.c:1268:23: warning: ‘ofdmpowerLevel[0]’ may be used uninitialized in this function [-Wuninitialized]\n\nSigned-off-by: Larry Finger <Larry.Finger@lwfinger.net>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/0eb82d344e8dd51dc71a8c8701062e84a9e65179"},{"sha":"4e194601ba500ba4e21d1d5bc76679369881628e","author":{"email":"22a70fd9773e4de05b12c05075e9bcd605577f4d@amd.com","name":"Robert Richter"},"message":"x86-32: Fix invalid stack address while in softirq\n\ncommit 1022623842cb72ee4d0dbf02f6937f38c92c3f41 upstream.\n\nIn 32 bit the stack address provided by kernel_stack_pointer() may\npoint to an invalid range causing NULL pointer access or page faults\nwhile in NMI (see trace below). This happens if called in softirq\ncontext and if the stack is empty. The address at &regs->sp is then\nout of range.\n\nFixing this by checking if regs and &regs->sp are in the same stack\ncontext. Otherwise return the previous stack pointer stored in struct\nthread_info. If that address is invalid too, return address of regs.\n\n BUG: unable to handle kernel NULL pointer dereference at 0000000a\n IP: [<c1004237>] print_context_stack+0x6e/0x8d\n *pde = 00000000\n Oops: 0000 [#1] SMP\n Modules linked in:\n Pid: 4434, comm: perl Not tainted 3.6.0-rc3-oprofile-i386-standard-g4411a05 #4 Hewlett-Packard HP xw9400 Workstation/0A1Ch\n EIP: 0060:[<c1004237>] EFLAGS: 00010093 CPU: 0\n EIP is at print_context_stack+0x6e/0x8d\n EAX: ffffe000 EBX: 0000000a ECX: f4435f94 EDX: 0000000a\n ESI: f4435f94 EDI: f4435f94 EBP: f5409ec0 ESP: f5409ea0\n  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068\n CR0: 8005003b CR2: 0000000a CR3: 34ac9000 CR4: 000007d0\n DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000\n DR6: ffff0ff0 DR7: 00000400\n Process perl (pid: 4434, ti=f5408000 task=f5637850 task.ti=f4434000)\n Stack:\n  000003e8 ffffe000 00001ffc f4e39b00 00000000 0000000a f4435f94 c155198c\n  f5409ef0 c1003723 c155198c f5409f04 00000000 f5409edc 00000000 00000000\n  f5409ee8 f4435f94 f5409fc4 00000001 f5409f1c c12dce1c 00000000 c155198c\n Call Trace:\n  [<c1003723>] dump_trace+0x7b/0xa1\n  [<c12dce1c>] x86_backtrace+0x40/0x88\n  [<c12db712>] ? oprofile_add_sample+0x56/0x84\n  [<c12db731>] oprofile_add_sample+0x75/0x84\n  [<c12ddb5b>] op_amd_check_ctrs+0x46/0x260\n  [<c12dd40d>] profile_exceptions_notify+0x23/0x4c\n  [<c1395034>] nmi_handle+0x31/0x4a\n  [<c1029dc5>] ? ftrace_define_fields_irq_handler_entry+0x45/0x45\n  [<c13950ed>] do_nmi+0xa0/0x2ff\n  [<c1029dc5>] ? ftrace_define_fields_irq_handler_entry+0x45/0x45\n  [<c13949e5>] nmi_stack_correct+0x28/0x2d\n  [<c1029dc5>] ? ftrace_define_fields_irq_handler_entry+0x45/0x45\n  [<c1003603>] ? do_softirq+0x4b/0x7f\n  <IRQ>\n  [<c102a06f>] irq_exit+0x35/0x5b\n  [<c1018f56>] smp_apic_timer_interrupt+0x6c/0x7a\n  [<c1394746>] apic_timer_interrupt+0x2a/0x30\n Code: 89 fe eb 08 31 c9 8b 45 0c ff 55 ec 83 c3 04 83 7d 10 00 74 0c 3b 5d 10 73 26 3b 5d e4 73 0c eb 1f 3b 5d f0 76 1a 3b 5d e8 73 15 <8b> 13 89 d0 89 55 e0 e8 ad 42 03 00 85 c0 8b 55 e0 75 a6 eb cc\n EIP: [<c1004237>] print_context_stack+0x6e/0x8d SS:ESP 0068:f5409ea0\n CR2: 000000000000000a\n ---[ end trace 62afee3481b00012 ]---\n Kernel panic - not syncing: Fatal exception in interrupt\n\nV2:\n* add comments to kernel_stack_pointer()\n* always return a valid stack address by falling back to the address\n  of regs\n\nReported-by: Yang Wei <wei.yang@windriver.com>\nSigned-off-by: Robert Richter <robert.richter@amd.com>\nLink: http://lkml.kernel.org/r/20120912135059.GZ8285@erda.amd.com\nSigned-off-by: H. Peter Anvin <hpa@linux.intel.com>\nCc: Jun Zhang <jun.zhang@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/4e194601ba500ba4e21d1d5bc76679369881628e"},{"sha":"805754ae1cbed8635e20ad73e83a6ae53a839f33","author":{"email":"b02f0790d66a0f0a6b369873bf6df37420fbe5dd@intel.com","name":"Matt Fleming"},"message":"x86, efi: Fix processor-specific memcpy() build error\n\ncommit 0f905a43ce955b638139bd84486194770a6a2c08 upstream.\n\nBuilding for Athlon/Duron/K7 results in the following build error,\n\narch/x86/boot/compressed/eboot.o: In function `__constant_memcpy3d':\neboot.c:(.text+0x385): undefined reference to `_mmx_memcpy'\narch/x86/boot/compressed/eboot.o: In function `efi_main':\neboot.c:(.text+0x1a22): undefined reference to `_mmx_memcpy'\n\nbecause the boot stub code doesn't link with the kernel proper, and\ntherefore doesn't have access to the 3DNow version of memcpy. So,\nfollow the example of misc.c and #undef memcpy so that we use the\nversion provided by misc.c.\n\nSee https://bugzilla.kernel.org/show_bug.cgi?id=50391\n\nReported-by: Al Viro <viro@zeniv.linux.org.uk>\nReported-by: Ryan Underwood <nemesis@icequake.net>\nCc: H. Peter Anvin <hpa@zytor.com>\nSigned-off-by: Matt Fleming <matt.fleming@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/805754ae1cbed8635e20ad73e83a6ae53a839f33"},{"sha":"faa2f2f7b4f9415e290e12043a928a4491f773f5","author":{"email":"b41c17b861974b03cec38e3ec2992769b9bfae55@amd.com","name":"Boris Ostrovsky"},"message":"x86, microcode, AMD: Add support for family 16h processors\n\ncommit 36c46ca4f322a7bf89aad5462a3a1f61713edce7 upstream.\n\nAdd valid patch size for family 16h processors.\n\n[ hpa: promoting to urgent/stable since it is hw enabling and trivial ]\n\nSigned-off-by: Boris Ostrovsky <boris.ostrovsky@amd.com>\nAcked-by: Andreas Herrmann <herrmann.der.user@googlemail.com>\nLink: http://lkml.kernel.org/r/1353004910-2204-1-git-send-email-boris.ostrovsky@amd.com\nSigned-off-by: H. Peter Anvin <hpa@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/faa2f2f7b4f9415e290e12043a928a4491f773f5"},{"sha":"885b12e0b603c9a449a03d6e0b0faf8bfb126bda","author":{"email":"efcb9882ab6e84a080de34c9a74e0036aaa50134@solcon.nl","name":"Albert Pool"},"message":"rtlwifi: rtl8192cu: Add new USB ID\n\ncommit a485e827f07bfdd0762059386e6e787bed6e81ee upstream.\n\nThis is an ISY IWL 2000. Probably a clone of Belkin F7D1102 050d:1102.\nIts FCC ID is the same.\n\nSigned-off-by: Albert Pool <albertpool@solcon.nl>\nAcked-by: Larry Finger <Larry.Finger@lwfinger.net>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/885b12e0b603c9a449a03d6e0b0faf8bfb126bda"},{"sha":"d78a2f741b79002579b8ea6e4de7cd8f5744f6d5","author":{"email":"abbaae6378dda6b8d65fe6bd0f8beb334a5e4c4f@marvell.com","name":"Bing Zhao"},"message":"mwifiex: report error to MMC core if we cannot suspend\n\ncommit dd321acddc3be1371263b8c9e6c6f2af89f63d57 upstream.\n\nWhen host_sleep_config command fails we should return error to\nMMC core to indicate the failure for our device.\n\nThe misspelled variable is also removed as it's redundant.\n\nSigned-off-by: Bing Zhao <bzhao@marvell.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/d78a2f741b79002579b8ea6e4de7cd8f5744f6d5"},{"sha":"0cff68e9b4f2becaf802f7f3b8856d671ac79dcf","author":{"email":"abbaae6378dda6b8d65fe6bd0f8beb334a5e4c4f@marvell.com","name":"Bing Zhao"},"message":"mwifiex: fix system hang issue in cmd timeout error case\n\ncommit b1a47aa5e1e159e2cb06d7dfcc17ef5149b09299 upstream.\n\nReported by Tim Shepard:\nI was seeing sporadic failures (wedgeups), and the majority of those\nfailures I saw printed the printouts in mwifiex_cmd_timeout_func with\ncmd = 0xe5 which is CMD_802_11_HS_CFG_ENH.  When this happens, two\nminutes later I get notified that the rtcwake thread is blocked, like\nthis:\n      INFO: task rtcwake:3495 blocked for more than 120 seconds.\n\nTo get the hung thread unblocked we wake up the cmd wait queue and\ncancel the ioctl.\n\nReported-by: Tim Shepard <shep@laptop.org>\nSigned-off-by: Bing Zhao <bzhao@marvell.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/0cff68e9b4f2becaf802f7f3b8856d671ac79dcf"},{"sha":"757a83cc33ff30815fc59543d8afb2b7d2f07b9d","author":{"email":"dab3e64c9b6ff7dce28693076765b4373d8dfee7@intel.com","name":"Maciej Patelczyk"},"message":"SCSI: isci: copy fis 0x34 response into proper buffer\n\ncommit 49bd665c5407a453736d3232ee58f2906b42e83c upstream.\n\nSATA MICROCODE DOWNALOAD fails on isci driver. After receiving Register\nDevice to Host (FIS 0x34) frame Initiator resets phy.\nIn the frame handler routine response (FIS 0x34) was copied into wrong\nbuffer and upper layer did not receive any answer which resulted in\ntimeout and reset.\nThis patch corrects this bug.\n\nSigned-off-by: Maciej Patelczyk <maciej.patelczyk@intel.com>\nSigned-off-by: Lukasz Dorau <lukasz.dorau@intel.com>\nSigned-off-by: James Bottomley <JBottomley@Parallels.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/757a83cc33ff30815fc59543d8afb2b7d2f07b9d"},{"sha":"26e3bf0c73b880d8278a8a09379b443edad72321","author":{"email":"08dc22c6156113f2deff178e35e3ed9b24d6af9e@amd.com","name":"Alex Deucher"},"message":"drm/radeon: add new SI pci id\n\ncommit 0181bd5dea2ed0696f84591a92da0b6a1f1a2e62 upstream.\n\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/26e3bf0c73b880d8278a8a09379b443edad72321"},{"sha":"c66fbb66407eaa326c2289e806e7aa73452801b4","author":{"email":"9f57ef5ff1095f40b1ee8b7caa363908baef59d7@ladisch.de","name":"Clemens Ladisch"},"message":"ALSA: ua101, usx2y: fix broken MIDI output\n\ncommit e99ddfde6ae0dd2662bb40435696002b590e4057 upstream.\n\nCommit 88a8516a2128 (ALSA: usbaudio: implement USB autosuspend) added\nautosuspend code to all files making up the snd-usb-audio driver.\nHowever, midi.c is part of snd-usb-lib and is also used by other\ndrivers, not all of which support autosuspend.  Thus, calls to\nusb_autopm_get_interface() could fail, and this unexpected error would\nresult in the MIDI output being completely unusable.\n\nMake it work by ignoring the error that is expected with drivers that do\nnot support autosuspend.\n\nReported-by: Colin Fletcher <colin.m.fletcher@googlemail.com>\nReported-by: Devin Venable <venable.devin@gmail.com>\nReported-by: Dr Nick Bailey <nicholas.bailey@glasgow.ac.uk>\nReported-by: Jannis Achstetter <jannis_achstetter@web.de>\nReported-by: Rui Nuno Capela <rncbc@rncbc.org>\nCc: Oliver Neukum <oliver@neukum.org>\nSigned-off-by: Clemens Ladisch <clemens@ladisch.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/c66fbb66407eaa326c2289e806e7aa73452801b4"},{"sha":"eeb06b97e0e9dc44e4b0947a1b9bc5dfe7726a9d","author":{"email":"9fb354e0a5603a0331399c18f4aa5aab2f9d9c5b@canonical.com","name":"David Henningsson"},"message":"ALSA: hda - Cirrus: Correctly clear line_out_pins when moving to speaker\n\ncommit 34c3d1926bdaf45d3a891dd577482abcdd9faa34 upstream.\n\nIf this array is not cleared, the jack related code later might\nfail to create \"Internal Speaker Phantom Jack\" on Dell Inspiron 3420 and\nDell Vostro 2420.\n\nBugLink: https://bugs.launchpad.net/bugs/1076840\nSigned-off-by: David Henningsson <david.henningsson@canonical.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/eeb06b97e0e9dc44e4b0947a1b9bc5dfe7726a9d"},{"sha":"f90b35bdb0538992c750ecfd9cbe22121170fb33","author":{"email":"407b36959ca09543ccda8f8e06721c791bc53435@HansenPartnership.com","name":"James Bottomley"},"message":"PARISC: fix virtual aliasing issue in get_shared_area()\n\ncommit 949a05d03490e39e773e8652ccab9157e6f595b4 upstream.\n\nOn Thu, 2012-11-01 at 16:45 -0700, Michel Lespinasse wrote:\n> Looking at the arch/parisc/kernel/sys_parisc.c implementation of\n> get_shared_area(), I do have a concern though. The function basically\n> ignores the pgoff argument, so that if one creates a shared mapping of\n> pages 0-N of a file, and then a separate shared mapping of pages 1-N\n> of that same file, both will have the same cache offset for their\n> starting address.\n>\n> This looks like this would create obvious aliasing issues. Am I\n> misreading this ? I can't understand how this could work good enough\n> to be undetected, so there must be something I'm missing here ???\n\nThis turns out to be correct and we need to pay attention to the pgoff as\nwell as the address when creating the virtual address for the area.\nFortunately, the bug is rarely triggered as most applications which use pgoff\ntend to use large values (git being the primary one, and it uses pgoff in\nmultiples of 16MB) which are larger than our cache coherency modulus, so the\nproblem isn't often seen in practise.\n\nReported-by: Michel Lespinasse <walken@google.com>\nSigned-off-by: James Bottomley <JBottomley@Parallels.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/f90b35bdb0538992c750ecfd9cbe22121170fb33"},{"sha":"4efa7ccd9458275396866b1a6d362fbac94059c4","author":{"email":"de609eb4d5d70b1d38ec6642adbfc33a2781f63c@ZenIV.linux.org.uk","name":"Al Viro"},"message":"PARISC: fix user-triggerable panic on parisc\n\ncommit 441a179dafc0f99fc8b3a8268eef66958621082e upstream.\n\nint sys32_rt_sigprocmask(int how, compat_sigset_t __user *set, compat_sigset_t __user *oset,\n                                    unsigned int sigsetsize)\n{\n        sigset_t old_set, new_set;\n        int ret;\n\n        if (set && get_sigset32(set, &new_set, sigsetsize))\n\n...\nstatic int\nget_sigset32(compat_sigset_t __user *up, sigset_t *set, size_t sz)\n{\n        compat_sigset_t s;\n        int r;\n\n        if (sz != sizeof *set) panic(\"put_sigset32()\");\n\nIn other words, rt_sigprocmask(69, (void *)69, 69) done by 32bit process\nwill promptly panic the box.\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>\nSigned-off-by: James Bottomley <JBottomley@Parallels.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/4efa7ccd9458275396866b1a6d362fbac94059c4"},{"sha":"63a15899ca6ad8fb030ac41c4ea377829154168d","author":{"email":"1808e78cd17f2f3e319786a8bc7de3814d0401fd@gmail.com","name":"Jiri Engelthaler"},"message":"mtd: slram: invalid checking of absolute end address\n\ncommit c36a7ff4578ab6294885aef5ef241aeec4cdb1f0 upstream.\n\nFixed parsing end absolute address.\n\nSigned-off-by: Jiri Engelthaler <engycz@gmail.com>\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/63a15899ca6ad8fb030ac41c4ea377829154168d"},{"sha":"ad95545bf04539989d357a8ff704ba0c94495c35","author":{"email":"1c3b1584a6008857f36c03c58f657c0fc16fc09e@linaro.org","name":"Sachin Kamat"},"message":"mtd: ofpart: Fix incorrect NULL check in parse_ofoldpart_partitions()\n\ncommit 5a6ea4af0907f995dc06df21a9c9ef764c7cd3bc upstream.\n\nThe pointer returned by kzalloc should be tested for NULL\nto avoid potential NULL pointer dereference later. Incorrect\npointer was being tested for NULL. Bug introduced by commit fbcf62a3\n(mtd: physmap_of: move parse_obsolete_partitions to become separate\nparser).\nThis patch fixes this bug.\n\nSigned-off-by: Sachin Kamat <sachin.kamat@linaro.org>\nCc: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>\nCc: Artem Bityutskiy <artem.bityutskiy@intel.com>\nSigned-off-by: David Woodhouse <David.Woodhouse@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/xtrymind/android_kernel_google_msm/commits/ad95545bf04539989d357a8ff704ba0c94495c35"}]}