)]}' { "log": [ { "commit": "ed55202fda5c68e44464cd5afdc819a8721b601a", "tree": "60d724803e0e8cccf7795c185820c77b50fa1f40", "parents": [ "9825e3158e302980b71c54b72e90f0624e1cfab3" ], "author": { "name": "Gavin Shan", "email": "shangw@linux.vnet.ibm.com", "time": "Mon Sep 17 04:34:28 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Oct 13 05:38:39 2012 +0900" }, "message": "powerpc/eeh: Fix crash on converting OF node to edev\n\ncommit 1e38b7140185e384da216aff66a711df09b5afc9 upstream.\n\nThe kernel crash was reported by Alexy. He was testing some feature\nwith private kernel, in which Alexy added some code in pci_pm_reset()\nto read the CSR after writting it. The bug could be reproduced on\nFiber Channel card (Fibre Channel: Emulex Corporation Saturn-X:\nLightPulse Fibre Channel Host Adapter (rev 03)) by the following\ncommands.\n\n\t# echo 1 \u003e /sys/devices/pci0004:01/0004:01:00.0/reset\n\t# rmmod lpfc\n\t# modprobe lpfc\n\nThe history behind the test case is that those additional config\nspace reading operations in pci_pm_reset() would cause EEH error,\nbut we didn\u0027t detect EEH error until \"modprobe lpfc\". For the case,\nall the PCI devices on PCI bus (0004:01) were removed and added after\nPE reset. Then the EEH devices would be figured out again based on\nthe OF nodes. Unfortunately, there were some child OF nodes under\nPCI device (0004:01:00.0), but they didn\u0027t have attached PCI_DN since\nthey\u0027re invisible from PCI domain. However, we were still trying to\nconvert OF node to EEH device without checking on the attached PCI_DN.\nEventually, it caused the kernel crash as follows:\n\nUnable to handle kernel paging request for data at address 0x00000030\nFaulting instruction address: 0xc00000000004d888\ncpu 0x0: Vector: 300 (Data Access) at [c000000fc797b950]\n pc: c00000000004d888: .eeh_add_device_tree_early+0x78/0x140\n lr: c00000000004d880: .eeh_add_device_tree_early+0x70/0x140\n sp: c000000fc797bbd0\n msr: 8000000000009032\n dar: 30\n dsisr: 40000000\n current \u003d 0xc000000fc78d9f70\n paca \u003d 0xc00000000edb0000 softe: 0 irq_happened: 0x00\n pid \u003d 2951, comm \u003d eehd\nenter ? for help\n[c000000fc797bc50] c00000000004d848 .eeh_add_device_tree_early+0x38/0x140\n[c000000fc797bcd0] c00000000004d848 .eeh_add_device_tree_early+0x38/0x140\n[c000000fc797bd50] c000000000051b54 .pcibios_add_pci_devices+0x34/0x190\n[c000000fc797bde0] c00000000004fb10 .eeh_reset_device+0x100/0x160\n[c000000fc797be70] c0000000000502dc .eeh_handle_event+0x19c/0x300\n[c000000fc797bf00] c000000000050570 .eeh_event_handler+0x130/0x1a0\n[c000000fc797bf90] c000000000020138 .kernel_thread+0x54/0x70\n\nThe patch changes of_node_to_eeh_dev() and just returns NULL if the\npassed OF node doesn\u0027t have attached PCI_DN.\n\nReported-by: Alexey Kardashevskiy \u003caik@ozlabs.ru\u003e\nSigned-off-by: Gavin Shan \u003cshangw@linux.vnet.ibm.com\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "4893cf612a68d26cdbe0e16ba9c42772136e2340", "tree": "b057aa6eda3d88d158efcb9fc5389c928d1387be", "parents": [ "f15977883584e7b52832518c3fef115957d3203b" ], "author": { "name": "Jean Delvare", "email": "jdelvare@suse.de", "time": "Tue Oct 02 16:42:36 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Oct 13 05:38:37 2012 +0900" }, "message": "kbuild: Fix gcc -x syntax\n\ncommit b1e0d8b70fa31821ebca3965f2ef8619d7c5e316 upstream.\n\nThe correct syntax for gcc -x is \"gcc -x assembler\", not\n\"gcc -xassembler\". Even though the latter happens to work, the former\nis what is documented in the manual page and thus what gcc wrappers\nsuch as icecream do expect.\n\nThis isn\u0027t a cosmetic change. The missing space prevents icecream from\nrecognizing compilation tasks it can\u0027t handle, leading to silent kernel\nmiscompilations.\n\nBesides me, credits go to Michael Matz and Dirk Mueller for\ninvestigating the miscompilation issue and tracking it down to this\nincorrect -x parameter syntax.\n\nSigned-off-by: Jean Delvare \u003cjdelvare@suse.de\u003e\nAcked-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Bernhard Walle \u003cbernhard@bwalle.de\u003e\nCc: Michal Marek \u003cmmarek@suse.cz\u003e\nCc: Ralf Baechle \u003cralf@linux-mips.org\u003e\nSigned-off-by: Michal Marek \u003cmmarek@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "605843502b0573c0c865b13f770d971aadaf0c41", "tree": "3ada2b24affbd75599009aeea4bb7d81beac01b5", "parents": [ "399abb8918aa5cef74a1d5c582bc7c08c8c99757" ], "author": { "name": "Geert Uytterhoeven", "email": "geert@linux-m68k.org", "time": "Thu Oct 04 17:11:13 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Oct 13 05:38:36 2012 +0900" }, "message": "mn10300: only add -mmem-funcs to KBUILD_CFLAGS if gcc supports it\n\ncommit 9957423f035c2071f6d1c5d2f095cdafbeb25ad7 upstream.\n\nIt seems the current (gcc 4.6.3) no longer provides this so make it\nconditional.\n\nAs reported by Tony before, the mn10300 architecture cross-compiles with\ngcc-4.6.3 if -mmem-funcs is not added to KBUILD_CFLAGS.\n\nReported-by: Tony Breeds \u003ctony@bakeyournoodle.com\u003e\nSigned-off-by: Geert Uytterhoeven \u003cgeert@linux-m68k.org\u003e\nCc: David Howells \u003cdhowells@redhat.com\u003e\nCc: Koichi Yasutake \u003cyasutake.koichi@jp.panasonic.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "4a3bb116ee8ab2f912fdb6d2af40028b15825151", "tree": "d83784241a15dd195a8d15c9c14241a645c60fca", "parents": [ "b4d4dc33a372aaee2205d4506b4c7ead6275067d" ], "author": { "name": "Avi Kivity", "email": "avi@redhat.com", "time": "Wed Aug 22 13:03:48 2012 +0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Oct 07 08:32:29 2012 -0700" }, "message": "x86/alternatives: Fix p6 nops on non-modular kernels\n\ncommit cb09cad44f07044d9810f18f6f9a6a6f3771f979 upstream.\n\nProbably a leftover from the early days of self-patching, p6nops\nare marked __initconst_or_module, which causes them to be\ndiscarded in a non-modular kernel. If something later triggers\npatching, it will overwrite kernel code with garbage.\n\nReported-by: Tomas Racek \u003ctracek@redhat.com\u003e\nSigned-off-by: Avi Kivity \u003cavi@redhat.com\u003e\nCc: Michael Tokarev \u003cmjt@tls.msk.ru\u003e\nCc: Borislav Petkov \u003cborislav.petkov@amd.com\u003e\nCc: Marcelo Tosatti \u003cmtosatti@redhat.com\u003e\nCc: qemu-devel@nongnu.org\nCc: Anthony Liguori \u003canthony@codemonkey.ws\u003e\nCc: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nCc: Alan Cox \u003calan@lxorguk.ukuu.org.uk\u003e\nCc: Alan Cox \u003calan@linux.intel.com\u003e\nLink: http://lkml.kernel.org/r/5034AE84.90708@redhat.com\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Ben Jencks \u003cben@bjencks.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "bba5a67bba4c56ab0ce632d7a3e1a651d9162b9e", "tree": "a5f6c2031dbe52ba45118c2265c9f3c23c7ef3a0", "parents": [ "804f6a4a4745ce54f3afa76b3d2270b385f565f8" ], "author": { "name": "Vikram Pandita", "email": "vikram.pandita@ti.com", "time": "Thu Sep 06 15:45:37 2012 +0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Oct 07 08:32:25 2012 -0700" }, "message": "serial: omap: fix software flow control\n\ncommit 957ee7270d632245b43f6feb0e70d9a5e9ea6cf6 upstream.\n\nSoftware flow control register bits were not defined correctly.\n\nAlso clarify the IXON and IXOFF logic to reflect what userspace wants.\n\nTested-by: Shubhrajyoti D \u003cshubhrajyoti@ti.com\u003e\nSigned-off-by: Vikram Pandita \u003cvikram.pandita@ti.com\u003e\nSigned-off-by: Shubhrajyoti D \u003cshubhrajyoti@ti.com\u003e\nAcked-by: Tony Lindgren \u003ctony@atomide.com\u003e\nSigned-off-by: Felipe Balbi \u003cbalbi@ti.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9effb1b2599c3ae0be3c5bf3f6187667fe2a6e70", "tree": "7c8d54448e1d169d363da93c0f19ece56303a70a", "parents": [ "446d14d4c51010379f7f12f3616773e7e7fb47d9" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Fri Jul 13 19:15:40 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:49 2012 -0700" }, "message": "ARM: 7467/1: mutex: use generic xchg-based implementation for ARMv6+\n\ncommit a76d7bd96d65fa5119adba97e1b58d95f2e78829 upstream.\n\nThe open-coded mutex implementation for ARMv6+ cores suffers from a\nsevere lack of barriers, so in the uncontended case we don\u0027t actually\nprotect any accesses performed during the critical section.\n\nFurthermore, the code is largely a duplication of the ARMv6+ atomic_dec\ncode but optimised to remove a branch instruction, as the mutex fastpath\nwas previously inlined. Now that this is executed out-of-line, we can\nreuse the atomic access code for the locking (in fact, we use the xchg\ncode as this produces shorter critical sections).\n\nThis patch uses the generic xchg based implementation for mutexes on\nARMv6+, which introduces barriers to the lock/unlock operations and also\nhas the benefit of removing a fair amount of inline assembly code.\n\nAcked-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nAcked-by: Nicolas Pitre \u003cnico@linaro.org\u003e\nReported-by: Shan Kang \u003ckangshan0910@gmail.com\u003e\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cb2184097168d9ee97126d8284a501759f6d1367", "tree": "728f7a345501f921e748a4a17e73339f49ebc87b", "parents": [ "e85f60c9fc3d5ecc66e6598c0e487aa5c4b7feeb" ], "author": { "name": "Timur Tabi", "email": "timur@freescale.com", "time": "Mon Jul 23 15:43:32 2012 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:37 2012 -0700" }, "message": "powerpc/85xx: p1022ds: fix DIU/LBC switching with NAND enabled\n\ncommit 896c01cb4bb3cfc2c0ea9873fa7a9f8bd0a7c8d8 upstream.\n\nIn order for indirect mode on the PIXIS to work properly, both chip selects\nneed to be set to GPCM mode, otherwise writes to the chip select base\naddresses will not actually post to the local bus -- they\u0027ll go to the\nNAND controller instead. Therefore, we need to set BR0 and BR1 to GPCM\nmode before switching to indirect mode.\n\nSigned-off-by: Timur Tabi \u003ctimur@freescale.com\u003e\nSigned-off-by: Kumar Gala \u003cgalak@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e85f60c9fc3d5ecc66e6598c0e487aa5c4b7feeb", "tree": "c06136af613eae207b7bb31afda7260cf44c533a", "parents": [ "3dcb53637949c288a1ff2a06ee3c0a212ace6ef1" ], "author": { "name": "Timur Tabi", "email": "timur@freescale.com", "time": "Fri Jul 13 14:28:42 2012 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:37 2012 -0700" }, "message": "powerpc/85xx: p1022ds: disable the NAND flash node if video is enabled\n\ncommit 6269f2584a359766f53005c676daff8aee60cbed upstream.\n\nThe Freescale P1022 has a unique pin muxing \"feature\" where the DIU video\ncontroller\u0027s video signals are muxed with 24 of the local bus address signals.\nWhen the DIU is enabled, the bulk of the local bus is disabled, preventing\naccess to memory-mapped devices like NAND flash and the pixis FPGA.\n\nTherefore, if the DIU is going to be enabled, then memory-mapped devices on\nthe localbus, like NAND flash, need to be disabled.\n\nThis patch is similar to \"powerpc/85xx: p1022ds: disable the NOR flash node\nif video is enabled\", except that it disables the NAND flash node instead.\nThis PIXIS node needs to remain enabled because it is used by platform code\nto switch into indirect mode.\n\nSigned-off-by: Timur Tabi \u003ctimur@freescale.com\u003e\nSigned-off-by: Kumar Gala \u003cgalak@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n\n" }, { "commit": "6c9e62877051270d20e34c0c3652e36f1cc37c04", "tree": "f800ecdea2c1fe845463755f6bd744883e6eb31d", "parents": [ "6adebb0e1d4820435e0c6739b0de20a196cc20d5" ], "author": { "name": "Alan Cox", "email": "alan@linux.intel.com", "time": "Tue May 15 18:44:15 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:33 2012 -0700" }, "message": "x86: Fix boot on Twinhead H12Y\n\ncommit 80b3e557371205566a71e569fbfcce5b11f92dbe upstream.\n\nDespite lots of investigation into why this is needed we don\u0027t\nknow or have an elegant cure. The only answer found on this\nlaptop is to mark a problem region as used so that Linux doesn\u0027t\nput anything there.\n\nCurrently all the users add reserve\u003d command lines and anyone\nnot knowing this needs to find the magic page that documents it.\nAutomate it instead.\n\nSigned-off-by: Alan Cox \u003calan@linux.intel.com\u003e\nTested-and-bugfixed-by: Arne Fitzenreiter \u003carne@fitzenreiter.de\u003e\nResolves-bug: https://bugzilla.kernel.org/show_bug.cgi?id\u003d10231\nLink: http://lkml.kernel.org/r/20120515174347.5109.94551.stgit@bluebook\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "870fefcd916e9766ff3ac689aa87e9f3abbe9381", "tree": "51ff1eb80eecc8be6c8f4e21b9573f30f9e7aad6", "parents": [ "0ed92b21f3807633c70f7565f92b034ef8bf4b1c" ], "author": { "name": "Jovi Zhang", "email": "bookjovi@gmail.com", "time": "Wed Aug 22 10:34:08 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:09 2012 -0700" }, "message": "MIPS: mm: Add compound tail page _mapcount when mapped\n\ncommit af89fa3986b9d034a286544ab1ed95096496a2f9 upstream.\n\nSee commit b6999b191 which did the same modification for x86\u0027s mm/gup,\n\nQuote from commit b6999b191:\n \"If compound pages are used and the page is a\n tail page, gup_huge_pmd() increases _mapcount to record tail page are\n mapped while gup_huge_pud does not do that.\"\n\n[ralf@linux-mips.org: fixed rejects caused by the original patch getting\nlinewrapped.]\n\nSigned-off-by: Jovi Zhang \u003cboojovi@gmail.com\u003e\nCc: Youquan Song \u003cyouquan.song@intel.com\u003e\nCc: Andi Kleen \u003candi@firstfloor.org\u003e\nPatchwork: https://patchwork.linux-mips.org/patch/4291/\nSigned-off-by: Ralf Baechle \u003cralf@linux-mips.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dca2dd18c62e3b90cb71534e0a715d246ce7196d", "tree": "4cfcbca9466bbc0314b372eaa11ac0d11adb1410", "parents": [ "9f8a301630c67302cab77da0c4cb06272a95459d" ], "author": { "name": "Matthew Leach", "email": "matthew.leach@arm.com", "time": "Tue Sep 11 17:56:57 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:08 2012 -0700" }, "message": "ARM: 7532/1: decompressor: reset SCTLR.TRE for VMSA ARMv7 cores\n\ncommit e1e5b7e4251c7538ca08c2c5545b0c2fbd8a6635 upstream.\n\nThis patch zeroes the SCTLR.TRE bit prior to setting the mapping as\ncacheable for ARMv7 cores in the decompressor, ensuring that the\nmemory region attributes are obtained from the C and B bits, not from\nthe page tables.\n\nCc: Nicolas Pitre \u003cnico@fluxnic.net\u003e\nReviewed-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Matthew Leach \u003cmatthew.leach@arm.com\u003e\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "02fc6e74ca8c7751b7764894fb4c9da5609c79b5", "tree": "c52b4123d27c2fe8c82d2abfdb8148d10ffd560d", "parents": [ "449efd1d33fcf40a81f902ceed6a21a406f8d105" ], "author": { "name": "Konrad Rzeszutek Wilk", "email": "konrad.wilk@oracle.com", "time": "Fri Aug 17 10:22:37 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:06 2012 -0700" }, "message": "xen/boot: Disable NUMA for PV guests.\n\ncommit 8d54db795dfb1049d45dc34f0dddbc5347ec5642 upstream.\n\nThe hypervisor is in charge of allocating the proper \"NUMA\" memory\nand dealing with the CPU scheduler to keep them bound to the proper\nNUMA node. The PV guests (and PVHVM) have no inkling of where they\nrun and do not need to know that right now. In the future we will\nneed to inject NUMA configuration data (if a guest spans two or more\nNUMA nodes) so that the kernel can make the right choices. But those\npatches are not yet present.\n\nIn the meantime, disable the NUMA capability in the PV guest, which\nalso fixes a bootup issue. Andre says:\n\n\"we see Dom0 crashes due to the kernel detecting the NUMA topology not\nby ACPI, but directly from the northbridge (CONFIG_AMD_NUMA).\n\nThis will detect the actual NUMA config of the physical machine, but\nwill crash about the mismatch with Dom0\u0027s virtual memory. Variation of\nthe theme: Dom0 sees what it\u0027s not supposed to see.\n\nThis happens with the said config option enabled and on a machine where\nthis scanning is still enabled (K8 and Fam10h, not Bulldozer class)\n\nWe have this dump then:\nNUMA: Warning: node ids are out of bound, from\u003d-1 to\u003d-1 distance\u003d10\nScanning NUMA topology in Northbridge 24\nNumber of physical nodes 4\nNode 0 MemBase 0000000000000000 Limit 0000000040000000\nNode 1 MemBase 0000000040000000 Limit 0000000138000000\nNode 2 MemBase 0000000138000000 Limit 00000001f8000000\nNode 3 MemBase 00000001f8000000 Limit 0000000238000000\nInitmem setup node 0 0000000000000000-0000000040000000\n NODE_DATA [000000003ffd9000 - 000000003fffffff]\nInitmem setup node 1 0000000040000000-0000000138000000\n NODE_DATA [0000000137fd9000 - 0000000137ffffff]\nInitmem setup node 2 0000000138000000-00000001f8000000\n NODE_DATA [00000001f095e000 - 00000001f0984fff]\nInitmem setup node 3 00000001f8000000-0000000238000000\nCannot find 159744 bytes in node 3\nBUG: unable to handle kernel NULL pointer dereference at (null)\nIP: [\u003cffffffff81d220e6\u003e] __alloc_bootmem_node+0x43/0x96\nPid: 0, comm: swapper Not tainted 3.3.6 #1 AMD Dinar/Dinar\nRIP: e030:[\u003cffffffff81d220e6\u003e] [\u003cffffffff81d220e6\u003e] __alloc_bootmem_node+0x43/0x96\n.. snip..\n [\u003cffffffff81d23024\u003e] sparse_early_usemaps_alloc_node+0x64/0x178\n [\u003cffffffff81d23348\u003e] sparse_init+0xe4/0x25a\n [\u003cffffffff81d16840\u003e] paging_init+0x13/0x22\n [\u003cffffffff81d07fbb\u003e] setup_arch+0x9c6/0xa9b\n [\u003cffffffff81683954\u003e] ? printk+0x3c/0x3e\n [\u003cffffffff81d01a38\u003e] start_kernel+0xe5/0x468\n [\u003cffffffff81d012cf\u003e] x86_64_start_reservations+0xba/0xc1\n [\u003cffffffff81007153\u003e] ? xen_setup_runstate_info+0x2c/0x36\n [\u003cffffffff81d050ee\u003e] xen_start_kernel+0x565/0x56c\n\"\n\nso we just disable NUMA scanning by setting numa_off\u003d1.\n\nReported-and-Tested-by: Andre Przywara \u003candre.przywara@amd.com\u003e\nAcked-by: Andre Przywara \u003candre.przywara@amd.com\u003e\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "449efd1d33fcf40a81f902ceed6a21a406f8d105", "tree": "2369eb51e11ae3f8ce450055593a6649e7675980", "parents": [ "967c0e4ab954d228ca87d85c523ae8a65c03cc5e" ], "author": { "name": "Stefano Stabellini", "email": "stefano.stabellini@eu.citrix.com", "time": "Wed Sep 12 12:44:30 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:06 2012 -0700" }, "message": "xen/m2p: do not reuse kmap_op-\u003edev_bus_addr\n\ncommit 2fc136eecd0c647a6b13fcd00d0c41a1a28f35a5 upstream.\n\nIf the caller passes a valid kmap_op to m2p_add_override, we use\nkmap_op-\u003edev_bus_addr to store the original mfn, but dev_bus_addr is\npart of the interface with Xen and if we are batching the hypercalls it\nmight not have been written by the hypervisor yet. That means that later\non Xen will write to it and we\u0027ll think that the original mfn is\nactually what Xen has written to it.\n\nRather than \"stealing\" struct members from kmap_op, keep using\npage-\u003eindex to store the original mfn and add another parameter to\nm2p_remove_override to get the corresponding kmap_op instead.\nIt is now responsibility of the caller to keep track of which kmap_op\ncorresponds to a particular page in the m2p_override (gntdev, the only\nuser of this interface that passes a valid kmap_op, is already doing that).\n\nReported-and-Tested-By: Sander Eikelenboom \u003clinux@eikelenboom.it\u003e\nSigned-off-by: Stefano Stabellini \u003cstefano.stabellini@eu.citrix.com\u003e\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e3c9398035cbf79a2ab75c2f43de999fc9a726f4", "tree": "c23687b0b8b6b70ae462a07fd85c5395d7dc78ed", "parents": [ "cf499a04f9b5c8d2218257046b66b3062401673a" ], "author": { "name": "Mel Gorman", "email": "mgorman@suse.de", "time": "Sun Aug 19 14:41:03 2012 +1200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:55 2012 -0700" }, "message": "Redefine ATOMIC_INIT and ATOMIC64_INIT to drop the casts\n\ncommit 67a806d9499353fabd5b5ff07337f3aa88a1c3ba upstream.\n\nThe following build error occurred during an alpha build:\n\n net/core/sock.c:274:36: error: initializer element is not constant\n\nDave Anglin says:\n\u003e Here is the line in sock.i:\n\u003e\n\u003e struct static_key memalloc_socks \u003d ((struct static_key) { .enabled \u003d\n\u003e ((atomic_t) { (0) }) });\n\nThe above line contains two compound literals. It also uses a designated\ninitializer to initialize the field enabled. A compound literal is not a\nconstant expression.\n\nThe location of the above statement isn\u0027t fully clear, but if a compound\nliteral occurs outside the body of a function, the initializer list must\nconsist of constant expressions.\n\nSigned-off-by: Mel Gorman \u003cmgorman@suse.de\u003e\nSigned-off-by: Fengguang Wu \u003cfengguang.wu@intel.com\u003e\nSigned-off-by: Michael Cree \u003cmcree@orcon.net.nz\u003e\nAcked-by: Matt Turner \u003cmattst88@gmail.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "93ee70835a254181a9d9c5750e9301b70899ad90", "tree": "e6b82ddb5bf1ce512d86a7c5c9afe84629743809", "parents": [ "d409354d1b8a1e47b8f29887179949ec951ffe83" ], "author": { "name": "Robert Richter", "email": "robert.richter@amd.com", "time": "Thu Jul 19 18:28:26 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:55 2012 -0700" }, "message": "oprofile, s390: Fix uninitialized memory access when writing to oprofilefs\n\ncommit 81ff3478d9ba7f0b48b0abef740e542fd83adf79 upstream.\n\nIf oprofilefs_ulong_from_user() is called with count equals zero, *val\nremains unchanged. Depending on the implementation it might be\nuninitialized. Fixing users of oprofilefs_ulong_ from_user().\n\nWe missed these s390 changes with:\n\n 913050b oprofile: Fix uninitialized memory access when writing to writing to oprofilefs\n\nSigned-off-by: Robert Richter \u003crobert.richter@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "4dbbba47b19e4e2902a3b5115569e97c210c3297", "tree": "622c4ac59d1b207960911cad5e0aa9f5eefb6d88", "parents": [ "6252fbdc0a40c20a21b24d7bfccf3c08ea9b10dc" ], "author": { "name": "Russell King", "email": "rmk+kernel@arm.linux.org.uk", "time": "Sat Aug 25 09:03:15 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:52 2012 -0700" }, "message": "ARM: Fix ioremap() of address zero\n\ncommit a849088aa1552b1a28eea3daff599ee22a734ae3 upstream.\n\nMurali Nalajala reports a regression that ioremapping address zero\nresults in an oops dump:\n\nUnable to handle kernel paging request at virtual address fa200000\npgd \u003d d4f80000\n[fa200000] *pgd\u003d00000000\nInternal error: Oops: 5 [#1] PREEMPT SMP ARM\nModules linked in:\nCPU: 0 Tainted: G W (3.4.0-g3b5f728-00009-g638207a #13)\nPC is at msm_pm_config_rst_vector_before_pc+0x8/0x30\nLR is at msm_pm_boot_config_before_pc+0x18/0x20\npc : [\u003cc0078f84\u003e] lr : [\u003cc007903c\u003e] psr: a0000093\nsp : c0837ef0 ip : cfe00000 fp : 0000000d\nr10: da7efc17 r9 : 225c4278 r8 : 00000006\nr7 : 0003c000 r6 : c085c824 r5 : 00000001 r4 : fa101000\nr3 : fa200000 r2 : c095080c r1 : 002250fc r0 : 00000000\nFlags: NzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel\nControl: 10c5387d Table: 25180059 DAC: 00000015\n[\u003cc0078f84\u003e] (msm_pm_config_rst_vector_before_pc+0x8/0x30) from [\u003cc007903c\u003e] (msm_pm_boot_config_before_pc+0x18/0x20)\n[\u003cc007903c\u003e] (msm_pm_boot_config_before_pc+0x18/0x20) from [\u003cc007a55c\u003e] (msm_pm_power_collapse+0x410/0xb04)\n[\u003cc007a55c\u003e] (msm_pm_power_collapse+0x410/0xb04) from [\u003cc007b17c\u003e] (arch_idle+0x294/0x3e0)\n[\u003cc007b17c\u003e] (arch_idle+0x294/0x3e0) from [\u003cc000eed8\u003e] (default_idle+0x18/0x2c)\n[\u003cc000eed8\u003e] (default_idle+0x18/0x2c) from [\u003cc000f254\u003e] (cpu_idle+0x90/0xe4)\n[\u003cc000f254\u003e] (cpu_idle+0x90/0xe4) from [\u003cc057231c\u003e] (rest_init+0x88/0xa0)\n[\u003cc057231c\u003e] (rest_init+0x88/0xa0) from [\u003cc07ff890\u003e] (start_kernel+0x3a8/0x40c)\nCode: c0704256 e12fff1e e59f2020 e5923000 (e5930000)\n\nThis is caused by the \u0027reserved\u0027 entries which we insert (see\n19b52abe3c5d7 - ARM: 7438/1: fill possible PMD empty section gaps)\nwhich get matched for physical address zero.\n\nResolve this by marking these reserved entries with a different flag.\n\nTested-by: Murali Nalajala \u003cmnalajal@codeaurora.org\u003e\nAcked-by: Nicolas Pitre \u003cnico@linaro.org\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8cc876def310b034ab0e0775a14d1a49472d7f5f", "tree": "5a1e9eafd41793894d0e686b00362fb26510d075", "parents": [ "eff605bb6c699aae80b199010f0beb26563fc399" ], "author": { "name": "Russell King", "email": "rmk+kernel@arm.linux.org.uk", "time": "Fri Sep 07 18:22:28 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:52 2012 -0700" }, "message": "ARM: 7527/1: uaccess: explicitly check __user pointer when !CPU_USE_DOMAINS\n\ncommit 8404663f81d212918ff85f493649a7991209fa04 upstream.\n\nThe {get,put}_user macros don\u0027t perform range checking on the provided\n__user address when !CPU_HAS_DOMAINS.\n\nThis patch reworks the out-of-line assembly accessors to check the user\naddress against a specified limit, returning -EFAULT if is is out of\nrange.\n\n[will: changed get_user register allocation to match put_user]\n[rmk: fixed building on older ARM architectures]\n\nReported-by: Catalin Marinas \u003ccatalin.marinas@arm.com\u003e\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "eff605bb6c699aae80b199010f0beb26563fc399", "tree": "2ea63babae83d99425cdcaa65967e17323333cdd", "parents": [ "dab510cf4641187bf69e1b5e1be014848c1b473f" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Fri Sep 07 18:21:44 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:52 2012 -0700" }, "message": "ARM: 7526/1: traps: send SIGILL if get_user fails on undef handling path\n\ncommit 2b2040af0b64cd93e5d4df2494c4486cf604090d upstream.\n\nget_user may fail to load from the provided __user address due to an\nunhandled fault generated by the access.\n\nIn the case of the undefined instruction trap, this results in failure\nto load the faulting instruction, in which case we should send SIGILL to\nthe task rather than continue with potentially uninitialised data.\n\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dab510cf4641187bf69e1b5e1be014848c1b473f", "tree": "fb3bdee6f93b5ab49d3d9518b4b1e44723013aa2", "parents": [ "3518fd322d6b13b278830cc41e26d6011c3641fa" ], "author": { "name": "David Brown", "email": "davidb@codeaurora.org", "time": "Tue Sep 04 21:36:37 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:51 2012 -0700" }, "message": "ARM: 7513/1: Make sure dtc is built before running it\n\ncommit 70b0476a2394de4f4e32e0b67288d80ff71ca963 upstream.\n\n\u0027make dtbs\u0027 in a clean tree will try running the dtc before actually\nbuilding it. Make these rules depend upon the scripts to build it.\n\nSigned-off-by: David Brown \u003cdavidb@codeaurora.org\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3518fd322d6b13b278830cc41e26d6011c3641fa", "tree": "af45c67a6d670baf83cd4cf8ddc2914b79a11fa5", "parents": [ "a18a65bd69dfdb28e729f22f9ca171fa81544dc4" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Thu Aug 16 18:55:44 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:51 2012 -0700" }, "message": "ARM: 7496/1: hw_breakpoint: don\u0027t rely on dfsr to show watchpoint access type\n\ncommit bf8801145c01ab600f8df66e8c879ac642fa5846 upstream.\n\nFrom ARM debug architecture v7.1 onwards, a watchpoint exception causes\nthe DFAR to be updated with the faulting data address. However, DFSR.WnR\ntakes an UNKNOWN value and therefore cannot be used in general to\ndetermine the access type that triggered the watchpoint.\n\nThis patch forbids watchpoints without an overflow handler from\nspecifying a specific access type (load/store). Those with overflow\nhandlers must be able to handle false positives potentially triggered by\na watchpoint of a different access type on the same address. For\nSIGTRAP-based handlers (i.e. ptrace), this should have no impact.\n\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "72961d91696071841fa013f11f686eaa7e2d0996", "tree": "31813ab89c9cf0013c067e1525816d271c7ab33f", "parents": [ "bbebafa0d9507206793a05fbeb010eafb1fdb0d0" ], "author": { "name": "Andreas Herrmann", "email": "andreas.herrmann3@amd.com", "time": "Tue Jul 31 15:41:45 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:34 2012 -0700" }, "message": "x86, microcode, AMD: Fix broken ucode patch size check\n\ncommit 36bf50d7697be18c6bfd0401e037df10bff1e573 upstream.\n\nThis issue was recently observed on an AMD C-50 CPU where a patch of\nmaximum size was applied.\n\nCommit be62adb49294 (\"x86, microcode, AMD: Simplify ucode verification\")\nadded current_size in get_matching_microcode(). This is calculated as\nsize of the ucode patch + 8 (ie. size of the header). Later this is\ncompared against the maximum possible ucode patch size for a CPU family.\nAnd of course this fails if the patch has already maximum size.\n\nSigned-off-by: Andreas Herrmann \u003candreas.herrmann3@amd.com\u003e\nSigned-off-by: Borislav Petkov \u003cborislav.petkov@amd.com\u003e\nLink: http://lkml.kernel.org/r/1344361461-10076-1-git-send-email-bp@amd64.org\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9db2bc1e0363bb9401e6407b198463c01f32dd84", "tree": "76bf494811a3312cd8892a75f41f133f42dc8036", "parents": [ "df0b962e0900ec0b2b93eac2795e3e65cc18052f" ], "author": { "name": "Mel Gorman", "email": "mgorman@suse.de", "time": "Mon Jul 23 12:16:19 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:33 2012 -0700" }, "message": "PARISC: Redefine ATOMIC_INIT and ATOMIC64_INIT to drop the casts\n\ncommit bba3d8c3b3c0f2123be5bc687d1cddc13437c923 upstream.\n\nThe following build error occured during a parisc build with\nswap-over-NFS patches applied.\n\nnet/core/sock.c:274:36: error: initializer element is not constant\nnet/core/sock.c:274:36: error: (near initialization for \u0027memalloc_socks\u0027)\nnet/core/sock.c:274:36: error: initializer element is not constant\n\nDave Anglin says:\n\u003e Here is the line in sock.i:\n\u003e\n\u003e struct static_key memalloc_socks \u003d ((struct static_key) { .enabled \u003d\n\u003e ((atomic_t) { (0) }) });\n\nThe above line contains two compound literals. It also uses a designated\ninitializer to initialize the field enabled. A compound literal is not a\nconstant expression.\n\nThe location of the above statement isn\u0027t fully clear, but if a compound\nliteral occurs outside the body of a function, the initializer list must\nconsist of constant expressions.\n\nReported-by: Fengguang Wu \u003cfengguang.wu@intel.com\u003e\nSigned-off-by: Mel Gorman \u003cmgorman@suse.de\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Parallels.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "242fa18ad8d4665c151bdd5c34ac34a8e701fff7", "tree": "70ed336dd84ad1e4a1bb710a8e2c4b0ef4027917", "parents": [ "fe83a638356c2a7ea4e429ea5ce627d5001757fe" ], "author": { "name": "Paul Mackerras", "email": "paulus@samba.org", "time": "Tue Sep 04 18:33:08 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:22 2012 -0700" }, "message": "powerpc: Make sure IPI handlers see data written by IPI senders\n\ncommit 9fb1b36ca1234e64a5d1cc573175303395e3354d upstream.\n\nWe have been observing hangs, both of KVM guest vcpu tasks and more\ngenerally, where a process that is woken doesn\u0027t properly wake up and\ncontinue to run, but instead sticks in TASK_WAKING state. This\nhappens because the update of rq-\u003ewake_list in ttwu_queue_remote()\nis not ordered with the update of ipi_message in\nsmp_muxed_ipi_message_pass(), and the reading of rq-\u003ewake_list in\nscheduler_ipi() is not ordered with the reading of ipi_message in\nsmp_ipi_demux(). Thus it is possible for the IPI receiver not to see\nthe updated rq-\u003ewake_list and therefore conclude that there is nothing\nfor it to do.\n\nIn order to make sure that anything done before smp_send_reschedule()\nis ordered before anything done in the resulting call to scheduler_ipi(),\nthis adds barriers in smp_muxed_message_pass() and smp_ipi_demux().\nThe barrier in smp_muxed_message_pass() is a full barrier to ensure that\nthere is a full ordering between the smp_send_reschedule() caller and\nscheduler_ipi(). In smp_ipi_demux(), we use xchg() rather than\nxchg_local() because xchg() includes release and acquire barriers.\nUsing xchg() rather than xchg_local() makes sense given that\nipi_message is not just accessed locally.\n\nThis moves the barrier between setting the message and calling the\ncause_ipi() function into the individual cause_ipi implementations.\nMost of them -- those that used outb, out_8 or similar -- already had\na full barrier because out_8 etc. include a sync before the MMIO\nstore. This adds an explicit barrier in the two remaining cases.\n\nThese changes made no measurable difference to the speed of IPIs as\nmeasured using a simple ping-pong latency test across two CPUs on\ndifferent cores of a POWER7 machine.\n\nThe analysis of the reason why processes were not waking up properly\nis due to Milton Miller.\n\nReported-by: Milton Miller \u003cmiltonm@bga.com\u003e\nSigned-off-by: Paul Mackerras \u003cpaulus@samba.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "fe83a638356c2a7ea4e429ea5ce627d5001757fe", "tree": "e6e5a81bd2d4d17750778ecccd46257add2b2c15", "parents": [ "c68ef2b5cb50b54e7be25f53186ebf20220c6476" ], "author": { "name": "Anton Blanchard", "email": "anton@samba.org", "time": "Mon Sep 03 16:51:10 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:22 2012 -0700" }, "message": "powerpc: Restore correct DSCR in context switch\n\ncommit 714332858bfd40dcf8f741498336d93875c23aa7 upstream.\n\nDuring a context switch we always restore the per thread DSCR value.\nIf we aren\u0027t doing explicit DSCR management\n(ie thread.dscr_inherit \u003d\u003d 0) and the default DSCR changed while\nthe process has been sleeping we end up with the wrong value.\n\nCheck thread.dscr_inherit and select the default DSCR or per thread\nDSCR as required.\n\nThis was found with the following test case, when running with\nmore threads than CPUs (ie forcing context switching):\n\nhttp://ozlabs.org/~anton/junkcode/dscr_default_test.c\n\nWith the four patches applied I can run a combination of all\ntest cases successfully at the same time:\n\nhttp://ozlabs.org/~anton/junkcode/dscr_default_test.c\nhttp://ozlabs.org/~anton/junkcode/dscr_explicit_test.c\nhttp://ozlabs.org/~anton/junkcode/dscr_inherit_test.c\n\nSigned-off-by: Anton Blanchard \u003canton@samba.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "c68ef2b5cb50b54e7be25f53186ebf20220c6476", "tree": "d373e4947db60eb93d0be7a022e60529c4b47d31", "parents": [ "59d0622a07571c6344f0e3c71e7a1a71eb8db9e9" ], "author": { "name": "Anton Blanchard", "email": "anton@samba.org", "time": "Mon Sep 03 16:49:47 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:22 2012 -0700" }, "message": "powerpc: Fix DSCR inheritance in copy_thread()\n\ncommit 1021cb268b3025573c4811f1dee4a11260c4507b upstream.\n\nIf the default DSCR is non zero we set thread.dscr_inherit in\ncopy_thread() meaning the new thread and all its children will ignore\nfuture updates to the default DSCR. This is not intended and is\na change in behaviour that a number of our users have hit.\n\nWe just need to inherit thread.dscr and thread.dscr_inherit from\nthe parent which ends up being much simpler.\n\nThis was found with the following test case:\n\nhttp://ozlabs.org/~anton/junkcode/dscr_default_test.c\n\nSigned-off-by: Anton Blanchard \u003canton@samba.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "59d0622a07571c6344f0e3c71e7a1a71eb8db9e9", "tree": "b7e27ef692a8a19da9d42d60cd4301394fc8c3bb", "parents": [ "652f43702b224351b790fd9182744d7946d4cdf6" ], "author": { "name": "Anton Blanchard", "email": "anton@samba.org", "time": "Mon Sep 03 16:48:46 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:22 2012 -0700" }, "message": "powerpc: Keep thread.dscr and thread.dscr_inherit in sync\n\ncommit 00ca0de02f80924dfff6b4f630e1dff3db005e35 upstream.\n\nWhen we update the DSCR either via emulation of mtspr(DSCR) or via\na change to dscr_default in sysfs we don\u0027t update thread.dscr.\nWe will eventually update it at context switch time but there is\na period where thread.dscr is incorrect.\n\nIf we fork at this point we will copy the old value of thread.dscr\ninto the child. To avoid this, always keep thread.dscr in sync with\nreality.\n\nThis issue was found with the following testcase:\n\nhttp://ozlabs.org/~anton/junkcode/dscr_inherit_test.c\n\nSigned-off-by: Anton Blanchard \u003canton@samba.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "652f43702b224351b790fd9182744d7946d4cdf6", "tree": "417d56cf598b44311b7d4664e7348ae9285c3c37", "parents": [ "a9959bb7e1510edb3326beb354e59da0a6a0dab1" ], "author": { "name": "Anton Blanchard", "email": "anton@samba.org", "time": "Mon Sep 03 16:47:56 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:22 2012 -0700" }, "message": "powerpc: Update DSCR on all CPUs when writing sysfs dscr_default\n\ncommit 1b6ca2a6fe56e7697d57348646e07df08f43b1bb upstream.\n\nWriting to dscr_default in sysfs doesn\u0027t actually change the DSCR -\nwe rely on a context switch on each CPU to do the work. There is no\nguarantee we will get a context switch in a reasonable amount of time\nso fire off an IPI to force an immediate change.\n\nThis issue was found with the following test case:\n\nhttp://ozlabs.org/~anton/junkcode/dscr_explicit_test.c\n\nSigned-off-by: Anton Blanchard \u003canton@samba.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e9497730c0f0b2b15006a869a2d3ed6febce5f1b", "tree": "19ba94f89558bf37d98744647c0ed045565349da", "parents": [ "0522ba5d15022bca061c7c73c811eaed916bb369" ], "author": { "name": "Mike Frysinger", "email": "vapier@gentoo.org", "time": "Sat Aug 18 16:11:37 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:21 2012 -0700" }, "message": "x32: Use compat shims for {g,s}etsockopt\n\ncommit 515c7af85ed92696c311c53d53cb4898ff32d784 upstream.\n\nSome of the arguments to {g,s}etsockopt are passed in userland pointers.\nIf we try to use the 64bit entry point, we end up sometimes failing.\n\nFor example, dhcpcd doesn\u0027t run in x32:\n\t# dhcpcd eth0\n\tdhcpcd[1979]: version 5.5.6 starting\n\tdhcpcd[1979]: eth0: broadcasting for a lease\n\tdhcpcd[1979]: eth0: open_socket: Invalid argument\n\tdhcpcd[1979]: eth0: send_raw_packet: Bad file descriptor\n\nThe code in particular is getting back EINVAL when doing:\n\tstruct sock_fprog pf;\n\tsetsockopt(s, SOL_SOCKET, SO_ATTACH_FILTER, \u0026pf, sizeof(pf));\n\nDiving into the kernel code, we can see:\ninclude/linux/filter.h:\n\tstruct sock_fprog {\n\t\tunsigned short len;\n\t\tstruct sock_filter __user *filter;\n\t};\n\nnet/core/sock.c:\n\tcase SO_ATTACH_FILTER:\n\t\tret \u003d -EINVAL;\n\t\tif (optlen \u003d\u003d sizeof(struct sock_fprog)) {\n\t\t\tstruct sock_fprog fprog;\n\n\t\t\tret \u003d -EFAULT;\n\t\t\tif (copy_from_user(\u0026fprog, optval, sizeof(fprog)))\n\t\t\t\tbreak;\n\n\t\t\tret \u003d sk_attach_filter(\u0026fprog, sk);\n\t\t}\n\t\tbreak;\n\narch/x86/syscalls/syscall_64.tbl:\n\t54 common setsockopt sys_setsockopt\n\t55 common getsockopt sys_getsockopt\n\nSo for x64, sizeof(sock_fprog) is 16 bytes. For x86/x32, it\u0027s 8 bytes.\nThis comes down to the pointer being 32bit for x32, which means we need\nto do structure size translation. But since x32 comes in directly to\nsys_setsockopt, it doesn\u0027t get translated like x86.\n\nAfter changing the syscall table and rebuilding glibc with the new kernel\nheaders, dhcp runs fine in an x32 userland.\n\nOddly, it seems like Linus noted the same thing during the initial port,\nbut I guess that was missed/lost along the way:\n\thttps://lkml.org/lkml/2011/8/26/452\n\n[ hpa: tagging for -stable since this is an ABI fix. ]\n\nBugzilla: https://bugs.gentoo.org/423649\nReported-by: Mads \u003cmads@ab3.no\u003e\nSigned-off-by: Mike Frysinger \u003cvapier@gentoo.org\u003e\nLink: http://lkml.kernel.org/r/1345320697-15713-1-git-send-email-vapier@gentoo.org\nCc: H. J. Lu \u003chjl.tools@gmail.com\u003e\nSigned-off-by: H. Peter Anvin \u003chpa@zytor.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "c3a0afddee7ed8979b8d14346376848e0a306850", "tree": "592103144c65d727cf562db177b8240eab2ad84c", "parents": [ "5be8fc241c52f469cd8f2c9e4ebd66ce4ab9df34" ], "author": { "name": "Michal Hocko", "email": "mhocko@suse.cz", "time": "Tue Aug 21 16:15:52 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:06 2012 -0700" }, "message": "mm: hugetlbfs: correctly populate shared pmd\n\ncommit eb48c071464757414538c68a6033c8f8c15196f8 upstream.\n\nEach page mapped in a process\u0027s address space must be correctly\naccounted for in _mapcount. Normally the rules for this are\nstraightforward but hugetlbfs page table sharing is different. The page\ntable pages at the PMD level are reference counted while the mapcount\nremains the same.\n\nIf this accounting is wrong, it causes bugs like this one reported by\nLarry Woodman:\n\n kernel BUG at mm/filemap.c:135!\n invalid opcode: 0000 [#1] SMP\n CPU 22\n Modules linked in: bridge stp llc sunrpc binfmt_misc dcdbas microcode pcspkr acpi_pad acpi]\n Pid: 18001, comm: mpitest Tainted: G W 3.3.0+ #4 Dell Inc. PowerEdge R620/07NDJ2\n RIP: 0010:[\u003cffffffff8112cfed\u003e] [\u003cffffffff8112cfed\u003e] __delete_from_page_cache+0x15d/0x170\n Process mpitest (pid: 18001, threadinfo ffff880428972000, task ffff880428b5cc20)\n Call Trace:\n delete_from_page_cache+0x40/0x80\n truncate_hugepages+0x115/0x1f0\n hugetlbfs_evict_inode+0x18/0x30\n evict+0x9f/0x1b0\n iput_final+0xe3/0x1e0\n iput+0x3e/0x50\n d_kill+0xf8/0x110\n dput+0xe2/0x1b0\n __fput+0x162/0x240\n\nDuring fork(), copy_hugetlb_page_range() detects if huge_pte_alloc()\nshared page tables with the check dst_pte \u003d\u003d src_pte. The logic is if\nthe PMD page is the same, they must be shared. This assumes that the\nsharing is between the parent and child. However, if the sharing is\nwith a different process entirely then this check fails as in this\ndiagram:\n\n parent\n |\n ------------\u003epmd\n src_pte----------\u003e data page\n ^\n other---------\u003epmd--------------------|\n ^\n child-----------|\n dst_pte\n\nFor this situation to occur, it must be possible for Parent and Other to\nhave faulted and failed to share page tables with each other. This is\npossible due to the following style of race.\n\n PROC A PROC B\n copy_hugetlb_page_range copy_hugetlb_page_range\n src_pte \u003d\u003d huge_pte_offset src_pte \u003d\u003d huge_pte_offset\n !src_pte so no sharing !src_pte so no sharing\n\n (time passes)\n\n hugetlb_fault hugetlb_fault\n huge_pte_alloc huge_pte_alloc\n huge_pmd_share huge_pmd_share\n LOCK(i_mmap_mutex)\n find nothing, no sharing\n UNLOCK(i_mmap_mutex)\n LOCK(i_mmap_mutex)\n find nothing, no sharing\n UNLOCK(i_mmap_mutex)\n pmd_alloc pmd_alloc\n LOCK(instantiation_mutex)\n fault\n UNLOCK(instantiation_mutex)\n LOCK(instantiation_mutex)\n fault\n UNLOCK(instantiation_mutex)\n\nThese two processes are not poing to the same data page but are not\nsharing page tables because the opportunity was missed. When either\nprocess later forks, the src_pte \u003d\u003d dst pte is potentially insufficient.\nAs the check falls through, the wrong PTE information is copied in\n(harmless but wrong) and the mapcount is bumped for a page mapped by a\nshared page table leading to the BUG_ON.\n\nThis patch addresses the issue by moving pmd_alloc into huge_pmd_share\nwhich guarantees that the shared pud is populated in the same critical\nsection as pmd. This also means that huge_pte_offset test in\nhuge_pmd_share is serialized correctly now which in turn means that the\nsuccess of the sharing will be higher as the racing tasks see the pud\nand pmd populated together.\n\nRace identified and changelog written mostly by Mel Gorman.\n\n{akpm@linux-foundation.org: attempt to make the huge_pmd_share() comment comprehensible, clean up coding style]\nReported-by: Larry Woodman \u003clwoodman@redhat.com\u003e\nTested-by: Larry Woodman \u003clwoodman@redhat.com\u003e\nReviewed-by: Mel Gorman \u003cmgorman@suse.de\u003e\nSigned-off-by: Michal Hocko \u003cmhocko@suse.cz\u003e\nReviewed-by: Rik van Riel \u003criel@redhat.com\u003e\nCc: David Gibson \u003cdavid@gibson.dropbear.id.au\u003e\nCc: Ken Chen \u003ckenchen@google.com\u003e\nCc: Cong Wang \u003cxiyou.wangcong@gmail.com\u003e\nCc: Hillf Danton \u003cdhillf@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "660345c4411ec182f2b735c3e19106ea468a9184", "tree": "19984742258080973415ccc5358af9eea43fa709", "parents": [ "f998ff53548d95327b6b1543d7b524db26a54d89" ], "author": { "name": "Michael Cree", "email": "mcree@orcon.net.nz", "time": "Sun Aug 19 14:40:56 2012 +1200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:06 2012 -0700" }, "message": "alpha: Don\u0027t export SOCK_NONBLOCK to user space.\n\ncommit a2fa3ccd7b43665fe14cb562761a6c3d26a1d13f upstream.\n\nCurrently we export SOCK_NONBLOCK to user space but that conflicts with\nthe definition from glibc leading to compilation errors in user programs\n(e.g. see Debian bug #658460).\n\nThe generic socket.h restricts the definition of SOCK_NONBLOCK to the\nkernel, as does the MIPS specific socket.h, so let\u0027s do the same on\nAlpha.\n\nSigned-off-by: Michael Cree \u003cmcree@orcon.net.nz\u003e\nAcked-by: Matt Turner \u003cmattst88@gmail.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f998ff53548d95327b6b1543d7b524db26a54d89", "tree": "7768e16d0e545d32fcc6d080d1f63265ebfd21cb", "parents": [ "b030a2c4a494ff09a9ca84a3280f6a327dd7a02f" ], "author": { "name": "Mike Frysinger", "email": "vapier@gentoo.org", "time": "Sun Aug 19 14:41:02 2012 +1200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:06 2012 -0700" }, "message": "alpha: fix fpu.h usage in userspace\n\ncommit 0be421862b857e61964435ffcaa7499cf77a5e5a upstream.\n\nAfter commit ec2212088c42 (\"Disintegrate asm/system.h for Alpha\"), the\nfpu.h header which we install for userland started depending on\nspecial_insns.h which is not installed.\n\nHowever, fpu.h only uses that for __KERNEL__ code, so protect the\ninclusion the same way to avoid build breakage in glibc:\n\n /usr/include/asm/fpu.h:4:31: fatal error: asm/special_insns.h: No such file or directory\n\nReported-by: Matt Turner \u003cmattst88@gentoo.org\u003e\nSigned-off-by: Mike Frysinger \u003cvapier@gentoo.org\u003e\nSigned-off-by: Michael Cree \u003cmcree@orcon.net.nz\u003e\nAcked-by: Matt Turner \u003cmattst88@gmail.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e78e9b4a7848cc1b52678161cbfaa7530efba251", "tree": "fcf0063c9403d326165420abefd5dba0b2922ee3", "parents": [ "830cb0da378e5ec143613069faf250b742456021" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Thu Aug 16 10:40:40 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:05 2012 -0700" }, "message": "ARM: imx: select CPU_FREQ_TABLE when needed\n\ncommit f637c4c9405e21f44cf0045eaf77eddd3a79ca5a upstream.\n\nThe i.MX cpufreq implementation uses the CPU_FREQ_TABLE helpers,\nso it needs to select that code to be built. This problem has\napparently existed since the i.MX cpufreq code was first merged\nin v2.6.37.\n\nBuilding IMX without CPU_FREQ_TABLE results in:\n\narch/arm/plat-mxc/built-in.o: In function `mxc_cpufreq_exit\u0027:\narch/arm/plat-mxc/cpufreq.c:173: undefined reference to `cpufreq_frequency_table_put_attr\u0027\narch/arm/plat-mxc/built-in.o: In function `mxc_set_target\u0027:\narch/arm/plat-mxc/cpufreq.c:84: undefined reference to `cpufreq_frequency_table_target\u0027\narch/arm/plat-mxc/built-in.o: In function `mxc_verify_speed\u0027:\narch/arm/plat-mxc/cpufreq.c:65: undefined reference to `cpufreq_frequency_table_verify\u0027\narch/arm/plat-mxc/built-in.o: In function `mxc_cpufreq_init\u0027:\narch/arm/plat-mxc/cpufreq.c:154: undefined reference to `cpufreq_frequency_table_cpuinfo\u0027\narch/arm/plat-mxc/cpufreq.c:162: undefined reference to `cpufreq_frequency_table_get_attr\u0027\n\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nAcked-by: Shawn Guo \u003cshawn.guo@linaro.org\u003e\nCc: Sascha Hauer \u003cs.hauer@pengutronix.de\u003e\nCc: Yong Shen \u003cyong.shen@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "830cb0da378e5ec143613069faf250b742456021", "tree": "c90e8204305d06202e850b411b8914695410e3e9", "parents": [ "47bca6a5021332b17aa5efc2d66af1018af70ba1" ], "author": { "name": "Shawn Guo", "email": "shawn.guo@linaro.org", "time": "Sat Aug 18 14:27:32 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:05 2012 -0700" }, "message": "ARM: imx6: spin the cpu until hardware takes it down\n\ncommit c944b0b9354ea06ffb0c8a7178949f1185f9f499 upstream.\n\nThough commit 602bf40 (ARM: imx6: exit coherency when shutting down\na cpu) improves the stability of imx6q cpu hotplug a lot, there are\nstill hangs seen with a more stressful hotplug testing.\n\nIt\u0027s expected that once imx_enable_cpu(cpu, false) is called, the cpu\nwill be taken down by hardware immediately, and the code after that\nwill not get any chance to execute. However, this is not always the\ncase from the testing. The cpu could possibly be alive for a few\ncycles before hardware actually takes it down. So rather than letting\ncpu execute some code that could cause a hang in these cycles, let\u0027s\nmake the cpu spin there and wait for hardware to take it down.\n\nSigned-off-by: Shawn Guo \u003cshawn.guo@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "47bca6a5021332b17aa5efc2d66af1018af70ba1", "tree": "3436df804e82ac19c77465cda9200cdbca6f7f9c", "parents": [ "449daa0ed24c186c7fd014e698f37cbb8aaf7a4c" ], "author": { "name": "Konrad Rzeszutek Wilk", "email": "konrad.wilk@oracle.com", "time": "Fri Aug 17 16:43:28 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:04 2012 -0700" }, "message": "xen/setup: Fix one-off error when adding for-balloon PFNs to the P2M.\n\ncommit c96aae1f7f393387d160211f60398d58463a7e65 upstream.\n\nWhen we are finished with return PFNs to the hypervisor, then\npopulate it back, and also mark the E820 MMIO and E820 gaps\nas IDENTITY_FRAMEs, we then call P2M to set areas that can\nbe used for ballooning. We were off by one, and ended up\nover-writting a P2M entry that most likely was an IDENTITY_FRAME.\nFor example:\n\n1-1 mapping on 40000-\u003e40200\n1-1 mapping on bc558-\u003ebc5ac\n1-1 mapping on bc5b4-\u003ebc8c5\n1-1 mapping on bc8c6-\u003ebcb7c\n1-1 mapping on bcd00-\u003e100000\nReleased 614 pages of unused memory\nSet 277889 page(s) to 1-1 mapping\nPopulating 40200-40466 pfn range: 614 pages added\n\n\u003d\u003e here we set from 40466 up to bc559 P2M tree to be\nINVALID_P2M_ENTRY. We should have done it up to bc558.\n\nThe end result is that if anybody is trying to construct\na PTE for PFN bc558 they end up with ~PAGE_PRESENT.\n\nReported-by-and-Tested-by: Andre Przywara \u003candre.przywara@amd.com\u003e\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "588d6b125faae8f369352dedaa4632071b93e78e", "tree": "948e0cd681cd96fab15a7479d3230098b58c57b6", "parents": [ "cef2cf5590819d565db994008a6bbb9f27dd9b41" ], "author": { "name": "Heiko Stuebner", "email": "heiko@sntech.de", "time": "Tue Aug 07 19:12:05 2012 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:04 2012 -0700" }, "message": "ARM: S3C24XX: Fix s3c2410_dma_enqueue parameters\n\ncommit b01858c7806e7e6f6121da2e51c9222fc4d21dc6 upstream.\n\nCommit d670ac019f60 (ARM: SAMSUNG: DMA Cleanup as per sparse) changed the\nprototype of the s3c2410_dma_* functions to use the enum dma_ch instead\nof an generic unsigned int.\n\nIn the s3c24xx dma.c s3c2410_dma_enqueue seems to have been forgotten,\nthe other functions there were changed correctly.\n\nSigned-off-by: Heiko Stuebner \u003cheiko@sntech.de\u003e\nSigned-off-by: Kukjin Kim \u003ckgene.kim@samsung.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cef2cf5590819d565db994008a6bbb9f27dd9b41", "tree": "77de1ff18f51bee0c2ab2f3135f29de27f40b4ca", "parents": [ "8c17041815762b385631d3a680128dca5a9be31b" ], "author": { "name": "Heiko Stuebner", "email": "heiko@sntech.de", "time": "Tue Aug 07 19:11:33 2012 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:04 2012 -0700" }, "message": "ARM: S3C24XX: Add missing DMACH_DT_PROP\n\ncommit e1267371eacf2cbcf580e41f9e64a986cdaf5c1d upstream.\n\nCommit 2b90807549 (spi: s3c64xx: add device tree support) requires\nthe DMACH_DT_PROP element in the dma_ch enum. It\u0027s not used on non-DT\nplatforms but has to be present nevertheless.\n\nSo mimic the dummy-add of DMACH_DT_PROP on s3c64xx for s3c24xx\nmachines, to correct the build breakage for the s3c24xx variants\nusing the s3c64xx-spi-driver.\n\nSigned-off-by: Heiko Stuebner \u003cheiko@sntech.de\u003e\nSigned-off-by: Kukjin Kim \u003ckgene.kim@samsung.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8c17041815762b385631d3a680128dca5a9be31b", "tree": "07bf5fd51b4a60fb729592fadf33af78ae8579e8", "parents": [ "88b67cb1f21cf5059bfbbc2bca7a597b9c58c312" ], "author": { "name": "Jon Hunter", "email": "jon-hunter@ti.com", "time": "Fri Jul 13 15:12:03 2012 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:04 2012 -0700" }, "message": "ARM: OMAP2+: Fix dmtimer set source clock failure\n\ncommit 54f32a35f4d3a653a18a2c8c239f19ae060bd803 upstream.\n\nCalling the dmtimer function omap_dm_timer_set_source() fails if following a\ncall to pm_runtime_put() to disable the timer. For example the following\nsequence would fail to set the parent clock ...\n\n\tomap_dm_timer_stop(gptimer);\n\tomap_dm_timer_set_source(gptimer, OMAP_TIMER_SRC_32_KHZ);\n\nThe following error message would be seen ...\n\nomap_dm_timer_set_source: failed to set timer_32k_ck as parent\n\nThe problem is that, by design, pm_runtime_put() simply decrements the usage\ncount and returns before the timer has actually been disabled. Therefore,\nsetting the parent clock failed because the timer was still active when the\ntrying to set the parent clock. Setting a parent clock will fail if the clock\nyou are setting the parent of has a non-zero usage count. To ensure that this\ndoes not fail use pm_runtime_put_sync() when disabling the timer.\n\nNote that this will not be seen on OMAP1 devices, because these devices do\nnot use the clock framework for dmtimers.\n\nSigned-off-by: Jon Hunter \u003cjon-hunter@ti.com\u003e\nAcked-by: Kevin Hilman \u003ckhilman@ti.com\u003e\nSigned-off-by: Tony Lindgren \u003ctony@atomide.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "88b67cb1f21cf5059bfbbc2bca7a597b9c58c312", "tree": "1b084ca74a93de2815199e5e07efb2531a0981ca", "parents": [ "635a2a845fb26b32b179d7cb7cfb288c91f39933" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Fri Aug 10 19:13:36 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:04 2012 -0700" }, "message": "ARM: 7489/1: errata: fix workaround for erratum #720789 on UP systems\n\ncommit 730a8128cd8978467eb1cf546b11014acb57d433 upstream.\n\nCommit 5a783cbc4836 (\"ARM: 7478/1: errata: extend workaround for erratum\n #720789\") added workarounds for erratum #720789 to the range TLB\ninvalidation functions with the observation that the erratum only\naffects SMP platforms. However, when running an SMP_ON_UP kernel on a\nuniprocessor platform we must take care to preserve the ASID as the\nworkaround is not required.\n\nThis patch ensures that we don\u0027t set the ASID to 0 when flushing the TLB\non such a system, preserving the original behaviour with the workaround\ndisabled.\n\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "635a2a845fb26b32b179d7cb7cfb288c91f39933", "tree": "0fcc6ce3b26db4a5749960f8df00db1136153c3e", "parents": [ "aa2e66e8fc1a25b9ff6f6f448a025b3599a90662" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Fri Aug 10 17:51:19 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:04 2012 -0700" }, "message": "ARM: 7488/1: mm: use 5 bits for swapfile type encoding\n\ncommit f5f2025ef3e2cdb593707cbf87378761f17befbe upstream.\n\nPage migration encodes the pfn in the offset field of a swp_entry_t.\nFor LPAE, we support physical addresses of up to 36 bits (due to\nsparsemem limitations with the size of page flags), requiring 24 bits\nto represent a pfn. A further 3 bits are used to encode a swp_entry into\na pte, leaving 5 bits for the type field. Furthermore, the core code\ndefines MAX_SWAPFILES_SHIFT as 5, so the additional type bit does not\nget used.\n\nThis patch reduces the width of the type field to 5 bits, allowing us\nto create up to 31 swapfiles of 64GB each.\n\nReviewed-by: Catalin Marinas \u003ccatalin.marinas@arm.com\u003e\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "aa2e66e8fc1a25b9ff6f6f448a025b3599a90662", "tree": "83d8c82f5b7f65778e99c14732850160bce17905", "parents": [ "7de4da6fedad1267970c6640e47561c2d38ec0b4" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Fri Aug 10 17:51:18 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:03 2012 -0700" }, "message": "ARM: 7487/1: mm: avoid setting nG bit for user mappings that aren\u0027t present\n\ncommit 47f1204329237a0f8655f5a9f14a38ac81946ca1 upstream.\n\nSwap entries are encoding in ptes such that !pte_present(pte) and\npte_file(pte). The remaining bits of the descriptor are used to identify\nthe swapfile and offset within it to the swap entry.\n\nWhen writing such a pte for a user virtual address, set_pte_at\nunconditionally sets the nG bit, which (in the case of LPAE) will\ncorrupt the swapfile offset and lead to a BUG:\n\n[ 140.494067] swap_free: Unused swap offset entry 000763b4\n[ 140.509989] BUG: Bad page map in process rs:main Q:Reg pte:0ec76800 pmd:8f92e003\n\nThis patch fixes the problem by only setting the nG bit for user\nmappings that are actually present.\n\nReviewed-by: Catalin Marinas \u003ccatalin.marinas@arm.com\u003e\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7de4da6fedad1267970c6640e47561c2d38ec0b4", "tree": "e261e47fd98b8f0b64a8c70130733728d13d2d54", "parents": [ "5ed0dc3c88fd7586d5ea0b615007bbcf1c7cf7ea" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Fri Aug 03 17:24:14 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:03 2012 -0700" }, "message": "ARM: 7483/1: vfp: only advertise VFPv4 in hwcaps if CONFIG_VFPv3 is enabled\n\ncommit 3d9fb0038a9b02febb01efc79a4a5d97f1822a90 upstream.\n\nVFPv4 support depends on the VFPv3 context save/restore code, so only\nadvertise support in the hwcaps if the kernel can actually handle it.\n\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b9247be526627cda981a6901c8db66f03ecb3ea8", "tree": "c54fdf27235bac5fbba565c39e2ac4a86c1749fa", "parents": [ "90f9cb724d38bf4ac4e355d19b1ee697dceea021" ], "author": { "name": "Stefano Stabellini", "email": "stefano.stabellini@eu.citrix.com", "time": "Wed May 23 18:57:20 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Aug 26 15:00:40 2012 -0700" }, "message": "xen: mark local pages as FOREIGN in the m2p_override\n\ncommit b9e0d95c041ca2d7ad297ee37c2e9cfab67a188f upstream.\n\nWhen the frontend and the backend reside on the same domain, even if we\nadd pages to the m2p_override, these pages will never be returned by\nmfn_to_pfn because the check \"get_phys_to_machine(pfn) !\u003d mfn\" will\nalways fail, so the pfn of the frontend will be returned instead\n(resulting in a deadlock because the frontend pages are already locked).\n\nINFO: task qemu-system-i38:1085 blocked for more than 120 seconds.\n\"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\nqemu-system-i38 D ffff8800cfc137c0 0 1085 1 0x00000000\n ffff8800c47ed898 0000000000000282 ffff8800be4596b0 00000000000137c0\n ffff8800c47edfd8 ffff8800c47ec010 00000000000137c0 00000000000137c0\n ffff8800c47edfd8 00000000000137c0 ffffffff82213020 ffff8800be4596b0\nCall Trace:\n [\u003cffffffff81101ee0\u003e] ? __lock_page+0x70/0x70\n [\u003cffffffff81a0fdd9\u003e] schedule+0x29/0x70\n [\u003cffffffff81a0fe80\u003e] io_schedule+0x60/0x80\n [\u003cffffffff81101eee\u003e] sleep_on_page+0xe/0x20\n [\u003cffffffff81a0e1ca\u003e] __wait_on_bit_lock+0x5a/0xc0\n [\u003cffffffff81101ed7\u003e] __lock_page+0x67/0x70\n [\u003cffffffff8106f750\u003e] ? autoremove_wake_function+0x40/0x40\n [\u003cffffffff811867e6\u003e] ? bio_add_page+0x36/0x40\n [\u003cffffffff8110b692\u003e] set_page_dirty_lock+0x52/0x60\n [\u003cffffffff81186021\u003e] bio_set_pages_dirty+0x51/0x70\n [\u003cffffffff8118c6b4\u003e] do_blockdev_direct_IO+0xb24/0xeb0\n [\u003cffffffff811e71a0\u003e] ? ext3_get_blocks_handle+0xe00/0xe00\n [\u003cffffffff8118ca95\u003e] __blockdev_direct_IO+0x55/0x60\n [\u003cffffffff811e71a0\u003e] ? ext3_get_blocks_handle+0xe00/0xe00\n [\u003cffffffff811e91c8\u003e] ext3_direct_IO+0xf8/0x390\n [\u003cffffffff811e71a0\u003e] ? ext3_get_blocks_handle+0xe00/0xe00\n [\u003cffffffff81004b60\u003e] ? xen_mc_flush+0xb0/0x1b0\n [\u003cffffffff81104027\u003e] generic_file_aio_read+0x737/0x780\n [\u003cffffffff813bedeb\u003e] ? gnttab_map_refs+0x15b/0x1e0\n [\u003cffffffff811038f0\u003e] ? find_get_pages+0x150/0x150\n [\u003cffffffff8119736c\u003e] aio_rw_vect_retry+0x7c/0x1d0\n [\u003cffffffff811972f0\u003e] ? lookup_ioctx+0x90/0x90\n [\u003cffffffff81198856\u003e] aio_run_iocb+0x66/0x1a0\n [\u003cffffffff811998b8\u003e] do_io_submit+0x708/0xb90\n [\u003cffffffff81199d50\u003e] sys_io_submit+0x10/0x20\n [\u003cffffffff81a18d69\u003e] system_call_fastpath+0x16/0x1b\n\nThe explanation is in the comment within the code:\n\nWe need to do this because the pages shared by the frontend\n(xen-blkfront) can be already locked (lock_page, called by\ndo_read_cache_page); when the userspace backend tries to use them\nwith direct_IO, mfn_to_pfn returns the pfn of the frontend, so\ndo_blockdev_direct_IO is going to try to lock the same pages\nagain resulting in a deadlock.\n\nA simplified call graph looks like this:\n\npygrub QEMU\n-----------------------------------------------\ndo_read_cache_page io_submit\n | |\nlock_page ext3_direct_IO\n |\n bio_add_page\n |\n lock_page\n\nInternally the xen-blkback uses m2p_add_override to swizzle (temporarily)\na \u0027struct page\u0027 to have a different MFN (so that it can point to another\nguest). It also can easily find out whether another pfn corresponding\nto the mfn exists in the m2p, and can set the FOREIGN bit\nin the p2m, making sure that mfn_to_pfn returns the pfn of the backend.\n\nThis allows the backend to perform direct_IO on these pages, but as a\nside effect prevents the frontend from using get_user_pages_fast on\nthem while they are being shared with the backend.\n\nSigned-off-by: Stefano Stabellini \u003cstefano.stabellini@eu.citrix.com\u003e\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a87531935d7afc5429944c89511c8acbdf467111", "tree": "4b2f3bf7b87f6ee32053508c1b41d704e92d4cae", "parents": [ "bdac2ea27e0237b3c76b1d8a9d7f73a3d6b3ad81" ], "author": { "name": "Heiko Carstens", "email": "heiko.carstens@de.ibm.com", "time": "Wed Aug 08 09:32:20 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Aug 26 15:00:39 2012 -0700" }, "message": "s390/compat: fix mmap compat system calls\n\ncommit e85871218513c54f7dfdb6009043cb638f2fecbe upstream.\n\nThe native 31 bit and the compat behaviour for the mmap system calls differ:\n\nIn native 31 bit mode the passed in address for the mmap system call will be\nunmodified passed to sys_mmap_pgoff().\nIn compat mode however the passed in address will be modified with\ncompat_ptr() which masks out the most significant bit.\n\nThe result is that in native 31 bit mode each mmap request (with MAP_FIXED)\nwill fail where the most significat bit is set, while in compat mode it\nmay succeed.\n\nThis odd behaviour was introduced with d3815898 \"[S390] mmap: add missing\ncompat_ptr conversion to both mmap compat syscalls\".\n\nTo restore a consistent behaviour accross native and compat mode this\npatch functionally reverts the above mentioned commit.\n\nSigned-off-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "bdac2ea27e0237b3c76b1d8a9d7f73a3d6b3ad81", "tree": "fccf9f9a2be56793e0a0851cafc105dbd1193550", "parents": [ "196ad09b956e63131e3d196e490a4dfbb85e875f" ], "author": { "name": "Heiko Carstens", "email": "heiko.carstens@de.ibm.com", "time": "Tue Aug 07 09:48:13 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Aug 26 15:00:39 2012 -0700" }, "message": "s390/compat: fix compat wrappers for process_vm system calls\n\ncommit 82aabdb6f1eb61e0034ec23901480f5dd23db7c4 upstream.\n\nThe compat wrappers incorrectly called the non compat versions of\nthe system process_vm system calls.\n\nSigned-off-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "95c92481f69cf89aa1db689940368c09fb425281", "tree": "acde98d86b0fbe22041ed1cb771641ed986a08cd", "parents": [ "733e9ad978a1530328ff78aff3186c20000e5b4e" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Mon Apr 30 16:21:37 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:33 2012 -0700" }, "message": "Input: eeti_ts: pass gpio value instead of IRQ\n\ncommit 4eef6cbfcc03b294d9d334368a851b35b496ce53 upstream.\n\nThe EETI touchscreen asserts its IRQ line as soon as it has data in its\ninternal buffers. The line is automatically deasserted once all data has\nbeen read via I2C. Hence, the driver has to monitor the GPIO line and\ncannot simply rely on the interrupt handler reception.\n\nIn the current implementation of the driver, irq_to_gpio() is used to\ndetermine the GPIO number from the i2c_client\u0027s IRQ value.\n\nAs irq_to_gpio() is not available on all platforms, this patch changes\nthis and makes the driver ignore the passed in IRQ. Instead, a GPIO is\nadded to the platform_data struct and gpio_to_irq is used to derive the\nIRQ from that GPIO. If this fails, bail out. The driver is only able to\nwork in environments where the touchscreen GPIO can be mapped to an\nIRQ.\n\nWithout this patch, building raumfeld_defconfig results in:\n\ndrivers/input/touchscreen/eeti_ts.c: In function \u0027eeti_ts_irq_active\u0027:\ndrivers/input/touchscreen/eeti_ts.c:65:2: error: implicit declaration of function \u0027irq_to_gpio\u0027 [-Werror\u003dimplicit-function-declaration]\n\nSigned-off-by: Daniel Mack \u003czonque@gmail.com\u003e\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nCc: Dmitry Torokhov \u003cdmitry.torokhov@gmail.com\u003e\nCc: Sven Neumann \u003cs.neumann@raumfeld.com\u003e\nCc: linux-input@vger.kernel.org\nCc: Haojian Zhuang \u003chaojian.zhuang@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0f27ec339c656ab8dc9255ac8a61a1cecd32d599", "tree": "d82471dbb56a1e13f6a5e07f353ae920a1583ebb", "parents": [ "87a266d5801001c09687fb4d755e336bad733c10" ], "author": { "name": "Shawn Guo", "email": "shawn.guo@linaro.org", "time": "Thu Aug 02 22:48:39 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:32 2012 -0700" }, "message": "ARM: dts: imx53-ard: add regulators for lan9220\n\ncommit 1eec0c569523782392b5e6245effddb626213b8c upstream.\n\nSince commit c7e963f (net/smsc911x: Add regulator support), the lan9220\ndevice tree probe fails on imx53-ard board, because the commit makes\nVDD33A and VDDVARIO supplies mandatory for the driver.\n\nAdd a fixed dummy 3V3 supplying lan9220 to fix the regression.\n\nSigned-off-by: Shawn Guo \u003cshawn.guo@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "87a266d5801001c09687fb4d755e336bad733c10", "tree": "76b18fb100ad701c0b6b846f7a1f101768bb1beb", "parents": [ "6213566323948ac7ed0aa4eb78058e77d445b0f8" ], "author": { "name": "Marek Vasut", "email": "marex@denx.de", "time": "Fri Aug 03 20:54:48 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:32 2012 -0700" }, "message": "ARM: mxs: Remove MMAP_MIN_ADDR setting from mxs_defconfig\n\ncommit 3bed491c8d28329e34f8a31e3fe64d03f3a350f1 upstream.\n\nThe CONFIG_DEFAULT_MMAP_MIN_ADDR was set to 65536 in mxs_defconfig,\nthis caused severe breakage of userland applications since the upper\nlimit for ARM is 32768. By default CONFIG_DEFAULT_MMAP_MIN_ADDR is\nset to 4096 and can also be changed via /proc/sys/vm/mmap_min_addr\nif needed.\n\nQuoting Russell King [1]:\n\n\"4096 is also fine for ARM too. There\u0027s not much point in having\ndefconfigs change it - that would just be pure noise in the config\nfiles.\"\n\nthe CONFIG_DEFAULT_MMAP_MIN_ADDR can be removed from the defconfig\naltogether.\n\nThis problem was introduced by commit cde7c41 (ARM: configs: add\ndefconfig for mach-mxs).\n\n[1] http://marc.info/?l\u003dlinux-arm-kernel\u0026m\u003d134401593807820\u0026w\u003d2\n\nSigned-off-by: Marek Vasut \u003cmarex@denx.de\u003e\nCc: Russell King \u003clinux@arm.linux.org.uk\u003e\nCc: Wolfgang Denk \u003cwd@denx.de\u003e\nSigned-off-by: Shawn Guo \u003cshawn.guo@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a05f127752f743db1b53e0309977573566ce5b6f", "tree": "c2d3a25894cf6d5859649d928ccbbf4ba9871360", "parents": [ "a434a3c014dfc52d07efa7817f1339124300aed4" ], "author": { "name": "Borislav Petkov", "email": "borislav.petkov@amd.com", "time": "Thu Jun 21 14:07:16 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:31 2012 -0700" }, "message": "x86, microcode: Sanitize per-cpu microcode reloading interface\n\ncommit c9fc3f778a6a215ace14ee556067c73982b6d40f upstream.\n\nMicrocode reloading in a per-core manner is a very bad idea for both\nmajor x86 vendors. And the thing is, we have such interface with which\nwe can end up with different microcode versions applied on different\ncores of an otherwise homogeneous wrt (family,model,stepping) system.\n\nSo turn off the possibility of doing that per core and allow it only\nsystem-wide.\n\nThis is a minimal fix which we\u0027d like to see in stable too thus the\nmore-or-less arbitrary decision to allow system-wide reloading only on\nthe BSP:\n\n$ echo 1 \u003e /sys/devices/system/cpu/cpu0/microcode/reload\n...\n\nand disable the interface on the other cores:\n\n$ echo 1 \u003e /sys/devices/system/cpu/cpu23/microcode/reload\n-bash: echo: write error: Invalid argument\n\nAlso, allowing the reload only from one CPU (the BSP in\nthat case) doesn\u0027t allow the reload procedure to degenerate\ninto an O(n^2) deal when triggering reloads from all\n/sys/devices/system/cpu/cpuX/microcode/reload sysfs nodes\nsimultaneously.\n\nA more generic fix will follow.\n\nSigned-off-by: Borislav Petkov \u003cborislav.petkov@amd.com\u003e\nCc: Henrique de Moraes Holschuh \u003chmh@hmh.eng.br\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nLink: http://lkml.kernel.org/r/1340280437-7718-2-git-send-email-bp@amd64.org\nSigned-off-by: H. Peter Anvin \u003chpa@zytor.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a434a3c014dfc52d07efa7817f1339124300aed4", "tree": "e691dfa81949dbe01312bc6dfbfb524fafa5982d", "parents": [ "575b5ea19669112f9f7a7e2c09e9cdb914f4683e" ], "author": { "name": "Shuah Khan", "email": "shuahkhan@gmail.com", "time": "Sun May 06 11:11:04 2012 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:31 2012 -0700" }, "message": "x86, microcode: microcode_core.c simple_strtoul cleanup\n\ncommit e826abd523913f63eb03b59746ffb16153c53dc4 upstream.\n\nChange reload_for_cpu() in kernel/microcode_core.c to call kstrtoul()\ninstead of calling obsoleted simple_strtoul().\n\nSigned-off-by: Shuah Khan \u003cshuahkhan@gmail.com\u003e\nReviewed-by: Borislav Petkov \u003cbp@alien8.de\u003e\nLink: http://lkml.kernel.org/r/1336324264.2897.9.camel@lorien2\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nCc: Henrique de Moraes Holschuh \u003chmh@hmh.eng.br\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "26665db4f7fa71c56eeb9205e79927cfc21e70c4", "tree": "8b5dc2c10b8b0aa9c1d1711daf991ae3df30db02", "parents": [ "12dae51a7567bb1e583ee0de6af538db256504db" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Jul 14 20:27:52 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:29 2012 -0700" }, "message": "random: remove rand_initialize_irq()\n\ncommit c5857ccf293968348e5eb4ebedc68074de3dcda6 upstream.\n\nWith the new interrupt sampling system, we are no longer using the\ntimer_rand_state structure in the irq descriptor, so we can stop\ninitializing it now.\n\n[ Merged in fixes from Sedat to find some last missing references to\n rand_initialize_irq() ]\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nSigned-off-by: Sedat Dilek \u003csedat.dilek@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cabf5b0af54cec6a2f9ce674cbc96fc8aa2fc468", "tree": "711098e955a849ef1d79acd8891b3026113d0916", "parents": [ "0295403cd835f7260c6d9262817138f9f1cd8e19" ], "author": { "name": "Alan Cox", "email": "alan@linux.intel.com", "time": "Wed Jul 25 16:28:19 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:10 2012 -0700" }, "message": "x86, nops: Missing break resulting in incorrect selection on Intel\n\ncommit d6250a3f12edb3a86db9598ffeca3de8b4a219e9 upstream.\n\nThe Intel case falls through into the generic case which then changes\nthe values. For cases like the P6 it doesn\u0027t do the right thing so\nthis seems to be a screwup.\n\nSigned-off-by: Alan Cox \u003calan@linux.intel.com\u003e\nLink: http://lkml.kernel.org/n/tip-lww2uirad4skzjlmrm0vru8o@git.kernel.org\nSigned-off-by: H. Peter Anvin \u003chpa@zytor.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "81155539833d8c492261a8fdd91e3e6579c274dd", "tree": "0719efb47a837efc7469af8a554b65673770550c", "parents": [ "85869d9f5da8449613f5631961fe9309f9c2d0ad" ], "author": { "name": "Russell King", "email": "rmk+kernel@arm.linux.org.uk", "time": "Mon Jul 30 19:42:10 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:07 2012 -0700" }, "message": "ARM: Fix undefined instruction exception handling\n\ncommit 15ac49b65024f55c4371a53214879a9c77c4fbf9 upstream.\n\nWhile trying to get a v3.5 kernel booted on the cubox, I noticed that\nVFP does not work correctly with VFP bounce handling. This is because\nof the confusion over 16-bit vs 32-bit instructions, and where PC is\nsupposed to point to.\n\nThe rule is that FP handlers are entered with regs-\u003eARM_pc pointing at\nthe _next_ instruction to be executed. However, if the exception is\nnot handled, regs-\u003eARM_pc points at the faulting instruction.\n\nThis is easy for ARM mode, because we know that the next instruction and\nprevious instructions are separated by four bytes. This is not true of\nThumb2 though.\n\nSince all FP instructions are 32-bit in Thumb2, it makes things easy.\nWe just need to select the appropriate adjustment. Do this by moving\nthe adjustment out of do_undefinstr() into the assembly code, as only\nthe assembly code knows whether it\u0027s dealing with a 32-bit or 16-bit\ninstruction.\n\nAcked-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "85869d9f5da8449613f5631961fe9309f9c2d0ad", "tree": "6f0cbcf1263702e0d24df126786545e882c54698", "parents": [ "7e49f71b7a6268bb9854b91f6fae3f070fb0222e" ], "author": { "name": "Javier Martinez Canillas", "email": "javier@dowhile0.org", "time": "Sat Jul 28 15:19:55 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:06 2012 -0700" }, "message": "ARM: 7480/1: only call smp_send_stop() on SMP\n\ncommit c5dff4ffd327088d85035bec535b7d0c9ea03151 upstream.\n\nOn reboot or poweroff (machine_shutdown()) a call to smp_send_stop() is\nmade (to stop the others CPU\u0027s) when CONFIG_SMP\u003dy.\n\narch/arm/kernel/process.c:\n\nvoid machine_shutdown(void)\n{\n #ifdef CONFIG_SMP\n smp_send_stop();\n #endif\n}\n\nsmp_send_stop() calls the function pointer smp_cross_call(), which is set\non the smp_init_cpus() function for OMAP processors.\n\narch/arm/mach-omap2/omap-smp.c:\n\nvoid __init smp_init_cpus(void)\n{\n...\n\tset_smp_cross_call(gic_raise_softirq);\n...\n}\n\nBut the ARM setup_arch() function only calls smp_init_cpus()\nif CONFIG_SMP\u003dy \u0026\u0026 is_smp().\n\narm/kernel/setup.c:\n\nvoid __init setup_arch(char **cmdline_p)\n{\n...\n #ifdef CONFIG_SMP\n\tif (is_smp())\n\t\tsmp_init_cpus();\n #endif\n...\n}\n\nNewer OMAP CPU\u0027s are SMP machines so omap2plus_defconfig sets\nCONFIG_SMP\u003dy. Unfortunately on an OMAP UP machine is_smp()\nreturns false and smp_init_cpus() is never called and the\nsmp_cross_call() function remains NULL.\n\nIf the machine is rebooted or powered off, smp_send_stop() will\nbe called (since CONFIG_SMP\u003dy) leading to the following error:\n\n[ 42.815551] Restarting system.\n[ 42.819030] Unable to handle kernel NULL pointer dereference at virtual address 00000000\n[ 42.827667] pgd \u003d d7a74000\n[ 42.830566] [00000000] *pgd\u003d96ce7831, *pte\u003d00000000, *ppte\u003d00000000\n[ 42.837249] Internal error: Oops: 80000007 [#1] SMP ARM\n[ 42.842773] Modules linked in:\n[ 42.846008] CPU: 0 Not tainted (3.5.0-rc3-next-20120622-00002-g62e87ba-dirty #44)\n[ 42.854278] PC is at 0x0\n[ 42.856994] LR is at smp_send_stop+0x4c/0xe4\n[ 42.861511] pc : [\u003c00000000\u003e] lr : [\u003cc00183a4\u003e] psr: 60000013\n[ 42.861511] sp : d6c85e70 ip : 00000000 fp : 00000000\n[ 42.873626] r10: 00000000 r9 : d6c84000 r8 : 00000002\n[ 42.879150] r7 : c07235a0 r6 : c06dd2d0 r5 : 000f4241 r4 : d6c85e74\n[ 42.886047] r3 : 00000000 r2 : 00000000 r1 : 00000006 r0 : d6c85e74\n[ 42.892944] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user\n[ 42.900482] Control: 10c5387d Table: 97a74019 DAC: 00000015\n[ 42.906555] Process reboot (pid: 1166, stack limit \u003d 0xd6c842f8)\n[ 42.912902] Stack: (0xd6c85e70 to 0xd6c86000)\n[ 42.917510] 5e60: c07235a0 00000000 00000000 d6c84000\n[ 42.926177] 5e80: 01234567 c00143d0 4321fedc c00511bc d6c85ebc 00000168 00000460 00000000\n[ 42.934814] 5ea0: c1017950 a0000013 c1017900 d8014390 d7ec3858 c0498e48 c1017950 00000000\n[ 42.943481] 5ec0: d6ddde10 d6c85f78 00000003 00000000 d6ddde10 d6c84000 00000000 00000000\n[ 42.952117] 5ee0: 00000002 00000000 00000000 c0088c88 00000002 00000000 00000000 c00f4b90\n[ 42.960784] 5f00: 00000000 d6c85ebc d8014390 d7e311c8 60000013 00000103 00000002 d6c84000\n[ 42.969421] 5f20: c00f3274 d6e00a00 00000001 60000013 d6c84000 00000000 00000000 c00895d4\n[ 42.978057] 5f40: 00000002 d8007c80 d781f000 c00f6150 d8010cc0 c00f3274 d781f000 d6c84000\n[ 42.986694] 5f60: c0013020 d6e00a00 00000001 20000010 0001257c ef000000 00000000 c00895d4\n[ 42.995361] 5f80: 00000002 00000001 00000003 00000000 00000001 00000003 00000000 00000058\n[ 43.003997] 5fa0: c00130c8 c0012f00 00000001 00000003 fee1dead 28121969 01234567 00000002\n[ 43.012634] 5fc0: 00000001 00000003 00000000 00000058 00012584 0001257c 00000001 00000000\n[ 43.021270] 5fe0: 000124bc bec5cc6c 00008f9c 4a2f7c40 20000010 fee1dead 00000000 00000000\n[ 43.029968] [\u003cc00183a4\u003e] (smp_send_stop+0x4c/0xe4) from [\u003cc00143d0\u003e] (machine_restart+0xc/0x4c)\n[ 43.039154] [\u003cc00143d0\u003e] (machine_restart+0xc/0x4c) from [\u003cc00511bc\u003e] (sys_reboot+0x144/0x1f0)\n[ 43.048278] [\u003cc00511bc\u003e] (sys_reboot+0x144/0x1f0) from [\u003cc0012f00\u003e] (ret_fast_syscall+0x0/0x3c)\n[ 43.057464] Code: bad PC value\n[ 43.060760] ---[ end trace c3988d1dd0b8f0fb ]---\n\nAdd a check so smp_cross_call() is only called when there is more than one CPU on-line.\n\nSigned-off-by: Javier Martinez Canillas \u003cjavier at dowhile0.org\u003e\nAcked-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7e49f71b7a6268bb9854b91f6fae3f070fb0222e", "tree": "9b5870553310675b820264f221165d6eb9c7cfa9", "parents": [ "17c7d1468f968e153d39a94efeedd0a0e2a77c2a" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Mon Jul 23 14:18:13 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:06 2012 -0700" }, "message": "ARM: 7479/1: mm: avoid NULL dereference when flushing gate_vma with VIVT caches\n\ncommit b74253f78400f9a4b42da84bb1de7540b88ce7c4 upstream.\n\nThe vivt_flush_cache_{range,page} functions check that the mm_struct\nof the VMA being flushed has been active on the current CPU before\nperforming the cache maintenance.\n\nThe gate_vma has a NULL mm_struct pointer and, as such, will cause a\nkernel fault if we try to flush it with the above operations. This\nhappens during ELF core dumps, which include the gate_vma as it may be\nuseful for debugging purposes.\n\nThis patch adds checks to the VIVT cache flushing functions so that VMAs\nwith a NULL mm_struct are flushed unconditionally (the vectors page may\nbe dirty if we use it to store the current TLS pointer).\n\nReported-by: Gilles Chanteperdrix \u003cgilles.chanteperdrix@xenomai.org\u003e\nTested-by: Uros Bizjak \u003cubizjak@gmail.com\u003e\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "17c7d1468f968e153d39a94efeedd0a0e2a77c2a", "tree": "2f45e1fc08b26f7b0013056ed702239a535793c2", "parents": [ "f95f7ae189b51123becde905e934954c86c8a0e2" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Fri Jul 20 18:24:55 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:06 2012 -0700" }, "message": "ARM: 7478/1: errata: extend workaround for erratum #720789\n\ncommit 5a783cbc48367cfc7b65afc75430953dfe60098f upstream.\n\nCommit cdf357f1 (\"ARM: 6299/1: errata: TLBIASIDIS and TLBIMVAIS\noperations can broadcast a faulty ASID\") replaced by-ASID TLB flushing\noperations with all-ASID variants to workaround A9 erratum #720789.\n\nThis patch extends the workaround to include the tlb_range operations,\nwhich were overlooked by the original patch.\n\nTested-by: Steve Capper \u003csteve.capper@arm.com\u003e\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f95f7ae189b51123becde905e934954c86c8a0e2", "tree": "4d799ea5e9df97b7b90ce238cf476f829443c13e", "parents": [ "ea2ebaa71c978254c2a93bf561236aec8a167166" ], "author": { "name": "Colin Cross", "email": "ccross@android.com", "time": "Fri Jul 20 02:03:42 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:06 2012 -0700" }, "message": "ARM: 7477/1: vfp: Always save VFP state in vfp_pm_suspend on UP\n\ncommit 24b35521b8ddf088531258f06f681bb7b227bf47 upstream.\n\nvfp_pm_suspend should save the VFP state in suspend after\nany lazy context switch. If it only saves when the VFP is enabled,\nthe state can get lost when, on a UP system:\n Thread 1 uses the VFP\n Context switch occurs to thread 2, VFP is disabled but the\n VFP context is not saved\n Thread 2 initiates suspend\n vfp_pm_suspend is called with the VFP disabled, and the unsaved\n VFP context of Thread 1 in the registers\n\nModify vfp_pm_suspend to save the VFP context whenever\nvfp_current_hw_state is not NULL.\n\nIncludes a fix from Ido Yariv \u003cido@wizery.com\u003e, who pointed out that on\nSMP systems, the state pointer can be pointing to a freed task struct if\na task exited on another cpu, fixed by using #ifndef CONFIG_SMP in the\nnew if clause.\n\nSigned-off-by: Colin Cross \u003cccross@android.com\u003e\nCc: Barry Song \u003cbs14@csr.com\u003e\nCc: Catalin Marinas \u003ccatalin.marinas@arm.com\u003e\nCc: Ido Yariv \u003cido@wizery.com\u003e\nCc: Daniel Drake \u003cdsd@laptop.org\u003e\nCc: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ea2ebaa71c978254c2a93bf561236aec8a167166", "tree": "5b93e476cf4b8c33122821762ed17b0298ac8926", "parents": [ "05aa0d1bc94e2809ec0ccb4be20860784e4640b1" ], "author": { "name": "Colin Cross", "email": "ccross@android.com", "time": "Fri Jul 20 02:03:43 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:06 2012 -0700" }, "message": "ARM: 7476/1: vfp: only clear vfp state for current cpu in vfp_pm_suspend\n\ncommit a84b895a2348f0dbff31b71ddf954f70a6cde368 upstream.\n\nvfp_pm_suspend runs on each cpu, only clear the hardware state\npointer for the current cpu. Prevents a possible crash if one\ncpu clears the hw state pointer when another cpu has already\nchecked if it is valid.\n\nSigned-off-by: Colin Cross \u003cccross@android.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "05aa0d1bc94e2809ec0ccb4be20860784e4640b1", "tree": "a5793c18831793b3a880167ba8db26564bae9be0", "parents": [ "ce6f0ff8d1031931df7031a88f4085e5f196a854" ], "author": { "name": "Shawn Guo", "email": "shawn.guo@linaro.org", "time": "Fri Jul 13 08:19:34 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:05 2012 -0700" }, "message": "ARM: 7466/1: disable interrupt before spinning endlessly\n\ncommit 98bd8b96b26db3399a48202318dca4aaa2515355 upstream.\n\nThe CPU will endlessly spin at the end of machine_halt and\nmachine_restart calls. However, this will lead to a soft lockup\nwarning after about 20 seconds, if CONFIG_LOCKUP_DETECTOR is enabled,\nas system timer is still alive.\n\nDisable interrupt before going to spin endlessly, so that the lockup\nwarning will never be seen.\n\nReported-by: Marek Vasut \u003cmarex@denx.de\u003e\nSigned-off-by: Shawn Guo \u003cshawn.guo@linaro.org\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5eaac83b7362a1944afde7e867e53c7135e36d68", "tree": "8c3de8082f3243f2f3f4d5f57a85f2b2a1061786", "parents": [ "8067fa23092f2c4e18c29c90f7d5bb765dbf8954" ], "author": { "name": "Tony Luck", "email": "tony.luck@intel.com", "time": "Thu Jul 26 10:55:26 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Aug 15 08:10:04 2012 -0700" }, "message": "Redefine ATOMIC_INIT and ATOMIC64_INIT to drop the casts\n\ncommit a119365586b0130dfea06457f584953e0ff6481d upstream.\n\nThe following build error occured during a ia64 build with\nswap-over-NFS patches applied.\n\nnet/core/sock.c:274:36: error: initializer element is not constant\nnet/core/sock.c:274:36: error: (near initialization for \u0027memalloc_socks\u0027)\nnet/core/sock.c:274:36: error: initializer element is not constant\n\nThis is identical to a parisc build error. Fengguang Wu, Mel Gorman\nand James Bottomley did all the legwork to track the root cause of\nthe problem. This fix and entire commit log is shamelessly copied\nfrom them with one extra detail to change a dubious runtime use of\nATOMIC_INIT() to atomic_set() in drivers/char/mspec.c\n\nDave Anglin says:\n\u003e Here is the line in sock.i:\n\u003e\n\u003e struct static_key memalloc_socks \u003d ((struct static_key) { .enabled \u003d\n\u003e ((atomic_t) { (0) }) });\n\nThe above line contains two compound literals. It also uses a designated\ninitializer to initialize the field enabled. A compound literal is not a\nconstant expression.\n\nThe location of the above statement isn\u0027t fully clear, but if a compound\nliteral occurs outside the body of a function, the initializer list must\nconsist of constant expressions.\n\nSigned-off-by: Tony Luck \u003ctony.luck@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ef2e080c19599e3d0844f3bc599ee5dd627fc850", "tree": "19143fd205d2a4a176bba367794af8b8f979ec4f", "parents": [ "727cda365f7007f75a402f38ecd8bbf88a874e8f" ], "author": { "name": "Mikael Pettersson", "email": "mikpe@it.uu.se", "time": "Thu Apr 19 00:53:36 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:53 2012 -0700" }, "message": "m68k: Correct the Atari ALLOWINT definition\n\ncommit c663600584a596b5e66258cc10716fb781a5c2c9 upstream.\n\nBooting a 3.2, 3.3, or 3.4-rc4 kernel on an Atari using the\n`nfeth\u0027 ethernet device triggers a WARN_ONCE() in generic irq\nhandling code on the first irq for that device:\n\nWARNING: at kernel/irq/handle.c:146 handle_irq_event_percpu+0x134/0x142()\nirq 3 handler nfeth_interrupt+0x0/0x194 enabled interrupts\nModules linked in:\nCall Trace: [\u003c000299b2\u003e] warn_slowpath_common+0x48/0x6a\n [\u003c000299c0\u003e] warn_slowpath_common+0x56/0x6a\n [\u003c00029a4c\u003e] warn_slowpath_fmt+0x2a/0x32\n [\u003c0005b34c\u003e] handle_irq_event_percpu+0x134/0x142\n [\u003c0005b34c\u003e] handle_irq_event_percpu+0x134/0x142\n [\u003c0000a584\u003e] nfeth_interrupt+0x0/0x194\n [\u003c001ba0a8\u003e] schedule_preempt_disabled+0x0/0xc\n [\u003c0005b37a\u003e] handle_irq_event+0x20/0x2c\n [\u003c0005add4\u003e] generic_handle_irq+0x2c/0x3a\n [\u003c00002ab6\u003e] do_IRQ+0x20/0x32\n [\u003c0000289e\u003e] auto_irqhandler_fixup+0x4/0x6\n [\u003c00003144\u003e] cpu_idle+0x22/0x2e\n [\u003c001b8a78\u003e] printk+0x0/0x18\n [\u003c0024d112\u003e] start_kernel+0x37a/0x386\n [\u003c0003021d\u003e] __do_proc_dointvec+0xb1/0x366\n [\u003c0003021d\u003e] __do_proc_dointvec+0xb1/0x366\n [\u003c0024c31e\u003e] _sinittext+0x31e/0x9c0\n\nAfter invoking the irq\u0027s handler the kernel sees !irqs_disabled()\nand concludes that the handler erroneously enabled interrupts.\n\nHowever, debugging shows that !irqs_disabled() is true even before\nthe handler is invoked, which indicates a problem in the platform\ncode rather than the specific driver.\n\nThe warning does not occur in 3.1 or older kernels.\n\nIt turns out that the ALLOWINT definition for Atari is incorrect.\n\nThe Atari definition of ALLOWINT is ~0x400, the stated purpose of\nthat is to avoid taking HSYNC interrupts. irqs_disabled() returns\ntrue if the 3-bit ipl \u0026 4 is non-zero. The nfeth interrupt runs at\nipl 3 (it\u0027s autovector 3), but 3 \u0026 4 is zero so irqs_disabled() is\nfalse, and the warning above is generated.\n\nWhen interrupts are explicitly disabled, ipl is set to 7. When they\nare enabled, ipl is masked with ALLOWINT. On Atari this will result\nin ipl \u003d 3, which blocks interrupts at ipl 3 and below. So how come\nnfeth interrupts at ipl 3 are received at all? That\u0027s because ipl\nis reset to 2 by Atari-specific code in default_idle(), again with\nthe stated purpose of blocking HSYNC interrupts. This discrepancy\nmeans that ipl 3 can remain blocked for longer than intended.\n\nBoth default_idle() and falcon_hblhandler() identify HSYNC with\nipl 2, and the \"Atari ST/.../F030 Hardware Register Listing\" agrees,\nbut ALLOWINT is defined as if HSYNC was ipl 3.\n\n[As an experiment I modified default_idle() to reset ipl to 3, and\nas expected that resulted in all nfeth interrupts being blocked.]\n\nThe fix is simple: define ALLOWINT as ~0x500 instead. This makes\narch_local_irq_enable() consistent with default_idle(), and prevents\nthe !irqs_disabled() problems for ipl 3 interrupts.\n\nTested on Atari running in an Aranym VM.\n\nSigned-off-by: Mikael Pettersson \u003cmikpe@it.uu.se\u003e\nTested-by: Michael Schmitz \u003cschmitzmic@googlemail.com\u003e\nSigned-off-by: Geert Uytterhoeven \u003cgeert@linux-m68k.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n\n" }, { "commit": "727cda365f7007f75a402f38ecd8bbf88a874e8f", "tree": "117bba15a0514b07e7b2fdac1d87a545f70a9771", "parents": [ "8f32469c980654a17e935dae06a3557b488910a4" ], "author": { "name": "Andreas Schwab", "email": "schwab@linux-m68k.org", "time": "Sat Jul 28 00:20:34 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:53 2012 -0700" }, "message": "m68k: Make sys_atomic_cmpxchg_32 work on classic m68k\n\ncommit 9e2760d18b3cf179534bbc27692c84879c61b97c upstream.\n\nUser space access must always go through uaccess accessors, since on\nclassic m68k user space and kernel space are completely separate.\n\nSigned-off-by: Andreas Schwab \u003cschwab@linux-m68k.org\u003e\nTested-by: Thorsten Glaser \u003ctg@debian.org\u003e\nSigned-off-by: Geert Uytterhoeven \u003cgeert@linux-m68k.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "27cd8f51344dcf4799c7a092c1797402b833126a", "tree": "4af5fa7d852c6f73795dd0ea9508b86283fb009e", "parents": [ "b6e9ffcdb09fbf28665e025aa31fda702689786c" ], "author": { "name": "Josh Boyer", "email": "jwboyer@redhat.com", "time": "Wed Jul 25 10:40:34 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:39 2012 -0700" }, "message": "posix_types.h: Cleanup stale __NFDBITS and related definitions\n\ncommit 8ded2bbc1845e19c771eb55209aab166ef011243 upstream.\n\nRecently, glibc made a change to suppress sign-conversion warnings in\nFD_SET (glibc commit ceb9e56b3d1). This uncovered an issue with the\nkernel\u0027s definition of __NFDBITS if applications #include\n\u003clinux/types.h\u003e after including \u003csys/select.h\u003e. A build failure would\nbe seen when passing the -Werror\u003dsign-compare and -D_FORTIFY_SOURCE\u003d2\nflags to gcc.\n\nIt was suggested that the kernel should either match the glibc\ndefinition of __NFDBITS or remove that entirely. The current in-kernel\nuses of __NFDBITS can be replaced with BITS_PER_LONG, and there are no\nuses of the related __FDELT and __FDMASK defines. Given that, we\u0027ll\ncontinue the cleanup that was started with commit 8b3d1cda4f5f\n(\"posix_types: Remove fd_set macros\") and drop the remaining unused\nmacros.\n\nAdditionally, linux/time.h has similar macros defined that expand to\nnothing so we\u0027ll remove those at the same time.\n\nReported-by: Jeff Law \u003claw@redhat.com\u003e\nSuggested-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Josh Boyer \u003cjwboyer@redhat.com\u003e\n[ .. and fix up whitespace as per akpm ]\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "351bb0ecc5b0b9dc60d07a44078fa16971c7f3e7", "tree": "ae8c5c448e855657289affc7f907bd11b2142efd", "parents": [ "cd1af8b7d386e6b3991252650c16b3e9d5a03b65" ], "author": { "name": "Heiko Carstens", "email": "heiko.carstens@de.ibm.com", "time": "Fri Jul 27 09:45:39 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:31 2012 -0700" }, "message": "s390/mm: fix fault handling for page table walk case\n\ncommit 008c2e8f247f0a8db1e8e26139da12f3a3abcda0 upstream.\n\nMake sure the kernel does not incorrectly create a SIGBUS signal during\nuser space accesses:\n\nFor user space accesses in the switched addressing mode case the kernel\nmay walk page tables and access user address space via the kernel\nmapping. If a page table entry is invalid the function __handle_fault()\ngets called in order to emulate a page fault and trigger all the usual\nactions like paging in a missing page etc. by calling handle_mm_fault().\n\nIf handle_mm_fault() returns with an error fixup handling is necessary.\nFor the switched addressing mode case all errors need to be mapped to\n-EFAULT, so that the calling uaccess function can return -EFAULT to\nuser space.\n\nUnfortunately the __handle_fault() incorrectly calls do_sigbus() if\nVM_FAULT_SIGBUS is set. This however should only happen if a page fault\nwas triggered by a user space instruction. For kernel mode uaccesses\nthe correct action is to only return -EFAULT.\nSo user space may incorrectly see SIGBUS signals because of this bug.\n\nFor current machines this would only be possible for the switched\naddressing mode case in conjunction with futex operations.\n\nSigned-off-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cd1af8b7d386e6b3991252650c16b3e9d5a03b65", "tree": "93fc53558ab9ad563fb4d58b5f3b7f6a62e85215", "parents": [ "554c9a0c6f72a8a5c44962b82f495d95e547b4b3" ], "author": { "name": "Martin Schwidefsky", "email": "schwidefsky@de.ibm.com", "time": "Thu Jul 26 08:53:06 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:31 2012 -0700" }, "message": "s390/mm: downgrade page table after fork of a 31 bit process\n\ncommit 0f6f281b731d20bfe75c13f85d33f3f05b440222 upstream.\n\nThe downgrade of the 4 level page table created by init_new_context is\ncurrently done only in start_thread31. If a 31 bit process forks the\nnew mm uses a 4 level page table, including the task size of 2\u003c\u003c42\nthat goes along with it. This is incorrect as now a 31 bit process\ncan map memory beyond 2GB. Define arch_dup_mmap to do the downgrade\nafter fork.\n\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "554c9a0c6f72a8a5c44962b82f495d95e547b4b3", "tree": "451c24b944fcc114f4f7fc719b760e82d7491c06", "parents": [ "2c3fea5b8591cd8c539bff95108efc2a1f9c5f20" ], "author": { "name": "Heiko Carstens", "email": "heiko.carstens@de.ibm.com", "time": "Fri Jul 13 15:45:33 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:30 2012 -0700" }, "message": "s390/idle: fix sequence handling vs cpu hotplug\n\ncommit 0008204ffe85d23382d6fd0f971f3f0fbe70bae2 upstream.\n\nThe s390 idle accounting code uses a sequence counter which gets used\nwhen the per cpu idle statistics get updated and read.\n\nOne assumption on read access is that only when the sequence counter is\neven and did not change while reading all values the result is valid.\nOn cpu hotplug however the per cpu data structure gets initialized via\na cpu hotplug notifier on CPU_ONLINE.\nCPU_ONLINE however is too late, since the onlined cpu is already running\nand might access the per cpu data. Worst case is that the data structure\ngets initialized while an idle thread is updating its idle statistics.\nThis will result in an uneven sequence counter after an update.\n\nAs a result user space tools like top, which access /proc/stat in order\nto get idle stats, will busy loop waiting for the sequence counter to\nbecome even again, which will never happen until the queried cpu will\nupdate its idle statistics again. And even then the sequence counter\nwill only have an even value for a couple of cpu cycles.\n\nFix this by moving the initialization of the per cpu idle statistics\nto cpu_init(). I prefer that solution in favor of changing the\nnotifier to CPU_UP_PREPARE, which would be a different solution to\nthe problem.\n\nSigned-off-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7b689c5d930f281e417597af9f817ba03dc9d898", "tree": "75bb26f8fc89a58f25377e60cf2af6879fb795b0", "parents": [ "2830f9a08c084bcf40819942f04d0ca500faf4b8" ], "author": { "name": "Tony Luck", "email": "tony.luck@intel.com", "time": "Wed Jul 11 10:20:47 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:29 2012 -0700" }, "message": "x86/mce: Fix siginfo_t-\u003esi_addr value for non-recoverable memory faults\n\ncommit 6751ed65dc6642af64f7b8a440a75563c8aab7ae upstream.\n\nIn commit dad1743e5993f1 (\"x86/mce: Only restart instruction after machine\ncheck recovery if it is safe\") we fixed mce_notify_process() to force a\nsignal to the current process if it was not restartable (RIPV bit not\nset in MCG_STATUS). But doing it here means that the process doesn\u0027t\nget told the virtual address of the fault via siginfo_t-\u003esi_addr. This\nwould prevent application level recovery from the fault.\n\nMake a new MF_MUST_KILL flag bit for memory_failure() et al. to use so\nthat we will provide the right information with the signal.\n\nSigned-off-by: Tony Luck \u003ctony.luck@intel.com\u003e\nAcked-by: Borislav Petkov \u003cborislav.petkov@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0706b27d2ff206bdbeb457a56944ca372e6a9d8e", "tree": "a3a0615ee9fab7e083b5408f06c5776823fd8972", "parents": [ "c4c3d44ab775fa457c49d7fce906df0a310bb347" ], "author": { "name": "Nishanth Menon", "email": "nm@ti.com", "time": "Fri May 18 12:26:19 2012 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:28 2012 -0700" }, "message": "ARM: OMAP2+: OPP: Fix to ensure check of right oppdef after bad one\n\ncommit b110547e586eb5825bc1d04aa9147bff83b57672 upstream.\n\nCommit 9fa2df6b90786301b175e264f5fa9846aba81a65\n(ARM: OMAP2+: OPP: allow OPP enumeration to continue if device is not present)\nmakes the logic:\nfor (i \u003d 0; i \u003c opp_def_size; i++) {\n\t\u003csnip\u003e\n\tif (!oh || !oh-\u003eod) {\n\t\t\u003csnip\u003e\n\t\tcontinue;\n\t}\n\u003csnip\u003e\nopp_def++;\n}\n\nIn short, the moment we hit a \"Bad OPP\", we end up looping the list\ncomparing against the bad opp definition pointer for the rest of the\niteration count. Instead, increment opp_def in the for loop itself\nand allow continue to be used in code without much thought so that\nwe check the next set of OPP definition pointers :)\n\nCc: Steve Sakoman \u003csteve@sakoman.com\u003e\nCc: Tony Lindgren \u003ctony@atomide.com\u003e\nSigned-off-by: Nishanth Menon \u003cnm@ti.com\u003e\nSigned-off-by: Kevin Hilman \u003ckhilman@ti.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "753e14ef13311122aa5a819657d17940969a6f80", "tree": "4a0fad49040f8c110ceea8f46746d36a3022ce22", "parents": [ "f18e28667a2a26d0ead02cc730524fa6203ec818" ], "author": { "name": "Timur Tabi", "email": "timur@freescale.com", "time": "Thu Jul 05 10:08:28 2012 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:27 2012 -0700" }, "message": "powerpc/85xx: use the BRx registers to enable indirect mode on the P1022DS\n\ncommit 6bd825f02966be8ba544047cab313d6032c23819 upstream.\n\nIn order to enable the DIU video controller on the P1022DS, the FPGA needs\nto be switched to \"indirect mode\", where the localbus is disabled and\nthe FPGA is accessed via writes to localbus chip select signals CS0 and CS1.\n\nTo obtain the address of CS0 and CS1, the platform driver uses an \"indirect\npixis mode\" device tree node. This node assumes that the localbus \u0027ranges\u0027\nproperty is sorted in chip-select order. That is, reg value 0 maps to\nCS0, reg value 1 maps to CS1, etc. This is how the \u0027ranges\u0027 property is\nsupposed to be arranged.\n\nUnfortunately, the \u0027ranges\u0027 property is often mis-arranged, and not just on\nthe P1022DS. Linux normally does not care, since it does not program the\nlocalbus. But the indirect-mode code on the P1022DS does care.\n\nThe \"proper\" fix is to have U-Boot fix the \u0027ranges\u0027 property, but this would\nbe too cumbersome. The names and \u0027reg\u0027 properties of all the localbus\ndevices would also need to be updated, and determining which localbus device\nmaps to which chip select is board-specific.\n\nInstead, we determine the CS0/CS1 base addresses the same way that U-boot\ndoes -- by reading the BRx registers directly and mapping them to physical\naddresses. This code is simpler and more reliable, and it does not require\na U-boot or device tree change.\n\nSince the indirect pixis device tree node is no longer needed, the node is\ndeleted from the DTS.\n\nSigned-off-by: Timur Tabi \u003ctimur@freescale.com\u003e\nSigned-off-by: Kumar Gala \u003cgalak@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f18e28667a2a26d0ead02cc730524fa6203ec818", "tree": "1cf5d3d6380fea4bcfa035f8a996a666ab57a418", "parents": [ "a461394c31c5aa3c8cfe98dd0dc35f6b56047770" ], "author": { "name": "Kleber Sacilotto de Souza", "email": "klebers@linux.vnet.ibm.com", "time": "Thu Jul 12 17:14:36 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:27 2012 -0700" }, "message": "powerpc/eeh: Check handle_eeh_events() return value\n\ncommit 10db8d212864cb6741df7d7fafda5ab6661f6f88 upstream.\n\nFunction eeh_event_handler() dereferences the pointer returned by\nhandle_eeh_events() without checking, causing a crash if NULL was\nreturned, which is expected in some situations.\n\nThis patch fixes this bug by checking for the value returned by\nhandle_eeh_events() before dereferencing it.\n\nSigned-off-by: Kleber Sacilotto de Souza \u003cklebers@linux.vnet.ibm.com\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a461394c31c5aa3c8cfe98dd0dc35f6b56047770", "tree": "8a1027c89bb12e5dca2e7bf9a23e880ce9abe68d", "parents": [ "2cdb31f3c09f2bdd10d520a24def87d90c0030ba" ], "author": { "name": "Tiejun Chen", "email": "tiejun.chen@windriver.com", "time": "Wed Jul 11 14:22:46 2012 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:27 2012 -0700" }, "message": "powerpc: Add \"memory\" attribute for mfmsr()\n\ncommit b416c9a10baae6a177b4f9ee858b8d309542fbef upstream.\n\nAdd \"memory\" attribute in inline assembly language as a compiler\nbarrier to make sure 4.6.x GCC don\u0027t reorder mfmsr().\n\nSigned-off-by: Tiejun Chen \u003ctiejun.chen@windriver.com\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "2cdb31f3c09f2bdd10d520a24def87d90c0030ba", "tree": "e9150244ae2673c645f83ff0aceb6154c29b001c", "parents": [ "94c73bbcec6a77eb8a526a1230631a2cc18bf18b" ], "author": { "name": "roger blofeld", "email": "blofeldus@yahoo.com", "time": "Thu Jun 21 05:27:14 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Aug 09 08:31:27 2012 -0700" }, "message": "powerpc/ftrace: Fix assembly trampoline register usage\n\ncommit fd5a42980e1cf327b7240adf5e7b51ea41c23437 upstream.\n\nJust like the module loader, ftrace needs to be updated to use r12\ninstead of r11 with newer gcc\u0027s.\n\nSigned-off-by: Roger Blofeld \u003cblofeldus@yahoo.com\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Paul Gortmaker \u003cpaul.gortmaker@windriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a22ad130fc91983ac717a24e29838bf2969a67d4", "tree": "a63f0ff27d9efde695ee54b4c76df987ac3b65e0", "parents": [ "5a4db9ee4f44658077a11c71d78a17573016fc0e" ], "author": { "name": "Tushar Behera", "email": "tushar.behera@linaro.org", "time": "Thu Jul 12 18:06:28 2012 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Jul 29 08:04:21 2012 -0700" }, "message": "ARM: SAMSUNG: Update default rate for xusbxti clock\n\ncommit bdd3cc26ba651e33780ade33f1410320cf2d0cf4 upstream.\n\nThe rate of xusbxti clock is set in individual machine files.\nThe default value should be defined at the clock definition\nand individual machine files should modify it if required.\n\nDivision by zero in kernel.\n[\u003cc0011849\u003e] (unwind_backtrace+0x1/0x9c) from [\u003cc022c663\u003e] (Ldiv0+0x9/0x12)\n[\u003cc022c663\u003e] (Ldiv0+0x9/0x12) from [\u003cc001a3c3\u003e] (s3c_setrate_clksrc+0x33/0x78)\n[\u003cc001a3c3\u003e] (s3c_setrate_clksrc+0x33/0x78) from [\u003cc0019e67\u003e] (clk_set_rate+0x2f/0x78)\n\nSigned-off-by: Tushar Behera \u003ctushar.behera@linaro.org\u003e\nSigned-off-by: Kukjin Kim \u003ckgene.kim@samsung.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ec8348902ff82ae44f25b3127f8f3ec47e1e6a07", "tree": "1b87f4816054789f13b6005cd53357efdc796604", "parents": [ "60d091aeb66c0b201689862bcb803c32db712d05" ], "author": { "name": "David Daney", "email": "david.daney@cavium.com", "time": "Thu Jul 19 09:11:14 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Jul 29 08:04:20 2012 -0700" }, "message": "MIPS: Properly align the .data..init_task section.\n\ncommit 7b1c0d26a8e272787f0f9fcc5f3e8531df3b3409 upstream.\n\nImproper alignment can lead to unbootable systems and/or random\ncrashes.\n\n[ralf@linux-mips.org: This is a lond standing bug since\n6eb10bc9e2deab06630261cd05c4cb1e9a60e980 (kernel.org) rsp.\nc422a10917f75fd19fa7fe070aaaa23e384dae6f (lmo) [MIPS: Clean up linker script\nusing new linker script macros.] so dates back to 2.6.32.]\n\nSigned-off-by: David Daney \u003cdavid.daney@cavium.com\u003e\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/3881/\nSigned-off-by: Ralf Baechle \u003cralf@linux-mips.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5c77ea89ed79a692b0097dbca3652fbc83e30619", "tree": "a260a0925d36f5db62259914d38fc212b5d96fe6", "parents": [ "e301f7b1dbbb0af6dcb8ed10c800fa95bb34917a" ], "author": { "name": "Todd Poynor", "email": "toddpoynor@google.com", "time": "Fri Jul 13 15:30:48 2012 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Jul 19 08:58:55 2012 -0700" }, "message": "ARM: SAMSUNG: fix race in s3c_adc_start for ADC\n\ncommit 8265981bb439f3ecc5356fb877a6c2a6636ac88a upstream.\n\nChecking for adc-\u003ets_pend already claimed should be done with the\nlock held.\n\nSigned-off-by: Todd Poynor \u003ctoddpoynor@google.com\u003e\nAcked-by: Ben Dooks \u003cben-linux@fluff.org\u003e\nSigned-off-by: Kukjin Kim \u003ckgene.kim@samsung.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "acf8fbd7c1182204ed723dee365bc5ba9a503dd6", "tree": "6479ee55435b097d79e5e1fe45a1c1e7a3f030d6", "parents": [ "ff99851d5277c6131301a09f687aa3976ced31e7" ], "author": { "name": "Andrea Arcangeli", "email": "aarcange@redhat.com", "time": "Wed Jun 20 12:52:57 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:04:42 2012 -0700" }, "message": "thp: avoid atomic64_read in pmd_read_atomic for 32bit PAE\n\ncommit e4eed03fd06578571c01d4f1478c874bb432c815 upstream.\n\nIn the x86 32bit PAE CONFIG_TRANSPARENT_HUGEPAGE\u003dy case while holding the\nmmap_sem for reading, cmpxchg8b cannot be used to read pmd contents under\nXen.\n\nSo instead of dealing only with \"consistent\" pmdvals in\npmd_none_or_trans_huge_or_clear_bad() (which would be conceptually\nsimpler) we let pmd_none_or_trans_huge_or_clear_bad() deal with pmdvals\nwhere the low 32bit and high 32bit could be inconsistent (to avoid having\nto use cmpxchg8b).\n\nThe only guarantee we get from pmd_read_atomic is that if the low part of\nthe pmd was found null, the high part will be null too (so the pmd will be\nconsidered unstable). And if the low part of the pmd is found \"stable\"\nlater, then it means the whole pmd was read atomically (because after a\npmd is stable, neither MADV_DONTNEED nor page faults can alter it anymore,\nand we read the high part after the low part).\n\nIn the 32bit PAE x86 case, it is enough to read the low part of the pmdval\natomically to declare the pmd as \"stable\" and that\u0027s true for THP and no\nTHP, furthermore in the THP case we also have a barrier() that will\nprevent any inconsistent pmdvals to be cached by a later re-read of the\n*pmd.\n\nSigned-off-by: Andrea Arcangeli \u003caarcange@redhat.com\u003e\nCc: Jonathan Nieder \u003cjrnieder@gmail.com\u003e\nCc: Ulrich Obergfell \u003cuobergfe@redhat.com\u003e\nCc: Mel Gorman \u003cmgorman@suse.de\u003e\nCc: Hugh Dickins \u003chughd@google.com\u003e\nCc: Larry Woodman \u003clwoodman@redhat.com\u003e\nCc: Petr Matousek \u003cpmatouse@redhat.com\u003e\nCc: Rik van Riel \u003criel@redhat.com\u003e\nCc: Jan Beulich \u003cjbeulich@suse.com\u003e\nCc: KOSAKI Motohiro \u003ckosaki.motohiro@gmail.com\u003e\nTested-by: Andrew Jones \u003cdrjones@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ff99851d5277c6131301a09f687aa3976ced31e7", "tree": "1a7d2b5c47af230cb78978aefe87ba6655a8af45", "parents": [ "e5982925c66c542aa41b17ee35fc233ae1521898" ], "author": { "name": "Andrea Arcangeli", "email": "aarcange@redhat.com", "time": "Tue May 29 15:06:49 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:04:41 2012 -0700" }, "message": "mm: pmd_read_atomic: fix 32bit PAE pmd walk vs pmd_populate SMP race condition\n\ncommit 26c191788f18129af0eb32a358cdaea0c7479626 upstream.\n\nWhen holding the mmap_sem for reading, pmd_offset_map_lock should only\nrun on a pmd_t that has been read atomically from the pmdp pointer,\notherwise we may read only half of it leading to this crash.\n\nPID: 11679 TASK: f06e8000 CPU: 3 COMMAND: \"do_race_2_panic\"\n #0 [f06a9dd8] crash_kexec at c049b5ec\n #1 [f06a9e2c] oops_end at c083d1c2\n #2 [f06a9e40] no_context at c0433ded\n #3 [f06a9e64] bad_area_nosemaphore at c043401a\n #4 [f06a9e6c] __do_page_fault at c0434493\n #5 [f06a9eec] do_page_fault at c083eb45\n #6 [f06a9f04] error_code (via page_fault) at c083c5d5\n EAX: 01fb470c EBX: fff35000 ECX: 00000003 EDX: 00000100 EBP:\n 00000000\n DS: 007b ESI: 9e201000 ES: 007b EDI: 01fb4700 GS: 00e0\n CS: 0060 EIP: c083bc14 ERR: ffffffff EFLAGS: 00010246\n #7 [f06a9f38] _spin_lock at c083bc14\n #8 [f06a9f44] sys_mincore at c0507b7d\n #9 [f06a9fb0] system_call at c083becd\n start len\n EAX: ffffffda EBX: 9e200000 ECX: 00001000 EDX: 6228537f\n DS: 007b ESI: 00000000 ES: 007b EDI: 003d0f00\n SS: 007b ESP: 62285354 EBP: 62285388 GS: 0033\n CS: 0073 EIP: 00291416 ERR: 000000da EFLAGS: 00000286\n\nThis should be a longstanding bug affecting x86 32bit PAE without THP.\nOnly archs with 64bit large pmd_t and 32bit unsigned long should be\naffected.\n\nWith THP enabled the barrier() in pmd_none_or_trans_huge_or_clear_bad()\nwould partly hide the bug when the pmd transition from none to stable,\nby forcing a re-read of the *pmd in pmd_offset_map_lock, but when THP is\nenabled a new set of problem arises by the fact could then transition\nfreely in any of the none, pmd_trans_huge or pmd_trans_stable states.\nSo making the barrier in pmd_none_or_trans_huge_or_clear_bad()\nunconditional isn\u0027t good idea and it would be a flakey solution.\n\nThis should be fully fixed by introducing a pmd_read_atomic that reads\nthe pmd in order with THP disabled, or by reading the pmd atomically\nwith cmpxchg8b with THP enabled.\n\nLuckily this new race condition only triggers in the places that must\nalready be covered by pmd_none_or_trans_huge_or_clear_bad() so the fix\nis localized there but this bug is not related to THP.\n\nNOTE: this can trigger on x86 32bit systems with PAE enabled with more\nthan 4G of ram, otherwise the high part of the pmd will never risk to be\ntruncated because it would be zero at all times, in turn so hiding the\nSMP race.\n\nThis bug was discovered and fully debugged by Ulrich, quote:\n\n----\n[..]\npmd_none_or_trans_huge_or_clear_bad() loads the content of edx and\neax.\n\n 496 static inline int pmd_none_or_trans_huge_or_clear_bad(pmd_t\n *pmd)\n 497 {\n 498 /* depend on compiler for an atomic pmd read */\n 499 pmd_t pmdval \u003d *pmd;\n\n // edi \u003d pmd pointer\n0xc0507a74 \u003csys_mincore+548\u003e: mov 0x8(%esp),%edi\n...\n // edx \u003d PTE page table high address\n0xc0507a84 \u003csys_mincore+564\u003e: mov 0x4(%edi),%edx\n...\n // eax \u003d PTE page table low address\n0xc0507a8e \u003csys_mincore+574\u003e: mov (%edi),%eax\n\n[..]\n\nPlease note that the PMD is not read atomically. These are two \"mov\"\ninstructions where the high order bits of the PMD entry are fetched\nfirst. Hence, the above machine code is prone to the following race.\n\n- The PMD entry {high|low} is 0x0000000000000000.\n The \"mov\" at 0xc0507a84 loads 0x00000000 into edx.\n\n- A page fault (on another CPU) sneaks in between the two \"mov\"\n instructions and instantiates the PMD.\n\n- The PMD entry {high|low} is now 0x00000003fda38067.\n The \"mov\" at 0xc0507a8e loads 0xfda38067 into eax.\n----\n\nReported-by: Ulrich Obergfell \u003cuobergfe@redhat.com\u003e\nSigned-off-by: Andrea Arcangeli \u003caarcange@redhat.com\u003e\nCc: Mel Gorman \u003cmgorman@suse.de\u003e\nCc: Hugh Dickins \u003chughd@google.com\u003e\nCc: Larry Woodman \u003clwoodman@redhat.com\u003e\nCc: Petr Matousek \u003cpmatouse@redhat.com\u003e\nCc: Rik van Riel \u003criel@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3f616017b684a5faf29b7a6b7b100209357136e4", "tree": "386b2c6a9c29e4d31d614c4177bc3ad206b4b791", "parents": [ "174d58573117bc688e9481c8f7392bd1ddf24fcf" ], "author": { "name": "H. Peter Anvin", "email": "hpa@linux.intel.com", "time": "Fri Jun 22 10:58:06 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:04:22 2012 -0700" }, "message": "x86, cpufeature: Rename X86_FEATURE_DTS to X86_FEATURE_DTHERM\n\ncommit 4ad33411308596f2f918603509729922a1ec4411 upstream.\n\nIt makes sense to label \"Digital Thermal Sensor\" as \"DTS\", but\nunfortunately the string \"dts\" was already used for \"Debug Store\", and\n/proc/cpuinfo is a user space ABI.\n\nTherefore, rename this to \"dtherm\".\n\nThis conflict went into mainline via the hwmon tree without any x86\nmaintainer ack, and without any kind of hint in the subject.\n\n a4659053 x86/hwmon: fix initialization of coretemp\n\nReported-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nLink: http://lkml.kernel.org/r/4FE34BCB.5050305@linux.intel.com\nCc: Jan Beulich \u003cJBeulich@suse.com\u003e\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "174d58573117bc688e9481c8f7392bd1ddf24fcf", "tree": "55ef380d3e2c58d0888a48ac810ef0ea6cb4ebd2", "parents": [ "a92fdd54f75eae8e7d591070c83e146ab8eec2e3" ], "author": { "name": "Suresh Siddha", "email": "suresh.b.siddha@intel.com", "time": "Thu Jun 14 18:07:15 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:04:22 2012 -0700" }, "message": "x86, compat: Use test_thread_flag(TIF_IA32) in compat signal delivery\n\ncommit 0b91f45b23cb73ce11acdc3cf4c6efd4441e3b3e upstream.\n\nSignal delivery compat path may not have the \u0027TS_COMPAT\u0027 flag (that\nflag indicates how we entered the kernel). So use\ntest_thread_flag(TIF_IA32) instead of is_ia32_task(): one of the\nfunctions of TIF_IA32 is just what kind of signal frame we want.\n\nSigned-off-by: Suresh Siddha \u003csuresh.b.siddha@intel.com\u003e\nLink: http://lkml.kernel.org/r/1339722435.3475.57.camel@sbsiddha-desk.sc.intel.com\nSigned-off-by: H. Peter Anvin \u003chpa@zytor.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0341705f37081a337d6c073d326e4e9ad2ddcc83", "tree": "1c3b884b25656a31ad0a3ef8635fbafb3e00ecb8", "parents": [ "cb739ad1bba5a996533cf381b9079a1e876d15bb" ], "author": { "name": "Andrew Lunn", "email": "andrew@lunn.ch", "time": "Fri Jun 29 09:25:58 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:04:07 2012 -0700" }, "message": "ARM: Orion: Fix WDT compile for Dove and MV78xx0\n\ncommit 1e0c1ce00d83834d03f4d8d039734ca4703298df upstream.\n\nCommit 0fa1f0609a0c1fe8b2be3c0089a2cb48f7fda521 (ARM: Orion: Fix\nVirtual/Physical mixup with watchdog) broke the Dove \u0026 MV78xx0\nbuild. Although these two SoC don\u0027t use the watchdog, the shared\nplatform code still needs to build. Add the necessary defines.\n\nReported-by: Nicolas Pitre \u003cnico@fluxnic.net\u003e\nSigned-off-by: Andrew Lunn \u003candrew@lunn.ch\u003e\nTested-by: Nicolas Pitre \u003cnico@fluxnic.net\u003e\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cb739ad1bba5a996533cf381b9079a1e876d15bb", "tree": "3b47028a08b2c5c5bfc2afc36225af0931a6ca52", "parents": [ "0bd3d94b39087298b88f7ee2570d1062e09e8dfd" ], "author": { "name": "Andrew Lunn", "email": "andrew@lunn.ch", "time": "Fri Jun 22 08:54:02 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:04:07 2012 -0700" }, "message": "ARM: Orion: Fix Virtual/Physical mixup with watchdog\n\ncommit 0fa1f0609a0c1fe8b2be3c0089a2cb48f7fda521 upstream.\n\nThe orion watchdog is expecting to be passed the physcial address of\nthe hardware, and will ioremap() it to give a virtual address it will\nuse as the base address for the hardware. However, when creating the\nplatform resource record, a virtual address was being used.\n\nAdd the necassary #define\u0027s so we can pass the physical address as\nexpected.\n\nTested on Kirkwood and Orion5x.\n\nSigned-off-by: Andrew Lunn \u003candrew@lunn.ch\u003e\nSigned-off-by: Olof Johansson \u003colof@lixom.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b429b0cf0a702501aaa7bdf59c235643c529a83c", "tree": "d05790399ce46d2baf7c1a476260fbf843ee05b7", "parents": [ "b939c2acf1dc42b08407ef5174f2e8d6f43dd5ea" ], "author": { "name": "Zhang Rui", "email": "rui.zhang@intel.com", "time": "Mon Feb 20 14:20:06 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:04:07 2012 -0700" }, "message": "ACPI, x86: fix Dell M6600 ACPI reboot regression via DMI\n\ncommit 76eb9a30db4bc8fd172f9155247264b5f2686d7b upstream.\n\nDell Precision M6600 is known to require PCI reboot, so add it to\nthe reboot blacklist in pci_reboot_dmi_table[].\n\nhttps://bugzilla.kernel.org/show_bug.cgi?id\u003d42749\n\ncc: x86@kernel.org\nSigned-off-by: Zhang Rui \u003crui.zhang@intel.com\u003e\nSigned-off-by: Len Brown \u003clen.brown@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b939c2acf1dc42b08407ef5174f2e8d6f43dd5ea", "tree": "7fa3979ce8d92c0f2e9f42e27b91663945921e8b", "parents": [ "5752cdb805ff89942d99d12118e2844e7db34df8" ], "author": { "name": "Feng Tang", "email": "feng.tang@intel.com", "time": "Mon Jun 04 15:00:06 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:04:07 2012 -0700" }, "message": "ACPI: Add a quirk for \"AMILO PRO V2030\" to ignore the timer overriding\n\ncommit f6b54f083cc66cf9b11d2120d8df3c2ad4e0836d upstream.\n\nThis is the 2nd part of fix for kernel bugzilla 40002:\n \"IRQ 0 assigned to VGA\"\nhttps://bugzilla.kernel.org/show_bug.cgi?id\u003d40002\n\nThe root cause is the buggy FW, whose ACPI tables assign the GSI 16\nto 2 irqs 0 and 16(VGA), and the VGA is the right owner of GSI 16.\nSo add a quirk to ignore the irq0 overriding GSI 16 for the\nFUJITSU SIEMENS AMILO PRO V2030 platform will solve this issue.\n\nReported-and-tested-by: Szymon Kowalczyk \u003cfazerxlo@o2.pl\u003e\nSigned-off-by: Feng Tang \u003cfeng.tang@intel.com\u003e\nSigned-off-by: Len Brown \u003clen.brown@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5752cdb805ff89942d99d12118e2844e7db34df8", "tree": "ff9bf40bee38ffbdf2b1c15946f103c2d2f3e27f", "parents": [ "371122fc6eef7cafc8acaf0891fd15cf623388a3" ], "author": { "name": "Feng Tang", "email": "feng.tang@intel.com", "time": "Mon Jun 04 15:00:05 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:04:07 2012 -0700" }, "message": "ACPI: Remove one board specific WARN when ignoring timer overriding\n\ncommit 7f68b4c2e158019c2ec494b5cfbd9c83b4e5b253 upstream.\n\nCurrent WARN msg is only for the ati_ixp4x0 board, while this function\nis used by mulitple platforms. So this one board specific warning\nis not appropriate any more.\n\nSigned-off-by: Feng Tang \u003cfeng.tang@intel.com\u003e\nSigned-off-by: Len Brown \u003clen.brown@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "371122fc6eef7cafc8acaf0891fd15cf623388a3", "tree": "979b673c8916a0a7c0a5ae392e2dc29bd7d097ae", "parents": [ "890b3d0ea620c942718dd29d601a7aaa4362280b" ], "author": { "name": "Feng Tang", "email": "feng.tang@intel.com", "time": "Mon Jun 04 15:00:04 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:04:06 2012 -0700" }, "message": "ACPI: Make acpi_skip_timer_override cover all source_irq\u003d\u003d0 cases\n\ncommit ae10ccdc3093486f8c2369d227583f9d79f628e5 upstream.\n\nCurrently when acpi_skip_timer_override is set, it only cover the\n(source_irq \u003d\u003d 0 \u0026\u0026 global_irq \u003d\u003d 2) cases. While there is also\nplatform which need use this option and its global_irq is not 2.\nThis patch will extend acpi_skip_timer_override to cover all\ntimer overriding cases as long as the source irq is 0.\n\nThis is the first part of a fix to kernel bug bugzilla 40002:\n\t\"IRQ 0 assigned to VGA\"\nhttps://bugzilla.kernel.org/show_bug.cgi?id\u003d40002\n\nReported-and-tested-by: Szymon Kowalczyk \u003cfazerxlo@o2.pl\u003e\nSigned-off-by: Feng Tang \u003cfeng.tang@intel.com\u003e\nSigned-off-by: Len Brown \u003clen.brown@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dd3ce2fa647d42d524392d5e6a0647061fc64c67", "tree": "d6da72ba3b947b0d0ed0cb1fabcbf489bb257a42", "parents": [ "6ef0d09aaa123dfba91f3261c78827c4d85e786a" ], "author": { "name": "Benjamin Herrenschmidt", "email": "benh@kernel.crashing.org", "time": "Tue Jul 10 18:37:56 2012 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:49 2012 -0700" }, "message": "powerpc: Fix build of some debug irq code\n\ncommit 21b2de341270bd7bb7a811027ffe63276d9b3b75 upstream.\n\nThere was a typo, checking for CONFIG_TRACE_IRQFLAG instead of\nCONFIG_TRACE_IRQFLAGS causing some useful debug code to not be\nbuilt\n\nThis in turns causes a build error on BookE 64-bit due to incorrect\nsemicolons at the end of a couple of macros, so let\u0027s fix that too\n\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6ef0d09aaa123dfba91f3261c78827c4d85e786a", "tree": "f12d26a03b0731dd554dd4115bfc260ec3a6a90d", "parents": [ "d3ae4a87530c1e10c0705995c87fe8a7b4267f4b" ], "author": { "name": "Benjamin Herrenschmidt", "email": "benh@kernel.crashing.org", "time": "Tue Jul 10 18:36:40 2012 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:49 2012 -0700" }, "message": "powerpc: More fixes for lazy IRQ vs. idle\n\ncommit be2cf20a5ad31ebb13562c1c866ecc626fbd721e upstream.\n\nLooks like we still have issues with pSeries and Cell idle code\nvs. the lazy irq state. In fact, the reset fixes that went upstream\nare exposing the problem more by causing BUG_ON() to trigger (which\nthis patch turns into a WARN_ON instead).\n\nWe need to be careful when using a variant of low power state that\nhas the side effect of turning interrupts back on, to properly set\nall the SW \u0026 lazy state to look as if everything is enabled before\nwe enter the low power state with MSR:EE off as we will return with\nMSR:EE on. If not, we have a discrepancy of state which can cause\nthings to go very wrong later on.\n\nThis patch moves the logic into a helper and uses it from the\npseries and cell idle code. The power4/970 idle code already got\nthings right (in assembly even !) so I\u0027m not touching it. The power7\n\"bare metal\" idle code is subtly different and correct. Remains PA6T\nand some hypervisor based Cell platforms which have questionable\ncode in there, but they are mostly dead platforms so I\u0027ll fix them\nwhen I manage to get final answers from the respective maintainers\nabout how the low power state actually works on them.\n\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7e9356ed7ba29f1f76d7b5fae6b3c9f128663741", "tree": "5a3d695db328a3b0c8947f14a4886121932075be", "parents": [ "9b385370031c7880d19ce46849d3768aa30b3e09" ], "author": { "name": "Anton Blanchard", "email": "anton@samba.org", "time": "Thu Jun 28 19:28:57 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:23 2012 -0700" }, "message": "powerpc/xmon: Use cpumask iterator to avoid warning\n\ncommit bc1d7702910c7c7e88eb60b58429dbfe293683ce upstream.\n\nWe have a bug report where the kernel hits a warning in the cpumask\ncode:\n\nWARNING: at include/linux/cpumask.h:107\n\nWhich is:\n WARN_ON_ONCE(cpu \u003e\u003d nr_cpumask_bits);\n\nThe backtrace is:\n cpu_cmd\n cmds\n xmon_core\n xmon\n die\n\nxmon is iterating through 0 to NR_CPUS. I\u0027m not sure why we are still\nopen coding this but iterating above nr_cpu_ids is definitely a bug.\n\nThis patch iterates through all possible cpus, in case we issue a\nsystem reset and CPUs in an offline state call in.\n\nPerhaps the old code was trying to handle CPUs that were in the\npartition but were never started (eg kexec into a kernel with an\nnr_cpus\u003d boot option). They are going to die way before we get into\nxmon since we haven\u0027t set any kernel state up for them.\n\nSigned-off-by: Anton Blanchard \u003canton@samba.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9b385370031c7880d19ce46849d3768aa30b3e09", "tree": "5abd9db7a72ac366a1ffbba0afd5008718891c3d", "parents": [ "937bff779cd840aca9f74dd7f2d43dafad3979bb" ], "author": { "name": "Michael Neuling", "email": "mikey@neuling.org", "time": "Mon Jun 25 13:33:11 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:22 2012 -0700" }, "message": "powerpc/kvm: sldi should be sld\n\ncommit 2f584a146a2965b82fce89b8d2f95dc5cfe468d0 upstream.\n\nSince we are taking a registers, this should never have been an sldi.\nTalking to paulus offline, this is the correct fix.\n\nWas introduced by:\n commit 19ccb76a1938ab364a412253daec64613acbf3df\n Author: Paul Mackerras \u003cpaulus@samba.org\u003e\n Date: Sat Jul 23 17:42:46 2011 +1000\n\nTalking to paulus, this shouldn\u0027t be a literal.\n\nSigned-off-by: Michael Neuling \u003cmikey@neuling.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "937bff779cd840aca9f74dd7f2d43dafad3979bb", "tree": "0292851c004d3bd9f47b138698dc47695eedd950", "parents": [ "45500e587ad1c2ea809c52961675c4eb9befcab5" ], "author": { "name": "Nicolas Pitre", "email": "nicolas.pitre@linaro.org", "time": "Wed Jun 27 17:28:57 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:22 2012 -0700" }, "message": "ARM: 7438/1: fill possible PMD empty section gaps\n\ncommit 19b52abe3c5d759661500a1dc810924369b2ad46 upstream.\n\nOn ARM with the 2-level page table format, a PMD entry is represented by\ntwo consecutive section entries covering 2MB of virtual space.\n\nHowever, static mappings always were allowed to use separate 1MB section\nentries. This means in practice that a static mapping may create half\npopulated PMDs via create_mapping().\n\nSince commit 0536bdf33f (ARM: move iotable mappings within the vmalloc\nregion) those static mappings are located in the vmalloc area. We must\nensure no such half populated PMDs are accessible once vmalloc() or\nioremap() start looking at the vmalloc area for nearby free virtual\naddress ranges, or various things leading to a kernel crash will happen.\n\nSigned-off-by: Nicolas Pitre \u003cnico@linaro.org\u003e\nReported-by: Santosh Shilimkar \u003csantosh.shilimkar@ti.com\u003e\nTested-by: \"R, Sricharan\" \u003cr.sricharan@ti.com\u003e\nReviewed-by: Catalin Marinas \u003ccatalin.marinas@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "45500e587ad1c2ea809c52961675c4eb9befcab5", "tree": "524a526626520a175906b88a3eedf808ddbdb0d4", "parents": [ "7abbc8e46545b3c98734484b4fbfaf849ed29c27" ], "author": { "name": "Jonghwan Choi", "email": "jhbird.choi@samsung.com", "time": "Wed Jun 20 17:05:37 2012 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:22 2012 -0700" }, "message": "ARM: SAMSUNG: Should check for IS_ERR(clk) instead of NULL\n\ncommit a5d8f4765f0e92ef027492a8cb979c5b8d45f2c3 upstream.\n\nOn the error condition clk_get() returns ERR_PTR().\n\nSigned-off-by: Jonghwan Choi \u003cjhbird.choi@samsung.com\u003e\nSigned-off-by: Kukjin Kim \u003ckgene.kim@samsung.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7abbc8e46545b3c98734484b4fbfaf849ed29c27", "tree": "d07200decf873a372a835471df890ec23f5ee62b", "parents": [ "ee1602ff18545ddf7f19638fb350e4eec2030c0d" ], "author": { "name": "Jose Miguel Goncalves", "email": "jose.goncalves@inov.pt", "time": "Sat May 12 06:11:49 2012 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:22 2012 -0700" }, "message": "ARM: SAMSUNG: Fix for S3C2412 EBI memory mapping\n\ncommit 3dca938656c7b0ff6b0717a5dde0f5f45e592be5 upstream.\n\nWhile upgrading the kernel on a S3C2412 based board I\u0027ve noted\nthat it was impossible to boot the board with a 2.6.32 or upper\nkernel. I\u0027ve tracked down the problem to the EBI virtual memory\nmapping that is in conflict with the IO mapping definition in\narch/arm/mach-s3c24xx/s3c2412.c.\n\nSigned-off-by: Jose Miguel Goncalves \u003cjose.goncalves@inov.pt\u003e\nSigned-off-by: Kukjin Kim \u003ckgene.kim@samsung.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ee1602ff18545ddf7f19638fb350e4eec2030c0d", "tree": "5fb6a4f86e7ef199685a19a996178b5c9d8e7252", "parents": [ "8057f6c444173496806618f2fe173c2f02fb3995" ], "author": { "name": "Anton Blanchard", "email": "anton@samba.org", "time": "Wed Jun 27 13:13:52 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:21 2012 -0700" }, "message": "powerpc: check_and_cede_processor() never cedes\n\ncommit 0b17ba7258db83cd02da560884e053b85de371f2 upstream.\n\nCommit f948501b36c6 (\"Make hard_irq_disable() actually hard-disable\ninterrupts\") caused check_and_cede_processor to stop working.\n-\u003eirq_happened will never be zero right after a hard_irq_disable\nso the compiler removes the call to cede_processor completely.\n\nThe bug was introduced back in the lazy interrupt handling rework\nof 3.4 but was hidden until recently because hard_irq_disable did\nnothing.\n\nThis issue will eventually appear in 3.4 stable since the\nhard_irq_disable fix is marked stable, so mark this one for stable\ntoo.\n\nSigned-off-by: Anton Blanchard \u003canton@samba.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8057f6c444173496806618f2fe173c2f02fb3995", "tree": "452d6469fee0fd2a457ea1aeff2fe4cc8ea7eccb", "parents": [ "3fb55c2a681f7618c828b5853abc27f86d7e9fe1" ], "author": { "name": "Michael Neuling", "email": "mikey@neuling.org", "time": "Tue Jun 26 21:26:37 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:21 2012 -0700" }, "message": "powerpc/pseries: Fix software invalidate TCE\n\ncommit bc6dc752f35488160ffac07ae91bed1bddaea32a upstream.\n\nThe following added support for powernv but broke pseries/BML:\n 1f1616e powerpc/powernv: Add TCE SW invalidation support\n\nTCE_PCI_SW_INVAL was split into FREE and CREATE flags but the tests in\nthe pseries code were not updated to reflect this.\n\nSigned-off-by: Michael Neuling \u003cmikey@neuling.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3fb55c2a681f7618c828b5853abc27f86d7e9fe1", "tree": "5f07892b4ec591e4e319bcd3d3bbc21cac16a231", "parents": [ "3f8d5752c3926dab96e00bfb5d0c8e2f015a975e" ], "author": { "name": "Michael Neuling", "email": "mikey@neuling.org", "time": "Tue Jun 19 20:01:45 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:21 2012 -0700" }, "message": "powerpc: Fix uninitialised error in numa.c\n\ncommit 82b2521d257b5c0efd51821cf5fa306e53bbb6ba upstream.\n\nchroma_defconfig currently gives me this with gcc 4.6:\n arch/powerpc/mm/numa.c:638:13: error: \u0027dm\u0027 may be used uninitialized in this function [-Werror\u003duninitialized]\n\nIt\u0027s a bogus warning/error since of_get_drconf_memory() only writes it\nanyway.\n\nSigned-off-by: Michael Neuling \u003cmikey@neuling.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3f8d5752c3926dab96e00bfb5d0c8e2f015a975e", "tree": "32ca440fda746c596e5099eefe6960904e984c64", "parents": [ "9fe9217b874769f0b42bc4f8de4fc3df785e9ef3" ], "author": { "name": "Steven Rostedt", "email": "rostedt@goodmis.org", "time": "Mon Jun 04 16:27:54 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:21 2012 -0700" }, "message": "powerpc/ftrace: Do not trace restore_interrupts()\n\ncommit 2d773aa4810d4a612d1c879faacc38594cc3f841 upstream.\n\nAs I was adding code that affects all archs, I started testing function\ntracer against PPC64 and found that it currently locks up with 3.4\nkernel. I figured it was due to tracing a function that shouldn\u0027t be, so\nI went through the following process to bisect to find the culprit:\n\n cat /debug/tracing/available_filter_functions \u003e t\n num\u003d`wc -l t`\n sed -ne \"1,${num}p\" t \u003e t1\n let num\u003dnum+1\n sed -ne \"${num},$p\" t \u003e t2\n cat t1 \u003e /debug/tracing/set_ftrace_filter\n echo function /debug/tracing/current_tracer\n \u003cfailed? bisect t1, if not bisect t2\u003e\n\nIt finally came down to this function: restore_interrupts()\n\nI\u0027m not sure why this locks up the system. It just seems to prevent\nscheduling from occurring. Interrupts seem to still work, as I can ping\nthe box. But all user processes freeze.\n\nWhen restore_interrupts() is not traced, function tracing works fine.\n\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "c1389ce1e02c1e1f617d7cf70852ad5d9f9ef355", "tree": "16d857353115a638dc1ffb8010d15e4c8907ba1e", "parents": [ "c84299b8ddb3de60ac857aee396d709346eed27f" ], "author": { "name": "Stephen Warren", "email": "swarren@nvidia.com", "time": "Mon Jun 18 15:01:50 2012 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Mon Jul 16 09:03:20 2012 -0700" }, "message": "ARM: tegra: make tegra_cpu_reset_handler_enable() __init\n\ncommit 6355f25ed965421725d92cf719fc63008690ca1c upstream.\n\nThis solves a section mismatch warning. I hadn\u0027t noticed this before,\nbecause my compiler was inlining tegra_cpu_reset_handler_enable() inside\ntegra_cpu_reset_handler_init(), which is already __init, but I switched\ncompilers and it stopped doing that.\n\nSigned-off-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nSigned-off-by: Olof Johansson \u003colof@lixom.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d6bc383209efd8a57b3c73ef2524a98df32c7bcc", "tree": "68755644c839229bcbfe77f08a5fffce3ab034bb", "parents": [ "231afb7c7ded9bf798b71efdf576615e91c367af" ], "author": { "name": "Paul Mackerras", "email": "paulus@samba.org", "time": "Fri Jun 15 14:51:39 2012 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Jun 22 11:36:57 2012 -0700" }, "message": "Make hard_irq_disable() actually hard-disable interrupts\n\ncommit f948501b36c6b3d9352ce212a197098a7e958971 upstream.\n\nAt present, hard_irq_disable() does nothing on powerpc because of\nthis code in include/linux/interrupt.h:\n\n #ifndef hard_irq_disable\n #define hard_irq_disable() do { } while(0)\n #endif\n\nSo we need to make our hard_irq_disable be a macro. It was previously\na macro until commit 7230c56441 (\"powerpc: Rework lazy-interrupt\nhandling\") changed it to a static inline function.\n\nAcked-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Paul Mackerras \u003cpaulus@samba.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n--\n arch/powerpc/include/asm/hw_irq.h | 3 +++\n 1 file changed, 3 insertions(+)\n\n" }, { "commit": "c7aa88da6b435fb45b01fe6076caf73ee6e529ae", "tree": "8eb45ab3382016bc3b0f50e5bc2bb7ff334a882b", "parents": [ "2da19ffd395d0fdba4ccbc4a3c751554059d4aa3" ], "author": { "name": "Andre Przywara", "email": "andre.przywara@amd.com", "time": "Tue May 29 13:07:31 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Jun 22 11:36:54 2012 -0700" }, "message": "xen/setup: filter APERFMPERF cpuid feature out\n\ncommit 5e626254206a709c6e937f3dda69bf26c7344f6f upstream.\n\nXen PV kernels allow access to the APERF/MPERF registers to read the\neffective frequency. Access to the MSRs is however redirected to the\ncurrently scheduled physical CPU, making consecutive read and\ncompares unreliable. In addition each rdmsr traps into the hypervisor.\nSo to avoid bogus readouts and expensive traps, disable the kernel\ninternal feature flag for APERF/MPERF if running under Xen.\nThis will\na) remove the aperfmperf flag from /proc/cpuinfo\nb) not mislead the power scheduler (arch/x86/kernel/cpu/sched.c) to\n use the feature to improve scheduling (by default disabled)\nc) not mislead the cpufreq driver to use the MSRs\n\nThis does not cover userland programs which access the MSRs via the\ndevice file interface, but this will be addressed separately.\n\nSigned-off-by: Andre Przywara \u003candre.przywara@amd.com\u003e\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "688b04fe535dafad0849c1980361d9f2a1596a7e", "tree": "1b34cee04f62f1fa9e4374ab154ea4b62857a8ef", "parents": [ "9ffa519e1b6c7db54ce371a809dd45584aff42bf" ], "author": { "name": "Jaccon Bastiaansen", "email": "jaccon.bastiaansen@gmail.com", "time": "Mon Apr 30 11:53:43 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Jun 22 11:36:52 2012 -0700" }, "message": "ARM i.MX imx21ads: Fix overlapping static i/o mappings\n\ncommit 350ab15bb2ffe7103bc6bf6c634f3c5b286eaf2a upstream.\n\nThe statically defined I/O memory regions for the i.MX21 on chip\nperipherals and the on board I/O peripherals of the i.MX21ADS board\noverlap. This results in a kernel crash during startup. This is fixed\nby reducing the memory range for the on board I/O peripherals to the\nactually required range.\n\nSigned-off-by: Jaccon Bastiaansen \u003cjaccon.bastiaansen@gmail.com\u003e\nSigned-off-by: Sascha Hauer \u003cs.hauer@pengutronix.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9ffa519e1b6c7db54ce371a809dd45584aff42bf", "tree": "a52ee3cd0edaa21513e0090597b2083b73d92edd", "parents": [ "8bca81891d1b2a8849bbfb54dcd0ac74ce5de85f" ], "author": { "name": "Shawn Guo", "email": "shawn.guo@linaro.org", "time": "Tue May 22 22:13:46 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Jun 22 11:36:52 2012 -0700" }, "message": "ARM: imx6: exit coherency when shutting down a cpu\n\ncommit 602bf40971d7f9a1ec0b7ba2b7e6427849828651 upstream.\n\nThere is a system hang issue on imx6q which can easily be seen with\nrunning a cpu hotplug stress testing (hotplug secondary cores from\nuser space via sysfs interface for thousands iterations).\n\nIt turns out that the issue is caused by coherency of the cpu that\nis being shut down. When shutting down a cpu, we need to have the\ncpu exit coherency to prevent it from receiving cache, TLB, or BTB\nmaintenance operations broadcast by other CPUs in the cluster.\n\nCopy cpu_enter_lowpower() and cpu_leave_lowpower() from mach-vexpress\nto have coherency properly handled in platform_cpu_die(), thus fix\nthe issue.\n\nSigned-off-by: Shawn Guo \u003cshawn.guo@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" } ], "next": "8bca81891d1b2a8849bbfb54dcd0ac74ce5de85f" }