{"push_id":2339857276,"size":88,"distinct_size":0,"ref":"refs/heads/aosp/upstream-linux-4.9.y","head":"3e598a7089eef1fe04d5b87cc154295302960e62","before":"7f3bd8db99746a60bcae1ec4059a4756d19b63c2","commits":[{"sha":"ba4f9c192d3b655af9a24e0b8273e58d9ed8aa63","author":{"name":"Michal Suchanek","email":"ea0a5c401a01ab38a18f00fb5875cc26dd79e517@suse.de"},"message":"powerpc/pseries: include linux/types.h in asm/hvcall.h\n\ncommit 1b689a95ce7427075f9ac9fb4aea1af530742b7f upstream.\n\nCommit 6e032b350cd1 (\"powerpc/powernv: Check device-tree for RFI flush\nsettings\") uses u64 in asm/hvcall.h without including linux/types.h\n\nThis breaks hvcall.h users that do not include the header themselves.\n\nFixes: 6e032b350cd1 (\"powerpc/powernv: Check device-tree for RFI flush settings\")\nSigned-off-by: Michal Suchanek <msuchanek@suse.de>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/ba4f9c192d3b655af9a24e0b8273e58d9ed8aa63"},{"sha":"ee6858f72a39226728e5085fc7388785a8ddc5d3","author":{"name":"Matthew Wilcox","email":"b68326deb85f860adfc3ac32411fb6008f48b1b9@microsoft.com"},"message":"cifs: Fix missing put_xid in cifs_file_strict_mmap\n\ncommit f04a703c3d613845ae3141bfaf223489de8ab3eb upstream.\n\nIf cifs_zap_mapping() returned an error, we would return without putting\nthe xid that we got earlier.  Restructure cifs_file_strict_mmap() and\ncifs_file_mmap() to be more similar to each other and have a single\npoint of return that always puts the xid.\n\nSigned-off-by: Matthew Wilcox <mawilcox@microsoft.com>\nSigned-off-by: Steve French <smfrench@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/ee6858f72a39226728e5085fc7388785a8ddc5d3"},{"sha":"f59eda16646ab3b0de9e7cac9528c40df46606ac","author":{"name":"Daniel N Pettersson","email":"ae29ab92925b3d53538dd30a5c329c26373aae63@axis.com"},"message":"cifs: Fix autonegotiate security settings mismatch\n\ncommit 9aca7e454415f7878b28524e76bebe1170911a88 upstream.\n\nAutonegotiation gives a security settings mismatch error if the SMB\nserver selects an SMBv3 dialect that isn't SMB3.02. The exact error is\n\"protocol revalidation - security settings mismatch\".\nThis can be tested using Samba v4.2 or by setting the global Samba\nsetting max protocol = SMB3_00.\n\nThe check that fails in smb3_validate_negotiate is the dialect\nverification of the negotiate info response. This is because it tries\nto verify against the protocol_id in the global smbdefault_values. The\nprotocol_id in smbdefault_values is SMB3.02.\nIn SMB2_negotiate the protocol_id in smbdefault_values isn't updated,\nit is global so it probably shouldn't be, but server->dialect is.\n\nThis patch changes the check in smb3_validate_negotiate to use\nserver->dialect instead of server->vals->protocol_id. The patch works\nwith autonegotiate and when using a specific version in the vers mount\noption.\n\nSigned-off-by: Daniel N Pettersson <danielnp@axis.com>\nSigned-off-by: Steve French <smfrench@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/f59eda16646ab3b0de9e7cac9528c40df46606ac"},{"sha":"7e68916c361ac6d730601bef4e8a4c43aa93495e","author":{"name":"Aurelien Aptel","email":"cd571d2c99d35af3081f2c53207440bdad2eaa35@suse.com"},"message":"CIFS: zero sensitive data when freeing\n\ncommit 97f4b7276b829a8927ac903a119bef2f963ccc58 upstream.\n\nalso replaces memset()+kfree() by kzfree().\n\nSigned-off-by: Aurelien Aptel <aaptel@suse.com>\nSigned-off-by: Steve French <smfrench@gmail.com>\nReviewed-by: Pavel Shilovsky <pshilov@microsoft.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/7e68916c361ac6d730601bef4e8a4c43aa93495e"},{"sha":"297c7cc4b5651b174a62925b6c961085f04979fd","author":{"name":"Yang Shunyong","email":"874e45ed16c4dcf10b3e7ee9b2b4e3eef460ac9d@hxt-semitech.com"},"message":"dmaengine: dmatest: fix container_of member in dmatest_callback\n\ncommit 66b3bd2356e0a1531c71a3dcf96944621e25c17c upstream.\n\nThe type of arg passed to dmatest_callback is struct dmatest_done.\nIt refers to test_done in struct dmatest_thread, not done_wait.\n\nFixes: 6f6a23a213be (\"dmaengine: dmatest: move callback wait ...\")\nSigned-off-by: Yang Shunyong <shunyong.yang@hxt-semitech.com>\nAcked-by: Adam Wallis <awallis@codeaurora.org>\nSigned-off-by: Vinod Koul <vinod.koul@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/297c7cc4b5651b174a62925b6c961085f04979fd"},{"sha":"83946c33b9b99b5bc6157cfbf3970265f006c2bf","author":{"name":"Hugh Dickins","email":"11bd16bbccd141ee47d9426ad06afbc74b915cf0@google.com"},"message":"kaiser: fix compile error without vsyscall\n\nTobias noticed a compile error on 4.4.115, and it's the same on 4.9.80:\narch/x86/mm/kaiser.c: In function ‘kaiser_init’:\narch/x86/mm/kaiser.c:348:8: error: ‘vsyscall_pgprot’ undeclared\n                                   (first use in this function)\n\nIt seems like his combination of kernel options doesn't work for KAISER.\nX86_VSYSCALL_EMULATION is not set on his system, while LEGACY_VSYSCALL\nis set to NONE (LEGACY_VSYSCALL_NONE=y). He managed to get things\ncompiling again, by moving the 'extern unsigned long vsyscall_pgprot'\noutside of the preprocessor statement. This works because the optimizer\nremoves that code (vsyscall_enabled() is always false) - and that's how\nit was done in some older backports.\n\nReported-by: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>\nSigned-off-by: Hugh Dickins <hughd@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/83946c33b9b99b5bc6157cfbf3970265f006c2bf"},{"sha":"0b376535ad5493d2fcf70ab5f6539551aadb493e","author":{"name":"Thomas Gleixner","email":"352b5f5ba0189d2583768a9bb8247f98115b9038@linutronix.de"},"message":"posix-timer: Properly check sigevent->sigev_notify\n\ncommit cef31d9af908243421258f1df35a4a644604efbe upstream.\n\ntimer_create() specifies via sigevent->sigev_notify the signal delivery for\nthe new timer. The valid modes are SIGEV_NONE, SIGEV_SIGNAL, SIGEV_THREAD\nand (SIGEV_SIGNAL | SIGEV_THREAD_ID).\n\nThe sanity check in good_sigevent() is only checking the valid combination\nfor the SIGEV_THREAD_ID bit, i.e. SIGEV_SIGNAL, but if SIGEV_THREAD_ID is\nnot set it accepts any random value.\n\nThis has no real effects on the posix timer and signal delivery code, but\nit affects show_timer() which handles the output of /proc/$PID/timers. That\nfunction uses a string array to pretty print sigev_notify. The access to\nthat array has no bound checks, so random sigev_notify cause access beyond\nthe array bounds.\n\nAdd proper checks for the valid notify modes and remove the SIGEV_THREAD_ID\nmasking from various code pathes as SIGEV_NONE can never be set in\ncombination with SIGEV_THREAD_ID.\n\nReported-by: Eric Biggers <ebiggers3@gmail.com>\nReported-by: Dmitry Vyukov <dvyukov@google.com>\nReported-by: Alexey Dobriyan <adobriyan@gmail.com>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: John Stultz <john.stultz@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/0b376535ad5493d2fcf70ab5f6539551aadb493e"},{"sha":"57ddb8eae517315f811c4915f1d5c11e59423707","author":{"name":"Petr Cvek","email":"b70ea866dcf102039b02e74d361dfde39c54067e@tul.cz"},"message":"usb: gadget: uvc: Missing files for configfs interface\n\ncommit c8cd751060b149997b9de53a494fb1490ded72c5 upstream.\n\nCommit 76e0da34c7ce (\"usb-gadget/uvc: use per-attribute show and store\nmethods\") caused a stringification of an undefined macro argument \"aname\",\nso three UVC parameters (streaming_interval, streaming_maxpacket and\nstreaming_maxburst) were named \"aname\".\n\nAdd the definition of \"aname\" to the main macro and name the filenames as\noriginaly intended.\n\nSigned-off-by: Petr Cvek <petr.cvek@tul.cz>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/57ddb8eae517315f811c4915f1d5c11e59423707"},{"sha":"1c679981309b4d36b024fc954cfcf2111a007de0","author":{"name":"Steven Rostedt (VMware)","email":"9f626a07de58780741a9085807c77fd646ef3459@goodmis.org"},"message":"sched/rt: Use container_of() to get root domain in rto_push_irq_work_func()\n\ncommit ad0f1d9d65938aec72a698116cd73a980916895e upstream.\n\nWhen the rto_push_irq_work_func() is called, it looks at the RT overloaded\nbitmask in the root domain via the runqueue (rq->rd). The problem is that\nduring CPU up and down, nothing here stops rq->rd from changing between\ntaking the rq->rd->rto_lock and releasing it. That means the lock that is\nreleased is not the same lock that was taken.\n\nInstead of using this_rq()->rd to get the root domain, as the irq work is\npart of the root domain, we can simply get the root domain from the irq work\nthat is passed to the routine:\n\n container_of(work, struct root_domain, rto_push_work)\n\nThis keeps the root domain consistent.\n\nReported-by: Pavan Kondeti <pkondeti@codeaurora.org>\nSigned-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Mike Galbraith <efault@gmx.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nFixes: 4bdced5c9a292 (\"sched/rt: Simplify the IPI based RT balancing logic\")\nLink: http://lkml.kernel.org/r/CAEU1=PkiHO35Dzna8EQqNSKW1fr1y1zRQ5y66X117MG06sQtNA@mail.gmail.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/1c679981309b4d36b024fc954cfcf2111a007de0"},{"sha":"a384e5437f705972d2884cea17b931c1a2cd3277","author":{"name":"Steven Rostedt (VMware)","email":"9f626a07de58780741a9085807c77fd646ef3459@goodmis.org"},"message":"sched/rt: Up the root domain ref count when passing it around via IPIs\n\ncommit 364f56653708ba8bcdefd4f0da2a42904baa8eeb upstream.\n\nWhen issuing an IPI RT push, where an IPI is sent to each CPU that has more\nthan one RT task scheduled on it, it references the root domain's rto_mask,\nthat contains all the CPUs within the root domain that has more than one RT\ntask in the runable state. The problem is, after the IPIs are initiated, the\nrq->lock is released. This means that the root domain that is associated to\nthe run queue could be freed while the IPIs are going around.\n\nAdd a sched_get_rd() and a sched_put_rd() that will increment and decrement\nthe root domain's ref count respectively. This way when initiating the IPIs,\nthe scheduler will up the root domain's ref count before releasing the\nrq->lock, ensuring that the root domain does not go away until the IPI round\nis complete.\n\nReported-by: Pavan Kondeti <pkondeti@codeaurora.org>\nSigned-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Mike Galbraith <efault@gmx.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nFixes: 4bdced5c9a292 (\"sched/rt: Simplify the IPI based RT balancing logic\")\nLink: http://lkml.kernel.org/r/CAEU1=PkiHO35Dzna8EQqNSKW1fr1y1zRQ5y66X117MG06sQtNA@mail.gmail.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/a384e5437f705972d2884cea17b931c1a2cd3277"},{"sha":"7e2fb808d3c7c52f88ebc670949dbf1bae48f2a2","author":{"name":"Mohamed Ghannam","email":"5eb3f933fdfc6698c763351d205c026ea603aa21@gmail.com"},"message":"dccp: CVE-2017-8824: use-after-free in DCCP code\n\ncommit 69c64866ce072dea1d1e59a0d61e0f66c0dffb76 upstream.\n\nWhenever the sock object is in DCCP_CLOSED state,\ndccp_disconnect() must free dccps_hc_tx_ccid and\ndccps_hc_rx_ccid and set to NULL.\n\nSigned-off-by: Mohamed Ghannam <simo.ghannam@gmail.com>\nReviewed-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/7e2fb808d3c7c52f88ebc670949dbf1bae48f2a2"},{"sha":"1ff1353a03c6cde5334a94cb67f8632141b0589b","author":{"name":"Malcolm Priestley","email":"e187a437af0ab791fc51b0acfa7691f617a012f3@gmail.com"},"message":"media: dvb-usb-v2: lmedm04: Improve logic checking of warm start\n\ncommit 3d932ee27e852e4904647f15b64dedca51187ad7 upstream.\n\nWarm start has no check as whether a genuine device has\nconnected and proceeds to next execution path.\n\nCheck device should read 0x47 at offset of 2 on USB descriptor read\nand it is the amount requested of 6 bytes.\n\nFix for\nkasan: CONFIG_KASAN_INLINE enabled\nkasan: GPF could be caused by NULL-ptr deref or user memory access as\n\nReported-by: Andrey Konovalov <andreyknvl@google.com>\nSigned-off-by: Malcolm Priestley <tvboxspy@gmail.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>\nCc: Ben Hutchings <ben.hutchings@codethink.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/1ff1353a03c6cde5334a94cb67f8632141b0589b"},{"sha":"f320dd20224ca9193040c379f0243030dd67fa4b","author":{"name":"Malcolm Priestley","email":"e187a437af0ab791fc51b0acfa7691f617a012f3@gmail.com"},"message":"media: dvb-usb-v2: lmedm04: move ts2020 attach to dm04_lme2510_tuner\n\ncommit 7bf7a7116ed313c601307f7e585419369926ab05 upstream.\n\nWhen the tuner was split from m88rs2000 the attach function is in wrong\nplace.\n\nMove to dm04_lme2510_tuner to trap errors on failure and removing\na call to lme_coldreset.\n\nPrevents driver starting up without any tuner connected.\n\nFixes to trap for ts2020 fail.\nLME2510(C): FE Found M88RS2000\nts2020: probe of 0-0060 failed with error -11\n...\nLME2510(C): TUN Found RS2000 tuner\nkasan: CONFIG_KASAN_INLINE enabled\nkasan: GPF could be caused by NULL-ptr deref or user memory access\ngeneral protection fault: 0000 [#1] PREEMPT SMP KASAN\n\nReported-by: Andrey Konovalov <andreyknvl@google.com>\nSigned-off-by: Malcolm Priestley <tvboxspy@gmail.com>\nTested-by: Andrey Konovalov <andreyknvl@google.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>\nCc: Ben Hutchings <ben.hutchings@codethink.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/f320dd20224ca9193040c379f0243030dd67fa4b"},{"sha":"198a7ddaf5d2c76130b28f19ed6d768860ea2b8e","author":{"name":"Arvind Yadav","email":"1650c5a66df99aba40094ad382bcfb9e3d7811e6@gmail.com"},"message":"media: hdpvr: Fix an error handling path in hdpvr_probe()\n\ncommit c0f71bbb810237a38734607ca4599632f7f5d47f upstream.\n\nHere, hdpvr_register_videodev() is responsible for setup and\nregister a video device. Also defining and initializing a worker.\nhdpvr_register_videodev() is calling by hdpvr_probe at last.\nSo no need to flush any work here.\nUnregister v4l2, free buffers and memory. If hdpvr_probe() will fail.\n\nSigned-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>\nReported-by: Andrey Konovalov <andreyknvl@google.com>\nTested-by: Andrey Konovalov <andreyknvl@google.com>\nSigned-off-by: Hans Verkuil <hans.verkuil@cisco.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>\nCc: Ben Hutchings <ben.hutchings@codethink.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/198a7ddaf5d2c76130b28f19ed6d768860ea2b8e"},{"sha":"cbdabc7027b1fea4d6a7d86bc573096ef5126657","author":{"name":"Arnd Bergmann","email":"72a0f6d3b182607e6d5c44b93e1abb7b23ee18f3@arndb.de"},"message":"mtd: cfi: convert inline functions to macros\n\ncommit 9e343e87d2c4c707ef8fae2844864d4dde3a2d13 upstream.\n\nThe map_word_() functions, dating back to linux-2.6.8, try to perform\nbitwise operations on a 'map_word' structure. This may have worked\nwith compilers that were current then (gcc-3.4 or earlier), but end\nup being rather inefficient on any version I could try now (gcc-4.4 or\nhigher). Specifically we hit a problem analyzed in gcc PR81715 where we\nfail to reuse the stack space for local variables.\n\nThis can be seen immediately in the stack consumption for\ncfi_staa_erase_varsize() and other functions that (with CONFIG_KASAN)\ncan be up to 2200 bytes. Changing the inline functions into macros brings\nthis down to 1280 bytes.  Without KASAN, the same problem exists, but\nthe stack consumption is lower to start with, my patch shrinks it from\n920 to 496 bytes on with arm-linux-gnueabi-gcc-5.4, and saves around\n1KB in .text size for cfi_cmdset_0020.c, as it avoids copying map_word\nstructures for each call to one of these helpers.\n\nWith the latest gcc-8 snapshot, the problem is fixed in upstream gcc,\nbut nobody uses that yet, so we should still work around it in mainline\nkernels and probably backport the workaround to stable kernels as well.\nWe had a couple of other functions that suffered from the same gcc bug,\nand all of those had a simpler workaround involving dummy variables\nin the inline function. Unfortunately that did not work here, the\nmacro hack was the best I could come up with.\n\nIt would also be helpful to have someone to a little performance testing\non the patch, to see how much it helps in terms of CPU utilitzation.\n\nLink: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81715\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nAcked-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/cbdabc7027b1fea4d6a7d86bc573096ef5126657"},{"sha":"d25d52ff1011faaee8174bac39b0c58a59833f22","author":{"name":"Kamal Dasu","email":"6912f8a1a99f381a6bf1545748683a4e0bc94a73@gmail.com"},"message":"mtd: nand: brcmnand: Disable prefetch by default\n\ncommit f953f0f89663c39f08f4baaa8a4a881401b65654 upstream.\n\nBrcm nand controller prefetch feature needs to be disabled\nby default. Enabling affects performance on random reads as\nwell as dma reads.\n\nSigned-off-by: Kamal Dasu <kdasu.kdev@gmail.com>\nFixes: 27c5b17cd1b1 (\"mtd: nand: add NAND driver \"library\" for Broadcom STB NAND controller\")\nAcked-by: Florian Fainelli <f.fainelli@gmail.com>\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/d25d52ff1011faaee8174bac39b0c58a59833f22"},{"sha":"d80cd3e93653e4868d99aed4eb18ff2fcd134574","author":{"name":"Miquel Raynal","email":"a7767255b3edc7e6f3fcad603d168d8a229ae75e@free-electrons.com"},"message":"mtd: nand: Fix nand_do_read_oob() return value\n\ncommit 87e89ce8d0d14f573c068c61bec2117751fb5103 upstream.\n\nStarting from commit 041e4575f034 (\"mtd: nand: handle ECC errors in\nOOB\"), nand_do_read_oob() (from the NAND core) did return 0 or a\nnegative error, and the MTD layer expected it.\n\nHowever, the trend for the NAND layer is now to return an error or a\npositive number of bitflips. Deciding which status to return to the user\nbelongs to the MTD layer.\n\nCommit e47f68587b82 (\"mtd: check for max_bitflips in mtd_read_oob()\")\nbrought this logic to the mtd_read_oob() function while the return value\ncoming from nand_do_read_oob() (called by the ->_read_oob() hook) was\nleft unchanged.\n\nFixes: e47f68587b82 (\"mtd: check for max_bitflips in mtd_read_oob()\")\nSigned-off-by: Miquel Raynal <miquel.raynal@free-electrons.com>\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/d80cd3e93653e4868d99aed4eb18ff2fcd134574"},{"sha":"44ebd641be56653803482756aca487b5152a22d5","author":{"name":"Miquel Raynal","email":"a7767255b3edc7e6f3fcad603d168d8a229ae75e@free-electrons.com"},"message":"mtd: nand: sunxi: Fix ECC strength choice\n\ncommit f4c6cd1a7f2275d5bc0e494b21fff26f8dde80f0 upstream.\n\nWhen the requested ECC strength does not exactly match the strengths\nsupported by the ECC engine, the driver is selecting the closest\nstrength meeting the 'selected_strength > requested_strength'\nconstraint. Fix the fact that, in this particular case, ecc->strength\nvalue was not updated to match the 'selected_strength'.\n\nFor instance, one can encounter this issue when no ECC requirement is\nfilled in the device tree while the NAND chip minimum requirement is not\na strength/step_size combo natively supported by the ECC engine.\n\nFixes: 1fef62c1423b (\"mtd: nand: add sunxi NAND flash controller support\")\nSuggested-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Miquel Raynal <miquel.raynal@free-electrons.com>\nSigned-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/44ebd641be56653803482756aca487b5152a22d5"},{"sha":"84f9d8536c8bf440d84093eb749290d88f7e1d76","author":{"name":"Sascha Hauer","email":"d847028614434a015d0d4c60124701f73d57a979@pengutronix.de"},"message":"ubi: fastmap: Erase outdated anchor PEBs during attach\n\ncommit f78e5623f45bab2b726eec29dc5cefbbab2d0b1c upstream.\n\nThe fastmap update code might erase the current fastmap anchor PEB\nin case it doesn't find any new free PEB. When a power cut happens\nin this situation we must not have any outdated fastmap anchor PEB\non the device, because that would be used to attach during next\nboot.\nThe easiest way to make that sure is to erase all outdated fastmap\nanchor PEBs synchronously during attach.\n\nSigned-off-by: Sascha Hauer <s.hauer@pengutronix.de>\nReviewed-by: Richard Weinberger <richard@nod.at>\nFixes: dbb7d2a88d2a (\"UBI: Add fastmap core\")\nSigned-off-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/84f9d8536c8bf440d84093eb749290d88f7e1d76"},{"sha":"de14d0c124ca496381872a42cd32a53433ed28b2","author":{"name":"Bradley Bolen","email":"57962cf3b8c3b80c6136f9c4e23f1c35d9ff61c3@gmail.com"},"message":"ubi: block: Fix locking for idr_alloc/idr_remove\n\ncommit 7f29ae9f977bcdc3654e68bc36d170223c52fd48 upstream.\n\nThis fixes a race with idr_alloc where gd->first_minor can be set to the\nsame value for two simultaneous calls to ubiblock_create.  Each instance\ncalls device_add_disk with the same first_minor.  device_add_disk calls\nbdi_register_owner which generates several warnings.\n\nWARNING: CPU: 1 PID: 179 at kernel-source/fs/sysfs/dir.c:31\nsysfs_warn_dup+0x68/0x88\nsysfs: cannot create duplicate filename '/devices/virtual/bdi/252:2'\n\nWARNING: CPU: 1 PID: 179 at kernel-source/lib/kobject.c:240\nkobject_add_internal+0x1ec/0x2f8\nkobject_add_internal failed for 252:2 with -EEXIST, don't try to\nregister things with the same name in the same directory\n\nWARNING: CPU: 1 PID: 179 at kernel-source/fs/sysfs/dir.c:31\nsysfs_warn_dup+0x68/0x88\nsysfs: cannot create duplicate filename '/dev/block/252:2'\n\nHowever, device_add_disk does not error out when bdi_register_owner\nreturns an error.  Control continues until reaching blk_register_queue.\nIt then BUGs.\n\nkernel BUG at kernel-source/fs/sysfs/group.c:113!\n[<c01e26cc>] (internal_create_group) from [<c01e2950>]\n(sysfs_create_group+0x20/0x24)\n[<c01e2950>] (sysfs_create_group) from [<c00e3d38>]\n(blk_trace_init_sysfs+0x18/0x20)\n[<c00e3d38>] (blk_trace_init_sysfs) from [<c02bdfbc>]\n(blk_register_queue+0xd8/0x154)\n[<c02bdfbc>] (blk_register_queue) from [<c02cec84>]\n(device_add_disk+0x194/0x44c)\n[<c02cec84>] (device_add_disk) from [<c0436ec8>]\n(ubiblock_create+0x284/0x2e0)\n[<c0436ec8>] (ubiblock_create) from [<c0427bb8>]\n(vol_cdev_ioctl+0x450/0x554)\n[<c0427bb8>] (vol_cdev_ioctl) from [<c0189110>] (vfs_ioctl+0x30/0x44)\n[<c0189110>] (vfs_ioctl) from [<c01892e0>] (do_vfs_ioctl+0xa0/0x790)\n[<c01892e0>] (do_vfs_ioctl) from [<c0189a14>] (SyS_ioctl+0x44/0x68)\n[<c0189a14>] (SyS_ioctl) from [<c0010640>] (ret_fast_syscall+0x0/0x34)\n\nLocking idr_alloc/idr_remove removes the race and keeps gd->first_minor\nunique.\n\nFixes: 2bf50d42f3a4 (\"UBI: block: Dynamically allocate minor numbers\")\nSigned-off-by: Bradley Bolen <bradleybolen@gmail.com>\nReviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com>\nSigned-off-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/de14d0c124ca496381872a42cd32a53433ed28b2"}]}
{"actor":{"display_login":"Jackeagle"}}