)]}' { "log": [ { "commit": "b9bf60ac3e3779d4ffa03daceebf59df7b46c224", "tree": "92b29a20a04ca4aab9b8cf52fd4b3b99371add87", "parents": [ "8c2223fc19032e7b8761e46c15e1ed167a252285" ], "author": { "name": "Cong Wang", "email": "amwang@redhat.com", "time": "Thu Feb 21 23:32:27 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:06 2013 -0800" }, "message": "vlan: adjust vlan_set_encap_proto() for its callers\n\n[ Upstream commit da8c87241c26aac81a64c7e4d21d438a33018f4e ]\n\nThere are two places to call vlan_set_encap_proto():\nvlan_untag() and __pop_vlan_tci().\n\nvlan_untag() assumes skb-\u003edata points after mac addr, otherwise\nthe following code\n\n vhdr \u003d (struct vlan_hdr *) skb-\u003edata;\n vlan_tci \u003d ntohs(vhdr-\u003eh_vlan_TCI);\n __vlan_hwaccel_put_tag(skb, vlan_tci);\n\n skb_pull_rcsum(skb, VLAN_HLEN);\n\nwon\u0027t be correct. But __pop_vlan_tci() assumes points _before_\nmac addr.\n\nIn vlan_set_encap_proto(), it looks for some magic L2 value\nafter mac addr:\n\n rawp \u003d skb-\u003edata;\n if (*(unsigned short *) rawp \u003d\u003d 0xFFFF)\n\t...\n\nTherefore __pop_vlan_tci() is obviously wrong.\n\nA quick fix is avoiding using skb-\u003edata in vlan_set_encap_proto(),\nuse \u0027vhdr+1\u0027 is always correct in both cases.\n\nSigned-off-by: Cong Wang \u003camwang@redhat.com\u003e\nCc: David S. Miller \u003cdavem@davemloft.net\u003e\nCc: Jesse Gross \u003cjesse@nicira.com\u003e\nAcked-by: Jesse Gross \u003cjesse@nicira.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "8c2223fc19032e7b8761e46c15e1ed167a252285", "tree": "0054de1a82d88309207385e115d051179b583578", "parents": [ "e5a096aa0aeb1fc8ad8b3d6bd70d322a0d65edc4" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Sat Feb 23 01:13:47 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:06 2013 -0800" }, "message": "sock_diag: Fix out-of-bounds access to sock_diag_handlers[]\n\n[ Upstream commit 6e601a53566d84e1ffd25e7b6fe0b6894ffd79c0 ]\n\nUserland can send a netlink message requesting SOCK_DIAG_BY_FAMILY\nwith a family greater or equal then AF_MAX -- the array size of\nsock_diag_handlers[]. The current code does not test for this\ncondition therefore is vulnerable to an out-of-bound access opening\ndoors for a privilege escalation.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nAcked-by: Eric Dumazet \u003cedumazet@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "e5a096aa0aeb1fc8ad8b3d6bd70d322a0d65edc4", "tree": "d5055028b4ac0b56b49b6d65237038c5c7f46778", "parents": [ "785e5dce256ea5bdf4871af13f9908b74264b515" ], "author": { "name": "Eric Dumazet", "email": "edumazet@google.com", "time": "Thu Feb 21 12:18:52 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:06 2013 -0800" }, "message": "ipv6: use a stronger hash for tcp\n\n[ Upstream commit 08dcdbf6a7b9d14c2302c5bd0c5390ddf122f664 ]\n\nIt looks like its possible to open thousands of TCP IPv6\nsessions on a server, all landing in a single slot of TCP hash\ntable. Incoming packets have to lookup sockets in a very\nlong list.\n\nWe should hash all bits from foreign IPv6 addresses, using\na salt and hash mix, not a simple XOR.\n\ninet6_ehashfn() can also separately use the ports, instead\nof xoring them.\n\nReported-by: Neal Cardwell \u003cncardwell@google.com\u003e\nSigned-off-by: Eric Dumazet \u003cedumazet@google.com\u003e\nCc: Yuchung Cheng \u003cycheng@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "785e5dce256ea5bdf4871af13f9908b74264b515", "tree": "f4ca23b59e0623fe10600a1a7b8b6d63279986ff", "parents": [ "1e6b5fb5ce92028f6c87864712ed7290446a4c11" ], "author": { "name": "Li Wei", "email": "lw@cn.fujitsu.com", "time": "Thu Feb 21 00:09:54 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:06 2013 -0800" }, "message": "ipv4: fix a bug in ping_err().\n\n[ Upstream commit b531ed61a2a2a77eeb2f7c88b49aa5ec7d9880d8 ]\n\nWe should get \u0027type\u0027 and \u0027code\u0027 from the outer ICMP header.\n\nSigned-off-by: Li Wei \u003clw@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": "1e6b5fb5ce92028f6c87864712ed7290446a4c11", "tree": "0426fe2c4e1f79732c2957659a0adc6e4476cdcb", "parents": [ "29b3bb0be43fea0a49e5235894e1dcbc0ac299dc" ], "author": { "name": "Ying Xue", "email": "ying.xue@windriver.com", "time": "Fri Feb 15 22:28:25 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:06 2013 -0800" }, "message": "net: fix a compile error when SOCK_REFCNT_DEBUG is enabled\n\n[ Upstream commit dec34fb0f5b7873de45132a84a3af29e61084a6b ]\n\nWhen SOCK_REFCNT_DEBUG is enabled, below build error is met:\n\nkernel/sysctl_binary.o: In function `sk_refcnt_debug_release\u0027:\ninclude/net/sock.h:1025: multiple definition of `sk_refcnt_debug_release\u0027\nkernel/sysctl.o:include/net/sock.h:1025: first defined here\nkernel/audit.o: In function `sk_refcnt_debug_release\u0027:\ninclude/net/sock.h:1025: multiple definition of `sk_refcnt_debug_release\u0027\nkernel/sysctl.o:include/net/sock.h:1025: first defined here\nmake[1]: *** [kernel/built-in.o] Error 1\nmake: *** [kernel] Error 2\n\nSo we decide to make sk_refcnt_debug_release static to eliminate\nthe error.\n\nSigned-off-by: Ying Xue \u003cying.xue@windriver.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "29b3bb0be43fea0a49e5235894e1dcbc0ac299dc", "tree": "cee0a17f0637f7d2d7eb308d08163ccaf5cb12b0", "parents": [ "320c1509197bce83d2ebb45d4cc5f9b4d91c05dc" ], "author": { "name": "David Vrabel", "email": "david.vrabel@citrix.com", "time": "Thu Feb 14 03:18:58 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:06 2013 -0800" }, "message": "xen-netback: cancel the credit timer when taking the vif down\n\n[ Upstream commit 3e55f8b306cf305832a4ac78aa82e1b40e818ece ]\n\nIf the credit timer is left armed after calling\nxen_netbk_remove_xenvif(), then it may fire and attempt to schedule\nthe vif which will then oops as vif-\u003enetbk \u003d\u003d NULL.\n\nThis may happen both in the fatal error path and during normal\ndisconnection from the front end.\n\nThe sequencing during shutdown is critical to ensure that: a)\nvif-\u003enetbk doesn\u0027t become unexpectedly NULL; and b) the net device/vif\nis not freed.\n\n1. Mark as unschedulable (netif_carrier_off()).\n2. Synchronously cancel the timer.\n3. Remove the vif from the schedule list.\n4. Remove it from it netback thread group.\n5. Wait for vif-\u003erefcnt to become 0.\n\nSigned-off-by: David Vrabel \u003cdavid.vrabel@citrix.com\u003e\nAcked-by: Ian Campbell \u003cian.campbell@citrix.com\u003e\nReported-by: Christopher S. Aker \u003ccaker@theshore.net\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "320c1509197bce83d2ebb45d4cc5f9b4d91c05dc", "tree": "464087cfc79fa5369e00e98321039e4ada9cdb70", "parents": [ "b5428e471b91192a2438d04c1d2ff2b3d4708366" ], "author": { "name": "David Vrabel", "email": "david.vrabel@citrix.com", "time": "Thu Feb 14 03:18:57 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:06 2013 -0800" }, "message": "xen-netback: correctly return errors from netbk_count_requests()\n\n[ Upstream commit 35876b5ffc154c357476b2c3bdab10feaf4bd8f0 ]\n\nnetbk_count_requests() could detect an error, call\nnetbk_fatal_tx_error() but return 0. The vif may then be used\nafterwards (e.g., in a call to netbk_tx_error().\n\nSince netbk_fatal_tx_error() could set vif-\u003erefcnt to 1, the vif may\nbe freed immediately after the call to netbk_fatal_tx_error() (e.g.,\nif the vif is also removed).\n\nNetback thread Xenwatch thread\n-------------------------------------------\nnetbk_fatal_tx_err() netback_remove()\n xenvif_disconnect()\n ...\n free_netdev()\nnetbk_tx_err() Oops!\n\nSigned-off-by: Wei Liu \u003cwei.liu2@citrix.com\u003e\nSigned-off-by: Jan Beulich \u003cJBeulich@suse.com\u003e\nSigned-off-by: David Vrabel \u003cdavid.vrabel@citrix.com\u003e\nReported-by: Christopher S. Aker \u003ccaker@theshore.net\u003e\nAcked-by: Ian Campbell \u003cian.campbell@citrix.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "b5428e471b91192a2438d04c1d2ff2b3d4708366", "tree": "e1a3431cc3f210338fae06ced15b266352544d56", "parents": [ "6e95f970d1cb6801b5f26d2c167fb1e0ad6c5dba" ], "author": { "name": "Eric Dumazet", "email": "edumazet@google.com", "time": "Tue Feb 12 06:16:53 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:06 2013 -0800" }, "message": "net: fix infinite loop in __skb_recv_datagram()\n\n[ Upstream commit 77c1090f94d1b0b5186fb13a1b71b47b1343f87f ]\n\nTommi was fuzzing with trinity and reported the following problem :\n\ncommit 3f518bf745 (datagram: Add offset argument to __skb_recv_datagram)\nmissed that a raw socket receive queue can contain skbs with no payload.\n\nWe can loop in __skb_recv_datagram() with MSG_PEEK mode, because\nwait_for_packet() is not prepared to skip these skbs.\n\n[ 83.541011] INFO: rcu_sched detected stalls on CPUs/tasks: {}\n(detected by 0, t\u003d26002 jiffies, g\u003d27673, c\u003d27672, q\u003d75)\n[ 83.541011] INFO: Stall ended before state dump start\n[ 108.067010] BUG: soft lockup - CPU#0 stuck for 22s! [trinity-child31:2847]\n...\n[ 108.067010] Call Trace:\n[ 108.067010] [\u003cffffffff818cc103\u003e] __skb_recv_datagram+0x1a3/0x3b0\n[ 108.067010] [\u003cffffffff818cc33d\u003e] skb_recv_datagram+0x2d/0x30\n[ 108.067010] [\u003cffffffff819ed43d\u003e] rawv6_recvmsg+0xad/0x240\n[ 108.067010] [\u003cffffffff818c4b04\u003e] sock_common_recvmsg+0x34/0x50\n[ 108.067010] [\u003cffffffff818bc8ec\u003e] sock_recvmsg+0xbc/0xf0\n[ 108.067010] [\u003cffffffff818bf31e\u003e] sys_recvfrom+0xde/0x150\n[ 108.067010] [\u003cffffffff81ca4329\u003e] system_call_fastpath+0x16/0x1b\n\nReported-by: Tommi Rantala \u003ctt.rantala@gmail.com\u003e\nTested-by: Tommi Rantala \u003ctt.rantala@gmail.com\u003e\nSigned-off-by: Eric Dumazet \u003cedumazet@google.com\u003e\nCc: Pavel Emelyanov \u003cxemul@parallels.com\u003e\nAcked-by: Pavel Emelyanov \u003cxemul@parallels.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "6e95f970d1cb6801b5f26d2c167fb1e0ad6c5dba", "tree": "478d6b2bc46eba7e68ffcfe3054cac491f404eea", "parents": [ "a9115fba99247ad51211beb3ffd23b6553c80ee9" ], "author": { "name": "Stephen Hemminger", "email": "stephen@networkplumber.org", "time": "Mon Feb 11 08:22:22 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:05 2013 -0800" }, "message": "bridge: set priority of STP packets\n\n[ Upstream commit 547b4e718115eea74087e28d7fa70aec619200db ]\n\nSpanning Tree Protocol packets should have always been marked as\ncontrol packets, this causes them to get queued in the high prirority\nFIFO. As Radia Perlman mentioned in her LCA talk, STP dies if bridge\ngets overloaded and can\u0027t communicate. This is a long-standing bug back\nto the first versions of Linux bridge.\n\nSigned-off-by: Stephen Hemminger \u003cstephen@networkplumber.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "a9115fba99247ad51211beb3ffd23b6553c80ee9", "tree": "c3a4e28f8f5058e9e304977ba1d575c43ea0fc3b", "parents": [ "6a924a76039689fd260ee311b85fb2202bcd4910" ], "author": { "name": "David Herrmann", "email": "dh.herrmann@gmail.com", "time": "Mon Feb 18 01:47:15 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:05 2013 -0800" }, "message": "HID: wiimote: fix nunchuck button parser\n\ncommit 89bdd0c6f38ccf0de43d5a36ede384a730f3394e upstream.\n\nThe buttons of the Wii Remote Nunchuck extension are actually active low.\nFix the parser to forward the inverted values. The comment in the function\nalways said \"0 \u003d\u003d pressed\" but the implementation was wrong from the\nbeginning.\n\nReported-by: Victor Quicksilver \u003cvictor.quicksilver@gmail.com\u003e\nSigned-off-by: David Herrmann \u003cdh.herrmann@gmail.com\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6a924a76039689fd260ee311b85fb2202bcd4910", "tree": "68acd397b3703d2ede27a55584196efd4c4d6f6e", "parents": [ "f515e1d59602f8eafaad39b6842bd823ad34654e" ], "author": { "name": "Shawn Guo", "email": "shawn.guo@linaro.org", "time": "Tue Jan 15 23:30:27 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:05 2013 -0800" }, "message": "mmc: sdhci-esdhc-imx: fix host version read\n\ncommit ef4d0888bb7e1b963880f086575081c3d39cad2d upstream.\n\nWhen commit 95a2482 (mmc: sdhci-esdhc-imx: add basic imx6q usdhc\nsupport) works around host version issue on imx6q, it gets the\nregister address fixup \"reg ^\u003d 2\" lost for imx25/35/51/53 esdhc.\nThus, the controller version on these SoCs is wrongly identified\nas v1 while it\u0027s actually v2.\n\nAdd the address fixup back and take a different approach to correct\nimx6q host version, so that the host version read gets back to work\nfor all SoCs.\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": "f515e1d59602f8eafaad39b6842bd823ad34654e", "tree": "48d183d9d59e79c35719953ef85b489641f4e598", "parents": [ "c30b55c385288be48f7accd16a6929ad4d983311" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Fri Jan 25 10:28:18 2013 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:05 2013 -0800" }, "message": "fb: Yet another band-aid for fixing lockdep mess\n\ncommit e93a9a868792ad71cdd09d75e5a02d8067473c4e upstream.\n\nI\u0027ve still got lockdep warnings even after Alan\u0027s patch, and it seems that\nyet more band aids are required to paper over similar paths for\nunbind_con_driver() and unregister_con_driver(). After this hack, lockdep\nwarnings are finally gone.\n\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nCc: Alan Cox \u003calan@linux.intel.com\u003e\nCc: Florian Tobias Schandinat \u003cFlorianSchandinat@gmx.de\u003e\nCc: Jiri Kosina \u003cjkosina@suse.cz\u003e\nTested-by: Sedat Dilek \u003csedat.dilek@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "c30b55c385288be48f7accd16a6929ad4d983311", "tree": "1588731963ecab2c47c3999d7691a095ab591d0e", "parents": [ "62a3dcc78d04dcd84276eaa7a40dec1066054532" ], "author": { "name": "Alan Cox", "email": "alan@linux.intel.com", "time": "Fri Jan 25 10:28:15 2013 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:05 2013 -0800" }, "message": "fb: rework locking to fix lock ordering on takeover\n\ncommit 50e244cc793d511b86adea24972f3a7264cae114 upstream.\n\nAdjust the console layer to allow a take over call where the caller\nalready holds the locks. Make the fb layer lock in order.\n\nThis is partly a band aid, the fb layer is terminally confused about the\nlocking rules it uses for its notifiers it seems.\n\n[akpm@linux-foundation.org: remove stray non-ascii char, tidy comment]\n[akpm@linux-foundation.org: export do_take_over_console()]\n[airlied: cleanup another non-ascii char]\nSigned-off-by: Alan Cox \u003calan@linux.intel.com\u003e\nCc: Florian Tobias Schandinat \u003cFlorianSchandinat@gmx.de\u003e\nCc: Stephen Rothwell \u003csfr@canb.auug.org.au\u003e\nCc: Jiri Kosina \u003cjkosina@suse.cz\u003e\nTested-by: Sedat Dilek \u003csedat.dilek@gmail.com\u003e\nReviewed-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "62a3dcc78d04dcd84276eaa7a40dec1066054532", "tree": "b4aada491b65d9ea400cffdf69dedd9c0424dd12", "parents": [ "0bbdba111a75875890290150333c07f2d79b160a" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Thu Jan 24 16:12:41 2013 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:05 2013 -0800" }, "message": "fbcon: don\u0027t lose the console font across generic-\u003echip driver switch\n\ncommit ae1287865f5361fa138d4d3b1b6277908b54eac9 upstream.\n\nIf grub2 loads efifb/vesafb, then when systemd starts it can set the console\nfont on that framebuffer device, however when we then load the native KMS\ndriver, the first thing it does is tear down the generic framebuffer driver.\n\nThe thing is the generic code is doing the right thing, it frees the font\nbecause otherwise it would leak memory. However we can assume that if you\nare removing the generic firmware driver (vesa/efi/offb), that a new driver\n*should* be loading soon after, so we effectively leak the font.\n\nHowever the old code left a dangling pointer in vc-\u003evc_font.data and we\ncan now reuse that dangling pointer to load the font into the new\ndriver, now that we aren\u0027t freeing it.\n\nBugzilla: https://bugzilla.redhat.com/show_bug.cgi?id\u003d892340\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nCc: Kay Sievers \u003ckay.sievers@vrfy.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0bbdba111a75875890290150333c07f2d79b160a", "tree": "943bf4088cabc596c10b7776db0ec8776f3ec20c", "parents": [ "aa3fc3566478493f635d265731d81a3defcef98d" ], "author": { "name": "Anatolij Gustschin", "email": "agust@denx.de", "time": "Thu Jan 17 21:28:37 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:05 2013 -0800" }, "message": "drivers/video: fsl-diu-fb: fix pixel formats for 24 and 16 bpp\n\ncommit 5d3cc311a76073f6e0a27c0752f7e41f69e95ea7 upstream.\n\nFramebuffer colors for 24 and 16 bpp are currently wrong. The order\nof the color component arguments in the MAKE_PF() is not natural\nand causes some confusion. The generated pixel format values for 24\nand 16 bpp depths do not much the values in the comments.\n\nFix the macro arguments to be in the natural RGB order and adjust\nthe arguments for all depths to generate correct pixel format values\n(equal to the values mentioned in the comments).\n\nSigned-off-by: Anatolij Gustschin \u003cagust@denx.de\u003e\nCc: Timur Tabi \u003ctimur@tabi.org\u003e\nAcked-by: Timur Tabi \u003ctimur@freescale.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "aa3fc3566478493f635d265731d81a3defcef98d", "tree": "173e3e5880d328049cf6310a8eb39a31fc26e671", "parents": [ "49e8ae95b16fbc66b630b50ad3a18273b9342a06" ], "author": { "name": "Jean Delvare", "email": "khali@linux-fr.org", "time": "Sun Dec 16 22:00:50 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:05 2013 -0800" }, "message": "pcmcia/vrc4171: Add missing spinlock init\n\ncommit 811af9723859884f2f771f3174f3ddedab7c53b5 upstream.\n\nIt doesn\u0027t seem this spinlock was properly initialized. This bug was\nintroduced by commit 7a410e8d4d97457c8c381e2de9cdc7bd3306badc.\n\nSigned-off-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "49e8ae95b16fbc66b630b50ad3a18273b9342a06", "tree": "40a8447c990c49e5e353198d8b6934d55c64705b", "parents": [ "25c3a0840c99270041487907b6365cb5bfc8a03f" ], "author": { "name": "John David Anglin", "email": "dave.anglin@bell.net", "time": "Mon Jan 14 19:45:00 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:05 2013 -0800" }, "message": "Purge existing TLB entries in set_pte_at and ptep_set_wrprotect\n\ncommit 7139bc1579901b53db7e898789e916ee2fb52d78 upstream.\n\nThis patch goes a long way toward fixing the minifail bug, and\nit  significantly improves the stability of SMP machines such as\nthe rp3440.  When write  protecting a page for COW, we need to\npurge the existing translation.  Otherwise, the COW break\ndoesn\u0027t occur as expected because the TLB may still have a stale entry\nwhich allows writes.\n\n[jejb: fix up checkpatch errors]\nSigned-off-by: John David Anglin \u003cdave.anglin@bell.net\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Parallels.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "25c3a0840c99270041487907b6365cb5bfc8a03f", "tree": "41ec36436d91aba18a591b87c61f8d8a8045fbcb", "parents": [ "27c303244ef8049be6fd8088230c7f5e02a522b3" ], "author": { "name": "Phileas Fogg", "email": "phileas-fogg@mail.ru", "time": "Sat Feb 23 00:32:19 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:04 2013 -0800" }, "message": "powerpc/kexec: Disable hard IRQ before kexec\n\ncommit 8520e443aa56cc157b015205ea53e7b9fc831291 upstream.\n\nDisable hard IRQ before kexec a new kernel image.\nNot doing it can result in corrupted data in the memory segments\nreserved for the new kernel.\n\nSigned-off-by: Phileas Fogg \u003cphileas-fogg@mail.ru\u003e\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "27c303244ef8049be6fd8088230c7f5e02a522b3", "tree": "ccb85f0306747f1b44f919fc798d36bc70d2cd1e", "parents": [ "cae53e2a9a03e53152fdd331067923f7d65fc72e" ], "author": { "name": "Joonsoo Kim", "email": "js1304@gmail.com", "time": "Sat Feb 09 05:52:45 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:04 2013 -0800" }, "message": "ARM: 7643/1: sched: correct update_sched_clock()\n\ncommit 7c4e9ced424be4d36df6a3e3825763e97ee97607 upstream.\n\nIf we want load epoch_cyc and epoch_ns atomically,\nwe should update epoch_cyc_copy first of all.\nThis notify reader that updating is in progress.\n\nIf we update epoch_cyc first like as current implementation,\nthere is subtle error case.\nLook at the below example.\n\n\u003cInitial Condition\u003e\ncyc \u003d 9\nns \u003d 900\ncyc_copy \u003d 9\n\n\u003d\u003d CASE 1 \u003d\u003d\n\u003cCPU A \u003d reader\u003e \u003cCPU B \u003d updater\u003e\n write cyc \u003d 10\nread cyc \u003d 10\nread ns \u003d 900\n write ns \u003d 1000\n write cyc_copy \u003d 10\nread cyc_copy \u003d 10\n\noutput \u003d (10, 900)\n\n\u003d\u003d CASE 2 \u003d\u003d\n\u003cCPU A \u003d reader\u003e \u003cCPU B \u003d updater\u003e\nread cyc \u003d 9\n write cyc \u003d 10\n write ns \u003d 1000\nread ns \u003d 1000\nread cyc_copy \u003d 9\n write cyc_copy \u003d 10\noutput \u003d (9, 1000)\n\nIf atomic read is ensured, output should be (9, 900) or (10, 1000).\nBut, output in example case are not.\n\nSo, change updating sequence in order to correct this problem.\n\nSigned-off-by: Joonsoo Kim \u003ciamjoonsoo.kim@lge.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": "cae53e2a9a03e53152fdd331067923f7d65fc72e", "tree": "03760f8c8c2e82b207a45d1da5c6babc5c31297a", "parents": [ "76753d39bf46abf7e37df89e2258bef933bb2207" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Tue Jan 08 21:58:31 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:04 2013 -0800" }, "message": "ARM: samsung: fix assembly syntax for new gas\n\ncommit 2815774bb38445006074e16251b9ef5123bdc616 upstream.\n\nRecent assembler versions complain about extraneous\nwhitespace inside [] brackets. This fixes all of\nthese instances for the samsung platforms. We should\nbackport this to all kernels that might need to\nbe built with new binutils.\n\narch/arm/kernel/entry-armv.S: Assembler messages:\narch/arm/kernel/entry-armv.S:214: Error: ARM register expected -- `ldr r2,[ r6,#(0x10)]\u0027\narch/arm/kernel/entry-armv.S:214: Error: ARM register expected -- `ldr r0,[ r6,#(0x14)]\u0027\narch/arm/kernel/entry-armv.S:430: Error: ARM register expected -- `ldr r2,[ r6,#(0x10)]\u0027\narch/arm/kernel/entry-armv.S:430: Error: ARM register expected -- `ldr r0,[ r6,#(0x14)]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2410.S: Assembler messages:\narch/arm/mach-s3c24xx/sleep-s3c2410.S:48: Error: ARM register expected -- `ldr r7,[ r4 ]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2410.S:49: Error: ARM register expected -- `ldr r8,[ r5 ]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2410.S:50: Error: ARM register expected -- `ldr r9,[ r6 ]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2410.S:64: Error: ARM register expected -- `streq r7,[ r4 ]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2410.S:65: Error: ARM register expected -- `streq r8,[ r5 ]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2410.S:66: Error: ARM register expected -- `streq r9,[ r6 ]\u0027\narch/arm/kernel/debug.S: Assembler messages:\narch/arm/kernel/debug.S:83: Error: ARM register expected -- `ldr r2,[ r2,#((0x0B0)+(((0x56000000)-(0x50000000))+(0xF6000000+(0x01000000))))-((0)+(((0x56000000)-(0x50000000))+(0xF6000000+(0x01000000))))]\u0027\narch/arm/kernel/debug.S:83: Error: ARM register expected -- `ldr r2,[ r3,#(0x18)]\u0027\narch/arm/kernel/debug.S:85: Error: ARM register expected -- `ldr r2,[ r2,#((0x0B0)+(((0x56000000)-(0x50000000))+(0xF6000000+(0x01000000))))-((0)+(((0x56000000)-(0x50000000))+(0xF6000000+(0x01000000))))]\u0027\narch/arm/kernel/debug.S:85: Error: ARM register expected -- `ldr r2,[ r3,#(0x18)]\u0027\narch/arm/mach-s3c24xx/pm-h1940.S: Assembler messages:\narch/arm/mach-s3c24xx/pm-h1940.S:33: Error: ARM register expected -- `ldr pc,[ r0,#((0x0B8)+(((0x56000000)-(0x50000000))+(0xF6000000+(0x01000000))))-(((0x56000000)-(0x50000000))+(0xF6000000+(0x01000000)))]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2412.S: Assembler messages:\narch/arm/mach-s3c24xx/sleep-s3c2412.S:60: Error: ARM register expected -- `ldrne r9,[ r1 ]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2412.S:61: Error: ARM register expected -- `strne r9,[ r1 ]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2412.S:62: Error: ARM register expected -- `ldrne r9,[ r2 ]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2412.S:63: Error: ARM register expected -- `strne r9,[ r2 ]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2412.S:64: Error: ARM register expected -- `ldrne r9,[ r3 ]\u0027\narch/arm/mach-s3c24xx/sleep-s3c2412.S:65: Error: ARM register expected -- `strne r9,[ r3 ]\u0027\narch/arm/kernel/debug.S:83: Error: ARM register expected -- `ldr r2,[ r3,#(0x08)]\u0027\narch/arm/kernel/debug.S:83: Error: ARM register expected -- `ldr r2,[ r3,#(0x18)]\u0027\narch/arm/kernel/debug.S:83: Error: ARM register expected -- `ldr r2,[ r3,#(0x10)]\u0027\narch/arm/kernel/debug.S:85: Error: ARM register expected -- `ldr r2,[ r3,#(0x08)]\u0027\narch/arm/kernel/debug.S:85: Error: ARM register expected -- `ldr r2,[ r3,#(0x18)]\u0027\narch/arm/kernel/debug.S:85: Error: ARM register expected -- `ldr r2,[ r3,#(0x10)]\u0027\n\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nAcked-by: Kukjin Kim \u003ckgene.kim@samsung.com\u003e\nCc: Ben Dooks \u003cben-linux@fluff.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "76753d39bf46abf7e37df89e2258bef933bb2207", "tree": "fdaead7e4c9977dac8a2c975672edfc89ac0b534", "parents": [ "03e578b9213094935c692d5728229cc8c0df0fd6" ], "author": { "name": "Igor Grinberg", "email": "grinberg@compulab.co.il", "time": "Sun Jan 13 13:49:47 2013 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:04 2013 -0800" }, "message": "ARM: PXA3xx: program the CSMSADRCFG register\n\ncommit d107a204154ddd79339203c2deeb7433f0cf6777 upstream.\n\nThe Chip Select Configuration Register must be programmed to 0x2 in\norder to achieve the correct behavior of the Static Memory Controller.\n\nWithout this patch devices wired to DFI and accessed through SMC cannot\nbe accessed after resume from S2.\n\nDo not rely on the boot loader to program the CSMSADRCFG register by\nprogramming it in the kernel smemc module.\n\nSigned-off-by: Igor Grinberg \u003cgrinberg@compulab.co.il\u003e\nAcked-by: Eric Miao \u003ceric.y.miao@gmail.com\u003e\nSigned-off-by: Haojian Zhuang \u003chaojian.zhuang@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "03e578b9213094935c692d5728229cc8c0df0fd6", "tree": "07105225551a8128cf074419558664cebaf47883", "parents": [ "4aee4099c7309d0610cf857d9d02d27ebfeb1b95" ], "author": { "name": "Chris Rattray", "email": "crattray@opensource.wolfsonmicro.com", "time": "Fri Feb 01 15:51:41 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:04 2013 -0800" }, "message": "ASoC: wm2200: correct IN2L and IN3L digital mute\n\ncommit 0d2b6422529a26ac4dee06196524ba9da70cf735 upstream.\n\nSigned-off-by: Chris Rattray \u003ccrattray@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "4aee4099c7309d0610cf857d9d02d27ebfeb1b95", "tree": "3b7a1cf31e1e02256806de561ff8d9dad190f696", "parents": [ "59959c9505e28cc7b9ead416cb064b4e56ba7dd5" ], "author": { "name": "Malcolm Priestley", "email": "tvboxspy@gmail.com", "time": "Wed Jan 30 20:07:29 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:04 2013 -0800" }, "message": "staging: vt6656: Fix URB submitted while active warning.\n\ncommit ae5943de8c8c4438cbac5cda599ff0b88c224468 upstream.\n\nThis error happens because PIPEnsControlOut and PIPEnsControlIn unlock the\nspin lock for delay, letting in another thread.\n\nThe patch moves the current MP_SET_FLAG to before filling\nof sUsbCtlRequest for pControlURB and clears it in event of failing.\n\nAny thread calling either function while fMP_CONTROL_READS or fMP_CONTROL_WRITES\nflags set will return STATUS_FAILURE.\n\nSigned-off-by: Malcolm Priestley \u003ctvboxspy@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "59959c9505e28cc7b9ead416cb064b4e56ba7dd5", "tree": "6de0bff8e4386df0e47c59aa4bb29c36dc15102d", "parents": [ "a143ae690fbf24c2473d5c7c42875c29e150bd13" ], "author": { "name": "Ian Abbott", "email": "abbotti@mev.co.uk", "time": "Mon Jan 28 16:14:31 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:04 2013 -0800" }, "message": "staging: comedi: disallow COMEDI_DEVCONFIG on non-board minors\n\ncommit 754ab5c0e55dd118273ca2c217c4d95e9fbc8259 upstream.\n\nComedi has two sorts of minor devices:\n(a) normal board minor devices in the range 0 to\nCOMEDI_NUM_BOARD_MINORS-1 inclusive; and\n(b) special subdevice minor devices in the range COMEDI_NUM_BOARD_MINORS\nupwards that are used to open the same underlying comedi device as the\nnormal board minor devices, but with non-default read and write\nsubdevices for asynchronous commands.\n\nThe special subdevice minor devices get created when a board supporting\nasynchronous commands is attached to a normal board minor device, and\ndestroyed when the board is detached from the normal board minor device.\nOne way to attach or detach a board is by using the COMEDI_DEVCONFIG\nioctl. This should only be used on normal board minors as the special\nsubdevice minors are too ephemeral. In particular, the change\nintroduced in commit 7d3135af399e92cf4c9bbc5f86b6c140aab3b88c (\"staging:\ncomedi: prevent auto-unconfig of manually configured devices\") breaks\nhorribly for special subdevice minor devices.\n\nSince there\u0027s no legitimate use for the COMEDI_DEVCONFIG ioctl on a\nspecial subdevice minor device node, disallow it and return -ENOTTY.\n\nSigned-off-by: Ian Abbott \u003cabbotti@mev.co.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a143ae690fbf24c2473d5c7c42875c29e150bd13", "tree": "d5db145f9d78d40feb5ba7fa5850fe1c17afb773", "parents": [ "6bdf87562cb048e3e9a76d18e440794830647657" ], "author": { "name": "Patrik Jakobsson", "email": "patrik.r.jakobsson@gmail.com", "time": "Wed Feb 13 22:20:22 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:04 2013 -0800" }, "message": "drm/i915: Set i9xx sdvo clock limits according to specifications\n\ncommit 4f7dfb6788dd022446847fbbfbe45e13bedb5be2 upstream.\n\nThe Intel PRM says the M1 and M2 divisors must be in the range of 10-20 and 5-9.\nSince we do all calculations based on them being register values (which are\nsubtracted by 2) we need to specify them accordingly.\n\nSigned-off-by: Patrik Jakobsson \u003cpatrik.r.jakobsson@gmail.com\u003e\nReviewed-by: Chris Wilson \u003cchris@chris-wilson.co.uk\u003e\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id\u003d56359\nSigned-off-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6bdf87562cb048e3e9a76d18e440794830647657", "tree": "189c1bbcb91a7477eb75e08364c0e4968a73a21d", "parents": [ "df87bd32f94547ecaa586052a6edeb653294a5b4" ], "author": { "name": "Mika Kuoppala", "email": "mika.kuoppala@linux.intel.com", "time": "Fri Feb 08 16:35:37 2013 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:04 2013 -0800" }, "message": "drm/i915: disable shared panel fitter for pipe\n\ncommit 24a1f16de97c4cf0029d9acd04be06db32208726 upstream.\n\nIf encoder is switched off by BIOS, but the panel fitter is left on,\nwe never try to turn off the panel fitter and leave it still attached\nto the pipe - which can cause blurry output elsewhere.\n\nBased on work by Chris Wilson \u003cchris@chris-wilson.co.uk\u003e\n\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id\u003d58867\nSigned-off-by: Mika Kuoppala \u003cmika.kuoppala@intel.com\u003e\nTested-by: Andreas Sturmlechner \u003candreas.sturmlechner@gmail.com\u003e\n[danvet: Remove the redundant HAS_PCH_SPLIT check and add a tiny\ncomment.]\nSigned-off-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "df87bd32f94547ecaa586052a6edeb653294a5b4", "tree": "2be4e85a83c12982aabf5cb3f2ff484af538b3a2", "parents": [ "bdfb3335569583fd195a3a1a89380d7648a9a85f" ], "author": { "name": "Daniel Vetter", "email": "daniel.vetter@ffwll.ch", "time": "Mon Jan 21 19:48:59 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:03 2013 -0800" }, "message": "intel/iommu: force writebuffer-flush quirk on Gen 4 Chipsets\n\ncommit 210561ffd72d00eccf12c0131b8024d5436bae95 upstream.\n\nWe already have the quirk entry for the mobile platform, but also\nreports on some desktop versions. So be paranoid and set it\neverywhere.\n\nReferences: http://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg33138.html\nReported-and-tested-by: Mihai Moldovan \u003cionic@ionic.de\u003e\nCc: David Woodhouse \u003cdwmw2@infradead.org\u003e\nCc: \"Sankaran, Rajesh\" \u003crajesh.sankaran@intel.com\u003e\nSigned-off-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "bdfb3335569583fd195a3a1a89380d7648a9a85f", "tree": "01b3dc5da797651dac0f949db3f9c4ff080f08d0", "parents": [ "61d40262e55fe00b817fe7e28f0f4dfad6e31fca" ], "author": { "name": "Nicholas Bellinger", "email": "nab@linux-iscsi.org", "time": "Tue Feb 19 03:15:14 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:03 2013 -0800" }, "message": "target: Fix divide by zero bug in fabric_max_sectors for unconfigured devices\n\ncommit 7a3cf6ca1ab2a2f7161c6dec5a787fc7a5de864e upstream\n\nThis patch fixes a possible divide by zero bug when the fabric_max_sectors\ndevice attribute is written and backend se_device failed to be successfully\nconfigured -\u003e enabled.\n\nGo ahead and use block_size\u003d512 within se_dev_set_fabric_max_sectors()\nin the event of a target_configure_device() failure case, as no valid\ndev-\u003edev_attrib.block_size value will have been setup yet.\n\nSigned-off-by: Nicholas Bellinger \u003cnab@linux-iscsi.org\u003e\nCc: Herton Ronaldo Krzesinski \u003cherton.krzesinski@canonical.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "61d40262e55fe00b817fe7e28f0f4dfad6e31fca", "tree": "9bed5eada4a8ecfd569a401637acfae3a723ba20", "parents": [ "d8a5f7fe8d632290ecbb6f692b98136957abe21a" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Thu Feb 07 10:10:04 2013 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:03 2013 -0800" }, "message": "drm/usb: bind driver to correct device\n\ncommit 9f23de52b64f7fb801fd76f3dd8651a0dc89187b upstream.\n\nWhile looking at plymouth on udl I noticed that plymouth was trying\nto use its fb plugin not its drm one, it was trying to drmOpen a driver called\nusb not udl, noticed that we actually had out driver pointing at the wrong\ndevice.\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d8a5f7fe8d632290ecbb6f692b98136957abe21a", "tree": "7290e02ef42631b0ac0d0a25f7aa750d0b677926", "parents": [ "d8fe02dde5c0aa474a32fe13d0743be515bb41dc" ], "author": { "name": "Ville Syrjälä", "email": "ville.syrjala@linux.intel.com", "time": "Thu Jan 31 19:43:38 2013 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:03 2013 -0800" }, "message": "drm: Use C8 instead of RGB332 when determining the format from depth/bpp\n\ncommit d84f031bd230fdf9c3b7734940c859bf28b90219 upstream.\n\nSupport for real RGB332 is a rarity, most hardware only really support\nC8. So use C8 instead of RGB332 when determining the format based on\ndepth/bpp.\n\nThis fixes 8bpp fbcon on i915, since i915 will only accept C8 and not\nRGB332.\n\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id\u003d59572\nSigned-off-by: Ville Syrjälä \u003cville.syrjala@linux.intel.com\u003e\nAcked-by: Dave Airlie \u003cairlied@gmail.com\u003e\nTested-by: mlsemon35@gmail.com\nSigned-off-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d8fe02dde5c0aa474a32fe13d0743be515bb41dc", "tree": "1d63fe99571339d7ae2017447bbf164ee53aa3d3", "parents": [ "7b480b03691358af771e6104087e05ffecc7d16a" ], "author": { "name": "Ville Syrjälä", "email": "ville.syrjala@linux.intel.com", "time": "Thu Jan 31 19:43:37 2013 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:03 2013 -0800" }, "message": "drm: Fill depth/bits_per_pixel for C8 format\n\ncommit c51a6bc5f6d328926a9a4a1247c5030faf190a80 upstream.\n\nSet depth/bits_per_pixel to 8 for C8 format.\n\nSigned-off-by: Ville Syrjälä \u003cville.syrjala@linux.intel.com\u003e\nAcked-by: Dave Airlie \u003cairlied@gmail.com\u003e\nSigned-off-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7b480b03691358af771e6104087e05ffecc7d16a", "tree": "08c9c9f590dc34b7b319b2f6bd7f0b8a91714625", "parents": [ "df28f4890263a0540b395402b43b57f047ccf7d5" ], "author": { "name": "Paulo Zanoni", "email": "paulo.r.zanoni@intel.com", "time": "Fri Feb 15 13:36:27 2013 -0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:03 2013 -0800" }, "message": "drm: don\u0027t add inferred modes for monitors that don\u0027t support them\n\ncommit 196e077dc165a307efbd9e7569f81bbdbcf18f65 upstream.\n\nIf bit 0 of the features byte (0x18) is set to 0, then, according to\nthe EDID spec, \"the display is non-continuous frequency (multi-mode)\nand is only specified to accept the video timing formats that are\nlisted in Base EDID and certain Extension Blocks\".\n\nFor more information, please see the EDID spec, check the notes of the\ntable that explains the \"Feature Support\" byte (18h) and also the\nnotes on the tables of the section that explains \"Display Range Limits\n\u0026 Additional Timing Description Definition (tag #FDh)\".\n\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id\u003d45729\nReviewed-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nReviewed-by: Adam Jackson \u003cajax@redhat.com\u003e\nSigned-off-by: Paulo Zanoni \u003cpaulo.r.zanoni@intel.com\u003e\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "df28f4890263a0540b395402b43b57f047ccf7d5", "tree": "4b8430b47afc77c27f42b094ddebd03b93982974", "parents": [ "ae4c05e0232e869cf2418ac6c0c862bb5287d672" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Thu Jan 24 14:14:19 2013 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:03 2013 -0800" }, "message": "vgacon/vt: clear buffer attributes when we load a 512 character font (v2)\n\ncommit 2a2483072393b27f4336ab068a1f48ca19ff1c1e upstream.\n\nWhen we switch from 256-\u003e512 byte font rendering mode, it means the\ncurrent contents of the screen is being reinterpreted. The bit that holds\nthe high bit of the 9-bit font, may have been previously set, and thus\nthe new font misrenders.\n\nThe problem case we see is grub2 writes spaces with the bit set, so it\nends up with data like 0x820, which gets reinterpreted into 0x120 char\nwhich the font translates into G with a circumflex. This flashes up on\nscreen at boot and is quite ugly.\n\nA current side effect of this patch though is that any rendering on the\nscreen changes color to a slightly darker color, but at least the screen\nno longer corrupts.\n\nv2: as suggested by hpa, always clear the attribute space, whether we\nare are going to or from 512 chars.\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ae4c05e0232e869cf2418ac6c0c862bb5287d672", "tree": "3c1f51740a9dd859fc619addf64ea48774e3466d", "parents": [ "b701cf407f9508fb899b482d9224daba2cedec75" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Thu Feb 07 12:30:25 2013 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:03 2013 -0800" }, "message": "drm/udl: disable fb_defio by default\n\ncommit 677d23b70bf949f75746c80cbae92c233c6b5e2a upstream.\n\nThere seems to be a bad interaction between gem/shmem and defio on top,\nI get list corruption on the page lru in the shmem code.\n\nTurn it off for now until we get some more digging done.\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b701cf407f9508fb899b482d9224daba2cedec75", "tree": "2fd4bd61e5cba093b1bd76a5cf316b1a4c16234f", "parents": [ "746042cf26dbcf5a8feb4f8938a3531a6169c96e" ], "author": { "name": "Dave Airlie", "email": "airlied@redhat.com", "time": "Thu Feb 07 11:19:15 2013 +1000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:03 2013 -0800" }, "message": "drm/udl: make usage as a console safer\n\ncommit bcb39af4486be07e896fc374a2336bad3104ae0a upstream.\n\nOkay you don\u0027t really want to use udl devices as your console, but if\nyou are unlucky enough to do so, you run into a lot of schedule while atomic\ndue to printk being called from all sorts of funky places. So check if we\nare in an atomic context, and queue the damage for later, the next printk\nshould cause it to appear. This isn\u0027t ideal, but it is simple, and seems to\nwork okay in my testing here.\n\n(dirty area idea came from xenfb)\n\nfixes a bunch of sleeping while atomic issues running fbcon on udl devices.\n\nSigned-off-by: Dave Airlie \u003cairlied@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "746042cf26dbcf5a8feb4f8938a3531a6169c96e", "tree": "778aa4587a7d8c42d7889521f786bd62c68aa11b", "parents": [ "5cf5b734496e73c30f43833138078ee7884ec725" ], "author": { "name": "Alex Deucher", "email": "alexander.deucher@amd.com", "time": "Tue Feb 05 11:47:09 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:03 2013 -0800" }, "message": "drm/radeon/dce6: fix display powergating\n\ncommit 0e3d50bfcbd338254795a700dcff429a96cba1a6 upstream.\n\nOnly enable it when we disable the display rather than\nat DPMS time since enabling it requires a full modeset\nto restore the display state. Fixes blank screens in\ncertain cases.\n\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5cf5b734496e73c30f43833138078ee7884ec725", "tree": "072b066d1564c766d02d84ffd0d43f87863e606b", "parents": [ "652328944e2514cd8306a71a2bbac4896efa49ed" ], "author": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Thu Feb 14 11:49:01 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:02 2013 -0800" }, "message": "sunvdc: Fix off-by-one in generic_request().\n\n[ Upstream commit f4d9605434c0fd4cc8639bf25cfc043418c52362 ]\n\nThe \u0027operations\u0027 bitmap corresponds one-for-one with the operation\ncodes, no adjustment is necessary.\n\nReported-by: Mark Kettenis \u003cmark.kettenis@xs4all.nl\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "652328944e2514cd8306a71a2bbac4896efa49ed", "tree": "88ee6a2560f28136cf90659bcd6584d660cc40ad", "parents": [ "7e8b41d605b06c68a7df890e34cb560d837e87ac" ], "author": { "name": "David Henningsson", "email": "david.henningsson@canonical.com", "time": "Tue Feb 19 16:11:22 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:02 2013 -0800" }, "message": "ALSA: hda - hdmi: ELD shouldn\u0027t be valid after unplug\n\ncommit bbfd8a19b6913f50a362457c34d49bfafe5e456e upstream.\n\nCurrently, eld_valid is never set to false, except at kernel module\nload time. This patch makes sure that eld is no longer valid when\nthe cable is (hot-)unplugged.\n\nSigned-off-by: David Henningsson \u003cdavid.henningsson@canonical.com\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7e8b41d605b06c68a7df890e34cb560d837e87ac", "tree": "e7c181762bccea3fe94660069a66b51e9b9d03f3", "parents": [ "63b2afe91cef7d844ea07a1ad17be63ded94e8ca" ], "author": { "name": "Fernando Luis Vazquez Cao", "email": "fernando@oss.ntt.co.jp", "time": "Tue Feb 12 16:47:44 2013 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:02 2013 -0800" }, "message": "ALSA: hda - Workaround for silent output on Sony Vaio VGC-LN51JGB with ALC889\n\ncommit 12e31a78c70dc12897fda2489113f445c0e94a18 upstream.\n\nSome Vaio all-in-one desktop PCs (for example VGC-LN51JGB) are affected by\nthe same issue that caused Vaio Z laptops to become silent: the speaker pin\nmust be connected to the first DAC even though the codec itself advertises\nflexible routing through any of the DACs.\n\nUse the no-primary-hp fixup for choosing the speaker pin as the primary so\nthat the right DAC is assigned on this device.\n\nSigned-off-by: Fernando Luis Vazquez Cao \u003cfernando@oss.ntt.co.jp\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "63b2afe91cef7d844ea07a1ad17be63ded94e8ca", "tree": "e77081ec85422034d825f1cc2ac61887434e97cc", "parents": [ "e32afc122e3a808944a9f7af5612bf2a3cbea89a" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Fri Feb 01 14:01:27 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:02 2013 -0800" }, "message": "ALSA: hda - Release assigned pin/cvt at error path of hdmi_pcm_open()\n\ncommit 2ad779b7329d6894a80df94e693e72eaa0d56790 upstream.\n\nIf the driver detects and invalid ELD, it gives an open error.\nBut it forgot to release the assigned pin, converter and spdif ctls\nbefore returning.\n\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e32afc122e3a808944a9f7af5612bf2a3cbea89a", "tree": "8718795508df5c4fa7fa206900fc918b50cdd294", "parents": [ "e3fc3cb2a03623b48250dd3a12378a42d276f20e" ], "author": { "name": "Pawel Moll", "email": "mail@pawelmoll.com", "time": "Thu Feb 21 01:55:50 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:02 2013 -0800" }, "message": "ALSA: usb: Fix Processing Unit Descriptor parsers\n\ncommit b531f81b0d70ffbe8d70500512483227cc532608 upstream.\n\nCommit 99fc86450c439039d2ef88d06b222fd51a779176 \"ALSA: usb-mixer:\nparse descriptors with structs\" introduced a set of useful parsers\nfor descriptors. Unfortunately the parses for the Processing Unit\nDescriptor came with a very subtle bug...\n\nFunctions uac_processing_unit_iProcessing() and\nuac_processing_unit_specific() were indexing the baSourceID array\nforgetting the fields before the iProcessing and process-specific\ndescriptors.\n\nThe problem was observed with Sound Blaster Extigy mixer,\nwhere nNrModes in Up/Down-mix Processing Unit Descriptor\nwas accessed at offset 10 of the descriptor (value 0)\ninstead of offset 15 (value 7). In result the resulting\ncontrol had interesting limit values:\n\nSimple mixer control \u0027Channel Routing Mode Select\u0027,0\n Capabilities: volume volume-joined penum\n Playback channels: Mono\n Capture channels: Mono\n Limits: 0 - -1\n Mono: -1 [100%]\n\nFixed by starting from the bmControls, which was calculated\ncorrectly, instead of baSourceID.\n\nNow the mentioned control is fine:\n\nSimple mixer control \u0027Channel Routing Mode Select\u0027,0\n Capabilities: volume volume-joined penum\n Playback channels: Mono\n Capture channels: Mono\n Limits: 0 - 6\n Mono: 0 [0%]\n\nSigned-off-by: Pawel Moll \u003cmail@pawelmoll.com\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e3fc3cb2a03623b48250dd3a12378a42d276f20e", "tree": "5135611ce13fce188deae1689743f74abc7f58f2", "parents": [ "a8fb02fe99203fea52046151817672102124d389" ], "author": { "name": "Clemens Ladisch", "email": "clemens@ladisch.de", "time": "Thu Jan 31 21:14:33 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:02 2013 -0800" }, "message": "ALSA: usb-audio: fix Roland A-PRO support\n\ncommit 7da58046482fceb17c4a0d4afefd9507ec56de7f upstream.\n\nThe quirk for the Roland/Cakewalk A-PRO keyboards accidentally used the\nwrong interface number, which prevented the driver from attaching to the\ndevice.\n\nSigned-off-by: Clemens Ladisch \u003cclemens@ladisch.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a8fb02fe99203fea52046151817672102124d389", "tree": "82bc3d2b432750e67538f125f7266166d0552fe6", "parents": [ "92a5267ac37e74cf44675f5992fc6fa4ad694a04" ], "author": { "name": "Tomasz Guszkowski", "email": "tsg@o2.pl", "time": "Tue Feb 05 22:10:31 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:02 2013 -0800" }, "message": "p54usb: corrected USB ID for T-Com Sinus 154 data II\n\ncommit 008e33f733ca51acb2dd9d88ea878693b04d1d2a upstream.\n\nCorrected USB ID for T-Com Sinus 154 data II. ISL3887-based. The\ndevice was tested in managed mode with no security, WEP 128\nbit and WPA-PSK (TKIP) with firmware 2.13.1.0.lm87.arm (md5sum:\n7d676323ac60d6e1a3b6d61e8c528248). It works.\n\nSigned-off-by: Tomasz Guszkowski \u003ctsg@o2.pl\u003e\nAcked-By: Christian Lamparter \u003cchunkeey@googlemail.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "92a5267ac37e74cf44675f5992fc6fa4ad694a04", "tree": "b0ddd2e1406971f6b13f7d667d5066aa0b95a953", "parents": [ "8e0ed8259d2016543b07a43896bc6f4b7f541e42" ], "author": { "name": "Trond Myklebust", "email": "Trond.Myklebust@netapp.com", "time": "Tue Feb 19 12:04:42 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:02 2013 -0800" }, "message": "NLM: Ensure that we resend all pending blocking locks after a reclaim\n\ncommit 666b3d803a511fbc9bc5e5ea8ce66010cf03ea13 upstream.\n\nCurrently, nlmclnt_lock will break out of the for(;;) loop when\nthe reclaimer wakes up the blocking lock thread by setting\nnlm_lck_denied_grace_period. This causes the lock request to fail\nwith an ENOLCK error.\nThe intention was always to ensure that we resend the lock request\nafter the grace period has expired.\n\nReported-by: Wangyuan Zhang \u003cWangyuan.Zhang@netapp.com\u003e\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8e0ed8259d2016543b07a43896bc6f4b7f541e42", "tree": "e4ba2114395b37ce37306371fae5db41d7a3981f", "parents": [ "38bc0fe99edd35ef738800167c67055f8ca7e476" ], "author": { "name": "fanchaoting", "email": "fanchaoting@cn.fujitsu.com", "time": "Mon Feb 04 21:15:02 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:02 2013 -0800" }, "message": "umount oops when remove blocklayoutdriver first\n\ncommit 5a12cca697aca5dfba42a7d4c3356acc0445a2b0 upstream.\n\nnow pnfs client uses block layout, maybe we can remove\nblocklayoutdriver first. if we umount later,\nit can cause oops in unset_pnfs_layoutdriver.\nbecause nfss-\u003epnfs_curr_ld-\u003eclear_layoutdriver is invalid.\n\nreproduce it:\n modprobe blocklayoutdriver\n mount -t nfs4 -o minorversion\u003d1 pnfsip:/ /mnt/\n rmmod blocklayoutdriver\n umount /mnt\n\nthen you can see following\n\nCPU 0\nPid: 17023, comm: umount.nfs4 Tainted: GF O 3.7.0-rc6-pnfs #1 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform\nRIP: 0010:[\u003cffffffffa04cfe6d\u003e] [\u003cffffffffa04cfe6d\u003e] unset_pnfs_layoutdriver+0x1d/0x70 [nfsv4]\nRSP: 0018:ffff8800022d9e48 EFLAGS: 00010286\nRAX: ffffffffa04a1b00 RBX: ffff88000b013800 RCX: 0000000000000001\nRDX: ffffffff81ae8ee0 RSI: ffff880001ee94b8 RDI: ffff88000b013800\nRBP: ffff8800022d9e58 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000000 R12: ffff880001ee9400\nR13: ffff8800105978c0 R14: 00007fff25846c08 R15: 0000000001bba550\nFS: 00007f45ae7f0700(0000) GS:ffff880012c00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b\nCR2: ffffffffa04a1b38 CR3: 0000000002c0c000 CR4: 00000000000006f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\nProcess umount.nfs4 (pid: 17023, threadinfo ffff8800022d8000, task ffff880006e48aa0)\nStack:\nffff8800105978c0 ffff88000b013800 ffff8800022d9e78 ffffffffa04cd0ce\nffff8800022d9e78 ffff88000b013800 ffff8800022d9ea8 ffffffffa04755a7\nffff8800022d9ea8 ffff880002f96400 ffff88000b013800 ffff880002f96400\nCall Trace:\n[\u003cffffffffa04cd0ce\u003e] nfs4_destroy_server+0x1e/0x30 [nfsv4]\n[\u003cffffffffa04755a7\u003e] nfs_free_server+0xb7/0x150 [nfs]\n[\u003cffffffffa047d4d5\u003e] nfs_kill_super+0x35/0x40 [nfs]\n[\u003cffffffff81178d35\u003e] deactivate_locked_super+0x45/0x70\n[\u003cffffffff8117986a\u003e] deactivate_super+0x4a/0x70\n[\u003cffffffff81193ee2\u003e] mntput_no_expire+0xd2/0x130\n[\u003cffffffff81194d62\u003e] sys_umount+0x72/0xe0\n[\u003cffffffff8154af59\u003e] system_call_fastpath+0x16/0x1b\nCode: 06 e1 b8 ea ff ff ff eb 9e 0f 1f 44 00 00 55 48 89 e5 53 48 83 ec 08 66 66 66 66 90 48 8b 87 80 03 00 00 48 89 fb 48 85 c0 74 29 \u003c48\u003e 8b 40 38 48 85 c0 74 02 ff d0 48 8b 03 3e ff 48 04 0f 94 c2\nRIP [\u003cffffffffa04cfe6d\u003e] unset_pnfs_layoutdriver+0x1d/0x70 [nfsv4]\nRSP \u003cffff8800022d9e48\u003e\nCR2: ffffffffa04a1b38\n---[ end trace 29f75aaedda058bf ]---\n\nSigned-off-by: fanchaoting\u003cfanchaoting@cn.fujitsu.com\u003e\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "38bc0fe99edd35ef738800167c67055f8ca7e476", "tree": "fa3935fccea2b989f9333c20fff4147e68ca05f4", "parents": [ "f4ce5b3f263c05e7af66fa4eba7c4eb8e1b006bf" ], "author": { "name": "Grant Likely", "email": "grant.likely@secretlab.ca", "time": "Thu Feb 14 18:14:27 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:01 2013 -0800" }, "message": "drivercore: Fix ordering between deferred_probe and exiting initcalls\n\ncommit d72cca1eee5b26e313da2a380d4862924e271031 upstream.\n\nOne of the side effects of deferred probe is that some drivers which\nused to be probed before initcalls completed are now happening slightly\nlater. This causes two problems.\n- If a console driver gets deferred, then it may not be ready when\n userspace starts. For example, if a uart depends on pinctrl, then the\n uart will get deferred and /dev/console will not be available\n- __init sections will be discarded before built-in drivers are probed.\n Strictly speaking, __init functions should not be called in a drivers\n __probe path, but there are a lot of drivers (console stuff again)\n that do anyway. In the past it was perfectly safe to do so because all\n built-in drivers got probed before the end of initcalls.\n\nThis patch fixes the problem by forcing the first pass of the deferred\nlist to complete at late_initcall time. This is late enough to catch the\ndrivers that are known to have the above issues.\n\nSigned-off-by: Grant Likely \u003cgrant.likely@secretlab.ca\u003e\nTested-by: Haojian Zhuang \u003chaojian.zhuang@linaro.org\u003e\nCc: Arnd Bergmann \u003carnd@arndb.de\u003e\nCc: Russell King \u003clinux@arm.linux.org.uk\u003e\nCc: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f4ce5b3f263c05e7af66fa4eba7c4eb8e1b006bf", "tree": "4d6ca134dbfbde49745557a183d144cb59457ba7", "parents": [ "06c7976c91566d676766ad57b574757f6d0abd02" ], "author": { "name": "Mel Gorman", "email": "mgorman@suse.de", "time": "Fri Feb 22 16:35:59 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:01 2013 -0800" }, "message": "mm/fadvise.c: drain all pagevecs if POSIX_FADV_DONTNEED fails to discard all pages\n\ncommit 67d46b296a1ba1477c0df8ff3bc5e0167a0b0732 upstream.\n\nRob van der Heij reported the following (paraphrased) on private mail.\n\n\tThe scenario is that I want to avoid backups to fill up the page\n\tcache and purge stuff that is more likely to be used again (this is\n\twith s390x Linux on z/VM, so I don\u0027t give it as much memory that\n\twe don\u0027t care anymore). So I have something with LD_PRELOAD that\n\tintercepts the close() call (from tar, in this case) and issues\n\ta posix_fadvise() just before closing the file.\n\n\tThis mostly works, except for small files (less than 14 pages)\n\tthat remains in page cache after the face.\n\nUnfortunately Rob has not had a chance to test this exact patch but the\ntest program below should be reproducing the problem he described.\n\nThe issue is the per-cpu pagevecs for LRU additions. If the pages are\nadded by one CPU but fadvise() is called on another then the pages\nremain resident as the invalidate_mapping_pages() only drains the local\npagevecs via its call to pagevec_release(). The user-visible effect is\nthat a program that uses fadvise() properly is not obeyed.\n\nA possible fix for this is to put the necessary smarts into\ninvalidate_mapping_pages() to globally drain the LRU pagevecs if a\npagevec page could not be discarded. The downside with this is that an\ninode cache shrink would send a global IPI and memory pressure\npotentially causing global IPI storms is very undesirable.\n\nInstead, this patch adds a check during fadvise(POSIX_FADV_DONTNEED) to\ncheck if invalidate_mapping_pages() discarded all the requested pages.\nIf a subset of pages are discarded it drains the LRU pagevecs and tries\nagain. If the second attempt fails, it assumes it is due to the pages\nbeing mapped, locked or dirty and does not care. With this patch, an\napplication using fadvise() correctly will be obeyed but there is a\ndownside that a malicious application can force the kernel to send\nglobal IPIs and increase overhead.\n\nIf accepted, I would like this to be considered as a -stable candidate.\nIt\u0027s not an urgent issue but it\u0027s a system call that is not working as\nadvertised which is weak.\n\nThe following test program demonstrates the problem. It should never\nreport that pages are still resident but will without this patch. It\nassumes that CPU 0 and 1 exist.\n\nint main() {\n\tint fd;\n\tint pagesize \u003d getpagesize();\n\tssize_t written \u003d 0, expected;\n\tchar *buf;\n\tunsigned char *vec;\n\tint resident, i;\n\tcpu_set_t set;\n\n\t/* Prepare a buffer for writing */\n\texpected \u003d FILESIZE_PAGES * pagesize;\n\tbuf \u003d malloc(expected + 1);\n\tif (buf \u003d\u003d NULL) {\n\t\tprintf(\"ENOMEM\\n\");\n\t\texit(EXIT_FAILURE);\n\t}\n\tbuf[expected] \u003d 0;\n\tmemset(buf, \u0027a\u0027, expected);\n\n\t/* Prepare the mincore vec */\n\tvec \u003d malloc(FILESIZE_PAGES);\n\tif (vec \u003d\u003d NULL) {\n\t\tprintf(\"ENOMEM\\n\");\n\t\texit(EXIT_FAILURE);\n\t}\n\n\t/* Bind ourselves to CPU 0 */\n\tCPU_ZERO(\u0026set);\n\tCPU_SET(0, \u0026set);\n\tif (sched_setaffinity(getpid(), sizeof(set), \u0026set) \u003d\u003d -1) {\n\t\tperror(\"sched_setaffinity\");\n\t\texit(EXIT_FAILURE);\n\t}\n\n\t/* open file, unlink and write buffer */\n\tfd \u003d open(\"fadvise-test-file\", O_CREAT|O_EXCL|O_RDWR);\n\tif (fd \u003d\u003d -1) {\n\t\tperror(\"open\");\n\t\texit(EXIT_FAILURE);\n\t}\n\tunlink(\"fadvise-test-file\");\n\twhile (written \u003c expected) {\n\t\tssize_t this_write;\n\t\tthis_write \u003d write(fd, buf + written, expected - written);\n\n\t\tif (this_write \u003d\u003d -1) {\n\t\t\tperror(\"write\");\n\t\t\texit(EXIT_FAILURE);\n\t\t}\n\n\t\twritten +\u003d this_write;\n\t}\n\tfree(buf);\n\n\t/*\n\t * Force ourselves to another CPU. If fadvise only flushes the local\n\t * CPUs pagevecs then the fadvise will fail to discard all file pages\n\t */\n\tCPU_ZERO(\u0026set);\n\tCPU_SET(1, \u0026set);\n\tif (sched_setaffinity(getpid(), sizeof(set), \u0026set) \u003d\u003d -1) {\n\t\tperror(\"sched_setaffinity\");\n\t\texit(EXIT_FAILURE);\n\t}\n\n\t/* sync and fadvise to discard the page cache */\n\tfsync(fd);\n\tif (posix_fadvise(fd, 0, expected, POSIX_FADV_DONTNEED) \u003d\u003d -1) {\n\t\tperror(\"posix_fadvise\");\n\t\texit(EXIT_FAILURE);\n\t}\n\n\t/* map the file and use mincore to see which parts of it are resident */\n\tbuf \u003d mmap(NULL, expected, PROT_READ, MAP_SHARED, fd, 0);\n\tif (buf \u003d\u003d NULL) {\n\t\tperror(\"mmap\");\n\t\texit(EXIT_FAILURE);\n\t}\n\tif (mincore(buf, expected, vec) \u003d\u003d -1) {\n\t\tperror(\"mincore\");\n\t\texit(EXIT_FAILURE);\n\t}\n\n\t/* Check residency */\n\tfor (i \u003d 0, resident \u003d 0; i \u003c FILESIZE_PAGES; i++) {\n\t\tif (vec[i])\n\t\t\tresident++;\n\t}\n\tif (resident !\u003d 0) {\n\t\tprintf(\"Nr unexpected pages resident: %d\\n\", resident);\n\t\texit(EXIT_FAILURE);\n\t}\n\n\tmunmap(buf, expected);\n\tclose(fd);\n\tfree(vec);\n\texit(EXIT_SUCCESS);\n}\n\nSigned-off-by: Mel Gorman \u003cmgorman@suse.de\u003e\nReported-by: Rob van der Heij \u003crvdheij@gmail.com\u003e\nTested-by: Rob van der Heij \u003crvdheij@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": "06c7976c91566d676766ad57b574757f6d0abd02", "tree": "ddf95fb6f65792326ace682ea9170e4e9fa52a05", "parents": [ "3b6e03c9ac4d57ccb03737a997069dc7ab65601c" ], "author": { "name": "Greg Thelen", "email": "gthelen@google.com", "time": "Fri Feb 22 16:36:01 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:01 2013 -0800" }, "message": "tmpfs: fix use-after-free of mempolicy object\n\ncommit 5f00110f7273f9ff04ac69a5f85bb535a4fd0987 upstream.\n\nThe tmpfs remount logic preserves filesystem mempolicy if the mpol\u003dM\noption is not specified in the remount request. A new policy can be\nspecified if mpol\u003dM is given.\n\nBefore this patch remounting an mpol bound tmpfs without specifying\nmpol\u003d mount option in the remount request would set the filesystem\u0027s\nmempolicy object to a freed mempolicy object.\n\nTo reproduce the problem boot a DEBUG_PAGEALLOC kernel and run:\n # mkdir /tmp/x\n\n # mount -t tmpfs -o size\u003d100M,mpol\u003dinterleave nodev /tmp/x\n\n # grep /tmp/x /proc/mounts\n nodev /tmp/x tmpfs rw,relatime,size\u003d102400k,mpol\u003dinterleave:0-3 0 0\n\n # mount -o remount,size\u003d200M nodev /tmp/x\n\n # grep /tmp/x /proc/mounts\n nodev /tmp/x tmpfs rw,relatime,size\u003d204800k,mpol\u003d??? 0 0\n # note ? garbage in mpol\u003d... output above\n\n # dd if\u003d/dev/zero of\u003d/tmp/x/f count\u003d1\n # panic here\n\nPanic:\n BUG: unable to handle kernel NULL pointer dereference at (null)\n IP: [\u003c (null)\u003e] (null)\n [...]\n Oops: 0010 [#1] SMP DEBUG_PAGEALLOC\n Call Trace:\n mpol_shared_policy_init+0xa5/0x160\n shmem_get_inode+0x209/0x270\n shmem_mknod+0x3e/0xf0\n shmem_create+0x18/0x20\n vfs_create+0xb5/0x130\n do_last+0x9a1/0xea0\n path_openat+0xb3/0x4d0\n do_filp_open+0x42/0xa0\n do_sys_open+0xfe/0x1e0\n compat_sys_open+0x1b/0x20\n cstar_dispatch+0x7/0x1f\n\nNon-debug kernels will not crash immediately because referencing the\ndangling mpol will not cause a fault. Instead the filesystem will\nreference a freed mempolicy object, which will cause unpredictable\nbehavior.\n\nThe problem boils down to a dropped mpol reference below if\nshmem_parse_options() does not allocate a new mpol:\n\n config \u003d *sbinfo\n shmem_parse_options(data, \u0026config, true)\n mpol_put(sbinfo-\u003empol)\n sbinfo-\u003empol \u003d config.mpol /* BUG: saves unreferenced mpol */\n\nThis patch avoids the crash by not releasing the mempolicy if\nshmem_parse_options() doesn\u0027t create a new mpol.\n\nHow far back does this issue go? I see it in both 2.6.36 and 3.3. I did\nnot look back further.\n\nSigned-off-by: Greg Thelen \u003cgthelen@google.com\u003e\nAcked-by: Hugh Dickins \u003chughd@google.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3b6e03c9ac4d57ccb03737a997069dc7ab65601c", "tree": "7694979d071bb8e8482b46d5ee480a24ad3d4dc9", "parents": [ "cd336937712589aff73931ed84c2bc56d0574a3c" ], "author": { "name": "Lars-Peter Clausen", "email": "lars@metafoo.de", "time": "Thu Feb 21 16:44:04 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:01 2013 -0800" }, "message": "drivers/video/backlight/adp88?0_bl.c: fix resume\n\ncommit 5eb02c01bd1f3ef195989ab05e835e2b0711b5a9 upstream.\n\nClearing the NSTBY bit in the control register also automatically clears\nthe BLEN bit. So we need to make sure to set it again during resume,\notherwise the backlight will stay off.\n\nSigned-off-by: Lars-Peter Clausen \u003clars@metafoo.de\u003e\nAcked-by: Michael Hennerich \u003cmichael.hennerich@analog.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": "cd336937712589aff73931ed84c2bc56d0574a3c", "tree": "4b8c8fcc7c8c930eb6c8958619b8bfac02444d88", "parents": [ "9fd4e539ed0737be165fc633063885a477ac556a" ], "author": { "name": "Junxiao Bi", "email": "junxiao.bi@oracle.com", "time": "Thu Feb 21 16:42:45 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:01 2013 -0800" }, "message": "ocfs2: unlock super lock if lockres refresh failed\n\ncommit 3278bb748d2437eb1464765f36429e5d6aa91c38 upstream.\n\nIf lockres refresh failed, the super lock will never be released which\nwill cause some processes on other cluster nodes hung forever.\n\nSigned-off-by: Junxiao Bi \u003cjunxiao.bi@oracle.com\u003e\nCc: Joel Becker \u003cjlbec@evilplan.org\u003e\nCc: Mark Fasheh \u003cmfasheh@suse.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": "9fd4e539ed0737be165fc633063885a477ac556a", "tree": "12c25b8cb743292f178efb769b89cdecd4914660", "parents": [ "0b7fba4034da2a6dd6ebb994ad9f592939a752cf" ], "author": { "name": "MITSUNARI Shigeo", "email": "herumi@nifty.com", "time": "Thu Feb 21 16:42:01 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:01 2013 -0800" }, "message": "fs/block_dev.c: page cache wrongly left invalidated after revalidate_disk()\n\ncommit 7630b661da330b35dd57b6f5d6d62b386f2dd751 upstream.\n\nWe found that bdev-\u003ebd_invalidated was left set once revalidate_disk()\nis called, which results in page cache flush every time that device is\nopen.\n\nSpecifically, we found this problem in MD block device. Once we resize\na MD device, mdadm --monitor periodically flush all page cache for that\ndevice every 60 or 1000 seconds when it opens the device.\n\nThis bug lies since at least 3.2.0 till the latest kernel(3.6.2). Patch\nis attached.\n\nThe following steps will reproduce the problem.\n\n1. prepair a block device (eg /dev/sdb).\n\n2. create two partitions:\n\n sudo parted /dev/sdb\n mklabel gpt\n mkpart primary 0% 50%\n mkpart primary 50% 100%\n\n3. create a md device.\n\n sudo mdadm -C /dev/md/hoge -l 1 -n 2 -e 1.2 --assume-clean --auto\u003dmd --symlink\u003dno /dev/sdb1 /dev/sdb2\n\n4. create file system and mount it\n\n sudo mkfs.ext3 /dev/md/hoge\n sudo mkdir /mnt/test\n sudo mount /dev/md/hoge /mnt/test\n\n5. try to resize the device\n\n sudo mdadm -G /dev/md/hoge --size\u003dmax\n\n6. create a file to fill file cache.\n\n sudo dd if\u003d/dev/urandom of\u003d/mnt/test/data bs\u003d1M count\u003d10\n\nand verify the current status of file by free command.\n\n7. mdadm monitor will open the md device every 1000 seconds and you\n will find all file cache on the device are cleared.\n\nThe timing can be reduced by the following steps.\n\na) kill mdadm and restart it with --delay option\n\n /sbin/mdadm --monitor --delay\u003d30 --pid-file /var/run/mdadm/monitor.pid --daemonise --scan --syslog\n\nor open the md device directly.\n\n sudo dd if\u003d/dev/md/hoge of\u003d/dev/null bs\u003d4096 count\u003d1\n\nSigned-off-by: MITSUNARI Shigeo \u003cherumi@nifty.com\u003e\nCc: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Jeff Moyer \u003cjmoyer@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": "0b7fba4034da2a6dd6ebb994ad9f592939a752cf", "tree": "dfc4a960280b225d7af935c0e8cf2b7f9fc030c4", "parents": [ "803437207a3e6fef7791adeb7a0c2adb4b012459" ], "author": { "name": "Jim Somerville", "email": "Jim.Somerville@windriver.com", "time": "Thu Feb 21 16:41:59 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:01 2013 -0800" }, "message": "inotify: remove broken mask checks causing unmount to be EINVAL\n\ncommit 676a0675cf9200ac047fb50825f80867b3bb733b upstream.\n\nRunning the command:\n\n\tinotifywait -e unmount /mnt/disk\n\nimmediately aborts with a -EINVAL return code. This is however a valid\nparameter. This abort occurs only if unmount is the sole event\nparameter. If other event parameters are supplied, then the unmount\nevent wait will work.\n\nThe problem was introduced by commit 44b350fc23e (\"inotify: Fix mask\nchecks\"). In that commit, it states:\n\n\tThe mask checks in inotify_update_existing_watch() and\n\tinotify_new_watch() are useless because inotify_arg_to_mask()\n\tsets FS_IN_IGNORED and FS_EVENT_ON_CHILD bits anyway.\n\nBut instead of removing the useless checks, it did this:\n\n\t mask \u003d inotify_arg_to_mask(arg);\n\t- if (unlikely(!mask))\n\t+ if (unlikely(!(mask \u0026 IN_ALL_EVENTS)))\n\t return -EINVAL;\n\nThe problem is that IN_ALL_EVENTS doesn\u0027t include IN_UNMOUNT, and other\nparts of the code keep IN_UNMOUNT separate from IN_ALL_EVENTS. So the\ncheck should be:\n\n\tif (unlikely(!(mask \u0026 (IN_ALL_EVENTS | IN_UNMOUNT))))\n\nBut inotify_arg_to_mask(arg) always sets the IN_UNMOUNT bit in the mask\nanyway, so the check is always going to pass and thus should simply be\nremoved. Also note that inotify_arg_to_mask completely controls what\nmask bits get set from arg, there\u0027s no way for invalid bits to get\nenabled there.\n\nLets fix it by simply removing the useless broken checks.\n\nSigned-off-by: Jim Somerville \u003cJim.Somerville@windriver.com\u003e\nSigned-off-by: Paul Gortmaker \u003cpaul.gortmaker@windriver.com\u003e\nCc: Jerome Marchand \u003cjmarchan@redhat.com\u003e\nCc: John McCutchan \u003cjohn@johnmccutchan.com\u003e\nCc: Robert Love \u003crlove@rlove.org\u003e\nCc: Eric Paris \u003ceparis@parisplace.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "803437207a3e6fef7791adeb7a0c2adb4b012459", "tree": "eec95051fb2e48121d2b7bd57b4c40e96809c879", "parents": [ "e3aa5ed471454f36e99b8d3a960746eb58c07180" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Mon Feb 18 09:52:08 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:01 2013 -0800" }, "message": "futex: Revert \"futex: Mark get_robust_list as deprecated\"\n\ncommit fe2b05f7ca9f906be61dced5489f63b8b4d7c770 upstream.\n\nThis reverts commit ec0c4274e33c0373e476b73e01995c53128f1257.\n\nget_robust_list() is in use and a removal would break existing user\nspace. With the permission checks in place it\u0027s not longer a security\nhole. Remove the deprecation warnings.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Cyrill Gorcunov \u003cgorcunov@openvz.org\u003e\nCc: Richard Weinberger \u003crichard@nod.at\u003e\nCc: akpm@linux-foundation.org\nCc: paul.gortmaker@windriver.com\nCc: davej@redhat.com\nCc: keescook@chromium.org\nCc: ebiederm@xmission.com\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e3aa5ed471454f36e99b8d3a960746eb58c07180", "tree": "6b6b2d5e89a4c07629f7c8141e82e496cad5c764", "parents": [ "2030511afec79a7f65b967c3d8a22e4a1edd9532" ], "author": { "name": "Christian Borntraeger", "email": "borntraeger@de.ibm.com", "time": "Fri Jan 25 15:34:15 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:01 2013 -0800" }, "message": "s390/kvm: Fix store status for ACRS/FPRS\n\ncommit 15bc8d8457875f495c59d933b05770ba88d1eacb upstream.\n\nOn store status we need to copy the current state of registers\ninto a save area. Currently we might save stale versions:\nThe sie state descriptor doesnt have fields for guest ACRS,FPRS,\nthose registers are simply stored in the host registers. The host\nprogram must copy these away if needed. We do that in vcpu_put/load.\n\nIf we now do a store status in KVM code between vcpu_put/load, the\nsaved values are not up-to-date. Lets collect the ACRS/FPRS before\nsaving them.\n\nThis also fixes some strange problems with hotplug and virtio-ccw,\nsince the low level machine check handler (on hotplug a machine check\nwill happen) will revalidate all registers with the content of the\nsave area.\n\nSigned-off-by: Christian Borntraeger \u003cborntraeger@de.ibm.com\u003e\nSigned-off-by: Gleb Natapov \u003cgleb@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "2030511afec79a7f65b967c3d8a22e4a1edd9532", "tree": "eaa759f8f957a089596c01ef09ebdfc71b4340ec", "parents": [ "7fecb64cca9a98f60ff4bc794bb353512bd5c665" ], "author": { "name": "Cornelia Huck", "email": "cornelia.huck@de.ibm.com", "time": "Fri Dec 14 17:02:16 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:01 2013 -0800" }, "message": "KVM: s390: Handle hosts not supporting s390-virtio.\n\ncommit 55c171a6d90dc0574021f9c836127cfd1a7d2e30 upstream.\n\nRunning under a kvm host does not necessarily imply the presence of\na page mapped above the main memory with the virtio information;\nhowever, the code includes a hard coded access to that page.\n\nInstead, check for the presence of the page and exit gracefully\nbefore we hit an addressing exception if it does not exist.\n\nReviewed-by: Marcelo Tosatti \u003cmtosatti@redhat.com\u003e\nReviewed-by: Alexander Graf \u003cagraf@suse.de\u003e\nSigned-off-by: Cornelia Huck \u003ccornelia.huck@de.ibm.com\u003e\nSigned-off-by: Gleb Natapov \u003cgleb@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7fecb64cca9a98f60ff4bc794bb353512bd5c665", "tree": "eff3883ea5932d820a5166067695ccabec0d07a1", "parents": [ "d0730c2bf33c1cdab392f88013be6b5ebacf0f29" ], "author": { "name": "Robin Holt", "email": "holt@sgi.com", "time": "Fri Feb 22 16:35:34 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:00 2013 -0800" }, "message": "mmu_notifier_unregister NULL Pointer deref and multiple -\u003erelease() callouts\n\ncommit 751efd8610d3d7d67b7bdf7f62646edea7365dd7 upstream.\n\nThere is a race condition between mmu_notifier_unregister() and\n__mmu_notifier_release().\n\nAssume two tasks, one calling mmu_notifier_unregister() as a result of a\nfilp_close() -\u003eflush() callout (task A), and the other calling\nmmu_notifier_release() from an mmput() (task B).\n\n A B\nt1 srcu_read_lock()\nt2 if (!hlist_unhashed())\nt3 srcu_read_unlock()\nt4 srcu_read_lock()\nt5 hlist_del_init_rcu()\nt6 synchronize_srcu()\nt7 srcu_read_unlock()\nt8 hlist_del_rcu() \u003c--- NULL pointer deref.\n\nAdditionally, the list traversal in __mmu_notifier_release() is not\nprotected by the by the mmu_notifier_mm-\u003ehlist_lock which can result in\ncallouts to the -\u003erelease() notifier from both mmu_notifier_unregister()\nand __mmu_notifier_release().\n\n-stable suggestions:\n\nThe stable trees prior to 3.7.y need commits 21a92735f660 and\n70400303ce0c cherry-picked in that order prior to cherry-picking this\ncommit. The 3.7.y tree already has those two commits.\n\nSigned-off-by: Robin Holt \u003cholt@sgi.com\u003e\nCc: Andrea Arcangeli \u003caarcange@redhat.com\u003e\nCc: Wanpeng Li \u003cliwanp@linux.vnet.ibm.com\u003e\nCc: Xiao Guangrong \u003cxiaoguangrong@linux.vnet.ibm.com\u003e\nCc: Avi Kivity \u003cavi@redhat.com\u003e\nCc: Hugh Dickins \u003chughd@google.com\u003e\nCc: Marcelo Tosatti \u003cmtosatti@redhat.com\u003e\nCc: Sagi Grimberg \u003csagig@mellanox.co.il\u003e\nCc: Haggai Eran \u003chaggaie@mellanox.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": "d0730c2bf33c1cdab392f88013be6b5ebacf0f29", "tree": "e077ff276de128de50cb464cad3a591f1a11b270", "parents": [ "4209ee0d3f7992af3903b5f9a3359f6d2f597c4b" ], "author": { "name": "Andrea Arcangeli", "email": "aarcange@redhat.com", "time": "Mon Oct 08 16:31:52 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:00 2013 -0800" }, "message": "mm: mmu_notifier: make the mmu_notifier srcu static\n\ncommit 70400303ce0c4ced3139499c676d5c79636b0c72 upstream.\n\nThe variable must be static especially given the variable name.\n\ns/RCU/SRCU/ over a few comments.\n\nSigned-off-by: Andrea Arcangeli \u003caarcange@redhat.com\u003e\nCc: Xiao Guangrong \u003cxiaoguangrong@linux.vnet.ibm.com\u003e\nCc: Sagi Grimberg \u003csagig@mellanox.com\u003e\nCc: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nCc: Haggai Eran \u003chaggaie@mellanox.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": "4209ee0d3f7992af3903b5f9a3359f6d2f597c4b", "tree": "5009887555ccf68907acf7ff9b14c9acfed6ee00", "parents": [ "362efcc9b0ba020f9124c70c56381ed64491aeca" ], "author": { "name": "Sagi Grimberg", "email": "sagig@mellanox.co.il", "time": "Mon Oct 08 16:29:24 2012 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:00 2013 -0800" }, "message": "mm: mmu_notifier: have mmu_notifiers use a global SRCU so they may safely schedule\n\ncommit 21a92735f660eaecf69a6f2e777f18463760ec32 upstream.\n\nWith an RCU based mmu_notifier implementation, any callout to\nmmu_notifier_invalidate_range_{start,end}() or\nmmu_notifier_invalidate_page() would not be allowed to call schedule()\nas that could potentially allow a modification to the mmu_notifier\nstructure while it is currently being used.\n\nSince srcu allocs 4 machine words per instance per cpu, we may end up\nwith memory exhaustion if we use srcu per mm. So all mms share a global\nsrcu. Note that during large mmu_notifier activity exit \u0026 unregister\npaths might hang for longer periods, but it is tolerable for current\nmmu_notifier clients.\n\nSigned-off-by: Sagi Grimberg \u003csagig@mellanox.co.il\u003e\nSigned-off-by: Andrea Arcangeli \u003caarcange@redhat.com\u003e\nCc: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nCc: Haggai Eran \u003chaggaie@mellanox.com\u003e\nCc: \"Paul E. McKenney\" \u003cpaulmck@us.ibm.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": "362efcc9b0ba020f9124c70c56381ed64491aeca", "tree": "2b1df024dd7a25a1278a4eaa1b7e2f87a621b9e2", "parents": [ "2199a6528ce9b299f3a3e2a6b50cfd197cbc135e" ], "author": { "name": "Bjorn Helgaas", "email": "bhelgaas@google.com", "time": "Tue Jan 29 16:44:27 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:00 2013 -0800" }, "message": "Driver core: treat unregistered bus_types as having no devices\n\ncommit 4fa3e78be7e985ca814ce2aa0c09cbee404efcf7 upstream.\n\nA bus_type has a list of devices (klist_devices), but the list and the\nsubsys_private structure that contains it are not initialized until the\nbus_type is registered with bus_register().\n\nThe panic/reboot path has fixups that look up devices in pci_bus_type. If\nwe panic before registering pci_bus_type, the bus_type exists but the list\ndoes not, so mach_reboot_fixups() trips over a null pointer and panics\nagain:\n\n mach_reboot_fixups\n pci_get_device\n ..\n bus_find_device(\u0026pci_bus_type, ...)\n bus-\u003ep is NULL\n\nJoonsoo reported a problem when panicking before PCI was initialized.\nI think this patch should be sufficient to replace the patch he posted\nhere: https://lkml.org/lkml/2012/12/28/75 (\"[PATCH] x86, reboot: skip\nreboot_fixups in early boot phase\")\n\nReported-by: Joonsoo Kim \u003cjs1304@gmail.com\u003e\nSigned-off-by: Bjorn Helgaas \u003cbhelgaas@google.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "2199a6528ce9b299f3a3e2a6b50cfd197cbc135e", "tree": "0c20d1cf584f4e7e74a7e6cb1159d351d1c34d92", "parents": [ "4f4eb62481b02ffec9edee9f109d22d6debe0281" ], "author": { "name": "Wei Liu", "email": "wei.liu2@citrix.com", "time": "Mon Feb 18 14:57:58 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:00 2013 -0800" }, "message": "xen: close evtchn port if binding to irq fails\n\ncommit e7e44e444876478d50630f57b0c31d29f6725020 upstream.\n\nSigned-off-by: Wei Liu \u003cwei.liu2@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": "4f4eb62481b02ffec9edee9f109d22d6debe0281", "tree": "ca136eea35c663caf6a7e8e9a212a34c84cf06e3", "parents": [ "6a171676006047cd613093b74a6cfdcba8686065" ], "author": { "name": "Stefan Bader", "email": "stefan.bader@canonical.com", "time": "Fri Feb 15 09:48:52 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:00 2013 -0800" }, "message": "xen: Send spinlock IPI to all waiters\n\ncommit 76eaca031f0af2bb303e405986f637811956a422 upstream.\n\nThere is a loophole between Xen\u0027s current implementation of\npv-spinlocks and the scheduler. This was triggerable through\na testcase until v3.6 changed the TLB flushing code. The\nproblem potentially is still there just not observable in the\nsame way.\n\nWhat could happen was (is):\n\n1. CPU n tries to schedule task x away and goes into a slow\n wait for the runq lock of CPU n-# (must be one with a lower\n number).\n2. CPU n-#, while processing softirqs, tries to balance domains\n and goes into a slow wait for its own runq lock (for updating\n some records). Since this is a spin_lock_irqsave in softirq\n context, interrupts will be re-enabled for the duration of\n the poll_irq hypercall used by Xen.\n3. Before the runq lock of CPU n-# is unlocked, CPU n-1 receives\n an interrupt (e.g. endio) and when processing the interrupt,\n tries to wake up task x. But that is in schedule and still\n on_cpu, so try_to_wake_up goes into a tight loop.\n4. The runq lock of CPU n-# gets unlocked, but the message only\n gets sent to the first waiter, which is CPU n-# and that is\n busily stuck.\n5. CPU n-# never returns from the nested interruption to take and\n release the lock because the scheduler uses a busy wait.\n And CPU n never finishes the task migration because the unlock\n notification only went to CPU n-#.\n\nTo avoid this and since the unlocking code has no real sense of\nwhich waiter is best suited to grab the lock, just send the IPI\nto all of them. This causes the waiters to return from the hyper-\ncall (those not interrupted at least) and do active spinlocking.\n\nBugLink: http://bugs.launchpad.net/bugs/1011792\n\nAcked-by: Jan Beulich \u003cJBeulich@suse.com\u003e\nSigned-off-by: Stefan Bader \u003cstefan.bader@canonical.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": "6a171676006047cd613093b74a6cfdcba8686065", "tree": "b973676f1d440f7ac430bff3e4ad807cb73a089e", "parents": [ "d1179077b018d6c5488eaaa5c71349094d5104f3" ], "author": { "name": "Jussi Kivilinna", "email": "jussi.kivilinna@mbnet.fi", "time": "Mon Feb 18 10:29:30 2013 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:00 2013 -0800" }, "message": "rtlwifi: usb: allocate URB control message setup_packet and data buffer separately\n\ncommit bc6b89237acb3dee6af6e64e51a18255fef89cc2 upstream.\n\nrtlwifi allocates both setup_packet and data buffer of control message urb,\nusing shared kmalloc in _usbctrl_vendorreq_async_write. Structure used for\nallocating is:\n\tstruct {\n\t\tu8 data[254];\n\t\tstruct usb_ctrlrequest dr;\n\t};\n\nBecause \u0027struct usb_ctrlrequest\u0027 is __packed, setup packet is unaligned and\nDMA mapping of both \u0027data\u0027 and \u0027dr\u0027 confuses ARM/sunxi, leading to memory\ncorruptions and freezes.\n\nPatch changes setup packet to be allocated separately.\n\n[v2]:\n - Use WARN_ON_ONCE instead of WARN_ON\n\nSigned-off-by: Jussi Kivilinna \u003cjussi.kivilinna@mbnet.fi\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d1179077b018d6c5488eaaa5c71349094d5104f3", "tree": "404b1e1b0a737b4c2b3469efbeaf2d3caa205167", "parents": [ "1946c763f335fcc7482936c039fddeb179c7f384" ], "author": { "name": "Larry Finger", "email": "Larry.Finger@lwfinger.net", "time": "Fri Feb 08 12:28:18 2013 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:59:00 2013 -0800" }, "message": "rtlwifi: rtl8192cu: Add new USB ID\n\ncommit 8708aac79e4572ba673d7a21e94ddca9f3abb7fc upstream.\n\nA new model of the RTL8188CUS has appeared.\n\nReported-and-tested-by: Thomas Rosenkrantz \u003ctom.rosary@googlemail.com\u003e\nSigned-off-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1946c763f335fcc7482936c039fddeb179c7f384", "tree": "1c792af5e522a351f92ad67bcba08f3ebf63e8ab", "parents": [ "906c9c42101742d1ec86ab22eb55d24d496830a7" ], "author": { "name": "Larry Finger", "email": "Larry.Finger@lwfinger.net", "time": "Sun Feb 17 17:01:20 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:59 2013 -0800" }, "message": "b43: Increase number of RX DMA slots\n\ncommit ccae0e50c16a7f7adb029c169147400d1ce9f703 upstream.\n\nBastian Bittorf reported that some of the silent freezes on a Linksys WRT54G\nwere due to overflow of the RX DMA ring buffer, which was created with 64\nslots. That finding reminded me that I was seeing similar crashed on a netbook,\nwhich also has a relatively slow processor. After increasing the number of\nslots to 128, runs on the netbook that previously failed now worked; however,\nI found that 109 slots had been used in one test. For that reason, the number\nof slots is being increased to 256.\n\nSigned-off-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nCc: Bastian Bittorf \u003cbittorf@bluebottle.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": "906c9c42101742d1ec86ab22eb55d24d496830a7", "tree": "f0f61878a686f7cddbfc483f57cf8e244eb5aa1b", "parents": [ "46605dae03a55a70d7fd9886f466b435afc7738b" ], "author": { "name": "Johan Hovold", "email": "jhovold@gmail.com", "time": "Wed Feb 13 17:53:28 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:59 2013 -0800" }, "message": "USB: serial: fix null-pointer dereferences on disconnect\n\ncommit b2ca699076573c94fee9a73cb0d8645383b602a0 upstream.\n\nMake sure serial-driver dtr_rts is called with disc_mutex held after\nchecking the disconnected flag.\n\nDue to a bug in the tty layer, dtr_rts may get called after a device has\nbeen disconnected and the tty-device unregistered. Some drivers have had\nindividual checks for disconnect to make sure the disconnected interface\nwas not accessed, but this should really be handled in usb-serial core\n(at least until the long-standing tty-bug has been fixed).\n\nNote that the problem has been made more acute with commit 0998d0631001\n(\"device-core: Ensure drvdata \u003d NULL when no driver is bound\") as the\nport data is now also NULL when dtr_rts is called resulting in further\noopses.\n\nReported-by: Chris Ruehl \u003cchris.ruehl@gtsys.com.hk\u003e\nSigned-off-by: Johan Hovold \u003cjhovold@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "46605dae03a55a70d7fd9886f466b435afc7738b", "tree": "16925a0b7170e3cdfee53930ae7a0ce65447ec74", "parents": [ "0c10d7fd0d53e3e44cc04edc37120bce6d74e2ca" ], "author": { "name": "Oleg Nesterov", "email": "oleg@redhat.com", "time": "Tue Jan 29 20:07:41 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:59 2013 -0800" }, "message": "tty: set_termios/set_termiox should not return -EINTR\n\ncommit 183d95cdd834381c594d3aa801c1f9f9c0c54fa9 upstream.\n\nSee https://bugzilla.redhat.com/show_bug.cgi?id\u003d904907\nread command causes bash to abort with double free or corruption (out).\n\nA simple test-case from Roman:\n\n\t// Compile the reproducer and send sigchld ti that process.\n\t// EINTR occurs even if SA_RESTART flag is set.\n\n\tvoid handler(int sig)\n\t{\n\t}\n\n\tmain()\n\t{\n\t struct sigaction act;\n\t act.sa_handler \u003d handler;\n\t act.sa_flags \u003d SA_RESTART;\n\t sigaction (SIGCHLD, \u0026act, 0);\n\t struct termio ttp;\n\t ioctl(0, TCGETA, \u0026ttp);\n\t while(1)\n\t {\n\t if (ioctl(0, TCSETAW, ttp) \u003c 0)\n\t {\n\t\tif (errno \u003d\u003d EINTR)\n\t\t{\n\t\t fprintf(stderr, \"BUG!\"); return(1);\n\t\t}\n\t }\n\t }\n\t}\n\nChange set_termios/set_termiox to return -ERESTARTSYS to fix this\nparticular problem.\n\nI didn\u0027t dare to change other EINTR\u0027s in drivers/tty/, but they look\nequally wrong.\n\nReported-by: Roman Rakus \u003crrakus@redhat.com\u003e\nReported-by: Lingzhu Xiang \u003clxiang@redhat.com\u003e\nSigned-off-by: Oleg Nesterov \u003coleg@redhat.com\u003e\nCc: Jiri Slaby \u003cjslaby@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0c10d7fd0d53e3e44cc04edc37120bce6d74e2ca", "tree": "720cd82debce25b029a9a04087b3e728c47c4724", "parents": [ "ceb0446b6dff34bfe41c9fa54796e7b21a17bd56" ], "author": { "name": "Dirkjan Bussink", "email": "d.bussink@gmail.com", "time": "Wed Jan 30 11:44:50 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:59 2013 -0800" }, "message": "tty: Prevent deadlock in n_gsm driver\n\ncommit 4d9b109060f690f5c835130ff54165ae157b3087 upstream.\n\nThis change fixes a deadlock when the multiplexer is closed while there\nare still client side ports open.\n\nWhen the multiplexer is closed and there are active tty\u0027s it tries to\nclose them with tty_vhangup. This has a problem though, because\ntty_vhangup needs the tty_lock. This patch changes it to unlock the\ntty_lock before attempting the hangup and relocks afterwards. The\nadditional call to tty_port_tty_set is needed because otherwise the\nport stays active because of the reference counter.\n\nThis change also exposed another problem that other code paths don\u0027t\nexpect that the multiplexer could have been closed. This patch also adds\nchecks for these cases in the gsmtty_ class of function that could be\ncalled.\n\nThe documentation explicitly states that \"first close all virtual ports\nbefore closing the physical port\" but we\u0027ve found this to not always\nreality in our field situations. The GPRS / UTMS modem sometimes crashes\nand needs a power cycle in that case which means cleanly shutting down\neverything is not always possible. This change makes it much more robust\nfor our situation where at least the system is recoverable with this patch\nand doesn\u0027t hang in a deadlock situation inside the kernel.\n\nThe patch is against the long term support kernel (3.4.27) and should\napply cleanly to more recent branches. Tested with a Telit GE864-QUADV2\nand Telit HE910 modem.\n\nSigned-off-by: Dirkjan Bussink \u003cdirkjan.bussink@nedap.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ceb0446b6dff34bfe41c9fa54796e7b21a17bd56", "tree": "2163be2454a07459fa32cf95eb3ed919e0f5e7ac", "parents": [ "7fb3e95821e901ed594c88747e5729a39723d2ff" ], "author": { "name": "Denis Efremov", "email": "yefremov.denis@gmail.com", "time": "Mon Feb 11 19:04:06 2013 +0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:59 2013 -0800" }, "message": "ALSA: rme32.c irq enabling after spin_lock_irq\n\ncommit f49a59c4471d81a233e09dda45187cc44fda009d upstream.\n\nAccording to the other code in this driver and similar\ncode in rme96 it seems, that spin_lock_irq in\nsnd_rme32_capture_close function should be paired\nwith spin_unlock_irq.\n\nFound by Linux Driver Verification project (linuxtesting.org).\n\nSigned-off-by: Denis Efremov \u003cyefremov.denis@gmail.com\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7fb3e95821e901ed594c88747e5729a39723d2ff", "tree": "da1f1c414c3a2c7b174327a9472c0ab17530fb58", "parents": [ "507d34bf74e3cef390d74b180ed9695e6bf3dcbb" ], "author": { "name": "Denis Efremov", "email": "yefremov.denis@gmail.com", "time": "Mon Feb 11 19:49:48 2013 +0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:59 2013 -0800" }, "message": "ALSA: ali5451: remove irq enabling in pointer callback\n\ncommit dacae5a19b4cbe1b5e3a86de23ea74cbe9ec9652 upstream.\n\nsnd_ali_pointer function is called with local\ninterrupts disabled. However it seems very strange to\nreenable them in such way.\n\nFound by Linux Driver Verification project (linuxtesting.org).\n\nSigned-off-by: Denis Efremov \u003cyefremov.denis@gmail.com\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "507d34bf74e3cef390d74b180ed9695e6bf3dcbb", "tree": "f914c8fa84f6c80b32a8eaffa7889e5ea2d6ec6d", "parents": [ "dd9c58a90c955ae794c1080156db8d8f64a52a21" ], "author": { "name": "Olaf Hering", "email": "[mailto:olaf@aepfle.de]", "time": "Sun Feb 03 17:22:37 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:59 2013 -0800" }, "message": "x86: Hyper-V: register clocksource only if its advertised\n\ncommit 32068f6527b8f1822a30671dedaf59c567325026 upstream.\n\nEnable hyperv_clocksource only if its advertised as a feature.\nXenServer 6 returns the signature which is checked in\nms_hyperv_platform(), but it does not offer all features. Currently the\nclocksource is enabled unconditionally in ms_hyperv_init_platform(), and\nthe result is a hanging guest.\n\nHyper-V spec Bit 1 indicates the availability of Partition Reference\nCounter. Register the clocksource only if this bit is set.\n\nThe guest in question prints this in dmesg:\n [ 0.000000] Hypervisor detected: Microsoft HyperV\n [ 0.000000] HyperV: features 0x70, hints 0x0\n\nThis bug can be reproduced easily be setting \u0027viridian\u003d1\u0027 in a HVM domU\n.cfg file. A workaround without this patch is to boot the HVM guest with\n\u0027clocksource\u003djiffies\u0027.\n\nSigned-off-by: Olaf Hering \u003colaf@aepfle.de\u003e\nLink: http://lkml.kernel.org/r/1359940959-32168-1-git-send-email-kys@microsoft.com\nSigned-off-by: K. Y. Srinivasan \u003ckys@microsoft.com\u003e\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dd9c58a90c955ae794c1080156db8d8f64a52a21", "tree": "a232bd8d075111e352edf86dfc9de49b7fcddce3", "parents": [ "7c3e516d99265e4aa915f3c05611b0f426bf8ce3" ], "author": { "name": "Leonid Shatz", "email": "leonid.shatz@ravellosystems.com", "time": "Mon Feb 04 14:33:37 2013 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:59 2013 -0800" }, "message": "hrtimer: Prevent hrtimer_enqueue_reprogram race\n\ncommit b22affe0aef429d657bc6505aacb1c569340ddd2 upstream.\n\nhrtimer_enqueue_reprogram contains a race which could result in\ntimer.base switch during unlock/lock sequence.\n\nhrtimer_enqueue_reprogram is releasing the lock protecting the timer\nbase for calling raise_softirq_irqsoff() due to a lock ordering issue\nversus rq-\u003elock.\n\nIf during that time another CPU calls __hrtimer_start_range_ns() on\nthe same hrtimer, the timer base might switch, before the current CPU\ncan lock base-\u003elock again and therefor the unlock_timer_base() call\nwill unlock the wrong lock.\n\n[ tglx: Added comment and massaged changelog ]\n\nSigned-off-by: Leonid Shatz \u003cleonid.shatz@ravellosystems.com\u003e\nSigned-off-by: Izik Eidus \u003cizik.eidus@ravellosystems.com\u003e\nCc: Andrea Arcangeli \u003caarcange@redhat.com\u003e\nLink: http://lkml.kernel.org/r/1359981217-389-1-git-send-email-izik.eidus@ravellosystems.com\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7c3e516d99265e4aa915f3c05611b0f426bf8ce3", "tree": "ca0e3900b725d528910363170a55f591c40fec50", "parents": [ "b3c57f009cfd9ed81737169c4026bfd03191d993" ], "author": { "name": "Stanislaw Gruszka", "email": "sgruszka@redhat.com", "time": "Fri Feb 15 11:08:11 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:59 2013 -0800" }, "message": "posix-cpu-timers: Fix nanosleep task_struct leak\n\ncommit e6c42c295e071dd74a66b5a9fcf4f44049888ed8 upstream.\n\nThe trinity fuzzer triggered a task_struct reference leak via\nclock_nanosleep with CPU_TIMERs. do_cpu_nanosleep() calls\nposic_cpu_timer_create(), but misses a corresponding\nposix_cpu_timer_del() which leads to the task_struct reference leak.\n\nReported-and-tested-by: Tommi Rantala \u003ctt.rantala@gmail.com\u003e\nSigned-off-by: Stanislaw Gruszka \u003csgruszka@redhat.com\u003e\nCc: Dave Jones \u003cdavej@redhat.com\u003e\nCc: John Stultz \u003cjohn.stultz@linaro.org\u003e\nCc: Oleg Nesterov \u003coleg@redhat.com\u003e\nLink: http://lkml.kernel.org/r/20130215100810.GF4392@redhat.com\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b3c57f009cfd9ed81737169c4026bfd03191d993", "tree": "73ae8bf6b8258783eb608f18f4c984d36c2a6fcf", "parents": [ "526a26556b9069238ea7eecb9095cc672daef0e5" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Nov 23 10:08:44 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:58 2013 -0800" }, "message": "genirq: Avoid deadlock in spurious handling\n\ncommit e716efde75267eab919cdb2bef5b2cb77f305326 upstream.\n\ncommit 52553ddf(genirq: fix regression in irqfixup, irqpoll)\nintroduced a potential deadlock by calling the action handler with the\nirq descriptor lock held.\n\nRemove the call and let the handling code run even for an interrupt\nwhere only a single action is registered. That matches the goal of\nthe above commit and avoids the deadlock.\n\nDocument the confusing action \u003d desc-\u003eaction reload in the handling\nloop while at it.\n\nReported-and-tested-by: \"Wang, Warner\" \u003cwarner.wang@hp.com\u003e\nTested-by: Edward Donovan \u003cedward.donovan@numble.net\u003e\nCc: \"Wang, Song-Bo (Stoney)\" \u003csong-bo.wang@hp.com\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "526a26556b9069238ea7eecb9095cc672daef0e5", "tree": "8dc2f9265c4ec28a26528bf8ab37b3af49449f43", "parents": [ "17c2f96bd1de5999900303b3eb923b8cdf6ee2ba" ], "author": { "name": "H. Peter Anvin", "email": "hpa@linux.intel.com", "time": "Thu Feb 07 17:14:08 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:58 2013 -0800" }, "message": "timeconst.pl: Eliminate Perl warning\n\ncommit 63a3f603413ffe82ad775f2d62a5afff87fd94a0 upstream.\n\ndefined(@array) is deprecated in Perl and gives off a warning.\nRestructure the code to remove that warning.\n\n[ hpa: it would be interesting to revert to the timeconst.bc script.\n It appears that the failures reported by akpm during testing of\n that script was due to a known broken version of make, not a problem\n with bc. The Makefile rules could probably be restructured to avoid\n the make bug, or it is probably old enough that it doesn\u0027t matter. ]\n\nReported-by: Andi Kleen \u003cak@linux.intel.com\u003e\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nCc: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "17c2f96bd1de5999900303b3eb923b8cdf6ee2ba", "tree": "f6ba7eb0b52708858ab17225f83b5d738bebba5e", "parents": [ "5c444ede11d516377ec6a3230d450441f46cfb4f" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Feb 18 09:58:02 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:58 2013 -0800" }, "message": "mm: fix pageblock bitmap allocation\n\ncommit 7c45512df987c5619db041b5c9b80d281e26d3db upstream.\n\nCommit c060f943d092 (\"mm: use aligned zone start for pfn_to_bitidx\ncalculation\") fixed out calculation of the index into the pageblock\nbitmap when a !SPARSEMEM zome was not aligned to pageblock_nr_pages.\n\nHowever, the _allocation_ of that bitmap had never taken this alignment\nrequirement into accout, so depending on the exact size and alignment of\nthe zone, the use of that index could then access past the allocation,\nresulting in some very subtle memory corruption.\n\nThis was reported (and bisected) by Ingo Molnar: one of his random\nconfig builds would hang with certain very specific kernel command line\noptions.\n\nIn the meantime, commit c060f943d092 has been marked for stable, so this\nfix needs to be back-ported to the stable kernels that backported the\ncommit to use the right alignment.\n\nBisected-and-tested-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nAcked-by: Mel Gorman \u003cmgorman@suse.de\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5c444ede11d516377ec6a3230d450441f46cfb4f", "tree": "c0c86e7064e79eec0820eff152aca27a97324a53", "parents": [ "99867c9603b88d11ef8c7223b978d389fcb8e4c6" ], "author": { "name": "H. Peter Anvin", "email": "hpa@linux.intel.com", "time": "Thu Jan 31 14:00:48 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:58 2013 -0800" }, "message": "x86-32, mm: Remove reference to alloc_remap()\n\ncommit 07f4207a305c834f528d08428df4531744e25678 upstream.\n\nWe have removed the remap allocator for x86-32, and x86-64 never had\nit (and doesn\u0027t need it). Remove residual reference to it.\n\nReported-by: Yinghai Lu \u003cyinghai@kernel.org\u003e\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nCc: Dave Hansen \u003cdave@linux.vnet.ibm.com\u003e\nLink: http://lkml.kernel.org/r/CAE9FiQVn6_QZi3fNQ-JHYiR-7jeDJ5hT0SyT_%2BzVvfOj\u003dPzF3w@mail.gmail.com\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "99867c9603b88d11ef8c7223b978d389fcb8e4c6", "tree": "3b0505025380cb6193adac2e7ed9d97cd4e968af", "parents": [ "025cee7f8fef02af09b03c8e1cd9843cb32adf9b" ], "author": { "name": "H. Peter Anvin", "email": "hpa@linux.intel.com", "time": "Thu Jan 31 13:53:10 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:58 2013 -0800" }, "message": "x86-32, mm: Remove reference to resume_map_numa_kva()\n\ncommit bb112aec5ee41427e9b9726e3d57b896709598ed upstream.\n\nRemove reference to removed function resume_map_numa_kva().\n\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nCc: Dave Hansen \u003cdave@linux.vnet.ibm.com\u003e\nLink: http://lkml.kernel.org/r/20130131005616.1C79F411@kernel.stglabs.ibm.com\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "025cee7f8fef02af09b03c8e1cd9843cb32adf9b", "tree": "1362d1ba2e8d3cf9cd8a2fa7b4cbee67400daee8", "parents": [ "1c3000a67a350c7ac31897cf22ec8e4ddd47d3aa" ], "author": { "name": "Dave Hansen", "email": "dave@linux.vnet.ibm.com", "time": "Wed Jan 30 16:56:16 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 28 06:58:58 2013 -0800" }, "message": "x86-32, mm: Rip out x86_32 NUMA remapping code\n\ncommit f03574f2d5b2d6229dcdf2d322848065f72953c7 upstream.\n\nThis code was an optimization for 32-bit NUMA systems.\n\nIt has probably been the cause of a number of subtle bugs over\nthe years, although the conditions to excite them would have\nbeen hard to trigger. Essentially, we remap part of the kernel\nlinear mapping area, and then sometimes part of that area gets\nfreed back in to the bootmem allocator. If those pages get\nused by kernel data structures (say mem_map[] or a dentry),\nthere\u0027s no big deal. But, if anyone ever tried to use the\nlinear mapping for these pages _and_ cared about their physical\naddress, bad things happen.\n\nFor instance, say you passed __GFP_ZERO to the page allocator\nand then happened to get handed one of these pages, it zero the\nremapped page, but it would make a pte to the _old_ page.\nThere are probably a hundred other ways that it could screw\nwith things.\n\nWe don\u0027t need to hang on to performance optimizations for\nthese old boxes any more. All my 32-bit NUMA systems are long\ndead and buried, and I probably had access to more than most\npeople.\n\nThis code is causing real things to break today:\n\n\thttps://lkml.org/lkml/2013/1/9/376\n\nI looked in to actually fixing this, but it requires surgery\nto way too much brittle code, as well as stuff like\nper_cpu_ptr_to_phys().\n\n[ hpa: Cc: this for -stable, since it is a memory corruption issue.\n However, an alternative is to simply mark NUMA as depends BROKEN\n rather than EXPERIMENTAL in the X86_32 subclause... ]\n\nLink: http://lkml.kernel.org/r/20130131005616.1C79F411@kernel.stglabs.ibm.com\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1c3000a67a350c7ac31897cf22ec8e4ddd47d3aa", "tree": "2e353f5e2f3192c5b5d255b4e42294eb7a040786", "parents": [ "ce0030c00f95cf9110d9cdcd41e901e1fb814417" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 21 10:05:05 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 21 10:05:05 2013 -0800" }, "message": "3.4.33\n" }, { "commit": "ce0030c00f95cf9110d9cdcd41e901e1fb814417", "tree": "40b124b99205bd469ed156b682d7f0f4e5726e5a", "parents": [ "9ad3bfb9e26197c378d6c239180ed7bcf7c29fd8" ], "author": { "name": "Alexandre SIMON", "email": "Alexandre.Simon@univ-lorraine.fr", "time": "Fri Feb 01 15:31:54 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 21 10:04:57 2013 -0800" }, "message": "printk: fix buffer overflow when calling log_prefix function from call_console_drivers\n\nThis patch corrects a buffer overflow in kernels from 3.0 to 3.4 when calling\nlog_prefix() function from call_console_drivers().\n\nThis bug existed in previous releases but has been revealed with commit\n162a7e7500f9664636e649ba59defe541b7c2c60 (2.6.39 \u003d\u003e 3.0) that made changes\nabout how to allocate memory for early printk buffer (use of memblock_alloc).\nIt disappears with commit 7ff9554bb578ba02166071d2d487b7fc7d860d62 (3.4 \u003d\u003e 3.5)\nthat does a refactoring of printk buffer management.\n\nIn log_prefix(), the access to \"p[0]\", \"p[1]\", \"p[2]\" or\n\"simple_strtoul(\u0026p[1], \u0026endp, 10)\" may cause a buffer overflow as this\nfunction is called from call_console_drivers by passing \"\u0026LOG_BUF(cur_index)\"\nwhere the index must be masked to do not exceed the buffer\u0027s boundary.\n\nThe trick is to prepare in call_console_drivers() a buffer with the necessary\ndata (PRI field of syslog message) to be safely evaluated in log_prefix().\n\nThis patch can be applied to stable kernel branches 3.0.y, 3.2.y and 3.4.y.\n\nWithout this patch, one can freeze a server running this loop from shell :\n $ export DUMMY\u003d`cat /dev/urandom | tr -dc \u002712345AZERTYUIOPQSDFGHJKLMWXCVBNazertyuiopqsdfghjklmwxcvbn\u0027 | head -c255`\n $ while true do ; echo $DUMMY \u003e /dev/kmsg ; done\n\nThe \"server freeze\" depends on where memblock_alloc does allocate printk buffer :\nif the buffer overflow is inside another kernel allocation the problem may not\nbe revealed, else the server may hangs up.\n\nSigned-off-by: Alexandre SIMON \u003cAlexandre.Simon@univ-lorraine.fr\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "9ad3bfb9e26197c378d6c239180ed7bcf7c29fd8", "tree": "354fdd516629fc58bea3f499b32e2b080f777058", "parents": [ "248924caf7d1e452e3cad8433ae7b4942654ea8b" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Feb 17 10:49:37 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Feb 17 10:49:37 2013 -0800" }, "message": "Linux 3.4.32\n" }, { "commit": "248924caf7d1e452e3cad8433ae7b4942654ea8b", "tree": "8512843c5248c7c5b507a546cba54e5ac7f37b57", "parents": [ "266c43c175a51002b04c18a453a39708d1775ced" ], "author": { "name": "Alexander Duyck", "email": "alexander.h.duyck@intel.com", "time": "Wed Aug 08 05:23:22 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Feb 17 10:49:26 2013 -0800" }, "message": "igb: Remove artificial restriction on RQDPC stat reading\n\ncommit ae1c07a6b7ced6c0c94c99e3b53f4e7856fa8bff upstream.\n\nFor some reason the reading of the RQDPC register was being artificially\nlimited to 4K. Instead of limiting the value we should read the value and\nadd the full amount. Otherwise this can lead to a misleading number of\ndropped packets when the actual value is in fact much higher.\n\nSigned-off-by: Alexander Duyck \u003calexander.h.duyck@intel.com\u003e\nTested-by: Jeff Pieper \u003cjeffrey.e.pieper@intel.com\u003e\nSigned-off-by: Jeff Kirsher \u003cjeffrey.t.kirsher@intel.com\u003e\nCc: Vinson Lee \u003cvlee@twitter.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "266c43c175a51002b04c18a453a39708d1775ced", "tree": "0acd6525da8acda8848f20e3f13d86ce80d4fc49", "parents": [ "15295d7dc33491a0a015a0f48d04bbaa696b802d" ], "author": { "name": "Satoru Takeuchi", "email": "takeuchi_satoru@jp.fujitsu.com", "time": "Thu Feb 14 09:12:52 2013 +0900" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Feb 17 10:49:26 2013 -0800" }, "message": "efi: Clear EFI_RUNTIME_SERVICES rather than EFI_BOOT by \"noefi\" boot parameter\n\ncommit 1de63d60cd5b0d33a812efa455d5933bf1564a51 upstream.\n\nThere was a serious problem in samsung-laptop that its platform driver is\ndesigned to run under BIOS and running under EFI can cause the machine to\nbecome bricked or can cause Machine Check Exceptions.\n\n Discussion about this problem:\n https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557\n https://bugzilla.kernel.org/show_bug.cgi?id\u003d47121\n\n The patches to fix this problem:\n efi: Make \u0027efi_enabled\u0027 a function to query EFI facilities\n 83e68189745ad931c2afd45d8ee3303929233e7f\n\n samsung-laptop: Disable on EFI hardware\n e0094244e41c4d0c7ad69920681972fc45d8ce34\n\nUnfortunately this problem comes back again if users specify \"noefi\" option.\nThis parameter clears EFI_BOOT and that driver continues to run even if running\nunder EFI. Refer to the document, this parameter should clear\nEFI_RUNTIME_SERVICES instead.\n\nDocumentation/kernel-parameters.txt:\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\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...\n\tnoefi\t\t[X86] Disable EFI runtime services support.\n...\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\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\nDocumentation/x86/x86_64/uefi.txt:\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\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...\n- If some or all EFI runtime services don\u0027t work, you can try following\n kernel command line parameters to turn off some or all EFI runtime\n services.\n\tnoefi\t\tturn off all EFI runtime services\n...\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\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\nSigned-off-by: Satoru Takeuchi \u003ctakeuchi_satoru@jp.fujitsu.com\u003e\nLink: http://lkml.kernel.org/r/511C2C04.2070108@jp.fujitsu.com\nCc: Matt Fleming \u003cmatt.fleming@intel.com\u003e\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "15295d7dc33491a0a015a0f48d04bbaa696b802d", "tree": "f16b86cb84bcf807dee09fc22b281d3972759bf7", "parents": [ "dc66ff14a9489f8c239ecc43a20ca946cce8d217" ], "author": { "name": "Rafael J. Wysocki", "email": "rjw@sisk.pl", "time": "Mon Feb 11 20:49:49 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Feb 17 10:49:26 2013 -0800" }, "message": "PCI/PM: Clean up PME state when removing a device\n\ncommit 249bfb83cf8ba658955f0245ac3981d941f746ee upstream.\n\nDevices are added to pci_pme_list when drivers use pci_enable_wake()\nor pci_wake_from_d3(), but they aren\u0027t removed from the list unless\nthe driver explicitly disables wakeup. Many drivers never disable\nwakeup, so their devices remain on the list even after they are\nremoved, e.g., via hotplug. A subsequent PME poll will oops when\nit tries to touch the device.\n\nThis patch disables PME# on a device before removing it, which removes\nthe device from pci_pme_list. This is safe even if the device never\nhad PME# enabled.\n\nThis oops can be triggered by unplugging a Thunderbolt ethernet adapter\non a Macbook Pro, as reported by Daniel below.\n\n[bhelgaas: changelog]\nReference: http://lkml.kernel.org/r/CAMVG2svG21yiM1wkH4_2pen2n+cr2-Zv7TbH3Gj+8MwevZjDbw@mail.gmail.com\nReported-and-tested-by: Daniel J Blueman \u003cdaniel@quora.org\u003e\nSigned-off-by: Rafael J. Wysocki \u003crafael.j.wysocki@intel.com\u003e\nSigned-off-by: Bjorn Helgaas \u003cbhelgaas@google.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dc66ff14a9489f8c239ecc43a20ca946cce8d217", "tree": "8fbed3843b3ae682b468285ba552d03ca863cdb2", "parents": [ "44f80d63b26469593b633bc40049538683e70311" ], "author": { "name": "Jan Beulich", "email": "JBeulich@suse.com", "time": "Thu Jan 24 13:11:10 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Feb 17 10:49:26 2013 -0800" }, "message": "x86/xen: don\u0027t assume %ds is usable in xen_iret for 32-bit PVOPS.\n\ncommit 13d2b4d11d69a92574a55bfd985cfb0ca77aebdc upstream.\n\nThis fixes CVE-2013-0228 / XSA-42\n\nDrew Jones while working on CVE-2013-0190 found that that unprivileged guest user\nin 32bit PV guest can use to crash the \u003e guest with the panic like this:\n\n-------------\ngeneral protection fault: 0000 [#1] SMP\nlast sysfs file: /sys/devices/vbd-51712/block/xvda/dev\nModules linked in: sunrpc ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4\niptable_filter ip_tables ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6\nxt_state nf_conntrack ip6table_filter ip6_tables ipv6 xen_netfront ext4\nmbcache jbd2 xen_blkfront dm_mirror dm_region_hash dm_log dm_mod [last\nunloaded: scsi_wait_scan]\n\nPid: 1250, comm: r Not tainted 2.6.32-356.el6.i686 #1\nEIP: 0061:[\u003cc0407462\u003e] EFLAGS: 00010086 CPU: 0\nEIP is at xen_iret+0x12/0x2b\nEAX: eb8d0000 EBX: 00000001 ECX: 08049860 EDX: 00000010\nESI: 00000000 EDI: 003d0f00 EBP: b77f8388 ESP: eb8d1fe0\n DS: 0000 ES: 007b FS: 0000 GS: 00e0 SS: 0069\nProcess r (pid: 1250, ti\u003deb8d0000 task\u003dc2953550 task.ti\u003deb8d0000)\nStack:\n 00000000 0027f416 00000073 00000206 b77f8364 0000007b 00000000 00000000\nCall Trace:\nCode: c3 8b 44 24 18 81 4c 24 38 00 02 00 00 8d 64 24 30 e9 03 00 00 00\n8d 76 00 f7 44 24 08 00 00 02 80 75 33 50 b8 00 e0 ff ff 21 e0 \u003c8b\u003e 40\n10 8b 04 85 a0 f6 ab c0 8b 80 0c b0 b3 c0 f6 44 24 0d 02\nEIP: [\u003cc0407462\u003e] xen_iret+0x12/0x2b SS:ESP 0069:eb8d1fe0\ngeneral protection fault: 0000 [#2]\n---[ end trace ab0d29a492dcd330 ]---\nKernel panic - not syncing: Fatal exception\nPid: 1250, comm: r Tainted: G D ---------------\n2.6.32-356.el6.i686 #1\nCall Trace:\n [\u003cc08476df\u003e] ? panic+0x6e/0x122\n [\u003cc084b63c\u003e] ? oops_end+0xbc/0xd0\n [\u003cc084b260\u003e] ? do_general_protection+0x0/0x210\n [\u003cc084a9b7\u003e] ? error_code+0x73/\n-------------\n\nPetr says: \"\n I\u0027ve analysed the bug and I think that xen_iret() cannot cope with\n mangled DS, in this case zeroed out (null selector/descriptor) by either\n xen_failsafe_callback() or RESTORE_REGS because the corresponding LDT\n entry was invalidated by the reproducer. \"\n\nJan took a look at the preliminary patch and came up a fix that solves\nthis problem:\n\n\"This code gets called after all registers other than those handled by\nIRET got already restored, hence a null selector in %ds or a non-null\none that got loaded from a code or read-only data descriptor would\ncause a kernel mode fault (with the potential of crashing the kernel\nas a whole, if panic_on_oops is set).\"\n\nThe way to fix this is to realize that the we can only relay on the\nregisters that IRET restores. The two that are guaranteed are the\n%cs and %ss as they are always fixed GDT selectors. Also they are\ninaccessible from user mode - so they cannot be altered. This is\nthe approach taken in this patch.\n\nAnother alternative option suggested by Jan would be to relay on\nthe subtle realization that using the %ebp or %esp relative references uses\nthe %ss segment. In which case we could switch from using %eax to %ebp and\nwould not need the %ss over-rides. That would also require one extra\ninstruction to compensate for the one place where the register is used\nas scaled index. However Andrew pointed out that is too subtle and if\nfurther work was to be done in this code-path it could escape folks attention\nand lead to accidents.\n\nReviewed-by: Petr Matousek \u003cpmatouse@redhat.com\u003e\nReported-by: Petr Matousek \u003cpmatouse@redhat.com\u003e\nReviewed-by: Andrew Cooper \u003candrew.cooper3@citrix.com\u003e\nSigned-off-by: Jan Beulich \u003cjbeulich@suse.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": "44f80d63b26469593b633bc40049538683e70311", "tree": "9485fbdc4c4a182e7c387aca7195c384e59b3868", "parents": [ "65f55391cf03b2e4bcfec63b08b8db032b4d6f3a" ], "author": { "name": "Mel Gorman", "email": "mgorman@suse.de", "time": "Mon Feb 11 14:52:36 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Feb 17 10:49:26 2013 -0800" }, "message": "x86/mm: Check if PUD is large when validating a kernel address\n\ncommit 0ee364eb316348ddf3e0dfcd986f5f13f528f821 upstream.\n\nA user reported the following oops when a backup process reads\n/proc/kcore:\n\n BUG: unable to handle kernel paging request at ffffbb00ff33b000\n IP: [\u003cffffffff8103157e\u003e] kern_addr_valid+0xbe/0x110\n [...]\n\n Call Trace:\n [\u003cffffffff811b8aaa\u003e] read_kcore+0x17a/0x370\n [\u003cffffffff811ad847\u003e] proc_reg_read+0x77/0xc0\n [\u003cffffffff81151687\u003e] vfs_read+0xc7/0x130\n [\u003cffffffff811517f3\u003e] sys_read+0x53/0xa0\n [\u003cffffffff81449692\u003e] system_call_fastpath+0x16/0x1b\n\nInvestigation determined that the bug triggered when reading\nsystem RAM at the 4G mark. On this system, that was the first\naddress using 1G pages for the virt-\u003ephys direct mapping so the\nPUD is pointing to a physical address, not a PMD page.\n\nThe problem is that the page table walker in kern_addr_valid() is\nnot checking pud_large() and treats the physical address as if\nit was a PMD. If it happens to look like pmd_none then it\u0027ll\nsilently fail, probably returning zeros instead of real data. If\nthe data happens to look like a present PMD though, it will be\nwalked resulting in the oops above.\n\nThis patch adds the necessary pud_large() check.\n\nUnfortunately the problem was not readily reproducible and now\nthey are running the backup program without accessing\n/proc/kcore so the patch has not been validated but I think it\nmakes sense.\n\nSigned-off-by: Mel Gorman \u003cmgorman@suse.de\u003e\nReviewed-by: Rik van Riel \u003criel@redhat.coM\u003e\nReviewed-by: Michal Hocko \u003cmhocko@suse.cz\u003e\nAcked-by: Johannes Weiner \u003channes@cmpxchg.org\u003e\nCc: linux-mm@kvack.org\nLink: http://lkml.kernel.org/r/20130211145236.GX21389@suse.de\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "65f55391cf03b2e4bcfec63b08b8db032b4d6f3a", "tree": "2ce99f5095bd900b1c54acfc0f2551f4a4047466", "parents": [ "e2ef6aad8a81c730bba92b2a44d758cabd7d9053" ], "author": { "name": "Stoney Wang", "email": "song-bo.wang@hp.com", "time": "Thu Feb 07 10:53:02 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Feb 17 10:49:25 2013 -0800" }, "message": "x86/apic: Work around boot failure on HP ProLiant DL980 G7 Server systems\n\ncommit cb214ede7657db458fd0b2a25ea0b28dbf900ebc upstream.\n\nWhen a HP ProLiant DL980 G7 Server boots a regular kernel,\nthere will be intermittent lost interrupts which could\nresult in a hang or (in extreme cases) data loss.\n\nThe reason is that this system only supports x2apic physical\nmode, while the kernel boots with a logical-cluster default\nsetting.\n\nThis bug can be worked around by specifying the \"x2apic_phys\" or\n\"nox2apic\" boot option, but we want to handle this system\nwithout requiring manual workarounds.\n\nThe BIOS sets ACPI_FADT_APIC_PHYSICAL in FADT table.\nAs all apicids are smaller than 255, BIOS need to pass the\ncontrol to the OS with xapic mode, according to x2apic-spec,\nchapter 2.9.\n\nCurrent code handle x2apic when BIOS pass with xapic mode\nenabled:\n\nWhen user specifies x2apic_phys, or FADT indicates PHYSICAL:\n\n1. During madt oem check, apic driver is set with xapic logical\n or xapic phys driver at first.\n\n2. enable_IR_x2apic() will enable x2apic_mode.\n\n3. if user specifies x2apic_phys on the boot line, x2apic_phys_probe()\n will install the correct x2apic phys driver and use x2apic phys mode.\n Otherwise it will skip the driver will let x2apic_cluster_probe to\n take over to install x2apic cluster driver (wrong one) even though FADT\n indicates PHYSICAL, because x2apic_phys_probe does not check\n FADT PHYSICAL.\n\nAdd checking x2apic_fadt_phys in x2apic_phys_probe() to fix the\nproblem.\n\nSigned-off-by: Stoney Wang \u003csong-bo.wang@hp.com\u003e\n[ updated the changelog and simplified the code ]\nSigned-off-by: Yinghai Lu \u003cyinghai@kernel.org\u003e\nLink: http://lkml.kernel.org/r/1360263182-16226-1-git-send-email-yinghai@kernel.org\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e2ef6aad8a81c730bba92b2a44d758cabd7d9053", "tree": "9934b62dec05632e026c4338fa038efd0cb6f04b", "parents": [ "18051b4221f2d593d8f98913cf7095dfec269706" ], "author": { "name": "Kees Cook", "email": "keescook@chromium.org", "time": "Thu Feb 07 09:44:13 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Feb 17 10:49:25 2013 -0800" }, "message": "x86: Do not leak kernel page mapping locations\n\ncommit e575a86fdc50d013bf3ad3aa81d9100e8e6cc60d upstream.\n\nWithout this patch, it is trivial to determine kernel page\nmappings by examining the error code reported to dmesg[1].\nInstead, declare the entire kernel memory space as a violation\nof a present page.\n\nAdditionally, since show_unhandled_signals is enabled by\ndefault, switch branch hinting to the more realistic\nexpectation, and unobfuscate the setting of the PF_PROT bit to\nimprove readability.\n\n[1] http://vulnfactory.org/blog/2013/02/06/a-linux-memory-trick/\n\nReported-by: Dan Rosenberg \u003cdan.j.rosenberg@gmail.com\u003e\nSuggested-by: Brad Spengler \u003cspender@grsecurity.net\u003e\nSigned-off-by: Kees Cook \u003ckeescook@chromium.org\u003e\nAcked-by: H. Peter Anvin \u003chpa@zytor.com\u003e\nCc: Paul E. McKenney \u003cpaulmck@linux.vnet.ibm.com\u003e\nCc: Frederic Weisbecker \u003cfweisbec@gmail.com\u003e\nCc: Eric W. Biederman \u003cebiederm@xmission.com\u003e\nCc: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nCc: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nCc: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nLink: http://lkml.kernel.org/r/20130207174413.GA12485@www.outflux.net\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "18051b4221f2d593d8f98913cf7095dfec269706", "tree": "fe479d3cdee492fed9d2180481b71b5ed579d3b7", "parents": [ "72a274602416d7c5dc04641832af8d0710a548dd" ], "author": { "name": "Heiko Carstens", "email": "heiko.carstens@de.ibm.com", "time": "Tue Jan 29 09:16:28 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Sun Feb 17 10:49:25 2013 -0800" }, "message": "s390/timer: avoid overflow when programming clock comparator\n\ncommit d911e03d097bdc01363df5d81c43f69432eb785c upstream.\n\nSince ed4f209 \"s390/time: fix sched_clock() overflow\" a new helper function\nis used to avoid overflows when converting TOD format values to nanosecond\nvalues.\nThe kvm interrupt code formerly however only worked by accident because of\nan overflow. It tried to program a timer that would expire in more than ~29\nyears. Because of the old TOD-to-nanoseconds overflow bug the real expiry\nvalue however was much smaller, but now it isn\u0027t anymore.\nThis however triggers yet another bug in the function that programs the clock\ncomparator s390_next_ktime(): if the absolute \"expires\" value is after 2042\nthis will result in an overflow and the programmed value is lower than the\ncurrent TOD value which immediatly triggers a clock comparator (\u003d timer)\ninterrupt.\nSince the timer isn\u0027t expired it will be programmed immediately again and so\non... the result is a dead system.\nTo fix this simply program the maximum possible value if an overflow is\ndetected.\n\nReported-by: Christian Borntraeger \u003cborntraeger@de.ibm.com\u003e\nTested-by: Christian Borntraeger \u003cborntraeger@de.ibm.com\u003e\nSigned-off-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "72a274602416d7c5dc04641832af8d0710a548dd", "tree": "da2f53e7860275a1374852f65db8ee12d3b1130f", "parents": [ "495f02922e05a6858005dc6b9e07eeed026cf9a0" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:52:45 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:52:45 2013 -0800" }, "message": "Linux 3.4.31\n" }, { "commit": "495f02922e05a6858005dc6b9e07eeed026cf9a0", "tree": "78de770fba9a01e465e52de231571ff5d9070601", "parents": [ "eac7b44eb80d3e1fa3310ad2dc57e10c2fc970fd" ], "author": { "name": "Somnath Kotur", "email": "somnath.kotur@emulex.com", "time": "Tue Jun 26 22:32:10 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:49:07 2013 -0800" }, "message": "be2net: Fix to trim skb for padded vlan packets to workaround an ASIC Bug\n\ncommit 93040ae5cc8dcc893eca4a4366dc8415af278edf upstream.\n\nFixed spelling error in a comment as pointed out by DaveM.\nAlso refactored existing code a bit to provide placeholders for another ASIC\nBug workaround that will be checked-in soon after this.\n\nSigned-off-by: Somnath Kotur \u003csomnath.kotur@emulex.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nCc: Jacek Luczak \u003cdifrost.kernel@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "eac7b44eb80d3e1fa3310ad2dc57e10c2fc970fd", "tree": "4c4387ca900bd1c0de1c63d465dbf77538fbe9d2", "parents": [ "a10a3daa591e6ea2619da1e0418af2a30aa77ac5" ], "author": { "name": "Nithin Nayak Sujir", "email": "nsujir@broadcom.com", "time": "Mon Jan 14 17:11:00 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:49:07 2013 -0800" }, "message": "tg3: Fix crc errors on jumbo frame receive\n\n[ Upstream commit daf3ec688e057f6060fb9bb0819feac7a8bbf45c ]\n\nTG3_PHY_AUXCTL_SMDSP_ENABLE/DISABLE macros do a blind write to the phy\nauxiliary control register and overwrite the EXT_PKT_LEN (bit 14) resulting\nin intermittent crc errors on jumbo frames with some link partners. Change\nthe code to do a read/modify/write.\n\nSigned-off-by: Nithin Nayak Sujir \u003cnsujir@broadcom.com\u003e\nSigned-off-by: Michael Chan \u003cmchan@broadcom.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "a10a3daa591e6ea2619da1e0418af2a30aa77ac5", "tree": "587a642eeacb3486398aa7e715d20be1ba66f60e", "parents": [ "94fab0a18e9cbec420c58c7b12b93acf1663c3fd" ], "author": { "name": "Nithin Nayak Sujir", "email": "nsujir@broadcom.com", "time": "Mon Jan 14 17:10:59 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:49:07 2013 -0800" }, "message": "tg3: Avoid null pointer dereference in tg3_interrupt in netconsole mode\n\n[ Upstream commit 9c13cb8bb477a83b9a3c9e5a5478a4e21294a760 ]\n\nWhen netconsole is enabled, logging messages generated during tg3_open\ncan result in a null pointer dereference for the uninitialized tg3\nstatus block. Use the irq_sync flag to disable polling in the early\nstages. irq_sync is cleared when the driver is enabling interrupts after\nall initialization is completed.\n\nSigned-off-by: Nithin Nayak Sujir \u003cnsujir@broadcom.com\u003e\nSigned-off-by: Michael Chan \u003cmchan@broadcom.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "94fab0a18e9cbec420c58c7b12b93acf1663c3fd", "tree": "3257222639a169f5a25876ad2bca46dbddce426b", "parents": [ "f641de91169472dc398fbd971cef380ad8d0f787" ], "author": { "name": "Sarveshwar Bandi", "email": "sarveshwar.bandi@emulex.com", "time": "Wed Oct 10 01:15:01 2012 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:49:07 2013 -0800" }, "message": "bridge: Pull ip header into skb-\u003edata before looking into ip header.\n\n[ Upstream commit 6caab7b0544e83e6c160b5e80f5a4a7dd69545c7 ]\n\nIf lower layer driver leaves the ip header in the skb fragment, it needs to\nbe first pulled into skb-\u003edata before inspecting ip header length or ip version\nnumber.\n\nSigned-off-by: Sarveshwar Bandi \u003csarveshwar.bandi@emulex.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "f641de91169472dc398fbd971cef380ad8d0f787", "tree": "5fd7cea4a429f37f04ed28ac53738ebfd4c77dcf", "parents": [ "2813296332187d222b96363fe29f10929f7a5228" ], "author": { "name": "Ilpo Järvinen", "email": "ilpo.jarvinen@helsinki.fi", "time": "Mon Feb 04 02:14:25 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:49:06 2013 -0800" }, "message": "tcp: fix for zero packets_in_flight was too broad\n\n[ Upstream commit 6731d2095bd4aef18027c72ef845ab1087c3ba63 ]\n\nThere are transients during normal FRTO procedure during which\nthe packets_in_flight can go to zero between write_queue state\nupdates and firing the resulting segments out. As FRTO processing\noccurs during that window the check must be more precise to\nnot match \"spuriously\" :-). More specificly, e.g., when\npackets_in_flight is zero but FLAG_DATA_ACKED is true the problematic\nbranch that set cwnd into zero would not be taken and new segments\nmight be sent out later.\n\nSigned-off-by: Ilpo Järvinen \u003cilpo.jarvinen@helsinki.fi\u003e\nTested-by: Eric Dumazet \u003cedumazet@google.com\u003e\nAcked-by: Neal Cardwell \u003cncardwell@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "2813296332187d222b96363fe29f10929f7a5228", "tree": "10dfdbd0714285dbb4385bfd38f67ae968b6a4aa", "parents": [ "42671f1e6fd8922b071bd3fd3e0cfad7226c654d" ], "author": { "name": "Eric Dumazet", "email": "edumazet@google.com", "time": "Sun Feb 03 09:13:05 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:49:06 2013 -0800" }, "message": "tcp: frto should not set snd_cwnd to 0\n\n[ Upstream commit 2e5f421211ff76c17130b4597bc06df4eeead24f ]\n\nCommit 9dc274151a548 (tcp: fix ABC in tcp_slow_start())\nuncovered a bug in FRTO code :\ntcp_process_frto() is setting snd_cwnd to 0 if the number\nof in flight packets is 0.\n\nAs Neal pointed out, if no packet is in flight we lost our\nchance to disambiguate whether a loss timeout was spurious.\n\nWe should assume it was a proper loss.\n\nReported-by: Pasi Kärkkäinen \u003cpasik@iki.fi\u003e\nSigned-off-by: Neal Cardwell \u003cncardwell@google.com\u003e\nSigned-off-by: Eric Dumazet \u003cedumazet@google.com\u003e\nCc: Ilpo Järvinen \u003cilpo.jarvinen@helsinki.fi\u003e\nCc: Yuchung Cheng \u003cycheng@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "42671f1e6fd8922b071bd3fd3e0cfad7226c654d", "tree": "ffee516e70edfee8999af8c52e3b81c3517f7f45", "parents": [ "90ffc8f3315b0d296fea07fbc6fef87155f81f45" ], "author": { "name": "Ian Campbell", "email": "Ian.Campbell@citrix.com", "time": "Wed Feb 06 23:41:38 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:49:06 2013 -0800" }, "message": "netback: correct netbk_tx_err to handle wrap around.\n\n[ Upstream commit b9149729ebdcfce63f853aa54a404c6a8f6ebbf3 ]\n\nSigned-off-by: Ian Campbell \u003cian.campbell@citrix.com\u003e\nAcked-by: Jan Beulich \u003cJBeulich@suse.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "90ffc8f3315b0d296fea07fbc6fef87155f81f45", "tree": "1855501c29a41ee45670a7d3d7646d5da062414e", "parents": [ "33eb2607ebfcb68bc9ae8ab029f916f1f4ee5097" ], "author": { "name": "Ian Campbell", "email": "Ian.Campbell@citrix.com", "time": "Wed Feb 06 23:41:37 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:49:06 2013 -0800" }, "message": "xen/netback: free already allocated memory on failure in xen_netbk_get_requests\n\n[ Upstream commit 4cc7c1cb7b11b6f3515bd9075527576a1eecc4aa ]\n\nSigned-off-by: Ian Campbell \u003cian.campbell@citrix.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "33eb2607ebfcb68bc9ae8ab029f916f1f4ee5097", "tree": "9124b0dd2a87598210579e52a6bd50006bc605a5", "parents": [ "be7254fc6c92c016a6768cc30596198c61043ff5" ], "author": { "name": "Matthew Daley", "email": "mattjd@gmail.com", "time": "Wed Feb 06 23:41:36 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:49:06 2013 -0800" }, "message": "xen/netback: don\u0027t leak pages on failure in xen_netbk_tx_check_gop.\n\n[ Upstream commit 7d5145d8eb2b9791533ffe4dc003b129b9696c48 ]\n\nSigned-off-by: Matthew Daley \u003cmattjd@gmail.com\u003e\nReviewed-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nAcked-by: Ian Campbell \u003cian.campbell@citrix.com\u003e\nAcked-by: Jan Beulich \u003cJBeulich@suse.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "be7254fc6c92c016a6768cc30596198c61043ff5", "tree": "3c921b173035797e0966f9f912bbad76fa1c2c71", "parents": [ "d6f5498856f31246818bbe4ebfa710ce92730a37" ], "author": { "name": "Ian Campbell", "email": "Ian.Campbell@citrix.com", "time": "Wed Feb 06 23:41:35 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Feb 14 10:49:06 2013 -0800" }, "message": "xen/netback: shutdown the ring if it contains garbage.\n\n[ Upstream commit 48856286b64e4b66ec62b94e504d0b29c1ade664 ]\n\nA buggy or malicious frontend should not be able to confuse netback.\nIf we spot anything which is not as it should be then shutdown the\ndevice and don\u0027t try to continue with the ring in a potentially\nhostile state. Well behaved and non-hostile frontends will not be\npenalised.\n\nAs well as making the existing checks for such errors fatal also add a\nnew check that ensures that there isn\u0027t an insane number of requests\non the ring (i.e. more than would fit in the ring). If the ring\ncontains garbage then previously is was possible to loop over this\ninsane number, getting an error each time and therefore not generating\nany more pending requests and therefore not exiting the loop in\nxen_netbk_tx_build_gops for an externded period.\n\nAlso turn various netdev_dbg calls which no precipitate a fatal error\ninto netdev_err, they are rate limited because the device is shutdown\nafterwards.\n\nThis fixes at least one known DoS/softlockup of the backend domain.\n\nSigned-off-by: Ian Campbell \u003cian.campbell@citrix.com\u003e\nReviewed-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nAcked-by: Jan Beulich \u003cJBeulich@suse.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" } ], "next": "d6f5498856f31246818bbe4ebfa710ce92730a37" }