)]}' { "log": [ { "commit": "65404686fff96a6f84f86628d86686b702faeda1", "tree": "e5076d4ce7a9d1bb6ceae3edea074ff9e0d6909c", "parents": [ "400cbedf7d18881f36408095b5f3387c53aaa2a1" ], "author": { "name": "Alan Stern", "email": "stern@rowland.harvard.edu", "time": "Tue Jan 21 10:38:45 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:46 2014 -0800" }, "message": "usb-storage: add unusual-devs entry for BlackBerry 9000\n\ncommit c5637e5119c43452a00e27c274356b072263ecbb upstream.\n\nThis patch adds an unusual-devs entry for the BlackBerry 9000. This\nfixes Bugzilla #22442.\n\nSigned-off-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nReported-by: Moritz Moeller-Herrmann \u003cmoritz-kernel@moeller-herrmann.de\u003e\nTested-by: Moritz Moeller-Herrmann \u003cmoritz-kernel@moeller-herrmann.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "400cbedf7d18881f36408095b5f3387c53aaa2a1", "tree": "1a4c64b4e2db4d31649045c55c35b1a7f35a6ef4", "parents": [ "1c41ee3a84da5eff41aaf5e58b18a3233e4ae637" ], "author": { "name": "Ulrich Hahn", "email": "uhahn@eanco.de", "time": "Sun Feb 02 14:42:52 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:46 2014 -0800" }, "message": "USB: ftdi_sio: add Tagsys RFID Reader IDs\n\ncommit 76f24e3f39a1a94bab0d54e98899d64abcd9f69c upstream.\n\nAdding two more IDs to the ftdi_sio usb serial driver.\nIt now connects Tagsys RFID readers.\nThere might be more IDs out there for other Tagsys models.\n\nSigned-off-by: Ulrich Hahn \u003cuhahn@eanco.de\u003e\nCc: Johan Hovold \u003cjohan@hovold.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1c41ee3a84da5eff41aaf5e58b18a3233e4ae637", "tree": "6dc312e4f688ddd3dac14ac5bac763e3e37c486b", "parents": [ "402d5390c91374880c4028490087b8cffe338be3" ], "author": { "name": "Bjørn Mork", "email": "bjorn@mork.no", "time": "Tue Jan 14 18:56:54 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:46 2014 -0800" }, "message": "usb: ftdi_sio: add Mindstorms EV3 console adapter\n\ncommit 67847baee056892dc35efb9c3fd05ae7f075588c upstream.\n\nSigned-off-by: Bjørn Mork \u003cbjorn@mork.no\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "402d5390c91374880c4028490087b8cffe338be3", "tree": "7f58e0523ad27cfce4f3e80a58cdf15fe3cb21a2", "parents": [ "dce0ea4a4732af1333525b76bde5572073d4bbfa" ], "author": { "name": "Hartmut Knaack", "email": "knaack.h@gmx.de", "time": "Wed Jan 01 23:04:00 2014 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:45 2014 -0800" }, "message": "staging:iio:ad799x fix error_free_irq which was freeing an irq that may not have been requested\n\ncommit 38408d056188be29a6c4e17f3703c796551bb330 upstream.\n\nOnly free an IRQ in error_free_irq, if it has been requested previously.\n\nSigned-off-by: Hartmut Knaack \u003cknaack.h@gmx.de\u003e\nAcked-by: Lars-Peter Clausen \u003clars@metafoo.de\u003e\nSigned-off-by: Jonathan Cameron \u003cjic23@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dce0ea4a4732af1333525b76bde5572073d4bbfa", "tree": "5ac5ac997404b46d88112aaf1ad219eb5d4d2b98", "parents": [ "cc01cae91828041fd1dfa5c1b6bf09221c1659c8" ], "author": { "name": "Lars Poeschel", "email": "poeschel@lemonage.de", "time": "Tue Jan 07 13:34:37 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:45 2014 -0800" }, "message": "tty: n_gsm: Fix for modems with brk in modem status control\n\ncommit 3ac06b905655b3ef2fd2196bab36e4587e1e4e4f upstream.\n\n3GPP TS 07.10 states in section 5.4.6.3.7:\n\"The length byte contains the value 2 or 3 ... depending on the break\nsignal.\" The break byte is optional and if it is sent, the length is\n3. In fact the driver was not able to work with modems that send this\nbreak byte in their modem status control message. If the modem just\nsends the break byte if it is really set, then weird things might\nhappen.\nThe code for deconding the modem status to the internal linux\npresentation in gsm_process_modem has already a big comment about\nthis 2 or 3 byte length thing and it is already able to decode the\nbrk, but the code calling the gsm_process_modem function in\ngsm_control_modem does not encode it and hand it over the right way.\nThis patch fixes this.\nWithout this fix if the modem sends the brk byte in it\u0027s modem status\ncontrol message the driver will hang when opening a muxed channel.\n\nSigned-off-by: Lars Poeschel \u003cpoeschel@lemonage.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cc01cae91828041fd1dfa5c1b6bf09221c1659c8", "tree": "dc6fdf8336b17a105df512ebd6e4cb807cdc3fce", "parents": [ "e24cfb1b4f4942681c3ce382e83cc090f0ad1550" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Feb 07 17:10:26 2014 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:45 2014 -0800" }, "message": "lockd: send correct lock when granting a delayed lock.\n\ncommit 2ec197db1a56c9269d75e965f14c344b58b2a4f6 upstream.\n\nIf an NFS client attempts to get a lock (using NLM) and the lock is\nnot available, the server will remember the request and when the lock\nbecomes available it will send a GRANT request to the client to\nprovide the lock.\n\nIf the client already held an adjacent lock, the GRANT callback will\nreport the union of the existing and new locks, which can confuse the\nclient.\n\nThis happens because __posix_lock_file (called by vfs_lock_file)\nupdates the passed-in file_lock structure when adjacent or\nover-lapping locks are found.\n\nTo avoid this problem we take a copy of the two fields that can\nbe changed (fl_start and fl_end) before the call and restore them\nafterwards.\nAn alternate would be to allocate a \u0027struct file_lock\u0027, initialise it,\nuse locks_copy_lock() to take a copy, then locks_release_private()\nafter the vfs_lock_file() call. But that is a lot more work.\n\nReported-by: Olaf Kirch \u003cokir@suse.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: J. Bruce Fields \u003cbfields@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n--\nv1 had a couple of issues (large on-stack struct and didn\u0027t really work properly).\nThis version is much better tested.\nSigned-off-by: J. Bruce Fields \u003cbfields@redhat.com\u003e\n\n" }, { "commit": "e24cfb1b4f4942681c3ce382e83cc090f0ad1550", "tree": "f76ef4cbcc279ba32a47feb047d0f407ab53c450", "parents": [ "566d9875cb708d907f8a0b3c2a0dffb96dcb973c" ], "author": { "name": "Paul Bolle", "email": "pebolle@tiscali.nl", "time": "Tue Feb 04 23:23:12 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:45 2014 -0800" }, "message": "raw: test against runtime value of max_raw_minors\n\ncommit 5bbb2ae3d6f896f8d2082d1eceb6131c2420b7cf upstream.\n\nbind_get() checks the device number it is called with. It uses\nMAX_RAW_MINORS for the upper bound. But MAX_RAW_MINORS is set at compile\ntime while the actual number of raw devices can be set at runtime. This\nmeans the test can either be too strict or too lenient. And if the test\nends up being too lenient bind_get() might try to access memory beyond\nwhat was allocated for \"raw_devices\".\n\nSo check against the runtime value (max_raw_minors) in this function.\n\nSigned-off-by: Paul Bolle \u003cpebolle@tiscali.nl\u003e\nAcked-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "566d9875cb708d907f8a0b3c2a0dffb96dcb973c", "tree": "d4e5862a92812de5ed1a0ca8ebd2420237aa488d", "parents": [ "9558f9d82eed2e0015783c553794aeed79dfa0f8" ], "author": { "name": "Geert Uytterhoeven", "email": "geert+renesas@linux-m68k.org", "time": "Tue Jan 28 10:33:03 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:45 2014 -0800" }, "message": "spi: Fix crash with double message finalisation on error handling\n\ncommit 1f802f8249a0da536877842c43c7204064c4de8b upstream.\n\nThis reverts commit e120cc0dcf2880a4c5c0a6cb27b655600a1cfa1d.\n\nIt causes a NULL pointer dereference with drivers using the generic\nspi_transfer_one_message(), which always calls\nspi_finalize_current_message(), which zeroes master-\u003ecur_msg.\n\nDrivers implementing transfer_one_message() theirselves must always call\nspi_finalize_current_message(), even if the transfer failed:\n\n * @transfer_one_message: the subsystem calls the driver to transfer a single\n * message while queuing transfers that arrive in the meantime. When the\n * driver is finished with this message, it must call\n * spi_finalize_current_message() so the subsystem can issue the next\n * transfer\n\nSigned-off-by: Geert Uytterhoeven \u003cgeert+renesas@linux-m68k.org\u003e\nSigned-off-by: Mark Brown \u003cbroonie@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9558f9d82eed2e0015783c553794aeed79dfa0f8", "tree": "eb7d3ed29dd1a4a54c8a9fe83117c0f3a2999dff", "parents": [ "021139f22c744a254870dcb23b326037a32a1aa7" ], "author": { "name": "Martin Schwidefsky", "email": "schwidefsky@de.ibm.com", "time": "Mon Feb 03 17:37:15 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:45 2014 -0800" }, "message": "s390: fix kernel crash due to linkage stack instructions\n\ncommit 8d7f6690cedb83456edd41c9bd583783f0703bf0 upstream.\n\nThe kernel currently crashes with a low-address-protection exception\nif a user space process executes an instruction that tries to use the\nlinkage stack. Set the base-ASTE origin and the subspace-ASTE origin\nof the dispatchable-unit-control-table to point to a dummy ASTE.\nSet up control register 15 to point to an empty linkage stack with no\nroom left.\n\nA user space process with a linkage stack instruction will still crash\nbut with a different exception which is correctly translated to a\nsegmentation fault instead of a kernel oops.\n\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "021139f22c744a254870dcb23b326037a32a1aa7", "tree": "d8136577e50f76a00676a4675d0b793ba506e294", "parents": [ "fb11ab59b2999e2afee7c7fcd3687bf07b2fc988" ], "author": { "name": "Michael Holzheu", "email": "holzheu@linux.vnet.ibm.com", "time": "Thu Jan 30 16:14:02 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:45 2014 -0800" }, "message": "s390/dump: Fix dump memory detection\n\ncommit d7736ff5be31edaa4fe5ab62810c64529a24b149 upstream.\n\nDumps created by kdump or zfcpdump can contain invalid memory holes when\ndumping z/VM systems that have memory pressure.\n\nFor example:\n\n # zgetdump -i /proc/vmcore.\n Memory map:\n 0000000000000000 - 0000000000bfffff (12 MB)\n 0000000000e00000 - 00000000014fffff (7 MB)\n 000000000bd00000 - 00000000f3bfffff (3711 MB)\n\nThe memory detection function find_memory_chunks() issues tprot to\nfind valid memory chunks. In case of CMM it can happen that pages are\nmarked as unstable via set_page_unstable() in arch_free_page().\nIf z/VM has released that pages, tprot returns -EFAULT and indicates\na memory hole.\n\nSo fix this and switch off CMM in case of kdump or zfcpdump.\n\nSigned-off-by: Michael Holzheu \u003cholzheu@linux.vnet.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": "fb11ab59b2999e2afee7c7fcd3687bf07b2fc988", "tree": "45835c3a6f71d27876e248647723790aec483dd9", "parents": [ "ce5562e5704bf715fc3084d9f218e5ba3fbf0991" ], "author": { "name": "Johannes Berg", "email": "johannes.berg@intel.com", "time": "Sat Feb 01 00:16:23 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:45 2014 -0800" }, "message": "mac80211: fix fragmentation code, particularly for encryption\n\ncommit 338f977f4eb441e69bb9a46eaa0ac715c931a67f upstream.\n\nThe \"new\" fragmentation code (since my rewrite almost 5 years ago)\nerroneously sets skb-\u003elen rather than using skb_trim() to adjust\nthe length of the first fragment after copying out all the others.\nThis leaves the skb tail pointer pointing to after where the data\noriginally ended, and thus causes the encryption MIC to be written\nat that point, rather than where it belongs: immediately after the\ndata.\n\nThe impact of this is that if software encryption is done, then\n a) encryption doesn\u0027t work for the first fragment, the connection\n becomes unusable as the first fragment will never be properly\n verified at the receiver, the MIC is practically guaranteed to\n be wrong\n b) we leak up to 8 bytes of plaintext (!) of the packet out into\n the air\n\nThis is only mitigated by the fact that many devices are capable\nof doing encryption in hardware, in which case this can\u0027t happen\nas the tail pointer is irrelevant in that case. Additionally,\nfragmentation is not used very frequently and would normally have\nto be configured manually.\n\nFix this by using skb_trim() properly.\n\nFixes: 2de8e0d999b8 (\"mac80211: rewrite fragmentation\")\nReported-by: Jouni Malinen \u003cj@w1.fi\u003e\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ce5562e5704bf715fc3084d9f218e5ba3fbf0991", "tree": "82d8ace413b39e89e8ae9f40c45b4196f7c639d2", "parents": [ "2af3263a0d1d456ba63d7d167fadd7f08fd8fe1c" ], "author": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Mon Feb 10 14:25:41 2014 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:45 2014 -0800" }, "message": "fs/file.c:fdtable: avoid triggering OOMs from alloc_fdmem\n\ncommit 96c7a2ff21501691587e1ae969b83cbec8b78e08 upstream.\n\nRecently due to a spike in connections per second memcached on 3\nseparate boxes triggered the OOM killer from accept. At the time the\nOOM killer was triggered there was 4GB out of 36GB free in zone 1. The\nproblem was that alloc_fdtable was allocating an order 3 page (32KiB) to\nhold a bitmap, and there was sufficient fragmentation that the largest\npage available was 8KiB.\n\nI find the logic that PAGE_ALLOC_COSTLY_ORDER can\u0027t fail pretty dubious\nbut I do agree that order 3 allocations are very likely to succeed.\n\nThere are always pathologies where order \u003e 0 allocations can fail when\nthere are copious amounts of free memory available. Using the pigeon\nhole principle it is easy to show that it requires 1 page more than 50%\nof the pages being free to guarantee an order 1 (8KiB) allocation will\nsucceed, 1 page more than 75% of the pages being free to guarantee an\norder 2 (16KiB) allocation will succeed and 1 page more than 87.5% of\nthe pages being free to guarantee an order 3 allocate will succeed.\n\nA server churning memory with a lot of small requests and replies like\nmemcached is a common case that if anything can will skew the odds\nagainst large pages being available.\n\nTherefore let\u0027s not give external applications a practical way to kill\nlinux server applications, and specify __GFP_NORETRY to the kmalloc in\nalloc_fdmem. Unless I am misreading the code and by the time the code\nreaches should_alloc_retry in __alloc_pages_slowpath (where\n__GFP_NORETRY becomes signification). We have already tried everything\nreasonable to allocate a page and the only thing left to do is wait. So\nnot waiting and falling back to vmalloc immediately seems like the\nreasonable thing to do even if there wasn\u0027t a chance of triggering the\nOOM killer.\n\nSigned-off-by: \"Eric W. Biederman\" \u003cebiederm@xmission.com\u003e\nCc: Eric Dumazet \u003ceric.dumazet@gmail.com\u003e\nAcked-by: David Rientjes \u003crientjes@google.com\u003e\nCc: Cong Wang \u003ccwang@twopensource.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": "2af3263a0d1d456ba63d7d167fadd7f08fd8fe1c", "tree": "edf574498abd0056e1c9abe7de0a46564c26c83c", "parents": [ "dd12c7c4cb2167696bf8bacdcaa94cdeb8f74e3b" ], "author": { "name": "David Vrabel", "email": "david.vrabel@citrix.com", "time": "Tue Feb 04 18:53:56 2014 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sat Feb 22 10:32:45 2014 -0800" }, "message": "xen-blkfront: handle backend CLOSED without CLOSING\n\ncommit 3661371701e714f0cea4120f6a365340858fb4e4 upstream.\n\nBackend drivers shouldn\u0027t transistion to CLOSED unless the frontend is\nCLOSED. If a backend does transition to CLOSED too soon then the\nfrontend may not see the CLOSING state and will not properly shutdown.\n\nSo, treat an unexpected backend CLOSED state the same as CLOSING.\n\nSigned-off-by: David Vrabel \u003cdavid.vrabel@citrix.com\u003e\nAcked-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.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": "dd12c7c4cb2167696bf8bacdcaa94cdeb8f74e3b", "tree": "8a9b4cf12cb404ad669df2ad315e7840bafe3fef", "parents": [ "478b97d4d7c5468e2ea21ad34d344a4dac5ff230" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:46:04 2014 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:46:04 2014 -0800" }, "message": "Linux 3.4.81\n" }, { "commit": "478b97d4d7c5468e2ea21ad34d344a4dac5ff230", "tree": "2bdfc8e1021fce68e702ba187cccca00c52038ca", "parents": [ "26fead641f8e2a5052aa3cfc88caf876f0e84941" ], "author": { "name": "Jeff Layton", "email": "jlayton@redhat.com", "time": "Thu Aug 02 14:30:56 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:33 2014 -0800" }, "message": "nfs: tear down caches in nfs_init_writepagecache when allocation fails\n\ncommit 3dd4765fce04c0b4af1e0bc4c0b10f906f95fabc upstream.\n\n...and ensure that we tear down the nfs_commit_data cache too when\nunloading the module.\n\nCc: Bryan Schumaker \u003cbjschuma@netapp.com\u003e\nSigned-off-by: Jeff Layton \u003cjlayton@redhat.com\u003e\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\n[bwh: Backported to 3.2: drop the nfs_cdata_cachep cleanup; it doesn\u0027t exist]\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "26fead641f8e2a5052aa3cfc88caf876f0e84941", "tree": "8441d517c6bb82508196ac15a8f16228446dea82", "parents": [ "374d3a4168761631fe309e2bda8dc3bfb4eadcb6" ], "author": { "name": "Dan Rosenberg", "email": "drosenberg@vsecurity.com", "time": "Mon Jul 30 14:40:26 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:33 2014 -0800" }, "message": "lib/vsprintf.c: kptr_restrict: fix pK-error in SysRq show-all-timers(Q)\n\ncommit 3715c5309f6d175c3053672b73fd4f73be16fd07 upstream.\n\nWhen using ALT+SysRq+Q all the pointers are replaced with \"pK-error\" like\nthis:\n\n\t[23153.208033] .base: pK-error\n\nwith echo h \u003e /proc/sysrq-trigger it works:\n\n\t[23107.776363] .base: ffff88023e60d540\n\nThe intent behind this behavior was to return \"pK-error\" in cases where\nthe %pK format specifier was used in interrupt context, because the\nCAP_SYSLOG check wouldn\u0027t be meaningful. Clearly this should only apply\nwhen kptr_restrict is actually enabled though.\n\nReported-by: Stevie Trujillo \u003cstevie.trujillo@gmail.com\u003e\nSigned-off-by: Dan Rosenberg \u003cdan.j.rosenberg@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: Ben Hutchings \u003cben@decadent.org.uk\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "374d3a4168761631fe309e2bda8dc3bfb4eadcb6", "tree": "fed59f0dbc6d7bbe8f434fc7e4f6438ad54861c7", "parents": [ "ba37c708e4bb32505bc1c88a5a6ac1a434cfaee0" ], "author": { "name": "Asias He", "email": "asias@redhat.com", "time": "Fri May 25 16:03:27 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:33 2014 -0800" }, "message": "virtio-blk: Use block layer provided spinlock\n\ncommit 2c95a3290919541b846bee3e0fbaa75860929f53 upstream.\n\nBlock layer will allocate a spinlock for the queue if the driver does\nnot provide one in blk_init_queue().\n\nThe reason to use the internal spinlock is that blk_cleanup_queue() will\nswitch to use the internal spinlock in the cleanup code path.\n\n if (q-\u003equeue_lock !\u003d \u0026q-\u003e__queue_lock)\n q-\u003equeue_lock \u003d \u0026q-\u003e__queue_lock;\n\nHowever, processes which are in D state might have taken the driver\nprovided spinlock, when the processes wake up, they would release the\nblock provided spinlock.\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n[ BUG: bad unlock balance detected! ]\n3.4.0-rc7+ #238 Not tainted\n-------------------------------------\nfio/3587 is trying to release lock (\u0026(\u0026q-\u003e__queue_lock)-\u003erlock) at:\n[\u003cffffffff813274d2\u003e] blk_queue_bio+0x2a2/0x380\nbut there are no more locks to release!\n\nother info that might help us debug this:\n1 lock held by fio/3587:\n #0: (\u0026(\u0026vblk-\u003elock)-\u003erlock){......}, at:\n[\u003cffffffff8132661a\u003e] get_request_wait+0x19a/0x250\n\nOther drivers use block layer provided spinlock as well, e.g. SCSI.\n\nSwitching to the block layer provided spinlock saves a bit of memory and\ndoes not increase lock contention. Performance test shows no real\ndifference is observed before and after this patch.\n\nChanges in v2: Improve commit log as Michael suggested.\n\nCc: virtualization@lists.linux-foundation.org\nCc: kvm@vger.kernel.org\nSigned-off-by: Asias He \u003casias@redhat.com\u003e\nAcked-by: Michael S. Tsirkin \u003cmst@redhat.com\u003e\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\n[bwh: Backported to 3.2: adjust context]\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ba37c708e4bb32505bc1c88a5a6ac1a434cfaee0", "tree": "b578770a11a61a69ea9bab81506a468c8c79feb0", "parents": [ "b249f99c023402a192e1af812326c5092e64175f" ], "author": { "name": "Seth Forshee", "email": "seth.forshee@canonical.com", "time": "Tue Jul 24 23:54:11 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:33 2014 -0800" }, "message": "Input: synaptics - handle out of bounds values from the hardware\n\ncommit c0394506e69b37c47d391c2a7bbea3ea236d8ec8 upstream.\n\nThe touchpad on the Acer Aspire One D250 will report out of range values\nin the extreme lower portion of the touchpad. These appear as abrupt\nchanges in the values reported by the hardware from very low values to\nvery high values, which can cause unexpected vertical jumps in the\nposition of the mouse pointer.\n\nWhat seems to be happening is that the value is wrapping to a two\u0027s\ncompliment negative value of higher resolution than the 13-bit value\nreported by the hardware, with the high-order bits being truncated. This\npatch adds handling for these values by converting them to the\nappropriate negative values.\n\nThe only tricky part about this is deciding when to treat a number as\nnegative. It stands to reason that if out of range values can be\nreported on the low end then it could also happen on the high end, so\nnot all out of range values should be treated as negative. The approach\ntaken here is to split the difference between the maximum legitimate\nvalue for the axis and the maximum possible value that the hardware can\nreport, treating values greater than this number as negative and all\nother values as positive. This can be tweaked later if hardware is found\nthat operates outside of these parameters.\n\nBugLink: http://bugs.launchpad.net/bugs/1001251\nSigned-off-by: Seth Forshee \u003cseth.forshee@canonical.com\u003e\nReviewed-by: Daniel Kurtz \u003cdjkurtz@chromium.org\u003e\nSigned-off-by: Dmitry Torokhov \u003cdmitry.torokhov@gmail.com\u003e\n[bwh: Backported to 3.2: adjust context]\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b249f99c023402a192e1af812326c5092e64175f", "tree": "49b94c6486350105fe8334c9e81b105dc557f6af", "parents": [ "ec90b6113735a9f9fcb64a604b28f446fe03ded2" ], "author": { "name": "Bojan Smojver", "email": "bojan@rexursive.com", "time": "Sun Apr 29 22:42:06 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:33 2014 -0800" }, "message": "PM / Hibernate: Hibernate/thaw fixes/improvements\n\ncommit 5a21d489fd9541a4a66b9a500659abaca1b19a51 upstream.\n\n 1. Do not allocate memory for buffers from emergency pools, unless\n absolutely required. Do not warn about and do not retry non-essential\n failed allocations.\n\n 2. Do not check the amount of free pages left on every single page\n write, but wait until one map is completely populated and then check.\n\n 3. Set maximum number of pages for read buffering consistently, instead\n of inadvertently depending on the size of the sector type.\n\n 4. Fix copyright line, which I missed when I submitted the hibernation\n threading patch.\n\n 5. Dispense with bit shifting arithmetic to improve readability.\n\n 6. Really recalculate the number of pages required to be free after all\n allocations have been done.\n\n 7. Fix calculation of pages required for read buffering. Only count in\n pages that do not belong to high memory.\n\nSigned-off-by: Bojan Smojver \u003cbojan@rexursive.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crjw@sisk.pl\u003e\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ec90b6113735a9f9fcb64a604b28f446fe03ded2", "tree": "07c0fadb0081f3f0331eacaf721c746c9a399693", "parents": [ "230a0c3b5881b5493c06d382d799305b4ee603c5" ], "author": { "name": "Avi Kivity", "email": "avi@redhat.com", "time": "Sun Apr 22 17:02:11 2012 +0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:33 2014 -0800" }, "message": "KVM: Fix buffer overflow in kvm_set_irq()\n\ncommit f2ebd422f71cda9c791f76f85d2ca102ae34a1ed upstream.\n\nkvm_set_irq() has an internal buffer of three irq routing entries, allowing\nconnecting a GSI to three IRQ chips or on MSI. However setup_routing_entry()\ndoes not properly enforce this, allowing three irqchip routes followed by\nan MSI route to overflow the buffer.\n\nFix by ensuring that an MSI entry is added to an empty list.\n\nSigned-off-by: Avi Kivity \u003cavi@redhat.com\u003e\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "230a0c3b5881b5493c06d382d799305b4ee603c5", "tree": "aaa43c328f8f44993c2d68885dc6595805fd0cde", "parents": [ "45a0374fd5ee6c27349dc41e31db0bd0c87663ca" ], "author": { "name": "Nicholas Bellinger", "email": "nab@linux-iscsi.org", "time": "Sat Sep 29 17:15:37 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:33 2014 -0800" }, "message": "target/file: Re-enable optional fd_buffered_io\u003d1 operation\n\ncommit b32f4c7ed85c5cee2a21a55c9f59ebc9d57a2463 upstream.\n\nThis patch re-adds the ability to optionally run in buffered FILEIO mode\n(eg: w/o O_DSYNC) for device backends in order to once again use the\nLinux buffered cache as a write-back storage mechanism.\n\nThis logic was originally dropped with mainline v3.5-rc commit:\n\ncommit a4dff3043c231d57f982af635c9d2192ee40e5ae\nAuthor: Nicholas Bellinger \u003cnab@linux-iscsi.org\u003e\nDate: Wed May 30 16:25:41 2012 -0700\n\n target/file: Use O_DSYNC by default for FILEIO backends\n\nThis difference with this patch is that fd_create_virtdevice() now\nforces the explicit setting of emulate_write_cache\u003d1 when buffered FILEIO\noperation has been enabled.\n\n(v2: Switch to FDBD_HAS_BUFFERED_IO_WCE + add more detailed\n comment as requested by hch)\n\nReported-by: Ferry \u003ciscsitmp@bananateam.nl\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Nicholas Bellinger \u003cnab@linux-iscsi.org\u003e\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "45a0374fd5ee6c27349dc41e31db0bd0c87663ca", "tree": "6100f3b9ecf0054cbef08942181207e1105e8f7a", "parents": [ "f7441069a08718df307a9022095d53e558dcf2da" ], "author": { "name": "Nicholas Bellinger", "email": "nab@linux-iscsi.org", "time": "Wed May 30 16:25:41 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:33 2014 -0800" }, "message": "target/file: Use O_DSYNC by default for FILEIO backends\n\ncommit a4dff3043c231d57f982af635c9d2192ee40e5ae upstream.\n\nConvert to use O_DSYNC for all cases at FILEIO backend creation time to\navoid the extra syncing of pure timestamp updates with legacy O_SYNC during\ndefault operation as recommended by hch. Continue to do this independently of\nWrite Cache Enable (WCE) bit, as WCE\u003d0 is currently the default for all backend\ndevices and enabled by user on per device basis via attrib/emulate_write_cache.\n\nThis patch drops the now unnecessary fd_buffered_io\u003d token usage that was\noriginally signalling when to explictly disable O_SYNC at backend creation\ntime for buffered I/O operation. This can end up being dangerous for a number\nof reasons during physical node failure, so go ahead and drop this option\nfor now when O_DSYNC is used as the default.\n\nAlso allow explict FUA WRITEs -\u003e vfs_fsync_range() call to function in\nfd_execute_cmd() independently of WCE bit setting.\n\nReported-by: Christoph Hellwig \u003chch@lst.de\u003e\nCc: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Nicholas Bellinger \u003cnab@linux-iscsi.org\u003e\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\n[bwh: Backported to 3.2:\n - We have fd_do_task() and not fd_execute_cmd()\n - Various fields are in struct se_task rather than struct se_cmd\n - fd_create_virtdevice() flags initialisation hasn\u0027t been cleaned up]\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f7441069a08718df307a9022095d53e558dcf2da", "tree": "fd8d5a16208c84988c101f92faef0249f406b1cd", "parents": [ "f5a4c4b79e57f875b6788f6f8352ca246bfd8450" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Fri Oct 04 09:29:12 2013 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:33 2014 -0800" }, "message": "IB/qib: Convert qib_user_sdma_pin_pages() to use get_user_pages_fast()\n\ncommit 603e7729920e42b3c2f4dbfab9eef4878cb6e8fa upstream.\n\nqib_user_sdma_queue_pkts() gets called with mmap_sem held for\nwriting. Except for get_user_pages() deep down in\nqib_user_sdma_pin_pages() we don\u0027t seem to need mmap_sem at all. Even\nmore interestingly the function qib_user_sdma_queue_pkts() (and also\nqib_user_sdma_coalesce() called somewhat later) call copy_from_user()\nwhich can hit a page fault and we deadlock on trying to get mmap_sem\nwhen handling that fault.\n\nSo just make qib_user_sdma_pin_pages() use get_user_pages_fast() and\nleave mmap_sem locking for mm.\n\nThis deadlock has actually been observed in the wild when the node\nis under memory pressure.\n\nReviewed-by: Mike Marciniszyn \u003cmike.marciniszyn@intel.com\u003e\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Roland Dreier \u003croland@purestorage.com\u003e\n[Backported to 3.4: (Thank to Ben Hutchings)\n - Adjust context\n - Adjust indentation and nr_pages argument in qib_user_sdma_pin_pages()]\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nSigned-off-by: Mike Marciniszyn \u003cmike.marciniszyn@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f5a4c4b79e57f875b6788f6f8352ca246bfd8450", "tree": "936b2200d4581b36faa0c94fab560013486885be", "parents": [ "e2d51f27e382be7b70a755f3ea2fbbeacdb50834" ], "author": { "name": "Peter Zijlstra", "email": "a.p.zijlstra@chello.nl", "time": "Thu May 17 17:15:29 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "sched/nohz: Fix rq-\u003ecpu_load calculations some more\n\ncommit 5aaa0b7a2ed5b12692c9ffb5222182bd558d3146 upstream.\n\nFollow up on commit 556061b00 (\"sched/nohz: Fix rq-\u003ecpu_load[]\ncalculations\") since while that fixed the busy case it regressed the\nmostly idle case.\n\nAdd a callback from the nohz exit to also age the rq-\u003ecpu_load[]\narray. This closes the hole where either there was no nohz load\nbalance pass during the nohz, or there was a \u0027significant\u0027 amount of\nidle time between the last nohz balance and the nohz exit.\n\nSo we\u0027ll update unconditionally from the tick to not insert any\naccidental 0 load periods while busy, and we try and catch up from\nnohz idle balance and nohz exit. Both these are still prone to missing\na jiffy, but that has always been the case.\n\nSigned-off-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nCc: pjt@google.com\nCc: Venkatesh Pallipadi \u003cvenki@google.com\u003e\nLink: http://lkml.kernel.org/n/tip-kt0trz0apodbf84ucjfdbr1a@git.kernel.org\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e2d51f27e382be7b70a755f3ea2fbbeacdb50834", "tree": "893a14b43a9eda39df07c1a6879c74f197977358", "parents": [ "1c2bd0db1189643691557ff34406906b053cef92" ], "author": { "name": "Peter Zijlstra", "email": "a.p.zijlstra@chello.nl", "time": "Fri May 11 17:31:26 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "sched/nohz: Fix rq-\u003ecpu_load[] calculations\n\ncommit 556061b00c9f2fd6a5524b6bde823ef12f299ecf upstream.\n\nWhile investigating why the load-balancer did funny I found that the\nrq-\u003ecpu_load[] tables were completely screwy.. a bit more digging\nrevealed that the updates that got through were missing ticks followed\nby a catchup of 2 ticks.\n\nThe catchup assumes the cpu was idle during that time (since only nohz\ncan cause missed ticks and the machine is idle etc..) this means that\nesp. the higher indices were significantly lower than they ought to\nbe.\n\nThe reason for this is that its not correct to compare against jiffies\non every jiffy on any other cpu than the cpu that updates jiffies.\n\nThis patch cludges around it by only doing the catch-up stuff from\nnohz_idle_balance() and doing the regular stuff unconditionally from\nthe tick.\n\nSigned-off-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nCc: pjt@google.com\nCc: Venkatesh Pallipadi \u003cvenki@google.com\u003e\nLink: http://lkml.kernel.org/n/tip-tp4kj18xdd5aj4vvj0qg55s2@git.kernel.org\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1c2bd0db1189643691557ff34406906b053cef92", "tree": "7ca9b005df493f23b9d3230decc8dd7e8e6d60e7", "parents": [ "2955866584c57545061dc38dc69de3461437aa9a" ], "author": { "name": "Steven Rostedt", "email": "rostedt@goodmis.org", "time": "Tue Feb 11 14:50:01 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "ftrace: Have function graph only trace based on global_ops filters\n\ncommit 23a8e8441a0a74dd612edf81dc89d1600bc0a3d1 upstream.\n\nDoing some different tests, I discovered that function graph tracing, when\nfiltered via the set_ftrace_filter and set_ftrace_notrace files, does\nnot always keep with them if another function ftrace_ops is registered\nto trace functions.\n\nThe reason is that function graph just happens to trace all functions\nthat the function tracer enables. When there was only one user of\nfunction tracing, the function graph tracer did not need to worry about\nbeing called by functions that it did not want to trace. But now that there\nare other users, this becomes a problem.\n\nFor example, one just needs to do the following:\n\n # cd /sys/kernel/debug/tracing\n # echo schedule \u003e set_ftrace_filter\n # echo function_graph \u003e current_tracer\n # cat trace\n[..]\n 0) | schedule() {\n ------------------------------------------\n 0) \u003cidle\u003e-0 \u003d\u003e rcu_pre-7\n ------------------------------------------\n\n 0) ! 2980.314 us | }\n 0) | schedule() {\n ------------------------------------------\n 0) rcu_pre-7 \u003d\u003e \u003cidle\u003e-0\n ------------------------------------------\n\n 0) + 20.701 us | }\n\n # echo 1 \u003e /proc/sys/kernel/stack_tracer_enabled\n # cat trace\n[..]\n 1) + 20.825 us | }\n 1) + 21.651 us | }\n 1) + 30.924 us | } /* SyS_ioctl */\n 1) | do_page_fault() {\n 1) | __do_page_fault() {\n 1) 0.274 us | down_read_trylock();\n 1) 0.098 us | find_vma();\n 1) | handle_mm_fault() {\n 1) | _raw_spin_lock() {\n 1) 0.102 us | preempt_count_add();\n 1) 0.097 us | do_raw_spin_lock();\n 1) 2.173 us | }\n 1) | do_wp_page() {\n 1) 0.079 us | vm_normal_page();\n 1) 0.086 us | reuse_swap_page();\n 1) 0.076 us | page_move_anon_rmap();\n 1) | unlock_page() {\n 1) 0.082 us | page_waitqueue();\n 1) 0.086 us | __wake_up_bit();\n 1) 1.801 us | }\n 1) 0.075 us | ptep_set_access_flags();\n 1) | _raw_spin_unlock() {\n 1) 0.098 us | do_raw_spin_unlock();\n 1) 0.105 us | preempt_count_sub();\n 1) 1.884 us | }\n 1) 9.149 us | }\n 1) + 13.083 us | }\n 1) 0.146 us | up_read();\n\nWhen the stack tracer was enabled, it enabled all functions to be traced, which\nnow the function graph tracer also traces. This is a side effect that should\nnot occur.\n\nTo fix this a test is added when the function tracing is changed, as well as when\nthe graph tracer is enabled, to see if anything other than the ftrace global_ops\nfunction tracer is enabled. If so, then the graph tracer calls a test trampoline\nthat will look at the function that is being traced and compare it with the\nfilters defined by the global_ops.\n\nAs an optimization, if there\u0027s no other function tracers registered, or if\nthe only registered function tracers also use the global ops, the function\ngraph infrastructure will call the registered function graph callback directly\nand not go through the test trampoline.\n\nFixes: d2d45c7a03a2 \"tracing: Have stack_tracer use a separate list of functions\"\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "2955866584c57545061dc38dc69de3461437aa9a", "tree": "bd8336f3d3d943f71733da5980c4729460652a34", "parents": [ "95bcd16ee7ce1cfb3fea853e38023f65d9d21c7c" ], "author": { "name": "Steven Rostedt", "email": "rostedt@goodmis.org", "time": "Tue Feb 11 14:49:37 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "ftrace: Fix synchronization location disabling and freeing ftrace_ops\n\ncommit a4c35ed241129dd142be4cadb1e5a474a56d5464 upstream.\n\nThe synchronization needed after ftrace_ops are unregistered must happen\nafter the callback is disabled from becing called by functions.\n\nThe current location happens after the function is being removed from the\ninternal lists, but not after the function callbacks were disabled, leaving\nthe functions susceptible of being called after their callbacks are freed.\n\nThis affects perf and any externel users of function tracing (LTTng and\nSystemTap).\n\nFixes: cdbe61bfe704 \"ftrace: Allow dynamically allocated function tracers\"\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "95bcd16ee7ce1cfb3fea853e38023f65d9d21c7c", "tree": "412a793ec08d91d0f2949ee315c4969e645d4613", "parents": [ "a7333f3d237f3007d14a2ee0456b96a4b33522d0" ], "author": { "name": "Steven Rostedt", "email": "rostedt@goodmis.org", "time": "Tue Feb 11 14:49:07 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "ftrace: Synchronize setting function_trace_op with ftrace_trace_function\n\ncommit 405e1d834807e51b2ebd3dea81cb51e53fb61504 upstream.\n\n[ Partial commit backported to 3.4. The ftrace_sync() code by this is\n required for other fixes that 3.4 needs. ]\n\nftrace_trace_function is a variable that holds what function will be called\ndirectly by the assembly code (mcount). If just a single function is\nregistered and it handles recursion itself, then the assembly will call that\nfunction directly without any helper function. It also passes in the\nftrace_op that was registered with the callback. The ftrace_op to send is\nstored in the function_trace_op variable.\n\nThe ftrace_trace_function and function_trace_op needs to be coordinated such\nthat the called callback wont be called with the wrong ftrace_op, otherwise\nbad things can happen if it expected a different op. Luckily, there\u0027s no\ncallback that doesn\u0027t use the helper functions that requires this. But\nthere soon will be and this needs to be fixed.\n\nUse a set_function_trace_op to store the ftrace_op to set the\nfunction_trace_op to when it is safe to do so (during the update function\nwithin the breakpoint or stop machine calls). Or if dynamic ftrace is not\nbeing used (static tracing) then we have to do a bit more synchronization\nwhen the ftrace_trace_function is set as that takes affect immediately\n(as oppose to dynamic ftrace doing it with the modification of the trampoline).\n\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "a7333f3d237f3007d14a2ee0456b96a4b33522d0", "tree": "1dc0d9ad4bd6986b35ea6566faa1e91bb471140f", "parents": [ "3fea8b0a9f978cce6d0685464d4e8acb9bbd1acc" ], "author": { "name": "Mikulas Patocka", "email": "mpatocka@redhat.com", "time": "Mon Jan 13 19:37:54 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "dm sysfs: fix a module unload race\n\ncommit 2995fa78e423d7193f3b57835f6c1c75006a0315 upstream.\n\nThis reverts commit be35f48610 (\"dm: wait until embedded kobject is\nreleased before destroying a device\") and provides an improved fix.\n\nThe kobject release code that calls the completion must be placed in a\nnon-module file, otherwise there is a module unload race (if the process\ncalling dm_kobject_release is preempted and the DM module unloaded after\nthe completion is triggered, but before dm_kobject_release returns).\n\nTo fix this race, this patch moves the completion code to dm-builtin.c\nwhich is always compiled directly into the kernel if BLK_DEV_DM is\nselected.\n\nThe patch introduces a new dm_kobject_holder structure, its purpose is\nto keep the completion and kobject in one place, so that it can be\naccessed from non-module code without the need to export the layout of\nstruct mapped_device to that code.\n\nSigned-off-by: Mikulas Patocka \u003cmpatocka@redhat.com\u003e\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3fea8b0a9f978cce6d0685464d4e8acb9bbd1acc", "tree": "cf9660ea94006074cb4bc8d499e50d3ef5db6128", "parents": [ "237597d8f73155bba781acf3f4f558f6ed08a8ee" ], "author": { "name": "Xishi Qiu", "email": "qiuxishi@huawei.com", "time": "Tue Jul 31 16:43:19 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "mm: setup pageblock_order before it\u0027s used by sparsemem\n\ncommit ca57df79d4f64e1a4886606af4289d40636189c5 upstream.\n\nOn architectures with CONFIG_HUGETLB_PAGE_SIZE_VARIABLE set, such as\nItanium, pageblock_order is a variable with default value of 0. It\u0027s set\nto the right value by set_pageblock_order() in function\nfree_area_init_core().\n\nBut pageblock_order may be used by sparse_init() before free_area_init_core()\nis called along path:\nsparse_init()\n -\u003esparse_early_usemaps_alloc_node()\n\t-\u003eusemap_size()\n\t -\u003eSECTION_BLOCKFLAGS_BITS\n\t\t-\u003e((1UL \u003c\u003c (PFN_SECTION_SHIFT - pageblock_order)) *\nNR_PAGEBLOCK_BITS)\n\nThe uninitialized pageblock_size will cause memory wasting because\nusemap_size() returns a much bigger value then it\u0027s really needed.\n\nFor example, on an Itanium platform,\nsparse_init() pageblock_order\u003d0 usemap_size\u003d24576\nfree_area_init_core() before pageblock_order\u003d0, usemap_size\u003d24576\nfree_area_init_core() after pageblock_order\u003d12, usemap_size\u003d8\n\nThat means 24K memory has been wasted for each section, so fix it by calling\nset_pageblock_order() from sparse_init().\n\nSigned-off-by: Xishi Qiu \u003cqiuxishi@huawei.com\u003e\nSigned-off-by: Jiang Liu \u003cliuj97@gmail.com\u003e\nCc: Tony Luck \u003ctony.luck@intel.com\u003e\nCc: Yinghai Lu \u003cyinghai@kernel.org\u003e\nCc: KAMEZAWA Hiroyuki \u003ckamezawa.hiroyu@jp.fujitsu.com\u003e\nCc: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nCc: KOSAKI Motohiro \u003ckosaki.motohiro@jp.fujitsu.com\u003e\nCc: David Rientjes \u003crientjes@google.com\u003e\nCc: Keping Chen \u003cchenkeping@huawei.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "237597d8f73155bba781acf3f4f558f6ed08a8ee", "tree": "35f736d485797cd4a8aef3b9e6d391dab049de1d", "parents": [ "dbdd2eb440291a1d71e54cfe0e6465402d81abc3" ], "author": { "name": "Andrew Morton", "email": "akpm@linux-foundation.org", "time": "Tue May 29 15:06:31 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "mm/page_alloc.c: remove pageblock_default_order()\n\ncommit 955c1cd7401565671b064e499115344ec8067dfd upstream.\n\nThis has always been broken: one version takes an unsigned int and the\nother version takes no arguments. This bug was hidden because one\nversion of set_pageblock_order() was a macro which doesn\u0027t evaluate its\nargument.\n\nSimplify it all and remove pageblock_default_order() altogether.\n\nReported-by: rajman mekaco \u003crajman.mekaco@gmail.com\u003e\nCc: Mel Gorman \u003cmel@csn.ul.ie\u003e\nCc: KAMEZAWA Hiroyuki \u003ckamezawa.hiroyu@jp.fujitsu.com\u003e\nCc: Tejun Heo \u003ctj@kernel.org\u003e\nCc: Minchan Kim \u003cminchan.kim@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dbdd2eb440291a1d71e54cfe0e6465402d81abc3", "tree": "3ab82f58da229cd93dc7781c265cb88e4ef3fad7", "parents": [ "4e0bc3f3cd9028d4a2bc2f21c6d371b2f671823b" ], "author": { "name": "Daniel Vetter", "email": "daniel.vetter@ffwll.ch", "time": "Sun Jul 01 17:09:42 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "drm/i915: kick any firmware framebuffers before claiming the gtt\n\ncommit 9f846a16d213523fbe6daea17e20df6b8ac5a1e5 upstream.\n\nEspecially vesafb likes to map everything as uc- (yikes), and if that\nmapping hangs around still while we try to map the gtt as wc the\nkernel will downgrade our request to uc-, resulting in abyssal\nperformance.\n\nUnfortunately we can\u0027t do this as early as readon does (i.e. as the\nfirst thing we do when initializing the hw) because our fb/mmio space\nregion moves around on a per-gen basis. So I\u0027ve had to move it below\nthe gtt initialization, but that seems to work, too. The important\nthing is that we do this before we set up the gtt wc mapping.\n\nNow an altogether different question is why people compile their\nkernels with vesafb enabled, but I guess making things just work isn\u0027t\nbad per se ...\n\nv2:\n- s/radeondrmfb/inteldrmfb/\n- fix up error handling\n\nv3: Kill #ifdef X86, this is Intel after all. Noticed by Ben Widawsky.\n\nv4: Jani Nikula complained about the pointless bool primary\ninitialization.\n\nv5: Don\u0027t oops if we can\u0027t allocate, noticed by Chris Wilson.\n\nv6: Resolve conflicts with agp rework and fixup whitespace.\n\nThis is commit e188719a2891f01b3100d in drm-next.\n\nBackport to 3.5 -fixes queue requested by Dave Airlie - due to grub\nusing vesa on fedora their initrd seems to load vesafb before loading\nthe real kms driver. So tons more people actually experience a\ndead-slow gpu. Hence also the Cc: stable.\n\nReported-and-tested-by: \"Kilarski, Bernard R\" \u003cbernard.r.kilarski@intel.com\u003e\nReviewed-by: Chris Wilson \u003cchris@chris-wilson.co.uk\u003e\nSigned-off-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n\n" }, { "commit": "4e0bc3f3cd9028d4a2bc2f21c6d371b2f671823b", "tree": "511d96edb6c4f61d805b0daea755929e569b0714", "parents": [ "5e23efd0c1d6c67761f859c141ba67bac80b81e0" ], "author": { "name": "Tao Ma", "email": "boyu.mt@taobao.com", "time": "Mon May 28 18:20:59 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "ext4: protect group inode free counting with group lock\n\ncommit 6f2e9f0e7d795214b9cf5a47724a273b705fd113 upstream.\n\nNow when we set the group inode free count, we don\u0027t have a proper\ngroup lock so that multiple threads may decrease the inode free\ncount at the same time. And e2fsck will complain something like:\n\nFree inodes count wrong for group #1 (1, counted\u003d0).\nFix? no\n\nFree inodes count wrong for group #2 (3, counted\u003d0).\nFix? no\n\nDirectories count wrong for group #2 (780, counted\u003d779).\nFix? no\n\nFree inodes count wrong for group #3 (2272, counted\u003d2273).\nFix? no\n\nSo this patch try to protect it with the ext4_lock_group.\n\nbtw, it is found by xfstests test case 269 and the volume is\nmkfsed with the parameter\n\"-O ^resize_inode,^uninit_bg,extent,meta_bg,flex_bg,ext_attr\"\nand I have run it 100 times and the error in e2fsck doesn\u0027t\nshow up again.\n\nSigned-off-by: Tao Ma \u003cboyu.mt@taobao.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nSigned-off-by: Benjamin LaHaise \u003cbcrl@kvack.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n\n" }, { "commit": "5e23efd0c1d6c67761f859c141ba67bac80b81e0", "tree": "1de16dc6a5c06a7fae118e8e3e2553645892a778", "parents": [ "36f0c45db55e2e840deefc286a33c2c7aef2f18e" ], "author": { "name": "Paul E. McKenney", "email": "paulmck@linux.vnet.ibm.com", "time": "Mon Oct 15 21:35:59 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "printk: Fix scheduling-while-atomic problem in console_cpu_notify()\n\ncommit 85eae82a0855d49852b87deac8653e4ebc8b291f upstream.\n\nThe console_cpu_notify() function runs with interrupts disabled in the\nCPU_DYING case. It therefore cannot block, for example, as will happen\nwhen it calls console_lock(). Therefore, remove the CPU_DYING leg of\nthe switch statement to avoid this problem.\n\nSigned-off-by: Paul E. McKenney \u003cpaulmck@linux.vnet.ibm.com\u003e\nReviewed-by: Srivatsa S. Bhat \u003csrivatsa.bhat@linux.vnet.ibm.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nCc: Guillaume Morin \u003cguillaume@morinfr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "36f0c45db55e2e840deefc286a33c2c7aef2f18e", "tree": "b60ecc8db08ea8bc6496dfb1684533668b738cd2", "parents": [ "d89985cb8cf57e6e444ee4ddf48cec39d0f28b1c" ], "author": { "name": "Peter Oberparleiter", "email": "oberpar@linux.vnet.ibm.com", "time": "Thu Feb 06 15:58:20 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "x86, hweight: Fix BUG when booting with CONFIG_GCOV_PROFILE_ALL\u003dy\n\ncommit 6583327c4dd55acbbf2a6f25e775b28b3abf9a42 upstream.\n\nCommit d61931d89b, \"x86: Add optimized popcnt variants\" introduced\ncompile flag -fcall-saved-rdi for lib/hweight.c. When combined with\noptions -fprofile-arcs and -O2, this flag causes gcc to generate\nbroken constructor code. As a result, a 64 bit x86 kernel compiled\nwith CONFIG_GCOV_PROFILE_ALL\u003dy prints message \"gcov: could not create\nfile\" and runs into sproadic BUGs during boot.\n\nThe gcc people indicate that these kinds of problems are endemic when\nusing ad hoc calling conventions. It is therefore best to treat any\nfile compiled with ad hoc calling conventions as an isolated\nenvironment and avoid things like profiling or coverage analysis,\nsince those subsystems assume a \"normal\" calling conventions.\n\nThis patch avoids the bug by excluding lib/hweight.o from coverage\nprofiling.\n\nReported-by: Meelis Roos \u003cmroos@linux.ee\u003e\nCc: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Peter Oberparleiter \u003coberpar@linux.vnet.ibm.com\u003e\nLink: http://lkml.kernel.org/r/52F3A30C.7050205@linux.vnet.ibm.com\nSigned-off-by: H. Peter Anvin \u003chpa@zytor.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d89985cb8cf57e6e444ee4ddf48cec39d0f28b1c", "tree": "3cbb095f153ad38b85a1cf4606e166a4a270c893", "parents": [ "4d4bed8141f7883dfbed44749653f769367b3e01" ], "author": { "name": "KOSAKI Motohiro", "email": "kosaki.motohiro@jp.fujitsu.com", "time": "Thu Feb 06 12:04:28 2014 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "mm: __set_page_dirty uses spin_lock_irqsave instead of spin_lock_irq\n\ncommit 227d53b397a32a7614667b3ecaf1d89902fb6c12 upstream.\n\nTo use spin_{un}lock_irq is dangerous if caller disabled interrupt.\nDuring aio buffer migration, we have a possibility to see the following\ncall stack.\n\naio_migratepage [disable interrupt]\n migrate_page_copy\n clear_page_dirty_for_io\n set_page_dirty\n __set_page_dirty_buffers\n __set_page_dirty\n spin_lock_irq\n\nThis mean, current aio migration is a deadlockable. spin_lock_irqsave\nis a safer alternative and we should use it.\n\nSigned-off-by: KOSAKI Motohiro \u003ckosaki.motohiro@jp.fujitsu.com\u003e\nReported-by: David Rientjes rientjes@google.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": "4d4bed8141f7883dfbed44749653f769367b3e01", "tree": "eb2c450ec6520d6dcaa5a4b6807c480cdfb463e8", "parents": [ "a0f916d429bcb240f8048c0d5f61d07c6d0c73ae" ], "author": { "name": "KOSAKI Motohiro", "email": "kosaki.motohiro@jp.fujitsu.com", "time": "Thu Feb 06 12:04:24 2014 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "mm: __set_page_dirty_nobuffers() uses spin_lock_irqsave() instead of spin_lock_irq()\n\ncommit a85d9df1ea1d23682a0ed1e100e6965006595d06 upstream.\n\nDuring aio stress test, we observed the following lockdep warning. This\nmean AIO+numa_balancing is currently deadlockable.\n\nThe problem is, aio_migratepage disable interrupt, but\n__set_page_dirty_nobuffers unintentionally enable it again.\n\nGenerally, all helper function should use spin_lock_irqsave() instead of\nspin_lock_irq() because they don\u0027t know caller at all.\n\n other info that might help us debug this:\n Possible unsafe locking scenario:\n\n CPU0\n ----\n lock(\u0026(\u0026ctx-\u003ecompletion_lock)-\u003erlock);\n \u003cInterrupt\u003e\n lock(\u0026(\u0026ctx-\u003ecompletion_lock)-\u003erlock);\n\n *** DEADLOCK ***\n\n dump_stack+0x19/0x1b\n print_usage_bug+0x1f7/0x208\n mark_lock+0x21d/0x2a0\n mark_held_locks+0xb9/0x140\n trace_hardirqs_on_caller+0x105/0x1d0\n trace_hardirqs_on+0xd/0x10\n _raw_spin_unlock_irq+0x2c/0x50\n __set_page_dirty_nobuffers+0x8c/0xf0\n migrate_page_copy+0x434/0x540\n aio_migratepage+0xb1/0x140\n move_to_new_page+0x7d/0x230\n migrate_pages+0x5e5/0x700\n migrate_misplaced_page+0xbc/0xf0\n do_numa_page+0x102/0x190\n handle_pte_fault+0x241/0x970\n handle_mm_fault+0x265/0x370\n __do_page_fault+0x172/0x5a0\n do_page_fault+0x1a/0x70\n page_fault+0x28/0x30\n\nSigned-off-by: KOSAKI Motohiro \u003ckosaki.motohiro@jp.fujitsu.com\u003e\nCc: Larry Woodman \u003clwoodman@redhat.com\u003e\nCc: Rik van Riel \u003criel@redhat.com\u003e\nCc: Johannes Weiner \u003cjweiner@redhat.com\u003e\nAcked-by: David Rientjes \u003crientjes@google.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": "a0f916d429bcb240f8048c0d5f61d07c6d0c73ae", "tree": "76d140745d5050c649ad216bfc58691d7a7eeacd", "parents": [ "a6d2ebcda7cb7467b3f5ca597710be25cc8ad76f" ], "author": { "name": "Stephen Smalley", "email": "sds@tycho.nsa.gov", "time": "Thu Jan 30 11:26:59 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 20 10:45:32 2014 -0800" }, "message": "SELinux: Fix kernel BUG on empty security contexts.\n\ncommit 2172fa709ab32ca60e86179dc67d0857be8e2c98 upstream.\n\nSetting an empty security context (length\u003d0) on a file will\nlead to incorrectly dereferencing the type and other fields\nof the security context structure, yielding a kernel BUG.\nAs a zero-length security context is never valid, just reject\nall such security contexts whether coming from userspace\nvia setxattr or coming from the filesystem upon a getxattr\nrequest by SELinux.\n\nSetting a security context value (empty or otherwise) unknown to\nSELinux in the first place is only possible for a root process\n(CAP_MAC_ADMIN), and, if running SELinux in enforcing mode, only\nif the corresponding SELinux mac_admin permission is also granted\nto the domain by policy. In Fedora policies, this is only allowed for\nspecific domains such as livecd for setting down security contexts\nthat are not defined in the build host policy.\n\nReproducer:\nsu\nsetenforce 0\ntouch foo\nsetfattr -n security.selinux foo\n\nCaveat:\nRelabeling or removing foo after doing the above may not be possible\nwithout booting with SELinux disabled. Any subsequent access to foo\nafter doing the above will also trigger the BUG.\n\nBUG output from Matthew Thode:\n[ 473.893141] ------------[ cut here ]------------\n[ 473.962110] kernel BUG at security/selinux/ss/services.c:654!\n[ 473.995314] invalid opcode: 0000 [#6] SMP\n[ 474.027196] Modules linked in:\n[ 474.058118] CPU: 0 PID: 8138 Comm: ls Tainted: G D I\n3.13.0-grsec #1\n[ 474.116637] Hardware name: Supermicro X8ST3/X8ST3, BIOS 2.0\n07/29/10\n[ 474.149768] task: ffff8805f50cd010 ti: ffff8805f50cd488 task.ti:\nffff8805f50cd488\n[ 474.183707] RIP: 0010:[\u003cffffffff814681c7\u003e] [\u003cffffffff814681c7\u003e]\ncontext_struct_compute_av+0xce/0x308\n[ 474.219954] RSP: 0018:ffff8805c0ac3c38 EFLAGS: 00010246\n[ 474.252253] RAX: 0000000000000000 RBX: ffff8805c0ac3d94 RCX:\n0000000000000100\n[ 474.287018] RDX: ffff8805e8aac000 RSI: 00000000ffffffff RDI:\nffff8805e8aaa000\n[ 474.321199] RBP: ffff8805c0ac3cb8 R08: 0000000000000010 R09:\n0000000000000006\n[ 474.357446] R10: 0000000000000000 R11: ffff8805c567a000 R12:\n0000000000000006\n[ 474.419191] R13: ffff8805c2b74e88 R14: 00000000000001da R15:\n0000000000000000\n[ 474.453816] FS: 00007f2e75220800(0000) GS:ffff88061fc00000(0000)\nknlGS:0000000000000000\n[ 474.489254] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 474.522215] CR2: 00007f2e74716090 CR3: 00000005c085e000 CR4:\n00000000000207f0\n[ 474.556058] Stack:\n[ 474.584325] ffff8805c0ac3c98 ffffffff811b549b ffff8805c0ac3c98\nffff8805f1190a40\n[ 474.618913] ffff8805a6202f08 ffff8805c2b74e88 00068800d0464990\nffff8805e8aac860\n[ 474.653955] ffff8805c0ac3cb8 000700068113833a ffff880606c75060\nffff8805c0ac3d94\n[ 474.690461] Call Trace:\n[ 474.723779] [\u003cffffffff811b549b\u003e] ? lookup_fast+0x1cd/0x22a\n[ 474.778049] [\u003cffffffff81468824\u003e] security_compute_av+0xf4/0x20b\n[ 474.811398] [\u003cffffffff8196f419\u003e] avc_compute_av+0x2a/0x179\n[ 474.843813] [\u003cffffffff8145727b\u003e] avc_has_perm+0x45/0xf4\n[ 474.875694] [\u003cffffffff81457d0e\u003e] inode_has_perm+0x2a/0x31\n[ 474.907370] [\u003cffffffff81457e76\u003e] selinux_inode_getattr+0x3c/0x3e\n[ 474.938726] [\u003cffffffff81455cf6\u003e] security_inode_getattr+0x1b/0x22\n[ 474.970036] [\u003cffffffff811b057d\u003e] vfs_getattr+0x19/0x2d\n[ 475.000618] [\u003cffffffff811b05e5\u003e] vfs_fstatat+0x54/0x91\n[ 475.030402] [\u003cffffffff811b063b\u003e] vfs_lstat+0x19/0x1b\n[ 475.061097] [\u003cffffffff811b077e\u003e] SyS_newlstat+0x15/0x30\n[ 475.094595] [\u003cffffffff8113c5c1\u003e] ? __audit_syscall_entry+0xa1/0xc3\n[ 475.148405] [\u003cffffffff8197791e\u003e] system_call_fastpath+0x16/0x1b\n[ 475.179201] Code: 00 48 85 c0 48 89 45 b8 75 02 0f 0b 48 8b 45 a0 48\n8b 3d 45 d0 b6 00 8b 40 08 89 c6 ff ce e8 d1 b0 06 00 48 85 c0 49 89 c7\n75 02 \u003c0f\u003e 0b 48 8b 45 b8 4c 8b 28 eb 1e 49 8d 7d 08 be 80 01 00 00 e8\n[ 475.255884] RIP [\u003cffffffff814681c7\u003e]\ncontext_struct_compute_av+0xce/0x308\n[ 475.296120] RSP \u003cffff8805c0ac3c38\u003e\n[ 475.328734] ---[ end trace f076482e9d754adc ]---\n\nReported-by: Matthew Thode \u003cmthode@mthode.org\u003e\nSigned-off-by: Stephen Smalley \u003csds@tycho.nsa.gov\u003e\nSigned-off-by: Paul Moore \u003cpmoore@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a6d2ebcda7cb7467b3f5ca597710be25cc8ad76f", "tree": "e68b2990d8ac5855b2d9aef8a215f6480fbcfd1b", "parents": [ "cd34de10471a5ddad397739fae33555d47e53769" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 13:00:25 2014 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 13:00:25 2014 -0800" }, "message": "Linux 3.4.80\n" }, { "commit": "cd34de10471a5ddad397739fae33555d47e53769", "tree": "99e2e27194d72d5767093568a956751b835fdf43", "parents": [ "cf85cc93b24891b7e57b1d9939742b5774570b19" ], "author": { "name": "Colin Cross", "email": "ccross@android.com", "time": "Mon Feb 10 13:16:29 2014 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:21 2014 -0800" }, "message": "3.4.y: timekeeping: fix 32-bit overflow in get_monotonic_boottime\n\nfixed upstream in v3.6 by ec145babe754f9ea1079034a108104b6001e001c\n\nget_monotonic_boottime adds three nanonsecond values stored\nin longs, followed by an s64. If the long values are all\nclose to 1e9 the first three additions can overflow and\nbecome negative when added to the s64. Cast the first\nvalue to s64 so that all additions are 64 bit.\n\nSigned-off-by: Colin Cross \u003cccross@android.com\u003e\n[jstultz: Fished this out of the AOSP commong.git tree. This was\nfixed upstream in v3.6 by ec145babe754f9ea1079034a108104b6001e001c]\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "cf85cc93b24891b7e57b1d9939742b5774570b19", "tree": "2a4719b1695dc561a13ea93b3083a60bca871e7b", "parents": [ "ab99a94d45f5db1ed178ed986f93b938bc018a87" ], "author": { "name": "John Stultz", "email": "john.stultz@linaro.org", "time": "Tue Dec 10 17:18:18 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:20 2014 -0800" }, "message": "timekeeping: Avoid possible deadlock from clock_was_set_delayed\n\ncommit 6fdda9a9c5db367130cf32df5d6618d08b89f46a upstream.\n\nAs part of normal operaions, the hrtimer subsystem frequently calls\ninto the timekeeping code, creating a locking order of\n hrtimer locks -\u003e timekeeping locks\n\nclock_was_set_delayed() was suppoed to allow us to avoid deadlocks\nbetween the timekeeping the hrtimer subsystem, so that we could\nnotify the hrtimer subsytem the time had changed while holding\nthe timekeeping locks. This was done by scheduling delayed work\nthat would run later once we were out of the timekeeing code.\n\nBut unfortunately the lock chains are complex enoguh that in\nscheduling delayed work, we end up eventually trying to grab\nan hrtimer lock.\n\nSasha Levin noticed this in testing when the new seqlock lockdep\nenablement triggered the following (somewhat abrieviated) message:\n\n[ 251.100221] \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n[ 251.100221] [ INFO: possible circular locking dependency detected ]\n[ 251.100221] 3.13.0-rc2-next-20131206-sasha-00005-g8be2375-dirty #4053 Not tainted\n[ 251.101967] -------------------------------------------------------\n[ 251.101967] kworker/10:1/4506 is trying to acquire lock:\n[ 251.101967] (timekeeper_seq){----..}, at: [\u003cffffffff81160e96\u003e] retrigger_next_event+0x56/0x70\n[ 251.101967]\n[ 251.101967] but task is already holding lock:\n[ 251.101967] (hrtimer_bases.lock#11){-.-...}, at: [\u003cffffffff81160e7c\u003e] retrigger_next_event+0x3c/0x70\n[ 251.101967]\n[ 251.101967] which lock already depends on the new lock.\n[ 251.101967]\n[ 251.101967]\n[ 251.101967] the existing dependency chain (in reverse order) is:\n[ 251.101967]\n-\u003e #5 (hrtimer_bases.lock#11){-.-...}:\n[snipped]\n-\u003e #4 (\u0026rt_b-\u003ert_runtime_lock){-.-...}:\n[snipped]\n-\u003e #3 (\u0026rq-\u003elock){-.-.-.}:\n[snipped]\n-\u003e #2 (\u0026p-\u003epi_lock){-.-.-.}:\n[snipped]\n-\u003e #1 (\u0026(\u0026pool-\u003elock)-\u003erlock){-.-...}:\n[ 251.101967] [\u003cffffffff81194803\u003e] validate_chain+0x6c3/0x7b0\n[ 251.101967] [\u003cffffffff81194d9d\u003e] __lock_acquire+0x4ad/0x580\n[ 251.101967] [\u003cffffffff81194ff2\u003e] lock_acquire+0x182/0x1d0\n[ 251.101967] [\u003cffffffff84398500\u003e] _raw_spin_lock+0x40/0x80\n[ 251.101967] [\u003cffffffff81153e69\u003e] __queue_work+0x1a9/0x3f0\n[ 251.101967] [\u003cffffffff81154168\u003e] queue_work_on+0x98/0x120\n[ 251.101967] [\u003cffffffff81161351\u003e] clock_was_set_delayed+0x21/0x30\n[ 251.101967] [\u003cffffffff811c4bd1\u003e] do_adjtimex+0x111/0x160\n[ 251.101967] [\u003cffffffff811e2711\u003e] compat_sys_adjtimex+0x41/0x70\n[ 251.101967] [\u003cffffffff843a4b49\u003e] ia32_sysret+0x0/0x5\n[ 251.101967]\n-\u003e #0 (timekeeper_seq){----..}:\n[snipped]\n[ 251.101967] other info that might help us debug this:\n[ 251.101967]\n[ 251.101967] Chain exists of:\n timekeeper_seq --\u003e \u0026rt_b-\u003ert_runtime_lock --\u003e hrtimer_bases.lock#11\n\n[ 251.101967] Possible unsafe locking scenario:\n[ 251.101967]\n[ 251.101967] CPU0 CPU1\n[ 251.101967] ---- ----\n[ 251.101967] lock(hrtimer_bases.lock#11);\n[ 251.101967] lock(\u0026rt_b-\u003ert_runtime_lock);\n[ 251.101967] lock(hrtimer_bases.lock#11);\n[ 251.101967] lock(timekeeper_seq);\n[ 251.101967]\n[ 251.101967] *** DEADLOCK ***\n[ 251.101967]\n[ 251.101967] 3 locks held by kworker/10:1/4506:\n[ 251.101967] #0: (events){.+.+.+}, at: [\u003cffffffff81154960\u003e] process_one_work+0x200/0x530\n[ 251.101967] #1: (hrtimer_work){+.+...}, at: [\u003cffffffff81154960\u003e] process_one_work+0x200/0x530\n[ 251.101967] #2: (hrtimer_bases.lock#11){-.-...}, at: [\u003cffffffff81160e7c\u003e] retrigger_next_event+0x3c/0x70\n[ 251.101967]\n[ 251.101967] stack backtrace:\n[ 251.101967] CPU: 10 PID: 4506 Comm: kworker/10:1 Not tainted 3.13.0-rc2-next-20131206-sasha-00005-g8be2375-dirty #4053\n[ 251.101967] Workqueue: events clock_was_set_work\n\nSo the best solution is to avoid calling clock_was_set_delayed() while\nholding the timekeeping lock, and instead using a flag variable to\ndecide if we should call clock_was_set() once we\u0027ve released the locks.\n\nThis works for the case here, where the do_adjtimex() was the deadlock\ntrigger point. Unfortuantely, in update_wall_time() we still hold\nthe jiffies lock, which would deadlock with the ipi triggered by\nclock_was_set(), preventing us from calling it even after we drop the\ntimekeeping lock. So instead call clock_was_set_delayed() at that point.\n\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Prarit Bhargava \u003cprarit@redhat.com\u003e\nCc: Richard Cochran \u003crichardcochran@gmail.com\u003e\nCc: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Sasha Levin \u003csasha.levin@oracle.com\u003e\nReported-by: Sasha Levin \u003csasha.levin@oracle.com\u003e\nTested-by: Sasha Levin \u003csasha.levin@oracle.com\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n\n" }, { "commit": "ab99a94d45f5db1ed178ed986f93b938bc018a87", "tree": "3878a550498c249d709c3880f3e7efd04ba4cd48", "parents": [ "dbf3239455b155c3e72deacda93ef3a041e190c9" ], "author": { "name": "Borislav Petkov", "email": "bp@alien8.de", "time": "Sat Jul 20 19:00:23 2013 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:20 2014 -0800" }, "message": "rtc-cmos: Add an alarm disable quirk\n\ncommit d5a1c7e3fc38d9c7d629e1e47f32f863acbdec3d upstream.\n\n41c7f7424259f (\"rtc: Disable the alarm in the hardware (v2)\") added the\nfunctionality to disable the RTC wake alarm when shutting down the box.\n\nHowever, there are at least two b0rked BIOSes we know about:\n\nhttps://bugzilla.novell.com/show_bug.cgi?id\u003d812592\nhttps://bugzilla.novell.com/show_bug.cgi?id\u003d805740\n\nwhere, when wakeup alarm is enabled in the BIOS, the machine reboots\nautomatically right after shutdown, regardless of what wakeup time is\nprogrammed.\n\nBisecting the issue lead to this patch so disable its functionality with\na DMI quirk only for those boxes.\n\nCc: Brecht Machiels \u003cbrecht@mos6581.org\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: Rabin Vincent \u003crabin.vincent@stericsson.com\u003e\nSigned-off-by: Borislav Petkov \u003cbp@suse.de\u003e\n[jstultz: Changed variable name for clarity, added extra dmi entry]\nTested-by: Brecht Machiels \u003cbrecht@mos6581.org\u003e\nTested-by: Borislav Petkov \u003cbp@suse.de\u003e\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dbf3239455b155c3e72deacda93ef3a041e190c9", "tree": "c7a8cfce370fa0de4cdeaab1b75925061fe9ccf1", "parents": [ "f61eb9ceb26cee3fdbb8c7a4920f171f7661fb4f" ], "author": { "name": "Ying Xue", "email": "ying.xue@windriver.com", "time": "Tue Jul 17 15:03:43 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:19 2014 -0800" }, "message": "sched/rt: Avoid updating RT entry timeout twice within one tick period\n\ncommit 57d2aa00dcec67afa52478730f2b524521af14fb upstream.\n\nThe issue below was found in 2.6.34-rt rather than mainline rt\nkernel, but the issue still exists upstream as well.\n\nSo please let me describe how it was noticed on 2.6.34-rt:\n\nOn this version, each softirq has its own thread, it means there\nis at least one RT FIFO task per cpu. The priority of these\ntasks is set to 49 by default. If user launches an RT FIFO task\nwith priority lower than 49 of softirq RT tasks, it\u0027s possible\nthere are two RT FIFO tasks enqueued one cpu runqueue at one\nmoment. By current strategy of balancing RT tasks, when it comes\nto RT tasks, we really need to put them off to a CPU that they\ncan run on as soon as possible. Even if it means a bit of cache\nline flushing, we want RT tasks to be run with the least latency.\n\nWhen the user RT FIFO task which just launched before is\nrunning, the sched timer tick of the current cpu happens. In this\ntick period, the timeout value of the user RT task will be\nupdated once. Subsequently, we try to wake up one softirq RT\ntask on its local cpu. As the priority of current user RT task\nis lower than the softirq RT task, the current task will be\npreempted by the higher priority softirq RT task. Before\npreemption, we check to see if current can readily move to a\ndifferent cpu. If so, we will reschedule to allow the RT push logic\nto try to move current somewhere else. Whenever the woken\nsoftirq RT task runs, it first tries to migrate the user FIFO RT\ntask over to a cpu that is running a task of lesser priority. If\nmigration is done, it will send a reschedule request to the found\ncpu by IPI interrupt. Once the target cpu responds the IPI\ninterrupt, it will pick the migrated user RT task to preempt its\ncurrent task. When the user RT task is running on the new cpu,\nthe sched timer tick of the cpu fires. So it will tick the user\nRT task again. This also means the RT task timeout value will be\nupdated again. As the migration may be done in one tick period,\nit means the user RT task timeout value will be updated twice\nwithin one tick.\n\nIf we set a limit on the amount of cpu time for the user RT task\nby setrlimit(RLIMIT_RTTIME), the SIGXCPU signal should be posted\nupon reaching the soft limit.\n\nBut exactly when the SIGXCPU signal should be sent depends on the\nRT task timeout value. In fact the timeout mechanism of sending\nthe SIGXCPU signal assumes the RT task timeout is increased once\nevery tick.\n\nHowever, currently the timeout value may be added twice per\ntick. So it results in the SIGXCPU signal being sent earlier\nthan expected.\n\nTo solve this issue, we prevent the timeout value from increasing\ntwice within one tick time by remembering the jiffies value of\nlast updating the timeout. As long as the RT task\u0027s jiffies is\ndifferent with the global jiffies value, we allow its timeout to\nbe updated.\n\nSigned-off-by: Ying Xue \u003cying.xue@windriver.com\u003e\nSigned-off-by: Fan Du \u003cfan.du@windriver.com\u003e\nReviewed-by: Yong Zhang \u003cyong.zhang0@gmail.com\u003e\nAcked-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\nCc: \u003cpeterz@infradead.org\u003e\nLink: http://lkml.kernel.org/r/1342508623-2887-1-git-send-email-ying.xue@windriver.com\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\n[ lizf: backported to 3.4: adjust context ]\nSigned-off-by: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f61eb9ceb26cee3fdbb8c7a4920f171f7661fb4f", "tree": "7ef1b69d19fdc57f57ce58dc78988ce4a653aa8e", "parents": [ "1e5c13ec422f665432bfc9f7c5fc1f9fd614afd3" ], "author": { "name": "Peter Boonstoppel", "email": "pboonstoppel@nvidia.com", "time": "Thu Aug 09 15:34:47 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:19 2014 -0800" }, "message": "sched: Unthrottle rt runqueues in __disable_runtime()\n\ncommit a4c96ae319b8047f62dedbe1eac79e321c185749 upstream.\n\nmigrate_tasks() uses _pick_next_task_rt() to get tasks from the\nreal-time runqueues to be migrated. When rt_rq is throttled\n_pick_next_task_rt() won\u0027t return anything, in which case\nmigrate_tasks() can\u0027t move all threads over and gets stuck in an\ninfinite loop.\n\nInstead unthrottle rt runqueues before migrating tasks.\n\nAdditionally: move unthrottle_offline_cfs_rqs() to rq_offline_fair()\n\nSigned-off-by: Peter Boonstoppel \u003cpboonstoppel@nvidia.com\u003e\nSigned-off-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nCc: Paul Turner \u003cpjt@google.com\u003e\nLink: http://lkml.kernel.org/r/5FBF8E85CA34454794F0F7ECBA79798F379D3648B7@HQMAIL04.nvidia.com\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\n[ lizf: backported to 3.4: adjust context ]\nSigned-off-by: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1e5c13ec422f665432bfc9f7c5fc1f9fd614afd3", "tree": "8588210c14890e4a797a9ea5402d6fa42ba3ceb6", "parents": [ "21b53baf40aecb134593ec74eb787f16c569cfc5" ], "author": { "name": "Mike Galbraith", "email": "efault@gmx.de", "time": "Tue Aug 07 10:02:38 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:18 2014 -0800" }, "message": "sched,rt: fix isolated CPUs leaving root_task_group indefinitely throttled\n\ncommit e221d028bb08b47e624c5f0a31732c642db9d19a upstream.\n\nRoot task group bandwidth replenishment must service all CPUs, regardless of\nwhere the timer was last started, and regardless of the isolation mechanism,\nlest \u0027Quoth the Raven, \"Nevermore\"\u0027 become rt scheduling policy.\n\nSigned-off-by: Mike Galbraith \u003cefault@gmx.de\u003e\nSigned-off-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nLink: http://lkml.kernel.org/r/1344326558.6968.25.camel@marge.simpson.net\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "21b53baf40aecb134593ec74eb787f16c569cfc5", "tree": "c4c8bb46216c1baf4fe84d8787f5f6b7e01fe2f9", "parents": [ "d5c20298b6d817b069c69d94df9cd8ed76b2ff15" ], "author": { "name": "Colin Cross", "email": "ccross@android.com", "time": "Wed May 16 21:34:23 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:18 2014 -0800" }, "message": "sched/rt: Fix SCHED_RR across cgroups\n\ncommit 454c79999f7eaedcdf4c15c449e43902980cbdf5 upstream.\n\ntask_tick_rt() has an optimization to only reschedule SCHED_RR tasks\nif they were the only element on their rq. However, with cgroups\na SCHED_RR task could be the only element on its per-cgroup rq but\nstill be competing with other SCHED_RR tasks in its parent\u0027s\ncgroup. In this case, the SCHED_RR task in the child cgroup would\nnever yield at the end of its timeslice. If the child cgroup\nrt_runtime_us was the same as the parent cgroup rt_runtime_us,\nthe task in the parent cgroup would starve completely.\n\nModify task_tick_rt() to check that the task is the only task on its\nrq, and that the each of the scheduling entities of its ancestors\nis also the only entity on its rq.\n\nSigned-off-by: Colin Cross \u003cccross@android.com\u003e\nSigned-off-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nLink: http://lkml.kernel.org/r/1337229266-15798-1-git-send-email-ccross@android.com\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d5c20298b6d817b069c69d94df9cd8ed76b2ff15", "tree": "382888a2b0d864b98998fd9a50419b153da6bbaf", "parents": [ "d7c16d1e0a33ea79d9dc33e3f13f41b4f5caa756" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Sat May 18 02:38:52 2013 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:18 2014 -0800" }, "message": "hpfs: deadlock and race in directory lseek()\n\ncommit 31abdab9c11bb1694ecd1476a7edbe8e964d94ac upstream.\n\nFor one thing, there\u0027s an ABBA deadlock on hpfs fs-wide lock and i_mutex\nin hpfs_dir_lseek() - there\u0027s a lot of methods that grab the former with\nthe caller already holding the latter, so it must take i_mutex first.\n\nFor another, locking the damn thing, carefully validating the offset,\nthen dropping locks and assigning the offset is obviously racy.\n\nMoreover, we _must_ do hpfs_add_pos(), or the machinery in dnode.c\nwon\u0027t modify the sucker on B-tree surgeries.\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Mikulas Patocka \u003cmikulas@artax.karlin.mff.cuni.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d7c16d1e0a33ea79d9dc33e3f13f41b4f5caa756", "tree": "94fe2dad06b41712c6f25992271551d474cf1ba8", "parents": [ "27fb12b9e08a7f5bb8d8faa65002b9f76ee285b6" ], "author": { "name": "Yijing Wang", "email": "wangyijing@huawei.com", "time": "Tue Jan 15 11:12:16 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:17 2014 -0800" }, "message": "PCI: Enable ARI if dev and upstream bridge support it; disable otherwise\n\ncommit b0cc6020e1cc62f1253215f189611b34be4a83c7 upstream.\n\nCurrently, we enable ARI in a device\u0027s upstream bridge if the bridge and\nthe device support it. But we never disable ARI, even if the device is\nremoved and replaced with a device that doesn\u0027t support ARI.\n\nThis means that if we hot-remove an ARI device and replace it with a\nnon-ARI multi-function device, we find only function 0 of the new device\nbecause the upstream bridge still has ARI enabled, and next_ari_fn()\nonly returns function 0 for the new non-ARI device.\n\nThis patch disables ARI in the upstream bridge if the device doesn\u0027t\nsupport ARI. See the PCIe spec, r3.0, sec 6.13.\n\n[bhelgaas: changelog, function comment]\n[yijing: replace PCIe Cap accessor with legacy PCI accessor]\nSigned-off-by: Yijing Wang \u003cwangyijing@huawei.com\u003e\nSigned-off-by: Jiang Liu \u003cjiang.liu@huawei.com\u003e\nSigned-off-by: Bjorn Helgaas \u003cbhelgaas@google.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n\n" }, { "commit": "27fb12b9e08a7f5bb8d8faa65002b9f76ee285b6", "tree": "6f4a6a51c32529a89a72287627587c68381a4992", "parents": [ "00a67d1c296f19848ffa299fcedaac531a4717f4" ], "author": { "name": "Alex Deucher", "email": "alexander.deucher@amd.com", "time": "Mon Jan 27 18:29:35 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:17 2014 -0800" }, "message": "drm/radeon/DCE4+: clear bios scratch dpms bit (v2)\n\ncommit 6802d4bad83f50081b2788698570218aaff8d10e upstream.\n\nThe BlankCrtc table in some DCE8 boards has some\nlogic shortcuts for the vbios when this bit is set.\nClear it for driver use.\n\nv2: fix typo\n\nBug:\nhttps://bugs.freedesktop.org/show_bug.cgi?id\u003d73420\n\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "00a67d1c296f19848ffa299fcedaac531a4717f4", "tree": "7730ce0365dae4a1337efdd3c9584a0f81dcec6f", "parents": [ "790d84498040cb890bd93a933d62f69bcaf85ce8" ], "author": { "name": "Alex Deucher", "email": "alexander.deucher@amd.com", "time": "Thu Jan 16 18:11:47 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:16 2014 -0800" }, "message": "drm/radeon: set the full cache bit for fences on r7xx+\n\ncommit d45b964a22cad962d3ede1eba8d24f5cee7b2a92 upstream.\n\nNeeded to properly flush the read caches for fences.\n\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "790d84498040cb890bd93a933d62f69bcaf85ce8", "tree": "60c716bec39e906d373ee79e6d0de6dc77f339f6", "parents": [ "e4496194b5e849e89065d675ffec7214238a6a19" ], "author": { "name": "Marek Olšák", "email": "marek.olsak@amd.com", "time": "Wed Jan 08 18:16:26 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:16 2014 -0800" }, "message": "drm/radeon: skip colorbuffer checking if COLOR_INFO.FORMAT is set to INVALID\n\ncommit 56492e0fac2dbaf7735ffd66b206a90624917789 upstream.\n\nThis fixes a bug which was causing rejections of valid GPU commands\nfrom userspace.\n\nSigned-off-by: Marek Olšák \u003cmarek.olsak@amd.com\u003e\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e4496194b5e849e89065d675ffec7214238a6a19", "tree": "962edfc9cb90a531be96d95b6b0fdf71eb8272f3", "parents": [ "aea570ea6bc6532cc33a2fb98d3a7348781f3b76" ], "author": { "name": "Michel Dänzer", "email": "michel.daenzer@amd.com", "time": "Wed Jan 08 11:40:20 2014 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:15 2014 -0800" }, "message": "radeon/pm: Guard access to rdev-\u003epm.power_state array\n\ncommit 370169516e736edad3b3c5aa49858058f8b55195 upstream.\n\nIt\u0027s never allocated on systems without an ATOMBIOS or COMBIOS ROM.\n\nShould fix an oops I encountered while resetting the GPU after a lockup\non my PowerBook with an RV350.\n\nSigned-off-by: Michel Dänzer \u003cmichel.daenzer@amd.com\u003e\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "aea570ea6bc6532cc33a2fb98d3a7348781f3b76", "tree": "6b6bbe88dcdaf4eada66b8cf18e5db5b2ade7ad2", "parents": [ "11690e1491de3c35b09bff55336c14aacbdf1627" ], "author": { "name": "Alex Deucher", "email": "alexander.deucher@amd.com", "time": "Tue Jan 07 10:05:02 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:15 2014 -0800" }, "message": "drm/radeon: warn users when hw_i2c is enabled (v2)\n\ncommit d195178297de9a91246519dbfa98952b70f9a9b6 upstream.\n\nThe hw i2c engines are disabled by default as the\ncurrent implementation is still experimental. Print\na warning when users enable it so that it\u0027s obvious\nwhen the option is enabled.\n\nv2: check for non-0 rather than 1\n\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nReviewed-by: Christian König \u003cchristian.koenig@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "11690e1491de3c35b09bff55336c14aacbdf1627", "tree": "55d4879bb25d9455b1140b5c90d82caa3096e989", "parents": [ "39bbeb69ace5742f3cbad2ae77c27bc2fa3c2c0f" ], "author": { "name": "Joe Thornber", "email": "ejt@redhat.com", "time": "Tue Jan 07 15:47:59 2014 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:14 2014 -0800" }, "message": "dm space map common: make sure new space is used during extend\n\ncommit 12c91a5c2d2a8e8cc40a9552313e1e7b0a2d9ee3 upstream.\n\nWhen extending a low level space map we should update nr_blocks at\nthe start so the new space is used for the index entries.\n\nOtherwise extend can fail, e.g.: sm_metadata_extend call sequence\nthat fails:\n -\u003e sm_ll_extend\n -\u003e dm_tm_new_block -\u003e dm_sm_new_block -\u003e sm_bootstrap_new_block\n \u003d\u003e returns -ENOSPC because smm-\u003ebegin \u003d\u003d smm-\u003ell.nr_blocks\n\nSigned-off-by: Joe Thornber \u003cejt@redhat.com\u003e\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "39bbeb69ace5742f3cbad2ae77c27bc2fa3c2c0f", "tree": "229e81113da919b062f39ef5f9de6668fd697f9a", "parents": [ "b0c0d5a3ee2a62e5cbeef3e2089bbd624e6869fa" ], "author": { "name": "Mikulas Patocka", "email": "mpatocka@redhat.com", "time": "Mon Jan 06 23:01:22 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:14 2014 -0800" }, "message": "dm: wait until embedded kobject is released before destroying a device\n\ncommit be35f486108227e10fe5d96fd42fb2b344c59983 upstream.\n\nThere may be other parts of the kernel holding a reference on the dm\nkobject. We must wait until all references are dropped before\ndeallocating the mapped_device structure.\n\nThe dm_kobject_release method signals that all references are dropped\nvia completion. But dm_kobject_release doesn\u0027t free the kobject (which\nis embedded in the mapped_device structure).\n\nThis is the sequence of operations:\n* when destroying a DM device, call kobject_put from dm_sysfs_exit\n* wait until all users stop using the kobject, when it happens the\n release method is called\n* the release method signals the completion and should return without\n delay\n* the dm device removal code that waits on the completion continues\n* the dm device removal code drops the dm_mod reference the device had\n* the dm device removal code frees the mapped_device structure that\n contains the kobject\n\nUsing kobject this way should avoid the module unload race that was\nmentioned at the beginning of this thread:\nhttps://lkml.org/lkml/2014/1/4/83\n\nSigned-off-by: Mikulas Patocka \u003cmpatocka@redhat.com\u003e\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b0c0d5a3ee2a62e5cbeef3e2089bbd624e6869fa", "tree": "21f195be25e828d2b05a01d99fe507536925c8fe", "parents": [ "b5f0608e9f3313adfc2753fc423c8126993d76ff" ], "author": { "name": "Weston Andros Adamson", "email": "dros@netapp.com", "time": "Tue Dec 17 12:16:11 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:13 2014 -0800" }, "message": "sunrpc: Fix infinite loop in RPC state machine\n\ncommit 6ff33b7dd0228b7d7ed44791bbbc98b03fd15d9d upstream.\n\nWhen a task enters call_refreshresult with status 0 from call_refresh and\n!rpcauth_uptodatecred(task) it enters call_refresh again with no rate-limiting\nor max number of retries.\n\nInstead of trying forever, make use of the retry path that other errors use.\n\nThis only seems to be possible when the crrefresh callback is gss_refresh_null,\nwhich only happens when destroying the context.\n\nTo reproduce:\n\n1) mount with sec\u003dkrb5 (or sec\u003dsys with krb5 negotiated for non FSID specific\n operations).\n\n2) reboot - the client will be stuck and will need to be hard rebooted\n\nBUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:2:46]\nModules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache ppdev crc32c_intel aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd serio_raw i2c_piix4 i2c_core e1000 parport_pc parport shpchp nfsd auth_rpcgss oid_registry exportfs nfs_acl lockd sunrpc autofs4 mptspi scsi_transport_spi mptscsih mptbase ata_generic floppy\nirq event stamp: 195724\nhardirqs last enabled at (195723): [\u003cffffffff814a925c\u003e] restore_args+0x0/0x30\nhardirqs last disabled at (195724): [\u003cffffffff814b0a6a\u003e] apic_timer_interrupt+0x6a/0x80\nsoftirqs last enabled at (195722): [\u003cffffffff8103f583\u003e] __do_softirq+0x1df/0x276\nsoftirqs last disabled at (195717): [\u003cffffffff8103f852\u003e] irq_exit+0x53/0x9a\nCPU: 0 PID: 46 Comm: kworker/0:2 Not tainted 3.13.0-rc3-branch-dros_testing+ #4\nHardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/31/2013\nWorkqueue: rpciod rpc_async_schedule [sunrpc]\ntask: ffff8800799c4260 ti: ffff880079002000 task.ti: ffff880079002000\nRIP: 0010:[\u003cffffffffa0064fd4\u003e] [\u003cffffffffa0064fd4\u003e] __rpc_execute+0x8a/0x362 [sunrpc]\nRSP: 0018:ffff880079003d18 EFLAGS: 00000246\nRAX: 0000000000000005 RBX: 0000000000000007 RCX: 0000000000000007\nRDX: 0000000000000007 RSI: ffff88007aecbae8 RDI: ffff8800783d8900\nRBP: ffff880079003d78 R08: ffff88006e30e9f8 R09: ffffffffa005a3d7\nR10: ffff88006e30e7b0 R11: ffff8800783d8900 R12: ffffffffa006675e\nR13: ffff880079003ce8 R14: ffff88006e30e7b0 R15: ffff8800783d8900\nFS: 0000000000000000(0000) GS:ffff88007f200000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f3072333000 CR3: 0000000001a0b000 CR4: 00000000001407f0\nStack:\n ffff880079003d98 0000000000000246 0000000000000000 ffff88007a9a4830\n ffff880000000000 ffffffff81073f47 ffff88007f212b00 ffff8800799c4260\n ffff8800783d8988 ffff88007f212b00 ffffe8ffff604800 0000000000000000\nCall Trace:\n [\u003cffffffff81073f47\u003e] ? trace_hardirqs_on_caller+0x145/0x1a1\n [\u003cffffffffa00652d3\u003e] rpc_async_schedule+0x27/0x32 [sunrpc]\n [\u003cffffffff81052974\u003e] process_one_work+0x211/0x3a5\n [\u003cffffffff810528d5\u003e] ? process_one_work+0x172/0x3a5\n [\u003cffffffff81052eeb\u003e] worker_thread+0x134/0x202\n [\u003cffffffff81052db7\u003e] ? rescuer_thread+0x280/0x280\n [\u003cffffffff81052db7\u003e] ? rescuer_thread+0x280/0x280\n [\u003cffffffff810584a0\u003e] kthread+0xc9/0xd1\n [\u003cffffffff810583d7\u003e] ? __kthread_parkme+0x61/0x61\n [\u003cffffffff814afd6c\u003e] ret_from_fork+0x7c/0xb0\n [\u003cffffffff810583d7\u003e] ? __kthread_parkme+0x61/0x61\nCode: e8 87 63 fd e0 c6 05 10 dd 01 00 01 48 8b 43 70 4c 8d 6b 70 45 31 e4 a8 02 0f 85 d5 02 00 00 4c 8b 7b 48 48 c7 43 48 00 00 00 00 \u003c4c\u003e 8b 4b 50 4d 85 ff 75 0c 4d 85 c9 4d 89 cf 0f 84 32 01 00 00\n\nAnd the output of \"rpcdebug -m rpc -s all\":\n\nRPC: 61 call_refresh (status 0)\nRPC: 61 call_refresh (status 0)\nRPC: 61 refreshing RPCSEC_GSS cred ffff88007a413cf0\nRPC: 61 refreshing RPCSEC_GSS cred ffff88007a413cf0\nRPC: 61 call_refreshresult (status 0)\nRPC: 61 refreshing RPCSEC_GSS cred ffff88007a413cf0\nRPC: 61 call_refreshresult (status 0)\nRPC: 61 refreshing RPCSEC_GSS cred ffff88007a413cf0\nRPC: 61 call_refresh (status 0)\nRPC: 61 call_refreshresult (status 0)\nRPC: 61 call_refresh (status 0)\nRPC: 61 call_refresh (status 0)\nRPC: 61 refreshing RPCSEC_GSS cred ffff88007a413cf0\nRPC: 61 call_refreshresult (status 0)\nRPC: 61 call_refresh (status 0)\nRPC: 61 refreshing RPCSEC_GSS cred ffff88007a413cf0\nRPC: 61 call_refresh (status 0)\nRPC: 61 refreshing RPCSEC_GSS cred ffff88007a413cf0\nRPC: 61 refreshing RPCSEC_GSS cred ffff88007a413cf0\nRPC: 61 call_refreshresult (status 0)\nRPC: 61 call_refresh (status 0)\nRPC: 61 call_refresh (status 0)\nRPC: 61 call_refresh (status 0)\nRPC: 61 call_refresh (status 0)\nRPC: 61 call_refreshresult (status 0)\nRPC: 61 refreshing RPCSEC_GSS cred ffff88007a413cf0\n\nSigned-off-by: Weston Andros Adamson \u003cdros@netapp.com\u003e\nSigned-off-by: Trond Myklebust \u003ctrond.myklebust@primarydata.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b5f0608e9f3313adfc2753fc423c8126993d76ff", "tree": "659d5a08c6831cbdbd86e091ce08f7985efa600b", "parents": [ "3c16dfe205528505f3ea4b9586f794cb1e3278e2" ], "author": { "name": "Weston Andros Adamson", "email": "dros@primarydata.com", "time": "Mon Jan 13 16:54:45 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:13 2014 -0800" }, "message": "nfs4.1: properly handle ENOTSUP in SECINFO_NO_NAME\n\ncommit 78b19bae0813bd6f921ca58490196abd101297bd upstream.\n\nDon\u0027t check for -NFS4ERR_NOTSUPP, it\u0027s already been mapped to -ENOTSUPP\nby nfs4_stat_to_errno.\n\nThis allows the client to mount v4.1 servers that don\u0027t support\nSECINFO_NO_NAME by falling back to the \"guess and check\" method of\nnfs4_find_root_sec.\n\nSigned-off-by: Weston Andros Adamson \u003cdros@primarydata.com\u003e\nSigned-off-by: Trond Myklebust \u003ctrond.myklebust@primarydata.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3c16dfe205528505f3ea4b9586f794cb1e3278e2", "tree": "131b09cb49509e463c783ab8c4d66a0c0b49f8d3", "parents": [ "8b939c238fdafd3b48e08547b929b1ab1ab37cf4" ], "author": { "name": "Trond Myklebust", "email": "Trond.Myklebust@netapp.com", "time": "Wed Dec 04 17:39:23 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:12 2014 -0800" }, "message": "NFSv4: OPEN must handle the NFS4ERR_IO return code correctly\n\ncommit c7848f69ec4a8c03732cde5c949bd2aa711a9f4b upstream.\n\ndecode_op_hdr() cannot distinguish between an XDR decoding error and\nthe perfectly valid errorcode NFS4ERR_IO. This is normally not a\nproblem, but for the particular case of OPEN, we need to be able\nto increment the NFSv4 open sequence id when the server returns\na valid response.\n\nReported-by: J Bruce Fields \u003cbfields@fieldses.org\u003e\nLink: http://lkml.kernel.org/r/20131204210356.GA19452@fieldses.org\nSigned-off-by: Trond Myklebust \u003ctrond.myklebust@primarydata.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8b939c238fdafd3b48e08547b929b1ab1ab37cf4", "tree": "6ebfcb9ffa95d0fd6e84025a466fc65334027437", "parents": [ "2332020b306a8da315f28cdac1cf19e6d9d470fd" ], "author": { "name": "Daniel Santos", "email": "daniel.santos@pobox.com", "time": "Sun Jan 05 17:39:26 2014 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:12 2014 -0800" }, "message": "spidev: fix hang when transfer_one_message fails\n\ncommit e120cc0dcf2880a4c5c0a6cb27b655600a1cfa1d upstream.\n\nThis corrects a problem in spi_pump_messages() that leads to an spi\nmessage hanging forever when a call to transfer_one_message() fails.\nThis failure occurs in my MCP2210 driver when the cs_change bit is set\non the last transfer in a message, an operation which the hardware does\nnot support.\n\nRationale\nSince the transfer_one_message() returns an int, we must presume that it\nmay fail. If transfer_one_message() should never fail, it should return\nvoid. Thus, calls to transfer_one_message() should properly manage a\nfailure.\n\nFixes: ffbbdd21329f3 (spi: create a message queueing infrastructure)\nSigned-off-by: Daniel Santos \u003cdaniel.santos@pobox.com\u003e\nSigned-off-by: Mark Brown \u003cbroonie@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "2332020b306a8da315f28cdac1cf19e6d9d470fd", "tree": "daf7825848b8b75b9ac5662cb3a836adecbb45a3", "parents": [ "0cc70c5ec55e404dd4c970a3566dc60508088932" ], "author": { "name": "Ira Weiny", "email": "ira.weiny@intel.com", "time": "Wed Dec 18 08:41:37 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:11 2014 -0800" }, "message": "IB/qib: Fix QP check when looping back to/from QP1\n\ncommit 6e0ea9e6cbcead7fa8c76e3e3b9de4a50c5131c5 upstream.\n\nThe GSI QP type is compatible with and should be allowed to send data\nto/from any UD QP. This was found when testing ibacm on the same node\nas an SA.\n\nReviewed-by: Mike Marciniszyn \u003cmike.marciniszyn@intel.com\u003e\nSigned-off-by: Ira Weiny \u003cira.weiny@intel.com\u003e\nSigned-off-by: Roland Dreier \u003croland@purestorage.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0cc70c5ec55e404dd4c970a3566dc60508088932", "tree": "45496133db35e147867f02d0a77e889a387cc82c", "parents": [ "0b909374b96f4ac56fcb18f3a94ff5c359ab46fa" ], "author": { "name": "Boaz Harrosh", "email": "bharrosh@panasas.com", "time": "Thu Nov 21 17:58:08 2013 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:11 2014 -0800" }, "message": "ore: Fix wrong math in allocation of per device BIO\n\ncommit aad560b7f63b495f48a7232fd086c5913a676e6f upstream.\n\nAt IO preparation we calculate the max pages at each device and\nallocate a BIO per device of that size. The calculation was wrong\non some unaligned corner cases offset/length combination and would\nmake prepare return with -ENOMEM. This would be bad for pnfs-objects\nthat would in that case IO through MDS. And fatal for exofs were it\nwould fail writes with EIO.\n\nFix it by doing the proper math, that will work in all cases. (I\nran a test with all possible offset/length combinations this time\nround).\n\nAlso when reading we do not need to allocate for the parity units\nsince we jump over them.\n\nAlso lower the max_io_length to take into account the parity pages\nso not to allocate BIOs bigger than PAGE_SIZE\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0b909374b96f4ac56fcb18f3a94ff5c359ab46fa", "tree": "f484b57fd8b3099a6e1f7473b866454d236d4f44", "parents": [ "3111943e88d17449a3a45fa777de67ab6ebf8447" ], "author": { "name": "Michael Grzeschik", "email": "m.grzeschik@pengutronix.de", "time": "Fri Nov 29 14:14:29 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:10 2014 -0800" }, "message": "mtd: mxc_nand: remove duplicated ecc_stats counting\n\ncommit 0566477762f9e174e97af347ee9c865f908a5647 upstream.\n\nThe ecc_stats.corrected count variable will already be incremented in\nthe above framework-layer just after this callback.\n\nSigned-off-by: Michael Grzeschik \u003cm.grzeschik@pengutronix.de\u003e\nSigned-off-by: Brian Norris \u003ccomputersforpeace@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3111943e88d17449a3a45fa777de67ab6ebf8447", "tree": "650c5765820b610b17fb563f11db000696a6abdb", "parents": [ "4c6544f60383bf6e95744f874598f7e5dd952110" ], "author": { "name": "Mark Brown", "email": "broonie@linaro.org", "time": "Mon Jan 27 00:32:14 2014 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:10 2014 -0800" }, "message": "ACPI / init: Flag use of ACPI and ACPI idioms for power supplies to regulator API\n\ncommit 49a12877d2777cadcb838981c3c4f5a424aef310 upstream.\n\nThere is currently no facility in ACPI to express the hookup of voltage\nregulators, the expectation is that the regulators that exist in the\nsystem will be handled transparently by firmware if they need software\ncontrol at all. This means that if for some reason the regulator API is\nenabled on such a system it should assume that any supplies that devices\nneed are provided by the system at all relevant times without any software\nintervention.\n\nTell the regulator core to make this assumption by calling\nregulator_has_full_constraints(). Do this as soon as we know we are using\nACPI so that the information is available to the regulator core as early\nas possible. This will cause the regulator core to pretend that there is\nan always on regulator supplying any supply that is requested but that has\nnot otherwise been mapped which is the behaviour expected on a system with\nACPI.\n\nShould the ability to specify regulators be added in future revisions of\nACPI then once we have support for ACPI mappings in the kernel the same\nassumptions will apply. It is also likely that systems will default to a\nmode of operation which does not require any interpretation of these\nmappings in order to be compatible with existing operating system releases\nso it should remain safe to make these assumptions even if the mappings\nexist but are not supported by the kernel.\n\nSigned-off-by: Mark Brown \u003cbroonie@linaro.org\u003e\nSigned-off-by: Rafael J. Wysocki \u003crafael.j.wysocki@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "4c6544f60383bf6e95744f874598f7e5dd952110", "tree": "0f82d239c15aa3e0200fb41a623f9ebbd01e3436", "parents": [ "b06c0a0cc545114be1579934e90ecc477201fde7" ], "author": { "name": "Josh Triplett", "email": "josh@joshtriplett.org", "time": "Tue Aug 20 17:20:14 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:09 2014 -0800" }, "message": "turbostat: Use GCC\u0027s CPUID functions to support PIC\n\ncommit 2b92865e648ce04a39fda4f903784a5d01ecb0dc upstream.\n\nturbostat uses inline assembly to call cpuid. On 32-bit x86, on systems\nthat have certain security features enabled by default that make -fPIC\nthe default, this causes a build error:\n\nturbostat.c: In function ‘check_cpuid’:\nturbostat.c:1906:2: error: PIC register clobbered by ‘ebx’ in ‘asm’\n asm(\"cpuid\" : \"\u003da\" (fms), \"\u003dc\" (ecx), \"\u003dd\" (edx) : \"a\" (1) : \"ebx\");\n ^\n\nGCC provides a header cpuid.h, containing a __get_cpuid function that\nworks with both PIC and non-PIC. (On PIC, it saves and restores ebx\naround the cpuid instruction.) Use that instead.\n\nSigned-off-by: Josh Triplett \u003cjosh@joshtriplett.org\u003e\nSigned-off-by: Len Brown \u003clen.brown@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b06c0a0cc545114be1579934e90ecc477201fde7", "tree": "dbf21dc718ab0f39a6bc6a5a68cfbc7240c065b7", "parents": [ "6fadde4ee7c143a0f059ecddfa14958a876bd934" ], "author": { "name": "Li Zefan", "email": "lizefan@huawei.com", "time": "Tue Sep 10 11:43:37 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:09 2014 -0800" }, "message": "slub: Fix calculation of cpu slabs\n\ncommit 8afb1474db4701d1ab80cd8251137a3260e6913e upstream.\n\n /sys/kernel/slab/:t-0000048 # cat cpu_slabs\n 231 N0\u003d16 N1\u003d215\n /sys/kernel/slab/:t-0000048 # cat slabs\n 145 N0\u003d36 N1\u003d109\n\nSee, the number of slabs is smaller than that of cpu slabs.\n\nThe bug was introduced by commit 49e2258586b423684f03c278149ab46d8f8b6700\n(\"slub: per cpu cache for partial pages\").\n\nWe should use page-\u003epages instead of page-\u003epobjects when calculating\nthe number of cpu partial slabs. This also fixes the mapping of slabs\nand nodes.\n\nAs there\u0027s no variable storing the number of total/active objects in\ncpu partial slabs, and we don\u0027t have user interfaces requiring those\nstatistics, I just add WARN_ON for those cases.\n\nAcked-by: Christoph Lameter \u003ccl@linux.com\u003e\nReviewed-by: Wanpeng Li \u003cliwanp@linux.vnet.ibm.com\u003e\nSigned-off-by: Li Zefan \u003clizefan@huawei.com\u003e\nSigned-off-by: Pekka Enberg \u003cpenberg@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6fadde4ee7c143a0f059ecddfa14958a876bd934", "tree": "8ec1b64b380fc2936fb6611fb64a81d9e0f95d10", "parents": [ "cd1188e7a59ca6c03cab5fe490bf18888a3ca5dc" ], "author": { "name": "Ludovic Desroches", "email": "ludovic.desroches@atmel.com", "time": "Wed Nov 20 16:01:11 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:08 2014 -0800" }, "message": "mmc: atmel-mci: fix timeout errors in SDIO mode when using DMA\n\ncommit 66b512eda74d59b17eac04c4da1b38d82059e6c9 upstream.\n\nWith some SDIO devices, timeout errors can happen when reading data.\nTo solve this issue, the DMA transfer has to be activated before sending\nthe command to the device. This order is incorrect in PDC mode. So we\nhave to take care if we are using DMA or PDC to know when to send the\nMMC command.\n\nSigned-off-by: Ludovic Desroches \u003cludovic.desroches@atmel.com\u003e\nAcked-by: Nicolas Ferre \u003cnicolas.ferre@atmel.com\u003e\nSigned-off-by: Chris Ball \u003ccjb@laptop.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cd1188e7a59ca6c03cab5fe490bf18888a3ca5dc", "tree": "0190e9cc1c4755e196580ebe407525e9b87f715e", "parents": [ "559316545580bbc61cf839e164c8a4c871c6ba42" ], "author": { "name": "AKASHI Takahiro", "email": "takahiro.akashi@linaro.org", "time": "Mon Jan 13 13:33:09 2014 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:08 2014 -0800" }, "message": "audit: correct a type mismatch in audit_syscall_exit()\n\ncommit 06bdadd7634551cfe8ce071fe44d0311b3033d9e upstream.\n\naudit_syscall_exit() saves a result of regs_return_value() in intermediate\n\"int\" variable and passes it to __audit_syscall_exit(), which expects its\nsecond argument as a \"long\" value. This will result in truncating the\nvalue returned by a system call and making a wrong audit record.\n\nI don\u0027t know why gcc compiler doesn\u0027t complain about this, but anyway it\ncauses a problem at runtime on arm64 (and probably most 64-bit archs).\n\nSigned-off-by: AKASHI Takahiro \u003ctakahiro.akashi@linaro.org\u003e\nCc: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Eric Paris \u003ceparis@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Eric Paris \u003ceparis@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "559316545580bbc61cf839e164c8a4c871c6ba42", "tree": "eb8153fafbd68d1c10fb9874cd3c601f5b4f531f", "parents": [ "ef609edc523e00e7b8cf6be348f52f6d6577d63e" ], "author": { "name": "Alex Williamson", "email": "alex.williamson@redhat.com", "time": "Tue Jan 21 15:48:18 2014 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:08 2014 -0800" }, "message": "intel-iommu: fix off-by-one in pagetable freeing\n\ncommit 08336fd218e087cc4fcc458e6b6dcafe8702b098 upstream.\n\ndma_pte_free_level() has an off-by-one error when checking whether a pte\nis completely covered by a range. Take for example the case of\nattempting to free pfn 0x0 - 0x1ff, ie. 512 entries covering the first\n2M superpage.\n\nThe level_size() is 0x200 and we test:\n\n static void dma_pte_free_level(...\n\t...\n\n\tif (!(0 \u003e 0 || 0x1ff \u003c 0 + 0x200)) {\n\t\t...\n\t}\n\nClearly the 2nd test is true, which means we fail to take the branch to\nclear and free the pagetable entry. As a result, we\u0027re leaking\npagetables and failing to install new pages over the range.\n\nThis was found with a PCI device assigned to a QEMU guest using vfio-pci\nwithout a VGA device present. The first 1M of guest address space is\nmapped with various combinations of 4K pages, but eventually the range\nis entirely freed and replaced with a 2M contiguous mapping.\nintel-iommu errors out with something like:\n\n ERROR: DMA PTE for vPFN 0x0 already set (to 5c2b8003 not 849c00083)\n\nIn this case 5c2b8003 is the pointer to the previous leaf page that was\nneither freed nor cleared and 849c00083 is the superpage entry that\nwe\u0027re trying to replace it with.\n\nSigned-off-by: Alex Williamson \u003calex.williamson@redhat.com\u003e\nCc: David Woodhouse \u003cdwmw2@infradead.org\u003e\nCc: Joerg Roedel \u003cjoro@8bytes.org\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": "ef609edc523e00e7b8cf6be348f52f6d6577d63e", "tree": "730c6ffc56d7904a5473602a80897f6da5dd246b", "parents": [ "e3b1f4138a12a66dcd2a48e5b4a7fa1bba9c2c5b" ], "author": { "name": "Tetsuo Handa", "email": "penguin-kernel@I-love.SAKURA.ne.jp", "time": "Mon Jan 06 21:28:15 2014 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 13 11:51:07 2014 -0800" }, "message": "SELinux: Fix memory leak upon loading policy\n\ncommit 8ed814602876bec9bad2649ca17f34b499357a1c upstream.\n\nHello.\n\nI got below leak with linux-3.10.0-54.0.1.el7.x86_64 .\n\n[ 681.903890] kmemleak: 5538 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\n\nBelow is a patch, but I don\u0027t know whether we need special handing for undoing\nebitmap_set_bit() call.\n----------\n\u003e\u003eFrom fe97527a90fe95e2239dfbaa7558f0ed559c0992 Mon Sep 17 00:00:00 2001\nFrom: Tetsuo Handa \u003cpenguin-kernel@I-love.SAKURA.ne.jp\u003e\nDate: Mon, 6 Jan 2014 16:30:21 +0900\nSubject: SELinux: Fix memory leak upon loading policy\n\nCommit 2463c26d \"SELinux: put name based create rules in a hashtable\" did not\ncheck return value from hashtab_insert() in filename_trans_read(). It leaks\nmemory if hashtab_insert() returns error.\n\n unreferenced object 0xffff88005c9160d0 (size 8):\n comm \"systemd\", pid 1, jiffies 4294688674 (age 235.265s)\n hex dump (first 8 bytes):\n 57 0b 00 00 6b 6b 6b a5 W...kkk.\n backtrace:\n [\u003cffffffff816604ae\u003e] kmemleak_alloc+0x4e/0xb0\n [\u003cffffffff811cba5e\u003e] kmem_cache_alloc_trace+0x12e/0x360\n [\u003cffffffff812aec5d\u003e] policydb_read+0xd1d/0xf70\n [\u003cffffffff812b345c\u003e] security_load_policy+0x6c/0x500\n [\u003cffffffff812a623c\u003e] sel_write_load+0xac/0x750\n [\u003cffffffff811eb680\u003e] vfs_write+0xc0/0x1f0\n [\u003cffffffff811ec08c\u003e] SyS_write+0x4c/0xa0\n [\u003cffffffff81690419\u003e] system_call_fastpath+0x16/0x1b\n [\u003cffffffffffffffff\u003e] 0xffffffffffffffff\n\nHowever, we should not return EEXIST error to the caller, or the systemd will\nshow below message and the boot sequence freezes.\n\n systemd[1]: Failed to load SELinux policy. Freezing.\n\nSigned-off-by: Tetsuo Handa \u003cpenguin-kernel@I-love.SAKURA.ne.jp\u003e\nAcked-by: Eric Paris \u003ceparis@redhat.com\u003e\nSigned-off-by: Paul Moore \u003cpmoore@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e3b1f4138a12a66dcd2a48e5b4a7fa1bba9c2c5b", "tree": "0dc456c7fe11ff7aa84c50d04b8d780818e45975", "parents": [ "988e453293f02271214645c7887638124095aa88" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:59 2014 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:59 2014 -0800" }, "message": "Linux 3.4.79\n" }, { "commit": "988e453293f02271214645c7887638124095aa88", "tree": "21ef4250810747ff72c9431acf3d661864c28c02", "parents": [ "06c23d087a238d3838de9b87c793195daae8a8bc" ], "author": { "name": "Paul Mackerras", "email": "paulus@samba.org", "time": "Sat Jan 18 21:14:47 2014 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:48 2014 -0800" }, "message": "powerpc: Make sure \"cache\" directory is removed when offlining cpu\n\ncommit 91b973f90c1220d71923e7efe1e61f5329806380 upstream.\n\nThe code in remove_cache_dir() is supposed to remove the \"cache\"\nsubdirectory from the sysfs directory for a CPU when that CPU is\nbeing offlined. It tries to do this by calling kobject_put() on\nthe kobject for the subdirectory. However, the subdirectory only\ngets removed once the last reference goes away, and the reference\nbeing put here may well not be the last reference. That means\nthat the \"cache\" subdirectory may still exist when the offlining\noperation has finished. If the same CPU subsequently gets onlined,\nthe code tries to add a new \"cache\" subdirectory. If the old\nsubdirectory has not yet been removed, we get a WARN_ON in the\nsysfs code, with stack trace, and an error message printed on the\nconsole. Further, we ultimately end up with an online cpu with no\n\"cache\" subdirectory.\n\nThis fixes it by doing an explicit kobject_del() at the point where\nwe want the subdirectory to go away. kobject_del() removes the sysfs\ndirectory even though the object still exists in memory. The object\nwill get freed at some point in the future. A subsequent onlining\noperation can create a new sysfs directory, even if the old object\nstill exists in memory, without causing any problems.\n\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": "06c23d087a238d3838de9b87c793195daae8a8bc", "tree": "8b9b6d20649575d7bad76509a70b0568e20f165c", "parents": [ "9e7fe101104b9254d37e316250d9570e0b29ecd2" ], "author": { "name": "Wang Shilong", "email": "wangsl.fnst@cn.fujitsu.com", "time": "Tue Jan 07 17:26:58 2014 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:48 2014 -0800" }, "message": "Btrfs: handle EAGAIN case properly in btrfs_drop_snapshot()\n\ncommit 90515e7f5d7d24cbb2a4038a3f1b5cfa2921aa17 upstream.\n\nWe may return early in btrfs_drop_snapshot(), we shouldn\u0027t\ncall btrfs_std_err() for this case, fix it.\n\nSigned-off-by: Wang Shilong \u003cwangsl.fnst@cn.fujitsu.com\u003e\nSigned-off-by: Josef Bacik \u003cjbacik@fb.com\u003e\nSigned-off-by: Chris Mason \u003cclm@fb.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9e7fe101104b9254d37e316250d9570e0b29ecd2", "tree": "8e12aa7962322c858c7063eab49fb2bf4f17199e", "parents": [ "bce4e9bf144e6394b61d1b275a720d76e2bc4b1a" ], "author": { "name": "Andy Grover", "email": "agrover@redhat.com", "time": "Fri Jan 24 16:18:54 2014 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:48 2014 -0800" }, "message": "target/iscsi: Fix network portal creation race\n\ncommit ee291e63293146db64668e8d65eb35c97e8324f4 upstream.\n\nWhen creating network portals rapidly, such as when restoring a\nconfiguration, LIO\u0027s code to reuse existing portals can return a false\nnegative if the thread hasn\u0027t run yet and set np_thread_state to\nISCSI_NP_THREAD_ACTIVE. This causes an error in the network stack\nwhen attempting to bind to the same address/port.\n\nThis patch sets NP_THREAD_ACTIVE before the np is placed on g_np_list,\nso even if the thread hasn\u0027t run yet, iscsit_get_np will return the\nexisting np.\n\nAlso, convert np_lock -\u003e np_mutex + hold across adding new net portal\nto g_np_list to prevent a race where two threads may attempt to create\nthe same network portal, resulting in one of them failing.\n\n(nab: Add missing mutex_unlocks in iscsit_add_np failure paths)\n(DanC: Fix incorrect spin_unlock -\u003e spin_unlock_bh)\n\nSigned-off-by: Andy Grover \u003cagrover@redhat.com\u003e\nSigned-off-by: Nicholas Bellinger \u003cnab@linux-iscsi.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "bce4e9bf144e6394b61d1b275a720d76e2bc4b1a", "tree": "7f75ea9c7baccd5a94f9ca0c500e62056c09ac21", "parents": [ "7af4a2da7aaca5f5a0e97fec4050cd8a3c59ebcd" ], "author": { "name": "Vijaya Mohan Guvva", "email": "vmohan@brocade.com", "time": "Wed Dec 04 05:43:58 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:48 2014 -0800" }, "message": "SCSI: bfa: Chinook quad port 16G FC HBA claim issue\n\ncommit dcaf9aed995c2b2a49fb86bbbcfa2f92c797ab5d upstream.\n\nBfa driver crash is observed while pushing the firmware on to chinook\nquad port card due to uninitialized bfi_image_ct2 access which gets\ninitialized only for CT2 ASIC based cards after request_firmware().\nFor quard port chinook (CT2 ASIC based), bfi_image_ct2 is not getting\ninitialized as there is no check for chinook PCI device ID before\nrequest_firmware and instead bfi_image_cb is initialized as it is the\ndefault case for card type check.\n\nThis patch includes changes to read the right firmware for quad port chinook.\n\nSigned-off-by: Vijaya Mohan Guvva \u003cvmohan@brocade.com\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Parallels.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7af4a2da7aaca5f5a0e97fec4050cd8a3c59ebcd", "tree": "b980af768a9a06c51bcf1c025d120f9faa377509", "parents": [ "cd1e02030a6f006234061a306454c4e3e4d4701a" ], "author": { "name": "Thomas Pugliese", "email": "thomas.pugliese@gmail.com", "time": "Mon Dec 09 13:40:29 2013 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:48 2014 -0800" }, "message": "usb: core: get config and string descriptors for unauthorized devices\n\ncommit 83e83ecb79a8225e79bc8e54e9aff3e0e27658a2 upstream.\n\nThere is no need to skip querying the config and string descriptors for\nunauthorized WUSB devices when usb_new_device is called. It is allowed\nby WUSB spec. The only action that needs to be delayed until\nauthorization time is the set config. This change allows user mode\ntools to see the config and string descriptors earlier in enumeration\nwhich is needed for some WUSB devices to function properly on Android\nsystems. It also reduces the amount of divergent code paths needed\nfor WUSB devices.\n\nSigned-off-by: Thomas Pugliese \u003cthomas.pugliese@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cd1e02030a6f006234061a306454c4e3e4d4701a", "tree": "041ba66baee753b2738aa801b7edf2d3cb6b4b31", "parents": [ "ee270c98472e0bf2ef7d9c15c81be0b1353bd969" ], "author": { "name": "Andy Honig", "email": "ahonig@google.com", "time": "Tue Nov 19 14:12:18 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:48 2014 -0800" }, "message": "KVM: x86: Fix potential divide by 0 in lapic (CVE-2013-6367)\n\ncommit b963a22e6d1a266a67e9eecc88134713fd54775c upstream.\n\nUnder guest controllable circumstances apic_get_tmcct will execute a\ndivide by zero and cause a crash. If the guest cpuid support\ntsc deadline timers and performs the following sequence of requests\nthe host will crash.\n- Set the mode to periodic\n- Set the TMICT to 0\n- Set the mode bits to 11 (neither periodic, nor one shot, nor tsc deadline)\n- Set the TMICT to non-zero.\nThen the lapic_timer.period will be 0, but the TMICT will not be. If the\nguest then reads from the TMCCT then the host will perform a divide by 0.\n\nThis patch ensures that if the lapic_timer.period is 0, then the division\ndoes not occur.\n\nReported-by: Andrew Honig \u003cahonig@google.com\u003e\nSigned-off-by: Andrew Honig \u003cahonig@google.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n[bwh: Backported to 3.2: s/kvm_apic_get_reg/apic_get_reg/]\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nCc: Vinson Lee \u003cvlee@twopensource.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ee270c98472e0bf2ef7d9c15c81be0b1353bd969", "tree": "e2efb72a4d3a7afdc79df78fbdf1ebf40c7f9e4a", "parents": [ "df647935d589103da0b8f8e3d4354646c006e85b" ], "author": { "name": "Richard Weinberger", "email": "richard@nod.at", "time": "Tue Jan 14 22:46:36 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:48 2014 -0800" }, "message": "net,via-rhine: Fix tx_timeout handling\n\n[ Upstream commit a926592f5e4e900f3fa903298c4619a131e60963 ]\n\nrhine_reset_task() misses to disable the tx scheduler upon reset,\nthis can lead to a crash if work is still scheduled while we\u0027re resetting\nthe tx queue.\n\nFixes:\n[ 93.591707] BUG: unable to handle kernel NULL pointer dereference at 0000004c\n[ 93.595514] IP: [\u003cc119d10d\u003e] rhine_napipoll+0x491/0x6\n\nSigned-off-by: Richard Weinberger \u003crichard@nod.at\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "df647935d589103da0b8f8e3d4354646c006e85b", "tree": "dedc4674726e9697411fddaad3c5eccbcbf4e126", "parents": [ "237275e9210b828f11c7dc2feac0ca1b0ced8eee" ], "author": { "name": "Hannes Frederic Sowa", "email": "hannes@stressinduktion.org", "time": "Mon Jan 13 02:45:22 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:48 2014 -0800" }, "message": "net: avoid reference counter overflows on fib_rules in multicast forwarding\n\n[ Upstream commit 95f4a45de1a0f172b35451fc52283290adb21f6e ]\n\nBob Falken reported that after 4G packets, multicast forwarding stopped\nworking. This was because of a rule reference counter overflow which\nfreed the rule as soon as the overflow happend.\n\nThis patch solves this by adding the FIB_LOOKUP_NOREF flag to\nfib_rules_lookup calls. This is safe even from non-rcu locked sections\nas in this case the flag only implies not taking a reference to the rule,\nwhich we don\u0027t need at all.\n\nRules only hold references to the namespace, which are guaranteed to be\navailable during the call of the non-rcu protected function reg_vif_xmit\nbecause of the interface reference which itself holds a reference to\nthe net namespace.\n\nFixes: f0ad0860d01e47 (\"ipv4: ipmr: support multiple tables\")\nFixes: d1db275dd3f6e4 (\"ipv6: ip6mr: support multiple tables\")\nReported-by: Bob Falken \u003cNetFestivalHaveFun@gmx.com\u003e\nCc: Patrick McHardy \u003ckaber@trash.net\u003e\nCc: Thomas Graf \u003ctgraf@suug.ch\u003e\nCc: Julian Anastasov \u003cja@ssi.bg\u003e\nCc: Eric Dumazet \u003ceric.dumazet@gmail.com\u003e\nSigned-off-by: Hannes Frederic Sowa \u003channes@stressinduktion.org\u003e\nAcked-by: Eric Dumazet \u003cedumazet@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "237275e9210b828f11c7dc2feac0ca1b0ced8eee", "tree": "f8bc32a43ad90af369899433587de3b9182f097c", "parents": [ "335d84d37ae8c6e293bada7565c32eff404519ed" ], "author": { "name": "Neal Cardwell", "email": "ncardwell@google.com", "time": "Sun Feb 02 20:40:13 2014 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:48 2014 -0800" }, "message": "inet_diag: fix inet_diag_dump_icsk() timewait socket state logic\n\n[ Based upon upstream commit 70315d22d3c7383f9a508d0aab21e2eb35b2303a ]\n\nFix inet_diag_dump_icsk() to reflect the fact that both TIME_WAIT and\nFIN_WAIT2 connections are represented by inet_timewait_sock (not just\nTIME_WAIT). Thus:\n\n(a) We need to iterate through the time_wait buckets if the user wants\neither TIME_WAIT or FIN_WAIT2. (Before fixing this, \"ss -nemoi state\nfin-wait-2\" would not return any sockets, even if there were some in\nFIN_WAIT2.)\n\n(b) We need to check tw_substate to see if the user wants to dump\nsockets in the particular substate (TIME_WAIT or FIN_WAIT2) that a\ngiven connection is in. (Before fixing this, \"ss -nemoi state\ntime-wait\" would actually return sockets in state FIN_WAIT2.)\n\nAn analogous fix is in v3.13: 70315d22d3c7383f9a508d0aab21e2eb35b2303a\n(\"inet_diag: fix inet_diag_dump_icsk() to use correct state for\ntimewait sockets\") but that patch is quite different because 3.13 code\nis very different in this area due to the unification of TCP hash\ntables in 05dbc7b (\"tcp/dccp: remove twchain\") in v3.13-rc1.\n\nI tested that this applies cleanly between v3.3 and v3.12, and tested\nthat it works in both 3.3 and 3.12. It does not apply cleanly to 3.2\nand earlier (though it makes semantic sense), and semantically is not\nthe right fix for 3.13 and beyond (as mentioned above).\n\nSigned-off-by: Neal Cardwell \u003cncardwell@google.com\u003e\nCc: Eric Dumazet \u003cedumazet@google.com\u003e\nAcked-by: Eric Dumazet \u003cedumazet@google.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "335d84d37ae8c6e293bada7565c32eff404519ed", "tree": "aa4fbc1e787a1161aa7d311774b37278a13cf391", "parents": [ "49ac3cba40b81521509c3a08c93ea1d6b5660745" ], "author": { "name": "Michal Schmidt", "email": "mschmidt@redhat.com", "time": "Thu Jan 09 14:36:27 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "bnx2x: fix DMA unmapping of TSO split BDs\n\n[ Upstream commit 95e92fd40c967c363ad66b2fd1ce4dcd68132e54 ]\n\nbnx2x triggers warnings with CONFIG_DMA_API_DEBUG\u003dy:\n\n WARNING: CPU: 0 PID: 2253 at lib/dma-debug.c:887 check_unmap+0xf8/0x920()\n bnx2x 0000:28:00.0: DMA-API: device driver frees DMA memory with\n different size [device address\u003d0x00000000da2b389e] [map size\u003d1490 bytes]\n [unmap size\u003d66 bytes]\n\nThe reason is that bnx2x splits a TSO BD into two BDs (headers + data)\nusing one DMA mapping for both, but it uses only the length of the first\nBD when unmapping.\n\nThis patch fixes the bug by unmapping the whole length of the two BDs.\n\nSigned-off-by: Michal Schmidt \u003cmschmidt@redhat.com\u003e\nReviewed-by: Eric Dumazet \u003cedumazet@google.com\u003e\nAcked-by: Dmitry Kravkov \u003cdmitry@broadcom.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "49ac3cba40b81521509c3a08c93ea1d6b5660745", "tree": "a3d3bdfe577f9118f8f14a7b3a95d5c283c1cad9", "parents": [ "6a2797db120b8c9ffe34e9327e451f705894b82a" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Mon Jan 13 12:32:44 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "hp_accel: Add a new PnP ID HPQ6007 for new HP laptops\n\ncommit b0ad4ff35d479a46a3b995a299db9aeb097acfce upstream.\n\nThe DriveGuard chips on the new HP laptops are with a new PnP ID\n\"HPQ6007\". It should be compatible with older chips.\n\nAcked-by: Éric Piel \u003ceric.piel@tremplin-utc.net\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Matthew Garrett \u003cmatthew.garrett@nebula.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6a2797db120b8c9ffe34e9327e451f705894b82a", "tree": "37d2fb46138a5cdf9bb85ebe0b2f65cdc968399b", "parents": [ "f2d6404bdb7a2a8e6832d98cac1428ff12c2c5cf" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Fri Jan 10 14:20:42 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "ALSA: Enable CONFIG_ZONE_DMA for smaller PCI DMA masks\n\ncommit 80ab8eae70e51d578ebbeb228e0f7a562471b8b7 upstream.\n\nThe PCI devices with DMA masks smaller than 32bit should enable\nCONFIG_ZONE_DMA. Since the recent change of page allocator, page\nallocations via dma_alloc_coherent() with the limited DMA mask bits\nmay fail more frequently, ended up with no available buffers, when\nCONFIG_ZONE_DMA isn\u0027t enabled. With CONFIG_ZONE_DMA, the system has\nmuch more chance to obtain such pages.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id\u003d68221\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f2d6404bdb7a2a8e6832d98cac1428ff12c2c5cf", "tree": "1bca129f6366ec3e757f37cb842b24e49c13d876", "parents": [ "f5e764b0d4b5252c2850eabd00748e60d951f2b5" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Fri Dec 27 00:13:08 2013 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "ALSA: rme9652: fix a missing comma in channel_map_9636_ds[]\n\ncommit 770bd4bf2e664939a9dacd3d26ec9ff7a3933210 upstream.\n\nThe lack of comma leads to the wrong channel for an SPDIF channel.\nUnfortunately this wasn\u0027t caught by compiler because it\u0027s still a\nvalid expression.\n\nReported-by: Alexander Aristov \u003caristov.alexander@gmail.com\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f5e764b0d4b5252c2850eabd00748e60d951f2b5", "tree": "eaebc0d0bdf2614fb21349eb18e93ee238dda07f", "parents": [ "28a02c0eef5ec0cb78c181e611f46d251e08a711" ], "author": { "name": "Lars-Peter Clausen", "email": "lars@metafoo.de", "time": "Wed Jan 08 11:22:25 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "ASoC: adau1701: Fix ADAU1701_SEROCTL_WORD_LEN_16 constant\n\ncommit e20970ada3f699c113fe64b04492af083d11a7d8 upstream.\n\nThe driver defines ADAU1701_SEROCTL_WORD_LEN_16 as 0x10 while it should be b10,\nso 0x2. This patch fixes it.\n\nReported-by: Magnus Reftel \u003cmagnus.reftel@lockless.no\u003e\nSigned-off-by: Lars-Peter Clausen \u003clars@metafoo.de\u003e\nSigned-off-by: Mark Brown \u003cbroonie@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "28a02c0eef5ec0cb78c181e611f46d251e08a711", "tree": "28ae161877599d450a966b946ff34fcfc7c327df", "parents": [ "17b27b25f3618f48d3a80ab2b2887ab597446015" ], "author": { "name": "Sebastian Andrzej Siewior", "email": "bigeasy@linutronix.de", "time": "Wed Nov 27 17:43:43 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "parport: parport_pc: remove double PCI ID for NetMos\n\ncommit d6a484520c5572a4170fa915109ccfc0c38f5008 upstream.\n\nIn commit 85747f (\"PATCH] parport: add NetMOS 9805 support\") Max added\nthe PCI ID for NetMOS 9805 based on a Debian bug report from 2k4 which\nwas at the v2.4.26 time frame. The patch made into 2.6.14.\nShortly before that patch akpm merged commit 296d3c783b (\"[PATCH] Support\nNetMOS based PCI cards providing serial and parallel ports\") which made\ninto v2.6.9-rc1.\nNow we have two different entries for the same PCI id.\nI have here the NetMos 9805 which claims to support SPP/EPP/ECP mode.\nThis patch takes Max\u0027s entry for titan_1284p1 (base !\u003d -1 specifies the\nioport for ECP mode) and replaces akpm\u0027s entry for netmos_9805 which\nspecified -1 (\u003dnone). Both share the same PCI-ID (my card has subsystem\n0x1000 / 0x0020 so it should match PCI_ANY).\n\nWhile here I also drop the entry for titan_1284p2 which is the same as\nnetmos_9815.\n\nCc: Maximilian Attems \u003cmaks@stro.at\u003e\nSigned-off-by: Sebastian Andrzej Siewior \u003cbigeasy@linutronix.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "17b27b25f3618f48d3a80ab2b2887ab597446015", "tree": "8f1b6c27adb4ba8969a94d56ae2e8e21ea5ff8e2", "parents": [ "fbc32582959394e3932b9eb1688d6991c9a42ea2" ], "author": { "name": "Yegor Yefremov", "email": "yegorslists@googlemail.com", "time": "Mon Dec 09 12:11:15 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "serial: add support for 200 v3 series Titan card\n\ncommit 48c0247d7b7bf58abb85a39021099529df365c4d upstream.\n\nSigned-off-by: Yegor Yefremov \u003cyegorslists@googlemail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "fbc32582959394e3932b9eb1688d6991c9a42ea2", "tree": "7266dead6706dd13bf49c5d7d6d223c9e68b5cab", "parents": [ "3a9694557f5aefc34a08bddcfcbd0ca12d8dec9a" ], "author": { "name": "Jean-Jacques Hiblot", "email": "jjhiblot@traphandler.com", "time": "Thu Jan 09 16:01:54 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "ARM: at91: smc: bug fix in sam9_smc_cs_read()\n\ncommit 1588c51cf6d782e63a8719681d905ef0ac22ee62 upstream.\n\nThere was a copy/paste error when reading the nwe_pulse value.\n\nSigned-off-by: Jean-Jacques Hiblot \u003cjjhiblot@traphandler.com\u003e\nAcked-by: Boris BREZILLON \u003cb.brezillon@overkiz.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@atmel.com\u003e\nSigned-off-by: Kevin Hilman \u003ckhilman@linaro.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3a9694557f5aefc34a08bddcfcbd0ca12d8dec9a", "tree": "1f8442e58739d0ee9e009f050c07c8f150f8aa62", "parents": [ "b135ecd41b9e19dda09654086a54f9cd13ab89b3" ], "author": { "name": "Marek Roszko", "email": "mark.roszko@gmail.com", "time": "Tue Jan 07 11:45:06 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "tty/serial: at91: Handle shutdown more safely\n\ncommit 0cc7c6c7916b1b6f34350ff1473b80b9f7e459c0 upstream.\n\nInterrupts were being cleaned up late in the shutdown handler, it is possible\nthat an interrupt can occur and schedule a tasklet that runs after the port is\ncleaned up. There is a null dereference due to this race condition with the\nfollowing stacktrace:\n\n[\u003cc02092b0\u003e] (atmel_tasklet_func+0x514/0x814) from [\u003cc001fd34\u003e] (tasklet_action+0x70/0xa8)\n[\u003cc001fd34\u003e] (tasklet_action+0x70/0xa8) from [\u003cc001f60c\u003e] (__do_softirq+0x90/0x144)\n[\u003cc001f60c\u003e] (__do_softirq+0x90/0x144) from [\u003cc001fa18\u003e] (irq_exit+0x40/0x4c)\n[\u003cc001fa18\u003e] (irq_exit+0x40/0x4c) from [\u003cc000e298\u003e] (handle_IRQ+0x64/0x84)\n[\u003cc000e298\u003e] (handle_IRQ+0x64/0x84) from [\u003cc000d6c0\u003e] (__irq_svc+0x40/0x50)\n[\u003cc000d6c0\u003e] (__irq_svc+0x40/0x50) from [\u003cc0208060\u003e] (atmel_rx_dma_release+0x88/0xb8)\n[\u003cc0208060\u003e] (atmel_rx_dma_release+0x88/0xb8) from [\u003cc0209740\u003e] (atmel_shutdown+0x104/0x160)\n[\u003cc0209740\u003e] (atmel_shutdown+0x104/0x160) from [\u003cc0205e8c\u003e] (uart_port_shutdown+0x2c/0x38)\n\nSigned-off-by: Marek Roszko \u003cmark.roszko@gmail.com\u003e\nAcked-by: Leilei Zhao \u003cleilei.zhao@atmel.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@atmel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b135ecd41b9e19dda09654086a54f9cd13ab89b3", "tree": "59ce51e674167f7cab04d142986849a74ce2f050", "parents": [ "86374e1cbe070cc1d554d0490a0357c09a5d95f0" ], "author": { "name": "Malcolm Priestley", "email": "tvboxspy@gmail.com", "time": "Sun Dec 08 09:11:30 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "staging: vt6656: [BUG] BBvUpdatePreEDThreshold Always set sensitivity on bScanning\n\ncommit 8f248dae133668bfb8e9379b4b3f0571c858b24a upstream.\n\nbyBBPreEDIndex value is initially 0, this means that from\ncold BBvUpdatePreEDThreshold is never set.\n\nThis means that sensitivity may be in an ambiguous state,\nfailing to scan any wireless points or at least distant ones.\n\nSigned-off-by: Malcolm Priestley \u003ctvboxspy@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "86374e1cbe070cc1d554d0490a0357c09a5d95f0", "tree": "3d5eb3834f4e093fed669cb556a685811ff0be9e", "parents": [ "b17696dbe5c61eb8a312789878c0538517c26f02" ], "author": { "name": "Larry Finger", "email": "Larry.Finger@lwfinger.net", "time": "Tue Dec 24 11:22:54 2013 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "staging: r8712u: Set device type to wlan\n\ncommit 3a21f00a5002b14e4aab52aef59d33ed28468a13 upstream.\n\nThe latest version of NetworkManager does not recognize the device as wireless\nwithout this change.\n\nSigned-off-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b17696dbe5c61eb8a312789878c0538517c26f02", "tree": "c4fa3c020032039cd9a44d10dd37a9e7d622075a", "parents": [ "06600864a0aa2827669c3bad96bf0081a7c4019e" ], "author": { "name": "ZHAO Gang", "email": "gamerh2o@gmail.com", "time": "Sat Jan 18 00:17:38 2014 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "b43: fix the wrong assignment of status.freq in b43_rx()\n\ncommit 64e5acb09ca6b50c97299cff9ef51299470b29f2 upstream.\n\nUse the right function to update frequency value.\n\nIf rx skb is probe response or beacon, the wrong frequency value can\ncause problem that bss info can\u0027t be updated when it should be.\n\nFixes: 8318d78a44d4 (\"cfg80211 API for channels/bitrates, mac80211 and driver conversion\")\nSigned-off-by: ZHAO Gang \u003cgamerh2o@gmail.com\u003e\nAcked-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "06600864a0aa2827669c3bad96bf0081a7c4019e", "tree": "d647cf9d3a8bffbe1d4e4ba8bbbce772854b0ce5", "parents": [ "5cdc61ecc7d1753890162f5f59a5ddebc81d6b97" ], "author": { "name": "Larry Finger", "email": "Larry.Finger@lwfinger.net", "time": "Sun Jan 12 15:11:39 2014 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "b43legacy: Fix unload oops if firmware is not available\n\ncommit 452028665312672c6ba9e16a19248ee00ead9400 upstream.\n\nThe asyncronous firmware load uses a completion struct to hold firmware\nprocessing until the user-space routines are up and running. There is.\nhowever, a problem in that the waiter is nevered canceled during teardown.\nAs a result, unloading the driver when firmware is not available causes an oops.\n\nSigned-off-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5cdc61ecc7d1753890162f5f59a5ddebc81d6b97", "tree": "e198cf738f349ab75d7bc8612d51fe660e648163", "parents": [ "4dbfb7dd725b29e1aa1bbe2db6aadaf6d825b9c4" ], "author": { "name": "Larry Finger", "email": "Larry.Finger@lwfinger.net", "time": "Sun Jan 12 15:11:38 2014 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "b43: Fix unload oops if firmware is not available\n\ncommit 0673effd41dba323d6a280ef37b5ef29f3f5a653 upstream.\n\nThe asyncronous firmware load uses a completion struct to hold firmware\nprocessing until the user-space routines are up and running. There is.\nhowever, a problem in that the waiter is nevered canceled during teardown.\nAs a result, unloading the driver when firmware is not available causes an oops.\n\nTo be able to access the completion structure at teardown, it had to be moved\ninto the b43_wldev structure.\n\nThis patch also fixes a typo in a comment.\n\nSigned-off-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "4dbfb7dd725b29e1aa1bbe2db6aadaf6d825b9c4", "tree": "a50bded751f09606995d4b0e68cba6f3cb81d665", "parents": [ "2ef4b350117b132da638064241c0d1e4a05e3408" ], "author": { "name": "Larry Finger", "email": "Larry.Finger@lwfinger.net", "time": "Sun Jan 12 15:11:37 2014 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "b43: Fix lockdep splat\n\ncommit 09164043f63c947a49797750a09ca1cd7c31108e upstream.\n\nIn https://bugzilla.kernel.org/show_bug.cgi?id\u003d67561, a locking dependency is reported\nwhen b43 is used with hostapd, and rfkill is used to kill the radio output.\n\nThe lockdep splat (in part) is as follows:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n[ INFO: possible circular locking dependency detected ]\n3.12.0 #1 Not tainted\n-------------------------------------------------------\nrfkill/10040 is trying to acquire lock:\n (rtnl_mutex){+.+.+.}, at: [\u003cffffffff8146f282\u003e] rtnl_lock+0x12/0x20\n\nbut task is already holding lock:\n (rfkill_global_mutex){+.+.+.}, at: [\u003cffffffffa04832ca\u003e] rfkill_fop_write+0x6a/0x170 [rfkill]\n\n--snip--\n\nChain exists of:\n rtnl_mutex --\u003e misc_mtx --\u003e rfkill_global_mutex\n\nThe fix is to move the initialization of the hardware random number generator\noutside the code range covered by the rtnl_mutex.\n\nReported-by: yury \u003curykhy@gmail.com\u003e\nTested-by: yury \u003curykhy@gmail.com\u003e\nSigned-off-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "2ef4b350117b132da638064241c0d1e4a05e3408", "tree": "8044b5a3d49d39d051b45d625a1737b53829594c", "parents": [ "eb14346e16c5dfad3b0eac308b6f4f93fdf0e3dd" ], "author": { "name": "Larry Finger", "email": "Larry.Finger@lwfinger.net", "time": "Mon Nov 18 11:11:34 2013 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "rtlwifi: rtl8192cu: Fix some code in RF handling\n\ncommit e9b0784bb9de3152e787ee779868c626b137fb3b upstream.\n\nSigned-off-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "eb14346e16c5dfad3b0eac308b6f4f93fdf0e3dd", "tree": "0d545740647d265c83f19905630d33433daae6dd", "parents": [ "94c773a2f58ca0c5b7204753d653b221f5761d0a" ], "author": { "name": "Larry Finger", "email": "Larry.Finger@lwfinger.net", "time": "Mon Nov 18 11:11:28 2013 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "rtlwifi: Set the link state\n\ncommit 619ce76f8bb850b57032501a39f26aa6c6731c70 upstream.\n\nThe present code fails to set the linked state when an interface is\nadded.\n\nSigned-off-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "94c773a2f58ca0c5b7204753d653b221f5761d0a", "tree": "89df0be23bfa78c1c1f6809c1df81cdd9ea34bd0", "parents": [ "23faa15314addfc1a1a2768ce55c3f8a61570d6e" ], "author": { "name": "Larry Finger", "email": "Larry.Finger@lwfinger.net", "time": "Thu Jan 09 10:27:27 2014 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:47 2014 -0800" }, "message": "rtlwifi: rtl8192cu: Add new device ID\n\ncommit f87f960b2fb802f26ee3b00c19320e57a9c583ff upstream.\n\nReported-by: Jan Prinsloo \u003cjanroot@gmail.com\u003e\nTested-by: Jan Prinsloo \u003cjanroot@gmail.com\u003e\nSigned-off-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "23faa15314addfc1a1a2768ce55c3f8a61570d6e", "tree": "ce34d295a71a4444e62a352010367da8b070abdd", "parents": [ "0c18e8161aa0e9083a12c86106d0bbe19591c29e" ], "author": { "name": "Jack Pham", "email": "jackp@codeaurora.org", "time": "Fri Nov 15 14:53:14 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:46 2014 -0800" }, "message": "usb: xhci: Check for XHCI_PLAT in xhci_cleanup_msix()\n\ncommit 9005355af23856c55a5538c9024355785424821b upstream.\n\nIf CONFIG_PCI is enabled, make sure xhci_cleanup_msix()\ndoesn\u0027t try to free a bogus PCI IRQ or dereference an invalid\npci_dev when the xHCI device is actually a platform_device.\n\nThis patch should be backported to kernels as old as 3.9, that\ncontain the commit 52fb61250a7a132b0cfb9f4a1060a1f3c49e5a25\n\"xhci-plat: Don\u0027t enable legacy PCI interrupts.\"\n\nSigned-off-by: Jack Pham \u003cjackp@codeaurora.org\u003e\nSigned-off-by: Sarah Sharp \u003csarah.a.sharp@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0c18e8161aa0e9083a12c86106d0bbe19591c29e", "tree": "10439d5b65507fb4e515e4eb5d13488dd2fc0d22", "parents": [ "9b39aa6263e96fd35de126ccd205dae6935beef6" ], "author": { "name": "Mikhail Zolotaryov", "email": "lebon@lebon.org.ua", "time": "Sat Dec 28 01:56:35 2013 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:46 2014 -0800" }, "message": "USB: Nokia 502 is an unusual device\n\ncommit 0e16114f2db4838251fb64f3b550996ad3585890 upstream.\n\nThe USB storage operation of Nokia Asha 502 Dual SIM smartphone running Asha\nPlatform 1.1.1 is unreliable in respect of data consistency (i.e. transfered\nfiles are corrupted). A similar issue is described here:\nhttp://discussions.nokia.com/t5/Asha-and-other-Nokia-Series-30/Nokia-301-USB-transfers-and-corrupted-files/td-p/1974170\n\nThe workaround is (MAX_SECTORS_64):\n rmmod usb_storage \u0026\u0026 modprobe usb_storage quirks\u003d0421:06aa:m\n\nThe patch adds the tested device to the unusual list permanently.\n\nSigned-off-by: Mikhail Zolotaryov \u003clebon@lebon.org.ua\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9b39aa6263e96fd35de126ccd205dae6935beef6", "tree": "ea9c382e65f6a646e04b4fd168b3f8d76ca6ae43", "parents": [ "88083fd5ed5d3e42050530b4098145562254c20e" ], "author": { "name": "Johan Hovold", "email": "jhovold@gmail.com", "time": "Thu Jan 02 22:49:24 2014 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 06 11:05:46 2014 -0800" }, "message": "USB: cypress_m8: fix ring-indicator detection and reporting\n\ncommit 440ebadeae9298d7de3d4d105342691841ec88d0 upstream.\n\nFix ring-indicator (RI) status-bit definition, which was defined as CTS,\neffectively preventing RI-changes from being detected while reporting\nfalse RI status.\n\nThis bug predates git.\n\nSigned-off-by: Johan Hovold \u003cjhovold@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" } ], "next": "88083fd5ed5d3e42050530b4098145562254c20e" }