{"push_id":2433757233,"size":192,"distinct_size":192,"ref":"refs/heads/nuz","head":"925447f015e7496306229727fd6549bc200898d6","before":"7fee7e905a8f7c102bcbbb37bdb9eeb5cafadc02","commits":[{"sha":"5900ecf33c2ff2329dc34167fca8405250743c71","author":{"name":"Jakub Sitnicki","email":"3c27733c6d91e2f4be701ea28b3cf30bbdfa6372@redhat.com"},"message":"ipv6: Skip XFRM lookup if dst_entry in socket cache is valid\n\ncommit 00bc0ef5880dc7b82f9c320dead4afaad48e47be upstream.\n\nAt present we perform an xfrm_lookup() for each UDPv6 message we\nsend. The lookup involves querying the flow cache (flow_cache_lookup)\nand, in case of a cache miss, creating an XFRM bundle.\n\nIf we miss the flow cache, we can end up creating a new bundle and\nderiving the path MTU (xfrm_init_pmtu) from on an already transformed\ndst_entry, which we pass from the socket cache (sk->sk_dst_cache) down\nto xfrm_lookup(). This can happen only if we're caching the dst_entry\nin the socket, that is when we're using a connected UDP socket.\n\nTo put it another way, the path MTU shrinks each time we miss the flow\ncache, which later on leads to incorrectly fragmented payload. It can\nbe observed with ESPv6 in transport mode:\n\n  1) Set up a transformation and lower the MTU to trigger fragmentation\n    # ip xfrm policy add dir out src ::1 dst ::1 \\\n      tmpl src ::1 dst ::1 proto esp spi 1\n    # ip xfrm state add src ::1 dst ::1 \\\n      proto esp spi 1 enc 'aes' 0x0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b\n    # ip link set dev lo mtu 1500\n\n  2) Monitor the packet flow and set up an UDP sink\n    # tcpdump -ni lo -ttt &\n    # socat udp6-listen:12345,fork /dev/null &\n\n  3) Send a datagram that needs fragmentation with a connected socket\n    # perl -e 'print \"@\" x 1470 | socat - udp6:[::1]:12345\n    2016/06/07 18:52:52 socat[724] E read(3, 0x555bb3d5ba00, 8192): Protocol error\n    00:00:00.000000 IP6 ::1 > ::1: frag (0|1448) ESP(spi=0x00000001,seq=0x2), length 1448\n    00:00:00.000014 IP6 ::1 > ::1: frag (1448|32)\n    00:00:00.000050 IP6 ::1 > ::1: ESP(spi=0x00000001,seq=0x3), length 1272\n    (^ ICMPv6 Parameter Problem)\n    00:00:00.000022 IP6 ::1 > ::1: ESP(spi=0x00000001,seq=0x5), length 136\n\n  4) Compare it to a non-connected socket\n    # perl -e 'print \"@\" x 1500' | socat - udp6-sendto:[::1]:12345\n    00:00:40.535488 IP6 ::1 > ::1: frag (0|1448) ESP(spi=0x00000001,seq=0x6), length 1448\n    00:00:00.000010 IP6 ::1 > ::1: frag (1448|64)\n\nWhat happens in step (3) is:\n\n  1) when connecting the socket in __ip6_datagram_connect(), we\n     perform an XFRM lookup, miss the flow cache, create an XFRM\n     bundle, and cache the destination,\n\n  2) afterwards, when sending the datagram, we perform an XFRM lookup,\n     again, miss the flow cache (due to mismatch of flowi6_iif and\n     flowi6_oif, which is an issue of its own), and recreate an XFRM\n     bundle based on the cached (and already transformed) destination.\n\nTo prevent the recreation of an XFRM bundle, avoid an XFRM lookup\naltogether whenever we already have a destination entry cached in the\nsocket. This prevents the path MTU shrinkage and brings us on par with\nUDPv4.\n\nThe fix also benefits connected PINGv6 sockets, another user of\nip6_sk_dst_lookup_flow(), who also suffer messages being transformed\ntwice.\n\nJoint work with Hannes Frederic Sowa.\n\nReported-by: Jan Tluka <jtluka@redhat.com>\nSigned-off-by: Jakub Sitnicki <jkbs@redhat.com>\nAcked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Benedict Wong <benedictwong@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/5900ecf33c2ff2329dc34167fca8405250743c71"},{"sha":"5ae0e9de0ac6728f8a29612ff216240945a25dc8","author":{"name":"Anna-Maria Gleixner","email":"3315635ed9023d8ec3469862a05d31782ee85bbe@linutronix.de"},"message":"hrtimer: Ensure POSIX compliance (relative CLOCK_REALTIME hrtimers)\n\ncommit 48d0c9becc7f3c66874c100c126459a9da0fdced upstream.\n\nThe POSIX specification defines that relative CLOCK_REALTIME timers are not\naffected by clock modifications. Those timers have to use CLOCK_MONOTONIC\nto ensure POSIX compliance.\n\nThe introduction of the additional HRTIMER_MODE_PINNED mode broke this\nrequirement for pinned timers.\n\nThere is no user space visible impact because user space timers are not\nusing pinned mode, but for consistency reasons this needs to be fixed.\n\nCheck whether the mode has the HRTIMER_MODE_REL bit set instead of\ncomparing with HRTIMER_MODE_ABS.\n\nSigned-off-by: Anna-Maria Gleixner <anna-maria@linutronix.de>\nCc: Christoph Hellwig <hch@lst.de>\nCc: John Stultz <john.stultz@linaro.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: keescook@chromium.org\nFixes: 597d0275736d (\"timers: Framework for identifying pinned timers\")\nLink: http://lkml.kernel.org/r/20171221104205.7269-7-anna-maria@linutronix.de\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nCc: Mike Galbraith <efault@gmx.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/5ae0e9de0ac6728f8a29612ff216240945a25dc8"},{"sha":"9d293792bfdd25f1c1a7aecc0152e2b2bc596e45","author":{"name":"Sascha Hauer","email":"d847028614434a015d0d4c60124701f73d57a979@pengutronix.de"},"message":"mtd: nand: gpmi: Fix failure when a erased page has a bitflip at BBM\n\n\n[ Upstream commit fdf2e821052958a114618a95ab18a300d0b080cb ]\n\nWhen erased subpages are read then the BCH decoder returns STATUS_ERASED\nif they are all empty, or STATUS_UNCORRECTABLE if there are bitflips.\nWhen there are bitflips, we have to set these bits again to show the\nupper layers a completely erased page. When a bitflip happens in the\nexact byte where the bad block marker is, then this byte is swapped\nwith another byte in block_mark_swapping(). The correction code then\ndetects a bitflip in another subpage and no longer corrects the bitflip\nwhere it really happens.\n\nCorrect this behaviour by calling block_mark_swapping() after the\nbitflips have been corrected.\n\nIn our case UBIFS failed with this bug because it expects erased\npages to be really empty:\n\nUBIFS error (pid 187): ubifs_scan: corrupt empty space at LEB 36:118735\nUBIFS error (pid 187): ubifs_scanned_corruption: corruption at LEB 36:118735\nUBIFS error (pid 187): ubifs_scanned_corruption: first 8192 bytes from LEB 36:118735\nUBIFS error (pid 187): ubifs_scan: LEB 36 scanning failed\nUBIFS error (pid 187): do_commit: commit failed, error -117\n\nSigned-off-by: Sascha Hauer <s.hauer@pengutronix.de>\nReviewed-by: Richard Weinberger <richard@nod.at>\nAcked-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/9d293792bfdd25f1c1a7aecc0152e2b2bc596e45"},{"sha":"a97c0dc1a45fbe574eeb713f063b2e3dac73e152","author":{"name":"Brendan McGrath","email":"cd51d4f5d4ed894175ae7ee2d8b07621cf7549be@redmandi.dyndns.org"},"message":"ipv6: icmp6: Allow icmp messages to be looped back\n\n\n[ Upstream commit 588753f1eb18978512b1c9b85fddb457d46f9033 ]\n\nOne example of when an ICMPv6 packet is required to be looped back is\nwhen a host acts as both a Multicast Listener and a Multicast Router.\n\nA Multicast Router will listen on address ff02::16 for MLDv2 messages.\n\nCurrently, MLDv2 messages originating from a Multicast Listener running\non the same host as the Multicast Router are not being delivered to the\nMulticast Router. This is due to dst.input being assigned the default\nvalue of dst_discard.\n\nThis results in the packet being looped back but discarded before being\ndelivered to the Multicast Router.\n\nThis patch sets dst.input to ip6_input to ensure a looped back packet\nis delivered to the Multicast Router.\n\nSigned-off-by: Brendan McGrath <redmcg@redmandi.dyndns.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/a97c0dc1a45fbe574eeb713f063b2e3dac73e152"},{"sha":"7c7e39f79bad5cb368714ab746c0d578de79e493","author":{"name":"Al Viro","email":"2a537e97523ffee458777df5f34a2f8c9964f945@zeniv.linux.org.uk"},"message":"sget(): handle failures of register_shrinker()\n\n\n[ Upstream commit 9ee332d99e4d5a97548943b81c54668450ce641b ]\n\nSigned-off-by: Al Viro <viro@zeniv.linux.org.uk>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/7c7e39f79bad5cb368714ab746c0d578de79e493"},{"sha":"bfde9f19290e7dce114d447b8ab23340e8bd049d","author":{"name":"Radu Pirea","email":"30242bc73d6ec9c026e256d6ad1d4a2b059d9b3c@microchip.com"},"message":"spi: atmel: fixed spin_lock usage inside atmel_spi_remove\n\n\n[ Upstream commit 66e900a3d225575c8b48b59ae1fe74bb6e5a65cc ]\n\nThe only part of atmel_spi_remove which needs to be atomic is hardware\nreset.\n\natmel_spi_stop_dma calls dma_terminate_all and this needs interrupts\nenabled.\natmel_spi_release_dma calls dma_release_channel and dma_release_channel\nlocks a mutex inside of spin_lock.\n\nSo the call of these functions can't be inside a spin_lock.\n\nReported-by: Jia-Ju Bai <baijiaju1990@gmail.com>\nSigned-off-by: Radu Pirea <radu.pirea@microchip.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/bfde9f19290e7dce114d447b8ab23340e8bd049d"},{"sha":"69712e5d5b312ad926191bf54bb69e945ffcad30","author":{"name":"Alexander Kochetkov","email":"01231858a87cc2160eb69facea6ee076f44ae0c9@gmail.com"},"message":"net: arc_emac: fix arc_emac_rx() error paths\n\n\n[ Upstream commit e688822d035b494071ecbadcccbd6f3325fb0f59 ]\n\narc_emac_rx() has some issues found by code review.\n\nIn case netdev_alloc_skb_ip_align() or dma_map_single() failure\nrx fifo entry will not be returned to EMAC.\n\nIn case dma_map_single() failure previously allocated skb became\nlost to driver. At the same time address of newly allocated skb\nwill not be provided to EMAC.\n\nSigned-off-by: Alexander Kochetkov <al.kochet@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/69712e5d5b312ad926191bf54bb69e945ffcad30"},{"sha":"05caa7ec533d19058d7978df5ce6d01507205d03","author":{"name":"Cathy Avery","email":"807779d96fa2984b61764dfba8b42044fa260449@redhat.com"},"message":"scsi: storvsc: Fix scsi_cmd error assignments in storvsc_handle_error\n\n\n[ Upstream commit d1b8b2391c24751e44f618fcf86fb55d9a9247fd ]\n\nWhen an I/O is returned with an srb_status of SRB_STATUS_INVALID_LUN\nwhich has zero good_bytes it must be assigned an error. Otherwise the\nI/O will be continuously requeued and will cause a deadlock in the case\nwhere disks are being hot added and removed. sd_probe_async will wait\nforever for its I/O to complete while holding scsi_sd_probe_domain.\n\nAlso returning the default error of DID_TARGET_FAILURE causes multipath\nto not retry the I/O resulting in applications receiving I/O errors\nbefore a failover can occur.\n\nSigned-off-by: Cathy Avery <cavery@redhat.com>\nSigned-off-by: Long Li <longli@microsoft.com>\nReviewed-by: Stephen Hemminger <stephen@networkplumber.org>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/05caa7ec533d19058d7978df5ce6d01507205d03"},{"sha":"7862b4d6f8acde0386d17ee162e0ddb26faea751","author":{"name":"Siva Reddy Kallam","email":"ba07f017a250fa4d5afe03107f268ce92ab480b2@broadcom.com"},"message":"tg3: Add workaround to restrict 5762 MRRS to 2048\n\n\n[ Upstream commit 4419bb1cedcda0272e1dc410345c5a1d1da0e367 ]\n\nOne of AMD based server with 5762 hangs with jumbo frame traffic.\nThis AMD platform has southbridge limitation which is restricting MRRS\nto 4000. As a work around, driver to restricts the MRRS to 2048 for\nthis particular 5762 NX1 card.\n\nSigned-off-by: Siva Reddy Kallam <siva.kallam@broadcom.com>\nSigned-off-by: Michael Chan <michael.chan@broadcom.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/7862b4d6f8acde0386d17ee162e0ddb26faea751"},{"sha":"e93041fc495ba9b76b842b4edff57655e54e4fd0","author":{"name":"Siva Reddy Kallam","email":"ba07f017a250fa4d5afe03107f268ce92ab480b2@broadcom.com"},"message":"tg3: Enable PHY reset in MTU change path for 5720\n\n\n[ Upstream commit e60ee41aaf898584205a6af5c996860d0fe6a836 ]\n\nA customer noticed RX path hang when MTU is changed on the fly while\nrunning heavy traffic with NCSI enabled for 5717 and 5719. Since 5720\nbelongs to same ASIC family, we observed same issue and same fix\ncould solve this problem for 5720.\n\nSigned-off-by: Siva Reddy Kallam <siva.kallam@broadcom.com>\nSigned-off-by: Michael Chan <michael.chan@broadcom.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/e93041fc495ba9b76b842b4edff57655e54e4fd0"},{"sha":"c85a6e7bdea9a9532c1e68c1c472082bf88bc210","author":{"name":"Guilherme G. Piccoli","email":"f53f142a5cc36375815fc4e17b5f9d0296f234c8@linux.vnet.ibm.com"},"message":"bnx2x: Improve reliability in case of nested PCI errors\n\n\n[ Upstream commit f7084059a9cb9e56a186e1677b1dcffd76c2cd24 ]\n\nWhile in recovery process of PCI error (called EEH on PowerPC arch),\nanother PCI transaction could be corrupted causing a situation of\nnested PCI errors. Also, this scenario could be reproduced with\nerror injection mechanisms (for debug purposes).\n\nWe observe that in case of nested PCI errors, bnx2x might attempt to\ninitialize its shmem and cause a kernel crash due to bad addresses\nread from MCP. Multiple different stack traces were observed depending\non the point the second PCI error happens.\n\nThis patch avoids the crashes by:\n\n * failing PCI recovery in case of nested errors (since multiple\n PCI errors in a row are not expected to lead to a functional\n adapter anyway), and by,\n\n * preventing access to adapter FW when MCP is failed (we mark it as\n failed when shmem cannot get initialized properly).\n\nReported-by: Abdul Haleem <abdhalee@linux.vnet.ibm.com>\nSigned-off-by: Guilherme G. Piccoli <gpiccoli@linux.vnet.ibm.com>\nAcked-by: Shahed Shaikh <Shahed.Shaikh@cavium.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/c85a6e7bdea9a9532c1e68c1c472082bf88bc210"},{"sha":"20f6d9c2af33da892a0e03ffd6249c7ab81edfb7","author":{"name":"Matthieu CASTET","email":"dfe58bee4732bceccfbc568d6d9e43eeac8a7255@parrot.com"},"message":"led: core: Fix brightness setting when setting delay_off=0\n\n\n[ Upstream commit 2b83ff96f51d0b039c4561b9f95c824d7bddb85c ]\n\nWith the current code, the following sequence won't work :\necho timer > trigger\n\necho 0 >  delay_off\n* at this point we call\n** led_delay_off_store\n** led_blink_set","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/20f6d9c2af33da892a0e03ffd6249c7ab81edfb7"},{"sha":"96dd200101791418675e7250b88828d71a46e80f","author":{"name":"Stefan Haberland","email":"c25de1589b4a1a2d9eb6398122abafeef7ef78a2@linux.vnet.ibm.com"},"message":"s390/dasd: fix wrongly assigned configuration data\n\n\n[ Upstream commit 8a9bd4f8ebc6800bfc0596e28631ff6809a2f615 ]\n\nWe store per path and per device configuration data to identify the\npath or device correctly. The per path configuration data might get\nmixed up if the original request gets into error recovery and is\nstarted with a random path mask.\n\nThis would lead to a wrong identification of a path in case of a CUIR\nevent for example.\n\nFix by copying the path mask from the original request to the error\nrecovery request in case it is a path verification request.\n\nSigned-off-by: Stefan Haberland <sth@linux.vnet.ibm.com>\nReviewed-by: Jan Hoeppner <hoeppner@linux.vnet.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/96dd200101791418675e7250b88828d71a46e80f"},{"sha":"ac086d5fe75a5c56a78f2500bd6dcbf9137fa2f4","author":{"name":"Aliaksei Karaliou","email":"e4351149f194341a446940e6aead6eac63a912b3@gmail.com"},"message":"xfs: quota: fix missed destroy of qi_tree_lock\n\n\n[ Upstream commit 2196881566225f3c3428d1a5f847a992944daa5b ]\n\nxfs_qm_destroy_quotainfo() does not destroy quotainfo->qi_tree_lock\nwhile destroys quotainfo->qi_quotaofflock.\n\nSigned-off-by: Aliaksei Karaliou <akaraliou.dev@gmail.com>\nReviewed-by: Darrick J. Wong <darrick.wong@oracle.com>\nSigned-off-by: Darrick J. Wong <darrick.wong@oracle.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/ac086d5fe75a5c56a78f2500bd6dcbf9137fa2f4"},{"sha":"9d3948996ee2b774435967809b7c2e37d2b536ff","author":{"name":"Aliaksei Karaliou","email":"e4351149f194341a446940e6aead6eac63a912b3@gmail.com"},"message":"xfs: quota: check result of register_shrinker()\n\n\n[ Upstream commit 3a3882ff26fbdbaf5f7e13f6a0bccfbf7121041d ]\n\nxfs_qm_init_quotainfo() does not check result of register_shrinker()\nwhich was tagged as __must_check recently, reported by sparse.\n\nSigned-off-by: Aliaksei Karaliou <akaraliou.dev@gmail.com>\n[darrick: move xfs_qm_destroy_quotainos nearer xfs_qm_init_quotainos]\nReviewed-by: Darrick J. Wong <darrick.wong@oracle.com>\nSigned-off-by: Darrick J. Wong <darrick.wong@oracle.com>\n\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/9d3948996ee2b774435967809b7c2e37d2b536ff"},{"sha":"154770b1dc1eeaf3d4db433b35621c2a4844e80d","author":{"name":"Tushar Dave","email":"5fd31bff9e56176dfb43df72b02ecb5b706733f2@oracle.com"},"message":"e1000: fix disabling already-disabled warning\n\n\n[ Upstream commit 0b76aae741abb9d16d2c0e67f8b1e766576f897d ]\n\nThis patch adds check so that driver does not disable already\ndisabled device.\n\n[   44.637743] advantechwdt: Unexpected close, not stopping watchdog!\n[   44.997548] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input6\n[   45.013419] e1000 0000:00:03.0: disabling already-disabled device\n[   45.013447] ------------[ cut here ]------------\n[   45.014868] WARNING: CPU: 1 PID: 71 at drivers/pci/pci.c:1641 pci_disable_device+0xa1/0x105:\n\t\t\t\t\t\tpci_disable_device at drivers/pci/pci.c:1640\n[   45.016171] CPU: 1 PID: 71 Comm: rcu_perf_shutdo Not tainted 4.14.0-01330-g3c07399 #1\n[   45.017197] task: ffff88011bee9e40 task.stack: ffffc90000860000\n[   45.017987] RIP: 0010:pci_disable_device+0xa1/0x105:\n\t\t\t\t\t\tpci_disable_device at drivers/pci/pci.c:1640\n[   45.018603] RSP: 0000:ffffc90000863e30 EFLAGS: 00010286\n[   45.019282] RAX: 0000000000000035 RBX: ffff88013a230008 RCX: 0000000000000000\n[   45.020182] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000203\n[   45.021084] RBP: ffff88013a3f31e8 R08: 0000000000000001 R09: 0000000000000000\n[   45.021986] R10: ffffffff827ec29c R11: 0000000000000002 R12: 0000000000000001\n[   45.022946] R13: ffff88013a230008 R14: ffff880117802b20 R15: ffffc90000863e8f\n[   45.023842] FS:  0000000000000000(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000\n[   45.024863] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   45.025583] CR2: ffffc900006d4000 CR3: 000000000220f000 CR4: 00000000000006a0\n[   45.026478] Call Trace:\n[   45.026811]  __e1000_shutdown+0x1d4/0x1e2:\n\t\t\t\t\t\t__e1000_shutdown at drivers/net/ethernet/intel/e1000/e1000_main.c:5162\n[   45.027344]  ? rcu_perf_cleanup+0x2a1/0x2a1:\n\t\t\t\t\t\trcu_perf_shutdown at kernel/rcu/rcuperf.c:627\n[   45.027883]  e1000_shutdown+0x14/0x3a:\n\t\t\t\t\t\te1000_shutdown at drivers/net/ethernet/intel/e1000/e1000_main.c:5235\n[   45.028351]  device_shutdown+0x110/0x1aa:\n\t\t\t\t\t\tdevice_shutdown at drivers/base/core.c:2807\n[   45.028858]  kernel_power_off+0x31/0x64:\n\t\t\t\t\t\tkernel_power_off at kernel/reboot.c:260\n[   45.029343]  rcu_perf_shutdown+0x9b/0xa7:\n\t\t\t\t\t\trcu_perf_shutdown at kernel/rcu/rcuperf.c:637\n[   45.029852]  ? __wake_up_common_lock+0xa2/0xa2:\n\t\t\t\t\t\tautoremove_wake_function at kernel/sched/wait.c:376\n[   45.030414]  kthread+0x126/0x12e:\n\t\t\t\t\t\tkthread at kernel/kthread.c:233\n[   45.030834]  ? __kthread_bind_mask+0x8e/0x8e:\n\t\t\t\t\t\tkthread at kernel/kthread.c:190\n[   45.031399]  ? ret_from_fork+0x1f/0x30:\n\t\t\t\t\t\tret_from_fork at arch/x86/entry/entry_64.S:443\n[   45.031883]  ? kernel_init+0xa/0xf5:\n\t\t\t\t\t\tkernel_init at init/main.c:997\n[   45.032325]  ret_from_fork+0x1f/0x30:\n\t\t\t\t\t\tret_from_fork at arch/x86/entry/entry_64.S:443\n[   45.032777] Code: 00 48 85 ed 75 07 48 8b ab a8 00 00 00 48 8d bb 98 00 00 00 e8 aa d1 11 00 48 89 ea 48 89 c6 48 c7 c7 d8 e4 0b 82 e8 55 7d da ff <0f> ff b9 01 00 00 00 31 d2 be 01 00 00 00 48 c7 c7 f0 b1 61 82\n[   45.035222] ---[ end trace c257137b1b1976ef ]---\n[   45.037838] ACPI: Preparing to enter system sleep state S5\n\nSigned-off-by: Tushar Dave <tushar.n.dave@oracle.com>\nTested-by: Fengguang Wu <fengguang.wu@intel.com>\nSigned-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/154770b1dc1eeaf3d4db433b35621c2a4844e80d"},{"sha":"4108c7767f28ed381d7c70a5a89884b97d0c34cc","author":{"name":"Xiongwei Song","email":"8040d3b6eaafd9d85fa13765d313115be5975f07@gmail.com"},"message":"drm/ttm: check the return value of kzalloc\n\n\n[ Upstream commit 19d859a7205bc59ffc38303eb25ae394f61d21dc ]\n\nIn the function ttm_page_alloc_init, kzalloc call is made for variable\n_manager, we need to check its return value, it may return NULL.\n\nSigned-off-by: Xiongwei Song <sxwjean@gmail.com>\nReviewed-by: Christian König <christian.koenig@amd.com>\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/4108c7767f28ed381d7c70a5a89884b97d0c34cc"},{"sha":"8094b1a3fa737e7f3515ae8b5286c65964d1a51f","author":{"name":"Eduardo Otubo","email":"43d9f272a12e705f5809e86b177d908142714cf9@redhat.com"},"message":"xen-netfront: enable device after manual module load\n\n\n[ Upstream commit b707fda2df4070785d0fa8a278aa13944c5f51f8 ]\n\nWhen loading the module after unloading it, the network interface would\nnot be enabled and thus wouldn't have a backend counterpart and unable\nto be used by the guest.\n\nThe guest would face errors like:\n\n  [root@guest ~]# ethtool -i eth0\n  Cannot get driver information: No such device\n\n  [root@guest ~]# ifconfig eth0\n  eth0: error fetching interface information: Device not found\n\nThis patch initializes the state of the netfront device whenever it is\nloaded manually, this state would communicate the netback to create its\ndevice and establish the connection between them.\n\nSigned-off-by: Eduardo Otubo <otubo@redhat.com>\nReviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/8094b1a3fa737e7f3515ae8b5286c65964d1a51f"},{"sha":"eb8936ae670aef8d6efa447a82e4acc48f6a304b","author":{"name":"Christophe JAILLET","email":"37dad06b5adae86647eb31988fda7e3e669b78d5@wanadoo.fr"},"message":"mdio-sun4i: Fix a memory leak\n\n\n[ Upstream commit 56c0290202ab94a2f2780c449395d4ae8495fab4 ]\n\nIf the probing of the regulator is deferred, the memory allocated by\n'mdiobus_alloc_size()' will be leaking.\nIt should be freed before the next call to 'sun4i_mdio_probe()' which will\nreallocate it.\n\nFixes: 4bdcb1dd9feb (\"net: Add MDIO bus driver for the Allwinner EMAC\")\nSigned-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/eb8936ae670aef8d6efa447a82e4acc48f6a304b"},{"sha":"56cf3902c1795e0180d8ce221562784fb5c1b85b","author":{"name":"Sergei Shtylyov","email":"405474b86ca3821db87329a130f0575274587812@cogentembedded.com"},"message":"SolutionEngine771x: fix Ether platform data\n\n\n[ Upstream commit 195e2addbce09e5afbc766efc1e6567c9ce840d3 ]\n\nThe 'sh_eth' driver's probe() method would fail  on the SolutionEngine7710\nboard and crash on SolutionEngine7712 board  as the platform code is\nhopelessly behind the driver's platform data --  it passes the PHY address\ninstead of 'struct sh_eth_plat_data *'; pass the latter to the driver in\norder to fix the bug...\n\nFixes: 71557a37adb5 (\"[netdrvr] sh_eth: Add SH7619 support\")\nSigned-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/PsyMan47/Pepsy-Kernel/commits/56cf3902c1795e0180d8ce221562784fb5c1b85b"}]}
{"actor":{"display_login":"PsyMan47"}}