{"push_id":3076730459,"size":257,"distinct_size":257,"ref":"refs/heads/rebase","head":"6d1a87d1bb6dc32bed3ed467480dbd8ceeeb0d52","before":"dc18babc17356091bc5910dcea6bf82bb73b92fc","commits":[{"sha":"322e659a03dcec9e19a2bbd116ee8f1c978a7030","author":{"name":"Coly Li","email":"f873d2e1ca1a16c3419d71461d4bbaa0a7678f5d@suse.de"},"message":"bcache: only permit to recovery read error when cache device is clean\n\ncommit d59b23795933678c9638fd20c942d2b4f3cd6185 upstream.\n\nWhen bcache does read I/Os, for example in writeback or writethrough mode,\nif a read request on cache device is failed, bcache will try to recovery\nthe request by reading from cached device. If the data on cached device is\nnot synced with cache device, then requester will get a stale data.\n\nFor critical storage system like database, providing stale data from\nrecovery may result an application level data corruption, which is\nunacceptible.\n\nWith this patch, for a failed read request in writeback or writethrough\nmode, recovery a recoverable read request only happens when cache device\nis clean. That is to say, all data on cached device is up to update.\n\nFor other cache modes in bcache, read request will never hit\ncached_dev_read_error(), they don't need this patch.\n\nPlease note, because cache mode can be switched arbitrarily in run time, a\nwritethrough mode might be switched from a writeback mode. Therefore\nchecking dc->has_data in writethrough mode still makes sense.\n\nChangelog:\nV4: Fix parens error pointed by Michael Lyle.\nv3: By response from Kent Oversteet, he thinks recovering stale data is a\n    bug to fix, and option to permit it is unnecessary. So this version\n    the sysfs file is removed.\nv2: rename sysfs entry from allow_stale_data_on_failure  to\n    allow_stale_data_on_failure, and fix the confusing commit log.\nv1: initial patch posted.\n\n[small change to patch comment spelling by mlyle]\n\nSigned-off-by: Coly Li <colyli@suse.de>\nSigned-off-by: Michael Lyle <mlyle@lyle.org>\nReported-by: Arne Wolf <awolf@lenovo.com>\nReviewed-by: Michael Lyle <mlyle@lyle.org>\nCc: Kent Overstreet <kent.overstreet@gmail.com>\nCc: Nix <nix@esperi.org.uk>\nCc: Kai Krakow <hurikhan77@gmail.com>\nCc: Eric Wheeler <bcache@lists.ewheeler.net>\nCc: Junhui Tang <tang.junhui@zte.com.cn>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/322e659a03dcec9e19a2bbd116ee8f1c978a7030"},{"sha":"9db9b5f2b1b691c78b239a71a4b6a8d950323a78","author":{"name":"Rui Hua","email":"6e250aeff645a3baea6dac1972db4ba4a9a296ac@gmail.com"},"message":"bcache: recover data from backing when data is clean\n\ncommit e393aa2446150536929140739f09c6ecbcbea7f0 upstream.\n\nWhen we send a read request and hit the clean data in cache device, there\nis a situation called cache read race in bcache(see the commit in the tail\nof cache_look_up(), the following explaination just copy from there):\nThe bucket we're reading from might be reused while our bio is in flight,\nand we could then end up reading the wrong data. We guard against this\nby checking (in bch_cache_read_endio()) if the pointer is stale again;\nif so, we treat it as an error (s->iop.error = -EINTR) and reread from\nthe backing device (but we don't pass that error up anywhere)\n\nIt should be noted that cache read race happened under normal\ncircumstances, not the circumstance when SSD failed, it was counted\nand shown in  /sys/fs/bcache/XXX/internal/cache_read_races.\n\nWithout this patch, when we use writeback mode, we will never reread from\nthe backing device when cache read race happened, until the whole cache\ndevice is clean, because the condition\n(s->recoverable && (dc && !atomic_read(&dc->has_dirty))) is false in\ncached_dev_read_error(). In this situation, the s->iop.error(= -EINTR)\nwill be passed up, at last, user will receive -EINTR when it's bio end,\nthis is not suitable, and wield to up-application.\n\nIn this patch, we use s->read_dirty_data to judge whether the read\nrequest hit dirty data in cache device, it is safe to reread data from\nthe backing device when the read request hit clean data. This can not\nonly handle cache read race, but also recover data when failed read\nrequest from cache device.\n\n[edited by mlyle to fix up whitespace, commit log title, comment\nspelling]\n\nFixes: d59b23795933 (\"bcache: only permit to recovery read error when cache device is clean\")\nSigned-off-by: Hua Rui <huarui.dev@gmail.com>\nReviewed-by: Michael Lyle <mlyle@lyle.org>\nReviewed-by: Coly Li <colyli@suse.de>\nSigned-off-by: Michael Lyle <mlyle@lyle.org>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/9db9b5f2b1b691c78b239a71a4b6a8d950323a78"},{"sha":"48f4d1f7fe48627a4c5c9332bcdf0f2a906e2f20","author":{"name":"Stefan Agner","email":"eb0877843acc39f8ef6f7269937dee931c372d23@agner.ch"},"message":"drm/fsl-dcu: avoid disabling pixel clock twice on suspend\n\ncommit 9306e996574f7f57136a62e49cd0075f85713623 upstream.\n\nWith commit 0a70c998d0c5 (\"drm/fsl-dcu: enable pixel clock when\nenabling CRTC\") the pixel clock is controlled by the CRTC code.\nDisabling the pixel clock in suspend leads to a warning due to\nthe second clk_disable_unprepare call:\n  WARNING: CPU: 0 PID: 359 at drivers/clk/clk.c:594 clk_core_disable+0x8c/0x90\n\nRemove clk_disable_unprepare call for pixel clock to avoid\nunbalanced clock disable on suspend.\n\nFixes: 0a70c998d0c5 (\"drm/fsl-dcu: enable pixel clock when enabling CRTC\")\nSigned-off-by: Stefan Agner <stefan@agner.ch>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/48f4d1f7fe48627a4c5c9332bcdf0f2a906e2f20"},{"sha":"cffc01d24d2591cd2184c13fba32f50abfd20e68","author":{"name":"Stefan Agner","email":"eb0877843acc39f8ef6f7269937dee931c372d23@agner.ch"},"message":"drm/fsl-dcu: enable IRQ before drm_atomic_helper_resume()\n\ncommit 9fd99f4f3f5e13ce959900ae57d64b1bdb51d823 upstream.\n\nThe resume helpers wait for a vblank to occurre hence IRQ need\nto be enabled. This avoids a warning as follows during resume:\n  WARNING: CPU: 0 PID: 314 at drivers/gpu/drm/drm_atomic_helper.c:1249 drm_atomic_helper_wait_for_vblanks.part.1+0x284/0x288\n  [CRTC:28:crtc-0] vblank wait timed out\n\nSigned-off-by: Stefan Agner <stefan@agner.ch>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/cffc01d24d2591cd2184c13fba32f50abfd20e68"},{"sha":"0de12a778b923807017d133ba5c0ef2d2a8444e1","author":{"name":"Horia Geantă","email":"6135224f23789828bd8d3b771a2745286516a2b5@nxp.com"},"message":"Revert \"crypto: caam - get rid of tasklet\"\n\ncommit 2b163b5bce04546da72617bfb6c8bf07a45c4b17 upstream.\n\nThis reverts commit 66d2e2028091a074aa1290d2eeda5ddb1a6c329c.\n\nQuoting from Russell's findings:\nhttps://www.mail-archive.com/linux-crypto@vger.kernel.org/msg21136.html\n\n[quote]\nOkay, I've re-tested, using a different way of measuring, because using\nopenssl speed is impractical for off-loaded engines.  I've decided to\nuse this way to measure the performance:\n\ndd if=/dev/zero bs=1048576 count=128 | /usr/bin/time openssl dgst -md5\n\nFor the threaded IRQs case gives:\n\n0.05user 2.74system 0:05.30elapsed 52%CPU (0avgtext+0avgdata 2400maxresident)k\n0.06user 2.52system 0:05.18elapsed 49%CPU (0avgtext+0avgdata 2404maxresident)k\n0.12user 2.60system 0:05.61elapsed 48%CPU (0avgtext+0avgdata 2460maxresident)k\n\t=> 5.36s => 25.0MB/s\n\nand the tasklet case:\n\n0.08user 2.53system 0:04.83elapsed 54%CPU (0avgtext+0avgdata 2468maxresident)k\n0.09user 2.47system 0:05.16elapsed 49%CPU (0avgtext+0avgdata 2368maxresident)k\n0.10user 2.51system 0:04.87elapsed 53%CPU (0avgtext+0avgdata 2460maxresident)k\n\t=> 4.95 => 27.1MB/s\n\nwhich corresponds to an 8% slowdown for the threaded IRQ case.  So,\ntasklets are indeed faster than threaded IRQs.\n\n[...]\n\nI think I've proven from the above that this patch needs to be reverted\ndue to the performance regression, and that there _is_ most definitely\na deterimental effect of switching from tasklets to threaded IRQs.\n[/quote]\n\nSigned-off-by: Horia Geantă <horia.geanta@nxp.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/0de12a778b923807017d133ba5c0ef2d2a8444e1"},{"sha":"ee23ae915fa74956503507c1e55cbb2102f349ec","author":{"name":"Wang Nan","email":"7b589a40e0ecd4816b422e8ed1f74a01c34bf6bb@huawei.com"},"message":"mm, oom_reaper: gather each vma to prevent leaking TLB entry\n\ncommit 687cb0884a714ff484d038e9190edc874edcf146 upstream.\n\ntlb_gather_mmu(&tlb, mm, 0, -1) means gathering the whole virtual memory\nspace.  In this case, tlb->fullmm is true.  Some archs like arm64\ndoesn't flush TLB when tlb->fullmm is true:\n\n  commit 5a7862e83000 (\"arm64: tlbflush: avoid flushing when fullmm == 1\").\n\nWhich causes leaking of tlb entries.\n\nWill clarifies his patch:\n \"Basically, we tag each address space with an ASID (PCID on x86) which\n  is resident in the TLB. This means we can elide TLB invalidation when\n  pulling down a full mm because we won't ever assign that ASID to\n  another mm without doing TLB invalidation elsewhere (which actually\n  just nukes the whole TLB).\n\n  I think that means that we could potentially not fault on a kernel\n  uaccess, because we could hit in the TLB\"\n\nThere could be a window between complete_signal() sending IPI to other\ncores and all threads sharing this mm are really kicked off from cores.\nIn this window, the oom reaper may calls tlb_flush_mmu_tlbonly() to\nflush TLB then frees pages.  However, due to the above problem, the TLB\nentries are not really flushed on arm64.  Other threads are possible to\naccess these pages through TLB entries.  Moreover, a copy_to_user() can\nalso write to these pages without generating page fault, causes\nuse-after-free bugs.\n\nThis patch gathers each vma instead of gathering full vm space.  In this\ncase tlb->fullmm is not true.  The behavior of oom reaper become similar\nto munmapping before do_exit, which should be safe for all archs.\n\nLink: http://lkml.kernel.org/r/20171107095453.179940-1-wangnan0@huawei.com\nFixes: aac453635549 (\"mm, oom: introduce oom reaper\")\nSigned-off-by: Wang Nan <wangnan0@huawei.com>\nAcked-by: Michal Hocko <mhocko@suse.com>\nAcked-by: David Rientjes <rientjes@google.com>\nCc: Minchan Kim <minchan@kernel.org>\nCc: Will Deacon <will.deacon@arm.com>\nCc: Bob Liu <liubo95@huawei.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Roman Gushchin <guro@fb.com>\nCc: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>\nCc: Andrea Arcangeli <aarcange@redhat.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n[backported to 4.9 stable tree]\nSigned-off-by: Michal Hocko <mhocko@suse.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/ee23ae915fa74956503507c1e55cbb2102f349ec"},{"sha":"3789201628f5b2d58289682bc38f7a601807e2b3","author":{"name":"Hans de Goede","email":"9fa1be1a5b5729e4c6b404f34c9ce49ff4882fd8@redhat.com"},"message":"uas: Always apply US_FL_NO_ATA_1X quirk to Seagate devices\n\ncommit 7fee72d5e8f1e7b8d8212e28291b1a0243ecf2f1 upstream.\n\nWe've been adding this as a quirk on a per device basis hoping that\nnewer disk enclosures would do better, but that has not happened,\nso simply apply this quirk to all Seagate devices.\n\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/3789201628f5b2d58289682bc38f7a601807e2b3"},{"sha":"6ad14c9c646b6d8accb48e8bbcfb201506a9884b","author":{"name":"Kai-Heng Feng","email":"06af28c154da900e58fef391e9e9415561e1d8ae@canonical.com"},"message":"usb: quirks: Add no-lpm quirk for KY-688 USB 3.1 Type-C Hub\n\ncommit e43a12f1793ae1fe006e26fe9327a8840a92233c upstream.\n\nKY-688 USB 3.1 Type-C Hub internally uses a Genesys Logic hub to connect\nto Realtek r8153.\n\nSimilar to commit (\"7496cfe5431f2 usb: quirks: Add no-lpm quirk for Moshi\nUSB to Ethernet Adapter\"), no-lpm can make r8153 ethernet work.\n\nSigned-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/6ad14c9c646b6d8accb48e8bbcfb201506a9884b"},{"sha":"65e6599937d1006a278d29d4b8e742759947ac8f","author":{"name":"Matt Wilson","email":"260f5074942ca36dab941199ff6b19fcaa26ccde@amazon.com"},"message":"serial: 8250_pci: Add Amazon PCI serial device ID\n\ncommit 3bfd1300abfe3adb18e84a89d97a0e82a22124bb upstream.\n\nThis device will be used in future Amazon EC2 instances as the primary\nserial port (i.e., data sent to this port will be available via the\nGetConsoleOuput [1] EC2 API).\n\n[1] http://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_GetConsoleOutput.html\n\nSigned-off-by: Matt Wilson <msw@amazon.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/65e6599937d1006a278d29d4b8e742759947ac8f"},{"sha":"232b47b3c88af1da737cd7760f247c4ed58168cf","author":{"name":"Heiko Carstens","email":"8dcf0f69152f32f23184f83357a3731522e56b9c@de.ibm.com"},"message":"s390/runtime instrumentation: simplify task exit handling\n\ncommit 8d9047f8b967ce6181fd824ae922978e1b055cc0 upstream.\n\nFree data structures required for runtime instrumentation from\narch_release_task_struct(). This allows to simplify the code a bit,\nand also makes the semantics a bit easier: arch_release_task_struct()\nis never called from the task that is being removed.\n\nIn addition this allows to get rid of exit_thread() in a later patch.\n\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/232b47b3c88af1da737cd7760f247c4ed58168cf"},{"sha":"e4f12192d9e2fae46661b4be364c3ec375d3d7c3","author":{"name":"Sebastian Sjoholm","email":"aac873ae2904de23fbb43c9a37dec75d4de04dc3@mac.com"},"message":"USB: serial: option: add Quectel BG96 id\n\ncommit c654b21ede93845863597de9ad774fd30db5f2ab upstream.\n\nQuectel BG96 is an Qualcomm MDM9206 based IoT modem, supporting both\nCAT-M and NB-IoT. Tested hardware is BG96 mounted on Quectel\ndevelopment board (EVB). The USB id is added to option.c to allow\nDIAG,GPS,AT and modem communication with the BG96.\n\nSigned-off-by: Sebastian Sjoholm <ssjoholm@mac.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/e4f12192d9e2fae46661b4be364c3ec375d3d7c3"},{"sha":"b0a46089fe818d33b42fc7c399239db5e4f7bfcf","author":{"name":"Boshi Wang","email":"67b5db99f272c4f8d58d3886024a9ca277231bf2@huawei.com"},"message":"ima: fix hash algorithm initialization\n\n\n[ Upstream commit ebe7c0a7be92bbd34c6ff5b55810546a0ee05bee ]\n\nThe hash_setup function always sets the hash_setup_done flag, even\nwhen the hash algorithm is invalid.  This prevents the default hash\nalgorithm defined as CONFIG_IMA_DEFAULT_HASH from being used.\n\nThis patch sets hash_setup_done flag only for valid hash algorithms.\n\nFixes: e7a2ad7eb6f4 \"ima: enable support for larger default filedata hash algorithms\"\nSigned-off-by: Boshi Wang <wangboshi@huawei.com>\nSigned-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/b0a46089fe818d33b42fc7c399239db5e4f7bfcf"},{"sha":"63074a793d69d9fd56e1456d598f4df9d35d9b70","author":{"name":"Christian Borntraeger","email":"49712f635b03c16d7f4c43df70e49ec8c565813d@de.ibm.com"},"message":"s390/pci: do not require AIS facility\n\n\n[ Upstream commit 48070c73058be6de9c0d754d441ed7092dfc8f12 ]\n\nAs of today QEMU does not provide the AIS facility to its guest.  This\nprevents Linux guests from using PCI devices as the ais facility is\nchecked during init. As this is just a performance optimization, we can\nmove the ais check into the code where we need it (calling the SIC\ninstruction). This is used at initialization and on interrupt. Both\nplaces do not require any serialization, so we can simply skip the\ninstruction.\n\nSince we will now get all interrupts, we can also avoid the 2nd scan.\nAs we can have multiple interrupts in parallel we might trigger spurious\nirqs more often for the non-AIS case but the core code can handle that.\n\nSigned-off-by: Christian Borntraeger <borntraeger@de.ibm.com>\nReviewed-by: Pierre Morel <pmorel@linux.vnet.ibm.com>\nReviewed-by: Halil Pasic <pasic@linux.vnet.ibm.com>\nAcked-by: Sebastian Ott <sebott@linux.vnet.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/63074a793d69d9fd56e1456d598f4df9d35d9b70"},{"sha":"8a95afc485767641f712a46086b858e4c7ae2996","author":{"name":"Andy Lutomirski","email":"2cc0d0d76de2e6f37b92deeb83c85cb306fc5dc1@kernel.org"},"message":"selftests/x86/ldt_get: Add a few additional tests for limits\n\n\n[ Upstream commit fec8f5ae1715a01c72ad52cb2ecd8aacaf142302 ]\n\nWe weren't testing the .limit and .limit_in_pages fields very well.\nAdd more tests.\n\nThis addition seems to trigger the \"bits 16:19 are undefined\" issue\nthat was fixed in an earlier patch.  I think that, at least on my\nCPU, the high nibble of the limit ends in LAR bits 16:19.\n\nSigned-off-by: Andy Lutomirski <luto@kernel.org>\nCc: Borislav Petkov <bpetkov@suse.de>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nLink: http://lkml.kernel.org/r/5601c15ea9b3113d288953fd2838b18bedf6bc67.1509794321.git.luto@kernel.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/8a95afc485767641f712a46086b858e4c7ae2996"},{"sha":"e5f2421df13523e46697d453575c020af57c945b","author":{"name":"Bryan O'Donoghue","email":"6179ee6cf56d4b668e54a2bb639ce0732423754e@nexus-software.ie"},"message":"staging: greybus: loopback: Fix iteration count on async path\n\n\n[ Upstream commit 44b02da39210e6dd67e39ff1f48d30c56d384240 ]\n\nCommit 12927835d211 (\"greybus: loopback: Add asynchronous bi-directional\nsupport\") does what it says on the tin - namely, adds support for\nasynchronous bi-directional loopback operations.\n\nWhat it neglects to do though is increment the per-connection\ngb->iteration_count on an asynchronous operation error. This patch fixes\nthat omission.\n\nFixes: 12927835d211 (\"greybus: loopback: Add asynchronous bi-directional support\")\n\nSigned-off-by: Bryan O'Donoghue <pure.logic@nexus-software.ie>\nReported-by: Mitch Tasman <tasman@leaflabs.com>\nReviewed-by: Johan Hovold <johan@kernel.org>\nCc: Alex Elder <elder@kernel.org>\nCc: Mitch Tasman <tasman@leaflabs.com>\nCc: greybus-dev@lists.linaro.org\nCc: devel@driverdev.osuosl.org\nCc: linux-kernel@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/e5f2421df13523e46697d453575c020af57c945b"},{"sha":"510f6573ef5da5cc678e0fdb955f95c6125cd3bd","author":{"name":"Greg Ungerer","email":"ed22c22dbde360207569092e60b4298397efb8da@linux-m68k.org"},"message":"m68k: fix ColdFire node shift size calculation\n\n\n[ Upstream commit f55ab8f27548ff3431a6567d400c6757c49fd520 ]\n\nThe m68k pg_data_table is a fix size array defined in arch/m68k/mm/init.c.\nIndex numbers within it are defined based on memory size. But for Coldfire\nthese don't take into account a non-zero physical RAM base address, and this\ncauses us to access past the end of this array at system start time.\n\nChange the node shift calculation so that we keep the index inside its range.\n\nReported-by: Angelo Dureghello <angelo@sysam.it>\nTested-by: Angelo Dureghello <angelo@sysam.it>\nSigned-off-by: Greg Ungerer <gerg@linux-m68k.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/510f6573ef5da5cc678e0fdb955f95c6125cd3bd"},{"sha":"946d33e1e6cd99e7191a6446c82ebc66d5432aab","author":{"name":"Lukas Wunner","email":"65adda4326914576405c9e3a62f4904d96573863@wunner.de"},"message":"serial: 8250_fintek: Fix rs485 disablement on invalid ioctl()\n\n\n[ Upstream commit 3236a965486ba0c6043cf2c7b51943d8b382ae29 ]\n\nThis driver's ->rs485_config callback checks if SER_RS485_RTS_ON_SEND\nand SER_RS485_RTS_AFTER_SEND have the same value.  If they do, it means\nthe user has passed in invalid data with the TIOCSRS485 ioctl()\nsince RTS must have a different polarity when sending and when not\nsending.  In this case, rs485 mode is not enabled (the RS485_URA bit\nis not set in the RS485 Enable Register) and this is supposed to be\nsignaled back to the user by clearing the SER_RS485_ENABLED bit in\nstruct serial_rs485 ... except a missing tilde character is preventing\nthat from happening.\n\nFixes: 28e3fb6c4dce (\"serial: Add support for Fintek F81216A LPC to 4 UART\")\nCc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>\nCc: \"Ji-Ze Hong (Peter Hong)\" <hpeter@gmail.com>\nSigned-off-by: Lukas Wunner <lukas@wunner.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/946d33e1e6cd99e7191a6446c82ebc66d5432aab"},{"sha":"ee08fca9a14d846120d5c00af803002dbac8223b","author":{"name":"Colin Ian King","email":"d100aa70785e45ee8deab668147d941941915c21@canonical.com"},"message":"staging: rtl8188eu: avoid a null dereference on pmlmepriv\n\n\n[ Upstream commit 123c0aab0050cd0e07ce18e453389fbbb0a5a425 ]\n\nThere is a check on pmlmepriv before dereferencing it when\nvfree'ing pmlmepriv->free_bss_buf however the previous call\nto rtw_free_mlme_priv_ie_data deferences pmlmepriv causing\na null pointer deference if it is null.  Avoid this by also\ncalling rtw_free_mlme_priv_ie_data if the pointer is non-null.\n\nDetected by CoverityScan, CID#1230262 (\"Dereference before null check\")\nFixes: 7b464c9fa5cc (\"staging: r8188eu: Add files for new driver - part 4\")\nSigned-off-by: Colin Ian King <colin.king@canonical.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/ee08fca9a14d846120d5c00af803002dbac8223b"},{"sha":"b3d7cc5a84b438cf738fe89310cac92f7f8dc7fe","author":{"name":"Hiromitsu Yamasaki","email":"de0022f3894ba1565a5840a1471e17f4e37b0025@renesas.com"},"message":"spi: sh-msiof: Fix DMA transfer size check\n\n\n[ Upstream commit 36735783fdb599c94b9c86824583df367c65900b ]\n\nDMA supports 32-bit words only,\neven if BITLEN1 of SITMDR2 register is 16bit.\n\nFixes: b0d0ce8b6b91 (\"spi: sh-msiof: Add DMA support\")\nSigned-off-by: Hiromitsu Yamasaki <hiromitsu.yamasaki.ym@renesas.com>\nSigned-off-by: Simon Horman <horms+renesas@verge.net.au>\nAcked-by: Geert Uytterhoeven <geert+renesas@glider.be>\nAcked-by: Dirk Behme <dirk.behme@de.bosch.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/b3d7cc5a84b438cf738fe89310cac92f7f8dc7fe"},{"sha":"e042fd0f03181475711c5350e88ac1f9ed5dce12","author":{"name":"Johan Hovold","email":"759412786bc533369b22377bf83fb9056c5b25b2@kernel.org"},"message":"spi: spi-axi: fix potential use-after-free after deregistration\n\n\n[ Upstream commit 4d5e0689dc9d5640ad46cdfbe1896b74d8df1661 ]\n\nTake an extra reference to the controller before deregistering it to\nprevent use-after-free in the interrupt handler in case an interrupt\nfires before the line is disabled.\n\nFixes: b1353d1c1d45 (\"spi: Add Analog Devices AXI SPI Engine controller support\")\nAcked-by: Lars-Peter Clausen <lars@metafoo.de>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@verizon.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/eXtremeKernel/beryllium-dipper-polaris/commits/e042fd0f03181475711c5350e88ac1f9ed5dce12"}]}
{"actor":{"display_login":"AlekDevOfficial"}}