)]}' { "log": [ { "commit": "32e653056d900d3ecc984733dbfcea34c92bf6d0", "tree": "6f7adb3847243b894ed8f6b1589109c53bd03f0f", "parents": [ "fea0071c60870fbebc605ef72d87668d72dbbd81" ], "author": { "name": "Jianguo Wu", "email": "wujianguo@huawei.com", "time": "Mon Sep 17 14:08:56 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:05 2012 -0700" }, "message": "mm/ia64: fix a memory block size bug\n\ncommit 05cf96398e1b6502f9e191291b715c7463c9d5dd upstream.\n\nI found following definition in include/linux/memory.h, in my IA64\nplatform, SECTION_SIZE_BITS is equal to 32, and MIN_MEMORY_BLOCK_SIZE\nwill be 0.\n\n #define MIN_MEMORY_BLOCK_SIZE (1 \u003c\u003c SECTION_SIZE_BITS)\n\nBecause MIN_MEMORY_BLOCK_SIZE is int type and length of 32bits,\nso MIN_MEMORY_BLOCK_SIZE(1 \u003c\u003c 32) will will equal to 0.\nActually when SECTION_SIZE_BITS \u003e\u003d 31, MIN_MEMORY_BLOCK_SIZE will be wrong.\nThis will cause wrong system memory infomation in sysfs.\nI think it should be:\n\n #define MIN_MEMORY_BLOCK_SIZE (1UL \u003c\u003c SECTION_SIZE_BITS)\n\nAnd \"echo offline \u003e memory0/state\" will cause following call trace:\n\n kernel BUG at mm/memory_hotplug.c:885!\n sh[6455]: bugcheck! 0 [1]\n Pid: 6455, CPU 0, comm: sh\n psr : 0000101008526030 ifs : 8000000000000fa4 ip : [\u003ca0000001008c40f0\u003e] Not tainted (3.6.0-rc1)\n ip is at offline_pages+0x210/0xee0\n Call Trace:\n show_stack+0x80/0xa0\n show_regs+0x640/0x920\n die+0x190/0x2c0\n die_if_kernel+0x50/0x80\n ia64_bad_break+0x3d0/0x6e0\n ia64_native_leave_kernel+0x0/0x270\n offline_pages+0x210/0xee0\n alloc_pages_current+0x180/0x2a0\n\nSigned-off-by: Jianguo Wu \u003cwujianguo@huawei.com\u003e\nSigned-off-by: Jiang Liu \u003cjiang.liu@huawei.com\u003e\nCc: \"Luck, Tony\" \u003ctony.luck@intel.com\u003e\nReviewed-by: Michal Hocko \u003cmhocko@suse.cz\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": "fea0071c60870fbebc605ef72d87668d72dbbd81", "tree": "4e03b5a6c7cf27f77e4032539c3b7b331940b34a", "parents": [ "48f0f14ffb6ff4852922994d11fbda418d40100e" ], "author": { "name": "Benoît Locher", "email": "Benoit.Locher@skf.com", "time": "Mon Aug 27 15:02:45 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:05 2012 -0700" }, "message": "can: mcp251x: avoid repeated frame bug\n\ncommit cab32f39dcc5b35db96497dc0a026b5dea76e4e7 upstream.\n\nThe MCP2515 has a silicon bug causing repeated frame transmission, see section\n5 of MCP2515 Rev. B Silicon Errata Revision G (March 2007).\n\nBasically, setting TXBnCTRL.TXREQ in either SPI mode (00 or 11) will eventually\ncause the bug. The workaround proposed by Microchip is to use mode 00 and send\na RTS command on the SPI bus to initiate the transmission.\n\nSigned-off-by: Benoît Locher \u003cBenoit.Locher@skf.com\u003e\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "48f0f14ffb6ff4852922994d11fbda418d40100e", "tree": "c1889eaa22a13909c8790013e22852e8e4f7610f", "parents": [ "a95bb54b6345874159a82b93c67c49244d2433f2" ], "author": { "name": "Charles Wang", "email": "muming.wq@taobao.com", "time": "Mon Aug 20 16:02:33 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:05 2012 -0700" }, "message": "sched: Add missing call to calc_load_exit_idle()\n\ncommit 749c8814f08f12baa4a9c2812a7c6ede7d69507d upstream.\n\nAzat Khuzhin reported high loadavg in Linux v3.6\n\nAfter checking the upstream scheduler code, I found Peter\u0027s commit:\n\n 5167e8d5417b sched/nohz: Rewrite and fix load-avg computation -- again\n\nnot fully applied, missing the call to calc_load_exit_idle().\n\nAfter that idle exit in sampling window will always be calculated\nto non-idle, and the load will be higher than normal.\n\nThis patch adds the missing call to calc_load_exit_idle().\n\nSigned-off-by: Charles Wang \u003cmuming.wq@taobao.com\u003e\nSigned-off-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nLink: http://lkml.kernel.org/r/1345449754-27130-1-git-send-email-muming.wq@gmail.com\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a95bb54b6345874159a82b93c67c49244d2433f2", "tree": "b94b4b5377a11fcc273f89e02e0c009e067eaea2", "parents": [ "6093dd2f5a10b5a071aa623be7927a6421762adb" ], "author": { "name": "Guenter Roeck", "email": "linux@roeck-us.net", "time": "Tue Jun 19 08:00:00 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:05 2012 -0700" }, "message": "hwmon: (twl4030-madc-hwmon) Initialize uninitialized structure elements\n\ncommit 73d7c119255615a26070f9d6cdb722a166a29015 upstream.\n\ntwl4030_madc_conversion uses do_avg and type structure elements of\ntwl4030_madc_request. Initialize structure to avoid random operation.\n\nFix for: Coverity CID 200794 Uninitialized scalar variable.\n\nCc: Keerthy \u003cj-keerthy@ti.com\u003e\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nAcked-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nAcked-by: Keerthy \u003cj-keerthy@ti.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6093dd2f5a10b5a071aa623be7927a6421762adb", "tree": "212f67a5ffc75249c82f823e5df0d723762a9ca2", "parents": [ "aa7994f281a5e705b5f9cb13b3219fc346263872" ], "author": { "name": "Kevin Hilman", "email": "khilman@ti.com", "time": "Mon Sep 17 14:09:17 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:05 2012 -0700" }, "message": "drivers/rtc/rtc-twl.c: ensure all interrupts are disabled during probe\n\ncommit 8dcebaa9a0ae8a0487f4342f3d56d2cb1c980860 upstream.\n\nOn some platforms, bootloaders are known to do some interesting RTC\nprogramming. Without going into the obscurities as to why this may be\nthe case, suffice it to say the the driver should not make any\nassumptions about the state of the RTC when the driver loads. In\nparticular, the driver probe should be sure that all interrupts are\ndisabled until otherwise programmed.\n\nThis was discovered when finding bursty I2C traffic every second on\nOvero platforms. This I2C overhead was keeping the SoC from hitting\ndeep power states. The cause was found to be the RTC firing every\nsecond on the I2C-connected TWL PMIC.\n\nSpecial thanks to Felipe Balbi for suggesting to look for a rogue driver\nas the source of the I2C traffic rather than the I2C driver itself.\n\nSpecial thanks to Steve Sakoman for helping track down the source of the\ncontinuous RTC interrups on the Overo boards.\n\nSigned-off-by: Kevin Hilman \u003ckhilman@ti.com\u003e\nCc: Felipe Balbi \u003cbalbi@ti.com\u003e\nTested-by: Steve Sakoman \u003csteve@sakoman.com\u003e\nCc: Alessandro Zummo \u003ca.zummo@towertech.it\u003e\nTested-by: Shubhrajyoti Datta \u003comaplinuxkernel@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "aa7994f281a5e705b5f9cb13b3219fc346263872", "tree": "bcb197b1091bfd854890418b2aebd92c077b9a2f", "parents": [ "a4dd7e6c27a37237f09d437a515a3330093d4f70" ], "author": { "name": "Li Haifeng", "email": "omycle@gmail.com", "time": "Mon Sep 17 14:09:21 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:05 2012 -0700" }, "message": "mm/page_alloc: fix the page address of higher page\u0027s buddy calculation\n\ncommit 0ba8f2d59304dfe69b59c034de723ad80f7ab9ac upstream.\n\nThe heuristic method for buddy has been introduced since commit\n43506fad21ca (\"mm/page_alloc.c: simplify calculation of combined index\nof adjacent buddy lists\"). But the page address of higher page\u0027s buddy\nwas wrongly calculated, which will lead page_is_buddy to fail for ever.\nIOW, the heuristic method would be disabled with the wrong page address\nof higher page\u0027s buddy.\n\nCalculating the page address of higher page\u0027s buddy should be based\nhigher_page with the offset between index of higher page and index of\nhigher page\u0027s buddy.\n\nSigned-off-by: Haifeng Li \u003comycle@gmail.com\u003e\nSigned-off-by: Gavin Shan \u003cshangw@linux.vnet.ibm.com\u003e\nReviewed-by: Michal Hocko \u003cmhocko@suse.cz\u003e\nCc: KyongHo Cho \u003cpullip.cho@samsung.com\u003e\nCc: Mel Gorman \u003cmgorman@suse.de\u003e\nCc: Minchan Kim \u003cminchan.kim@gmail.com\u003e\nCc: Johannes Weiner \u003cjweiner@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a4dd7e6c27a37237f09d437a515a3330093d4f70", "tree": "60a334631413fe36026f9d2dcb9090da1ee15728", "parents": [ "547ee164a63242ef14c41410615aa60aa164fce2" ], "author": { "name": "Dylan Reid", "email": "dgreid@chromium.org", "time": "Sat Sep 01 01:38:19 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:30:05 2012 -0700" }, "message": "ASoC: samsung dma - Don\u0027t indicate support for pause/resume.\n\ncommit 57b2d68863f281737d8596cb3d76d89d9cc54fd8 upstream.\n\nThe pause and resume operations indicate that the stream can be\nun-paused/resumed from the exact location they were paused/suspended.\nThis is not true for this driver, the pause and suspend triggers share\nthe same code path with stop, they flush all pending DMA transfers.\nThis drops all pending samples. The pause_release/resume triggers are\nthe same as start, except that prepare won\u0027t be called beforehand,\nnothing will be enqueued to the DMA engine and nothing will happen (no\naudio). Removing the pause flag will let apps know that it isn\u0027t\nsupported. Removing the resume flag will cause user space to call\nprepare and start instead of resume, so audio will continue playing when\nthe system wakes up.\n\nBefore removing the pause and resume flags, I tested this on an exynos\n5250, using \u0027aplay -i\u0027. Pause/un-pause leads to silence followed by a\nwrite error. Suspend/resume testing led to the same result. Removing\nthe two flags fixes suspend/resume (since snd_pcm_prepare is called\nagain). And leads to a proper reporting of pause not supported.\n\nSigned-off-by: Dylan Reid \u003cdgreid@chromium.org\u003e\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "547ee164a63242ef14c41410615aa60aa164fce2", "tree": "8cf97cd29fd887a7bf7f02353701b386cd61efe2", "parents": [ "9fd0132a29b4e40e5cf5ff82a02227b7f603bba7" ], "author": { "name": "Paul Clements", "email": "paul.clements@steeleye.com", "time": "Mon Sep 17 14:09:02 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:59 2012 -0700" }, "message": "nbd: clear waiting_queue on shutdown\n\ncommit fded4e090c60100d709318896c79816d68d5b47d upstream.\n\nFix a serious but uncommon bug in nbd which occurs when there is heavy\nI/O going to the nbd device while, at the same time, a failure (server,\nnetwork) or manual disconnect of the nbd connection occurs.\n\nThere is a small window between the time that the nbd_thread is stopped\nand the socket is shutdown where requests can continue to be queued to\nnbd\u0027s internal waiting_queue. When this happens, those requests are\nnever completed or freed.\n\nThe fix is to clear the waiting_queue on shutdown of the nbd device, in\nthe same way that the nbd request queue (queue_head) is already being\ncleared.\n\nSigned-off-by: Paul Clements \u003cpaul.clements@steeleye.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": "9fd0132a29b4e40e5cf5ff82a02227b7f603bba7", "tree": "8116196b1b2b4ec092a71a7a6f4feb59444ca028", "parents": [ "d765682ea82fb83fd8d01b7663f78b5d2f9fd839" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Sep 19 12:52:30 2012 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:55 2012 -0700" }, "message": "md/raid5: fix calculate of \u0027degraded\u0027 when a replacement becomes active.\n\ncommit e5c86471f933608db5d43679f84cb4346c32033e upstream.\n\nWhen a replacement device becomes active, we mark the device that it\nreplaces as \u0027faulty\u0027 so that it can subsequently get removed.\nHowever \u0027calc_degraded\u0027 only pays attention to the primary device, not\nthe replacement, so the array appears to become degraded, which is\nwrong.\n\nSo teach \u0027calc_degraded\u0027 to consider any replacement if a primary\ndevice is faulty.\n\nThis is suitable for -stable as an incorrect \u0027degraded\u0027 value can\nconfuse md and could lead to data corruption.\nThis is only relevant for 3.3 and later.\n\nReported-by: Robin Hill \u003crobin@robinhill.me.uk\u003e\nReported-by: John Drescher \u003cdrescherjm@gmail.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d765682ea82fb83fd8d01b7663f78b5d2f9fd839", "tree": "9fa4d0763768e38d8538a713202378df00f7dc51", "parents": [ "1c55a12c2a3d5b54598e7ba04e2d0fcf858b9023" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Sep 19 12:54:22 2012 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:55 2012 -0700" }, "message": "md: make sure metadata is updated when spares are activated or removed.\n\ncommit 6dafab6b1383e912cd252fa809570b484eb6e0dc upstream.\n\nIt isn\u0027t always necessary to update the metadata when spares are\nremoved as the presence-or-not of a spare isn\u0027t really important to\nthe integrity of an array.\nAlso activating a spare doesn\u0027t always require updating the metadata\nas the update on \u0027recovery-completed\u0027 is usually sufficient.\n\nHowever the introduction of \u0027replacement\u0027 devices have made these\ntransitions sometimes more important. For example the \u0027Replacement\u0027\nflag isn\u0027t cleared until the original device is removed, so we need\nto ensure a metadata update after that \u0027spare\u0027 is removed.\n\nSo set MD_CHANGE_DEVS whenever a spare is activated or removed, to\ncomplement the current situation where it is set when a spare is added\nor a device is failed (or a number of other less common situations).\n\nThis is suitable for -stable as out-of-data metadata could lead\nto data corruption.\nThis is only relevant for 3.3 and later 9when \u0027replacement\u0027 as\nintroduced.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1c55a12c2a3d5b54598e7ba04e2d0fcf858b9023", "tree": "754c39d7c113cbfe9ffdfd83c5db9b63f842726b", "parents": [ "dd8121960467e40388876403758334fa91516db2" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Aug 16 16:46:12 2012 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:55 2012 -0700" }, "message": "md: Don\u0027t truncate size at 4TB for RAID0 and Linear\n\ncommit 667a5313ecd7308d79629c0738b0db588b0b0a4e upstream.\n\ncommit 27a7b260f71439c40546b43588448faac01adb93\n md: Fix handling for devices from 2TB to 4TB in 0.90 metadata.\n\nchanged 0.90 metadata handling to truncated size to 4TB as that is\nall that 0.90 can record.\nHowever for RAID0 and Linear, 0.90 doesn\u0027t need to record the size, so\nthis truncation is not needed and causes working arrays to become too small.\n\nSo avoid the truncation for RAID0 and Linear\n\nThis bug was introduced in 3.1 and is suitable for any stable kernels\nfrom then onwards.\nAs the offending commit was tagged for \u0027stable\u0027, any stable kernel\nthat it was applied to should also get this patch. That includes\nat least 2.6.32, 2.6.33 and 3.0. (Thanks to Ben Hutchings for\nproviding that list).\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dd8121960467e40388876403758334fa91516db2", "tree": "77174d90183bdd6a1940490ef46da3c67c5b253f", "parents": [ "e3c9398035cbf79a2ab75c2f43de999fc9a726f4" ], "author": { "name": "Dmitry Kasatkin", "email": "dmitry.kasatkin@intel.com", "time": "Wed Sep 12 13:26:55 2012 +0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:55 2012 -0700" }, "message": "digsig: add hash size comparision on signature verification\n\ncommit bc01637a80f5b670bd70a0279d3f93fa8de1c96d upstream.\n\nWhen pkcs_1_v1_5_decode_emsa() returns without error and hash sizes do\nnot match, hash comparision is not done and digsig_verify_rsa() returns\nno error. This is a bug and this patch fixes it.\n\nThe bug was introduced in v3.3 by commit b35e286a640f (\"lib/digsig:\npkcs_1_v1_5_decode_emsa cleanup\").\n\nSigned-off-by: Dmitry Kasatkin \u003cdmitry.kasatkin@intel.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e3c9398035cbf79a2ab75c2f43de999fc9a726f4", "tree": "c23687b0b8b6b70ae462a07fd85c5395d7dc78ed", "parents": [ "cf499a04f9b5c8d2218257046b66b3062401673a" ], "author": { "name": "Mel Gorman", "email": "mgorman@suse.de", "time": "Sun Aug 19 14:41:03 2012 +1200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:55 2012 -0700" }, "message": "Redefine ATOMIC_INIT and ATOMIC64_INIT to drop the casts\n\ncommit 67a806d9499353fabd5b5ff07337f3aa88a1c3ba upstream.\n\nThe following build error occurred during an alpha build:\n\n net/core/sock.c:274:36: error: initializer element is not constant\n\nDave Anglin says:\n\u003e Here is the line in sock.i:\n\u003e\n\u003e struct static_key memalloc_socks \u003d ((struct static_key) { .enabled \u003d\n\u003e ((atomic_t) { (0) }) });\n\nThe above line contains two compound literals. It also uses a designated\ninitializer to initialize the field enabled. A compound literal is not a\nconstant expression.\n\nThe location of the above statement isn\u0027t fully clear, but if a compound\nliteral occurs outside the body of a function, the initializer list must\nconsist of constant expressions.\n\nSigned-off-by: Mel Gorman \u003cmgorman@suse.de\u003e\nSigned-off-by: Fengguang Wu \u003cfengguang.wu@intel.com\u003e\nSigned-off-by: Michael Cree \u003cmcree@orcon.net.nz\u003e\nAcked-by: Matt Turner \u003cmattst88@gmail.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cf499a04f9b5c8d2218257046b66b3062401673a", "tree": "9c9930f689aa9df537462aed2e08e423dd181a3a", "parents": [ "f0868b703758f19c2ced945c2c3fce1c151ab369" ], "author": { "name": "Bjørn Mork", "email": "bjorn@mork.no", "time": "Sun Sep 02 15:41:34 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:55 2012 -0700" }, "message": "kobject: fix oops with \"input0: bad kobj_uevent_env content in show_uevent()\"\n\ncommit 60e233a56609fd963c59e99bd75c663d63fa91b6 upstream.\n\nFengguang Wu \u003cfengguang.wu@intel.com\u003e writes:\n\n\u003e After the __devinit* removal series, I can still get kernel panic in\n\u003e show_uevent(). So there are more sources of bug..\n\u003e\n\u003e Debug patch:\n\u003e\n\u003e @@ -343,8 +343,11 @@ static ssize_t show_uevent(struct device\n\u003e goto out;\n\u003e\n\u003e /* copy keys to file */\n\u003e - for (i \u003d 0; i \u003c env-\u003eenvp_idx; i++)\n\u003e + dev_err(dev, \"uevent %d env[%d]: %s/.../%s\\n\", env-\u003ebuflen, env-\u003eenvp_idx, top_kobj-\u003ename, dev-\u003ekobj.name);\n\u003e + for (i \u003d 0; i \u003c env-\u003eenvp_idx; i++) {\n\u003e + printk(KERN_ERR \"uevent %d env[%d]: %s\\n\", (int)count, i, env-\u003eenvp[i]);\n\u003e count +\u003d sprintf(\u0026buf[count], \"%s\\n\", env-\u003eenvp[i]);\n\u003e + }\n\u003e\n\u003e Oops message, the env[] is again not properly initilized:\n\u003e\n\u003e [ 44.068623] input input0: uevent 61 env[805306368]: input0/.../input0\n\u003e [ 44.069552] uevent 0 env[0]: (null)\n\nThis is a completely different CONFIG_HOTPLUG problem, only\ndemonstrating another reason why CONFIG_HOTPLUG should go away. I had a\nhard time trying to disable it anyway ;-)\n\nThe problem this time is lots of code assuming that a call to\nadd_uevent_var() will guarantee that env-\u003ebuflen \u003e 0. This is not true\nif CONFIG_HOTPLUG is unset. So things like this end up overwriting\nenv-\u003eenvp_idx because the array index is -1:\n\n\tif (add_uevent_var(env, \"MODALIAS\u003d\"))\n\t\treturn -ENOMEM;\n len \u003d input_print_modalias(\u0026env-\u003ebuf[env-\u003ebuflen - 1],\n\t\t\t\t sizeof(env-\u003ebuf) - env-\u003ebuflen,\n\t\t\t\t dev, 0);\n\nDon\u0027t know what the best action is, given that there seem to be a *lot*\nof this around the kernel. This patch \"fixes\" the problem for me, but I\ndon\u0027t know if it can be considered an appropriate fix.\n\n[ It is the correct fix for now, for 3.7 forcing CONFIG_HOTPLUG to\nalways be on is the longterm fix, but it\u0027s too late for 3.6 and older\nkernels to resolve this that way - gregkh ]\n\nReported-by: Fengguang Wu \u003cfengguang.wu@intel.com\u003e\nSigned-off-by: Bjørn Mork \u003cbjorn@mork.no\u003e\nTested-by: Fengguang Wu \u003cfengguang.wu@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f0868b703758f19c2ced945c2c3fce1c151ab369", "tree": "5d38447a48c5cde6c57c42e9b4a893044ffeb234", "parents": [ "93ee70835a254181a9d9c5750e9301b70899ad90" ], "author": { "name": "Alan Cox", "email": "alan@linux.intel.com", "time": "Tue Sep 04 16:07:18 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:55 2012 -0700" }, "message": "ahci: Add alternate identifier for the 88SE9172\n\ncommit 17c60c6b763cb5b83b0185e7d38d01d18e55a05a upstream.\n\nThis can also appear as 0x9192. Reported in bugzilla and confirmed with the\nboard documentation for these boards.\n\nResolves-bug: https://bugzilla.kernel.org/show_bug.cgi?id\u003d42970\nSigned-off-by: Alan Cox \u003calan@linux.intel.com\u003e\nSigned-off-by: Jeff Garzik \u003cjgarzik@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "93ee70835a254181a9d9c5750e9301b70899ad90", "tree": "e6b82ddb5bf1ce512d86a7c5c9afe84629743809", "parents": [ "d409354d1b8a1e47b8f29887179949ec951ffe83" ], "author": { "name": "Robert Richter", "email": "robert.richter@amd.com", "time": "Thu Jul 19 18:28:26 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:55 2012 -0700" }, "message": "oprofile, s390: Fix uninitialized memory access when writing to oprofilefs\n\ncommit 81ff3478d9ba7f0b48b0abef740e542fd83adf79 upstream.\n\nIf oprofilefs_ulong_from_user() is called with count equals zero, *val\nremains unchanged. Depending on the implementation it might be\nuninitialized. Fixing users of oprofilefs_ulong_ from_user().\n\nWe missed these s390 changes with:\n\n 913050b oprofile: Fix uninitialized memory access when writing to writing to oprofilefs\n\nSigned-off-by: Robert Richter \u003crobert.richter@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d409354d1b8a1e47b8f29887179949ec951ffe83", "tree": "a60384b71bacbc43d1dc3b1a5136b1e7a8ebc99f", "parents": [ "e66a381518f9ebf98cdc583d20ae706aa5d1dc28" ], "author": { "name": "Ian Chen", "email": "ian.cy.chen@samsung.com", "time": "Wed Aug 29 15:05:36 2012 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:54 2012 -0700" }, "message": "mmc: card: Skip secure erase on MoviNAND; causes unrecoverable corruption.\n\ncommit 3550ccdb9d8d350e526b809bf3dd92b550a74fe1 upstream.\n\nFor several MoviNAND eMMC parts, there are known issues with secure\nerase and secure trim. For these specific MoviNAND devices, we skip\nthese operations.\n\nSpecifically, there is a bug in the eMMC firmware that causes\nunrecoverable corruption when the MMC is erased with MMC_CAP_ERASE\nenabled.\n\nReferences:\n\nhttp://forum.xda-developers.com/showthread.php?t\u003d1644364\nhttps://plus.google.com/111398485184813224730/posts/21pTYfTsCkB#111398485184813224730/posts/21pTYfTsCkB\n\nSigned-off-by: Ian Chen \u003cian.cy.chen@samsung.com\u003e\nReviewed-by: Namjae Jeon \u003clinkinjeon@gmail.com\u003e\nAcked-by: Jaehoon Chung \u003cjh80.chung@samsung.com\u003e\nReviewed-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\nSigned-off-by: Chris Ball \u003ccjb@laptop.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e66a381518f9ebf98cdc583d20ae706aa5d1dc28", "tree": "ad4e03d6137580beaeabd4ae5cd18ffc276bd806", "parents": [ "3a4781e12d0e6264c76bfd110783321450138169" ], "author": { "name": "Shawn Guo", "email": "shawn.guo@linaro.org", "time": "Wed Aug 22 23:10:01 2012 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:54 2012 -0700" }, "message": "mmc: sdhci-esdhc: break out early if clock is 0\n\ncommit 74f330bceaa7b88d06062e1cac3d519a3dfc041e upstream.\n\nSince commit 30832ab56 (\"mmc: sdhci: Always pass clock request value\nzero to set_clock host op\") was merged, esdhc_set_clock starts hitting\n\"if (clock \u003d\u003d 0)\" where ESDHC_SYSTEM_CONTROL has been operated. This\ncauses SDHCI card-detection function being broken. Fix the regression\nby moving \"if (clock \u003d\u003d 0)\" above ESDHC_SYSTEM_CONTROL operation.\n\nSigned-off-by: Shawn Guo \u003cshawn.guo@linaro.org\u003e\nSigned-off-by: Chris Ball \u003ccjb@laptop.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3a4781e12d0e6264c76bfd110783321450138169", "tree": "70dc5ecbb2fbf646a868091c97844a4ac0e3b4ca", "parents": [ "8889866c58f77c557e79a30853ee4fd5f50780ef" ], "author": { "name": "Lauri Hintsala", "email": "lauri.hintsala@bluegiga.com", "time": "Tue Jul 17 17:16:09 2012 +0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:54 2012 -0700" }, "message": "mmc: mxs-mmc: fix deadlock in SDIO IRQ case\n\ncommit 1af36b2a993dddfa3d6860ec4879c9e8abc9b976 upstream.\n\nRelease the lock before mmc_signal_sdio_irq is called by mxs_mmc_irq_handler.\n\nBacktrace:\n[ 79.660000] \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[ 79.660000] [ INFO: possible recursive locking detected ]\n[ 79.660000] 3.4.0-00009-g3e96082-dirty #11 Not tainted\n[ 79.660000] ---------------------------------------------\n[ 79.660000] swapper/0 is trying to acquire lock:\n[ 79.660000] (\u0026(\u0026host-\u003elock)-\u003erlock#2){-.....}, at: [\u003cc026ea3c\u003e] mxs_mmc_enable_sdio_irq+0x18/0xd4\n[ 79.660000]\n[ 79.660000] but task is already holding lock:\n[ 79.660000] (\u0026(\u0026host-\u003elock)-\u003erlock#2){-.....}, at: [\u003cc026f744\u003e] mxs_mmc_irq_handler+0x1c/0xe8\n[ 79.660000]\n[ 79.660000] other info that might help us debug this:\n[ 79.660000] Possible unsafe locking scenario:\n[ 79.660000]\n[ 79.660000] CPU0\n[ 79.660000] ----\n[ 79.660000] lock(\u0026(\u0026host-\u003elock)-\u003erlock#2);\n[ 79.660000] lock(\u0026(\u0026host-\u003elock)-\u003erlock#2);\n[ 79.660000]\n[ 79.660000] *** DEADLOCK ***\n[ 79.660000]\n[ 79.660000] May be due to missing lock nesting notation\n[ 79.660000]\n[ 79.660000] 1 lock held by swapper/0:\n[ 79.660000] #0: (\u0026(\u0026host-\u003elock)-\u003erlock#2){-.....}, at: [\u003cc026f744\u003e] mxs_mmc_irq_handler+0x1c/0xe8\n[ 79.660000]\n[ 79.660000] stack backtrace:\n[ 79.660000] [\u003cc0014bd0\u003e] (unwind_backtrace+0x0/0xf4) from [\u003cc005f9c0\u003e] (__lock_acquire+0x1948/0x1d48)\n[ 79.660000] [\u003cc005f9c0\u003e] (__lock_acquire+0x1948/0x1d48) from [\u003cc005fea0\u003e] (lock_acquire+0xe0/0xf8)\n[ 79.660000] [\u003cc005fea0\u003e] (lock_acquire+0xe0/0xf8) from [\u003cc03a8460\u003e] (_raw_spin_lock_irqsave+0x44/0x58)\n[ 79.660000] [\u003cc03a8460\u003e] (_raw_spin_lock_irqsave+0x44/0x58) from [\u003cc026ea3c\u003e] (mxs_mmc_enable_sdio_irq+0x18/0xd4)\n[ 79.660000] [\u003cc026ea3c\u003e] (mxs_mmc_enable_sdio_irq+0x18/0xd4) from [\u003cc026f7fc\u003e] (mxs_mmc_irq_handler+0xd4/0xe8)\n[ 79.660000] [\u003cc026f7fc\u003e] (mxs_mmc_irq_handler+0xd4/0xe8) from [\u003cc006bdd8\u003e] (handle_irq_event_percpu+0x70/0x254)\n[ 79.660000] [\u003cc006bdd8\u003e] (handle_irq_event_percpu+0x70/0x254) from [\u003cc006bff8\u003e] (handle_irq_event+0x3c/0x5c)\n[ 79.660000] [\u003cc006bff8\u003e] (handle_irq_event+0x3c/0x5c) from [\u003cc006e6d0\u003e] (handle_level_irq+0x90/0x110)\n[ 79.660000] [\u003cc006e6d0\u003e] (handle_level_irq+0x90/0x110) from [\u003cc006b930\u003e] (generic_handle_irq+0x38/0x50)\n[ 79.660000] [\u003cc006b930\u003e] (generic_handle_irq+0x38/0x50) from [\u003cc00102fc\u003e] (handle_IRQ+0x30/0x84)\n[ 79.660000] [\u003cc00102fc\u003e] (handle_IRQ+0x30/0x84) from [\u003cc000f058\u003e] (__irq_svc+0x38/0x60)\n[ 79.660000] [\u003cc000f058\u003e] (__irq_svc+0x38/0x60) from [\u003cc0010520\u003e] (default_idle+0x2c/0x40)\n[ 79.660000] [\u003cc0010520\u003e] (default_idle+0x2c/0x40) from [\u003cc0010a90\u003e] (cpu_idle+0x64/0xcc)\n[ 79.660000] [\u003cc0010a90\u003e] (cpu_idle+0x64/0xcc) from [\u003cc04ff858\u003e] (start_kernel+0x244/0x2c8)\n[ 79.660000] BUG: spinlock lockup on CPU#0, swapper/0\n[ 79.660000] lock: c398cb2c, .magic: dead4ead, .owner: swapper/0, .owner_cpu: 0\n[ 79.660000] [\u003cc0014bd0\u003e] (unwind_backtrace+0x0/0xf4) from [\u003cc01ddb1c\u003e] (do_raw_spin_lock+0xf0/0x144)\n[ 79.660000] [\u003cc01ddb1c\u003e] (do_raw_spin_lock+0xf0/0x144) from [\u003cc03a8468\u003e] (_raw_spin_lock_irqsave+0x4c/0x58)\n[ 79.660000] [\u003cc03a8468\u003e] (_raw_spin_lock_irqsave+0x4c/0x58) from [\u003cc026ea3c\u003e] (mxs_mmc_enable_sdio_irq+0x18/0xd4)\n[ 79.660000] [\u003cc026ea3c\u003e] (mxs_mmc_enable_sdio_irq+0x18/0xd4) from [\u003cc026f7fc\u003e] (mxs_mmc_irq_handler+0xd4/0xe8)\n[ 79.660000] [\u003cc026f7fc\u003e] (mxs_mmc_irq_handler+0xd4/0xe8) from [\u003cc006bdd8\u003e] (handle_irq_event_percpu+0x70/0x254)\n[ 79.660000] [\u003cc006bdd8\u003e] (handle_irq_event_percpu+0x70/0x254) from [\u003cc006bff8\u003e] (handle_irq_event+0x3c/0x5c)\n[ 79.660000] [\u003cc006bff8\u003e] (handle_irq_event+0x3c/0x5c) from [\u003cc006e6d0\u003e] (handle_level_irq+0x90/0x110)\n[ 79.660000] [\u003cc006e6d0\u003e] (handle_level_irq+0x90/0x110) from [\u003cc006b930\u003e] (generic_handle_irq+0x38/0x50)\n[ 79.660000] [\u003cc006b930\u003e] (generic_handle_irq+0x38/0x50) from [\u003cc00102fc\u003e] (handle_IRQ+0x30/0x84)\n[ 79.660000] [\u003cc00102fc\u003e] (handle_IRQ+0x30/0x84) from [\u003cc000f058\u003e] (__irq_svc+0x38/0x60)\n[ 79.660000] [\u003cc000f058\u003e] (__irq_svc+0x38/0x60) from [\u003cc0010520\u003e] (default_idle+0x2c/0x40)\n[ 79.660000] [\u003cc0010520\u003e] (default_idle+0x2c/0x40) from [\u003cc0010a90\u003e] (cpu_idle+0x64/0xcc)\n[ 79.660000] [\u003cc0010a90\u003e] (cpu_idle+0x64/0xcc) from [\u003cc04ff858\u003e] (start_kernel+0x244/0x2c8)\n\nSigned-off-by: Lauri Hintsala \u003clauri.hintsala@bluegiga.com\u003e\nAcked-by: Shawn Guo \u003cshawn.guo@linaro.org\u003e\nSigned-off-by: Chris Ball \u003ccjb@laptop.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8889866c58f77c557e79a30853ee4fd5f50780ef", "tree": "146d3318c16e56410bebfaabcb5f467456c9d0cc", "parents": [ "2bafdfd612901af70fcea3cf1866e388eb68fdf0" ], "author": { "name": "Aaron Lu", "email": "aaron.lu@intel.com", "time": "Fri Sep 14 20:54:44 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:54 2012 -0700" }, "message": "ACPI / PM: Use KERN_DEBUG when no power resources are found\n\ncommit f25b70613c048ceb1df052576fda03321ebf41cf upstream.\n\ncommit a606dac368eed5696fb38e16b1394f1d049c09e9 adds support to link\ndevices which have _PRx, if a device does not have _PRx, a warning\nmessage will be printed.\n\nThis commit is for ZPODD on Intel ZPODD capable platforms, on other\nplatforms, it has no problem if there is no power resource for this\ndevice, so a warning here is not appropriate, change it to debug.\n\nReported-by: Borislav Petkov \u003cbp@amd64.org\u003e\nSigned-off-by: Aaron Lu \u003caaron.lu@intel.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crjw@sisk.pl\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "2bafdfd612901af70fcea3cf1866e388eb68fdf0", "tree": "d50736c004862e015bad8b8fa5079535d15dff05", "parents": [ "d156b47c4242843096e4a13f8ace5a0626bde3e9" ], "author": { "name": "Lin Ming", "email": "ming.m.lin@intel.com", "time": "Fri Sep 14 00:26:33 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:54 2012 -0700" }, "message": "ACPI / PM: Fix resource_lock dead lock in acpi_power_on_device\n\ncommit 40bf66ec9791f1452b90b82aadc3b6e6aee201f5 upstream.\n\nCommit 0090def(\"ACPI: Add interface to register/unregister device\nto/from power resources\") used resource_lock to protect the devices list\nthat relies on power resource. It caused a mutex dead lock, as below\n\n acpi_power_on ---\u003e lock resource_lock\n __acpi_power_on\n acpi_power_on_device\n acpi_power_get_inferred_state\n acpi_power_get_list_state ---\u003e lock resource_lock\n\nThis patch adds a new mutex \"devices_lock\" to protect the devices list\nand calls acpi_power_on_device in acpi_power_on, instead of\n__acpi_power_on, after the resource_lock is released.\n\n[rjw: Changed data type of a boolean variable to bool.]\n\nSigned-off-by: Lin Ming \u003cming.m.lin@intel.com\u003e\nSigned-off-by: Aaron Lu \u003caaron.lu@intel.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crjw@sisk.pl\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d156b47c4242843096e4a13f8ace5a0626bde3e9", "tree": "517ce331697fce4a5aadba64df99919e60235c53", "parents": [ "9b52a3b313497af37dcdba4ba4c0c95809db525c" ], "author": { "name": "Al Viro", "email": "viro@ZenIV.linux.org.uk", "time": "Mon Aug 20 14:59:25 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:54 2012 -0700" }, "message": "perf_event: Switch to internal refcount, fix race with close()\n\ncommit a6fa941d94b411bbd2b6421ffbde6db3c93e65ab upstream.\n\nDon\u0027t mess with file refcounts (or keep a reference to file, for\nthat matter) in perf_event. Use explicit refcount of its own\ninstead. Deal with the race between the final reference to event\ngoing away and new children getting created for it by use of\natomic_long_inc_not_zero() in inherit_event(); just have the\nlatter free what it had allocated and return NULL, that works\nout just fine (children of siblings of something doomed are\ncreated as singletons, same as if the child of leader had been\ncreated and immediately killed).\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nSigned-off-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nLink: http://lkml.kernel.org/r/20120820135925.GG23464@ZenIV.linux.org.uk\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9b52a3b313497af37dcdba4ba4c0c95809db525c", "tree": "2576701b4d08c2a0b7bfcf332073c1a5328549ee", "parents": [ "2ad98b042313307859bf2f332b95b6588ec0ba0d" ], "author": { "name": "Stephen Warren", "email": "swarren@nvidia.com", "time": "Fri Aug 24 21:20:15 2012 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:54 2012 -0700" }, "message": "sound: tegra_alc5632: remove HP detect GPIO inversion\n\ncommit c921928661eda599d73a6a86e58bdd5aecfa18cb upstream.\n\nBoth the schematics and practical testing show that the HP detect GPIO\nis high when the headphones are plugged in. Hence, the snd_soc_jack_gpio\nshould not specify to invert the signal.\n\nSigned-off-by: Stephen Warren \u003cswarren@nvidia.com\u003e\nAcked-by: Andrey Danin \u003cdanindrey@mail.ru\u003e\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "2ad98b042313307859bf2f332b95b6588ec0ba0d", "tree": "8772277f0ac4100b5c77d5c8361f595f391c423c", "parents": [ "125c4c2a41ac9249b54602db68b81a5ad398bbb7" ], "author": { "name": "Francesco Ruggeri", "email": "fruggeri@aristanetworks.com", "time": "Thu Sep 13 15:03:37 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:54 2012 -0700" }, "message": "fs/proc: fix potential unregister_sysctl_table hang\n\ncommit 6bf6104573482570f7103d3e5ddf9574db43a363 upstream.\n\nThe unregister_sysctl_table() function hangs if all references to its\nctl_table_header structure are not dropped.\n\nThis can happen sometimes because of a leak in proc_sys_lookup():\nproc_sys_lookup() gets a reference to the table via lookup_entry(), but\nit does not release it when a subsequent call to sysctl_follow_link()\nfails.\n\nThis patch fixes this leak by making sure the reference is always\ndropped on return.\n\nSee also commit 076c3eed2c31 (\"sysctl: Rewrite proc_sys_lookup\nintroducing find_entry and lookup_entry\") which reorganized this code in\n3.4.\n\nTested in Linux 3.4.4.\n\nSigned-off-by: Francesco Ruggeri \u003cfruggeri@aristanetworks.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "125c4c2a41ac9249b54602db68b81a5ad398bbb7", "tree": "2ff18e7064855d413fcc87486768b72534f36ff1", "parents": [ "8ef2b61115a3baeb3dc60782af32a3f6c46ed7a4" ], "author": { "name": "Bjørn Mork", "email": "bjorn@mork.no", "time": "Tue Sep 11 09:40:31 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:53 2012 -0700" }, "message": "USB: option: replace ZTE K5006-Z entry with vendor class rule\n\ncommit ba9edaa468869a8cea242a411066b0f490751798 upstream.\n\nFix the ZTE K5006-Z entry so that it actually matches anything\n\n commit f1b5c997 USB: option: add ZTE K5006-Z\n\nadded a device specific entry assuming that the device would use\nclass/subclass/proto \u003d\u003d ff/ff/ff like other ZTE devices. It\nturns out that ZTE has started using vendor specific subclass\nand protocol codes:\n\nT: Bus\u003d01 Lev\u003d01 Prnt\u003d01 Port\u003d03 Cnt\u003d01 Dev#\u003d 4 Spd\u003d480 MxCh\u003d 0\nD: Ver\u003d 2.00 Cls\u003d00(\u003eifc ) Sub\u003d00 Prot\u003d00 MxPS\u003d64 #Cfgs\u003d 1\nP: Vendor\u003d19d2 ProdID\u003d1018 Rev\u003d 0.00\nS: Manufacturer\u003dZTE,Incorporated\nS: Product\u003dZTE LTE Technologies MSM\nS: SerialNumber\u003dMF821Vxxxxxxx\nC:* #Ifs\u003d 5 Cfg#\u003d 1 Atr\u003dc0 MxPwr\u003d500mA\nI:* If#\u003d 0 Alt\u003d 0 #EPs\u003d 2 Cls\u003dff(vend.) Sub\u003d86 Prot\u003d10 Driver\u003d(none)\nE: Ad\u003d81(I) Atr\u003d02(Bulk) MxPS\u003d 512 Ivl\u003d0ms\nE: Ad\u003d01(O) Atr\u003d02(Bulk) MxPS\u003d 512 Ivl\u003d4ms\nI:* If#\u003d 1 Alt\u003d 0 #EPs\u003d 2 Cls\u003dff(vend.) Sub\u003d02 Prot\u003d05 Driver\u003d(none)\nE: Ad\u003d82(I) Atr\u003d02(Bulk) MxPS\u003d 512 Ivl\u003d0ms\nE: Ad\u003d02(O) Atr\u003d02(Bulk) MxPS\u003d 512 Ivl\u003d4ms\nI:* If#\u003d 2 Alt\u003d 0 #EPs\u003d 3 Cls\u003dff(vend.) Sub\u003d02 Prot\u003d01 Driver\u003d(none)\nE: Ad\u003d83(I) Atr\u003d03(Int.) MxPS\u003d 64 Ivl\u003d2ms\nE: Ad\u003d84(I) Atr\u003d02(Bulk) MxPS\u003d 512 Ivl\u003d0ms\nE: Ad\u003d03(O) Atr\u003d02(Bulk) MxPS\u003d 512 Ivl\u003d4ms\nI:* If#\u003d 3 Alt\u003d 0 #EPs\u003d 3 Cls\u003dff(vend.) Sub\u003d06 Prot\u003d00 Driver\u003dqmi_wwan\nE: Ad\u003d85(I) Atr\u003d03(Int.) MxPS\u003d 64 Ivl\u003d2ms\nE: Ad\u003d86(I) Atr\u003d02(Bulk) MxPS\u003d 512 Ivl\u003d0ms\nE: Ad\u003d04(O) Atr\u003d02(Bulk) MxPS\u003d 512 Ivl\u003d4ms\nI:* If#\u003d 4 Alt\u003d 0 #EPs\u003d 2 Cls\u003d08(stor.) Sub\u003d06 Prot\u003d50 Driver\u003dusb-storage\nE: Ad\u003d05(O) Atr\u003d02(Bulk) MxPS\u003d 512 Ivl\u003d0ms\nE: Ad\u003d87(I) Atr\u003d02(Bulk) MxPS\u003d 512 Ivl\u003d0ms\n\nWe do not have any information on how ZTE intend to use these\ncodes, but let us assume for now that the 3 sets matching\nserial functions in the K5006-Z always will identify a serial\nfunction in a ZTE device.\n\nCc: Thomas Schäfer \u003ctschaefer@t-online.de\u003e\nSigned-off-by: Bjørn Mork \u003cbjorn@mork.no\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8ef2b61115a3baeb3dc60782af32a3f6c46ed7a4", "tree": "0a7f06d0378aec65f5fe04b9073cf860cafbbc0c", "parents": [ "8fae345eec6e2fff49e634b108f3318d88205c6c" ], "author": { "name": "Ian Abbott", "email": "abbotti@mev.co.uk", "time": "Fri Aug 31 20:41:30 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:53 2012 -0700" }, "message": "staging: comedi: das08: Correct AO output for das08jr-16-ao\n\ncommit 61ed59ed09e6ad2b8395178ea5ad5f653bba08e3 upstream.\n\nDon\u0027t zero out bits 15..12 of the data value in `das08jr_ao_winsn()` as\nthat knobbles the upper three-quarters of the output range for the\n\u0027das08jr-16-ao\u0027 board.\n\nSigned-off-by: Ian Abbott \u003cabbotti@mev.co.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8fae345eec6e2fff49e634b108f3318d88205c6c", "tree": "85508930f8bb9910acf6afc3cd30afd4c0a8cb23", "parents": [ "191ee4172f0a89b85ce1daad00d88f33b66e07e6" ], "author": { "name": "Eric Dumazet", "email": "edumazet@google.com", "time": "Mon Sep 10 21:22:11 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:53 2012 -0700" }, "message": "staging: r8712u: fix bug in r8712_recv_indicatepkt()\n\ncommit abf02cfc179bb4bd30d05f582d61b3b8f429b813 upstream.\n\n64bit arches have a buggy r8712u driver, let\u0027s fix it.\n\nskb-\u003etail must be set properly or network stack behavior is undefined.\n\nAddresses https://bugzilla.redhat.com/show_bug.cgi?id\u003d847525\nAddresses https://bugzilla.kernel.org/show_bug.cgi?id\u003d45071\n\nSigned-off-by: Eric Dumazet \u003cedumazet@google.com\u003e\nCc: Dave Jones \u003cdavej@redhat.com\u003e\nAcked-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "191ee4172f0a89b85ce1daad00d88f33b66e07e6", "tree": "bd2ed5e7c41e3dd1a08f3c478402e1623dfbb76b", "parents": [ "6d4960ed8247d763e9022bda9f068fec7000af3f" ], "author": { "name": "Malcolm Priestley", "email": "tvboxspy@gmail.com", "time": "Wed Aug 29 23:08:21 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:53 2012 -0700" }, "message": "staging: vt6656: [BUG] - Failed connection, incorrect endian.\n\ncommit aa209eef3ce8419ff2926c2fa944dfbfb5afbacb upstream.\n\nHi,\n\nThis patch fixes a bug with driver failing to negotiate a connection.\n\nThe bug was traced to commit\n203e4615ee9d9fa8d3506b9d0ef30095e4d5bc90\nstaging: vt6656: removed custom definitions of Ethernet packet types\n\nIn that patch, definitions in include/linux/if_ether.h replaced ones\nin tether.h which had both big and little endian definitions.\n\ninclude/linux/if_ether.h only refers to big endian values, cpu_to_be16\nshould be used for the correct endian architectures.\n\nSigned-off-by: Malcolm Priestley \u003ctvboxspy@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6d4960ed8247d763e9022bda9f068fec7000af3f", "tree": "f23658c6bfd97bf4f53503e5b838a67fc3564d1d", "parents": [ "18e64a0a0dfc533ab56f7aa198316b4ea11adca9" ], "author": { "name": "Seth Jennings", "email": "sjenning@linux.vnet.ibm.com", "time": "Wed Aug 29 16:58:45 2012 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:53 2012 -0700" }, "message": "staging: zcache: fix cleancache race condition with shrinker\n\ncommit 6d7d9798ad5c97ee4e911dd070dc12dc5ae55bd0 upstream.\n\nThis patch fixes a race condition that results in memory\ncorruption when using cleancache.\n\nThe race exists between the zcache shrinker handler,\nshrink_zcache_memory() and cleancache_get_page().\n\nIn most cases, the shrinker will both evict a zbpg\nfrom its buddy list and flush it from tmem before a\ncleancache_get_page() occurs on that page. A subsequent\ncleancache_get_page() will fail in the tmem layer.\n\nIn the rare case that two occur together and the\ncleancache_get_page() path gets through the tmem\nlayer before the shrinker path can flush tmem,\nzbud_decompress() does a check to see if the zbpg is a\n\"zombie\", i.e. not on a buddy list, which means the shrinker\nis in the process of reclaiming it. If the zbpg is a zombie,\nzbud_decompress() returns -EINVAL.\n\nHowever, this return code is being ignored by the caller,\nzcache_pampd_get_data_and_free(), which results in the\ncaller of cleancache_get_page() thinking that the page has\nbeen properly retrieved when it has not.\n\nThis patch modifies zcache_pampd_get_data_and_free() to\nconvey the failure up the stack so that the caller of\ncleancache_get_page() knows the page retrieval failed.\n\nThis needs to be applied to stable trees as well.\nzcache-main.c was named zcache.c before v3.1, so\nI\u0027m not sure how you want to handle trees earlier\nthan that.\n\nSigned-off-by: Seth Jennings \u003csjenning@linux.vnet.ibm.com\u003e\nReviewed-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nReviewed-by: Minchan Kim \u003cminchan@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "18e64a0a0dfc533ab56f7aa198316b4ea11adca9", "tree": "b7af8794c1108431d73d8d135ee078584c35f56c", "parents": [ "4386363312d70a764a376f1635467bab8e26965a" ], "author": { "name": "Christopher Brannon", "email": "chris@the-brannons.com", "time": "Sat Jun 16 16:55:20 2012 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:53 2012 -0700" }, "message": "Staging: speakup: fix an improperly-declared variable.\n\ncommit 4ea418b8b2fa8a70d0fcc8231b65e67b3a72984b upstream.\n\nA local static variable was declared as a pointer to a string\nconstant. We\u0027re assigning to the underlying memory, so it\nneeds to be an array instead.\n\nSigned-off-by: Christopher Brannon \u003cchris@the-brannons.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "4386363312d70a764a376f1635467bab8e26965a", "tree": "b360c64e05b9eac54eb2c3690296ef7a114f19b0", "parents": [ "23b5a5da4f07b887adce9b42daa7aa14a72a5427" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Thu Sep 20 07:44:11 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:53 2012 -0700" }, "message": "ALSA: hda - Workaround for silent output on VAIO Z with ALC889\n\ncommit e427c2375646789ecd0ccaef1a1e41458559ab2d upstream.\n\nOn recent kernels, Realtek codec parser tries to optimize the routing\naggressively and take the headphone output as primary at first. This\ncaused a regression on VAIO Z with ALC889, the silent output from the\nspeaker.\n\nThe problem seems that the speaker pin must be connected to the first\nDAC (0x02) on this machine by some reason although the codec itself\nadvertises the flexible routing with any DACs.\n\nThis patch adds a fix-up for choosing the speaker pin as the primary\nso that the right DAC is assigned on this device.\n\nReported-and-tested-by: Adam Williamson \u003cawilliam@redhat.com\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "23b5a5da4f07b887adce9b42daa7aa14a72a5427", "tree": "ab71e62372d5c69bb7955185e2007a0363dcb322", "parents": [ "6172ace501d10b1c629c5e82af26d0b87773c1ef" ], "author": { "name": "Matteo Frigo", "email": "athena@fftw.org", "time": "Wed Sep 12 10:12:06 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:52 2012 -0700" }, "message": "ALSA: ice1724: Use linear scale for AK4396 volume control.\n\ncommit 3737e2be505d872bf2b3c1cd4151b2d2b413d7b5 upstream.\n\nThe AK4396 DAC has a linear-scale attentuator, but\nsound/pci/ice1712/prodigy_hifi.c used a log scale instead, which is\nnot quite right. This patch restores the correct scale, borrowing\nfrom the ak4396 code in sound/pci/oxygen/oxygen.c.\n\nSigned-off-by: Matteo Frigo \u003cathena@fftw.org\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6172ace501d10b1c629c5e82af26d0b87773c1ef", "tree": "68b4b4f08d6058aebe094dd37318e94e56e647a8", "parents": [ "68983b9dae341fbca6b74be02248adb86e105818" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Mon Sep 10 09:39:31 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:52 2012 -0700" }, "message": "ALSA: hda - Fix Oops at codec reset/reconfig\n\ncommit 07dc59f0988cb54fd87bd373b3b27eb2401dd811 upstream.\n\nsnd_hda_codec_reset() calls restore_pincfgs() where the codec is\npowered up again, which eventually tries to resume and initialize via\nthe callbacks of the codec. However, it\u0027s the place just after codec\nfree callback, thus no codec callbacks should be called after that.\nOn a codec like CS4206, it results in Oops due to the access in init\ncallback.\n\nThis patch fixes the issue by clearing the codec callbacks properly\nafter freeing codec.\n\nReported-by: Daniel J Blueman \u003cdaniel@quora.org\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "68983b9dae341fbca6b74be02248adb86e105818", "tree": "81f39bfbe6e7862917882f2b791dc01f247cd8e1", "parents": [ "4dbbba47b19e4e2902a3b5115569e97c210c3297" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Thu Sep 06 10:10:11 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:52 2012 -0700" }, "message": "ALSA: hda - Fix missing Master volume for STAC9200/925x\n\ncommit ab548d2dba63ba947287965e525cc02a15d9853d upstream.\n\nWith the commit [2faa3bf: ALSA: hda - Rewrite the mute-LED hook with\nvmaster hook in patch_sigmatel.c], the former Master volume control\nwas converted to PCM. This was supposed to be covered by the vmaster\ncontrol. But due to the lack of \"PCM\" slave definition, this didn\u0027t\nhappen properly. The patch fixes the missing entry.\n\nReported-by: Andrew Shadura \u003cbugzilla@tut.by\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "4dbbba47b19e4e2902a3b5115569e97c210c3297", "tree": "622c4ac59d1b207960911cad5e0aa9f5eefb6d88", "parents": [ "6252fbdc0a40c20a21b24d7bfccf3c08ea9b10dc" ], "author": { "name": "Russell King", "email": "rmk+kernel@arm.linux.org.uk", "time": "Sat Aug 25 09:03:15 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:52 2012 -0700" }, "message": "ARM: Fix ioremap() of address zero\n\ncommit a849088aa1552b1a28eea3daff599ee22a734ae3 upstream.\n\nMurali Nalajala reports a regression that ioremapping address zero\nresults in an oops dump:\n\nUnable to handle kernel paging request at virtual address fa200000\npgd \u003d d4f80000\n[fa200000] *pgd\u003d00000000\nInternal error: Oops: 5 [#1] PREEMPT SMP ARM\nModules linked in:\nCPU: 0 Tainted: G W (3.4.0-g3b5f728-00009-g638207a #13)\nPC is at msm_pm_config_rst_vector_before_pc+0x8/0x30\nLR is at msm_pm_boot_config_before_pc+0x18/0x20\npc : [\u003cc0078f84\u003e] lr : [\u003cc007903c\u003e] psr: a0000093\nsp : c0837ef0 ip : cfe00000 fp : 0000000d\nr10: da7efc17 r9 : 225c4278 r8 : 00000006\nr7 : 0003c000 r6 : c085c824 r5 : 00000001 r4 : fa101000\nr3 : fa200000 r2 : c095080c r1 : 002250fc r0 : 00000000\nFlags: NzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel\nControl: 10c5387d Table: 25180059 DAC: 00000015\n[\u003cc0078f84\u003e] (msm_pm_config_rst_vector_before_pc+0x8/0x30) from [\u003cc007903c\u003e] (msm_pm_boot_config_before_pc+0x18/0x20)\n[\u003cc007903c\u003e] (msm_pm_boot_config_before_pc+0x18/0x20) from [\u003cc007a55c\u003e] (msm_pm_power_collapse+0x410/0xb04)\n[\u003cc007a55c\u003e] (msm_pm_power_collapse+0x410/0xb04) from [\u003cc007b17c\u003e] (arch_idle+0x294/0x3e0)\n[\u003cc007b17c\u003e] (arch_idle+0x294/0x3e0) from [\u003cc000eed8\u003e] (default_idle+0x18/0x2c)\n[\u003cc000eed8\u003e] (default_idle+0x18/0x2c) from [\u003cc000f254\u003e] (cpu_idle+0x90/0xe4)\n[\u003cc000f254\u003e] (cpu_idle+0x90/0xe4) from [\u003cc057231c\u003e] (rest_init+0x88/0xa0)\n[\u003cc057231c\u003e] (rest_init+0x88/0xa0) from [\u003cc07ff890\u003e] (start_kernel+0x3a8/0x40c)\nCode: c0704256 e12fff1e e59f2020 e5923000 (e5930000)\n\nThis is caused by the \u0027reserved\u0027 entries which we insert (see\n19b52abe3c5d7 - ARM: 7438/1: fill possible PMD empty section gaps)\nwhich get matched for physical address zero.\n\nResolve this by marking these reserved entries with a different flag.\n\nTested-by: Murali Nalajala \u003cmnalajal@codeaurora.org\u003e\nAcked-by: Nicolas Pitre \u003cnico@linaro.org\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6252fbdc0a40c20a21b24d7bfccf3c08ea9b10dc", "tree": "8034a8d9764257a0ee232f5f59170f5f7a4830ea", "parents": [ "8cc876def310b034ab0e0775a14d1a49472d7f5f" ], "author": { "name": "Dae S. Kim", "email": "dae@velatum.com", "time": "Fri Aug 31 02:00:51 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:52 2012 -0700" }, "message": "Staging: Android alarm: IOCTL command encoding fix\n\ncommit 6bd4a5d96c08dc2380f8053b1bd4f879f55cd3c9 upstream.\n\nFixed a bug. Data was being written to user space using an IOCTL\ncommand encoded with _IOC_WRITE access mode.\n\nSigned-off-by: Dae S. Kim \u003cdae@velatum.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8cc876def310b034ab0e0775a14d1a49472d7f5f", "tree": "5a1e9eafd41793894d0e686b00362fb26510d075", "parents": [ "eff605bb6c699aae80b199010f0beb26563fc399" ], "author": { "name": "Russell King", "email": "rmk+kernel@arm.linux.org.uk", "time": "Fri Sep 07 18:22:28 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:52 2012 -0700" }, "message": "ARM: 7527/1: uaccess: explicitly check __user pointer when !CPU_USE_DOMAINS\n\ncommit 8404663f81d212918ff85f493649a7991209fa04 upstream.\n\nThe {get,put}_user macros don\u0027t perform range checking on the provided\n__user address when !CPU_HAS_DOMAINS.\n\nThis patch reworks the out-of-line assembly accessors to check the user\naddress against a specified limit, returning -EFAULT if is is out of\nrange.\n\n[will: changed get_user register allocation to match put_user]\n[rmk: fixed building on older ARM architectures]\n\nReported-by: Catalin Marinas \u003ccatalin.marinas@arm.com\u003e\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "eff605bb6c699aae80b199010f0beb26563fc399", "tree": "2ea63babae83d99425cdcaa65967e17323333cdd", "parents": [ "dab510cf4641187bf69e1b5e1be014848c1b473f" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Fri Sep 07 18:21:44 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:52 2012 -0700" }, "message": "ARM: 7526/1: traps: send SIGILL if get_user fails on undef handling path\n\ncommit 2b2040af0b64cd93e5d4df2494c4486cf604090d upstream.\n\nget_user may fail to load from the provided __user address due to an\nunhandled fault generated by the access.\n\nIn the case of the undefined instruction trap, this results in failure\nto load the faulting instruction, in which case we should send SIGILL to\nthe task rather than continue with potentially uninitialised data.\n\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dab510cf4641187bf69e1b5e1be014848c1b473f", "tree": "fb3bdee6f93b5ab49d3d9518b4b1e44723013aa2", "parents": [ "3518fd322d6b13b278830cc41e26d6011c3641fa" ], "author": { "name": "David Brown", "email": "davidb@codeaurora.org", "time": "Tue Sep 04 21:36:37 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:51 2012 -0700" }, "message": "ARM: 7513/1: Make sure dtc is built before running it\n\ncommit 70b0476a2394de4f4e32e0b67288d80ff71ca963 upstream.\n\n\u0027make dtbs\u0027 in a clean tree will try running the dtc before actually\nbuilding it. Make these rules depend upon the scripts to build it.\n\nSigned-off-by: David Brown \u003cdavidb@codeaurora.org\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3518fd322d6b13b278830cc41e26d6011c3641fa", "tree": "af45c67a6d670baf83cd4cf8ddc2914b79a11fa5", "parents": [ "a18a65bd69dfdb28e729f22f9ca171fa81544dc4" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Thu Aug 16 18:55:44 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:51 2012 -0700" }, "message": "ARM: 7496/1: hw_breakpoint: don\u0027t rely on dfsr to show watchpoint access type\n\ncommit bf8801145c01ab600f8df66e8c879ac642fa5846 upstream.\n\nFrom ARM debug architecture v7.1 onwards, a watchpoint exception causes\nthe DFAR to be updated with the faulting data address. However, DFSR.WnR\ntakes an UNKNOWN value and therefore cannot be used in general to\ndetermine the access type that triggered the watchpoint.\n\nThis patch forbids watchpoints without an overflow handler from\nspecifying a specific access type (load/store). Those with overflow\nhandlers must be able to handle false positives potentially triggered by\na watchpoint of a different access type on the same address. For\nSIGTRAP-based handlers (i.e. ptrace), this should have no impact.\n\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a18a65bd69dfdb28e729f22f9ca171fa81544dc4", "tree": "9118cdd6c741ff124e8292d694fb1f6af7498f76", "parents": [ "2d4d5e8eefbfb75feac2f2d98b70399f4c5c09a5" ], "author": { "name": "Nicholas Bellinger", "email": "nab@linux-iscsi.org", "time": "Thu Aug 16 15:33:10 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:51 2012 -0700" }, "message": "target: Fix -\u003edata_length re-assignment bug with SCSI overflow\n\ncommit 4c054ba63ad47ef244cfcfa1cea38134620a5bae upstream.\n\nThis patch fixes a long-standing bug with SCSI overflow handling\nwhere se_cmd-\u003edata_length was incorrectly being re-assigned to\nthe larger CDB extracted allocation length, resulting in a number\nof fabric level errors that would end up causing a session reset\nin most cases. So instead now:\n\n - Only re-assign se_cmd-\u003edata_length durining UNDERFLOW (to use the\n smaller value)\n - Use existing se_cmd-\u003edata_length for OVERFLOW (to use the smaller\n value)\n\nThis fix has been tested with the following CDB to generate an\nSCSI overflow:\n\n sg_raw -r512 /dev/sdc 28 0 0 0 0 0 0 0 9 0\n\nTested using iscsi-target, tcm_qla2xxx, loopback and tcm_vhost fabric\nports. Here is a bit more detail on each case:\n\n - iscsi-target: Bug with open-iscsi with overflow, sg_raw returns\n -3584 bytes of data.\n - tcm_qla2xxx: Working as expected, returnins 512 bytes of data\n - loopback: sg_raw returns CHECK_CONDITION, from overflow rejection\n in transport_generic_map_mem_to_cmd()\n - tcm_vhost: Same as loopback\n\nReported-by: Roland Dreier \u003croland@purestorage.com\u003e\nCc: Roland Dreier \u003croland@purestorage.com\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\nCc: Boaz Harrosh \u003cbharrosh@panasas.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": "2d4d5e8eefbfb75feac2f2d98b70399f4c5c09a5", "tree": "ae447cfcbe97f9d16be20619d7ff3ea18b8d7155", "parents": [ "25941570aadb0f03270acab13bab1378eec5ea21" ], "author": { "name": "Tyler Hicks", "email": "tyhicks@canonical.com", "time": "Thu Sep 13 12:00:56 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:51 2012 -0700" }, "message": "eCryptfs: Copy up attributes of the lower target inode after rename\n\ncommit 8335eafc2859e1a26282bef7c3d19f3d68868b8a upstream.\n\nAfter calling into the lower filesystem to do a rename, the lower target\ninode\u0027s attributes were not copied up to the eCryptfs target inode. This\nresulted in the eCryptfs target inode staying around, rather than being\nevicted, because i_nlink was not updated for the eCryptfs inode. This\nalso meant that eCryptfs didn\u0027t do the final iput() on the lower target\ninode so it stayed around, as well. This would result in a failure to\nfree up space occupied by the target file in the rename() operation.\nBoth target inodes would eventually be evicted when the eCryptfs\nfilesystem was unmounted.\n\nThis patch calls fsstack_copy_attr_all() after the lower filesystem\ndoes its -\u003erename() so that important inode attributes, such as i_nlink,\nare updated at the eCryptfs layer. ecryptfs_evict_inode() is now called\nand eCryptfs can drop its final reference on the lower inode.\n\nhttp://launchpad.net/bugs/561129\n\nSigned-off-by: Tyler Hicks \u003ctyhicks@canonical.com\u003e\nTested-by: Colin Ian King \u003ccolin.king@canonical.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "25941570aadb0f03270acab13bab1378eec5ea21", "tree": "4c8c9bee1a21658a5a6a69898585246e31675f4e", "parents": [ "f92e8b0ddb85dfe7d8d2547516c873ec8dd9838e" ], "author": { "name": "Amerigo Wang", "email": "amwang@redhat.com", "time": "Sat Aug 18 07:02:20 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:51 2012 -0700" }, "message": "netconsole: remove a redundant netconsole_target_put()\n\ncommit 72d3eb13b5c0abe7d63efac41f39c5b644c7bbaa upstream.\n\nThis netconsole_target_put() is obviously redundant, and it\ncauses a kernel segfault when removing a bridge device which has\nnetconsole running on it.\n\nThis is caused by:\n\n\tcommit 8d8fc29d02a33e4bd5f4fa47823c1fd386346093\n\tAuthor: Amerigo Wang \u003camwang@redhat.com\u003e\n\tDate: Thu May 19 21:39:10 2011 +0000\n\n\t netpoll: disable netpoll when enslave a device\n\nSigned-off-by: Cong Wang \u003camwang@redhat.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f92e8b0ddb85dfe7d8d2547516c873ec8dd9838e", "tree": "ab1d76761b98911b413eb705cad3516311e50fd6", "parents": [ "5975bc201acbe121eaf22ee41076a08b92abc26f" ], "author": { "name": "Miklos Szeredi", "email": "mszeredi@suse.cz", "time": "Mon Sep 17 22:31:38 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:51 2012 -0700" }, "message": "vfs: dcache: use DCACHE_DENTRY_KILLED instead of DCACHE_DISCONNECTED in d_kill()\n\ncommit b161dfa6937ae46d50adce8a7c6b12233e96e7bd upstream.\n\nIBM reported a soft lockup after applying the fix for the rename_lock\ndeadlock. Commit c83ce989cb5f (\"VFS: Fix the nfs sillyrename regression\nin kernel 2.6.38\") was found to be the culprit.\n\nThe nfs sillyrename fix used DCACHE_DISCONNECTED to indicate that the\ndentry was killed. This flag can be set on non-killed dentries too,\nwhich results in infinite retries when trying to traverse the dentry\ntree.\n\nThis patch introduces a separate flag: DCACHE_DENTRY_KILLED, which is\nonly set in d_kill() and makes try_to_ascend() test only this flag.\n\nIBM reported successful test results with this patch.\n\nSigned-off-by: Miklos Szeredi \u003cmszeredi@suse.cz\u003e\nCc: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5975bc201acbe121eaf22ee41076a08b92abc26f", "tree": "04bdc44a094944c0edbcc126bb2e45a1eef5a9d3", "parents": [ "f2742791b906afefa8f20906824d594e56afa20c" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Sep 14 14:48:21 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:51 2012 -0700" }, "message": "vfs: make O_PATH file descriptors usable for \u0027fstat()\u0027\n\ncommit 55815f70147dcfa3ead5738fd56d3574e2e3c1c2 upstream.\n\nWe already use them for openat() and friends, but fstat() also wants to\nbe able to use O_PATH file descriptors. This should make it more\ndirectly comparable to the O_SEARCH of Solaris.\n\nNote that you could already do the same thing with \"fstatat()\" and an\nempty path, but just doing \"fstat()\" directly is simpler and faster, so\nthere is no reason not to just allow it directly.\n\nSee also commit 332a2e1244bd, which did the same thing for fchdir, for\nthe same reasons.\n\nReported-by: ольга крыжановская \u003colga.kryzhanovska@gmail.com\u003e\nCc: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f2742791b906afefa8f20906824d594e56afa20c", "tree": "4584c93962ccaa83fd6f714149e77cade7141804", "parents": [ "3b4a9ccbdc75c6c014383b8656b57afd249d65cf" ], "author": { "name": "Stephen M. Cameron", "email": "scameron@beardog.cce.hp.com", "time": "Fri Sep 14 16:35:10 2012 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:50 2012 -0700" }, "message": "cciss: fix handling of protocol error\n\ncommit 2453f5f992717251cfadab6184fbb3ec2f2e8b40 upstream.\n\nIf a command completes with a status of CMD_PROTOCOL_ERR, this\ninformation should be conveyed to the SCSI mid layer, not dropped\non the floor. Unlike a similar bug in the hpsa driver, this bug\nonly affects tape drives and CD and DVD ROM drives in the cciss\ndriver, and to induce it, you have to disconnect (or damage) a\ncable, so it is not a very likely scenario (which would explain\nwhy the bug has gone undetected for the last 10 years.)\n\nSigned-off-by: Stephen M. Cameron \u003cscameron@beardog.cce.hp.com\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3b4a9ccbdc75c6c014383b8656b57afd249d65cf", "tree": "d51ba8e7627df6c2af1e018221d9f731b4f1f29c", "parents": [ "fc7da7e1c4356e4ffc7c30423325b7f0da3311b2" ], "author": { "name": "Tejun Heo", "email": "tj@kernel.org", "time": "Tue Sep 18 14:24:59 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:50 2012 -0700" }, "message": "cpufreq/powernow-k8: workqueue user shouldn\u0027t migrate the kworker to another CPU\n\ncommit 6889125b8b4e09c5e53e6ecab3433bed1ce198c9 upstream.\n\npowernowk8_target() runs off a per-cpu work item and if the\ncpufreq_policy-\u003ecpu is different from the current one, it migrates the\nkworker to the target CPU by manipulating current-\u003ecpus_allowed. The\nfunction migrates the kworker back to the original CPU but this is\nstill broken. Workqueue concurrency management requires the kworkers\nto stay on the same CPU and powernowk8_target() ends up triggerring\nBUG_ON(rq !\u003d this_rq()) in try_to_wake_up_local() if it contends on\nfidvid_mutex and sleeps.\n\nIt is unclear why this bug is being reported now. Duncan says it\nappeared to be a regression of 3.6-rc1 and couldn\u0027t reproduce it on\n3.5. Bisection seemed to point to 63d95a91 \"workqueue: use @pool\ninstead of @gcwq or @cpu where applicable\" which is an non-functional\nchange. Given that the reproduce case sometimes took upto days to\ntrigger, it\u0027s easy to be misled while bisecting. Maybe something made\ncontention on fidvid_mutex more likely? I don\u0027t know.\n\nThis patch fixes the bug by using work_on_cpu() instead if @pol-\u003ecpu\nisn\u0027t the same as the current one. The code assumes that\ncpufreq_policy-\u003ecpu is kept online by the caller, which Rafael tells\nme is the case.\n\nstable: ed48ece27c (\"workqueue: reimplement work_on_cpu() using\n system_wq\") should be applied before this; otherwise, the\n behavior could be horrible.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nReported-by: Duncan \u003c1i5t5.duncan@cox.net\u003e\nTested-by: Duncan \u003c1i5t5.duncan@cox.net\u003e\nCc: Rafael J. Wysocki \u003crjw@sisk.pl\u003e\nCc: Andreas Herrmann \u003candreas.herrmann3@amd.com\u003e\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id\u003d47301\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "fc7da7e1c4356e4ffc7c30423325b7f0da3311b2", "tree": "137b99d2912421d1181bcf616e5d83f87901960a", "parents": [ "2ff0cd9f615bae1de9d812de92eff6426aad26c9" ], "author": { "name": "Tejun Heo", "email": "tj@kernel.org", "time": "Tue Sep 18 12:48:43 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:50 2012 -0700" }, "message": "workqueue: reimplement work_on_cpu() using system_wq\n\ncommit ed48ece27cd3d5ee0354c32bbaec0f3e1d4715c3 upstream.\n\nThe existing work_on_cpu() implementation is hugely inefficient. It\ncreates a new kthread, execute that single function and then let the\nkthread die on each invocation.\n\nNow that system_wq can handle concurrent executions, there\u0027s no\nadvantage of doing this. Reimplement work_on_cpu() using system_wq\nwhich makes it simpler and way more efficient.\n\nstable: While this isn\u0027t a fix in itself, it\u0027s needed to fix a\n workqueue related bug in cpufreq/powernow-k8. AFAICS, this\n shouldn\u0027t break other existing users.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nAcked-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\nCc: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nCc: Bjorn Helgaas \u003cbhelgaas@google.com\u003e\nCc: Len Brown \u003clenb@kernel.org\u003e\nCc: Rafael J. Wysocki \u003crjw@sisk.pl\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "2ff0cd9f615bae1de9d812de92eff6426aad26c9", "tree": "c2bb19352286bb93c6d0e32163351a1d58f0589d", "parents": [ "6cacd608448898cf0b7bb4353e1a92c6dc7d5dd9" ], "author": { "name": "Jesse Gross", "email": "jesse@nicira.com", "time": "Fri May 25 11:29:30 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:50 2012 -0700" }, "message": "openvswitch: Reset upper layer protocol info on internal devices.\n\n[ Upstream commit 7fe99e2d434eafeac0c57b279a77e5de39212636 ]\n\nIt\u0027s possible that packets that are sent on internal devices (from\nthe OVS perspective) have already traversed the local IP stack.\nAfter they go through the internal device, they will again travel\nthrough the IP stack which may get confused by the presence of\nexisting information in the skb. The problem can be observed\nwhen switching between namespaces. This clears out that information\nto avoid problems but deliberately leaves other metadata alone.\nThis is to provide maximum flexibility in chaining together OVS\nand other Linux components.\n\nSigned-off-by: Jesse Gross \u003cjesse@nicira.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "6cacd608448898cf0b7bb4353e1a92c6dc7d5dd9", "tree": "b028a0fbe2a78e7f1cec0403b5061fb83cea5d03", "parents": [ "b9d798a996cddfc4c1045e9af97ee434ccab4956" ], "author": { "name": "Yuval Mintz", "email": "yuvalmin@broadcom.com", "time": "Sun Aug 26 00:35:45 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:50 2012 -0700" }, "message": "bnx2x: fix 57840_MF pci id\n\n[ Upstream commit 5c879d2094946081af934739850c7260e8b25d3c ]\n\nCommit c3def943c7117d42caaed3478731ea7c3c87190e have added support for\nnew pci ids of the 57840 board, while failing to change the obsolete value\nin \u0027pci_ids.h\u0027.\nThis patch does so, allowing the probe of such devices.\n\nSigned-off-by: Yuval Mintz \u003cyuvalmin@broadcom.com\u003e\nSigned-off-by: Eilon Greenstein \u003ceilong@broadcom.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "b9d798a996cddfc4c1045e9af97ee434ccab4956", "tree": "e38de752bdba626b8fe7f5b8f6506438b0bfe2d0", "parents": [ "fae286b0e547ed0379d93ace7664ea6f55cce0e0" ], "author": { "name": "Francesco Ruggeri", "email": "fruggeri@aristanetworks.com", "time": "Fri Aug 24 07:38:35 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:50 2012 -0700" }, "message": "net: ipv4: ipmr_expire_timer causes crash when removing net namespace\n\n[ Upstream commit acbb219d5f53821b2d0080d047800410c0420ea1 ]\n\nWhen tearing down a net namespace, ipv4 mr_table structures are freed\nwithout first deactivating their timers. This can result in a crash in\nrun_timer_softirq.\nThis patch mimics the corresponding behaviour in ipv6.\nLocking and synchronization seem to be adequate.\nWe are about to kfree mrt, so existing code should already make sure that\nno other references to mrt are pending or can be created by incoming traffic.\nThe functions invoked here do not cause new references to mrt or other\nrace conditions to be created.\nInvoking del_timer_sync guarantees that ipmr_expire_timer is inactive.\nBoth ipmr_expire_process (whose completion we may have to wait in\ndel_timer_sync) and mroute_clean_tables internally use mfc_unres_lock\nor other synchronizations when needed, and they both only modify mrt.\n\nTested in Linux 3.4.8.\n\nSigned-off-by: Francesco Ruggeri \u003cfruggeri@aristanetworks.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "fae286b0e547ed0379d93ace7664ea6f55cce0e0", "tree": "fa7f0814dc371a996fdc785add3b5dc072a9c3e1", "parents": [ "c5ca1d03c29df5dc550f71bd1669af8bc30e32f8" ], "author": { "name": "xeb@mail.ru", "email": "xeb@mail.ru", "time": "Fri Aug 24 01:07:38 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:42 2012 -0700" }, "message": "l2tp: avoid to use synchronize_rcu in tunnel free function\n\n[ Upstream commit 99469c32f79a32d8481f87be0d3c66dad286f4ec ]\n\nAvoid to use synchronize_rcu in l2tp_tunnel_free because context may be\natomic.\n\nSigned-off-by: Dmitry Kozlov \u003cxeb@mail.ru\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "c5ca1d03c29df5dc550f71bd1669af8bc30e32f8", "tree": "961fa011bc1dcfddef5088cce7516834ff87a11e", "parents": [ "fa1dcb6f0d338629cf1e3939227135ce0ea17b50" ], "author": { "name": "Claudiu Manoil", "email": "claudiu.manoil@freescale.com", "time": "Thu Aug 23 21:46:25 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:38 2012 -0700" }, "message": "gianfar: fix default tx vlan offload feature flag\n\n[ Upstream commit e2c53be223aca36cf93eb6a0f6bafa079e78f52b ]\n\nCommit -\n\"b852b72 gianfar: fix bug caused by\n87c288c6e9aa31720b72e2bc2d665e24e1653c3e\"\ndisables by default (on mac init) the hw vlan tag insertion.\nThe \"features\" flags were not updated to reflect this, and\n\"ethtool -K\" shows tx-vlan-offload to be \"on\" by default.\n\nCc: Sebastian Poehn \u003csebastian.poehn@belden.com\u003e\nSigned-off-by: Claudiu Manoil \u003cclaudiu.manoil@freescale.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "fa1dcb6f0d338629cf1e3939227135ce0ea17b50", "tree": "6bd85b93ddef522490d88bbc8fe5684e72f850c0", "parents": [ "fbc350126994de9682e0400b969ab84437768894" ], "author": { "name": "Ben Hutchings", "email": "bhutchings@solarflare.com", "time": "Wed Aug 15 18:09:15 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:38 2012 -0700" }, "message": "sfc: Fix reporting of IPv4 full filters through ethtool\n\n[ Upstream commit ac70b2e9a13423b5efa0178e081936ce6979aea5 ]\n\nETHTOOL_GRXCLSRULE returns filters for a TCP/IPv4 or UDP/IPv4 4-tuple\nwith source and destination swapped.\n\nSigned-off-by: Ben Hutchings \u003cbhutchings@solarflare.com\u003e\n" }, { "commit": "fbc350126994de9682e0400b969ab84437768894", "tree": "f9cc4d4fc4e9f96f1bfa2e746901511feb0403b7", "parents": [ "912af4d4433a29aa51bcbc33c4275541d8ccc4b1" ], "author": { "name": "Yuchung Cheng", "email": "ycheng@google.com", "time": "Thu Aug 23 07:05:17 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:38 2012 -0700" }, "message": "tcp: fix cwnd reduction for non-sack recovery\n\n[ Upstream commit 7c4a56fec379ac0d7754e0d4da6a7361f1a4fe64 ]\n\nThe cwnd reduction in fast recovery is based on the number of packets\nnewly delivered per ACK. For non-sack connections every DUPACK\nsignifies a packet has been delivered, but the sender mistakenly\nskips counting them for cwnd reduction.\n\nThe fix is to compute newly_acked_sacked after DUPACKs are accounted\nin sacked_out for non-sack connections.\n\nSigned-off-by: Yuchung Cheng \u003cycheng@google.com\u003e\nAcked-by: Nandita Dukkipati \u003cnanditad@google.com\u003e\nAcked-by: Neal Cardwell \u003cncardwell@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "912af4d4433a29aa51bcbc33c4275541d8ccc4b1", "tree": "0b66cd3dc6ac1ca8f4950c9991b166d55649fa9d", "parents": [ "7c799a1e1ca2bc766574078b684c14474da9f704" ], "author": { "name": "Pablo Neira Ayuso", "email": "pablo@netfilter.org", "time": "Thu Aug 23 02:09:11 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:38 2012 -0700" }, "message": "netlink: fix possible spoofing from non-root processes\n\n[ Upstream commit 20e1db19db5d6b9e4e83021595eab0dc8f107bef ]\n\nNon-root user-space processes can send Netlink messages to other\nprocesses that are well-known for being subscribed to Netlink\nasynchronous notifications. This allows ilegitimate non-root\nprocess to send forged messages to Netlink subscribers.\n\nThe userspace process usually verifies the legitimate origin in\ntwo ways:\n\na) Socket credentials. If UID !\u003d 0, then the message comes from\n some ilegitimate process and the message needs to be dropped.\n\nb) Netlink portID. In general, portID \u003d\u003d 0 means that the origin\n of the messages comes from the kernel. Thus, discarding any\n message not coming from the kernel.\n\nHowever, ctnetlink sets the portID in event messages that has\nbeen triggered by some user-space process, eg. conntrack utility.\nSo other processes subscribed to ctnetlink events, eg. conntrackd,\nknow that the event was triggered by some user-space action.\n\nNeither of the two ways to discard ilegitimate messages coming\nfrom non-root processes can help for ctnetlink.\n\nThis patch adds capability validation in case that dst_pid is set\nin netlink_sendmsg(). This approach is aggressive since existing\napplications using any Netlink bus to deliver messages between\ntwo user-space processes will break. Note that the exception is\nNETLINK_USERSOCK, since it is reserved for netlink-to-netlink\nuserspace communication.\n\nStill, if anyone wants that his Netlink bus allows netlink-to-netlink\nuserspace, then they can set NL_NONROOT_SEND. However, by default,\nI don\u0027t think it makes sense to allow to use NETLINK_ROUTE to\ncommunicate two processes that are sending no matter what information\nthat is not related to link/neighbouring/routing. They should be using\nNETLINK_USERSOCK instead for that.\n\nSigned-off-by: Pablo Neira Ayuso \u003cpablo@netfilter.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "7c799a1e1ca2bc766574078b684c14474da9f704", "tree": "3920b2c94d08c9355c0f6f3e94b30f8ffd42529b", "parents": [ "9e296becde8a8da5bcc1a8e22f27bdf9bd8636fe" ], "author": { "name": "Eric Dumazet", "email": "edumazet@google.com", "time": "Tue Aug 21 06:21:17 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:37 2012 -0700" }, "message": "af_netlink: force credentials passing [CVE-2012-3520]\n\n[ Upstream commit e0e3cea46d31d23dc40df0a49a7a2c04fe8edfea ]\n\nPablo Neira Ayuso discovered that avahi and\npotentially NetworkManager accept spoofed Netlink messages because of a\nkernel bug. The kernel passes all-zero SCM_CREDENTIALS ancillary data\nto the receiver if the sender did not provide such data, instead of not\nincluding any such data at all or including the correct data from the\npeer (as it is the case with AF_UNIX).\n\nThis bug was introduced in commit 16e572626961\n(af_unix: dont send SCM_CREDENTIALS by default)\n\nThis patch forces passing credentials for netlink, as\nbefore the regression.\n\nAnother fix would be to not add SCM_CREDENTIALS in\nnetlink messages if not provided by the sender, but it\nmight break some programs.\n\nWith help from Florian Weimer \u0026 Petr Matousek\n\nThis issue is designated as CVE-2012-3520\n\nSigned-off-by: Eric Dumazet \u003cedumazet@google.com\u003e\nCc: Petr Matousek \u003cpmatouse@redhat.com\u003e\nCc: Florian Weimer \u003cfweimer@redhat.com\u003e\nCc: Pablo Neira Ayuso \u003cpablo@netfilter.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "9e296becde8a8da5bcc1a8e22f27bdf9bd8636fe", "tree": "be7a8a0b16cb84b2781b7e210e9749b8236092db", "parents": [ "d09b3b2b1183848e287bc0b6397f8d05945becc4" ], "author": { "name": "Eric Leblond", "email": "eric@regit.org", "time": "Thu Aug 16 22:02:58 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:37 2012 -0700" }, "message": "af_packet: don\u0027t emit packet on orig fanout group\n\n[ Upstream commit c0de08d04215031d68fa13af36f347a6cfa252ca ]\n\nIf a packet is emitted on one socket in one group of fanout sockets,\nit is transmitted again. It is thus read again on one of the sockets\nof the fanout group. This result in a loop for software which\ngenerate packets when receiving one.\nThis retransmission is not the intended behavior: a fanout group\nmust behave like a single socket. The packet should not be\ntransmitted on a socket if it originates from a socket belonging\nto the same fanout group.\n\nThis patch fixes the issue by changing the transmission check to\ntake fanout group info account.\n\nReported-by: Aleksandr Kotov \u003ca1k@mail.ru\u003e\nSigned-off-by: Eric Leblond \u003ceric@regit.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "d09b3b2b1183848e287bc0b6397f8d05945becc4", "tree": "1f3bd8db097160f7672c7cd987a48e4eb4e6d9d6", "parents": [ "62b4d90b525c6c11e467a2eadb12fcf64a6f0829" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:57 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:37 2012 -0700" }, "message": "net: fix info leak in compat dev_ifconf()\n\n[ Upstream commit 43da5f2e0d0c69ded3d51907d9552310a6b545e8 ]\n\nThe implementation of dev_ifconf() for the compat ioctl interface uses\nan intermediate ifc structure allocated in userland for the duration of\nthe syscall. Though, it fails to initialize the padding bytes inserted\nfor alignment and that for leaks four bytes of kernel stack. Add an\nexplicit memset(0) before filling the structure to avoid the info leak.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "62b4d90b525c6c11e467a2eadb12fcf64a6f0829", "tree": "1a7f38e53fbca60b6651a295a8063b714947157d", "parents": [ "59039dc90bb7879bd4c8c959109d27131f0ce40f" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:56 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:37 2012 -0700" }, "message": "ipvs: fix info leak in getsockopt(IP_VS_SO_GET_TIMEOUT)\n\n[ Upstream commit 2d8a041b7bfe1097af21441cb77d6af95f4f4680 ]\n\nIf at least one of CONFIG_IP_VS_PROTO_TCP or CONFIG_IP_VS_PROTO_UDP is\nnot set, __ip_vs_get_timeouts() does not fully initialize the structure\nthat gets copied to userland and that for leaks up to 12 bytes of kernel\nstack. Add an explicit memset(0) before passing the structure to\n__ip_vs_get_timeouts() to avoid the info leak.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Wensong Zhang \u003cwensong@linux-vs.org\u003e\nCc: Simon Horman \u003chorms@verge.net.au\u003e\nCc: Julian Anastasov \u003cja@ssi.bg\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "59039dc90bb7879bd4c8c959109d27131f0ce40f", "tree": "63a3e774f903b4f560702083debf6749c33fd9ef", "parents": [ "00ed5b8f397447a944a3305274b74049bfcd633f" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:55 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:37 2012 -0700" }, "message": "dccp: fix info leak via getsockopt(DCCP_SOCKOPT_CCID_TX_INFO)\n\n[ Upstream commit 7b07f8eb75aa3097cdfd4f6eac3da49db787381d ]\n\nThe CCID3 code fails to initialize the trailing padding bytes of struct\ntfrc_tx_info added for alignment on 64 bit architectures. It that for\npotentially leaks four bytes kernel stack via the getsockopt() syscall.\nAdd an explicit memset(0) before filling the structure to avoid the\ninfo leak.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Gerrit Renker \u003cgerrit@erg.abdn.ac.uk\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "00ed5b8f397447a944a3305274b74049bfcd633f", "tree": "93b0b7fa842936ef99be4f604ee8d0e9d8346d1e", "parents": [ "dbcba7a54a0327f0ef6d6a3ec53b67d0969109b6" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:53 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:37 2012 -0700" }, "message": "llc: fix info leak via getsockname()\n\n[ Upstream commit 3592aaeb80290bda0f2cf0b5456c97bfc638b192 ]\n\nThe LLC code wrongly returns 0, i.e. \"success\", when the socket is\nzapped. Together with the uninitialized uaddrlen pointer argument from\nsys_getsockname this leads to an arbitrary memory leak of up to 128\nbytes kernel stack via the getsockname() syscall.\n\nReturn an error instead when the socket is zapped to prevent the info\nleak. Also remove the unnecessary memset(0). We don\u0027t directly write to\nthe memory pointed by uaddr but memcpy() a local structure at the end of\nthe function that is properly initialized.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Arnaldo Carvalho de Melo \u003cacme@ghostprotocols.net\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "dbcba7a54a0327f0ef6d6a3ec53b67d0969109b6", "tree": "802a5ba716e47fa4c7364c0681f48a0a3c7e124b", "parents": [ "8717cd3d63233ee5591bf8e8d6e5960a1f6252b1" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:51 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:36 2012 -0700" }, "message": "Bluetooth: L2CAP - Fix info leak via getsockname()\n\n[ Upstream commit 792039c73cf176c8e39a6e8beef2c94ff46522ed ]\n\nThe L2CAP code fails to initialize the l2_bdaddr_type member of struct\nsockaddr_l2 and the padding byte added for alignment. It that for leaks\ntwo bytes kernel stack via the getsockname() syscall. Add an explicit\nmemset(0) before filling the structure to avoid the info leak.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nCc: Gustavo Padovan \u003cgustavo@padovan.org\u003e\nCc: Johan Hedberg \u003cjohan.hedberg@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "8717cd3d63233ee5591bf8e8d6e5960a1f6252b1", "tree": "ffc4c49e501cf875899afc531332fe6b87c4cfff", "parents": [ "279d3f5b2d402034dee1a81b7f5e3f678aa46d21" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:50 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:36 2012 -0700" }, "message": "Bluetooth: RFCOMM - Fix info leak via getsockname()\n\n[ Upstream commit 9344a972961d1a6d2c04d9008b13617bcb6ec2ef ]\n\nThe RFCOMM code fails to initialize the trailing padding byte of struct\nsockaddr_rc added for alignment. It that for leaks one byte kernel stack\nvia the getsockname() syscall. Add an explicit memset(0) before filling\nthe structure to avoid the info leak.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nCc: Gustavo Padovan \u003cgustavo@padovan.org\u003e\nCc: Johan Hedberg \u003cjohan.hedberg@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "279d3f5b2d402034dee1a81b7f5e3f678aa46d21", "tree": "7e44b53ad4a9dc5cebdc5efde5ab80c926d877db", "parents": [ "745dcdb0fd330f0cc984bd8a7764a81f04e44780" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:49 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:36 2012 -0700" }, "message": "Bluetooth: RFCOMM - Fix info leak in ioctl(RFCOMMGETDEVLIST)\n\n[ Upstream commit f9432c5ec8b1e9a09b9b0e5569e3c73db8de432a ]\n\nThe RFCOMM code fails to initialize the two padding bytes of struct\nrfcomm_dev_list_req inserted for alignment before copying it to\nuserland. Additionally there are two padding bytes in each instance of\nstruct rfcomm_dev_info. The ioctl() that for disclosures two bytes plus\ndev_num times two bytes uninitialized kernel heap memory.\n\nAllocate the memory using kzalloc() to fix this issue.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nCc: Gustavo Padovan \u003cgustavo@padovan.org\u003e\nCc: Johan Hedberg \u003cjohan.hedberg@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "745dcdb0fd330f0cc984bd8a7764a81f04e44780", "tree": "f0acac1ff978f33ebb9fa23bb470d18e375a30df", "parents": [ "639edee79eb2035b6fe3976f50a1c5364acc7352" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:48 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:36 2012 -0700" }, "message": "Bluetooth: RFCOMM - Fix info leak in getsockopt(BT_SECURITY)\n\n[ Upstream commit 9ad2de43f1aee7e7274a4e0d41465489299e344b ]\n\nThe RFCOMM code fails to initialize the key_size member of struct\nbt_security before copying it to userland -- that for leaking one\nbyte kernel stack. Initialize key_size with 0 to avoid the info\nleak.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nCc: Gustavo Padovan \u003cgustavo@padovan.org\u003e\nCc: Johan Hedberg \u003cjohan.hedberg@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "639edee79eb2035b6fe3976f50a1c5364acc7352", "tree": "b891e242addb0d42f802f1d6042b8da270f7d663", "parents": [ "87c42a1dfd5939d0a24795cd99b3d63daa4e1eff" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:47 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:36 2012 -0700" }, "message": "Bluetooth: HCI - Fix info leak via getsockname()\n\n[ Upstream commit 3f68ba07b1da811bf383b4b701b129bfcb2e4988 ]\n\nThe HCI code fails to initialize the hci_channel member of struct\nsockaddr_hci and that for leaks two bytes kernel stack via the\ngetsockname() syscall. Initialize hci_channel with 0 to avoid the\ninfo leak.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nCc: Gustavo Padovan \u003cgustavo@padovan.org\u003e\nCc: Johan Hedberg \u003cjohan.hedberg@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "87c42a1dfd5939d0a24795cd99b3d63daa4e1eff", "tree": "abff8acbebc4d3f6037a53ea40dee1e9c75e1fff", "parents": [ "458ed5622e976848aacdea07d4bfcb84a350c460" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:46 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:36 2012 -0700" }, "message": "Bluetooth: HCI - Fix info leak in getsockopt(HCI_FILTER)\n\n[ Upstream commit e15ca9a0ef9a86f0477530b0f44a725d67f889ee ]\n\nThe HCI code fails to initialize the two padding bytes of struct\nhci_ufilter before copying it to userland -- that for leaking two\nbytes kernel stack. Add an explicit memset(0) before filling the\nstructure to avoid the info leak.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nCc: Gustavo Padovan \u003cgustavo@padovan.org\u003e\nCc: Johan Hedberg \u003cjohan.hedberg@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "458ed5622e976848aacdea07d4bfcb84a350c460", "tree": "863b701597e40dc811ba93d9a33c814ad7fd2496", "parents": [ "5b26dbdd5f22871c21fc2ea4afedfe4ecad62d72" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:45 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:36 2012 -0700" }, "message": "atm: fix info leak via getsockname()\n\n[ Upstream commit 3c0c5cfdcd4d69ffc4b9c0907cec99039f30a50a ]\n\nThe ATM code fails to initialize the two padding bytes of struct\nsockaddr_atmpvc inserted for alignment. Add an explicit memset(0)\nbefore filling the structure to avoid the info leak.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "5b26dbdd5f22871c21fc2ea4afedfe4ecad62d72", "tree": "879879858bb2508f4285b0d1eae2b25e4c51a7a1", "parents": [ "84a2d3c44cce71152f3555af83bafea6ec5ef23c" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:44 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:35 2012 -0700" }, "message": "atm: fix info leak in getsockopt(SO_ATMPVC)\n\n[ Upstream commit e862f1a9b7df4e8196ebec45ac62295138aa3fc2 ]\n\nThe ATM code fails to initialize the two padding bytes of struct\nsockaddr_atmpvc inserted for alignment. Add an explicit memset(0)\nbefore filling the structure to avoid the info leak.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "84a2d3c44cce71152f3555af83bafea6ec5ef23c", "tree": "fb069dbaa2fe6244cf4a4eaa9cbcdfdc57d22771", "parents": [ "c8cca9d90b953a0a2b5d0edab789f5c52ae983f5" ], "author": { "name": "Ben Hutchings", "email": "bhutchings@solarflare.com", "time": "Tue Aug 14 08:54:51 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:35 2012 -0700" }, "message": "ipv6: addrconf: Avoid calling netdevice notifiers with RCU read-side lock\n\n[ Upstream commit 4acd4945cd1e1f92b20d14e349c6c6a52acbd42d ]\n\nCong Wang reports that lockdep detected suspicious RCU usage while\nenabling IPV6 forwarding:\n\n [ 1123.310275] \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 [ 1123.442202] [ INFO: suspicious RCU usage. ]\n [ 1123.558207] 3.6.0-rc1+ #109 Not tainted\n [ 1123.665204] -------------------------------\n [ 1123.768254] include/linux/rcupdate.h:430 Illegal context switch in RCU read-side critical section!\n [ 1123.992320]\n [ 1123.992320] other info that might help us debug this:\n [ 1123.992320]\n [ 1124.307382]\n [ 1124.307382] rcu_scheduler_active \u003d 1, debug_locks \u003d 0\n [ 1124.522220] 2 locks held by sysctl/5710:\n [ 1124.648364] #0: (rtnl_mutex){+.+.+.}, at: [\u003cffffffff81768498\u003e] rtnl_trylock+0x15/0x17\n [ 1124.882211] #1: (rcu_read_lock){.+.+.+}, at: [\u003cffffffff81871df8\u003e] rcu_lock_acquire+0x0/0x29\n [ 1125.085209]\n [ 1125.085209] stack backtrace:\n [ 1125.332213] Pid: 5710, comm: sysctl Not tainted 3.6.0-rc1+ #109\n [ 1125.441291] Call Trace:\n [ 1125.545281] [\u003cffffffff8109d915\u003e] lockdep_rcu_suspicious+0x109/0x112\n [ 1125.667212] [\u003cffffffff8107c240\u003e] rcu_preempt_sleep_check+0x45/0x47\n [ 1125.781838] [\u003cffffffff8107c260\u003e] __might_sleep+0x1e/0x19b\n[...]\n [ 1127.445223] [\u003cffffffff81757ac5\u003e] call_netdevice_notifiers+0x4a/0x4f\n[...]\n [ 1127.772188] [\u003cffffffff8175e125\u003e] dev_disable_lro+0x32/0x6b\n [ 1127.885174] [\u003cffffffff81872d26\u003e] dev_forward_change+0x30/0xcb\n [ 1128.013214] [\u003cffffffff818738c4\u003e] addrconf_forward_change+0x85/0xc5\n[...]\n\naddrconf_forward_change() uses RCU iteration over the netdev list,\nwhich is unnecessary since it already holds the RTNL lock. We also\ncannot reasonably require netdevice notifier functions not to sleep.\n\nReported-by: Cong Wang \u003camwang@redhat.com\u003e\nSigned-off-by: Ben Hutchings \u003cbhutchings@solarflare.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "c8cca9d90b953a0a2b5d0edab789f5c52ae983f5", "tree": "cb7361eb1dbf30145276156e99f4e82941f456bd", "parents": [ "caf2630c41a183b72e5d6211e5efd1457ac0c463" ], "author": { "name": "danborkmann@iogearbox.net", "email": "danborkmann@iogearbox.net", "time": "Fri Aug 10 22:48:54 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:35 2012 -0700" }, "message": "af_packet: remove BUG statement in tpacket_destruct_skb\n\n[ Upstream commit 7f5c3e3a80e6654cf48dfba7cf94f88c6b505467 ]\n\nHere\u0027s a quote of the comment about the BUG macro from asm-generic/bug.h:\n\n Don\u0027t use BUG() or BUG_ON() unless there\u0027s really no way out; one\n example might be detecting data structure corruption in the middle\n of an operation that can\u0027t be backed out of. If the (sub)system\n can somehow continue operating, perhaps with reduced functionality,\n it\u0027s probably not BUG-worthy.\n\n If you\u0027re tempted to BUG(), think again: is completely giving up\n really the *only* solution? There are usually better options, where\n users don\u0027t need to reboot ASAP and can mostly shut down cleanly.\n\nIn our case, the status flag of a ring buffer slot is managed from both sides,\nthe kernel space and the user space. This means that even though the kernel\nside might work as expected, the user space screws up and changes this flag\nright between the send(2) is triggered when the flag is changed to\nTP_STATUS_SENDING and a given skb is destructed after some time. Then, this\nwill hit the BUG macro. As David suggested, the best solution is to simply\nremove this statement since it cannot be used for kernel side internal\nconsistency checks. I\u0027ve tested it and the system still behaves /stable/ in\nthis case, so in accordance with the above comment, we should rather remove it.\n\nSigned-off-by: Daniel Borkmann \u003cdaniel.borkmann@tik.ee.ethz.ch\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "caf2630c41a183b72e5d6211e5efd1457ac0c463", "tree": "5bcd1cdd058be10d65ea4fb7a809c5b00ef41aaf", "parents": [ "a348ed02b367a8a8307444724db5c8e96c90ac78" ], "author": { "name": "Alexey Khoroshilov", "email": "khoroshilov@ispras.ru", "time": "Wed Aug 08 00:33:25 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:35 2012 -0700" }, "message": "net/core: Fix potential memory leak in dev_set_alias()\n\n[ Upstream commit 7364e445f62825758fa61195d237a5b8ecdd06ec ]\n\nDo not leak memory by updating pointer with potentially NULL realloc return value.\n\nFound by Linux Driver Verification project (linuxtesting.org).\n\nSigned-off-by: Alexey Khoroshilov \u003ckhoroshilov@ispras.ru\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "a348ed02b367a8a8307444724db5c8e96c90ac78", "tree": "32ebdd8122276f761bbb80b3bebc7975b3fad32c", "parents": [ "bc3f72433351e278a92a38c2090aacff982ce558" ], "author": { "name": "Gao feng", "email": "gaofeng@cn.fujitsu.com", "time": "Tue Aug 07 00:23:11 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:35 2012 -0700" }, "message": "pptp: lookup route with the proper net namespace\n\n[ Upstream commit 08252b32311c3fa84219ad794d640af7399b5485 ]\n\npptp always use init_net as the net namespace to lookup\nroute, this will cause route lookup failed in container.\n\nbecause we already set the correct net namespace to struct\nsock in pptp_create,so fix this by using sock_net(sk) to\nreplace \u0026init_net.\n\nSigned-off-by: Gao feng \u003cgaofeng@cn.fujitsu.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "bc3f72433351e278a92a38c2090aacff982ce558", "tree": "b945c7dcdb4ae0f7abdc56a2df8bd9df0f599335", "parents": [ "7e0c71a9a5a23f9433eac1d0aabbc9d54da3428b" ], "author": { "name": "Wu Fengguang", "email": "fengguang.wu@intel.com", "time": "Thu Aug 02 23:10:01 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:35 2012 -0700" }, "message": "isdnloop: fix and simplify isdnloop_init()\n\n[ Upstream commit 77f00f6324cb97cf1df6f9c4aaeea6ada23abdb2 ]\n\nFix a buffer overflow bug by removing the revision and printk.\n\n[ 22.016214] isdnloop-ISDN-driver Rev 1.11.6.7\n[ 22.097508] isdnloop: (loop0) virtual card added\n[ 22.174400] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ffffffff83244972\n[ 22.174400]\n[ 22.436157] Pid: 1, comm: swapper Not tainted 3.5.0-bisect-00018-gfa8bbb1-dirty #129\n[ 22.624071] Call Trace:\n[ 22.720558] [\u003cffffffff832448c3\u003e] ? CallcNew+0x56/0x56\n[ 22.815248] [\u003cffffffff8222b623\u003e] panic+0x110/0x329\n[ 22.914330] [\u003cffffffff83244972\u003e] ? isdnloop_init+0xaf/0xb1\n[ 23.014800] [\u003cffffffff832448c3\u003e] ? CallcNew+0x56/0x56\n[ 23.090763] [\u003cffffffff8108e24b\u003e] __stack_chk_fail+0x2b/0x30\n[ 23.185748] [\u003cffffffff83244972\u003e] isdnloop_init+0xaf/0xb1\n\nSigned-off-by: Fengguang Wu \u003cfengguang.wu@intel.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "7e0c71a9a5a23f9433eac1d0aabbc9d54da3428b", "tree": "78f3871cb2b2f4cd89a6ed8bda6bfc325e3f7814", "parents": [ "4658b24b2dd0e4c6215db2203743fa999765e8a0" ], "author": { "name": "Hiroaki SHIMODA", "email": "shimoda.hiroaki@gmail.com", "time": "Fri Aug 03 19:57:52 2012 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:34 2012 -0700" }, "message": "net_sched: gact: Fix potential panic in tcf_gact().\n\n[ Upstream commit 696ecdc10622d86541f2e35cc16e15b6b3b1b67e ]\n\ngact_rand array is accessed by gact-\u003etcfg_ptype whose value\nis assumed to less than MAX_RAND, but any range checks are\nnot performed.\n\nSo add a check in tcf_gact_init(). And in tcf_gact(), we can\nreduce a branch.\n\nSigned-off-by: Hiroaki SHIMODA \u003cshimoda.hiroaki@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "4658b24b2dd0e4c6215db2203743fa999765e8a0", "tree": "9a88804f646780a2424a5ac87586151e923b1b64", "parents": [ "0a1f711681e0d7068b69c0697c4ba284fbf1b2bf" ], "author": { "name": "Ben Hutchings", "email": "bhutchings@solarflare.com", "time": "Mon Jul 30 16:11:42 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:34 2012 -0700" }, "message": "tcp: Apply device TSO segment limit earlier\n\n[ Upstream commit 1485348d2424e1131ea42efc033cbd9366462b01 ]\n\nCache the device gso_max_segs in sock::sk_gso_max_segs and use it to\nlimit the size of TSO skbs. This avoids the need to fall back to\nsoftware GSO for local TCP senders.\n\nSigned-off-by: Ben Hutchings \u003cbhutchings@solarflare.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "0a1f711681e0d7068b69c0697c4ba284fbf1b2bf", "tree": "aa32a825206b44aa90953dcf650ba39d6a502c24", "parents": [ "2dc3b21fbca98bd3c8d9e53acf5d966add3c7606" ], "author": { "name": "Ben Hutchings", "email": "bhutchings@solarflare.com", "time": "Mon Jul 30 15:57:44 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:34 2012 -0700" }, "message": "sfc: Fix maximum number of TSO segments and minimum TX queue size\n\n[ Upstream commit 7e6d06f0de3f74ca929441add094518ae332257c ]\n\nCurrently an skb requiring TSO may not fit within a minimum-size TX\nqueue. The TX queue selected for the skb may stall and trigger the TX\nwatchdog repeatedly (since the problem skb will be retried after the\nTX reset). This issue is designated as CVE-2012-3412.\n\nSet the maximum number of TSO segments for our devices to 100. This\nshould make no difference to behaviour unless the actual MSS is less\nthan about 700. Increase the minimum TX queue size accordingly to\nallow for 2 worst-case skbs, so that there will definitely be space\nto add an skb after we wake a queue.\n\nTo avoid invalidating existing configurations, change\nefx_ethtool_set_ringparam() to fix up values that are too small rather\nthan returning -EINVAL.\n\nSigned-off-by: Ben Hutchings \u003cbhutchings@solarflare.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "2dc3b21fbca98bd3c8d9e53acf5d966add3c7606", "tree": "6fe9f88dec40cfca839962a5a363848b27afb744", "parents": [ "00709f7f01c3a10252f030f0bdacecbb349d7be4" ], "author": { "name": "Ben Hutchings", "email": "bhutchings@solarflare.com", "time": "Mon Jul 30 15:57:00 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Oct 02 10:29:34 2012 -0700" }, "message": "net: Allow driver to limit number of GSO segments per skb\n\n[ Upstream commit 30b678d844af3305cda5953467005cebb5d7b687 ]\n\nA peer (or local user) may cause TCP to use a nominal MSS of as little\nas 88 (actual MSS of 76 with timestamps). Given that we have a\nsufficiently prodigious local sender and the peer ACKs quickly enough,\nit is nevertheless possible to grow the window for such a connection\nto the point that we will try to send just under 64K at once. This\nresults in a single skb that expands to 861 segments.\n\nIn some drivers with TSO support, such an skb will require hundreds of\nDMA descriptors; a substantial fraction of a TX ring or even more than\na full ring. The TX queue selected for the skb may stall and trigger\nthe TX watchdog repeatedly (since the problem skb will be retried\nafter the TX reset). This particularly affects sfc, for which the\nissue is designated as CVE-2012-3412.\n\nTherefore:\n1. Add the field net_device::gso_max_segs holding the device-specific\n limit.\n2. In netif_skb_features(), if the number of segments is too high then\n mask out GSO features to force fall back to software GSO.\n\nSigned-off-by: Ben Hutchings \u003cbhutchings@solarflare.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "00709f7f01c3a10252f030f0bdacecbb349d7be4", "tree": "e34065c6fb9912d86cbe81c955b7125eb0f21598", "parents": [ "e18625cacb8e252e3e4a9dea3db4dbca523276bc" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 15:18:55 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 15:18:55 2012 -0700" }, "message": "Linux 3.4.11\n" }, { "commit": "e18625cacb8e252e3e4a9dea3db4dbca523276bc", "tree": "de4ab619ddfbc14f4e74d6a917ceddaf39b2b4c4", "parents": [ "af843972724e172827266e91ba326c069c8c088c" ], "author": { "name": "Luca Tettamanti", "email": "kronos.it@gmail.com", "time": "Tue Aug 21 17:36:28 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:34 2012 -0700" }, "message": "hwmon: (asus_atk0110) Add quirk for Asus M5A78L\n\ncommit 43ca6cb28c871f2fbad10117b0648e5ae3b0f638 upstream.\n\nThe old interface is bugged and reads the wrong sensor when retrieving\nthe reading for the chassis fan (it reads the CPU sensor); the new\ninterface works fine.\n\nReported-by: Göran Uddeborg \u003cgoeran@uddeborg.se\u003e\nTested-by: Göran Uddeborg \u003cgoeran@uddeborg.se\u003e\nSigned-off-by: Luca Tettamanti \u003ckronos.it@gmail.com\u003e\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "af843972724e172827266e91ba326c069c8c088c", "tree": "532784df2f1c8e938f015e9f52c6fe7ae23981e4", "parents": [ "72961d91696071841fa013f11f686eaa7e2d0996" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Wed Aug 15 11:31:54 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:34 2012 -0700" }, "message": "dccp: check ccid before dereferencing\n\ncommit 276bdb82dedb290511467a5a4fdbe9f0b52dce6f upstream.\n\nccid_hc_rx_getsockopt() and ccid_hc_tx_getsockopt() might be called with\na NULL ccid pointer leading to a NULL pointer dereference. This could\nlead to a privilege escalation if the attacker is able to map page 0 and\nprepare it with a fake ccid_ops pointer.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Gerrit Renker \u003cgerrit@erg.abdn.ac.uk\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "72961d91696071841fa013f11f686eaa7e2d0996", "tree": "31813ab89c9cf0013c067e1525816d271c7ab33f", "parents": [ "bbebafa0d9507206793a05fbeb010eafb1fdb0d0" ], "author": { "name": "Andreas Herrmann", "email": "andreas.herrmann3@amd.com", "time": "Tue Jul 31 15:41:45 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:34 2012 -0700" }, "message": "x86, microcode, AMD: Fix broken ucode patch size check\n\ncommit 36bf50d7697be18c6bfd0401e037df10bff1e573 upstream.\n\nThis issue was recently observed on an AMD C-50 CPU where a patch of\nmaximum size was applied.\n\nCommit be62adb49294 (\"x86, microcode, AMD: Simplify ucode verification\")\nadded current_size in get_matching_microcode(). This is calculated as\nsize of the ucode patch + 8 (ie. size of the header). Later this is\ncompared against the maximum possible ucode patch size for a CPU family.\nAnd of course this fails if the patch has already maximum size.\n\nSigned-off-by: Andreas Herrmann \u003candreas.herrmann3@amd.com\u003e\nSigned-off-by: Borislav Petkov \u003cborislav.petkov@amd.com\u003e\nLink: http://lkml.kernel.org/r/1344361461-10076-1-git-send-email-bp@amd64.org\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "bbebafa0d9507206793a05fbeb010eafb1fdb0d0", "tree": "f97c78c97a495081de59374d803bf1e5d2999853", "parents": [ "095ac020be339cad6f158508cc3b9f740c60b53a" ], "author": { "name": "Konrad Rzeszutek Wilk", "email": "konrad.wilk@oracle.com", "time": "Wed Sep 05 16:35:20 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:33 2012 -0700" }, "message": "xen/pciback: Fix proper FLR steps.\n\ncommit 80ba77dfbce85f2d1be54847de3c866de1b18a9a upstream.\n\nWhen we do FLR and save PCI config we did it in the wrong order.\nThe end result was that if a PCI device was unbind from\nits driver, then binded to xen-pciback, and then back to its\ndriver we would get:\n\n\u003e lspci -s 04:00.0\n04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection\n13:42:12 # 4 :~/\n\u003e echo \"0000:04:00.0\" \u003e /sys/bus/pci/drivers/pciback/unbind\n\u003e modprobe e1000e\ne1000e: Intel(R) PRO/1000 Network Driver - 2.0.0-k\ne1000e: Copyright(c) 1999 - 2012 Intel Corporation.\ne1000e 0000:04:00.0: Disabling ASPM L0s L1\ne1000e 0000:04:00.0: enabling device (0000 -\u003e 0002)\nxen: registering gsi 48 triggering 0 polarity 1\nAlready setup the GSI :48\ne1000e 0000:04:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode\ne1000e: probe of 0000:04:00.0 failed with error -2\n\nThis fixes it by first saving the PCI configuration space, then\ndoing the FLR.\n\nReported-by: Ren, Yongjie \u003cyongjie.ren@intel.com\u003e\nReported-and-Tested-by: Tobias Geiger \u003ctobias.geiger@vido.info\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": "095ac020be339cad6f158508cc3b9f740c60b53a", "tree": "c2ef5f1222978026fc4172c1251f3f417fb51765", "parents": [ "9db2bc1e0363bb9401e6407b198463c01f32dd84" ], "author": { "name": "Ronny Hegewald", "email": "ronny.hegewald@online.de", "time": "Fri Aug 31 09:57:52 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:33 2012 -0700" }, "message": "xen: Use correct masking in xen_swiotlb_alloc_coherent.\n\ncommit b5031ed1be0aa419250557123633453753181643 upstream.\n\nWhen running 32-bit pvops-dom0 and a driver tries to allocate a coherent\nDMA-memory the xen swiotlb-implementation returned memory beyond 4GB.\n\nThe underlaying reason is that if the supplied driver passes in a\nDMA_BIT_MASK(64) ( hwdev-\u003ecoherent_dma_mask is set to 0xffffffffffffffff)\nour dma_mask will be u64 set to 0xffffffffffffffff even if we set it to\nDMA_BIT_MASK(32) previously. Meaning we do not reset the upper bits.\nBy using the dma_alloc_coherent_mask function - it does the proper casting\nand we get 0xfffffffff.\n\nThis caused not working sound on a system with 4 GB and a 64-bit\ncompatible sound-card with sets the DMA-mask to 64bit.\n\nOn bare-metal and the forward-ported xen-dom0 patches from OpenSuse a coherent\nDMA-memory is always allocated inside the 32-bit address-range by calling\ndma_alloc_coherent_mask.\n\nThis patch adds the same functionality to xen swiotlb and is a rebase of the\noriginal patch from Ronny Hegewald which never got upstream b/c the\nunderlaying reason was not understood until now.\n\nThe original email with the original patch is in:\nhttp://old-list-archives.xen.org/archives/html/xen-devel/2010-02/msg00038.html\nthe original thread from where the discussion started is in:\nhttp://old-list-archives.xen.org/archives/html/xen-devel/2010-01/msg00928.html\n\nSigned-off-by: Ronny Hegewald \u003cronny.hegewald@online.de\u003e\nSigned-off-by: Stefano Panella \u003cstefano.panella@citrix.com\u003e\nAcked-By: David Vrabel \u003cdavid.vrabel@citrix.com\u003e\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9db2bc1e0363bb9401e6407b198463c01f32dd84", "tree": "76bf494811a3312cd8892a75f41f133f42dc8036", "parents": [ "df0b962e0900ec0b2b93eac2795e3e65cc18052f" ], "author": { "name": "Mel Gorman", "email": "mgorman@suse.de", "time": "Mon Jul 23 12:16:19 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:33 2012 -0700" }, "message": "PARISC: Redefine ATOMIC_INIT and ATOMIC64_INIT to drop the casts\n\ncommit bba3d8c3b3c0f2123be5bc687d1cddc13437c923 upstream.\n\nThe following build error occured during a parisc build with\nswap-over-NFS patches applied.\n\nnet/core/sock.c:274:36: error: initializer element is not constant\nnet/core/sock.c:274:36: error: (near initialization for \u0027memalloc_socks\u0027)\nnet/core/sock.c:274:36: error: initializer element is not constant\n\nDave Anglin says:\n\u003e Here is the line in sock.i:\n\u003e\n\u003e struct static_key memalloc_socks \u003d ((struct static_key) { .enabled \u003d\n\u003e ((atomic_t) { (0) }) });\n\nThe above line contains two compound literals. It also uses a designated\ninitializer to initialize the field enabled. A compound literal is not a\nconstant expression.\n\nThe location of the above statement isn\u0027t fully clear, but if a compound\nliteral occurs outside the body of a function, the initializer list must\nconsist of constant expressions.\n\nReported-by: Fengguang Wu \u003cfengguang.wu@intel.com\u003e\nSigned-off-by: Mel Gorman \u003cmgorman@suse.de\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Parallels.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "df0b962e0900ec0b2b93eac2795e3e65cc18052f", "tree": "9336e47b755a8a6c860aca67e23ba410aa5b7fa1", "parents": [ "ae2e2906541827de51f896e3b035bf3b1c660e73" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Tue Aug 28 21:40:51 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:33 2012 -0700" }, "message": "drm/vmwgfx: add MODULE_DEVICE_TABLE so vmwgfx loads at boot\n\ncommit c4903429a92be60e6fe59868924a65eca4cd1a38 upstream.\n\nThis will cause udev to load vmwgfx instead of waiting for X\nto do it.\n\nReviewed-by: Jakob Bornecrantz \u003cjakob@vmware.com\u003e\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ae2e2906541827de51f896e3b035bf3b1c660e73", "tree": "d83aae835fd213ffdb7d5c5ed575318deebca42a", "parents": [ "7d60f877b38866c5b46162256207891c45057b39" ], "author": { "name": "Dmitry Torokhov", "email": "dmitry.torokhov@gmail.com", "time": "Tue Aug 21 21:57:15 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:33 2012 -0700" }, "message": "Input: i8042 - add Gigabyte T1005 series netbooks to noloop table\n\ncommit 7b125b94ca16b7e618c6241cb02c4c8060cea5e3 upstream.\n\nThey all define their chassis type as \"Other\" and therefore are not\ncategorized as \"laptops\" by the driver, which tries to perform AUX IRQ\ndelivery test which fails and causes touchpad not working.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id\u003d42620\nSigned-off-by: Dmitry Torokhov \u003cdmitry.torokhov@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7d60f877b38866c5b46162256207891c45057b39", "tree": "f06de1fb5e7f805428a775906cc4a9939c5ca751", "parents": [ "7db3f56f37640c88387dfda6fad1e930d589d0e3" ], "author": { "name": "Alan Stern", "email": "stern@rowland.harvard.edu", "time": "Thu Aug 23 10:51:55 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:33 2012 -0700" }, "message": "HID: add NOGET quirk for Eaton Ellipse MAX UPS\n\ncommit 67ddbb3e6568fb1820b2cc45b00c50702b114801 upstream.\n\nThis patch (as1603) adds a NOGET quirk for the Eaton Ellipse MAX UPS\ndevice. (The USB IDs were already present in hid-ids.h, apparently\nunder a different name.)\n\nSigned-off-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nReported-by: Laurent Bigonville \u003cl.bigonville@edpnet.be\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7db3f56f37640c88387dfda6fad1e930d589d0e3", "tree": "550bafb4d1ee8cdce8e0b59dbf949c7660e2e238", "parents": [ "f313f5b440c874dbee75922e30736b9069f0a1d1" ], "author": { "name": "James Ralston", "email": "james.d.ralston@intel.com", "time": "Mon Sep 10 10:14:02 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:33 2012 -0700" }, "message": "i2c-i801: Add Device IDs for Intel Lynx Point-LP PCH\n\ncommit 4a8f1ddde942e232387e6129ce4f4c412e43802f upstream.\n\nAdd the SMBus Device IDs for the Intel Lynx Point-LP PCH.\n\nSigned-off-by: James Ralston \u003cjames.d.ralston@intel.com\u003e\nSigned-off-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f313f5b440c874dbee75922e30736b9069f0a1d1", "tree": "bdd3e100ba8c92147ccd9a6569cbfa9f83303099", "parents": [ "b4b55ff702c3551ba39ccec0b1dda9e3b57429be" ], "author": { "name": "Axel Lin", "email": "axel.lin@gmail.com", "time": "Mon Sep 10 10:14:02 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:32 2012 -0700" }, "message": "i2c-designware: Fix build error if CONFIG_I2C_DESIGNWARE_PLATFORM\u003dy \u0026\u0026 CONFIG_I2C_DESIGNWARE_PCI\u003dy\n\ncommit e68bb91baa0bb9817567bd45d560919e8e26373b upstream.\n\nThis patch adds config I2C_DESIGNWARE_CORE in Kconfig, and let\nI2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_PCI select I2C_DESIGNWARE_CORE.\n\nBecause both I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_PCI can be built as\nbuilt-in or module, we also need to export the functions in i2c-designware-core.\n\nThis fixes below build error when CONFIG_I2C_DESIGNWARE_PLATFORM\u003dy \u0026\u0026\nCONFIG_I2C_DESIGNWARE_PCI\u003dy:\n\n LD drivers/i2c/busses/built-in.o\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_clear_int\u0027:\ni2c-designware-core.c:(.text+0xa10): multiple definition of `i2c_dw_clear_int\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x928): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_init\u0027:\ni2c-designware-core.c:(.text+0x178): multiple definition of `i2c_dw_init\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x90): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `dw_readl\u0027:\ni2c-designware-core.c:(.text+0xe8): multiple definition of `dw_readl\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x0): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_isr\u0027:\ni2c-designware-core.c:(.text+0x724): multiple definition of `i2c_dw_isr\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x63c): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_xfer\u0027:\ni2c-designware-core.c:(.text+0x4b0): multiple definition of `i2c_dw_xfer\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x3c8): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_is_enabled\u0027:\ni2c-designware-core.c:(.text+0x9d4): multiple definition of `i2c_dw_is_enabled\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x8ec): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `dw_writel\u0027:\ni2c-designware-core.c:(.text+0x124): multiple definition of `dw_writel\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x3c): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_xfer_msg\u0027:\ni2c-designware-core.c:(.text+0x2e8): multiple definition of `i2c_dw_xfer_msg\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x200): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_enable\u0027:\ni2c-designware-core.c:(.text+0x9c8): multiple definition of `i2c_dw_enable\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x8e0): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_read_comp_param\u0027:\ni2c-designware-core.c:(.text+0xa24): multiple definition of `i2c_dw_read_comp_param\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x93c): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_disable\u0027:\ni2c-designware-core.c:(.text+0x9dc): multiple definition of `i2c_dw_disable\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x8f4): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_func\u0027:\ni2c-designware-core.c:(.text+0x710): multiple definition of `i2c_dw_func\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x628): first defined here\ndrivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_disable_int\u0027:\ni2c-designware-core.c:(.text+0xa18): multiple definition of `i2c_dw_disable_int\u0027\ndrivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x930): first defined here\nmake[3]: *** [drivers/i2c/busses/built-in.o] Error 1\nmake[2]: *** [drivers/i2c/busses] Error 2\nmake[1]: *** [drivers/i2c] Error 2\nmake: *** [drivers] Error 2\n\nSigned-off-by: Axel Lin \u003caxel.lin@gmail.com\u003e\nSigned-off-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nTested-by: Jiri Slaby \u003cjslaby@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b4b55ff702c3551ba39ccec0b1dda9e3b57429be", "tree": "3ad28ac491732e607652401e9eefb20d2a3ce55b", "parents": [ "6cbe67f990c723facaeed94e29a1d854dc5930ec" ], "author": { "name": "Miklos Szeredi", "email": "mszeredi@suse.cz", "time": "Tue Sep 04 18:45:54 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:32 2012 -0700" }, "message": "fuse: fix retrieve length\n\ncommit c9e67d483776d8d2a5f3f70491161b205930ffe1 upstream.\n\nIn some cases fuse_retrieve() would return a short byte count if offset was\nnon-zero. The data returned was correct, though.\n\nSigned-off-by: Miklos Szeredi \u003cmszeredi@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6cbe67f990c723facaeed94e29a1d854dc5930ec", "tree": "dd429c8da860fb2d84694ed7bc0c514637e6128a", "parents": [ "d027dffcc66f749ee34c74edbd77efaaea573e4d" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Mon Sep 03 16:50:42 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:32 2012 -0700" }, "message": "ext3: Fix fdatasync() for files with only i_size changes\n\ncommit 156bddd8e505b295540f3ca0e27dda68cb0d49aa upstream.\n\nCode tracking when transaction needs to be committed on fdatasync(2) forgets\nto handle a situation when only inode\u0027s i_size is changed. Thus in such\nsituations fdatasync(2) doesn\u0027t force transaction with new i_size to disk\nand that can result in wrong i_size after a crash.\n\nFix the issue by updating inode\u0027s i_datasync_tid whenever its size is\nupdated.\n\nReported-by: Kristian Nielsen \u003cknielsen@knielsen-hq.org\u003e\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d027dffcc66f749ee34c74edbd77efaaea573e4d", "tree": "68f4a5b6be19f40bd11b1cbe43efd623f4e775a5", "parents": [ "d3ed1731ba6bca32ac0ac96377cae8fd735e16e6" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Wed Sep 05 15:48:23 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:32 2012 -0700" }, "message": "udf: Fix data corruption for files in ICB\n\ncommit 9c2fc0de1a6e638fe58c354a463f544f42a90a09 upstream.\n\nWhen a file is stored in ICB (inode), we overwrite part of the file, and\nthe page containing file\u0027s data is not in page cache, we end up corrupting\nfile\u0027s data by overwriting them with zeros. The problem is we use\nsimple_write_begin() which simply zeroes parts of the page which are not\nwritten to. The problem has been introduced by be021ee4 (udf: convert to\nnew aops).\n\nFix the problem by providing a -\u003ewrite_begin function which makes the page\nproperly uptodate.\n\nReported-by: Ian Abbott \u003cabbotti@mev.co.uk\u003e\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d3ed1731ba6bca32ac0ac96377cae8fd735e16e6", "tree": "d0d470c33b743c71ea39df269bcafe4feffe5b4c", "parents": [ "7a4601c0bfde4ed50c54f30c32c5677e3daec4f9" ], "author": { "name": "James Bottomley", "email": "JBottomley@Parallels.com", "time": "Wed Jul 25 23:55:55 2012 +0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:32 2012 -0700" }, "message": "SCSI: Fix \u0027Device not ready\u0027 issue on mpt2sas\n\ncommit 14216561e164671ce147458653b1fea06a4ada1e upstream.\n\nThis is a particularly nasty SCSI ATA Translation Layer (SATL) problem.\n\nSAT-2 says (section 8.12.2)\n\n if the device is in the stopped state as the result of\n processing a START STOP UNIT command (see 9.11), then the SATL\n shall terminate the TEST UNIT READY command with CHECK CONDITION\n status with the sense key set to NOT READY and the additional\n sense code of LOGICAL UNIT NOT READY, INITIALIZING COMMAND\n REQUIRED;\n\nmpt2sas internal SATL seems to implement this. The result is very confusing\nstandby behaviour (using hdparm -y). If you suspend a drive and then send\nanother command, usually it wakes up. However, if the next command is a TEST\nUNIT READY, the SATL sees that the drive is suspended and proceeds to follow\nthe SATL rules for this, returning NOT READY to all subsequent commands. This\nmeans that the ordering of TEST UNIT READY is crucial: if you send TUR and\nthen a command, you get a NOT READY to both back. If you send a command and\nthen a TUR, you get GOOD status because the preceeding command woke the drive.\n\nThis bit us badly because\n\ncommit 85ef06d1d252f6a2e73b678591ab71caad4667bb\nAuthor: Tejun Heo \u003ctj@kernel.org\u003e\nDate: Fri Jul 1 16:17:47 2011 +0200\n\n block: flush MEDIA_CHANGE from drivers on close(2)\n\nChanged our ordering on TEST UNIT READY commands meaning that SATA drives\nconnected to an mpt2sas now suspend and refuse to wake (because the mpt2sas\nSATL sees the suspend *before* the drives get awoken by the next ATA command)\nresulting in lots of failed commands.\n\nThe standard is completely nuts forcing this inconsistent behaviour, but we\nhave to work around it.\n\nThe fix for this is twofold:\n\n 1. Set the allow_restart flag so we wake the drive when we see it has been\n suspended\n\n 2. Return all TEST UNIT READY status directly to the mid layer without any\n further error handling which prevents us causing error handling which\n may offline the device just because of a media check TUR.\n\nReported-by: Matthias Prager \u003clinux@matthiasprager.de\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Parallels.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7a4601c0bfde4ed50c54f30c32c5677e3daec4f9", "tree": "54dcd326a9b53c50fc085940ee0837c8ae36046e", "parents": [ "797efad403c63c9a94a8f78e06ccb3aa5b4980a9" ], "author": { "name": "sreekanth.reddy@lsi.com", "email": "sreekanth.reddy@lsi.com", "time": "Tue Jul 17 15:57:05 2012 +0530" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:25 2012 -0700" }, "message": "SCSI: mpt2sas: Fix for Driver oops, when loading driver with max_queue_depth command line option to a very small value\n\ncommit 338b131a3269881c7431234855c93c219b0979b6 upstream.\n\nIf the specified max_queue_depth setting is less than the\nexpected number of internal commands, then driver will calculate\nthe queue depth size to a negitive number. This negitive number\nis actually a very large number because variable is unsigned\n16bit integer. So, the driver will ask for a very large amount of\nmemory for message frames and resulting into oops as memory\nallocation routines will not able to handle such a large request.\n\nSo, in order to limit this kind of oops, The driver need to set\nthe max_queue_depth to a scsi mid layer\u0027s can_queue value. Then\nthe overall message frames required for IO is minimum of either\n(max_queue_depth plus internal commands) or the IOC global\ncredits.\n\nSigned-off-by: Sreekanth Reddy \u003csreekanth.reddy@lsi.com\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Parallels.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "797efad403c63c9a94a8f78e06ccb3aa5b4980a9", "tree": "314284c5c8419a8a2424ccb76dff06db27dfedee", "parents": [ "dc0c0a9fc1f7ce1051f144c749f75921085fc869" ], "author": { "name": "Mike Snitzer", "email": "snitzer@redhat.com", "time": "Thu May 31 15:05:33 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:23 2012 -0700" }, "message": "SCSI: scsi_lib: fix scsi_io_completion\u0027s SG_IO error propagation\n\ncommit 27c419739b67decced4650440829b8d51bef954b upstream.\n\nThe following v3.4-rc1 commit unmasked an existing bug in scsi_io_completion\u0027s\nSG_IO error handling: 47ac56d [SCSI] scsi_error: classify some ILLEGAL_REQUEST\nsense as a permanent TARGET_ERROR\n\nGiven that certain ILLEGAL_REQUEST are now properly categorized as\nTARGET_ERROR the host_byte is being set (before host_byte wasn\u0027t ever\nset for these ILLEGAL_REQUEST).\n\nIn scsi_io_completion, initialize req-\u003eerrors with cmd-\u003eresult _after_\nthe SG_IO block that calls __scsi_error_from_host_byte (which may\nmodify the host_byte).\n\nBefore this fix:\n\n cdb to send: 12 01 01 00 00 00\nioctl(3, SG_IO, {\u0027S\u0027, SG_DXFER_NONE, cmd[6]\u003d[12, 01, 01, 00, 00, 00],\n mx_sb_len\u003d32, iovec_count\u003d0, dxfer_len\u003d0, timeout\u003d20000, flags\u003d0,\n status\u003d02, masked_status\u003d01, sb[19]\u003d[70, 00, 05, 00, 00, 00, 00, 0b,\n 00, 00, 00, 00, 24, 00, 00, 00, 00, 00, 00], host_status\u003d0x10,\n driver_status\u003d0x8, resid\u003d0, duration\u003d0, info\u003d0x1}) \u003d 0\nSCSI Status: Check Condition\n\nSense Information:\nsense buffer empty\n\nAfter:\n\n cdb to send: 12 01 01 00 00 00\nioctl(3, SG_IO, {\u0027S\u0027, SG_DXFER_NONE, cmd[6]\u003d[12, 01, 01, 00, 00, 00],\n mx_sb_len\u003d32, iovec_count\u003d0, dxfer_len\u003d0, timeout\u003d20000, flags\u003d0,\n status\u003d02, masked_status\u003d01, sb[19]\u003d[70, 00, 05, 00, 00, 00, 00, 0b,\n 00, 00, 00, 00, 24, 00, 00, 00, 00, 00, 00], host_status\u003d0,\n driver_status\u003d0x8, resid\u003d0, duration\u003d0, info\u003d0x1}) \u003d 0\nSCSI Status: Check Condition\n\nSense Information:\n Fixed format, current; Sense key: Illegal Request\n Additional sense: Invalid field in cdb\n Raw sense data (in hex):\n 70 00 05 00 00 00 00 0b 00 00 00 00 24 00 00 00\n 00 00 00\n\nReported-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\nTested-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nReviewed-by: Babu Moger \u003cbabu.moger@netapp.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Parallels.com\u003e\n\n" }, { "commit": "dc0c0a9fc1f7ce1051f144c749f75921085fc869", "tree": "d1d97b92ce5acde590421938ca9383a0ec6e1737", "parents": [ "43da476d7f734a1b55680668246d0237dde4ea57" ], "author": { "name": "Kashyap Desai", "email": "Kashyap.Desai@lsi.com", "time": "Tue Jul 17 18:20:44 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:23 2012 -0700" }, "message": "SCSI: megaraid_sas: Move poll_aen_lock initializer\n\ncommit bd8d6dd43a77bfd2b8fef5b094b9d6095e169dee upstream.\n\nThe following patch moves the poll_aen_lock initializer from\nmegasas_probe_one() to megasas_init(). This prevents a crash when a user\nloads the driver and tries to issue a poll() system call on the ioctl\ninterface with no adapters present.\n\nSigned-off-by: Kashyap Desai \u003cKashyap.Desai@lsi.com\u003e\nSigned-off-by: Adam Radford \u003caradford@gmail.com\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Parallels.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "43da476d7f734a1b55680668246d0237dde4ea57", "tree": "109cac684c7f88772dcf89779f863730e70907ad", "parents": [ "05d71a5a25da396f76ee942af6682dfaecc73e84" ], "author": { "name": "Mikulas Patocka", "email": "mpatocka@redhat.com", "time": "Sat Sep 01 12:34:07 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:23 2012 -0700" }, "message": "Fix order of arguments to compat_put_time[spec|val]\n\ncommit ed6fe9d614fc1bca95eb8c0ccd0e92db00ef9d5d upstream.\n\nCommit 644595f89620 (\"compat: Handle COMPAT_USE_64BIT_TIME in\nnet/socket.c\") introduced a bug where the helper functions to take\neither a 64-bit or compat time[spec|val] got the arguments in the wrong\norder, passing the kernel stack pointer off as a user pointer (and vice\nversa).\n\nBecause of the user address range check, that in turn then causes an\nEFAULT due to the user pointer range checking failing for the kernel\naddress. Incorrectly resuling in a failed system call for 32-bit\nprocesses with a 64-bit kernel.\n\nOn odder architectures like HP-PA (with separate user/kernel address\nspaces), it can be used read kernel memory.\n\nSigned-off-by: Mikulas Patocka \u003cmpatocka@redhat.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "05d71a5a25da396f76ee942af6682dfaecc73e84", "tree": "de2b299e87d121de753838be8285f9d1dc7f25e5", "parents": [ "242fa18ad8d4665c151bdd5c34ac34a8e701fff7" ], "author": { "name": "Dave Jones", "email": "davej@redhat.com", "time": "Thu Sep 06 12:01:00 2012 -0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Fri Sep 14 10:00:22 2012 -0700" }, "message": "Remove user-triggerable BUG from mpol_to_str\n\ncommit 80de7c3138ee9fd86a98696fd2cf7ad89b995d0a upstream.\n\nTrivially triggerable, found by trinity:\n\n kernel BUG at mm/mempolicy.c:2546!\n Process trinity-child2 (pid: 23988, threadinfo ffff88010197e000, task ffff88007821a670)\n Call Trace:\n show_numa_map+0xd5/0x450\n show_pid_numa_map+0x13/0x20\n traverse+0xf2/0x230\n seq_read+0x34b/0x3e0\n vfs_read+0xac/0x180\n sys_pread64+0xa2/0xc0\n system_call_fastpath+0x1a/0x1f\n RIP: mpol_to_str+0x156/0x360\n\nSigned-off-by: Dave Jones \u003cdavej@redhat.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" } ], "next": "242fa18ad8d4665c151bdd5c34ac34a8e701fff7" }