)]}' { "log": [ { "commit": "4d64cdba19f7c0d4c7fa15671b2817cfc5ebc643", "tree": "710d63c4996e9df3fd95f95544ce90b3707e697b", "parents": [ "9a17de12d2b4c4c9cb5b1414fade61f8e9561625" ], "author": { "name": "Ben Hutchings", "email": "bhutchings@solarflare.com", "time": "Tue Sep 11 21:46:41 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:54 2013 -0700" }, "message": "sfc: Fix MCDI structure field lookup\n\n[ Upstream commit 0a6e5008a9df678b48f8d4e57601aa4270df6c14 ]\n\nThe least significant bit number (LBN) of a field within an MCDI\nstructure is counted from the start of the structure, not the\ncontaining dword. In MCDI_ARRAY_FIELD() we need to mask it rather\nthan using the usual EFX_DWORD_FIELD() macro.\n\nSigned-off-by: Ben Hutchings \u003cbhutchings@solarflare.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "9a17de12d2b4c4c9cb5b1414fade61f8e9561625", "tree": "259fde9d1d8d1bf2f98c6c24227e69dfae32ef5b", "parents": [ "0f1ac29892c257ef9d13e317163d6761fe24a389" ], "author": { "name": "Ben Hutchings", "email": "bhutchings@solarflare.com", "time": "Tue Sep 11 21:37:36 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:54 2013 -0700" }, "message": "sfc: Add parentheses around use of bitfield macro arguments\n\n[ Upstream commit 9724a8504c875145f5a513bb8eca50671cee23b4 ]\n\nSigned-off-by: Ben Hutchings \u003cbhutchings@solarflare.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "0f1ac29892c257ef9d13e317163d6761fe24a389", "tree": "a9497df451254ea34b95a48af2d8d31b2f98340a", "parents": [ "be29fc5aa4a60b212066a28c0137236711486ec1" ], "author": { "name": "Ben Hutchings", "email": "bhutchings@solarflare.com", "time": "Fri Sep 07 00:58:10 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:54 2013 -0700" }, "message": "sfc: Convert firmware subtypes to native byte order in efx_mcdi_get_board_cfg()\n\n[ Upstream commit bfeed902946a31692e7a24ed355b6d13ac37d014 ]\n\nOn big-endian systems the MTD partition names currently have mangled\nsubtype numbers and are not recognised by the firmware update tool\n(sfupdate).\n\nSigned-off-by: Ben Hutchings \u003cbhutchings@solarflare.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "be29fc5aa4a60b212066a28c0137236711486ec1", "tree": "8d7c27afbd9a38cb427ec8c51c2bb21dbec1f1b5", "parents": [ "1280938465132080915aef414a1f40f62831bab9" ], "author": { "name": "Stuart Hodgson", "email": "smhodgson@solarflare.com", "time": "Fri Mar 30 13:04:51 2012 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:54 2013 -0700" }, "message": "sfc: Do not attempt to flush queues if DMA is disabled\n\n[ Upstream commit 3dca9d2dc285faf1910d405b65df845cab061356 ]\n\nefx_nic_fatal_interrupt() disables DMA before scheduling a reset.\nAfter this, we need not and *cannot* flush queues.\n\nSigned-off-by: Ben Hutchings \u003cbhutchings@solarflare.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "1280938465132080915aef414a1f40f62831bab9", "tree": "a2055fce3874fea9ddec94d17658e7d3ec18dc66", "parents": [ "05bec9da3978124bde3b40bfa0404760f45aa399" ], "author": { "name": "Hannes Frederic Sowa", "email": "hannes@stressinduktion.org", "time": "Fri Mar 15 11:32:30 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:54 2013 -0700" }, "message": "inet: limit length of fragment queue hash table bucket lists\n\n[ Upstream commit 5a3da1fe9561828d0ca7eca664b16ec2b9bf0055 ]\n\nThis patch introduces a constant limit of the fragment queue hash\ntable bucket list lengths. Currently the limit 128 is choosen somewhat\narbitrary and just ensures that we can fill up the fragment cache with\nempty packets up to the default ip_frag_high_thresh limits. It should\njust protect from list iteration eating considerable amounts of cpu.\n\nIf we reach the maximum length in one hash bucket a warning is printed.\nThis is implemented on the caller side of inet_frag_find to distinguish\nbetween the different users of inet_fragment.c.\n\nI dropped the out of memory warning in the ipv4 fragment lookup path,\nbecause we already get a warning by the slab allocator.\n\nCc: Eric Dumazet \u003ceric.dumazet@gmail.com\u003e\nCc: Jesper Dangaard Brouer \u003cjbrouer@redhat.com\u003e\nSigned-off-by: Hannes Frederic Sowa \u003channes@stressinduktion.org\u003e\nAcked-by: Eric Dumazet \u003cedumazet@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "05bec9da3978124bde3b40bfa0404760f45aa399", "tree": "0fd1cf90efad6fd3ca2f00862eaae47a1bfce229", "parents": [ "c2abe8ada7b63b6ede9c80e615fdbc97dde2e2e2" ], "author": { "name": "Maciej Żenczykowski", "email": "maze@google.com", "time": "Fri Mar 15 11:56:17 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:54 2013 -0700" }, "message": "bnx2x: fix occasional statistics off-by-4GB error\n\n[ Upstream commit b009aac12cd0fe34293c68af8ac48b85be3bd858 ]\n\nThe UPDATE_QSTAT function introduced on February 15, 2012\nin commit 1355b704b9ba \"bnx2x: consistent statistics after\ninternal driver reload\" incorrectly fails to handle overflow\nduring addition of the lower 32-bit field of a stat.\n\nThis bug is present since 3.4-rc1 and should thus be considered\na candidate for stable 3.4+ releases.\n\nGoogle-Bug-Id: 8374428\nSigned-off-by: Maciej Żenczykowski \u003cmaze@google.com\u003e\nCc: Mintz Yuval \u003cyuvalmin@broadcom.com\u003e\nAcked-by: Eilon Greenstein \u003ceilong@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": "c2abe8ada7b63b6ede9c80e615fdbc97dde2e2e2", "tree": "9002f32dd5e99c50d8176ea88d0bfe271eba1162", "parents": [ "08ebc8f4c0acb1e9a104e66fdc2bb5b4e29171f5" ], "author": { "name": "Michael S. Tsirkin", "email": "mst@redhat.com", "time": "Sun Mar 17 02:46:09 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:54 2013 -0700" }, "message": "vhost/net: fix heads usage of ubuf_info\n\n[ Upstream commit 46aa92d1ba162b4b3d6b7102440e459d4e4ee255 ]\n\nubuf info allocator uses guest controlled head as an index,\nso a malicious guest could put the same head entry in the ring twice,\nand we will get two callbacks on the same value.\nTo fix use upend_idx which is guaranteed to be unique.\n\nReported-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\nSigned-off-by: Michael S. Tsirkin \u003cmst@redhat.com\u003e\nCc: stable@kernel.org\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "08ebc8f4c0acb1e9a104e66fdc2bb5b4e29171f5", "tree": "faa7ef1cf3416911fee70d3f7c8a328fd166ad41", "parents": [ "b6da578e2a610a64e89f2a983f7675eb301c5d35" ], "author": { "name": "Vlad Yasevich", "email": "vyasevic@redhat.com", "time": "Wed Mar 13 04:18:58 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:53 2013 -0700" }, "message": "rtnetlink: Mask the rta_type when range checking\n\n[ Upstream commit a5b8db91442fce9c9713fcd656c3698f1adde1d6 ]\n\nRange/validity checks on rta_type in rtnetlink_rcv_msg() do\nnot account for flags that may be set. This causes the function\nto return -EINVAL when flags are set on the type (for example\nNLA_F_NESTED).\n\nSigned-off-by: Vlad Yasevich \u003cvyasevic@redhat.com\u003e\nAcked-by: Thomas Graf \u003ctgraf@suug.ch\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "b6da578e2a610a64e89f2a983f7675eb301c5d35", "tree": "e9a01ac902578dcb3c0cca6b9126e294d02942a7", "parents": [ "6a2d122cdd939e33279baf351c7cbf12c50eaeb5" ], "author": { "name": "Eric Dumazet", "email": "edumazet@google.com", "time": "Thu Mar 14 05:40:32 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:53 2013 -0700" }, "message": "tcp: fix skb_availroom()\n\n[ Upstream commit 16fad69cfe4adbbfa813de516757b87bcae36d93 ]\n\nChrome OS team reported a crash on a Pixel ChromeBook in TCP stack :\n\nhttps://code.google.com/p/chromium/issues/detail?id\u003d182056\n\ncommit a21d45726acac (tcp: avoid order-1 allocations on wifi and tx\npath) did a poor choice adding an \u0027avail_size\u0027 field to skb, while\nwhat we really needed was a \u0027reserved_tailroom\u0027 one.\n\nIt would have avoided commit 22b4a4f22da (tcp: fix retransmit of\npartially acked frames) and this commit.\n\nCrash occurs because skb_split() is not aware of the \u0027avail_size\u0027\nmanagement (and should not be aware)\n\nSigned-off-by: Eric Dumazet \u003cedumazet@google.com\u003e\nReported-by: Mukesh Agrawal \u003cquiche@chromium.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "6a2d122cdd939e33279baf351c7cbf12c50eaeb5", "tree": "d33d3ae99144bd170bd0453016fa85b2eae75ad6", "parents": [ "ca42fad953eab535f12b04cea9622b253faebb0b" ], "author": { "name": "Denis V. Lunev", "email": "den@openvz.org", "time": "Wed Mar 13 00:24:15 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:53 2013 -0700" }, "message": "ipv4: fix definition of FIB_TABLE_HASHSZ\n\n[ Upstream commit 5b9e12dbf92b441b37136ea71dac59f05f2673a9 ]\n\na long time ago by the commit\n\n commit 93456b6d7753def8760b423ac6b986eb9d5a4a95\n Author: Denis V. Lunev \u003cden@openvz.org\u003e\n Date: Thu Jan 10 03:23:38 2008 -0800\n\n [IPV4]: Unify access to the routing tables.\n\nthe defenition of FIB_HASH_TABLE size has obtained wrong dependency:\nit should depend upon CONFIG_IP_MULTIPLE_TABLES (as was in the original\ncode) but it was depended from CONFIG_IP_ROUTE_MULTIPATH\n\nThis patch returns the situation to the original state.\n\nThe problem was spotted by Tingwei Liu.\n\nSigned-off-by: Denis V. Lunev \u003cden@openvz.org\u003e\nCC: Tingwei Liu \u003ctingw.liu@gmail.com\u003e\nCC: Alexey Kuznetsov \u003ckuznet@ms2.inr.ac.ru\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "ca42fad953eab535f12b04cea9622b253faebb0b", "tree": "99575f5db9dd65133d270207f58aaa55859f6e5f", "parents": [ "0aa8bf90399754022f547b69e1812abe8bba4c0b" ], "author": { "name": "Xufeng Zhang", "email": "xufeng.zhang@windriver.com", "time": "Thu Mar 07 21:39:37 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:53 2013 -0700" }, "message": "sctp: don\u0027t break the loop while meeting the active_path so as to find the matched transport\n\n[ Upstream commit 2317f449af30073cfa6ec8352e4a65a89e357bdd ]\n\nsctp_assoc_lookup_tsn() function searchs which transport a certain TSN\nwas sent on, if not found in the active_path transport, then go search\nall the other transports in the peer\u0027s transport_addr_list, however, we\nshould continue to the next entry rather than break the loop when meet\nthe active_path transport.\n\nSigned-off-by: Xufeng Zhang \u003cxufeng.zhang@windriver.com\u003e\nAcked-by: Neil Horman \u003cnhorman@tuxdriver.com\u003e\nAcked-by: Vlad Yasevich \u003cvyasevich@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "0aa8bf90399754022f547b69e1812abe8bba4c0b", "tree": "1a8adaa01451430320715b5b6a1cfc9a5596f511", "parents": [ "147289d28fb7b7c10a9f8a2cd9e274a41fc3f1f6" ], "author": { "name": "Vlad Yasevich", "email": "vyasevich@gmail.com", "time": "Tue Mar 12 15:53:23 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:53 2013 -0700" }, "message": "sctp: Use correct sideffect command in duplicate cookie handling\n\n[ Upstream commit f2815633504b442ca0b0605c16bf3d88a3a0fcea ]\n\nWhen SCTP is done processing a duplicate cookie chunk, it tries\nto delete a newly created association. For that, it has to set\nthe right association for the side-effect processing to work.\nHowever, when it uses the SCTP_CMD_NEW_ASOC command, that performs\nmore work then really needed (like hashing the associationa and\nassigning it an id) and there is no point to do that only to\ndelete the association as a next step. In fact, it also creates\nan impossible condition where an association may be found by\nthe getsockopt() call, and that association is empty. This\ncauses a crash in some sctp getsockopts.\n\nThe solution is rather simple. We simply use SCTP_CMD_SET_ASOC\ncommand that doesn\u0027t have all the overhead and does exactly\nwhat we need.\n\nReported-by: Karl Heiss \u003ckheiss@gmail.com\u003e\nTested-by: Karl Heiss \u003ckheiss@gmail.com\u003e\nCC: Neil Horman \u003cnhorman@tuxdriver.com\u003e\nSigned-off-by: Vlad Yasevich \u003cvyasevich@gmail.com\u003e\nAcked-by: Neil Horman \u003cnhorman@tuxdriver.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "147289d28fb7b7c10a9f8a2cd9e274a41fc3f1f6", "tree": "599c043054fafc533c5ac2e3d4609c56292da52e", "parents": [ "e7778a61fff957a36c0e53fc565df17d68dcbee6" ], "author": { "name": "Nithin Sujir", "email": "nsujir@broadcom.com", "time": "Tue Mar 12 15:32:48 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:53 2013 -0700" }, "message": "tg3: 5715 does not link up when autoneg off\n\n[ Upstream commit 7c6cdead7cc9a99650d15497aae47d7472217eb1 ]\n\nCommit d13ba512cbba7de5d55d7a3b2aae7d83c8921457 (\"tg3: Remove\nSPEED_UNKNOWN checks\") cleaned up the autoneg advertisement by\nremoving some dead code. One effect of this change was that the\nadvertisement register would not be updated if autoneg is turned off.\n\nThis exposed a bug on the 5715 device w.r.t linking. The 5715 defaults\nto advertise only 10Mb Full duplex. But with autoneg disabled, it needs\nthe configured speed enabled in the advertisement register to link up.\n\nThis patch adds the work around to advertise all speeds on the 5715 when\nautoneg is disabled.\n\nReported-by: Marcin Miotk \u003cmarcinmiotk81@gmail.com\u003e\nReviewed-by: Benjamin Li \u003cbenli@broadcom.com\u003e\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": "e7778a61fff957a36c0e53fc565df17d68dcbee6", "tree": "c9a766abdae5ac9803ddc6fe37b5050d600c17d5", "parents": [ "b52f06719c794cc8df5ea871a4fd498ff252210a" ], "author": { "name": "Veaceslav Falico", "email": "vfalico@redhat.com", "time": "Tue Mar 12 06:31:32 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:52 2013 -0700" }, "message": "bonding: don\u0027t call update_speed_duplex() under spinlocks\n\n[ Upstream commit 876254ae2758d50dcb08c7bd00caf6a806571178 ]\n\nbond_update_speed_duplex() might sleep while calling underlying slave\u0027s\nroutines. Move it out of atomic context in bond_enslave() and remove it\nfrom bond_miimon_commit() - it was introduced by commit 546add79, however\nwhen the slave interfaces go up/change state it\u0027s their responsibility to\nfire NETDEV_UP/NETDEV_CHANGE events so that bonding can properly update\ntheir speed.\n\nI\u0027ve tested it on all combinations of ifup/ifdown, autoneg/speed/duplex\nchanges, remote-controlled and local, on (not) MII-based cards. All changes\nare visible.\n\nSigned-off-by: Veaceslav Falico \u003cvfalico@redhat.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "b52f06719c794cc8df5ea871a4fd498ff252210a", "tree": "b11aa21e96450bafdd90bfa0fcddb28de5911e87", "parents": [ "7436bcf6158d70346928b9b26568f5bb3213a36f" ], "author": { "name": "Veaceslav Falico", "email": "vfalico@redhat.com", "time": "Mon Mar 11 00:21:48 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:52 2013 -0700" }, "message": "netconsole: don\u0027t call __netpoll_cleanup() while atomic\n\n[ Upstream commit 3f315bef23075ea8a98a6fe4221a83b83456d970 ]\n\n__netpoll_cleanup() is called in netconsole_netdev_event() while holding a\nspinlock. Release/acquire the spinlock before/after it and restart the\nloop. Also, disable the netconsole completely, because we won\u0027t have chance\nafter the restart of the loop, and might end up in a situation where\nnt-\u003eenabled \u003d\u003d 1 and nt-\u003enp.dev \u003d\u003d NULL.\n\nSigned-off-by: Veaceslav Falico \u003cvfalico@redhat.com\u003e\nAcked-by: Neil Horman \u003cnhorman@tuxdriver.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "7436bcf6158d70346928b9b26568f5bb3213a36f", "tree": "a092676a959c4df2bcdd230d0421e3a03f28ffec", "parents": [ "1c93c2e727a02efe7e143c6d6798facbab31d9e1" ], "author": { "name": "David Ward", "email": "david.ward@ll.mit.edu", "time": "Mon Mar 11 10:43:39 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:52 2013 -0700" }, "message": "net/ipv4: Ensure that location of timestamp option is stored\n\n[ Upstream commit 4660c7f498c07c43173142ea95145e9dac5a6d14 ]\n\nThis is needed in order to detect if the timestamp option appears\nmore than once in a packet, to remove the option if the packet is\nfragmented, etc. My previous change neglected to store the option\nlocation when the router addresses were prespecified and Pointer \u003e\nLength. But now the option location is also stored when Flag is an\nunrecognized value, to ensure these option handling behaviors are\nstill performed.\n\nSigned-off-by: David Ward \u003cdavid.ward@ll.mit.edu\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "1c93c2e727a02efe7e143c6d6798facbab31d9e1", "tree": "591d9810e3e174a88446eb11ce43e3815f672830", "parents": [ "3ff89240cd6922f9da638e2cc3012b5f8f01f943" ], "author": { "name": "Tkhai Kirill", "email": "tkhai@yandex.ru", "time": "Sat Feb 23 23:01:15 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:52 2013 -0700" }, "message": "sunsu: Fix panic in case of nonexistent port at \"console\u003dttySY\" cmdline option\n\n[ Upstream commit cb29529ea0030e60ef1bbbf8399a43d397a51526 ]\n\nIf a machine has X (X \u003c 4) sunsu ports and cmdline\noption \"console\u003dttySY\" is passed, where X \u003c Y \u003c\u003d 4,\nthan the following panic happens:\n\nUnable to handle kernel NULL pointer dereference\nTPC: \u003csunsu_console_setup+0x78/0xe0\u003e\nRPC: \u003csunsu_console_setup+0x74/0xe0\u003e\nI7: \u003cregister_console+0x378/0x3e0\u003e\nCall Trace:\n [0000000000453a38] register_console+0x378/0x3e0\n [0000000000576fa0] uart_add_one_port+0x2e0/0x340\n [000000000057af40] su_probe+0x160/0x2e0\n [00000000005b8a4c] platform_drv_probe+0xc/0x20\n [00000000005b6c2c] driver_probe_device+0x12c/0x220\n [00000000005b6da8] __driver_attach+0x88/0xa0\n [00000000005b4df4] bus_for_each_dev+0x54/0xa0\n [00000000005b5a54] bus_add_driver+0x154/0x260\n [00000000005b7190] driver_register+0x50/0x180\n [00000000006d250c] sunsu_init+0x18c/0x1e0\n [00000000006c2668] do_one_initcall+0xe8/0x160\n [00000000006c282c] kernel_init_freeable+0x12c/0x1e0\n [0000000000603764] kernel_init+0x4/0x100\n [0000000000405f64] ret_from_syscall+0x1c/0x2c\n [0000000000000000] (null)\n\n1)Fix the panic;\n2)Increment registered port number every successful\nprobe.\n\nSigned-off-by: Kirill Tkhai \u003ctkhai@yandex.ru\u003e\nCC: David Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "3ff89240cd6922f9da638e2cc3012b5f8f01f943", "tree": "2476e7d3138b5f7b96c313400249df2187833c65", "parents": [ "dbfe0858b24ca63522a8aac435fbca03d358a900" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 14:16:12 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 28 12:11:52 2013 -0700" }, "message": "Revert \"USB: EHCI: don\u0027t check DMA values in QH overlays\"\n\nThis reverts commit 0319f9909ce68a7516dfc8d53400e07168d281a8, which is commit\nfeca7746d5d9e84b105a613b7f3b6ad00d327372 upstream.\n\nIt shouldn\u0027t have gone into this stable release.\n\nCc: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nCc: Joseph Salisbury \u003cjoseph.salisbury@canonical.com\u003e\nCc: Stephen Thirlwall \u003csdt@dr.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dbfe0858b24ca63522a8aac435fbca03d358a900", "tree": "7f2e8e601ee8752eff5a8f2d9a130cd33adcc945", "parents": [ "7cba6aeae533a95c6f49752c859adadf8439f42b" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:12 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:12 2013 -0700" }, "message": "Linux 3.4.37\n" }, { "commit": "7cba6aeae533a95c6f49752c859adadf8439f42b", "tree": "6e8525229ed45d19aa62a9f323fa724f367ef80d", "parents": [ "32ceecc2587ac7e079f17dbc9d5158928667baad" ], "author": { "name": "YOSHIFUJI Hideaki", "email": "yoshfuji@linux-ipv6.org", "time": "Sat Mar 09 09:11:57 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:02 2013 -0700" }, "message": "6lowpan: Fix endianness issue in is_addr_link_local().\n\n[ Upstream commit 9026c4927254f5bea695cc3ef2e255280e6a3011 ]\n\nSigned-off-by: YOSHIFUJI Hideaki \u003cyoshfuji@linux-ipv6.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "32ceecc2587ac7e079f17dbc9d5158928667baad", "tree": "b2c94f11009103aa536863f880cad60ca8aa653c", "parents": [ "78d3a467490d72c699393947f1e566fa28672947" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Sat Mar 09 05:52:21 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:02 2013 -0700" }, "message": "dcbnl: fix various netlink info leaks\n\n[ Upstream commit 29cd8ae0e1a39e239a3a7b67da1986add1199fc0 ]\n\nThe dcb netlink interface leaks stack memory in various places:\n* perm_addr[] buffer is only filled at max with 12 of the 32 bytes but\n copied completely,\n* no in-kernel driver fills all fields of an IEEE 802.1Qaz subcommand,\n so we\u0027re leaking up to 58 bytes for ieee_ets structs, up to 136 bytes\n for ieee_pfc structs, etc.,\n* the same is true for CEE -- no in-kernel driver fills the whole\n struct,\n\nPrevent all of the above stack info leaks by properly initializing the\nbuffers/structures involved.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "78d3a467490d72c699393947f1e566fa28672947", "tree": "cee705e2e0e50ff854f4e6932d969379776999e2", "parents": [ "47d7ed18c33cc4e9cba603c7ca776c40037ae842" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Sat Mar 09 05:52:20 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:02 2013 -0700" }, "message": "rtnl: fix info leak on RTM_GETLINK request for VF devices\n\n[ Upstream commit 84d73cd3fb142bf1298a8c13fd4ca50fd2432372 ]\n\nInitialize the mac address buffer with 0 as the driver specific function\nwill probably not fill the whole buffer. In fact, all in-kernel drivers\nfill only ETH_ALEN of the MAX_ADDR_LEN bytes, i.e. 6 of the 32 possible\nbytes. Therefore we currently leak 26 bytes of stack memory to userland\nvia the netlink interface.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "47d7ed18c33cc4e9cba603c7ca776c40037ae842", "tree": "9e4ffec7197c072c6d371e28f9b5138de627fd01", "parents": [ "c7a226b6464bfdc67433adcfe9e17b816157af98" ], "author": { "name": "Hannes Frederic Sowa", "email": "hannes@stressinduktion.org", "time": "Fri Mar 08 02:07:23 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:02 2013 -0700" }, "message": "ipv6: stop multicast forwarding to process interface scoped addresses\n\n[ Upstream commit ddf64354af4a702ee0b85d0a285ba74c7278a460 ]\n\nv2:\na) used struct ipv6_addr_props\n\nv3:\na) reverted changes for ipv6_addr_props\n\nv4:\na) do not use __ipv6_addr_needs_scope_id\n\nCc: YOSHIFUJI Hideaki \u003cyoshfuji@linux-ipv6.org\u003e\nSigned-off-by: Hannes Frederic Sowa \u003channes@stressinduktion.org\u003e\nAcked-by: YOSHIFUJI Hideaki \u003cyoshfuji@linux-ipv6.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "c7a226b6464bfdc67433adcfe9e17b816157af98", "tree": "40d3476093756d2d9883f6aac2cc5a93b7eab742", "parents": [ "8c6292ad910d6070a38fda048df788e02b8abe84" ], "author": { "name": "Cristian Bercaru", "email": "B43982@freescale.com", "time": "Fri Mar 08 07:03:38 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:02 2013 -0700" }, "message": "bridging: fix rx_handlers return code\n\n[ Upstream commit 3bc1b1add7a8484cc4a261c3e128dbe1528ce01f ]\n\nThe frames for which rx_handlers return RX_HANDLER_CONSUMED are no longer\ncounted as dropped. They are counted as successfully received by\n\u0027netif_receive_skb\u0027.\n\nThis allows network interface drivers to correctly update their RX-OK and\nRX-DRP counters based on the result of \u0027netif_receive_skb\u0027.\n\nSigned-off-by: Cristian Bercaru \u003cB43982@freescale.com\u003e\nSigned-off-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": "8c6292ad910d6070a38fda048df788e02b8abe84", "tree": "2df9752c4dc0014a3fd791af6f84d3e4f995c7d4", "parents": [ "e86429f5b4367734a4df8ffa46212d64934c310c" ], "author": { "name": "Paul Moore", "email": "pmoore@redhat.com", "time": "Wed Mar 06 11:45:24 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "netlabel: correctly list all the static label mappings\n\n[ Upstream commits 0c1233aba1e948c37f6dc7620cb7c253fcd71ce9 and\n a6a8fe950e1b8596bb06f2c89c3a1a4bf2011ba9 ]\n\nWhen we have a large number of static label mappings that spill across\nthe netlink message boundary we fail to properly save our state in the\nnetlink_callback struct which causes us to repeat the same listings.\nThis patch fixes this problem by saving the state correctly between\ncalls to the NetLabel static label netlink \"dumpit\" routines.\n\nSigned-off-by: Paul Moore \u003cpmoore@redhat.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "e86429f5b4367734a4df8ffa46212d64934c310c", "tree": "33673c48300fb22b64b13f7ac21d6b829b1df85a", "parents": [ "094b503a07c1b2f2c61505c548c4d55c0c297d02" ], "author": { "name": "Vlad Yasevich", "email": "vyasevic@redhat.com", "time": "Thu Mar 07 10:21:48 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "macvlan: Set IFF_UNICAST_FLT flag to prevent unnecessary promisc mode.\n\n[ Upstream commit 87ab7f6f2874f1115817e394a7ed2dea1c72549e ]\n\nMacvlan already supports hw address filters. Set the IFF_UNICAST_FLT\nso that it doesn\u0027t needlesly enter PROMISC mode when macvlans are\nstacked.\n\nSigned-of-by: Vlad Yasevich \u003cvyasevic@redhat.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "094b503a07c1b2f2c61505c548c4d55c0c297d02", "tree": "9a3581ddfc1a85105ce6198fc6871bbf9c3d1a90", "parents": [ "8bd2b8faec4d80e2c77645dcfd838d5f79e9e15b" ], "author": { "name": "Eric Dumazet", "email": "edumazet@google.com", "time": "Wed Mar 06 11:02:37 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "tun: add a missing nf_reset() in tun_net_xmit()\n\n[ Upstream commit f8af75f3517a24838a36eb5797a1a3e60bf9e276 ]\n\nDave reported following crash :\n\ngeneral protection fault: 0000 [#1] SMP\nCPU 2\nPid: 25407, comm: qemu-kvm Not tainted 3.7.9-205.fc18.x86_64 #1 Hewlett-Packard HP Z400 Workstation/0B4Ch\nRIP: 0010:[\u003cffffffffa0399bd5\u003e] [\u003cffffffffa0399bd5\u003e] destroy_conntrack+0x35/0x120 [nf_conntrack]\nRSP: 0018:ffff880276913d78 EFLAGS: 00010206\nRAX: 50626b6b7876376c RBX: ffff88026e530d68 RCX: ffff88028d158e00\nRDX: ffff88026d0d5470 RSI: 0000000000000011 RDI: 0000000000000002\nRBP: ffff880276913d88 R08: 0000000000000000 R09: ffff880295002900\nR10: 0000000000000000 R11: 0000000000000003 R12: ffffffff81ca3b40\nR13: ffffffff8151a8e0 R14: ffff880270875000 R15: 0000000000000002\nFS: 00007ff3bce38a00(0000) GS:ffff88029fc40000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b\nCR2: 00007fd1430bd000 CR3: 000000027042b000 CR4: 00000000000027e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\nProcess qemu-kvm (pid: 25407, threadinfo ffff880276912000, task ffff88028c369720)\nStack:\n ffff880156f59100 ffff880156f59100 ffff880276913d98 ffffffff815534f7\n ffff880276913db8 ffffffff8151a74b ffff880270875000 ffff880156f59100\n ffff880276913dd8 ffffffff8151a5a6 ffff880276913dd8 ffff88026d0d5470\nCall Trace:\n [\u003cffffffff815534f7\u003e] nf_conntrack_destroy+0x17/0x20\n [\u003cffffffff8151a74b\u003e] skb_release_head_state+0x7b/0x100\n [\u003cffffffff8151a5a6\u003e] __kfree_skb+0x16/0xa0\n [\u003cffffffff8151a666\u003e] kfree_skb+0x36/0xa0\n [\u003cffffffff8151a8e0\u003e] skb_queue_purge+0x20/0x40\n [\u003cffffffffa02205f7\u003e] __tun_detach+0x117/0x140 [tun]\n [\u003cffffffffa022184c\u003e] tun_chr_close+0x3c/0xd0 [tun]\n [\u003cffffffff8119669c\u003e] __fput+0xec/0x240\n [\u003cffffffff811967fe\u003e] ____fput+0xe/0x10\n [\u003cffffffff8107eb27\u003e] task_work_run+0xa7/0xe0\n [\u003cffffffff810149e1\u003e] do_notify_resume+0x71/0xb0\n [\u003cffffffff81640152\u003e] int_signal+0x12/0x17\nCode: 00 00 04 48 89 e5 41 54 53 48 89 fb 4c 8b a7 e8 00 00 00 0f 85 de 00 00 00 0f b6 73 3e 0f b7 7b 2a e8 10 40 00 00 48 85 c0 74 0e \u003c48\u003e 8b 40 28 48 85 c0 74 05 48 89 df ff d0 48 c7 c7 08 6a 3a a0\nRIP [\u003cffffffffa0399bd5\u003e] destroy_conntrack+0x35/0x120 [nf_conntrack]\n RSP \u003cffff880276913d78\u003e\n\nThis is because tun_net_xmit() needs to call nf_reset()\nbefore queuing skb into receive_queue\n\nReported-by: Dave Jones \u003cdavej@redhat.com\u003e\nSigned-off-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": "8bd2b8faec4d80e2c77645dcfd838d5f79e9e15b", "tree": "9b64b622e7d4f1616e69ee4e6e048ae49d35e406", "parents": [ "6202fe4eec7b98b7391865c8aebe513bc1f14009" ], "author": { "name": "Neal Cardwell", "email": "ncardwell@google.com", "time": "Mon Mar 04 06:23:05 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "tcp: fix double-counted receiver RTT when leaving receiver fast path\n\n[ Upstream commit aab2b4bf224ef8358d262f95b568b8ad0cecf0a0 ]\n\nWe should not update ts_recent and call tcp_rcv_rtt_measure_ts() both\nbefore and after going to step5. That wastes CPU and double-counts the\nreceiver-side RTT sample.\n\nSigned-off-by: Neal Cardwell \u003cncardwell@google.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": "6202fe4eec7b98b7391865c8aebe513bc1f14009", "tree": "d22e072024d814324cde88bc96d03e2274bf33b1", "parents": [ "2b2066c41aba3032831ff5402bbd3b68ff5b9d47" ], "author": { "name": "Lorenzo Colitti", "email": "lorenzo@google.com", "time": "Sun Mar 03 20:46:46 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "net: ipv6: Don\u0027t purge default router if accept_ra\u003d2\n\n[ Upstream commit 3e8b0ac3e41e3c882222a5522d5df7212438ab51 ]\n\nSetting net.ipv6.conf.\u003cinterface\u003e.accept_ra\u003d2 causes the kernel\nto accept RAs even when forwarding is enabled. However, enabling\nforwarding purges all default routes on the system, breaking\nconnectivity until the next RA is received. Fix this by not\npurging default routes on interfaces that have accept_ra\u003d2.\n\nSigned-off-by: Lorenzo Colitti \u003clorenzo@google.com\u003e\nAcked-by: YOSHIFUJI Hideaki \u003cyoshfuji@linux-ipv6.org\u003e\nAcked-by: Eric Dumazet \u003cedumazet@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "2b2066c41aba3032831ff5402bbd3b68ff5b9d47", "tree": "900a0dbb2feae815df7e3c1fbad05f56a5c871d8", "parents": [ "136d76de5b72b4a45eec80e4e5ee14f397aa1fed" ], "author": { "name": "Cong Wang", "email": "amwang@redhat.com", "time": "Sun Mar 03 16:18:11 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "rds: limit the size allocated by rds_message_alloc()\n\n[ Upstream commit ece6b0a2b25652d684a7ced4ae680a863af041e0 ]\n\nDave Jones reported the following bug:\n\n\"When fed mangled socket data, rds will trust what userspace gives it,\nand tries to allocate enormous amounts of memory larger than what\nkmalloc can satisfy.\"\n\nWARNING: at mm/page_alloc.c:2393 __alloc_pages_nodemask+0xa0d/0xbe0()\nHardware name: GA-MA78GM-S2H\nModules linked in: vmw_vsock_vmci_transport vmw_vmci vsock fuse bnep dlci bridge 8021q garp stp mrp binfmt_misc l2tp_ppp l2tp_core rfcomm s\nPid: 24652, comm: trinity-child2 Not tainted 3.8.0+ #65\nCall Trace:\n [\u003cffffffff81044155\u003e] warn_slowpath_common+0x75/0xa0\n [\u003cffffffff8104419a\u003e] warn_slowpath_null+0x1a/0x20\n [\u003cffffffff811444ad\u003e] __alloc_pages_nodemask+0xa0d/0xbe0\n [\u003cffffffff8100a196\u003e] ? native_sched_clock+0x26/0x90\n [\u003cffffffff810b2128\u003e] ? trace_hardirqs_off_caller+0x28/0xc0\n [\u003cffffffff810b21cd\u003e] ? trace_hardirqs_off+0xd/0x10\n [\u003cffffffff811861f8\u003e] alloc_pages_current+0xb8/0x180\n [\u003cffffffff8113eaaa\u003e] __get_free_pages+0x2a/0x80\n [\u003cffffffff811934fe\u003e] kmalloc_order_trace+0x3e/0x1a0\n [\u003cffffffff81193955\u003e] __kmalloc+0x2f5/0x3a0\n [\u003cffffffff8104df0c\u003e] ? local_bh_enable_ip+0x7c/0xf0\n [\u003cffffffffa0401ab3\u003e] rds_message_alloc+0x23/0xb0 [rds]\n [\u003cffffffffa04043a1\u003e] rds_sendmsg+0x2b1/0x990 [rds]\n [\u003cffffffff810b21cd\u003e] ? trace_hardirqs_off+0xd/0x10\n [\u003cffffffff81564620\u003e] sock_sendmsg+0xb0/0xe0\n [\u003cffffffff810b2052\u003e] ? get_lock_stats+0x22/0x70\n [\u003cffffffff810b24be\u003e] ? put_lock_stats.isra.23+0xe/0x40\n [\u003cffffffff81567f30\u003e] sys_sendto+0x130/0x180\n [\u003cffffffff810b872d\u003e] ? trace_hardirqs_on+0xd/0x10\n [\u003cffffffff816c547b\u003e] ? _raw_spin_unlock_irq+0x3b/0x60\n [\u003cffffffff816cd767\u003e] ? sysret_check+0x1b/0x56\n [\u003cffffffff810b8695\u003e] ? trace_hardirqs_on_caller+0x115/0x1a0\n [\u003cffffffff81341d8e\u003e] ? trace_hardirqs_on_thunk+0x3a/0x3f\n [\u003cffffffff816cd742\u003e] system_call_fastpath+0x16/0x1b\n---[ end trace eed6ae990d018c8b ]---\n\nReported-by: Dave Jones \u003cdavej@redhat.com\u003e\nCc: Dave Jones \u003cdavej@redhat.com\u003e\nCc: David S. Miller \u003cdavem@davemloft.net\u003e\nCc: Venkat Venkatsubra \u003cvenkat.x.venkatsubra@oracle.com\u003e\nSigned-off-by: Cong Wang \u003camwang@redhat.com\u003e\nAcked-by: Venkat Venkatsubra \u003cvenkat.x.venkatsubra@oracle.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "136d76de5b72b4a45eec80e4e5ee14f397aa1fed", "tree": "80fb7a9d156401590fa78da5bc35d9ea80b8713c", "parents": [ "0530082c3595511fa2bfc1434a5ad809e5ec90a3" ], "author": { "name": "Guillaume Nault", "email": "g.nault@alphalink.fr", "time": "Fri Mar 01 05:02:02 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "l2tp: Restore socket refcount when sendmsg succeeds\n\n[ Upstream commit 8b82547e33e85fc24d4d172a93c796de1fefa81a ]\n\nThe sendmsg() syscall handler for PPPoL2TP doesn\u0027t decrease the socket\nreference counter after successful transmissions. Any successful\nsendmsg() call from userspace will then increase the reference counter\nforever, thus preventing the kernel\u0027s session and tunnel data from\nbeing freed later on.\n\nThe problem only happens when writing directly on L2TP sockets.\nPPP sockets attached to L2TP are unaffected as the PPP subsystem\nuses pppol2tp_xmit() which symmetrically increase/decrease reference\ncounters.\n\nThis patch adds the missing call to sock_put() before returning from\npppol2tp_sendmsg().\n\nSigned-off-by: Guillaume Nault \u003cg.nault@alphalink.fr\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "0530082c3595511fa2bfc1434a5ad809e5ec90a3", "tree": "8ff0366e6bfc136bd5e4f65bce642e22bb4599e5", "parents": [ "51dfcbf53c4cc6b1a65a99f27cec3311531b982b" ], "author": { "name": "Stéphane Marchesin", "email": "marcheu@chromium.org", "time": "Tue Jan 29 19:41:59 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "drm/i915: Increase the RC6p threshold.\n\ncommit 0920a48719f1ceefc909387a64f97563848c7854 upstream.\n\nThis increases GEN6_RC6p_THRESHOLD from 100000 to 150000. For some\nreason this avoids the gen6_gt_check_fifodbg.isra warnings and\nassociated GPU lockups, which makes my ivy bridge machine stable.\n\nSigned-off-by: Stéphane Marchesin \u003cmarcheu@chromium.org\u003e\nAcked-by: Jesse Barnes \u003cjbarnes@virtuousgeek.org\u003e\nSigned-off-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "51dfcbf53c4cc6b1a65a99f27cec3311531b982b", "tree": "88d86a8dac37766b3e3ab394d8505a869e70733a", "parents": [ "187c2bd82defa4d64910eed4d8c39ac93a984306" ], "author": { "name": "Guo Chao", "email": "yan@linux.vnet.ibm.com", "time": "Thu Feb 21 15:16:49 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "loopdev: remove an user triggerable oops\n\ncommit b1a6650406875b9097a032eed89af50682fe1160 upstream.\n\nWhen loopdev is built as module and we pass an invalid parameter,\nloop_init() will return directly without deregister misc device, which\nwill cause an oops when insert loop module next time because we left some\ngarbage in the misc device list.\n\nTest case:\nsudo modprobe loop max_part\u003d1024\n(failed due to invalid parameter)\nsudo modprobe loop\n(oops)\n\nClean up nicely to avoid such oops.\n\nSigned-off-by: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: Alexander Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: M. Hindess \u003chindessm@uk.ibm.com\u003e\nCc: Nikanth Karthikesan \u003cknikanth@suse.de\u003e\nCc: Jens Axboe \u003caxboe@kernel.dk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\nAcked-by: Jeff Mahoney \u003cjeffm@suse.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "187c2bd82defa4d64910eed4d8c39ac93a984306", "tree": "01c7ae69a8d93c59f5702762afa0acf778b3d3b2", "parents": [ "d72b4f90a2b042136f74a3de50b29d6ce76b5f12" ], "author": { "name": "Guo Chao", "email": "yan@linux.vnet.ibm.com", "time": "Thu Feb 21 15:16:45 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:01 2013 -0700" }, "message": "loopdev: fix a deadlock\n\ncommit 5370019dc2d2c2ff90e95d181468071362934f3a upstream.\n\nbd_mutex and lo_ctl_mutex can be held in different order.\n\nPath #1:\n\nblkdev_open\n blkdev_get\n __blkdev_get (hold bd_mutex)\n lo_open (hold lo_ctl_mutex)\n\nPath #2:\n\nblkdev_ioctl\n lo_ioctl (hold lo_ctl_mutex)\n lo_set_capacity (hold bd_mutex)\n\nLockdep does not report it, because path #2 actually holds a subclass of\nlo_ctl_mutex. This subclass seems creep into the code by mistake. The\npatch author actually just mentioned it in the changelog, see commit\nf028f3b2 (\"loop: fix circular locking in loop_clr_fd()\"), also see:\n\n\thttp://marc.info/?l\u003dlinux-kernel\u0026m\u003d123806169129727\u0026w\u003d2\n\nPath #2 hold bd_mutex to call bd_set_size(), I\u0027ve protected it\nwith i_mutex in a previous patch, so drop bd_mutex at this site.\n\nSigned-off-by: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: Alexander Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: M. Hindess \u003chindessm@uk.ibm.com\u003e\nCc: Nikanth Karthikesan \u003cknikanth@suse.de\u003e\nCc: Jens Axboe \u003caxboe@kernel.dk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\nAcked-by: Jeff Mahoney \u003cjeffm@suse.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d72b4f90a2b042136f74a3de50b29d6ce76b5f12", "tree": "61006b7819cf5bf3eebe63702f0aa6a8eb095c15", "parents": [ "969ff7dc5423e50938e7b42b59fe1163aced714c" ], "author": { "name": "Guo Chao", "email": "yan@linux.vnet.ibm.com", "time": "Thu Feb 21 15:16:42 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "block: use i_size_write() in bd_set_size()\n\ncommit d646a02a9d44d1421f273ae3923d97b47b918176 upstream.\n\nblkdev_ioctl(GETBLKSIZE) uses i_size_read() to read size of block device.\nIf we update block size directly, reader may see intermediate result in\nsome machines and configurations. Use i_size_write() instead.\n\nSigned-off-by: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: Alexander Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Guo Chao \u003cyan@linux.vnet.ibm.com\u003e\nCc: M. Hindess \u003chindessm@uk.ibm.com\u003e\nCc: Nikanth Karthikesan \u003cknikanth@suse.de\u003e\nCc: Jens Axboe \u003caxboe@kernel.dk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\nAcked-by: Jeff Mahoney \u003cjeffm@suse.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "969ff7dc5423e50938e7b42b59fe1163aced714c", "tree": "ce4ad064d2103322f8b11964f1e089909982a5fc", "parents": [ "81da76ae314c66e32b8c06b0ce155a5b61670dd7" ], "author": { "name": "Ben Hutchings", "email": "ben@decadent.org.uk", "time": "Sat Mar 16 06:32:16 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "hwmon: (sht15) Fix memory leak if regulator_enable() fails\n\nCommit 3e78080f8148 (\u0027hwmon: (sht15) Check return value of\nregulator_enable()\u0027) depends on the use of devm_kmalloc() for automatic\nresource cleanup in the failure cases, which was introduced in 3.7. In\nolder stable branches, explicit cleanup is needed.\n\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n" }, { "commit": "81da76ae314c66e32b8c06b0ce155a5b61670dd7", "tree": "360ac46ec63c1a9fed6e2b255a895643b8dab47b", "parents": [ "cb505e2eb68fe9e22afa220bf172f6aa090b7dca" ], "author": { "name": "Dmitry Rogozhkin", "email": "dmitry.v.rogozhkin@intel.com", "time": "Wed Oct 03 17:15:26 2012 +0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "drm/i915: EBUSY status handling added to i915_gem_fault().\n\ncommit e79e0fe380847493266fba557217e2773c61bd1b upstream.\n\nSubsequent threads returning EBUSY from vm_insert_pfn() was not handled\ncorrectly. As a result concurrent access from new threads to\nmmapped data caused SIGBUS.\n\nNote that this fixes i-g-t/tests/gem_threaded_tiled_access.\n\nTested-by: Mika Kuoppala \u003cmika.kuoppala@intel.com\u003e\nSigned-off-by: Dmitry Rogozhkin \u003cdmitry.v.rogozhkin@intel.com\u003e\nReviewed-by: Chris Wilson \u003cchris@chris-wilson.co.uk\u003e\nSigned-off-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cb505e2eb68fe9e22afa220bf172f6aa090b7dca", "tree": "d1b25dcc977afffedbca41ee63b331c6f49f1f00", "parents": [ "a40a945f829a2b95d5460491d81061166817e3cb" ], "author": { "name": "Johan Hovold", "email": "jhovold@gmail.com", "time": "Tue Feb 05 14:35:11 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "atmel_lcdfb: fix 16-bpp modes on older SOCs\n\ncommit a79eac7165ed62114e6ca197195aa5060a54f137 upstream.\n\nFix regression introduced by commit 787f9fd23283 (\"atmel_lcdfb: support\n16bit BGR:565 mode, remove unsupported 15bit modes\") which broke 16-bpp\nmodes for older SOCs which use IBGR:555 (msb is intensity) rather\nthan BGR:565.\n\nUse SOC-type to determine the pixel layout.\n\nTested on at91sam9263 and at91sam9g45.\n\nAcked-by: Peter Korsgaard \u003cjacmet@sunsite.dk\u003e\nSigned-off-by: Johan Hovold \u003cjhovold@gmail.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@atmel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "a40a945f829a2b95d5460491d81061166817e3cb", "tree": "829e7fb09e5576636361e52b8a54c8c0fbb122be", "parents": [ "59c0110f7ee64a9b5389b8b4fd2ec5feab9c6dc8" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Sat Mar 09 15:18:39 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "btrfs: use rcu_barrier() to wait for bdev puts at unmount\n\ncommit bc178622d40d87e75abc131007342429c9b03351 upstream.\n\nDoing this would reliably fail with -EBUSY for me:\n\n# mount /dev/sdb2 /mnt/scratch; umount /mnt/scratch; mkfs.btrfs -f /dev/sdb2\n...\nunable to open /dev/sdb2: Device or resource busy\n\nbecause mkfs.btrfs tries to open the device O_EXCL, and somebody still has it.\n\nUsing systemtap to track bdev gets \u0026 puts shows a kworker thread doing a\nblkdev put after mkfs attempts a get; this is left over from the unmount\npath:\n\nbtrfs_close_devices\n\t__btrfs_close_devices\n\t\tcall_rcu(\u0026device-\u003ercu, free_device);\n\t\t\tfree_device\n\t\t\t\tINIT_WORK(\u0026device-\u003ercu_work, __free_device);\n\t\t\t\tschedule_work(\u0026device-\u003ercu_work);\n\nso unmount might complete before __free_device fires \u0026 does its blkdev_put.\n\nAdding an rcu_barrier() to btrfs_close_devices() causes unmount to wait\nuntil all blkdev_put()s are done, and the device is truly free once\nunmount completes.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: Josef Bacik \u003cjbacik@fusionio.com\u003e\nSigned-off-by: Chris Mason \u003cchris.mason@fusionio.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "59c0110f7ee64a9b5389b8b4fd2ec5feab9c6dc8", "tree": "78f1f0031158bd52e529d72e6280c238a7d6b3e2", "parents": [ "8a52ddf504acc488696bdbe7bc4cef7a30a40091" ], "author": { "name": "Heiko Carstens", "email": "heiko.carstens@de.ibm.com", "time": "Mon Mar 04 14:14:11 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "s390/mm: fix flush_tlb_kernel_range()\n\ncommit f6a70a07079518280022286a1dceb797d12e1edf upstream.\n\nOur flush_tlb_kernel_range() implementation calls __tlb_flush_mm() with\n\u0026init_mm as argument. __tlb_flush_mm() however will only flush tlbs\nfor the passed in mm if its mm_cpumask is not empty.\n\nFor the init_mm however its mm_cpumask has never any bits set. Which in\nturn means that our flush_tlb_kernel_range() implementation doesn\u0027t\nwork at all.\n\nThis can be easily verified with a vmalloc/vfree loop which allocates\na page, writes to it and then frees the page again. A crash will follow\nalmost instantly.\n\nTo fix this remove the cpumask_empty() check in __tlb_flush_mm() since\nthere shouldn\u0027t be too many mms with a zero mm_cpumask, besides the\ninit_mm of course.\n\nSigned-off-by: Heiko Carstens \u003cheiko.carstens@de.ibm.com\u003e\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8a52ddf504acc488696bdbe7bc4cef7a30a40091", "tree": "ef37d60b72766c144f0fe15d7189d15ac771e03e", "parents": [ "6bf083ffc825244992274a23017655caee8e4c58" ], "author": { "name": "Martin Schwidefsky", "email": "schwidefsky@de.ibm.com", "time": "Thu Feb 28 16:28:41 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "s390: critical section cleanup vs. machine checks\n\ncommit 6551fbdfd8b85d1ab5822ac98abb4fb449bcfae0 upstream.\n\nThe current machine check code uses the registers stored by the machine\nin the lowcore at __LC_GPREGS_SAVE_AREA as the registers of the interrupted\ncontext. The registers 0-7 of a user process can get clobbered if a machine\nchecks interrupts the execution of a critical section in entry[64].S.\n\nThe reason is that the critical section cleanup code may need to modify\nthe PSW and the registers for the previous context to get to the end of a\ncritical section. If registers 0-7 have to be replaced the relevant copy\nwill be in the registers, which invalidates the copy in the lowcore. The\nmachine check handler needs to explicitly store registers 0-7 to the stack.\n\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "6bf083ffc825244992274a23017655caee8e4c58", "tree": "e74f39428f6ed033b83b5e1e227d9883669fee7c", "parents": [ "d7805638b85ce978f7c0cf1ac49204d4288084f6" ], "author": { "name": "David Rientjes", "email": "rientjes@google.com", "time": "Sun Mar 17 15:49:10 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "perf,x86: fix link failure for non-Intel configs\n\ncommit 6c4d3bc99b3341067775efd4d9d13cc8e655fd7c upstream.\n\nCommit 1d9d8639c063 (\"perf,x86: fix kernel crash with PEBS/BTS after\nsuspend/resume\") introduces a link failure since\nperf_restore_debug_store() is only defined for CONFIG_CPU_SUP_INTEL:\n\n\tarch/x86/power/built-in.o: In function `restore_processor_state\u0027:\n\t(.text+0x45c): undefined reference to `perf_restore_debug_store\u0027\n\nFix it by defining the dummy function appropriately.\n\nSigned-off-by: David Rientjes \u003crientjes@google.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d7805638b85ce978f7c0cf1ac49204d4288084f6", "tree": "07e7e08575d7ab4e3af38f0bac9e1835973491e8", "parents": [ "8c97feb5edd118fe633ed29773c599536d562d43" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Mar 17 15:44:43 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "perf,x86: fix wrmsr_on_cpu() warning on suspend/resume\n\ncommit 2a6e06b2aed6995af401dcd4feb5e79a0c7ea554 upstream.\n\nCommit 1d9d8639c063 (\"perf,x86: fix kernel crash with PEBS/BTS after\nsuspend/resume\") fixed a crash when doing PEBS performance profiling\nafter resuming, but in using init_debug_store_on_cpu() to restore the\nDS_AREA mtrr it also resulted in a new WARN_ON() triggering.\n\ninit_debug_store_on_cpu() uses \"wrmsr_on_cpu()\", which in turn uses CPU\ncross-calls to do the MSR update. Which is not really valid at the\nearly resume stage, and the warning is quite reasonable. Now, it all\nhappens to _work_, for the simple reason that smp_call_function_single()\nends up just doing the call directly on the CPU when the CPU number\nmatches, but we really should just do the wrmsr() directly instead.\n\nThis duplicates the wrmsr() logic, but hopefully we can just remove the\nwrmsr_on_cpu() version eventually.\n\nReported-and-tested-by: Parag Warudkar \u003cparag.lkml@gmail.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "8c97feb5edd118fe633ed29773c599536d562d43", "tree": "95bae3db178398cd3d451efed85c9ee2b69dd1f0", "parents": [ "e55005034b11c0dd52ac08b7f769ec410b6bfa1f" ], "author": { "name": "Dan Carpenter", "email": "dan.carpenter@oracle.com", "time": "Sat Mar 16 12:48:11 2013 +0300" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:05:00 2013 -0700" }, "message": "selinux: use GFP_ATOMIC under spin_lock\n\ncommit 4502403dcf8f5c76abd4dbab8726c8e4ecb5cd34 upstream.\n\nThe call tree here is:\n\nsk_clone_lock() \u003c- takes bh_lock_sock(newsk);\nxfrm_sk_clone_policy()\n__xfrm_sk_clone_policy()\nclone_policy() \u003c- uses GFP_ATOMIC for allocations\nsecurity_xfrm_policy_clone()\nsecurity_ops-\u003exfrm_policy_clone_security()\nselinux_xfrm_policy_clone()\n\nSigned-off-by: Dan Carpenter \u003cdan.carpenter@oracle.com\u003e\nSigned-off-by: James Morris \u003cjames.l.morris@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e55005034b11c0dd52ac08b7f769ec410b6bfa1f", "tree": "ecb7ca5c21191bb2248c5989f72c5034e28a5dc3", "parents": [ "9d4a6f2cee36dab61a3bd58d1f197f733738995f" ], "author": { "name": "Benjamin Herrenschmidt", "email": "benh@kernel.crashing.org", "time": "Wed Mar 13 09:55:02 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "powerpc: Fix cputable entry for 970MP rev 1.0\n\ncommit d63ac5f6cf31c8a83170a9509b350c1489a7262b upstream.\n\nCommit 44ae3ab3358e962039c36ad4ae461ae9fb29596c forgot to update\nthe entry for the 970MP rev 1.0 processor when moving some CPU\nfeatures bits to the MMU feature bit mask. This breaks booting\non some rare G5 models using that chip revision.\n\nReported-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": "9d4a6f2cee36dab61a3bd58d1f197f733738995f", "tree": "75835b0c3a149ef4a17066ce36fe7e6a2f0bdb97", "parents": [ "32f81345140d7f237afba1a26d42a11117a0304e" ], "author": { "name": "Benjamin Herrenschmidt", "email": "benh@kernel.crashing.org", "time": "Wed Mar 13 09:49:06 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "powerpc: Fix STAB initialization\n\ncommit 13938117a57f88a22f0df9722a5db7271fda85cd upstream.\n\nCommit f5339277eb8d3aed37f12a27988366f68ab68930 accidentally removed\nmore than just iSeries bits and took out the call to stab_initialize()\nthus breaking support for POWER3 processors.\n\nPut it back. (Yes, nobody noticed until now ...)\n\nSigned-off-by: Benjamin Herrenschmidt \u003cbenh@kernel.crashing.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "32f81345140d7f237afba1a26d42a11117a0304e", "tree": "9a2b49bb4b5a7dbecf92bcd8263cd5857492028d", "parents": [ "dce5c33d7abb21e165722b32c43899457c73106f" ], "author": { "name": "Marcin Jurkowski", "email": "marcin1j@gmail.com", "time": "Sat Mar 02 14:50:15 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "w1: fix oops when w1_search is called from netlink connector\n\ncommit 9d1817cab2f030f6af360e961cc69bb1da8ad765 upstream.\n\nOn Sat, Mar 02, 2013 at 10:45:10AM +0100, Sven Geggus wrote:\n\u003e This is the bad commit I found doing git bisect:\n\u003e 04f482faf50535229a5a5c8d629cf963899f857c is the first bad commit\n\u003e commit 04f482faf50535229a5a5c8d629cf963899f857c\n\u003e Author: Patrick McHardy \u003ckaber@trash.net\u003e\n\u003e Date: Mon Mar 28 08:39:36 2011 +0000\n\nGood job. I was too lazy to bisect for bad commit;)\n\nReading the code I found problematic kthread_should_stop call from netlink\nconnector which causes the oops. After applying a patch, I\u0027ve been testing\nowfs+w1 setup for nearly two days and it seems to work very reliable (no\nhangs, no memleaks etc).\nMore detailed description and possible fix is given below:\n\nFunction w1_search can be called from either kthread or netlink callback.\nWhile the former works fine, the latter causes oops due to kthread_should_stop\ninvocation.\n\nThis patch adds a check if w1_search is serving netlink command, skipping\nkthread_should_stop invocation if so.\n\nSigned-off-by: Marcin Jurkowski \u003cmarcin1j@gmail.com\u003e\nAcked-by: Evgeniy Polyakov \u003czbr@ioremap.net\u003e\nCc: Josh Boyer \u003cjwboyer@gmail.com\u003e\nTested-by: Sven Geggus \u003clists@fuchsschwanzdomain.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "dce5c33d7abb21e165722b32c43899457c73106f", "tree": "c6dd866ca0eea137fd1d35a48d434a28d329c18a", "parents": [ "fa5553789ef0bb74434ffedad2fd9e2d994ba92f" ], "author": { "name": "Axel Lin", "email": "axel.lin@ingics.com", "time": "Thu Mar 14 16:27:18 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "hwmon: (lineage-pem) Add missing terminating entry for pem_[input|fan]_attributes\n\ncommit df069079c153d22adf6c28dcc0b1cf62bba75167 upstream.\n\nSigned-off-by: Axel Lin \u003caxel.lin@ingics.com\u003e\nAcked-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "fa5553789ef0bb74434ffedad2fd9e2d994ba92f", "tree": "42ff70e044b30525c1b358d35b6a394995890ab0", "parents": [ "fe88b8bc2e9e9f97428337582919b41bd7d3d22a" ], "author": { "name": "Guenter Roeck", "email": "linux@roeck-us.net", "time": "Thu Feb 21 10:27:54 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "hwmon: (pmbus/ltc2978) Fix temperature reporting\n\ncommit 8c958c703ef8804093437959221951eaf0e1e664 upstream.\n\nOn LTC2978, only READ_TEMPERATURE is supported. It reports\nthe internal junction temperature. This register is unpaged.\n\nOn LTC3880, READ_TEMPERATURE and READ_TEMPERATURE2 are supported.\nREAD_TEMPERATURE is paged and reports external temperatures.\nREAD_TEMPERATURE2 is unpaged and reports the internal junction\ntemperature.\n\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nAcked-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "fe88b8bc2e9e9f97428337582919b41bd7d3d22a", "tree": "7afb49d8f7026eb71976ff75168b7be18f381367", "parents": [ "9a9b01c04ef4b844f64bbf36987f918e64e304a2" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Fri Mar 08 18:11:17 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "ALSA: seq: Fix missing error handling in snd_seq_timer_open()\n\ncommit 66efdc71d95887b652a742a5dae51fa834d71465 upstream.\n\nsnd_seq_timer_open() didn\u0027t catch the whole error path but let through\nif the timer id is a slave. This may lead to Oops by accessing the\nuninitialized pointer.\n\n BUG: unable to handle kernel NULL pointer dereference at 00000000000002ae\n IP: [\u003cffffffff819b3477\u003e] snd_seq_timer_open+0xe7/0x130\n PGD 785cd067 PUD 76964067 PMD 0\n Oops: 0002 [#4] SMP\n CPU 0\n Pid: 4288, comm: trinity-child7 Tainted: G D W 3.9.0-rc1+ #100 Bochs Bochs\n RIP: 0010:[\u003cffffffff819b3477\u003e] [\u003cffffffff819b3477\u003e] snd_seq_timer_open+0xe7/0x130\n RSP: 0018:ffff88006ece7d38 EFLAGS: 00010246\n RAX: 0000000000000286 RBX: ffff88007851b400 RCX: 0000000000000000\n RDX: 000000000000ffff RSI: ffff88006ece7d58 RDI: ffff88006ece7d38\n RBP: ffff88006ece7d98 R08: 000000000000000a R09: 000000000000fffe\n R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n R13: ffff8800792c5400 R14: 0000000000e8f000 R15: 0000000000000007\n FS: 00007f7aaa650700(0000) GS:ffff88007f800000(0000) GS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00000000000002ae CR3: 000000006efec000 CR4: 00000000000006f0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400\n Process trinity-child7 (pid: 4288, threadinfo ffff88006ece6000, task ffff880076a8a290)\n Stack:\n 0000000000000286 ffffffff828f2be0 ffff88006ece7d58 ffffffff810f354d\n 65636e6575716573 2065756575712072 ffff8800792c0030 0000000000000000\n ffff88006ece7d98 ffff8800792c5400 ffff88007851b400 ffff8800792c5520\n Call Trace:\n [\u003cffffffff810f354d\u003e] ? trace_hardirqs_on+0xd/0x10\n [\u003cffffffff819b17e9\u003e] snd_seq_queue_timer_open+0x29/0x70\n [\u003cffffffff819ae01a\u003e] snd_seq_ioctl_set_queue_timer+0xda/0x120\n [\u003cffffffff819acb9b\u003e] snd_seq_do_ioctl+0x9b/0xd0\n [\u003cffffffff819acbe0\u003e] snd_seq_ioctl+0x10/0x20\n [\u003cffffffff811b9542\u003e] do_vfs_ioctl+0x522/0x570\n [\u003cffffffff8130a4b3\u003e] ? file_has_perm+0x83/0xa0\n [\u003cffffffff810f354d\u003e] ? trace_hardirqs_on+0xd/0x10\n [\u003cffffffff811b95ed\u003e] sys_ioctl+0x5d/0xa0\n [\u003cffffffff813663fe\u003e] ? trace_hardirqs_on_thunk+0x3a/0x3f\n [\u003cffffffff81faed69\u003e] system_call_fastpath+0x16/0x1b\n\nReported-and-tested-by: Tommi Rantala \u003ctt.rantala@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": "9a9b01c04ef4b844f64bbf36987f918e64e304a2", "tree": "12cd294a8b45e518c2083f399ef67b22348039df", "parents": [ "75750fc43320a6b2ef9852b3437fa25104add6f6" ], "author": { "name": "Stephane Eranian", "email": "eranian@google.com", "time": "Fri Mar 15 14:26:07 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "perf,x86: fix kernel crash with PEBS/BTS after suspend/resume\n\ncommit 1d9d8639c063caf6efc2447f5f26aa637f844ff6 upstream.\n\nThis patch fixes a kernel crash when using precise sampling (PEBS)\nafter a suspend/resume. Turns out the CPU notifier code is not invoked\non CPU0 (BP). Therefore, the DS_AREA (used by PEBS) is not restored properly\nby the kernel and keeps it power-on/resume value of 0 causing any PEBS\nmeasurement to crash when running on CPU0.\n\nThe workaround is to add a hook in the actual resume code to restore\nthe DS Area MSR value. It is invoked for all CPUS. So for all but CPU0,\nthe DS_AREA will be restored twice but this is harmless.\n\nReported-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Stephane Eranian \u003ceranian@google.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "75750fc43320a6b2ef9852b3437fa25104add6f6", "tree": "d4a051b23235706a0abd627799fc15d192017e1c", "parents": [ "3b11e57876950e7530fc9f6122179525000fda20" ], "author": { "name": "Jiri Slaby", "email": "jslaby@suse.cz", "time": "Tue Jan 15 23:26:22 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "TTY: do not reset master\u0027s packet mode\n\ncommit b81273a132177edd806476b953f6afeb17b786d5 upstream.\n\nNow that login from util-linux is forced to drop all references to a\nTTY which it wants to hangup (to reach reference count 1) we are\nseeing issues with telnet. When login closes its last reference to the\nslave PTY, it also resets packet mode on the *master* side. And we\nhave a race here.\n\nWhat telnet does is fork+exec of `login\u0027. Then there are two\nscenarios:\n* `login\u0027 closes the slave TTY and resets thus master\u0027s packet mode,\n but even now telnet properly sets the mode, or\n* `telnetd\u0027 sets packet mode on the master, `login\u0027 closes the slave\n TTY and resets master\u0027s packet mode.\n\nThe former case is OK. However the latter happens in much more cases,\nby the order of magnitude to be precise. So when one tries to login to\nsuch a messed telnet setup, they see the following:\ninux login:\n ogin incorrect\n\nNote the missing first letters -- telnet thinks it is still in the\npacket mode, so when it receives \"linux login\" from `login\u0027, it\nconsiders \"l\" as the type of the packet and strips it.\n\nSuS does not mention how the implementation should behave. Both BSDs I\nchecked (Free and Net) do not reset the flag upon the last close.\n\nBy this I am resurrecting an old bug, see References. We are hitting\nit regularly now, i.e. with updated util-linux, ergo login.\n\nHere, I am changing a behavior introduced back in 2.1 times. It would\nbetter have a long time testing before goes upstream.\n\nSigned-off-by: Jiri Slaby \u003cjslaby@suse.cz\u003e\nCc: Mauro Carvalho Chehab \u003cmchehab@redhat.com\u003e\nCc: Bryan Mason \u003cbmason@redhat.com\u003e\nReferences: https://lkml.org/lkml/2009/11/11/223\nReferences: https://bugzilla.redhat.com/show_bug.cgi?id\u003d504703\nReferences: https://bugzilla.novell.com/show_bug.cgi?id\u003d797042\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3b11e57876950e7530fc9f6122179525000fda20", "tree": "555033dad6b74594078125723909032269c364ad", "parents": [ "d91371bb47c16271e8dcb0da255ab1e0b5d15733" ], "author": { "name": "Paul Bolle", "email": "pebolle@tiscali.nl", "time": "Sat Mar 09 23:16:44 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:59 2013 -0700" }, "message": "tty: serial: fix typo \"ARCH_S5P6450\"\n\ncommit 827aa0d36d486f359808c8fb931cf7a71011a09d upstream.\n\nThis could have been either ARCH_S5P64X0 or CPU_S5P6450. Looking at\ncommit 2555e663b367b8d555e76023f4de3f6338c28d6c (\"ARM: S5P64X0: Add UART\nserial support for S5P6450\") - which added this typo - makes clear this\nshould be CPU_S5P6450.\n\nSigned-off-by: Paul Bolle \u003cpebolle@tiscali.nl\u003e\nAcked-by: Kukjin Kim \u003ckgene.kim@samsung.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d91371bb47c16271e8dcb0da255ab1e0b5d15733", "tree": "4b239aaeadac642d3d1232ee933a2eb910d2f4c5", "parents": [ "e3c51d6b8b4cc278196897e624bc2bdeae8f7798" ], "author": { "name": "Wang YanQing", "email": "udknight@gmail.com", "time": "Fri Mar 01 11:47:20 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "serial: 8250_pci: add support for another kind of NetMos Technology PCI 9835 Multi-I/O Controller\n\ncommit 8d2f8cd424ca0b99001f3ff4f5db87c4e525f366 upstream.\n\n01:08.0 Communication controller: NetMos Technology PCI 9835 Multi-I/O Controller (rev 01)\n\tSubsystem: Device [1000:0012]\n\tControl: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-\n\tStatus: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL\u003dmedium \u003eTAbort- \u003cTAbort- \u003cMAbort- \u003eSERR- \u003cPERR- INTx-\n\tInterrupt: pin A routed to IRQ 20\n\tRegion 0: I/O ports at e050 [size\u003d8]\n\tRegion 1: I/O ports at e040 [size\u003d8]\n\tRegion 2: I/O ports at e030 [size\u003d8]\n\tRegion 3: I/O ports at e020 [size\u003d8]\n\tRegion 4: I/O ports at e010 [size\u003d8]\n\tRegion 5: I/O ports at e000 [size\u003d16]\n\nSigned-off-by: Wang YanQing \u003cudknight@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e3c51d6b8b4cc278196897e624bc2bdeae8f7798", "tree": "ee6be9f35cdf1cc3ba023b20da1ed9d925850996", "parents": [ "44ddae422775744b49248dff8818a141d3a03820" ], "author": { "name": "Lars-Peter Clausen", "email": "lars@metafoo.de", "time": "Sat Mar 09 15:28:44 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "ext3: Fix format string issues\n\ncommit 8d0c2d10dd72c5292eda7a06231056a4c972e4cc upstream.\n\next3_msg() takes the printk prefix as the second parameter and the\nformat string as the third parameter. Two callers of ext3_msg omit the\nprefix and pass the format string as the second parameter and the first\nparameter to the format string as the third parameter. In both cases\nthis string comes from an arbitrary source. Which means the string may\ncontain format string characters, which will\nlead to undefined and potentially harmful behavior.\n\nThe issue was introduced in commit 4cf46b67eb(\"ext3: Unify log messages\nin ext3\") and is fixed by this patch.\n\nSigned-off-by: Lars-Peter Clausen \u003clars@metafoo.de\u003e\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "44ddae422775744b49248dff8818a141d3a03820", "tree": "22f91f1b83b72fa8cf4c652b70a30ce0ba7f99a9", "parents": [ "a4371b6605f7b6930ba95df316948be6b306be73" ], "author": { "name": "Kees Cook", "email": "keescook@chromium.org", "time": "Wed Mar 13 14:59:33 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "signal: always clear sa_restorer on execve\n\ncommit 2ca39528c01a933f6689cd6505ce65bd6d68a530 upstream.\n\nWhen the new signal handlers are set up, the location of sa_restorer is\nnot cleared, leaking a parent process\u0027s address space location to\nchildren. This allows for a potential bypass of the parent\u0027s ASLR by\nexamining the sa_restorer value returned when calling sigaction().\n\nBased on what should be considered \"secret\" about addresses, it only\nmatters across the exec not the fork (since the VMAs haven\u0027t changed\nuntil the exec). But since exec sets SIG_DFL and keeps sa_restorer,\nthis is where it should be fixed.\n\nGiven the few uses of sa_restorer, a \"set\" function was not written\nsince this would be the only use. Instead, we use\n__ARCH_HAS_SA_RESTORER, as already done in other places.\n\nExample of the leak before applying this patch:\n\n $ cat /proc/$$/maps\n ...\n 7fb9f3083000-7fb9f3238000 r-xp 00000000 fd:01 404469 .../libc-2.15.so\n ...\n $ ./leak\n ...\n 7f278bc74000-7f278be29000 r-xp 00000000 fd:01 404469 .../libc-2.15.so\n ...\n 1 0 (nil) 0x7fb9f30b94a0\n 2 4000000 (nil) 0x7f278bcaa4a0\n 3 4000000 (nil) 0x7f278bcaa4a0\n 4 0 (nil) 0x7fb9f30b94a0\n ...\n\n[akpm@linux-foundation.org: use SA_RESTORER for backportability]\nSigned-off-by: Kees Cook \u003ckeescook@chromium.org\u003e\nReported-by: Emese Revfy \u003cre.emese@gmail.com\u003e\nCc: Emese Revfy \u003cre.emese@gmail.com\u003e\nCc: PaX Team \u003cpageexec@freemail.hu\u003e\nCc: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: Oleg Nesterov \u003coleg@redhat.com\u003e\nCc: \"Eric W. Biederman\" \u003cebiederm@xmission.com\u003e\nCc: Serge Hallyn \u003cserge.hallyn@canonical.com\u003e\nCc: Julien Tinnes \u003cjln@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": "a4371b6605f7b6930ba95df316948be6b306be73", "tree": "4ce486c02b0df229d6bffa31ccd2059e92a2ab6a", "parents": [ "0319f9909ce68a7516dfc8d53400e07168d281a8" ], "author": { "name": "Malcolm Priestley", "email": "tvboxspy@gmail.com", "time": "Mon Feb 18 19:54:18 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "staging: vt6656: Fix oops on resume from suspend.\n\ncommit 6987a6dabfc40222ef767f67b57212fe3a0225fb upstream.\n\nRemove usb_put_dev from vt6656_suspend and usb_get_dev\nfrom vt6566_resume.\n\nThese are not normally in suspend/resume functions.\n\nSigned-off-by: Malcolm Priestley \u003ctvboxspy@gmail.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0319f9909ce68a7516dfc8d53400e07168d281a8", "tree": "adafa4d021035c055a5d1e417760db27eb62b9c1", "parents": [ "0b520a5db298be1d1e74b8e51a02d73e1dbf6045" ], "author": { "name": "Alan Stern", "email": "stern@rowland.harvard.edu", "time": "Fri Mar 01 10:51:15 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "USB: EHCI: don\u0027t check DMA values in QH overlays\n\ncommit feca7746d5d9e84b105a613b7f3b6ad00d327372 upstream.\n\nThis patch (as1661) fixes a rather obscure bug in ehci-hcd. In a\ncouple of places, the driver compares the DMA address stored in a QH\u0027s\noverlay region with the address of a particular qTD, in order to see\nwhether that qTD is the one currently being processed by the hardware.\n(If it is then the status in the QH\u0027s overlay region is more\nup-to-date than the status in the qTD, and if it isn\u0027t then the\noverlay\u0027s value needs to be adjusted when the QH is added back to the\nactive schedule.)\n\nHowever, DMA address in the overlay region isn\u0027t always valid. It\nsometimes will contain a stale value, which may happen by coincidence\nto be equal to a qTD\u0027s DMA address. Instead of checking the DMA\naddress, we should check whether the overlay region is active and\nvalid. The patch tests the ACTIVE bit in the overlay, and clears this\nbit when the overlay becomes invalid (which happens when the\ncurrently-executing URB is unlinked).\n\nThis is the second part of a fix for the regression reported at:\n\n\thttps://bugs.launchpad.net/bugs/1088733\n\nSigned-off-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nReported-by: Joseph Salisbury \u003cjoseph.salisbury@canonical.com\u003e\nReported-and-tested-by: Stephen Thirlwall \u003csdt@dr.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0b520a5db298be1d1e74b8e51a02d73e1dbf6045", "tree": "d1930051aa1003fd087b44c446f7e6f96c592fc1", "parents": [ "e870d9d8383f893b4b825220249e2f4d1014c3c0" ], "author": { "name": "Bjørn Mork", "email": "bjorn@mork.no", "time": "Mon Mar 04 14:19:21 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "USB: storage: fix Huawei mode switching regression\n\ncommit ab4b71644a26d1ab92b987b2fd30e17c25e89f85 upstream.\n\nThis reverts commit 200e0d99 (\"USB: storage: optimize to match the\nHuawei USB storage devices and support new switch command\" and the\nfollowup bugfix commit cd060956 (\"USB: storage: properly handle\nthe endian issues of idProduct\").\n\nThe commit effectively added a large number of Huawei devices to\nthe deprecated usb-storage mode switching logic. Many of these\ndevices have been in use and supported by the userspace\nusb_modeswitch utility for years. Forcing the switching inside\nthe kernel causes a number of regressions as a result of ignoring\nexisting onfigurations, and also completely takes away the ability\nto configure mode switching per device/system/user.\n\nKnown regressions caused by this:\n - Some of the devices support multiple modes, using different\n switching commands. There are existing configurations taking\n advantage of this.\n\n - There is a real use case for disabling mode switching and\n instead mounting the exposed storage device. This becomes\n impossible with switching logic inside the usb-storage driver.\n\n - At least on device fail as a result of the usb-storage switching\n command, becoming completely unswitchable. This is possibly a\n firmware bug, but still a regression because the device work as\n expected using usb_modeswitch defaults.\n\nIn-kernel mode switching was deprecated years ago with the\ndevelopment of the more user friendly userspace alternatives. The\nexisting list of devices in usb-storage was only kept to prevent\nbreaking already working systems. The long term plan is to remove\nthe list, not to add to it. Ref:\nhttp://permalink.gmane.org/gmane.linux.usb.general/28543\n\nSigned-off-by: Bjørn Mork \u003cbjorn@mork.no\u003e\nCc: \u003cfangxiaozhi@huawei.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e870d9d8383f893b4b825220249e2f4d1014c3c0", "tree": "ec4d623cefc7170f404d3064a8fc6ec986d2fea4", "parents": [ "5c1892eea53d57d2264195a3ba0de6b1e852ab79" ], "author": { "name": "Steve Conklin", "email": "sconklin@canonical.com", "time": "Thu Mar 07 17:19:33 2013 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "usb: serial: Add Rigblaster Advantage to device table\n\ncommit a57e82a18779ab8a5e5a1f5841cef937cf578913 upstream.\n\nThe Rigblaster Advantage is an amateur radio interface sold by West Mountain\nRadio. It contains a cp210x serial interface but the device ID is not in\nthe driver.\n\nSigned-off-by: Steve Conklin \u003csconklin@canonical.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5c1892eea53d57d2264195a3ba0de6b1e852ab79", "tree": "b9f71e46a7dbd719785e41155adedca5ecc4ccc0", "parents": [ "0864bc57e945053f733ff54adf2a60336734b9cc" ], "author": { "name": "Christian Schmiedl", "email": "christian.schmiedl@gemalto.com", "time": "Wed Mar 06 17:08:50 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "USB: added support for Cinterion\u0027s products AH6 and PLS8\n\ncommit 1941138e1c024ecb5bd797d414928d3eb94d8662 upstream.\n\nadd support for Cinterion\u0027s products AH6 and PLS8 by adding Product IDs\nand USB_DEVICE tuples.\n\nSigned-off-by: Christian Schmiedl \u003cchristian.schmiedl@gemalto.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "0864bc57e945053f733ff54adf2a60336734b9cc", "tree": "4432d4f3fe0e745dd168c0b8ff43e19d0a79cab5", "parents": [ "5c6142cc0c0e58daff87e26b1fce585397418bc4" ], "author": { "name": "Matwey V. Kornilov", "email": "matwey@sai.msu.ru", "time": "Sat Mar 09 13:57:32 2013 +0400" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "usb: cp210x new Vendor/Device IDs\n\ncommit be3101c23394af59694c8a2aae6d07f5da62fea5 upstream.\n\nThis patch adds support for the Lake Shore Cryotronics devices to\nthe CP210x driver.\n\nThese lines are ported from cp210x driver distributed by Lake Shore web site:\n http://www.lakeshore.com/Documents/Lake%20Shore%20cp210x-3.0.0.tar.gz\nand licensed under the terms of GPLv2.\n\nMoreover, I\u0027ve tested this changes with Lake Shore 335 in my labs.\n\nSigned-off-by: Matwey V. Kornilov \u003cmatwey@sai.msu.ru\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "5c6142cc0c0e58daff87e26b1fce585397418bc4", "tree": "055d24effa02f6391285cebaebb63ecb107d9d57", "parents": [ "82eccc247f86010b0936983b6e963ffd5d4c79e1" ], "author": { "name": "Oliver Neukum", "email": "oneukum@suse.de", "time": "Tue Mar 12 14:52:42 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:58 2013 -0700" }, "message": "USB: cdc-wdm: fix buffer overflow\n\ncommit c0f5ecee4e741667b2493c742b60b6218d40b3aa upstream.\n\nThe buffer for responses must not overflow.\nIf this would happen, set a flag, drop the data and return\nan error after user space has read all remaining data.\n\nSigned-off-by: Oliver Neukum \u003coliver@neukum.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "82eccc247f86010b0936983b6e963ffd5d4c79e1", "tree": "dcbef9914d5cbbc0e47d05050de8d32d9ac78fc3", "parents": [ "c8fba5853260c3114ed0a24f721cd4c415ea011c" ], "author": { "name": "Bjørn Mork", "email": "bjorn@mork.no", "time": "Wed Feb 27 15:52:56 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:57 2013 -0700" }, "message": "USB: option: add Huawei E5331\n\ncommit daec90e7382cbd0e73eb6861109b3da91e5ab1f3 upstream.\n\nAnother device using CDC ACM with vendor specific protocol to mark\nserial functions.\n\nSigned-off-by: Bjørn Mork \u003cbjorn@mork.no\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "c8fba5853260c3114ed0a24f721cd4c415ea011c", "tree": "83878b4513702cea4f37637340447278274e85c6", "parents": [ "40e0c1e9b65e94462498ead4a63b1ee08fa40d42" ], "author": { "name": "Amit Shah", "email": "amit.shah@redhat.com", "time": "Fri Mar 08 11:30:18 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:57 2013 -0700" }, "message": "virtio: rng: disallow multiple device registrations, fixes crashes\n\ncommit e84e7a56a3aa2963db506299e29a5f3f09377f9b upstream.\n\nThe code currently only supports one virtio-rng device at a time.\nInvoking guests with multiple devices causes the guest to blow up.\n\nCheck if we\u0027ve already registered and initialised the driver. Also\ncleanup in case of registration errors or hot-unplug so that a new\ndevice can be used.\n\nReported-by: Peter Krempa \u003cpkrempa@redhat.com\u003e\nReported-by: \u003cyunzheng@redhat.com\u003e\nSigned-off-by: Amit Shah \u003camit.shah@redhat.com\u003e\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "40e0c1e9b65e94462498ead4a63b1ee08fa40d42", "tree": "ef5ecf1e689db161578d4ec3af4ce78e72878243", "parents": [ "990942383df7d1c11471621a7fe25067cc270dd0" ], "author": { "name": "Konrad Rzeszutek Wilk", "email": "konrad.wilk@oracle.com", "time": "Tue Mar 05 13:14:19 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:57 2013 -0700" }, "message": "xen/pciback: Don\u0027t disable a PCI device that is already disabled.\n\ncommit bdc5c1812cea6efe1aaefb3131fcba28cd0b2b68 upstream.\n\nWhile shuting down a HVM guest with pci devices passed through we\nget this:\n\npciback 0000:04:00.0: restoring config space at offset 0x4 (was 0x100000, writing 0x100002)\n------------[ cut here ]------------\nWARNING: at drivers/pci/pci.c:1397 pci_disable_device+0x88/0xa0()\nHardware name: MS-7640\nDevice pciback\ndisabling already-disabled device\nModules linked in:\nPid: 53, comm: xenwatch Not tainted 3.9.0-rc1-20130304a+ #1\nCall Trace:\n [\u003cffffffff8106994a\u003e] warn_slowpath_common+0x7a/0xc0\n [\u003cffffffff81069a31\u003e] warn_slowpath_fmt+0x41/0x50\n [\u003cffffffff813cf288\u003e] pci_disable_device+0x88/0xa0\n [\u003cffffffff814554a7\u003e] xen_pcibk_reset_device+0x37/0xd0\n [\u003cffffffff81454b6f\u003e] ? pcistub_put_pci_dev+0x6f/0x120\n [\u003cffffffff81454b8d\u003e] pcistub_put_pci_dev+0x8d/0x120\n [\u003cffffffff814582a9\u003e] __xen_pcibk_release_devices+0x59/0xa0\n\nThis fixes the bug.\n\nReported-and-Tested-by: Sander Eikelenboom \u003clinux@eikelenboom.it\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": "990942383df7d1c11471621a7fe25067cc270dd0", "tree": "5910b8b8096813fa42f2289f13f3a2b127dcbde4", "parents": [ "92a7adfb8118f64787beb27b597d43f0202715d2" ], "author": { "name": "Dan Williams", "email": "dcbw@redhat.com", "time": "Tue Feb 19 09:47:09 2013 -0600" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Wed Mar 20 13:04:57 2013 -0700" }, "message": "qcaux: add Franklin U600\n\ncommit 2d90e63603ac235aecd7d20e234616e0682c8b1f upstream.\n\n4 ports; AT/PPP is standard CDC-ACM. The other three (added by this\npatch) are QCDM/DIAG, possibly GPS, and unknown.\n\nSigned-off-by: Dan Williams \u003cdcbw@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "92a7adfb8118f64787beb27b597d43f0202715d2", "tree": "0c3c30ab7fc136cf3aed6ae967666917180245fd", "parents": [ "8420d82e3a25e0f64526db253056945b1585dc08" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:30:25 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:30:25 2013 -0700" }, "message": "Linux 3.4.36\n" }, { "commit": "8420d82e3a25e0f64526db253056945b1585dc08", "tree": "68a87ed7a1303b50ef4b5f451d93c45eb3c60ee7", "parents": [ "983c9b4e483b7720e72378d69ef18b6188d17ab1" ], "author": { "name": "Sarah Sharp", "email": "sarah.a.sharp@linux.intel.com", "time": "Wed Mar 13 10:59:21 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:52 2013 -0700" }, "message": "USB: Fix connected device switch to Inactive state.\n\n[This is upstream commit d3b9d7a9051d7024a93c76a84b2f84b3b66ad6d5.\nIt needs to be backported to kernels as old as 3.2, because it fixes the\nbuggy commit 9dbcaec830cd97f44a0b91b315844e0d7144746b \"USB: Handle warm\nreset failure on empty port.\"]\n\nA USB 3.0 device can transition to the Inactive state if a U1 or U2 exit\ntransition fails. The current code in hub_events simply issues a warm\nreset, but does not call any pre-reset or post-reset driver methods (or\nunbind/rebind drivers without them). Therefore the drivers won\u0027t know\ntheir device has just been reset.\n\nhub_events should instead call usb_reset_device. This means\nhub_port_reset now needs to figure out whether it should issue a warm\nreset or a hot reset.\n\nRemove the FIXME note about needing disconnect() for a NOTATTACHED\ndevice. This patch fixes that.\n\nSigned-off-by: Sarah Sharp \u003csarah.a.sharp@linux.intel.com\u003e\nAcked-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "983c9b4e483b7720e72378d69ef18b6188d17ab1", "tree": "1284c4d0cf1ae0f60a1acf75627b3820f6ca80fc", "parents": [ "beabe20445c60322719d8f58e9eb9dd4660c1b3e" ], "author": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Tue Mar 12 15:18:13 2013 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:52 2013 -0700" }, "message": "Revert \"ALSA: hda - hdmi: Make jacks phantom, if they\u0027re not detectable\"\n\nThis reverts commit 30efd8debd1ef30be342d374f01e993509f5b76b upstream\n(dd54ec4067a23236736afecbda120030d7ce8fe9 in this tree) as it is not\nneeded for the 3.4-stable tree.\n\nCc: David Henningsson \u003cdavid.henningsson@canonical.com\u003e\nCc: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "beabe20445c60322719d8f58e9eb9dd4660c1b3e", "tree": "55166ff183186b0faa5b95fc71ac6747b9d9eaf2", "parents": [ "e850004e595d6322c6b7ccbfe21a4582051ad56b" ], "author": { "name": "Sarah Sharp", "email": "sarah.a.sharp@linux.intel.com", "time": "Thu Mar 07 16:24:24 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:52 2013 -0700" }, "message": "USB: Rip out recursive call on warm port reset.\n\n[This is upstream commit 24a6078754f28528bc91e7e7b3e6ae86bd936d8.\nIt needs to be backported to kernels as old as 3.2, because it fixes the\nbuggy commit 9dbcaec830cd97f44a0b91b315844e0d7144746b \"USB: Handle warm\nreset failure on empty port.\"]\n\nWhen a hot reset fails on a USB 3.0 port, the current port reset code\nrecursively calls hub_port_reset inside hub_port_wait_reset. This isn\u0027t\nideal, since we should avoid recursive calls in the kernel, and it also\ndoesn\u0027t allow us to issue multiple warm resets on reset failures.\n\nRip out the recursive call. Instead, add code to hub_port_reset to\nissue a warm reset if the hot reset fails, and try multiple warm resets\nbefore giving up on the port.\n\nIn hub_port_wait_reset, remove the recursive call and re-indent. The\ncode is basically the same, except:\n\n1. It bails out early if the port has transitioned to Inactive or\nCompliance Mode after the reset completed.\n\n2. It doesn\u0027t consider a connect status change to be a failed reset. If\nmultiple warm resets needed to be issued, the connect status may have\nchanged, so we need to ignore that and look at the port link state\ninstead. hub_port_reset will now do that.\n\n3. It unconditionally sets udev-\u003espeed on all types of successful\nresets. The old recursive code would set the port speed when the second\nhub_port_reset returned.\n\nThe old code did not handle connected devices needing a warm reset well.\nThere were only two situations that the old code handled correctly: an\nempty port needing a warm reset, and a hot reset that migrated to a warm\nreset.\n\nWhen an empty port needed a warm reset, hub_port_reset was called with\nthe warm variable set. The code in hub_port_finish_reset would skip\ntelling the USB core and the xHC host that the device was reset, because\notherwise that would result in a NULL pointer dereference.\n\nWhen a USB 3.0 device reset migrated to a warm reset, the recursive call\nmade the call stack look like this:\n\nhub_port_reset(warm \u003d false)\n hub_wait_port_reset(warm \u003d false)\n hub_port_reset(warm \u003d true)\n hub_wait_port_reset(warm \u003d true)\n hub_port_finish_reset(warm \u003d true)\n (return up the call stack to the first wait)\n\n hub_port_finish_reset(warm \u003d false)\n\nThe old code didn\u0027t want to notify the USB core or the xHC host of device reset\ntwice, so it only did it in the second call to hub_port_finish_reset,\nwhen warm was set to false. This was necessary because\nbefore patch two (\"USB: Ignore xHCI Reset Device status.\"), the USB core\nwould pay attention to the xHC Reset Device command error status, and\nthe second call would always fail.\n\nNow that we no longer have the recursive call, and warm can change from\nfalse to true in hub_port_reset, we need to have hub_port_finish_reset\nunconditionally notify the USB core and the xHC of the device reset.\n\nIn hub_port_finish_reset, unconditionally clear the connect status\nchange (CSC) bit for USB 3.0 hubs when the port reset is done. If we\nhad to issue multiple warm resets for a device, that bit may have been\nset if the device went into SS.Inactive and then was successfully warm\nreset.\n\nSigned-off-by: Sarah Sharp \u003csarah.a.sharp@linux.intel.com\u003e\nAcked-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "e850004e595d6322c6b7ccbfe21a4582051ad56b", "tree": "250637573ab5224f068a63723d461ac6d7a7c2ba", "parents": [ "ac79dc9b4a929bd8c0d9e4a2fccd3b7215cbaee4" ], "author": { "name": "Sarah Sharp", "email": "sarah.a.sharp@linux.intel.com", "time": "Thu Mar 07 16:24:22 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "USB: Prepare for refactoring by adding extra udev checks.\n\n[This is upstream commit 2d4fa940f99663c82ba55b2244638833b388e4e2.\nIt needs to be backported to kernels as old as 3.2, because it fixes the\nbuggy commit 9dbcaec830cd97f44a0b91b315844e0d7144746b \"USB: Handle warm\nreset failure on empty port.\"]\n\nThe next patch will refactor the hub port code to rip out the recursive\ncall to hub_port_reset on a failed hot reset. In preparation for that,\nmake sure all code paths can deal with being called with a NULL udev.\nThe usb_device will not be valid if warm reset was issued because a port\ntransitioned to the Inactive or Compliance Mode on a device connect.\n\nThis patch should have no effect on current behavior.\n\nSigned-off-by: Sarah Sharp \u003csarah.a.sharp@linux.intel.com\u003e\nAcked-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ac79dc9b4a929bd8c0d9e4a2fccd3b7215cbaee4", "tree": "a35a070a9f7dfc07f0de6945b0de1442ae032a77", "parents": [ "d2c96b7257048e9a558f2ebe4fe884b51fd9016f" ], "author": { "name": "Sarah Sharp", "email": "sarah.a.sharp@linux.intel.com", "time": "Thu Mar 07 16:24:19 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "USB: Don\u0027t use EHCI port sempahore for USB 3.0 hubs.\n\n[This is upstream commit 0fe51aa5eee51db7c7ecd201d42a977ad79c58b6.\nIt needs to be backported to kernels as old as 3.2, because it fixes the\nbuggy commit 9dbcaec830cd97f44a0b91b315844e0d7144746b \"USB: Handle warm\nreset failure on empty port.\"]\n\nThe EHCI host controller needs to prevent EHCI initialization when the\nUHCI or OHCI companion controller is in the middle of a port reset. It\nuses ehci_cf_port_reset_rwsem to do this. USB 3.0 hubs can\u0027t be under\nan EHCI host controller, so it makes no sense to down the semaphore for\nUSB 3.0 hubs. It also makes the warm port reset code more complex.\n\nDon\u0027t down ehci_cf_port_reset_rwsem for USB 3.0 hubs.\n\nSigned-off-by: Sarah Sharp \u003csarah.a.sharp@linux.intel.com\u003e\nAcked-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d2c96b7257048e9a558f2ebe4fe884b51fd9016f", "tree": "ef4f78def19091c0ece2c45daad02fb99222072a", "parents": [ "abf73cb191a83045c3cc6f46ea78b94439957585" ], "author": { "name": "Ben Hutchings", "email": "ben@decadent.org.uk", "time": "Fri Mar 08 12:43:32 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "dmi_scan: fix missing check for _DMI_ signature in smbios_present()\n\ncommit a40e7cf8f06b4e322ba902e4e9f6a6b0c2daa907 upstream.\n\nCommit 9f9c9cbb6057 (\"drivers/firmware/dmi_scan.c: fetch dmi version\nfrom SMBIOS if it exists\") hoisted the check for \"_DMI_\" into\ndmi_scan_machine(), which means that we don\u0027t bother to check for\n\"_DMI_\" at offset 16 in an SMBIOS entry. smbios_present() may also call\ndmi_present() for an address where we found \"_SM_\", if it failed further\nvalidation.\n\nCheck for \"_DMI_\" in smbios_present() before calling dmi_present().\n\n[akpm@linux-foundation.org: fix build]\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nReported-by: Tim McGrath \u003ctmhikaru@gmail.com\u003e\nTested-by: Tim Mcgrath \u003ctmhikaru@gmail.com\u003e\nCc: Zhenzhong Duan \u003czhenzhong.duan@oracle.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": "abf73cb191a83045c3cc6f46ea78b94439957585", "tree": "cb88f3a2335ab2db1e92601774312115f230d274", "parents": [ "f39e4f133d52fad48f5c823b6c8a867caf101677" ], "author": { "name": "Steven Rostedt", "email": "srostedt@redhat.com", "time": "Wed Feb 27 21:48:09 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "ftrace: Update the kconfig for DYNAMIC_FTRACE\n\ncommit db05021d49a994ee40a9735d9c3cb0060c9babb8 upstream.\n\nThe prompt to enable DYNAMIC_FTRACE (the ability to nop and\nenable function tracing at run time) had a confusing statement:\n\n \"enable/disable ftrace tracepoints dynamically\"\n\nThis was written before tracepoints were added to the kernel,\nbut now that tracepoints have been added, this is very confusing\nand has confused people enough to give wrong information during\npresentations.\n\nNot only that, I looked at the help text, and it still references\nthat dreaded daemon that use to wake up once a second to update\nthe nop locations and brick NICs, that hasn\u0027t been around for over\nfive years.\n\nTime to bring the text up to the current decade.\n\nReported-by: Ezequiel Garcia \u003celezegarcia@gmail.com\u003e\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f39e4f133d52fad48f5c823b6c8a867caf101677", "tree": "11fb57f56fb2444218c217f865350dc375a0a543", "parents": [ "cc6de71e8c24edbad16e45c011013d40eb903ffd" ], "author": { "name": "Tu, Xiaobing", "email": "xiaobing.tu@intel.com", "time": "Tue Oct 23 01:03:00 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "Fix memory leak in cpufreq stats.\n\ncommit e37736777254ce1abc85493a5cacbefe5983b896 upstream.\n\nWhen system enters sleep, non-boot CPUs will be disabled.\nCpufreq stats sysfs is created when the CPU is up, but it is not\nfreed when the CPU is going down. This will cause memory leak.\n\nSigned-off-by: xiaobing tu \u003cxiaobing.tu@intel.com\u003e\nSigned-off-by: guifang tang \u003cguifang.tang@intel.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crafael.j.wysocki@intel.com\u003e\nCc: Colin Cross \u003cccross@google.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cc6de71e8c24edbad16e45c011013d40eb903ffd", "tree": "0679f9de7e5d8b83b8aae72cac37cc9e052f9c78", "parents": [ "3126603e01babcec7cfe2f284099e2adff095bff" ], "author": { "name": "Al Viro", "email": "viro@ZenIV.linux.org.uk", "time": "Tue Mar 12 02:59:49 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "vfs: fix pipe counter breakage\n\ncommit a930d8790552658140d7d0d2e316af4f0d76a512 upstream.\n\nIf you open a pipe for neither read nor write, the pipe code will not\nadd any usage counters to the pipe, causing the \u0027struct pipe_inode_info\"\nto be potentially released early.\n\nThat doesn\u0027t normally matter, since you cannot actually use the pipe,\nbut the pipe release code - particularly fasync handling - still expects\nthe actual pipe infrastructure to all be there. And rather than adding\nNULL pointer checks, let\u0027s just disallow this case, the same way we\nalready do for the named pipe (\"fifo\") case.\n\nThis is ancient going back to pre-2.4 days, and until trinity, nobody\nnaver noticed.\n\nReported-by: Dave Jones \u003cdavej@redhat.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "3126603e01babcec7cfe2f284099e2adff095bff", "tree": "edd0b3fd6d738ef785f4338825b703f1e7fa7db7", "parents": [ "96ace773358d2989ea522a1cdccf65d75c1335f3" ], "author": { "name": "Mathieu Desnoyers", "email": "mathieu.desnoyers@efficios.com", "time": "Mon Feb 25 10:20:36 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "Fix: compat_rw_copy_check_uvector() misuse in aio, readv, writev, and security keys\n\ncommit 8aec0f5d4137532de14e6554fd5dd201ff3a3c49 upstream.\n\nLooking at mm/process_vm_access.c:process_vm_rw() and comparing it to\ncompat_process_vm_rw() shows that the compatibility code requires an\nexplicit \"access_ok()\" check before calling\ncompat_rw_copy_check_uvector(). The same difference seems to appear when\nwe compare fs/read_write.c:do_readv_writev() to\nfs/compat.c:compat_do_readv_writev().\n\nThis subtle difference between the compat and non-compat requirements\nshould probably be debated, as it seems to be error-prone. In fact,\nthere are two others sites that use this function in the Linux kernel,\nand they both seem to get it wrong:\n\nNow shifting our attention to fs/aio.c, we see that aio_setup_iocb()\nalso ends up calling compat_rw_copy_check_uvector() through\naio_setup_vectored_rw(). Unfortunately, the access_ok() check appears to\nbe missing. Same situation for\nsecurity/keys/compat.c:compat_keyctl_instantiate_key_iov().\n\nI propose that we add the access_ok() check directly into\ncompat_rw_copy_check_uvector(), so callers don\u0027t have to worry about it,\nand it therefore makes the compat call code similar to its non-compat\ncounterpart. Place the access_ok() check in the same location where\ncopy_from_user() can trigger a -EFAULT error in the non-compat code, so\nthe ABI behaviors are alike on both compat and non-compat.\n\nWhile we are here, fix compat_do_readv_writev() so it checks for\ncompat_rw_copy_check_uvector() negative return values.\n\nAnd also, fix a memory leak in compat_keyctl_instantiate_key_iov() error\nhandling.\n\nAcked-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nAcked-by: Al Viro \u003cviro@ZenIV.linux.org.uk\u003e\nSigned-off-by: Mathieu Desnoyers \u003cmathieu.desnoyers@efficios.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "96ace773358d2989ea522a1cdccf65d75c1335f3", "tree": "c9b078ec66184fb1d8f59930b3cf48f7b0cdcbe3", "parents": [ "30e39b7c57422b29533a1bf43f2fd921e088a71d" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Tue Mar 12 16:44:31 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:51 2013 -0700" }, "message": "keys: fix race with concurrent install_user_keyrings()\n\ncommit 0da9dfdd2cd9889201bc6f6f43580c99165cd087 upstream.\n\nThis fixes CVE-2013-1792.\n\nThere is a race in install_user_keyrings() that can cause a NULL pointer\ndereference when called concurrently for the same user if the uid and\nuid-session keyrings are not yet created. It might be possible for an\nunprivileged user to trigger this by calling keyctl() from userspace in\nparallel immediately after logging in.\n\nAssume that we have two threads both executing lookup_user_key(), both\nlooking for KEY_SPEC_USER_SESSION_KEYRING.\n\n\tTHREAD A\t\t\tTHREAD B\n\t\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\t\u003d\u003d\u003d\u003d\u003d\u003d\u003d\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\t\t\t\t\t\u003d\u003d\u003ecall install_user_keyrings();\n\tif (!cred-\u003euser-\u003esession_keyring)\n\t\u003d\u003d\u003ecall install_user_keyrings()\n\t\t\t\t\t...\n\t\t\t\t\tuser-\u003euid_keyring \u003d uid_keyring;\n\tif (user-\u003euid_keyring)\n\t\treturn 0;\n\t\u003c\u003d\u003d\n\tkey \u003d cred-\u003euser-\u003esession_keyring [\u003d\u003d NULL]\n\t\t\t\t\tuser-\u003esession_keyring \u003d session_keyring;\n\tatomic_inc(\u0026key-\u003eusage); [oops]\n\nAt the point thread A dereferences cred-\u003euser-\u003esession_keyring, thread B\nhasn\u0027t updated user-\u003esession_keyring yet, but thread A assumes it is\npopulated because install_user_keyrings() returned ok.\n\nThe race window is really small but can be exploited if, for example,\nthread B is interrupted or preempted after initializing uid_keyring, but\nbefore doing setting session_keyring.\n\nThis couldn\u0027t be reproduced on a stock kernel. However, after placing\nsystemtap probe on \u0027user-\u003esession_keyring \u003d session_keyring;\u0027 that\nintroduced some delay, the kernel could be crashed reliably.\n\nFix this by checking both pointers before deciding whether to return.\nAlternatively, the test could be done away with entirely as it is checked\ninside the mutex - but since the mutex is global, that may not be the best\nway.\n\nSigned-off-by: David Howells \u003cdhowells@redhat.com\u003e\nReported-by: Mateusz Guzik \u003cmguzik@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: James Morris \u003cjames.l.morris@oracle.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "30e39b7c57422b29533a1bf43f2fd921e088a71d", "tree": "49dc959d9bb11deb5be1cf30f7e3bc4cd8bc3db1", "parents": [ "76de736ea670500c46e84bff7ae0e040f69d4397" ], "author": { "name": "Mathias Krause", "email": "minipli@googlemail.com", "time": "Tue Feb 05 18:19:13 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "crypto: user - fix info leaks in report API\n\ncommit 9a5467bf7b6e9e02ec9c3da4e23747c05faeaac6 upstream.\n\nThree errors resulting in kernel memory disclosure:\n\n1/ The structures used for the netlink based crypto algorithm report API\nare located on the stack. As snprintf() does not fill the remainder of\nthe buffer with null bytes, those stack bytes will be disclosed to users\nof the API. Switch to strncpy() to fix this.\n\n2/ crypto_report_one() does not initialize all field of struct\ncrypto_user_alg. Fix this to fix the heap info leak.\n\n3/ For the module name we should copy only as many bytes as\nmodule_name() returns -- not as much as the destination buffer could\nhold. But the current code does not and therefore copies random data\nfrom behind the end of the module name, as the module name is always\nshorter than CRYPTO_MAX_ALG_NAME.\n\nAlso switch to use strncpy() to copy the algorithm\u0027s name and\ndriver_name. They are strings, after all.\n\nSigned-off-by: Mathias Krause \u003cminipli@googlemail.com\u003e\nCc: Steffen Klassert \u003csteffen.klassert@secunet.com\u003e\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "76de736ea670500c46e84bff7ae0e040f69d4397", "tree": "c985211c84b8686c11101e06c37a8a00fceeb410", "parents": [ "626614bf45e336d2623c90a812e6bd141e86949e" ], "author": { "name": "Konrad Rzeszutek Wilk", "email": "konrad.wilk@oracle.com", "time": "Tue Feb 26 12:51:27 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "xen/pat: Disable PAT using pat_enabled value.\n\ncommit c79c49826270b8b0061b2fca840fc3f013c8a78a upstream.\n\nThe git commit 8eaffa67b43e99ae581622c5133e20b0f48bcef1\n(xen/pat: Disable PAT support for now) explains in details why\nwe want to disable PAT for right now. However that\nchange was not enough and we should have also disabled\nthe pat_enabled value. Otherwise we end up with:\n\nmmap-example:3481 map pfn expected mapping type write-back for\n[mem 0x00010000-0x00010fff], got uncached-minus\n ------------[ cut here ]------------\nWARNING: at /build/buildd/linux-3.8.0/arch/x86/mm/pat.c:774 untrack_pfn+0xb8/0xd0()\nmem 0x00010000-0x00010fff], got uncached-minus\n------------[ cut here ]------------\nWARNING: at /build/buildd/linux-3.8.0/arch/x86/mm/pat.c:774\nuntrack_pfn+0xb8/0xd0()\n...\nPid: 3481, comm: mmap-example Tainted: GF 3.8.0-6-generic #13-Ubuntu\nCall Trace:\n [\u003cffffffff8105879f\u003e] warn_slowpath_common+0x7f/0xc0\n [\u003cffffffff810587fa\u003e] warn_slowpath_null+0x1a/0x20\n [\u003cffffffff8104bcc8\u003e] untrack_pfn+0xb8/0xd0\n [\u003cffffffff81156c1c\u003e] unmap_single_vma+0xac/0x100\n [\u003cffffffff81157459\u003e] unmap_vmas+0x49/0x90\n [\u003cffffffff8115f808\u003e] exit_mmap+0x98/0x170\n [\u003cffffffff810559a4\u003e] mmput+0x64/0x100\n [\u003cffffffff810560f5\u003e] dup_mm+0x445/0x660\n [\u003cffffffff81056d9f\u003e] copy_process.part.22+0xa5f/0x1510\n [\u003cffffffff81057931\u003e] do_fork+0x91/0x350\n [\u003cffffffff81057c76\u003e] sys_clone+0x16/0x20\n [\u003cffffffff816ccbf9\u003e] stub_clone+0x69/0x90\n [\u003cffffffff816cc89d\u003e] ? system_call_fastpath+0x1a/0x1f\n---[ end trace 4918cdd0a4c9fea4 ]---\n\n(a similar message shows up if you end up launching \u0027mcelog\u0027)\n\nThe call chain is (as analyzed by Liu, Jinsong):\ndo_fork\n --\u003e copy_process\n --\u003e dup_mm\n --\u003e dup_mmap\n \t--\u003e copy_page_range\n --\u003e track_pfn_copy\n --\u003e reserve_pfn_range\n --\u003e line 624: flags !\u003d want_flags\nIt comes from different memory types of page table (_PAGE_CACHE_WB) and MTRR\n(_PAGE_CACHE_UC_MINUS).\n\nStefan Bader dug in this deep and found out that:\n\"That makes it clearer as this will do\n\nreserve_memtype(...)\n--\u003e pat_x_mtrr_type\n --\u003e mtrr_type_lookup\n --\u003e __mtrr_type_lookup\n\nAnd that can return -1/0xff in case of MTRR not being enabled/initialized. Which\nis not the case (given there are no messages for it in dmesg). This is not equal\nto MTRR_TYPE_WRBACK and thus becomes _PAGE_CACHE_UC_MINUS.\n\nIt looks like the problem starts early in reserve_memtype:\n\n \tif (!pat_enabled) {\n /* This is identical to page table setting without PAT */\n if (new_type) {\n if (req_type \u003d\u003d _PAGE_CACHE_WC)\n *new_type \u003d _PAGE_CACHE_UC_MINUS;\n else\n \t*new_type \u003d req_type \u0026 _PAGE_CACHE_MASK;\n \t}\n return 0;\n }\n\nThis would be what we want, that is clearing the PWT and PCD flags from the\nsupported flags - if pat_enabled is disabled.\"\n\nThis patch does that - disabling PAT.\n\nReported-by: Sander Eikelenboom \u003clinux@eikelenboom.it\u003e\nReported-and-Tested-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\nReported-and-Tested-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": "626614bf45e336d2623c90a812e6bd141e86949e", "tree": "890650fe2548e3d1a6ed4db87651221917c49419", "parents": [ "1c48233e2eea4790e4b85b0e8b40537cecdba841" ], "author": { "name": "Benjamin Tissoires", "email": "benjamin.tissoires@redhat.com", "time": "Tue Mar 05 17:09:00 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "HID: logitech-dj: do not directly call hid_output_raw_report() during probe\n\ncommit dcd9006b1b053c7b1cebe81333261d4fd492ffeb upstream.\n\nhid_output_raw_report() makes a direct call to usb_control_msg(). However,\nsome USB3 boards have shown that the usb device is not ready during the\n.probe(). This blocks the entire usb device, and the paired mice, keyboards\nare not functional. The dmesg output is the following:\n\n[ 11.912287] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-2/input2\n[ 11.912537] logitech-djreceiver 0003:046D:C52B.0003: logi_dj_probe:logi_dj_recv_query_paired_devices error:-32\n[ 11.912636] logitech-djreceiver: probe of 0003:046D:C52B.0003 failed with error -32\n\nRelying on the scheduled call to usbhid_submit_report() fixes the problem.\n\nrelated bugs:\nhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072082\nhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039143\nhttps://bugzilla.redhat.com/show_bug.cgi?id\u003d840391\nhttps://bugzilla.kernel.org/show_bug.cgi?id\u003d49781\n\nReported-and-tested-by: Bob Bowles \u003cbobjohnbowles@gmail.com\u003e\nSigned-off-by: Benjamin Tissoires \u003cbenjamin.tissoires@redhat.com\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1c48233e2eea4790e4b85b0e8b40537cecdba841", "tree": "c3dc35acdad304af9b21459ba569894fcb985770", "parents": [ "f4ec9b23b178caab8e4ecc8b4a4c3531211411a9" ], "author": { "name": "Konstantin Khlebnikov", "email": "khlebnikov@openvz.org", "time": "Tue Mar 05 09:42:59 2013 +0000" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "e1000e: fix pci-device enable-counter balance\n\ncommit 4e0855dff094b0d56d6b5b271e0ce7851cc1e063 upstream.\n\nThis patch removes redundant and unbalanced pci_disable_device() from\n__e1000_shutdown(). pci_clear_master() is enough, device can go into\nsuspended state with elevated enable_cnt.\n\nBug was introduced in commit 23606cf5d1192c2b17912cb2ef6e62f9b11de133\n(\"e1000e / PCI / PM: Add basic runtime PM support (rev. 4)\") in v2.6.35\n\nSigned-off-by: Konstantin Khlebnikov \u003ckhlebnikov@openvz.org\u003e\nCc: Bruce Allan \u003cbruce.w.allan@intel.com\u003e\nAcked-by: Rafael J. Wysocki \u003crafael.j.wysocki@intel.com\u003e\nTested-by: Borislav Petkov \u003cbp@suse.de\u003e\nTested-by: Aaron Brown \u003caaron.f.brown@intel.com\u003e\nSigned-off-by: Jeff Kirsher \u003cjeffrey.t.kirsher@intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f4ec9b23b178caab8e4ecc8b4a4c3531211411a9", "tree": "7dd92517801633d10b7f51c563b51b5d6c0a7ba2", "parents": [ "1515f18665088e33e35706bd35268a16e8e7665d" ], "author": { "name": "Takashi Iwai", "email": "tiwai@suse.de", "time": "Tue Mar 05 15:43:39 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "ALSA: vmaster: Fix slave change notification\n\ncommit 2069d483b39a603a5f3428a19d3b4ac89aa97f48 upstream.\n\nWhen a value of a vmaster slave control is changed, the ctl change\nnotification is sometimes ignored. This happens when the master\ncontrol overrides, e.g. when the corresponding master control is\nmuted. The reason is that slave_put() returns the value of the actual\nslave put callback, and it doesn\u0027t reflect the virtual slave value\nchange.\n\nThis patch fixes the function just to return 1 whenever a slave value\nis changed.\n\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1515f18665088e33e35706bd35268a16e8e7665d", "tree": "cb54a188347e40c805429826ae1b4fcb726fddd0", "parents": [ "724285cf2c0ef53c2217a6a866ab50d57c386292" ], "author": { "name": "Sean Connor", "email": "sconnor004@allyinics.org", "time": "Thu Feb 28 09:20:00 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "ALSA: ice1712: Initialize card-\u003eprivate_data properly\n\ncommit 69a4cfdd444d1fe5c24d29b3a063964ac165d2cd upstream.\n\nSet card-\u003eprivate_data in snd_ice1712_create for fixing NULL\ndereference in snd_ice1712_remove().\n\nSigned-off-by: Sean Connor \u003csconnor004@allyinics.org\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "724285cf2c0ef53c2217a6a866ab50d57c386292", "tree": "e43d0833c284196ace7af1ed7b42d80ce1c6316d", "parents": [ "b08994da73be68f17f82a522f4f129c18dbbf77f" ], "author": { "name": "Will Deacon", "email": "will.deacon@arm.com", "time": "Thu Feb 28 17:49:11 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:50 2013 -0700" }, "message": "ARM: 7663/1: perf: fix ARMv7 EVTYPE_MASK to include NSH bit\n\ncommit f2fe09b055e2549de41fb107b34c60bac4a1b0cf upstream.\n\nMasked out PMXEVTYPER.NSH means that we can\u0027t enable profiling at PL2,\nregardless of the settings in the HDCR.\n\nThis patch fixes the broken mask.\n\nReported-by: Christoffer Dall \u003ccdall@cs.columbia.edu\u003e\nSigned-off-by: Will Deacon \u003cwill.deacon@arm.com\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "b08994da73be68f17f82a522f4f129c18dbbf77f", "tree": "9ef4f61a17637eeb435862bb6e11b32e8fb3395a", "parents": [ "bc37694dbaf8604619228ccc6e34528182b3a987" ], "author": { "name": "Alex Deucher", "email": "alexander.deucher@amd.com", "time": "Wed Feb 27 12:01:58 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "drm/radeon: add primary dac adj quirk for R200 board\n\ncommit e8fc41377f5037ff7a661ea06adc05f1daec1548 upstream.\n\nvbios values are wrong leading to colors that are\ntoo bright. Use the default values instead.\n\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "bc37694dbaf8604619228ccc6e34528182b3a987", "tree": "1628db2c9b0630899717a786060804de8b643fa7", "parents": [ "ec2bc2f65c469aa5d0a1eb21f8404e0e3114bde4" ], "author": { "name": "Guenter Roeck", "email": "linux@roeck-us.net", "time": "Thu Feb 21 10:49:40 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "hwmon: (pmbus/ltc2978) Use detected chip ID to select supported functionality\n\ncommit f366fccd0809f13ba20d64cae3c83f7338c88af7 upstream.\n\nWe read the chip ID from the chip, use it to determine if the chip ID provided\nto the driver is correct, and report it if wrong. We should also use the\ncorrect chip ID to select supported functionality.\n\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nAcked-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "ec2bc2f65c469aa5d0a1eb21f8404e0e3114bde4", "tree": "2bce7b7a154e6bff7e658e62e4d1668106f70218", "parents": [ "cca30bd4c94123776dc3620cd13c6aedb76e4b55" ], "author": { "name": "Guenter Roeck", "email": "linux@roeck-us.net", "time": "Thu Feb 21 09:33:25 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "hwmon: (pmbus/ltc2978) Fix peak attribute handling\n\ncommit dbd712c2272764a536e29ad6841dba74989a39d9 upstream.\n\nPeak attributes were not initialized and cleared correctly.\nAlso, temp2_max is only supported on page 0 and thus does not need to be\nan array.\n\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nAcked-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "cca30bd4c94123776dc3620cd13c6aedb76e4b55", "tree": "ccd84ecbb358e3203b3b417b4dcec1a1695a6ae9", "parents": [ "fbad8075baa695da5da4952969682172966a4fac" ], "author": { "name": "Mark Brown", "email": "broonie@opensource.wolfsonmicro.com", "time": "Sat Mar 02 15:33:30 2013 +0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "hwmon: (sht15) Check return value of regulator_enable()\n\ncommit 3e78080f81481aa8340374d5a37ae033c1cf4272 upstream.\n\nNot having power is a pretty serious error so check that we are able to\nenable the supply and error out if we can\u0027t.\n\nSigned-off-by: Mark Brown \u003cbroonie@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\n\n" }, { "commit": "fbad8075baa695da5da4952969682172966a4fac", "tree": "4de9c4b8a6363687a93b79d9a3ee342b3d75b831", "parents": [ "c443082d1998879713ecf9f97ee4ba8c76f8b7f0" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Feb 21 15:36:38 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "md: raid0: fix error return from create_stripe_zones.\n\ncommit 58ebb34c49fcfcaa029e4b1c1453d92583900f9a upstream.\n\nCreate_stripe_zones returns an error slightly differently to\nraid0_run and to raid0_takeover_*.\n\nThe error returned used by the second was wrong and an error would\nresult in mddev-\u003eprivate being set to NULL and sooner or later a\ncrash.\n\nSo never return NULL, return ERR_PTR(err), not NULL from\ncreate_stripe_zones.\n\nThis bug has been present since 2.6.35 so the fix is suitable\nfor any kernel since then.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "c443082d1998879713ecf9f97ee4ba8c76f8b7f0", "tree": "37f83d7390c5b3abc206ee45a5d327cb9b5ce5bb", "parents": [ "517557f2323d11a1a355e9c9155a1e315d87d487" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Feb 21 14:33:17 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:49 2013 -0700" }, "message": "md: fix two bugs when attempting to resize RAID0 array.\n\ncommit a64685399181780998281fe07309a94b25dd24c3 upstream.\n\nYou cannot resize a RAID0 array (in terms of making the devices\nbigger), but the code doesn\u0027t entirely stop you.\nSo:\n\n disable setting of the available size on each device for\n RAID0 and Linear devices. This must not change as doing so\n can change the effective layout of data.\n\n Make sure that the size that raid0_size() reports is accurate,\n but rounding devices sizes to chunk sizes. As the device sizes\n cannot change now, this isn\u0027t so important, but it is best to be\n safe.\n\nWithout this change:\n mdadm --grow /dev/md0 -z max\n mdadm --grow /dev/md0 -Z max\n then read to the end of the array\n\ncan cause a BUG in a RAID0 array.\n\nThese bugs have been present ever since it became possible\nto resize any device, which is a long time. So the fix is\nsuitable for any -stable kerenl.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "517557f2323d11a1a355e9c9155a1e315d87d487", "tree": "8809012bed39c1ba189e248a8f9aba3185c45c91", "parents": [ "f9c89dac69cb99c00d4c273cad43f466fb9a1c8b" ], "author": { "name": "Sebastian Riemer", "email": "sebastian.riemer@profitbricks.com", "time": "Thu Feb 21 13:28:09 2013 +1100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:48 2013 -0700" }, "message": "md: protect against crash upon fsync on ro array\n\ncommit bbfa57c0f2243a7c31fd248d22e9861a2802cad5 upstream.\n\nIf an fsync occurs on a read-only array, we need to send a\ncompletion for the IO and may not increment the active IO count.\nOtherwise, we hit a bug trace and can\u0027t stop the MD array anymore.\n\nBy advice of Christoph Hellwig we return success upon a flush\nrequest but we return -EROFS for other writes.\nWe detect flush requests by checking if the bio has zero sectors.\n\nThis patch is suitable to any -stable kernel to which it applies.\n\nSigned-off-by: Sebastian Riemer \u003csebastian.riemer@profitbricks.com\u003e\nCc: Christoph Hellwig \u003chch@infradead.org\u003e\nCc: Ben Hutchings \u003cben@decadent.org.uk\u003e\nCc: NeilBrown \u003cneilb@suse.de\u003e\nReported-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nAcked-by: Paul Menzel \u003cpaulepanter@users.sourceforge.net\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "f9c89dac69cb99c00d4c273cad43f466fb9a1c8b", "tree": "49e3ea411e482407ad92c211ed416725291e45e9", "parents": [ "34127f32d576cb64717afade55c6fcff6b062451" ], "author": { "name": "Felix Fietkau", "email": "nbd@openwrt.org", "time": "Mon Feb 25 20:51:07 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:43 2013 -0700" }, "message": "ath9k_hw: improve reset reliability after errors\n\ncommit 3412f2f086ea7531378fabe756bd4a1109994ae6 upstream.\n\nOn many different chips, important aspects of the MAC state are not\nfully cleared by a warm reset. This can show up as tx/rx hangs, those\nannoying \"DMA failed to stop in 10 ms...\" messages or other quirks.\n\nOn AR933x, the chip can occasionally get stuck in a way that only a\ndriver unload/reload or a reboot would bring it back to life.\n\nWith this patch, a full reset is issued when bringing the chip out of\nFULL-SLEEP state (after idle), or if either Rx or Tx was not shut down\nproperly. This makes the DMA related error messages disappear completely\nin my tests on AR933x, and the chip does not get stuck anymore.\n\nSigned-off-by: Felix Fietkau \u003cnbd@openwrt.org\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "34127f32d576cb64717afade55c6fcff6b062451", "tree": "9d24c07e748d6430bef2aa6af300a20d5845e859", "parents": [ "97cf710a238290b049f1f09dd220ca2f813d5fb9" ], "author": { "name": "Felix Fietkau", "email": "nbd@openwrt.org", "time": "Fri Feb 22 21:09:17 2013 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:43 2013 -0700" }, "message": "ath9k: fix RSSI dummy marker value\n\ncommit a3d63cadbad97671d740a9698acc2c95d1ca6e79 upstream.\n\nRSSI is being stored internally as s8 in several places. The indication\nof an unset RSSI value, ATH_RSSI_DUMMY_MARKER, was supposed to have been\nset to 127, but ended up being set to 0x127 because of a code cleanup\nmistake. This could lead to invalid signal strength values in a few\nplaces.\n\nSigned-off-by: Felix Fietkau \u003cnbd@openwrt.org\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "97cf710a238290b049f1f09dd220ca2f813d5fb9", "tree": "d6fbd5b02e7672710c5d94cb792d805f14a44932", "parents": [ "681e3b15fef858a9512d5fb2baceb85b0913385f" ], "author": { "name": "Avinash Patil", "email": "patila@marvell.com", "time": "Mon Feb 25 16:01:34 2013 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:43 2013 -0700" }, "message": "mwifiex: correct sleep delay counter\n\ncommit 3e7a4ff7c5b6423ddb644df9c41b8b6d2fb79d30 upstream.\n\nMaximum delay for waking up card is 50 ms. Because of typo in\ncounter, this delay goes to 500ms. This patch fixes the bug.\n\nSigned-off-by: Avinash Patil \u003cpatila@marvell.com\u003e\nSigned-off-by: Amitkumar Karwar \u003cakarwar@marvell.com\u003e\nSigned-off-by: Yogesh Ashok Powar \u003cyogeshp@marvell.com\u003e\nSigned-off-by: Bing Zhao \u003cbzhao@marvell.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": "681e3b15fef858a9512d5fb2baceb85b0913385f", "tree": "305a75805b006c16e5ced9bd6a356fb32607ca87", "parents": [ "7ae6c92933a962e3ff8b3999f88b5c7c86841b7f" ], "author": { "name": "Rusty Russell", "email": "rusty@rustcorp.com.au", "time": "Tue Mar 05 10:07:08 2013 +1030" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "hw_random: make buffer usable in scatterlist.\n\ncommit f7f154f1246ccc5a0a7e9ce50932627d60a0c878 upstream.\n\nvirtio_rng feeds the randomness buffer handed by the core directly\ninto the scatterlist, since commit bb347d98079a547e80bd4722dee1de61e4dca0e8.\n\nHowever, if CONFIG_HW_RANDOM\u003dm, the static buffer isn\u0027t a linear address\n(at least on most archs). We could fix this in virtio_rng, but it\u0027s actually\nfar easier to just do it in the core as virtio_rng would have to allocate\na buffer every time (it doesn\u0027t know how much the core will want to read).\n\nReported-by: Aurelien Jarno \u003caurelien@aurel32.net\u003e\nTested-by: Aurelien Jarno \u003caurelien@aurel32.net\u003e\nSigned-off-by: Rusty Russell \u003crusty@rustcorp.com.au\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "7ae6c92933a962e3ff8b3999f88b5c7c86841b7f", "tree": "f5e3b5a652bfc743f25fa3c7814e27a4b72c183a", "parents": [ "1ecb6934fa86281d26d60d984f0e0e6554531813" ], "author": { "name": "Olaf Hering", "email": "olaf@aepfle.de", "time": "Tue Sep 18 17:48:01 2012 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "ata_piix: reenable MS Virtual PC guests\n\ncommit d9904344fc4052fbe7e4dc137eba0dcdadf326bd upstream.\n\nAn earlier commit cd006086fa5d91414d8ff9ff2b78fbb593878e3c (\"ata_piix:\ndefer disks to the Hyper-V drivers by default\") broke MS Virtual PC\nguests. Hyper-V guests and Virtual PC guests have nearly identical DMI\ninfo. As a result the driver does currently ignore the emulated hardware\nin Virtual PC guests and defers the handling to hv_blkvsc. Since Virtual\nPC does not offer paravirtualized drivers no disks will be found in the\nguest.\n\nOne difference in the DMI info is the product version. This patch adds a\nmatch for MS Virtual PC 2007 and \"unignores\" the emulated hardware.\n\nThis was reported for openSuSE 12.1 in bugzilla:\nhttps://bugzilla.novell.com/show_bug.cgi?id\u003d737532\n\nHere is a detailed list of DMI info from example guests:\n\nhwinfo --bios:\n\nvirtual pc guest:\n\n System Info: #1\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"VS2005R2\"\n Serial: \"3178-9905-1533-4840-9282-0569-59\"\n UUID: undefined, but settable\n Wake-up: 0x06 (Power Switch)\n Board Info: #2\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"5.0\"\n Serial: \"3178-9905-1533-4840-9282-0569-59\"\n Chassis Info: #3\n Manufacturer: \"Microsoft Corporation\"\n Version: \"5.0\"\n Serial: \"3178-9905-1533-4840-9282-0569-59\"\n Asset Tag: \"7188-3705-6309-9738-9645-0364-00\"\n Type: 0x03 (Desktop)\n Bootup State: 0x03 (Safe)\n Power Supply State: 0x03 (Safe)\n Thermal State: 0x01 (Other)\n Security Status: 0x01 (Other)\n\nwin2k8 guest:\n\n System Info: #1\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"7.0\"\n Serial: \"9106-3420-9819-5495-1514-2075-48\"\n UUID: undefined, but settable\n Wake-up: 0x06 (Power Switch)\n Board Info: #2\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"7.0\"\n Serial: \"9106-3420-9819-5495-1514-2075-48\"\n Chassis Info: #3\n Manufacturer: \"Microsoft Corporation\"\n Version: \"7.0\"\n Serial: \"9106-3420-9819-5495-1514-2075-48\"\n Asset Tag: \"7076-9522-6699-1042-9501-1785-77\"\n Type: 0x03 (Desktop)\n Bootup State: 0x03 (Safe)\n Power Supply State: 0x03 (Safe)\n Thermal State: 0x01 (Other)\n Security Status: 0x01 (Other)\n\nwin2k12 guest:\n\n System Info: #1\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"7.0\"\n Serial: \"8179-1954-0187-0085-3868-2270-14\"\n UUID: undefined, but settable\n Wake-up: 0x06 (Power Switch)\n Board Info: #2\n Manufacturer: \"Microsoft Corporation\"\n Product: \"Virtual Machine\"\n Version: \"7.0\"\n Serial: \"8179-1954-0187-0085-3868-2270-14\"\n Chassis Info: #3\n Manufacturer: \"Microsoft Corporation\"\n Version: \"7.0\"\n Serial: \"8179-1954-0187-0085-3868-2270-14\"\n Asset Tag: \"8374-0485-4557-6331-0620-5845-25\"\n Type: 0x03 (Desktop)\n Bootup State: 0x03 (Safe)\n Power Supply State: 0x03 (Safe)\n Thermal State: 0x01 (Other)\n Security Status: 0x01 (Other)\n\nSigned-off-by: Olaf Hering \u003colaf@aepfle.de\u003e\nSigned-off-by: Jeff Garzik \u003cjgarzik@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "1ecb6934fa86281d26d60d984f0e0e6554531813", "tree": "7189db0c2e263bba7e36a27e0079d4cbb0993e7e", "parents": [ "d3e8a1806bb6a9f2b4d56de44a87efc18e3e82fd" ], "author": { "name": "Trond Myklebust", "email": "Trond.Myklebust@netapp.com", "time": "Fri Feb 22 14:57:57 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "SUNRPC: Don\u0027t start the retransmission timer when out of socket space\n\ncommit a9a6b52ee1baa865283a91eb8d443ee91adfca56 upstream.\n\nIf the socket is full, we\u0027re better off just waiting until it empties,\nor until the connection is broken. The reason why we generally don\u0027t\nwant to time out is that the call to xprt-\u003eops-\u003erelease_xprt() will\ntrigger a connection reset, which isn\u0027t helpful...\n\nLet\u0027s make an exception for soft RPC calls, since they have to provide\ntimeout guarantees.\n\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" }, { "commit": "d3e8a1806bb6a9f2b4d56de44a87efc18e3e82fd", "tree": "5957d80e189d2fc088f68f9566febe75d147fec0", "parents": [ "18d2c795ad10c2834518b083e3c6a58400f46a1a" ], "author": { "name": "Trond Myklebust", "email": "Trond.Myklebust@netapp.com", "time": "Fri Feb 22 12:53:43 2013 -0500" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@linuxfoundation.org", "time": "Thu Mar 14 11:29:42 2013 -0700" }, "message": "NFS: Don\u0027t allow NFS silly-renamed files to be deleted, no signal\n\ncommit 5a7a613a47a715711b3f2d3322a0eac21d459166 upstream.\n\nCommit 73ca100 broke the code that prevents the client from deleting\na silly renamed dentry. This affected \"delete on last close\"\nsemantics as after that commit, nothing prevented removal of\nsilly-renamed files. As a result, a process holding a file open\ncould easily get an ESTALE on the file in a directory where some\nother process issued \u0027rm -rf some_dir_containing_the_file\u0027 twice.\nBefore the commit, any attempt at unlinking silly renamed files would\nfail inside may_delete() with -EBUSY because of the\nDCACHE_NFSFS_RENAMED flag. The following testcase demonstrates\nthe problem:\n tail -f /nfsmnt/dir/file \u0026\n rm -rf /nfsmnt/dir\n rm -rf /nfsmnt/dir\n # second removal does not fail, \u0027tail\u0027 process receives ESTALE\n\nThe problem with the above commit is that it unhashes the old and\nnew dentries from the lookup path, even in the normal case when\na signal is not encountered and it would have been safe to call\nd_move. Unfortunately the old dentry has the special\nDCACHE_NFSFS_RENAMED flag set on it. Unhashing has the\nside-effect that future lookups call d_alloc(), allocating a new\ndentry without the special flag for any silly-renamed files. As a\nresult, subsequent calls to unlink silly renamed files do not fail\nbut allow the removal to go through. This will result in ESTALE\nerrors for any other process doing operations on the file.\n\nTo fix this, go back to using d_move on success.\nFor the signal case, it\u0027s unclear what we may safely do beyond d_drop.\n\nReported-by: Dave Wysochanski \u003cdwysocha@redhat.com\u003e\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\nAcked-by: Jeff Layton \u003cjlayton@redhat.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n" } ], "next": "18d2c795ad10c2834518b083e3c6a58400f46a1a" }