{"push_id":770752748,"size":1000,"distinct_size":1611,"ref":"refs/heads/cm-12.1","head":"907c27059838d904886fe48046c4d70c176fcdea","before":"2dab825f4cf9dfbf83367615eec1a07e86a5ccbf","commits":[{"sha":"b3c7bbd28bedd353375b620675f4ad8e55887ab1","author":{"email":"546b05909706652891a87f7bfe385ae147f61f91@kernel.org","name":"Tejun Heo"},"message":"ahci: disable MSI instead of NCQ on Samsung pci-e SSDs on macbooks\n\ncommit 66a7cbc303f4d28f201529b06061944d51ab530c upstream.\n\nSamsung pci-e SSDs on macbooks failed miserably on NCQ commands, so\n67809f85d31e (\"ahci: disable NCQ on Samsung pci-e SSDs on macbooks\")\ndisabled NCQ on them.  It turns out that NCQ is fine as long as MSI is\nnot used, so let's turn off MSI and leave NCQ on.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nLink: https://bugzilla.kernel.org/show_bug.cgi?id=60731\nTested-by: <dorin@i51.org>\nTested-by: Imre Kaloz <kaloz@openwrt.org>\nFixes: 67809f85d31e (\"ahci: disable NCQ on Samsung pci-e SSDs on macbooks\")\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/HridayHS/Lightning-Tomato/commits/b3c7bbd28bedd353375b620675f4ad8e55887ab1"},{"sha":"3d5a4abe4ec50dd3fd5d0fef01d31a88b120edfb","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"ALSA: usb-audio: Fix memory leak in FTU quirk\n\ncommit 1a290581ded60e87276741f8ca97b161d2b226fc upstream.\n\nM-audio FastTrack Ultra quirk doesn't release the kzalloc'ed memory.\nThis patch adds the private_free callback to release it properly.\n\nSigned-off-by: Takashi Iwai <tiwai@suse.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/HridayHS/Lightning-Tomato/commits/3d5a4abe4ec50dd3fd5d0fef01d31a88b120edfb"},{"sha":"7fc33df2700488bd62f89aec3b7115443462c596","author":{"email":"8c5ea195856807f4f02a6e0749c87ea6b7375f38@gmail.com","name":"Max Filippov"},"message":"xtensa: re-wire umount syscall to sys_oldumount\n\ncommit 2651cc6974d47fc43bef1cd8cd26966e4f5ba306 upstream.\n\nUserspace actually passes single parameter (path name) to the umount\nsyscall, so new umount just fails. Fix it by requesting old umount\nsyscall implementation and re-wiring umount to it.\n\nSigned-off-by: Max Filippov <jcmvbkbc@gmail.com>\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/HridayHS/Lightning-Tomato/commits/7fc33df2700488bd62f89aec3b7115443462c596"},{"sha":"d90c60e4fbe38669a36f1259f7510e34ea089afc","author":{"email":"152d4c5bebf13a5b809d42b4d789cf9d887e6698@redhat.com","name":"Ilya Dryomov"},"message":"libceph: do not crash on large auth tickets\n\ncommit aaef31703a0cf6a733e651885bfb49edc3ac6774 upstream.\n\nLarge (greater than 32k, the value of PAGE_ALLOC_COSTLY_ORDER) auth\ntickets will have their buffers vmalloc'ed, which leads to the\nfollowing crash in crypto:\n\n[   28.685082] BUG: unable to handle kernel paging request at ffffeb04000032c0\n[   28.686032] IP: [<ffffffff81392b42>] scatterwalk_pagedone+0x22/0x80\n[   28.686032] PGD 0\n[   28.688088] Oops: 0000 [#1] PREEMPT SMP\n[   28.688088] Modules linked in:\n[   28.688088] CPU: 0 PID: 878 Comm: kworker/0:2 Not tainted 3.17.0-vm+ #305\n[   28.688088] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007\n[   28.688088] Workqueue: ceph-msgr con_work\n[   28.688088] task: ffff88011a7f9030 ti: ffff8800d903c000 task.ti: ffff8800d903c000\n[   28.688088] RIP: 0010:[<ffffffff81392b42>]  [<ffffffff81392b42>] scatterwalk_pagedone+0x22/0x80\n[   28.688088] RSP: 0018:ffff8800d903f688  EFLAGS: 00010286\n[   28.688088] RAX: ffffeb04000032c0 RBX: ffff8800d903f718 RCX: ffffeb04000032c0\n[   28.688088] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8800d903f750\n[   28.688088] RBP: ffff8800d903f688 R08: 00000000000007de R09: ffff8800d903f880\n[   28.688088] R10: 18df467c72d6257b R11: 0000000000000000 R12: 0000000000000010\n[   28.688088] R13: ffff8800d903f750 R14: ffff8800d903f8a0 R15: 0000000000000000\n[   28.688088] FS:  00007f50a41c7700(0000) GS:ffff88011fc00000(0000) knlGS:0000000000000000\n[   28.688088] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b\n[   28.688088] CR2: ffffeb04000032c0 CR3: 00000000da3f3000 CR4: 00000000000006b0\n[   28.688088] Stack:\n[   28.688088]  ffff8800d903f698 ffffffff81392ca8 ffff8800d903f6e8 ffffffff81395d32\n[   28.688088]  ffff8800dac96000 ffff880000000000 ffff8800d903f980 ffff880119b7e020\n[   28.688088]  ffff880119b7e010 0000000000000000 0000000000000010 0000000000000010\n[   28.688088] Call Trace:\n[   28.688088]  [<ffffffff81392ca8>] scatterwalk_done+0x38/0x40\n[   28.688088]  [<ffffffff81392ca8>] scatterwalk_done+0x38/0x40\n[   28.688088]  [<ffffffff81395d32>] blkcipher_walk_done+0x182/0x220\n[   28.688088]  [<ffffffff813990bf>] crypto_cbc_encrypt+0x15f/0x180\n[   28.688088]  [<ffffffff81399780>] ? crypto_aes_set_key+0x30/0x30\n[   28.688088]  [<ffffffff8156c40c>] ceph_aes_encrypt2+0x29c/0x2e0\n[   28.688088]  [<ffffffff8156d2a3>] ceph_encrypt2+0x93/0xb0\n[   28.688088]  [<ffffffff8156d7da>] ceph_x_encrypt+0x4a/0x60\n[   28.688088]  [<ffffffff8155b39d>] ? ceph_buffer_new+0x5d/0xf0\n[   28.688088]  [<ffffffff8156e837>] ceph_x_build_authorizer.isra.6+0x297/0x360\n[   28.688088]  [<ffffffff8112089b>] ? kmem_cache_alloc_trace+0x11b/0x1c0\n[   28.688088]  [<ffffffff8156b496>] ? ceph_auth_create_authorizer+0x36/0x80\n[   28.688088]  [<ffffffff8156ed83>] ceph_x_create_authorizer+0x63/0xd0\n[   28.688088]  [<ffffffff8156b4b4>] ceph_auth_create_authorizer+0x54/0x80\n[   28.688088]  [<ffffffff8155f7c0>] get_authorizer+0x80/0xd0\n[   28.688088]  [<ffffffff81555a8b>] prepare_write_connect+0x18b/0x2b0\n[   28.688088]  [<ffffffff81559289>] try_read+0x1e59/0x1f10\n\nThis is because we set up crypto scatterlists as if all buffers were\nkmalloc'ed.  Fix it.\n\nSigned-off-by: Ilya Dryomov <idryomov@redhat.com>\nReviewed-by: Sage Weil <sage@redhat.com>\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/HridayHS/Lightning-Tomato/commits/d90c60e4fbe38669a36f1259f7510e34ea089afc"},{"sha":"c5f154c1042850bcdf83107640e1184c4ba25260","author":{"email":"643a80aaf16a8332d6a70921c14d4bb265446494@intel.com","name":"Emmanuel Grumbach"},"message":"iwlwifi: configure the LTR\n\ncommit 9180ac50716a097a407c6d7e7e4589754a922260 upstream.\n\nThe LTR is the handshake between the device and the root\ncomplex about the latency allowed when the bus exits power\nsave. This configuration was missing and this led to high\nlatency in the link power up. The end user could experience\nhigh latency in the network because of this.\n\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\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/HridayHS/Lightning-Tomato/commits/c5f154c1042850bcdf83107640e1184c4ba25260"},{"sha":"e52672e08db85aa990309793bb39d8976207abb7","author":{"email":"ef65de1c7be0aa837fe7b25ba9a7739905af6a55@gondor.apana.org.au","name":"Herbert Xu"},"message":"macvtap: Fix csum_start when VLAN tags are present\n\ncommit 3ce9b20f1971690b8b3b620e735ec99431573b39 upstream.\n\nWhen VLAN is in use in macvtap_put_user, we end up setting\ncsum_start to the wrong place.  The result is that the whoever\nends up doing the checksum setting will corrupt the packet instead\nof writing the checksum to the expected location, usually this\nmeans writing the checksum with an offset of -4.\n\nThis patch fixes this by adjusting csum_start when VLAN tags are\ndetected.\n\nFixes: f09e2249c4f5 (\"macvtap: restore vlan header on user read\")\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/HridayHS/Lightning-Tomato/commits/e52672e08db85aa990309793bb39d8976207abb7"},{"sha":"ae2a916c77854c4e2331344ab23a906a61cff5d2","author":{"email":"bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com","name":"Johannes Berg"},"message":"mac80211: fix use-after-free in defragmentation\n\ncommit b8fff407a180286aa683d543d878d98d9fc57b13 upstream.\n\nUpon receiving the last fragment, all but the first fragment\nare freed, but the multicast check for statistics at the end\nof the function refers to the current skb (the last fragment)\ncausing a use-after-free bug.\n\nSince multicast frames cannot be fragmented and we check for\nthis early in the function, just modify that check to also\ndo the accounting to fix the issue.\n\nReported-by: Yosef Khyal <yosefx.khyal@intel.com>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\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/HridayHS/Lightning-Tomato/commits/ae2a916c77854c4e2331344ab23a906a61cff5d2"},{"sha":"1ff6b0f29d60c0c0ab86d8ab93271a684218864c","author":{"email":"08dc22c6156113f2deff178e35e3ed9b24d6af9e@amd.com","name":"Alex Deucher"},"message":"drm/radeon: add missing crtc unlock when setting up the MC\n\ncommit f0d7bfb9407fccb6499ec01c33afe43512a439a2 upstream.\n\nNeed to unlock the crtc after updating the blanking state.\n\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\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/HridayHS/Lightning-Tomato/commits/1ff6b0f29d60c0c0ab86d8ab93271a684218864c"},{"sha":"e2d4eb9815db66e2ef4e0ff3767c6667cc56c27d","author":{"email":"f9463caf95f5a4c66cfb5519ed3d1d413440e4f4@mentor.com","name":"Nathan Lynch"},"message":"ARM: 8198/1: make kuser helpers depend on MMU\n\ncommit 08b964ff3c51b10aaf2e6ba639f40054c09f0f7a upstream.\n\nThe kuser helpers page is not set up on non-MMU systems, so it does\nnot make sense to allow CONFIG_KUSER_HELPERS to be enabled when\nCONFIG_MMU=n.  Allowing it to be set on !MMU results in an oops in\nset_tls (used in execve and the arm_syscall trap handler):\n\nUnhandled exception: IPSR = 00000005 LR = fffffff1\nCPU: 0 PID: 1 Comm: swapper Not tainted 3.18.0-rc1-00041-ga30465a #216\ntask: 8b838000 ti: 8b82a000 task.ti: 8b82a000\nPC is at flush_thread+0x32/0x40\nLR is at flush_thread+0x21/0x40\npc : [<8f00157a>]    lr : [<8f001569>]    psr: 4100000b\nsp : 8b82be20  ip : 00000000  fp : 8b83c000\nr10: 00000001  r9 : 88018c84  r8 : 8bb85000\nr7 : 8b838000  r6 : 00000000  r5 : 8bb77400  r4 : 8b82a000\nr3 : ffff0ff0  r2 : 8b82a000  r1 : 00000000  r0 : 88020354\nxPSR: 4100000b\nCPU: 0 PID: 1 Comm: swapper Not tainted 3.18.0-rc1-00041-ga30465a #216\n[<8f002bc1>] (unwind_backtrace) from [<8f002033>] (show_stack+0xb/0xc)\n[<8f002033>] (show_stack) from [<8f00265b>] (__invalid_entry+0x4b/0x4c)\n\nAs best I can tell this issue existed for the set_tls ARM syscall\nbefore commit fbfb872f5f41 \"ARM: 8148/1: flush TLS and thumbee\nregister state during exec\" consolidated the TLS manipulation code\ninto the set_tls helper function, but now that we're using it to flush\nregister state during execve, !MMU users encounter the oops at the\nfirst exec.\n\nPrevent CONFIG_MMU=n configurations from enabling\nCONFIG_KUSER_HELPERS.\n\nFixes: fbfb872f5f41 (ARM: 8148/1: flush TLS and thumbee register state during exec)\n\nSigned-off-by: Nathan Lynch <nathan_lynch@mentor.com>\nReported-by: Stefan Agner <stefan@agner.ch>\nAcked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\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/HridayHS/Lightning-Tomato/commits/e2d4eb9815db66e2ef4e0ff3767c6667cc56c27d"},{"sha":"1685e56ea5427cd29d2fbc73a133e2aefc173a2b","author":{"email":"3c25b01657254677d3e1a8fd1f0742c5d489bd39@redhat.com","name":"Kyle McMartin"},"message":"arm64: __clear_user: handle exceptions on strb\n\ncommit 97fc15436b36ee3956efad83e22a557991f7d19d upstream.\n\nARM64 currently doesn't fix up faults on the single-byte (strb) case of\n__clear_user... which means that we can cause a nasty kernel panic as an\nordinary user with any multiple PAGE_SIZE+1 read from /dev/zero.\ni.e.: dd if=/dev/zero of=foo ibs=1 count=1 (or ibs=65537, etc.)\n\nThis is a pretty obscure bug in the general case since we'll only\n__do_kernel_fault (since there's no extable entry for pc) if the\nmmap_sem is contended. However, with CONFIG_DEBUG_VM enabled, we'll\nalways fault.\n\nif (!down_read_trylock(&mm->mmap_sem)) {\n\tif (!user_mode(regs) && !search_exception_tables(regs->pc))\n\t\tgoto no_context;\nretry:\n\tdown_read(&mm->mmap_sem);\n} else {\n\t/*\n\t * The above down_read_trylock() might have succeeded in\n\t * which\n\t * case, we'll have missed the might_sleep() from\n\t * down_read().\n\t */\n\tmight_sleep();\n\tif (!user_mode(regs) && !search_exception_tables(regs->pc))\n\t\tgoto no_context;\n}\n\nFix that by adding an extable entry for the strb instruction, since it\ntouches user memory, similar to the other stores in __clear_user.\n\nSigned-off-by: Kyle McMartin <kyle@redhat.com>\nReported-by: Miloš Prchlík <mprchlik@redhat.com>\nSigned-off-by: Catalin Marinas <catalin.marinas@arm.com>\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/HridayHS/Lightning-Tomato/commits/1685e56ea5427cd29d2fbc73a133e2aefc173a2b"},{"sha":"4c67baa724a80610c6783bc0cc4cb1554028771a","author":{"email":"fbd796546fc801b34e01e453c6fd30283e012038@s5r6.in-berlin.de","name":"Stefan Richter"},"message":"firewire: cdev: prevent kernel stack leaking into ioctl arguments\n\ncommit eaca2d8e75e90a70a63a6695c9f61932609db212 upstream.\n\nFound by the UC-KLEE tool:  A user could supply less input to\nfirewire-cdev ioctls than write- or write/read-type ioctl handlers\nexpect.  The handlers used data from uninitialized kernel stack then.\n\nThis could partially leak back to the user if the kernel subsequently\ngenerated fw_cdev_event_'s (to be read from the firewire-cdev fd)\nwhich notably would contain the _u64 closure field which many of the\nioctl argument structures contain.\n\nThe fact that the handlers would act on random garbage input is a\nlesser issue since all handlers must check their input anyway.\n\nThe fix simply always null-initializes the entire ioctl argument buffer\nregardless of the actual length of expected user input.  That is, a\nruntime overhead of memset(..., 40) is added to each firewirew-cdev\nioctl() call.  [Comment from Clemens Ladisch:  This part of the stack is\nmost likely to be already in the cache.]\n\nRemarks:\n  - There was never any leak from kernel stack to the ioctl output\n    buffer itself.  IOW, it was not possible to read kernel stack by a\n    read-type or write/read-type ioctl alone; the leak could at most\n    happen in combination with read()ing subsequent event data.\n  - The actual expected minimum user input of each ioctl from\n    include/uapi/linux/firewire-cdev.h is, in bytes:\n    [0x00] = 32, [0x05] =  4, [0x0a] = 16, [0x0f] = 20, [0x14] = 16,\n    [0x01] = 36, [0x06] = 20, [0x0b] =  4, [0x10] = 20, [0x15] = 20,\n    [0x02] = 20, [0x07] =  4, [0x0c] =  0, [0x11] =  0, [0x16] =  8,\n    [0x03] =  4, [0x08] = 24, [0x0d] = 20, [0x12] = 36, [0x17] = 12,\n    [0x04] = 20, [0x09] = 24, [0x0e] =  4, [0x13] = 40, [0x18] =  4.\n\nReported-by: David Ramos <daramos@stanford.edu>\nSigned-off-by: Stefan Richter <stefanr@s5r6.in-berlin.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/HridayHS/Lightning-Tomato/commits/4c67baa724a80610c6783bc0cc4cb1554028771a"},{"sha":"afa8b97a533dde5bfaf5d1f6495b4f0ffa9c6850","author":{"email":"4fb2b5cc20694ed9d470f738b651303a1e636b2d@primarydata.com","name":"Peng Tao"},"message":"nfs: fix pnfs direct write memory leak\n\ncommit 8c393f9a721c30a030049a680e1bf896669bb279 upstream.\n\nFor pNFS direct writes, layout driver may dynamically allocate ds_cinfo.buckets.\nSo we need to take care to free them when freeing dreq.\n\nIdeally this needs to be done inside layout driver where ds_cinfo.buckets\nare allocated. But buckets are attached to dreq and reused across LD IO iterations.\nSo I feel it's OK to free them in the generic layer.\n\nSigned-off-by: Peng Tao <tao.peng@primarydata.com>\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\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/HridayHS/Lightning-Tomato/commits/afa8b97a533dde5bfaf5d1f6495b4f0ffa9c6850"},{"sha":"0b96a7a5a239d32353467fbef305358ee88d828d","author":{"email":"923f7720577207a44b32e59bbfbea59d27f1ae8e@lst.de","name":"Christoph Hellwig"},"message":"scsi: only re-lock door after EH on devices that were reset\n\ncommit 48379270fe6808cf4612ee094adc8da2b7a83baa upstream.\n\nSetups that use the blk-mq I/O path can lock up if a host with a single\ndevice that has its door locked enters EH.  Make sure to only send the\ncommand to re-lock the door to devices that actually were reset and thus\nmight have lost their state.  Otherwise the EH code might be get blocked\non blk_get_request as all requests for non-reset devices might be in use.\n\nSigned-off-by: Christoph Hellwig <hch@lst.de>\nReported-by: Meelis Roos <meelis.roos@ut.ee>\nTested-by: Meelis Roos <meelis.roos@ut.ee>\nReviewed-by: Martin K. Petersen <martin.petersen@oracle.com>\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/HridayHS/Lightning-Tomato/commits/0b96a7a5a239d32353467fbef305358ee88d828d"},{"sha":"d2f81eb6a634123d42cfdf31b7a19a860eecd09a","author":{"email":"5b1e7895819cf7d6bc77091b09bbfd6d330a4e74@gmx.de","name":"Helge Deller"},"message":"parisc: Use compat layer for msgctl, shmat, shmctl and semtimedop syscalls\n\ncommit 2fe749f50b0bec07650ef135b29b1f55bf543869 upstream.\n\nSwitch over the msgctl, shmat, shmctl and semtimedop syscalls to use the compat\nlayer. The problem was found with the debian procenv package, which called\n\tshmctl(0, SHM_INFO, &info);\nin which the shmctl syscall then overwrote parts of the surrounding areas on\nthe stack on which the info variable was stored and thus lead to a segfault\nlater on.\n\nAdditionally fix the definition of struct shminfo64 to use unsigned longs like\nthe other architectures. This has no impact on userspace since we only have a\n32bit userspace up to now.\n\nSigned-off-by: Helge Deller <deller@gmx.de>\nCc: John David Anglin <dave.anglin@bell.net>\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/HridayHS/Lightning-Tomato/commits/d2f81eb6a634123d42cfdf31b7a19a860eecd09a"},{"sha":"983caa8c730446e565f0cab373d31509e7074ba4","author":{"email":"596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz","name":"Jan Kara"},"message":"block: Fix computation of merged request priority\n\ncommit ece9c72accdc45c3a9484dacb1125ce572647288 upstream.\n\nPriority of a merged request is computed by ioprio_best(). If one of the\nrequests has undefined priority (IOPRIO_CLASS_NONE) and another request\nhas priority from IOPRIO_CLASS_BE, the function will return the\nundefined priority which is wrong. Fix the function to properly return\npriority of a request with the defined priority.\n\nFixes: d58cdfb89ce0c6bd5f81ae931a984ef298dbda20\nSigned-off-by: Jan Kara <jack@suse.cz>\nReviewed-by: Jeff Moyer <jmoyer@redhat.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>\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/HridayHS/Lightning-Tomato/commits/983caa8c730446e565f0cab373d31509e7074ba4"},{"sha":"23ef3f33f5bd2a7e6535d9b41df7a563761c3936","author":{"email":"61d5fad70554ae22d57a37634e04f12f58acc678@redhat.com","name":"Joe Thornber"},"message":"dm btree: fix a recursion depth bug in btree walking code\n\ncommit 9b460d3699324d570a4d4161c3741431887f102f upstream.\n\nThe walk code was using a 'ro_spine' to hold it's locked btree nodes.\nBut this data structure is designed for the rolling lock scheme, and\nas such automatically unlocks blocks that are two steps up the call\nchain.  This is not suitable for the simple recursive walk algorithm,\nwhich retraces its steps.\n\nThis code is only used by the persistent array code, which in turn is\nonly used by dm-cache.  In order to trigger it you need to have a\nmapping tree that is more than 2 levels deep; which equates to 8-16\nmillion cache blocks.  For instance a 4T ssd with a very small block\nsize of 32k only just triggers this bug.\n\nThe fix just places the locked blocks on the stack, and stops using\nthe ro_spine altogether.\n\nSigned-off-by: Joe Thornber <ejt@redhat.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\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/HridayHS/Lightning-Tomato/commits/23ef3f33f5bd2a7e6535d9b41df7a563761c3936"},{"sha":"6f31442d927a0e46b7b1731bf9ef0fcba9e18456","author":{"email":"4beca5398d608e62d2566fc23741b57e67f35e89@redhat.com","name":"Heinz Mauelshagen"},"message":"dm raid: ensure superblock's size matches device's logical block size\n\ncommit 40d43c4b4cac4c2647bf07110d7b07d35f399a84 upstream.\n\nThe dm-raid superblock (struct dm_raid_superblock) is padded to 512\nbytes and that size is being used to read it in from the metadata\ndevice into one preallocated page.\n\nReading or writing this on a 512-byte sector device works fine but on\na 4096-byte sector device this fails.\n\nSet the dm-raid superblock's size to the logical block size of the\nmetadata device, because IO at that size is guaranteed too work.  Also\nadd a size check to avoid silent partial metadata loss in case the\nsuperblock should ever grow past the logical block size or PAGE_SIZE.\n\n[includes pointer math fix from Dan Carpenter]\nReported-by: \"Liuhua Wang\" <lwang@suse.com>\nSigned-off-by: Heinz Mauelshagen <heinzm@redhat.com>\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\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/HridayHS/Lightning-Tomato/commits/6f31442d927a0e46b7b1731bf9ef0fcba9e18456"},{"sha":"1538d543d75606f1f32c6b83f1c9998f357352b3","author":{"email":"271b10744f2b592adf8fde144d536c86b011b93c@gmail.com","name":"Pali Rohár"},"message":"Input: alps - ignore potential bare packets when device is out of sync\n\ncommit 4ab8f7f320f91f279c3f06a9795cfea5c972888a upstream.\n\n5th and 6th byte of ALPS trackstick V3 protocol match condition for first\nbyte of PS/2 3 bytes packet. When driver enters out of sync state and ALPS\ntrackstick is sending data then driver match 5th, 6th and next 1st bytes as\nPS/2.\n\nIt basically means if user is using trackstick when driver is in out of\nsync state driver will never resync. Processing these bytes as 3 bytes PS/2\ndata cause total mess (random cursor movements, random clicks) and make\ntrackstick unusable until psmouse driver decide to do full device reset.\n\nLot of users reported problems with ALPS devices on Dell Latitude E6440,\nE6540 and E7440 laptops. ALPS device or Dell EC for unknown reason send\nsome invalid ALPS PS/2 bytes which cause driver out of sync. It looks like\nthat i8042 and psmouse/alps driver always receive group of 6 bytes packets\nso there are no missing bytes and no bytes were inserted between valid\nones.\n\nThis patch does not fix root of problem with ALPS devices found in Dell\nLatitude laptops but it does not allow to process some (invalid)\nsubsequence of 6 bytes ALPS packets as 3 bytes PS/2 when driver is out of\nsync.\n\nSo with this patch trackstick input device does not report bogus data when\nalso driver is out of sync, so trackstick should be usable on those\nmachines.\n\nSigned-off-by: Pali Rohár <pali.rohar@gmail.com>\nTested-by: Pali Rohár <pali.rohar@gmail.com>\nReviewed-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\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/HridayHS/Lightning-Tomato/commits/1538d543d75606f1f32c6b83f1c9998f357352b3"},{"sha":"43a352e899349c11b407ac84dbaf4d1ba78d89e7","author":{"email":"271b10744f2b592adf8fde144d536c86b011b93c@gmail.com","name":"Pali Rohár"},"message":"Input: alps - allow up to 2 invalid packets without resetting device\n\ncommit 9d720b34c0a432639252f63012e18b0507f5b432 upstream.\n\nOn some Dell Latitude laptops ALPS device or Dell EC send one invalid byte\nin 6 bytes ALPS packet. In this case psmouse driver enter out of sync\nstate. It looks like that all other bytes in packets are valid and also\ndevice working properly. So there is no need to do full device reset, just\nneed to wait for byte which match condition for first byte (start of\npacket). Because ALPS packets are bigger (6 or 8 bytes) default limit is\nsmall.\n\nThis patch increase number of invalid bytes to size of 2 ALPS packets which\npsmouse driver can drop before do full reset.\n\nResetting ALPS devices take some time and when doing reset on some Dell\nlaptops touchpad, trackstick and also keyboard do not respond. So it is\nbetter to do it only if really necessary.\n\nSigned-off-by: Pali Rohár <pali.rohar@gmail.com>\nTested-by: Pali Rohár <pali.rohar@gmail.com>\nReviewed-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\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/HridayHS/Lightning-Tomato/commits/43a352e899349c11b407ac84dbaf4d1ba78d89e7"},{"sha":"dc613cf1fc59fe5e1f52590e720ed7a5947a7e19","author":{"email":"cc958843532c615cbd4920e868f78c7985331a5a@primarydata.com","name":"Trond Myklebust"},"message":"NFSv4: Ensure that we remove NFSv4.0 delegations when state has expired\n\ncommit 4dfd4f7af0afd201706ad186352ca423b0f17d4b upstream.\n\nNFSv4.0 does not have TEST_STATEID/FREE_STATEID functionality, so\nunlike NFSv4.1, the recovery procedure when stateids have expired or\nhave been revoked requires us to just forget the delegation.\n\nhttp://lkml.kernel.org/r/CAN-5tyHwG=Cn2Q9KsHWadewjpTTy_K26ee+UnSvHvG4192p-Xw@mail.gmail.com\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\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/HridayHS/Lightning-Tomato/commits/dc613cf1fc59fe5e1f52590e720ed7a5947a7e19"}]}