)]}' { "log": [ { "commit": "fed13a083c6d2d3859518fc07ac9728047deebb9", "tree": "eb1a3954f2b3e866da6796f58b9a3a1dfbcbf8d9", "parents": [ "ac1adeabeaa094672b95b341fbaeb17fef3809ce" ], "author": { "name": "Claudio Cappelli", "email": "claudio.cappelli.linux@gmail.com", "time": "Wed Jun 10 20:38:30 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:42 2016 +0800" }, "message": "USB: option: add 2020:4000 ID\n\ncommit f6d7fb37f92622479ef6da604f27561f5045ba1e upstream.\n\nAdd device Olivetti Olicard 300 (Network Connect: MT6225) - IDs 2020:4000.\n\nT: Bus\u003d01 Lev\u003d02 Prnt\u003d04 Port\u003d00 Cnt\u003d01 Dev#\u003d 10 Spd\u003d480 MxCh\u003d 0\nD: Ver\u003d 2.00 Cls\u003def(misc ) Sub\u003d02 Prot\u003d01 MxPS\u003d64 #Cfgs\u003d 1\nP: Vendor\u003d2020 ProdID\u003d4000 Rev\u003d03.00\nS: Manufacturer\u003dNetwork Connect\nS: Product\u003dMT6225\nC: #Ifs\u003d 7 Cfg#\u003d 1 Atr\u003da0 MxPwr\u003d500mA\nI: If#\u003d 0 Alt\u003d 0 #EPs\u003d 1 Cls\u003d02(commc) Sub\u003d0e Prot\u003d00 Driver\u003dcdc_mbim\nI: If#\u003d 1 Alt\u003d 1 #EPs\u003d 2 Cls\u003d0a(data ) Sub\u003d00 Prot\u003d02 Driver\u003dcdc_mbim\nI: If#\u003d 2 Alt\u003d 0 #EPs\u003d 3 Cls\u003dff(vend.) Sub\u003d02 Prot\u003d01 Driver\u003doption\nI: If#\u003d 3 Alt\u003d 0 #EPs\u003d 2 Cls\u003dff(vend.) Sub\u003d00 Prot\u003d00 Driver\u003doption\nI: If#\u003d 4 Alt\u003d 0 #EPs\u003d 2 Cls\u003dff(vend.) Sub\u003d00 Prot\u003d00 Driver\u003doption\nI: If#\u003d 5 Alt\u003d 0 #EPs\u003d 2 Cls\u003dff(vend.) Sub\u003d00 Prot\u003d00 Driver\u003doption\nI: If#\u003d 6 Alt\u003d 0 #EPs\u003d 2 Cls\u003d08(stor.) Sub\u003d06 Prot\u003d50 Driver\u003dusb-storage\n\nSigned-off-by: Claudio Cappelli \u003cclaudio.cappelli.linux@gmail.com\u003e\nSuggested-by: Lars Melin \u003clarsm17@gmail.com\u003e\n[johan: amend commit message with devices info ]\nSigned-off-by: Johan Hovold \u003cjohan@kernel.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "ac1adeabeaa094672b95b341fbaeb17fef3809ce", "tree": "56d875fad73d3064e1d974cbb91f76b829fa2897", "parents": [ "9b733904f33edc0245486e64e76fe3540ddc9342" ], "author": { "name": "Joe Thornber", "email": "ejt@redhat.com", "time": "Fri Jul 03 10:22:42 2015 +0100" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:41 2016 +0800" }, "message": "dm thin: allocate the cell_sort_array dynamically\n\ncommit a822c83e47d97cdef38c4352e1ef62d9f46cfe98 upstream.\n\nGiven the pool\u0027s cell_sort_array holds 8192 pointers it triggers an\norder 5 allocation via kmalloc. This order 5 allocation is prone to\nfailure as system memory gets more fragmented over time.\n\nFix this by allocating the cell_sort_array using vmalloc.\n\nSigned-off-by: Joe Thornber \u003cejt@redhat.com\u003e\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\n[lizf: Backported 3.4: it\u0027s prinson_{create,destroy}() that need fixing]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "9b733904f33edc0245486e64e76fe3540ddc9342", "tree": "38a69a26cb3730fb55dc8c30b72421719f36f12e", "parents": [ "0fa41525bd0b893f48117457759a6f575c041044" ], "author": { "name": "Dennis Yang", "email": "shinrairis@gmail.com", "time": "Fri Jun 26 15:25:48 2015 +0100" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:41 2016 +0800" }, "message": "dm btree remove: fix bug in redistribute3\n\ncommit 4c7e309340ff85072e96f529582d159002c36734 upstream.\n\nredistribute3() shares entries out across 3 nodes. Some entries were\nbeing moved the wrong way, breaking the ordering. This manifested as a\nBUG() in dm-btree-remove.c:shift() when entries were removed from the\nbtree.\n\nFor additional context see:\nhttps://www.redhat.com/archives/dm-devel/2015-May/msg00113.html\n\nSigned-off-by: Dennis Yang \u003cshinrairis@gmail.com\u003e\nSigned-off-by: Joe Thornber \u003cejt@redhat.com\u003e\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "0fa41525bd0b893f48117457759a6f575c041044", "tree": "8b3fcce0234b96c10a466b16c916df2639ebb311", "parents": [ "1247d2434a3e0d1a64905ff1d0b5e6c158a56242" ], "author": { "name": "Dominic Sacré", "email": "dominic.sacre@gmx.de", "time": "Tue Jun 30 17:41:33 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:41 2016 +0800" }, "message": "ALSA: usb-audio: Add MIDI support for Steinberg MI2/MI4\n\ncommit 0689a86ae814f39af94a9736a0a5426dd82eb107 upstream.\n\nThe Steinberg MI2 and MI4 interfaces are compatible with the USB class\naudio spec, but the MIDI part of the devices is reported as a vendor\nspecific interface.\n\nThis patch adds entries to quirks-table.h to recognize the MIDI\nendpoints. Audio functionality was already working and is unaffected by\nthis change.\n\nSigned-off-by: Dominic Sacré \u003cdominic.sacre@gmx.de\u003e\nSigned-off-by: Albert Huitsing \u003calbert@huitsing.nl\u003e\nAcked-by: Clemens Ladisch \u003cclemens@ladisch.de\u003e\nSigned-off-by: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "1247d2434a3e0d1a64905ff1d0b5e6c158a56242", "tree": "427b8fe09e3a39269e08aaf22ac0a4e51d2328cb", "parents": [ "580fc1504f13683d46bbab083a286f227862f6ed" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Sun Jul 12 10:34:29 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:41 2016 +0800" }, "message": "9p: don\u0027t leave a half-initialized inode sitting around\n\ncommit 0a73d0a204a4a04a1e110539c5a524ae51f91d6d upstream.\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "580fc1504f13683d46bbab083a286f227862f6ed", "tree": "5e6e51235e5e08d0155f5d93de0e5b64db0206ce", "parents": [ "0a4cdc47f96f44c55cfa5a80ff383db2304dd734" ], "author": { "name": "Joe Perches", "email": "joe@perches.com", "time": "Thu Mar 26 20:47:10 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:41 2016 +0800" }, "message": "hpfs: hpfs_error: Remove static buffer, use vsprintf extension %pV instead\n\ncommit a28e4b2b18ccb90df402da3f21e1a83c9d4f8ec1 upstream.\n\nRemoving unnecessary static buffers is good.\nUse the vsprintf %pV extension instead.\n\nSigned-off-by: Joe Perches \u003cjoe@perches.com\u003e\nSigned-off-by: Mikulas Patocka \u003cmikulas@twibright.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n[Mikulas:\n - The bug corrected by the patch is - if hpfs_error is called concurrently\n on multiple filesystems, it could corrupt the string because the text\n buffer is shared. That\u0027s why I marked the patch for stable.]\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "0a4cdc47f96f44c55cfa5a80ff383db2304dd734", "tree": "4910099e1cdff38182b956a8a05349d6ce7a8fc3", "parents": [ "bb09c8d93f6bcd5983d3e51df0acb1473ef799ab" ], "author": { "name": "Sanidhya Kashyap", "email": "sanidhya.gatech@gmail.com", "time": "Sat Mar 21 12:57:50 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:40 2016 +0800" }, "message": "hpfs: kstrdup() out of memory handling\n\ncommit ce657611baf902f14ae559ce4e0787ead6712067 upstream.\n\nThere is a possibility of nothing being allocated to the new_opts in\ncase of memory pressure, therefore return ENOMEM for such case.\n\nSigned-off-by: Sanidhya Kashyap \u003csanidhya.gatech@gmail.com\u003e\nSigned-off-by: Mikulas Patocka \u003cmikulas@twibright.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "bb09c8d93f6bcd5983d3e51df0acb1473ef799ab", "tree": "14e0c6044cb2827b25c80af23c80a8365d39c0d9", "parents": [ "cfba310a0369d8d5e9b7c3718c749836021ee4e2" ], "author": { "name": "Kirill A. Shutemov", "email": "kirill.shutemov@linux.intel.com", "time": "Mon Jul 06 23:18:37 2015 +0300" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:40 2016 +0800" }, "message": "mm: avoid setting up anonymous pages into file mapping\n\ncommit 6b7339f4c31ad69c8e9c0b2859276e22cf72176d upstream.\n\nReading page fault handler code I\u0027ve noticed that under right\ncircumstances kernel would map anonymous pages into file mappings: if\nthe VMA doesn\u0027t have vm_ops-\u003efault() and the VMA wasn\u0027t fully populated\non -\u003emmap(), kernel would handle page fault to not populated pte with\ndo_anonymous_page().\n\nLet\u0027s change page fault handler to use do_anonymous_page() only on\nanonymous VMA (-\u003evm_ops \u003d\u003d NULL) and make sure that the VMA is not\nshared.\n\nFor file mappings without vm_ops-\u003efault() or shred VMA without vm_ops,\npage fault on pte_none() entry would lead to SIGBUS.\n\nSigned-off-by: Kirill A. Shutemov \u003ckirill.shutemov@linux.intel.com\u003e\nAcked-by: Oleg Nesterov \u003coleg@redhat.com\u003e\nCc: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nCc: Willy Tarreau \u003cw@1wt.eu\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "cfba310a0369d8d5e9b7c3718c749836021ee4e2", "tree": "3eb74c254f4e81c38ecbd0e8b58a168a61170f25", "parents": [ "1ceff7efd3cb0c854ad38b335bf1cf49e25e901a" ], "author": { "name": "Michal Hocko", "email": "mhocko@suse.cz", "time": "Sun Jul 05 12:33:44 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:40 2016 +0800" }, "message": "ext4: replace open coded nofail allocation in ext4_free_blocks()\n\ncommit 7444a072c387a93ebee7066e8aee776954ab0e41 upstream.\n\next4_free_blocks is looping around the allocation request and mimics\n__GFP_NOFAIL behavior without any allocation fallback strategy. Let\u0027s\nremove the open coded loop and replace it with __GFP_NOFAIL. Without the\nflag the allocator has no way to find out never-fail requirement and\ncannot help in any way.\n\nSigned-off-by: Michal Hocko \u003cmhocko@suse.cz\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "1ceff7efd3cb0c854ad38b335bf1cf49e25e901a", "tree": "46f66e9fd6899068ac3bce7eb4a1fcbf1f668578", "parents": [ "e47e85894f5db4049982296a46526a2aab78fd51" ], "author": { "name": "Nikolay Borisov", "email": "kernel@kyup.com", "time": "Thu Jul 02 01:34:07 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:40 2016 +0800" }, "message": "ext4: avoid deadlocks in the writeback path by using sb_getblk_gfp\n\ncommit c45653c341f5c8a0ce19c8f0ad4678640849cb86 upstream.\n\nSwitch ext4 to using sb_getblk_gfp with GFP_NOFS added to fix possible\ndeadlocks in the page writeback path.\n\nSigned-off-by: Nikolay Borisov \u003ckernel@kyup.com\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "e47e85894f5db4049982296a46526a2aab78fd51", "tree": "dda302bb17a28711cda5b14ace930aa6eaffa826", "parents": [ "9810a13f3e3fe2ba25fcd1fb6a8bd06e752998c2" ], "author": { "name": "Nikolay Borisov", "email": "kernel@kyup.com", "time": "Thu Jul 02 01:32:44 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:40 2016 +0800" }, "message": "bufferhead: Add _gfp version for sb_getblk()\n\ncommit bd7ade3cd9b0850264306f5c2b79024a417b6396 upstream.\n\nsb_getblk() is used during ext4 (and possibly other FSes) writeback\npaths. Sometimes such path require allocating memory and guaranteeing\nthat such allocation won\u0027t block. Currently, however, there is no way\nto provide user flags for sb_getblk which could lead to deadlocks.\n\nThis patch implements a sb_getblk_gfp with the only difference it can\naccept user-provided GFP flags.\n\nSigned-off-by: Nikolay Borisov \u003ckernel@kyup.com\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "9810a13f3e3fe2ba25fcd1fb6a8bd06e752998c2", "tree": "5aed0c07e063d6fda3def6f35363666d8a5b520c", "parents": [ "38464cd9b38b43ef757da18bc8b9badcd2b70dfb" ], "author": { "name": "Gioh Kim", "email": "gioh.kim@lge.com", "time": "Thu Sep 04 22:04:42 2014 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:39 2016 +0800" }, "message": "fs/buffer.c: support buffer cache allocations with gfp modifiers\n\ncommit 3b5e6454aaf6b4439b19400d8365e2ec2d24e411 upstream.\n\nA buffer cache is allocated from movable area because it is referred\nfor a while and released soon. But some filesystems are taking buffer\ncache for a long time and it can disturb page migration.\n\nNew APIs are introduced to allocate buffer cache with user specific\nflag. *_gfp APIs are for user want to set page allocation flag for\npage cache allocation. And *_unmovable APIs are for the user wants to\nallocate page cache from non-movable area.\n\nSigned-off-by: Gioh Kim \u003cgioh.kim@lge.com\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nReviewed-by: Jan Kara \u003cjack@suse.cz\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "38464cd9b38b43ef757da18bc8b9badcd2b70dfb", "tree": "1775ae7e40819d74f92613904b5fd82e5a4ce88e", "parents": [ "3edd6224c2a677bb59efe0b083a51fc2b3b5c64d" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Sat Jun 13 06:52:56 2015 +0100" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Mon Mar 21 09:17:39 2016 +0800" }, "message": "Btrfs: use kmem_cache_free when freeing entry in inode cache\n\ncommit c3f4a1685bb87e59c886ee68f7967eae07d4dffa upstream.\n\nThe free space entries are allocated using kmem_cache_zalloc(),\nthrough __btrfs_add_free_space(), therefore we should use\nkmem_cache_free() and not kfree() to avoid any confusion and\nany potential problem. Looking at the kfree() definition at\nmm/slab.c it has the following comment:\n\n /*\n * (...)\n *\n * Don\u0027t free memory not originally allocated by kmalloc()\n * or you will run into trouble.\n */\n\nSo better be safe and use kmem_cache_free().\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: David Sterba \u003cdsterba@suse.cz\u003e\nSigned-off-by: Chris Mason \u003cclm@fb.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "3edd6224c2a677bb59efe0b083a51fc2b3b5c64d", "tree": "d88f99deb20442017f6525013a89bd685105a4c7", "parents": [ "0e93547fff9eff4b36f56860a19cb71042ab7b34" ], "author": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:09 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:09 2015 +0800" }, "message": "Linux 3.4.110\n" }, { "commit": "0e93547fff9eff4b36f56860a19cb71042ab7b34", "tree": "fa72ad6469e71b8eaecae5206d41fcedf19ec71c", "parents": [ "4a69710b414cd12081da97ec35971c9b22833992" ], "author": { "name": "Olga Kornievskaia", "email": "aglo@umich.edu", "time": "Mon Sep 14 19:54:36 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:08 2015 +0800" }, "message": "Failing to send a CLOSE if file is opened WRONLY and server reboots on a 4.x mount\n\ncommit a41cbe86df3afbc82311a1640e20858c0cd7e065 upstream.\n\nA test case is as the description says:\nopen(foobar, O_WRONLY);\nsleep() --\u003e reboot the server\nclose(foobar)\n\nThe bug is because in nfs4state.c in nfs4_reclaim_open_state() a few\nline before going to restart, there is\nclear_bit(NFS4CLNT_RECLAIM_NOGRACE, \u0026state-\u003eflags).\n\nNFS4CLNT_RECLAIM_NOGRACE is a flag for the client states not open\nowner states. Value of NFS4CLNT_RECLAIM_NOGRACE is 4 which is the\nvalue of NFS_O_WRONLY_STATE in nfs4_state-\u003eflags. So clearing it wipes\nout state and when we go to close it, “call_close” doesn’t get set as\nstate flag is not set and CLOSE doesn’t go on the wire.\n\nSigned-off-by: Olga Kornievskaia \u003caglo@umich.edu\u003e\nSigned-off-by: Trond Myklebust \u003ctrond.myklebust@primarydata.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "4a69710b414cd12081da97ec35971c9b22833992", "tree": "e8e46ffe54817bc3c50873ed0b18f40af4fd09eb", "parents": [ "652b4f2f20702cbb6cb7846a39af99d182c59764" ], "author": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Sat Aug 15 20:27:13 2015 -0500" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:08 2015 +0800" }, "message": "vfs: Test for and handle paths that are unreachable from their mnt_root\n\ncommit 397d425dc26da728396e66d392d5dcb8dac30c37 upstream.\n\nIn rare cases a directory can be renamed out from under a bind mount.\nIn those cases without special handling it becomes possible to walk up\nthe directory tree to the root dentry of the filesystem and down\nfrom the root dentry to every other file or directory on the filesystem.\n\nLike division by zero .. from an unconnected path can not be given\na useful semantic as there is no predicting at which path component\nthe code will realize it is unconnected. We certainly can not match\nthe current behavior as the current behavior is a security hole.\n\nTherefore when encounting .. when following an unconnected path\nreturn -ENOENT.\n\n- Add a function path_connected to verify path-\u003edentry is reachable\n from path-\u003emnt.mnt_root. AKA to validate that rename did not do\n something nasty to the bind mount.\n\n To avoid races path_connected must be called after following a path\n component to it\u0027s next path component.\n\nSigned-off-by: \"Eric W. Biederman\" \u003cebiederm@xmission.com\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "652b4f2f20702cbb6cb7846a39af99d182c59764", "tree": "c8797a21ba17b47bba2e264dc72a03dbd04c242a", "parents": [ "7a403328c381da57af51f57428f55d1388d233b2" ], "author": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Sat Aug 15 13:36:12 2015 -0500" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:08 2015 +0800" }, "message": "dcache: Handle escaped paths in prepend_path\n\ncommit cde93be45a8a90d8c264c776fab63487b5038a65 upstream.\n\nA rename can result in a dentry that by walking up d_parent\nwill never reach it\u0027s mnt_root. For lack of a better term\nI call this an escaped path.\n\nprepend_path is called by four different functions __d_path,\nd_absolute_path, d_path, and getcwd.\n\n__d_path only wants to see paths are connected to the root it passes\nin. So __d_path needs prepend_path to return an error.\n\nd_absolute_path similarly wants to see paths that are connected to\nsome root. Escaped paths are not connected to any mnt_root so\nd_absolute_path needs prepend_path to return an error greater\nthan 1. So escaped paths will be treated like paths on lazily\nunmounted mounts.\n\ngetcwd needs to prepend \"(unreachable)\" so getcwd also needs\nprepend_path to return an error.\n\nd_path is the interesting hold out. d_path just wants to print\nsomething, and does not care about the weird cases. Which raises\nthe question what should be printed?\n\nGiven that \u003cescaped_path\u003e/\u003canything\u003e should result in -ENOENT I\nbelieve it is desirable for escaped paths to be printed as empty\npaths. As there are not really any meaninful path components when\nconsidered from the perspective of a mount tree.\n\nSo tweak prepend_path to return an empty path with an new error\ncode of 3 when it encounters an escaped path.\n\nSigned-off-by: \"Eric W. Biederman\" \u003cebiederm@xmission.com\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "7a403328c381da57af51f57428f55d1388d233b2", "tree": "0860d0a5f025833c599029e9235c7da696eac728", "parents": [ "e1ae22abf3a99e98cc109253400662b7f00403e1" ], "author": { "name": "Mike Marciniszyn", "email": "mike.marciniszyn@intel.com", "time": "Fri Oct 09 01:12:28 2015 +0100" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:08 2015 +0800" }, "message": "IB/qib: Change lkey table allocation to support more MRs\n\ncommit d6f1c17e162b2a11e708f28fa93f2f79c164b442 upstream.\n\nThe lkey table is allocated with with a get_user_pages() with an\norder based on a number of index bits from a module parameter.\n\nThe underlying kernel code cannot allocate that many contiguous pages.\n\nThere is no reason the underlying memory needs to be physically\ncontiguous.\n\nThis patch:\n- switches the allocation/deallocation to vmalloc/vfree\n- caps the number of bits to 23 to insure at least 1 generation bit\n o this matches the module parameter description\n\nReviewed-by: Vinit Agnihotri \u003cvinit.abhay.agnihotri@intel.com\u003e\nSigned-off-by: Mike Marciniszyn \u003cmike.marciniszyn@intel.com\u003e\nSigned-off-by: Doug Ledford \u003cdledford@redhat.com\u003e\n[bwh: Backported to 3.2:\n - Adjust context\n - Add definition of qib_dev_warn(), added upstream by commit ddb887658970\n (\"IB/qib: Convert opcode counters to per-context\")]\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "e1ae22abf3a99e98cc109253400662b7f00403e1", "tree": "d1b9c4b07d7e518270a478f6f1e994e828dc2987", "parents": [ "15488de7b72b6ab8254dda07053faa4be6b9ec66" ], "author": { "name": "Jan Kara", "email": "jack@suse.com", "time": "Tue Jul 28 14:57:14 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:08 2015 +0800" }, "message": "jbd2: avoid infinite loop when destroying aborted journal\n\ncommit 841df7df196237ea63233f0f9eaa41db53afd70f upstream.\n\nCommit 6f6a6fda2945 \"jbd2: fix ocfs2 corrupt when updating journal\nsuperblock fails\" changed jbd2_cleanup_journal_tail() to return EIO\nwhen the journal is aborted. That makes logic in\njbd2_log_do_checkpoint() bail out which is fine, except that\njbd2_journal_destroy() expects jbd2_log_do_checkpoint() to always make\na progress in cleaning the journal. Without it jbd2_journal_destroy()\njust loops in an infinite loop.\n\nFix jbd2_journal_destroy() to cleanup journal checkpoint lists of\njbd2_log_do_checkpoint() fails with error.\n\nReported-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nTested-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nFixes: 6f6a6fda294506dfe0e3e0a253bb2d2923f28f0a\nSigned-off-by: Jan Kara \u003cjack@suse.com\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "15488de7b72b6ab8254dda07053faa4be6b9ec66", "tree": "a78a65243595560eef2cd904bc6c1e2334a09b85", "parents": [ "0ca709ad358a1cb9be5f594a6eca77cbb3b7d7a1" ], "author": { "name": "John Youn", "email": "John.Youn@synopsys.com", "time": "Mon Sep 17 00:00:00 2001 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:08 2015 +0800" }, "message": "usb: dwc3: Reset the transfer resource index on SET_INTERFACE\n\ncommit aebda618718157a69c0dc0adb978d69bc2b8723c upstream.\n\nThis fixes an issue introduced in commit b23c843992b6 (usb: dwc3:\ngadget: fix DEPSTARTCFG for non-EP0 EPs) that made sure we would\nonly use DEPSTARTCFG once per SetConfig.\n\nThe trick is that we should use one DEPSTARTCFG per SetConfig *OR*\nSetInterface. SetInterface was completely missed from the original\npatch.\n\nThis problem became aparent after commit 76e838c9f776 (usb: dwc3:\ngadget: return error if command sent to DEPCMD register fails)\nadded checking of the return status of device endpoint commands.\n\n\u0027Set Endpoint Transfer Resource\u0027 command was caught failing\noccasionally. This is because the Transfer Resource\nIndex was not getting reset during a SET_INTERFACE request.\n\nFinally, to fix the issue, was we have to do is make sure that\nour start_config_issued flag gets reset whenever we receive a\nSetInterface request.\n\nTo verify the problem (and its fix), all we have to do is run\ntest 9 from testusb with \u0027testusb -t 9 -s 2048 -a -c 5000\u0027.\n\nTested-by: Huang Rui \u003cray.huang@amd.com\u003e\nTested-by: Subbaraya Sundeep Bhatta \u003csubbaraya.sundeep.bhatta@xilinx.com\u003e\nFixes: b23c843992b6 (usb: dwc3: gadget: fix DEPSTARTCFG for non-EP0 EPs)\nSigned-off-by: John Youn \u003cjohnyoun@synopsys.com\u003e\nSigned-off-by: Felipe Balbi \u003cbalbi@ti.com\u003e\n[lizf: Backported to 3.4: use dev_vdbg() instead of dwc3_trace()]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "0ca709ad358a1cb9be5f594a6eca77cbb3b7d7a1", "tree": "f186fe0772cb5106c9783c571e7d0173444c6c7b", "parents": [ "700af4cf0afd35a1083b028010ba3b192bf19bb6" ], "author": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Sun Oct 11 18:45:19 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:08 2015 +0800" }, "message": "ARM: Fix incorrect backport of 0b59d8806a31\n\nReported-by: Jim Faulkner \u003cjfaulkne@ccs.neu.edu\u003e\nFixed-by: Nicolas Schichan \u003cnschichan@freebox.fr\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "700af4cf0afd35a1083b028010ba3b192bf19bb6", "tree": "3c8587fd30bcd2865340e6a559a06e4f708bfda4", "parents": [ "12fb133f36f0690ee49260ca95c4f56f94f41853" ], "author": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Sun Oct 11 16:27:16 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:08 2015 +0800" }, "message": "crypto: s390/ghash: Fix incorrect backport of a1cae34e23b1\n\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "12fb133f36f0690ee49260ca95c4f56f94f41853", "tree": "3bf5027eeacd588bdf39c8af2a59d46e6c843415", "parents": [ "bdb211672fec45cbf48de2b1acddae8fb1924ef1" ], "author": { "name": "Christian König", "email": "christian.koenig@amd.com", "time": "Thu May 28 15:51:59 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:08 2015 +0800" }, "message": "drm/radeon: partially revert \"fix VM_CONTEXT*_PAGE_TABLE_END_ADDR handling\"\n\ncommit 7c0411d2fabc2e2702c9871ffb603e251158b317 upstream.\n\nWe have that bug for years and some users report side effects when fixing it on older hardware.\n\nSo revert it for VM_CONTEXT0_PAGE_TABLE_END_ADDR, but keep it for VM 1-15.\n\nSigned-off-by: Christian König \u003cchristian.koenig@amd.com\u003e\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\n[lizf: Backported to 3.4: drop the change to clk.c]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "bdb211672fec45cbf48de2b1acddae8fb1924ef1", "tree": "58586fb5bd50e435e8e24b64dbfb8cee5c4bd2ef", "parents": [ "a0b13721e2df7d316080520fb870464ed0a3ce14" ], "author": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Sun Oct 11 16:03:09 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:07 2015 +0800" }, "message": "Revert \"drm/radeon: Use drm_calloc_ab for CS relocs\"\n\nThis reverts commit 961bd13539b9e7ca5d2e667668141496b7a1d6bc.\n\nBoth Satoshi-san and Cal reported a kernel crash due to this commit.\n\nReported-by: Satoshi Iwamoto \u003csatoshi.iwamoto@nifty.ne.jp\u003e\nReported-by: Cal Peake \u003ccp@absolutedigital.net\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "a0b13721e2df7d316080520fb870464ed0a3ce14", "tree": "309a9629804d8e62c04fddacbf3c63d90f809333", "parents": [ "22b1c30792cfd5da151f0ba47d2e66d3ea760b96" ], "author": { "name": "Jani Nikula", "email": "jani.nikula@intel.com", "time": "Mon Jun 15 12:59:37 2015 +0300" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:07 2015 +0800" }, "message": "Revert \"drm/i915: Don\u0027t skip request retirement if the active list is empty\"\n\ncommit 245ec9d85696c3e539b23e210f248698b478379c upstream.\n\nThis reverts commit 0aedb1626566efd72b369c01992ee7413c82a0c5.\n\nI messed things up while applying [1] to drm-intel-fixes. Rectify.\n\n[1] http://mid.gmane.org/1432827156-9605-1-git-send-email-ville.syrjala@linux.intel.com\n\nFixes: 0aedb1626566 (\"drm/i915: Don\u0027t skip request retirement if the active list is empty\")\nAcked-by: Ville Syrjälä \u003cville.syrjala@linux.intel.com\u003e\nSigned-off-by: Jani Nikula \u003cjani.nikula@intel.com\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "22b1c30792cfd5da151f0ba47d2e66d3ea760b96", "tree": "e5ba2e5c9c3e13529379a7ea29085f7d5322f670", "parents": [ "8d6a97ca45dfa0fd1ef04c498126784f59198ad3" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Sat Jul 04 16:04:19 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:07 2015 +0800" }, "message": "9p: forgetting to cancel request on interrupted zero-copy RPC\n\ncommit a84b69cb6e0a41e86bc593904faa6def3b957343 upstream.\n\nIf we\u0027d already sent a request and decide to abort it, we *must*\nissue TFLUSH properly and not just blindly reuse the tag, or\nwe\u0027ll get seriously screwed when response eventually arrives\nand we confuse it for response to later request that had reused\nthe same tag.\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "8d6a97ca45dfa0fd1ef04c498126784f59198ad3", "tree": "10066160f6929fc3d3abde42e5d641e79a2bfcdb", "parents": [ "08c730489602b6e3092e54180f47a7b3bfc32172" ], "author": { "name": "Radim Krčmář", "email": "rkrcmar@redhat.com", "time": "Tue Jun 30 22:19:17 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:07 2015 +0800" }, "message": "KVM: x86: properly restore LVT0\n\ncommit db1385624c686fe99fe2d1b61a36e1537b915d08 upstream.\n\nLegacy NMI watchdog didn\u0027t work after migration/resume, because\nvapics_in_nmi_mode was left at 0.\n\nSigned-off-by: Radim Krčmář \u003crkrcmar@redhat.com\u003e\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n[lizf: Backported to 3.4:\n - adjust context\n - s/kvm_apic_get_reg/apic_get_reg/]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "08c730489602b6e3092e54180f47a7b3bfc32172", "tree": "8940b10d3b4fb1b45087452dc3c217868872cc31", "parents": [ "d4ee09b224ce7d0a815aa8a70a9a01b032358393" ], "author": { "name": "Radim Krčmář", "email": "rkrcmar@redhat.com", "time": "Wed Jul 01 15:31:49 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:07 2015 +0800" }, "message": "KVM: x86: make vapics_in_nmi_mode atomic\n\ncommit 42720138b06301cc8a7ee8a495a6d021c4b6a9bc upstream.\n\nWrites were a bit racy, but hard to turn into a bug at the same time.\n(Particularly because modern Linux doesn\u0027t use this feature anymore.)\n\nSigned-off-by: Radim Krčmář \u003crkrcmar@redhat.com\u003e\n[Actually the next patch makes it much, much easier to trigger the race\n so I\u0027m including this one for stable@ as well. - Paolo]\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "d4ee09b224ce7d0a815aa8a70a9a01b032358393", "tree": "3f43ff148cd23e2810141fbb84d28d2e251b7d20", "parents": [ "61b8a506b6e3d3d391121c7b3c1c1cf29472d8e1" ], "author": { "name": "Lv Zheng", "email": "lv.zheng@intel.com", "time": "Wed Jul 01 14:43:26 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:07 2015 +0800" }, "message": "ACPICA: Tables: Fix an issue that FACS initialization is performed twice\n\ncommit c04be18448355441a0c424362df65b6422e27bda upstream.\n\nACPICA commit 90f5332a15e9d9ba83831ca700b2b9f708274658\n\nThis patch adds a new FACS initialization flag for acpi_tb_initialize().\nacpi_enable_subsystem() might be invoked several times in OS bootup process,\nand we don\u0027t want FACS initialization to be invoked twice. Lv Zheng.\n\nLink: https://github.com/acpica/acpica/commit/90f5332a\nSigned-off-by: Lv Zheng \u003clv.zheng@intel.com\u003e\nSigned-off-by: Bob Moore \u003crobert.moore@intel.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crafael.j.wysocki@intel.com\u003e\n[lizf: Backported to 3.4: adjust filename]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "61b8a506b6e3d3d391121c7b3c1c1cf29472d8e1", "tree": "bda6ffa359ded3409482ba05e467c93642d52165", "parents": [ "8458a844200efaca2a5653cbddd065c060a16cf0" ], "author": { "name": "Miklos Szeredi", "email": "mszeredi@suse.cz", "time": "Wed Jul 01 16:25:55 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:07 2015 +0800" }, "message": "fuse: initialize fc-\u003erelease before calling it\n\ncommit 0ad0b3255a08020eaf50e34ef0d6df5bdf5e09ed upstream.\n\nfc-\u003erelease is called from fuse_conn_put() which was used in the error\ncleanup before fc-\u003erelease was initialized.\n\n[Jeremiah Mahler \u003cjmmahler@gmail.com\u003e: assign fc-\u003erelease after calling\nfuse_conn_init(fc) instead of before.]\n\nSigned-off-by: Miklos Szeredi \u003cmszeredi@suse.cz\u003e\nFixes: a325f9b92273 (\"fuse: update fuse_conn_init() and separate out fuse_conn_kill()\")\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "8458a844200efaca2a5653cbddd065c060a16cf0", "tree": "202ec06830ac4db1fe5a6f405c8494c72ae0ac9a", "parents": [ "d6a9245c6082d243e77fa997d2cfe612ad9fde96" ], "author": { "name": "Ilya Dryomov", "email": "idryomov@gmail.com", "time": "Mon Jun 29 19:30:23 2015 +0300" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:07 2015 +0800" }, "message": "crush: fix a bug in tree bucket decode\n\ncommit 82cd003a77173c91b9acad8033fb7931dac8d751 upstream.\n\nstruct crush_bucket_tree::num_nodes is u8, so ceph_decode_8_safe()\nshould be used. -Wconversion catches this, but I guess it went\nunnoticed in all the noise it spews. The actual problem (at least for\ncommon crushmaps) isn\u0027t the u32 -\u003e u8 truncation though - it\u0027s the\nadvancement by 4 bytes instead of 1 in the crushmap buffer.\n\nFixes: http://tracker.ceph.com/issues/2759\n\nSigned-off-by: Ilya Dryomov \u003cidryomov@gmail.com\u003e\nReviewed-by: Josh Durgin \u003cjdurgin@redhat.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "d6a9245c6082d243e77fa997d2cfe612ad9fde96", "tree": "15962428846910589327f9ffb5a8042378eef010", "parents": [ "2d0186edeb74f4a0b11e2d7f53085684fa12d273" ], "author": { "name": "Chris Wilson", "email": "chris@chris-wilson.co.uk", "time": "Sun Jun 28 14:18:16 2015 +0100" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:06 2015 +0800" }, "message": "agp/intel: Fix typo in needs_ilk_vtd_wa()\n\ncommit 8b572a4200828b4e75cc22ed2f494b58d5372d65 upstream.\n\nIn needs_ilk_vtd_wa(), we pass in the GPU device but compared it against\nthe ids for the mobile GPU and the mobile host bridge. That latter is\nimpossible and so likely was just a typo for the desktop GPU device id\n(which is also buggy).\n\nFixes commit da88a5f7f7d434e2cde1b3e19d952e6d84533662\nAuthor: Chris Wilson \u003cchris@chris-wilson.co.uk\u003e\nDate: Wed Feb 13 09:31:53 2013 +0000\n\n drm/i915: Disable WC PTE updates to w/a buggy IOMMU on ILK\n\nReported-by: Ting-Wei Lan \u003clantw44@gmail.com\u003e\nBugzilla: https://bugs.freedesktop.org/show_bug.cgi?id\u003d91127\nReferences: https://bugzilla.freedesktop.org/show_bug.cgi?id\u003d60391\nSigned-off-by: Chris Wilson \u003cchris@chris-wilson.co.uk\u003e\nCc: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nReviewed-by: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Jani Nikula \u003cjani.nikula@intel.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "2d0186edeb74f4a0b11e2d7f53085684fa12d273", "tree": "00ee72ffcdb74efec4f5d363e910447267b28f86", "parents": [ "c207c4948630601928b3fd5b168a89734f148e76" ], "author": { "name": "Chris Metcalf", "email": "cmetcalf@ezchip.com", "time": "Thu Jun 25 15:02:08 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:06 2015 +0800" }, "message": "__bitmap_parselist: fix bug in empty string handling\n\ncommit 2528a8b8f457d7432552d0e2b6f0f4046bb702f4 upstream.\n\nbitmap_parselist(\"\", \u0026mask, nmaskbits) will erroneously set bit zero in\nthe mask. The same bug is visible in cpumask_parselist() since it is\nlayered on top of the bitmask code, e.g. if you boot with \"isolcpus\u003d\",\nyou will actually end up with cpu zero isolated.\n\nThe bug was introduced in commit 4b060420a596 (\"bitmap, irq: add\nsmp_affinity_list interface to /proc/irq\") when bitmap_parselist() was\ngeneralized to support userspace as well as kernelspace.\n\nFixes: 4b060420a596 (\"bitmap, irq: add smp_affinity_list interface to /proc/irq\")\nSigned-off-by: Chris Metcalf \u003ccmetcalf@ezchip.com\u003e\nCc: Rasmus Villemoes \u003clinux@rasmusvillemoes.dk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "c207c4948630601928b3fd5b168a89734f148e76", "tree": "2501dbda07c35fc81536b876b97a67ed67e728d2", "parents": [ "7ebabd77613ddc5b1841c788085c5ac8c6b2cd85" ], "author": { "name": "Steven Rostedt (Red Hat)", "email": "rostedt@goodmis.org", "time": "Thu Jun 25 18:10:09 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:06 2015 +0800" }, "message": "tracing/filter: Do not allow infix to exceed end of string\n\ncommit 6b88f44e161b9ee2a803e5b2b1fbcf4e20e8b980 upstream.\n\nWhile debugging a WARN_ON() for filtering, I found that it is possible\nfor the filter string to be referenced after its end. With the filter:\n\n # echo \u0027\u003e\u0027 \u003e /sys/kernel/debug/events/ext4/ext4_truncate_exit/filter\n\nThe filter_parse() function can call infix_get_op() which calls\ninfix_advance() that updates the infix filter pointers for the cnt\nand tail without checking if the filter is already at the end, which\nwill put the cnt to zero and the tail beyond the end. The loop then calls\ninfix_next() that has\n\n\tps-\u003einfix.cnt--;\n\treturn ps-\u003einfix.string[ps-\u003einfix.tail++];\n\nThe cnt will now be below zero, and the tail that is returned is\nalready passed the end of the filter string. So far the allocation\nof the filter string usually has some buffer that is zeroed out, but\nif the filter string is of the exact size of the allocated buffer\nthere\u0027s no guarantee that the charater after the nul terminating\ncharacter will be zero.\n\nLuckily, only root can write to the filter.\n\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "7ebabd77613ddc5b1841c788085c5ac8c6b2cd85", "tree": "e39de8a4ecf033b01f21d27eca26a68bddc1d2e1", "parents": [ "800e58ae21796a472f39cd6d0601c87b297409af" ], "author": { "name": "Steven Rostedt (Red Hat)", "email": "rostedt@goodmis.org", "time": "Thu Jun 25 18:02:29 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:06 2015 +0800" }, "message": "tracing/filter: Do not WARN on operand count going below zero\n\ncommit b4875bbe7e68f139bd3383828ae8e994a0df6d28 upstream.\n\nWhen testing the fix for the trace filter, I could not come up with\na scenario where the operand count goes below zero, so I added a\nWARN_ON_ONCE(cnt \u003c 0) to the logic. But there is legitimate case\nthat it can happen (although the filter would be wrong).\n\n # echo \u0027\u003e\u0027 \u003e /sys/kernel/debug/events/ext4/ext4_truncate_exit/filter\n\nThat is, a single operation without any operands will hit the path\nwhere the WARN_ON_ONCE() can trigger. Although this is harmless,\nand the filter is reported as a error. But instead of spitting out\na warning to the kernel dmesg, just fail nicely and report it via\nthe proper channels.\n\nLink: http://lkml.kernel.org/r/558C6082.90608@oracle.com\n\nReported-by: Vince Weaver \u003cvincent.weaver@maine.edu\u003e\nReported-by: Sasha Levin \u003csasha.levin@oracle.com\u003e\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "800e58ae21796a472f39cd6d0601c87b297409af", "tree": "acc9389a960cf9ebde2078de4e731b3f76ef69c2", "parents": [ "019db118fefae4f5e792b007a73474d1d0ef1975" ], "author": { "name": "Pali Rohár", "email": "pali.rohar@gmail.com", "time": "Tue Jun 23 10:11:19 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:06 2015 +0800" }, "message": "dell-laptop: Fix allocating \u0026 freeing SMI buffer page\n\ncommit b8830a4e71b15d0364ac8e6c55301eea73f211da upstream.\n\nThis commit fix kernel crash when probing for rfkill devices in dell-laptop\ndriver failed. Function free_page() was incorrectly used on struct page *\ninstead of virtual address of SMI buffer.\n\nThis commit also simplify allocating page for SMI buffer by using\n__get_free_page() function instead of sequential call of functions\nalloc_page() and page_address().\n\nSigned-off-by: Pali Rohár \u003cpali.rohar@gmail.com\u003e\nAcked-by: Michal Hocko \u003cmhocko@suse.cz\u003e\nSigned-off-by: Darren Hart \u003cdvhart@linux.intel.com\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "019db118fefae4f5e792b007a73474d1d0ef1975", "tree": "d1245e9a6b7a4158e74295883c15857c03493763", "parents": [ "176a2eacd65fbc3b3d911605a83d3262770fc213" ], "author": { "name": "Catalin Marinas", "email": "catalin.marinas@arm.com", "time": "Wed Jun 24 16:58:26 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:06 2015 +0800" }, "message": "mm: kmemleak: allow safe memory scanning during kmemleak disabling\n\ncommit c5f3b1a51a591c18c8b33983908e7fdda6ae417e upstream.\n\nThe kmemleak scanning thread can run for minutes. Callbacks like\nkmemleak_free() are allowed during this time, the race being taken care\nof by the object-\u003elock spinlock. Such lock also prevents a memory block\nfrom being freed or unmapped while it is being scanned by blocking the\nkmemleak_free() -\u003e ... -\u003e __delete_object() function until the lock is\nreleased in scan_object().\n\nWhen a kmemleak error occurs (e.g. it fails to allocate its metadata),\nkmemleak_enabled is set and __delete_object() is no longer called on\nfreed objects. If kmemleak_scan is running at the same time,\nkmemleak_free() no longer waits for the object scanning to complete,\nallowing the corresponding memory block to be freed or unmapped (in the\ncase of vfree()). This leads to kmemleak_scan potentially triggering a\npage fault.\n\nThis patch separates the kmemleak_free() enabling/disabling from the\noverall kmemleak_enabled nob so that we can defer the disabling of the\nobject freeing tracking until the scanning thread completed. The\nkmemleak_free_part() is deliberately ignored by this patch since this is\nonly called during boot before the scanning thread started.\n\nSigned-off-by: Catalin Marinas \u003ccatalin.marinas@arm.com\u003e\nReported-by: Vignesh Radhakrishnan \u003cvigneshr@codeaurora.org\u003e\nTested-by: Vignesh Radhakrishnan \u003cvigneshr@codeaurora.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "176a2eacd65fbc3b3d911605a83d3262770fc213", "tree": "88b9834660f5e3bfb99116356e663a9c53ad02aa", "parents": [ "e2b3a182f87e27d44bc95dcb1d005bc4191ea7e1" ], "author": { "name": "Alexey Brodkin", "email": "Alexey.Brodkin@synopsys.com", "time": "Wed Jun 24 11:47:41 2015 +0300" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:06 2015 +0800" }, "message": "stmmac: troubleshoot unexpected bits in des0 \u0026 des1\n\ncommit f1590670ce069eefeb93916391a67643e6ad1630 upstream.\n\nCurrent implementation of descriptor init procedure only takes\ncare about setting/clearing ownership flag in \"des0\"/\"des1\"\nfields while it is perfectly possible to get unexpected bits\nset because of the following factors:\n\n [1] On driver probe underlying memory allocated with\n dma_alloc_coherent() might not be zeroed and so\n it will be filled with garbage.\n\n [2] During driver operation some bits could be set by SD/MMC\n controller (for example error flags etc).\n\nAnd unexpected and/or randomly set flags in \"des0\"/\"des1\"\nfields may lead to unpredictable behavior of GMAC DMA block.\n\nThis change addresses both items above with:\n\n [1] Use of dma_zalloc_coherent() instead of simple\n dma_alloc_coherent() to make sure allocated memory is\n zeroed. That shouldn\u0027t affect performance because\n this allocation only happens once on driver probe.\n\n [2] Do explicit zeroing of both \"des0\" and \"des1\" fields\n of all buffer descriptors during initialization of\n DMA transfer.\n\nAnd while at it fixed identation of dma_free_coherent()\ncounterpart as well.\n\nSigned-off-by: Alexey Brodkin \u003cabrodkin@synopsys.com\u003e\nCc: Giuseppe Cavallaro \u003cpeppe.cavallaro@st.com\u003e\nCc: arc-linux-dev@synopsys.com\nCc: linux-kernel@vger.kernel.org\nCc: David Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n[lizf: Backported to 3.4:\n - adjust contest\n - adjust allocations in init_dma_desc_rings()]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "e2b3a182f87e27d44bc95dcb1d005bc4191ea7e1", "tree": "207d8835d1b8cbf25e3fc47e3109f7622072505a", "parents": [ "dd7ad96cc31ad681593e41e5e0cfbd9752ee9f34" ], "author": { "name": "Satish Ashok", "email": "sashok@cumulusnetworks.com", "time": "Fri Jun 19 01:22:57 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:06 2015 +0800" }, "message": "bridge: multicast: restore router configuration on port link down/up\n\ncommit 754bc547f0a79f7568b5b81c7fc0a8d044a6571a upstream.\n\nWhen a port goes through a link down/up the multicast router configuration\nis not restored.\n\nSigned-off-by: Satish Ashok \u003csashok@cumulusnetworks.com\u003e\nSigned-off-by: Nikolay Aleksandrov \u003cnikolay@cumulusnetworks.com\u003e\nFixes: 0909e11758bd (\"bridge: Add multicast_router sysfs entries\")\nAcked-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "dd7ad96cc31ad681593e41e5e0cfbd9752ee9f34", "tree": "bc1e2d6177a2e96f035f47801dd5093fc3d8414e", "parents": [ "2ba0674bed6f8b830c9653015f431794d9c8efda" ], "author": { "name": "Uwe Kleine-König", "email": "u.kleine-koenig@pengutronix.de", "time": "Wed Apr 29 20:38:46 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:06 2015 +0800" }, "message": "watchdog: omap: assert the counter being stopped before reprogramming\n\ncommit 530c11d432727c697629ad5f9d00ee8e2864d453 upstream.\n\nThe omap watchdog has the annoying behaviour that writes to most\nregisters don\u0027t have any effect when the watchdog is already running.\nQuoting the AM335x reference manual:\n\n\tTo modify the timer counter value (the WDT_WCRR register),\n\tprescaler ratio (the WDT_WCLR[4:2] PTV bit field), delay\n\tconfiguration value (the WDT_WDLY[31:0] DLY_VALUE bit field), or\n\tthe load value (the WDT_WLDR[31:0] TIMER_LOAD bit field), the\n\twatchdog timer must be disabled by using the start/stop sequence\n\t(the WDT_WSPR register).\n\nCurrently the timer is stopped in the .probe callback but still there\nare possibilities that yield to a situation where omap_wdt_start is\nentered with the timer running (e.g. when /dev/watchdog is closed\nwithout stopping and then reopened). In such a case programming the\ntimeout silently fails!\n\nTo circumvent this stop the timer before reprogramming.\n\nAssuming one of the first things the watchdog user does is setting the\ntimeout explicitly nothing too bad should happen because this explicit\nsetting works fine.\n\nFixes: 7768a13c252a (\"[PATCH] OMAP: Add Watchdog driver support\")\nSigned-off-by: Uwe Kleine-König \u003cu.kleine-koenig@pengutronix.de\u003e\nReviewed-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\nSigned-off-by: Wim Van Sebroeck \u003cwim@iguana.be\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "2ba0674bed6f8b830c9653015f431794d9c8efda", "tree": "41cceb31b1a570a90c945b81876678f906c05ccf", "parents": [ "52686b9264cfdff747380f1bb70d11274fd83060" ], "author": { "name": "Darrick J. Wong", "email": "darrick.wong@oracle.com", "time": "Sun Jun 21 21:10:51 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:05 2015 +0800" }, "message": "ext4: don\u0027t retry file block mapping on bigalloc fs with non-extent file\n\ncommit 292db1bc6c105d86111e858859456bcb11f90f91 upstream.\n\next4 isn\u0027t willing to map clusters to a non-extent file. Don\u0027t signal\nthis with an out of space error, since the FS will retry the\nallocation (which didn\u0027t fail) forever. Instead, return EUCLEAN so\nthat the operation will fail immediately all the way back to userspace.\n\n(The fix is either to run e2fsck -E bmap2extent, or to chattr +e the file.)\n\nSigned-off-by: Darrick J. Wong \u003cdarrick.wong@oracle.com\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "52686b9264cfdff747380f1bb70d11274fd83060", "tree": "7e967243bf1be385fbf660b7a22edc0f9f2ebacd", "parents": [ "2fb9a78c44b0801fb17f3f73f553b8416b96abe0" ], "author": { "name": "Willem de Bruijn", "email": "willemb@google.com", "time": "Wed Jun 17 15:59:34 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:05 2015 +0800" }, "message": "packet: avoid out of bounds read in round robin fanout\n\ncommit 468479e6043c84f5a65299cc07cb08a22a28c2b1 upstream.\n\nPACKET_FANOUT_LB computes f-\u003err_cur such that it is modulo\nf-\u003enum_members. It returns the old value unconditionally, but\nf-\u003enum_members may have changed since the last store. Ensure\nthat the return value is always \u003c num.\n\nWhen modifying the logic, simplify it further by replacing the loop\nwith an unconditional atomic increment.\n\nFixes: dc99f600698d (\"packet: Add fanout support.\")\nSuggested-by: Eric Dumazet \u003cedumazet@google.com\u003e\nSigned-off-by: Willem de Bruijn \u003cwillemb@google.com\u003e\nAcked-by: Eric Dumazet \u003cedumazet@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n[lizf: Backported to 3.4:\n - adjust context\n - fanout_demux_lb() returns a pointer]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "2fb9a78c44b0801fb17f3f73f553b8416b96abe0", "tree": "0fa3049732e55c3340dbf3a1048ce775b47c55b8", "parents": [ "b80954b45832fbd665c2a8bc545601716942ce78" ], "author": { "name": "Eric Dumazet", "email": "edumazet@google.com", "time": "Tue Jun 16 07:59:11 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:05 2015 +0800" }, "message": "packet: read num_members once in packet_rcv_fanout()\n\ncommit f98f4514d07871da7a113dd9e3e330743fd70ae4 upstream.\n\nWe need to tell compiler it must not read f-\u003enum_members multiple\ntimes. Otherwise testing if num is not zero is flaky, and we could\nattempt an invalid divide by 0 in fanout_demux_cpu()\n\nNote bug was present in packet_rcv_fanout_hash() and\npacket_rcv_fanout_lb() but final 3.1 had a simple location\nafter commit 95ec3eb417115fb (\"packet: Add \u0027cpu\u0027 fanout policy.\")\n\nFixes: dc99f600698dc (\"packet: Add fanout support.\")\nSigned-off-by: Eric Dumazet \u003cedumazet@google.com\u003e\nCc: Willem de Bruijn \u003cwillemb@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n[lizf: Backported to 3.4: use ACCESS_ONCE() instead of READ_ONCE()]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "b80954b45832fbd665c2a8bc545601716942ce78", "tree": "7eca3dad92eb6f76487f2f9b8ee7c2a5d659a3b0", "parents": [ "9beee8b18a53aaf9a9678245dd1687a0430d862b" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Jun 20 22:50:33 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:05 2015 +0800" }, "message": "ext4: call sync_blockdev() before invalidate_bdev() in put_super()\n\ncommit 89d96a6f8e6491f24fc8f99fd6ae66820e85c6c1 upstream.\n\nNormally all of the buffers will have been forced out to disk before\nwe call invalidate_bdev(), but there will be some cases, where a file\nsystem operation was aborted due to an ext4_error(), where there may\nstill be some dirty buffers in the buffer cache for the device. So\ntry to force them out to memory before calling invalidate_bdev().\n\nThis fixes a warning triggered by generic/081:\n\nWARNING: CPU: 1 PID: 3473 at /usr/projects/linux/ext4/fs/block_dev.c:56 __blkdev_put+0xb5/0x16f()\n\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "9beee8b18a53aaf9a9678245dd1687a0430d862b", "tree": "22348750349ae7ebc9074cbea30dcea6f2b27d1f", "parents": [ "aef2b5342c1c17abbcd068d25ce5c48e6b43a5f8" ], "author": { "name": "Nikolay Aleksandrov", "email": "razor@blackwall.org", "time": "Mon Jun 15 20:28:51 2015 +0300" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:05 2015 +0800" }, "message": "bridge: fix br_stp_set_bridge_priority race conditions\n\ncommit 2dab80a8b486f02222a69daca6859519e05781d9 upstream.\n\nAfter the -\u003eset() spinlocks were removed br_stp_set_bridge_priority\nwas left running without any protection when used via sysfs. It can\nrace with port add/del and could result in use-after-free cases and\ncorrupted lists. Tested by running port add/del in a loop with stp\nenabled while setting priority in a loop, crashes are easily\nreproducible.\nThe spinlocks around sysfs -\u003eset() were removed in commit:\n14f98f258f19 (\"bridge: range check STP parameters\")\nThere\u0027s also a race condition in the netlink priority support that is\nfixed by this change, but it was introduced recently and the fixes tag\ncovers it, just in case it\u0027s needed the commit is:\naf615762e972 (\"bridge: add ageing_time, stp_state, priority over netlink\")\n\nSigned-off-by: Nikolay Aleksandrov \u003crazor@blackwall.org\u003e\nFixes: 14f98f258f19 (\"bridge: range check STP parameters\")\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "aef2b5342c1c17abbcd068d25ce5c48e6b43a5f8", "tree": "438da77f4c6bb8c0644f66e667be2093ef31afc5", "parents": [ "c4b0cf56edc955b00510b36c890ca3fd78df7d67" ], "author": { "name": "Jeff Layton", "email": "jlayton@poochiereds.net", "time": "Tue Jun 09 19:43:56 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:05 2015 +0800" }, "message": "nfs: increase size of EXCHANGE_ID name string buffer\n\ncommit 764ad8ba8cd4c6f836fca9378f8c5121aece0842 upstream.\n\nThe current buffer is much too small if you have a relatively long\nhostname. Bring it up to the size of the one that SETCLIENTID has.\n\nReported-by: Michael Skralivetsky \u003cmichael.skralivetsky@primarydata.com\u003e\nSigned-off-by: Jeff Layton \u003cjeff.layton@primarydata.com\u003e\nSigned-off-by: Trond Myklebust \u003ctrond.myklebust@primarydata.com\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "c4b0cf56edc955b00510b36c890ca3fd78df7d67", "tree": "8d493b9f46173cc03fabea8972b7b7b534fad8f9", "parents": [ "5e77bfbbf12d21ac303c802ce41a5f3fa3e1ff79" ], "author": { "name": "Ding Wang", "email": "justin.wang@spreadtrum.com", "time": "Mon May 18 20:14:15 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:05 2015 +0800" }, "message": "mmc: card: Fixup request missing in mmc_blk_issue_rw_rq\n\ncommit 29535f7b797df35cc9b6b3bca635591cdd3dd2a8 upstream.\n\nThe current handler of MMC_BLK_CMD_ERR in mmc_blk_issue_rw_rq function\nmay cause new coming request permanent missing when the ongoing\nrequest (previoulsy started) complete end.\n\nThe problem scenario is as follows:\n(1) Request A is ongoing;\n(2) Request B arrived, and finally mmc_blk_issue_rw_rq() is called;\n(3) Request A encounters the MMC_BLK_CMD_ERR error;\n(4) In the error handling of MMC_BLK_CMD_ERR, suppose mmc_blk_cmd_err()\n end request A completed and return zero. Continue the error handling,\n suppose mmc_blk_reset() reset device success;\n(5) Continue the execution, while loop completed because variable ret\n is zero now;\n(6) Finally, mmc_blk_issue_rw_rq() return without processing request B.\n\nThe process related to the missing request may wait that IO request\ncomplete forever, possibly crashing the application or hanging the system.\n\nFix this issue by starting new request when reset success.\n\nSigned-off-by: Ding Wang \u003cjustin.wang@spreadtrum.com\u003e\nFixes: 67716327eec7 (\"mmc: block: add eMMC hardware reset support\")\nSigned-off-by: Ulf Hansson \u003culf.hansson@linaro.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "5e77bfbbf12d21ac303c802ce41a5f3fa3e1ff79", "tree": "d6381f0cdbb66f2f2362f029f6013f0ee3c2ba86", "parents": [ "2fe77cbcdb483b9ce541c0978fb485f31213ee23" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Sat Jun 13 15:23:33 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:05 2015 +0800" }, "message": "ideapad: fix software rfkill setting\n\ncommit 4b200b4604bec3388426159f1656109d19fadf6e upstream.\n\nThis fixes a several year old regression that I found while trying\nto get the Yoga 3 11 to work. The ideapad_rfk_set function is meant\nto send a command to the embedded controller through ACPI, but\nas of c1f73658ed, it sends the index of the rfkill device instead\nof the command, and ignores the opcode field.\n\nThis changes it back to the original behavior, which indeed\nflips the rfkill state as seen in the debugfs interface.\n\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nFixes: c1f73658ed (\"ideapad: pass ideapad_priv as argument (part 2)\")\nSigned-off-by: Darren Hart \u003cdvhart@linux.intel.com\u003e\n[lizf: Backported to 3.4: @data is not a pointer but the device idx]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "2fe77cbcdb483b9ce541c0978fb485f31213ee23", "tree": "ef04521ff912e7cd41eea5fc2541ee46d8cdf427", "parents": [ "2cd65577af5bb06910596361166f8eb1b5bbc491" ], "author": { "name": "Joseph Qi", "email": "joseph.qi@huawei.com", "time": "Mon Jun 15 14:36:01 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:04 2015 +0800" }, "message": "jbd2: fix ocfs2 corrupt when updating journal superblock fails\n\ncommit 6f6a6fda294506dfe0e3e0a253bb2d2923f28f0a upstream.\n\nIf updating journal superblock fails after journal data has been\nflushed, the error is omitted and this will mislead the caller as a\nnormal case. In ocfs2, the checkpoint will be treated successfully\nand the other node can get the lock to update. Since the sb_start is\nstill pointing to the old log block, it will rewrite the journal data\nduring journal recovery by the other node. Thus the new updates will\nbe overwritten and ocfs2 corrupts. So in above case we have to return\nthe error, and ocfs2_commit_cache will take care of the error and\nprevent the other node to do update first. And only after recovering\njournal it can do the new updates.\n\nThe issue discussion mail can be found at:\nhttps://oss.oracle.com/pipermail/ocfs2-devel/2015-June/010856.html\nhttp://comments.gmane.org/gmane.comp.file-systems.ext4/48841\n\n[ Fixed bug in patch which allowed a non-negative error return from\n jbd2_cleanup_journal_tail() to leak out of jbd2_fjournal_flush(); this\n was causing xfstests ext4/306 to fail. -- Ted ]\n\nReported-by: Yiwen Jiang \u003cjiangyiwen@huawei.com\u003e\nSigned-off-by: Joseph Qi \u003cjoseph.qi@huawei.com\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nTested-by: Yiwen Jiang \u003cjiangyiwen@huawei.com\u003e\nCc: Junxiao Bi \u003cjunxiao.bi@oracle.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "2cd65577af5bb06910596361166f8eb1b5bbc491", "tree": "b8e1dcf943d13379f083ec56b28d14f18803d329", "parents": [ "ddae448fdcf3ae53104815c724300efa837bbacd" ], "author": { "name": "Arun Chandran", "email": "achandran@mvista.com", "time": "Mon Jun 15 15:59:02 2015 +0530" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:04 2015 +0800" }, "message": "regmap: Fix regmap_bulk_read in BE mode\n\ncommit 15b8d2c41fe5839582029f65c5f7004db451cc2b upstream.\n\nIn big endian mode regmap_bulk_read gives incorrect data\nfor byte reads.\n\nThis is because memcpy of a single byte from an address\nafter full word read gives different results when\nendianness differs. ie. we get little-end in LE and big-end in BE.\n\nSigned-off-by: Arun Chandran \u003cachandran@mvista.com\u003e\nSigned-off-by: Mark Brown \u003cbroonie@kernel.org\u003e\n[lizf: Backported to 3.4: format_val() takes only two arguments]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "ddae448fdcf3ae53104815c724300efa837bbacd", "tree": "23f076519ea3540338f12b656fdc9eaf5948d3d5", "parents": [ "493d6a2da3b5206d5da2f458a5d896a6ee7ad2c5" ], "author": { "name": "Dmitry Monakhov", "email": "dmonakhov@openvz.org", "time": "Mon Jun 15 00:18:02 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:04 2015 +0800" }, "message": "jbd2: use GFP_NOFS in jbd2_cleanup_journal_tail()\n\ncommit b4f1afcd068f6e533230dfed00782cd8a907f96b upstream.\n\njbd2_cleanup_journal_tail() can be invoked by jbd2__journal_start()\nSo allocations should be done with GFP_NOFS\n\n[Full stack trace snipped from 3.10-rh7]\n[\u003cffffffff815c4bd4\u003e] dump_stack+0x19/0x1b\n[\u003cffffffff8105dba1\u003e] warn_slowpath_common+0x61/0x80\n[\u003cffffffff8105dcca\u003e] warn_slowpath_null+0x1a/0x20\n[\u003cffffffff815c2142\u003e] slab_pre_alloc_hook.isra.31.part.32+0x15/0x17\n[\u003cffffffff8119c045\u003e] kmem_cache_alloc+0x55/0x210\n[\u003cffffffff811477f5\u003e] ? mempool_alloc_slab+0x15/0x20\n[\u003cffffffff811477f5\u003e] mempool_alloc_slab+0x15/0x20\n[\u003cffffffff81147939\u003e] mempool_alloc+0x69/0x170\n[\u003cffffffff815cb69e\u003e] ? _raw_spin_unlock_irq+0xe/0x20\n[\u003cffffffff8109160d\u003e] ? finish_task_switch+0x5d/0x150\n[\u003cffffffff811f1a8e\u003e] bio_alloc_bioset+0x1be/0x2e0\n[\u003cffffffff8127ee49\u003e] blkdev_issue_flush+0x99/0x120\n[\u003cffffffffa019a733\u003e] jbd2_cleanup_journal_tail+0x93/0xa0 [jbd2] --\u003eGFP_KERNEL\n[\u003cffffffffa019aca1\u003e] jbd2_log_do_checkpoint+0x221/0x4a0 [jbd2]\n[\u003cffffffffa019afc7\u003e] __jbd2_log_wait_for_space+0xa7/0x1e0 [jbd2]\n[\u003cffffffffa01952d8\u003e] start_this_handle+0x2d8/0x550 [jbd2]\n[\u003cffffffff811b02a9\u003e] ? __memcg_kmem_put_cache+0x29/0x30\n[\u003cffffffff8119c120\u003e] ? kmem_cache_alloc+0x130/0x210\n[\u003cffffffffa019573a\u003e] jbd2__journal_start+0xba/0x190 [jbd2]\n[\u003cffffffff811532ce\u003e] ? lru_cache_add+0xe/0x10\n[\u003cffffffffa01c9549\u003e] ? ext4_da_write_begin+0xf9/0x330 [ext4]\n[\u003cffffffffa01f2c77\u003e] __ext4_journal_start_sb+0x77/0x160 [ext4]\n[\u003cffffffffa01c9549\u003e] ext4_da_write_begin+0xf9/0x330 [ext4]\n[\u003cffffffff811446ec\u003e] generic_file_buffered_write_iter+0x10c/0x270\n[\u003cffffffff81146918\u003e] __generic_file_write_iter+0x178/0x390\n[\u003cffffffff81146c6b\u003e] __generic_file_aio_write+0x8b/0xb0\n[\u003cffffffff81146ced\u003e] generic_file_aio_write+0x5d/0xc0\n[\u003cffffffffa01bf289\u003e] ext4_file_write+0xa9/0x450 [ext4]\n[\u003cffffffff811c31d9\u003e] ? pipe_read+0x379/0x4f0\n[\u003cffffffff811b93f0\u003e] do_sync_write+0x90/0xe0\n[\u003cffffffff811b9b6d\u003e] vfs_write+0xbd/0x1e0\n[\u003cffffffff811ba5b8\u003e] SyS_write+0x58/0xb0\n[\u003cffffffff815d4799\u003e] system_call_fastpath+0x16/0x1b\n\nSigned-off-by: Dmitry Monakhov \u003cdmonakhov@openvz.org\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "493d6a2da3b5206d5da2f458a5d896a6ee7ad2c5", "tree": "753621083e3dd8cc7f9e643fadf1e4b3a8735de9", "parents": [ "c33fd0601490793b937dd27209d0ec37150e1c79" ], "author": { "name": "Marcelo Ricardo Leitner", "email": "marcelo.leitner@gmail.com", "time": "Fri Jun 12 10:16:41 2015 -0300" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:04 2015 +0800" }, "message": "sctp: fix ASCONF list handling\n\ncommit 2d45a02d0166caf2627fe91897c6ffc3b19514c4 upstream.\n\n-\u003eauto_asconf_splist is per namespace and mangled by functions like\nsctp_setsockopt_auto_asconf() which doesn\u0027t guarantee any serialization.\n\nAlso, the call to inet_sk_copy_descendant() was backuping\n-\u003eauto_asconf_list through the copy but was not honoring\n-\u003edo_auto_asconf, which could lead to list corruption if it was\ndifferent between both sockets.\n\nThis commit thus fixes the list handling by using -\u003eaddr_wq_lock\nspinlock to protect the list. A special handling is done upon socket\ncreation and destruction for that. Error handlig on sctp_init_sock()\nwill never return an error after having initialized asconf, so\nsctp_destroy_sock() can be called without addrq_wq_lock. The lock now\nwill be take on sctp_close_sock(), before locking the socket, so we\ndon\u0027t do it in inverse order compared to sctp_addr_wq_timeout_handler().\n\nInstead of taking the lock on sctp_sock_migrate() for copying and\nrestoring the list values, it\u0027s preferred to avoid rewritting it by\nimplementing sctp_copy_descendant().\n\nIssue was found with a test application that kept flipping sysctl\ndefault_auto_asconf on and off, but one could trigger it by issuing\nsimultaneous setsockopt() calls on multiple sockets or by\ncreating/destroying sockets fast enough. This is only triggerable\nlocally.\n\nFixes: 9f7d653b67ae (\"sctp: Add Auto-ASCONF support (core).\")\nReported-by: Ji Jianwen \u003cjiji@redhat.com\u003e\nSuggested-by: Neil Horman \u003cnhorman@tuxdriver.com\u003e\nSuggested-by: Hannes Frederic Sowa \u003channes@stressinduktion.org\u003e\nAcked-by: Hannes Frederic Sowa \u003channes@stressinduktion.org\u003e\nSigned-off-by: Marcelo Ricardo Leitner \u003cmarcelo.leitner@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n[lizf: Backported to 3.4:\n - use global spinlock instead of per-namespace lock]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "c33fd0601490793b937dd27209d0ec37150e1c79", "tree": "01f9d33f4bc0744c5b2d134d6671914d669c2b99", "parents": [ "0c0fd01eee9d08fdedd5a9de4656c32a422844a7" ], "author": { "name": "Ryan Underwood", "email": "nemesis@icequake.net", "time": "Sun Jan 25 16:07:09 2015 -0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:04 2015 +0800" }, "message": "Disable write buffering on Toshiba ToPIC95\n\ncommit 2fb22a8042fe96b4220843f79241c116d90922c4 upstream.\n\nDisable write buffering on the Toshiba ToPIC95 if it is enabled by\nsomebody (it is not supposed to be a power-on default according to\nthe datasheet). On the ToPIC95, practically no 32-bit Cardbus card\nwill work under heavy load without locking up the whole system if\nthis is left enabled. I tried about a dozen. It does not affect\n16-bit cards. This is similar to the O2 bugs in early controller\nrevisions it seems.\n\nBugzilla: https://bugzilla.kernel.org/show_bug.cgi?id\u003d55961\nSigned-off-by: Ryan C. Underwood \u003cnemesis@icequake.net\u003e\nSigned-off-by: Dominik Brodowski \u003clinux@dominikbrodowski.net\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "0c0fd01eee9d08fdedd5a9de4656c32a422844a7", "tree": "b6f7a64d2bfff1b0510317bf22dbb5e8416b7194", "parents": [ "ae6b0bc8ea85a9dcc11fc2525e821a22ebbb7c83" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Jun 12 23:45:33 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:04 2015 +0800" }, "message": "ext4: fix race between truncate and __ext4_journalled_writepage()\n\ncommit bdf96838aea6a265f2ae6cbcfb12a778c84a0b8e upstream.\n\nThe commit cf108bca465d: \"ext4: Invert the locking order of page_lock\nand transaction start\" caused __ext4_journalled_writepage() to drop\nthe page lock before the page was written back, as part of changing\nthe locking order to jbd2_journal_start -\u003e page_lock. However, this\nintroduced a potential race if there was a truncate racing with the\ndata\u003djournalled writeback mode.\n\nFix this by grabbing the page lock after starting the journal handle,\nand then checking to see if page had gotten truncated out from under\nus.\n\nThis fixes a number of different warnings or BUG_ON\u0027s when running\nxfstests generic/086 in data\u003djournalled mode, including:\n\njbd2_journal_dirty_metadata: vdc-8: bad jh for block 115643: transaction (ee3fe7\nc0, 164), jh-\u003eb_transaction ( (null), 0), jh-\u003eb_next_transaction ( (null), 0), jlist 0\n\n\t \t \t - and -\n\nkernel BUG at /usr/projects/linux/ext4/fs/jbd2/transaction.c:2200!\n ...\nCall Trace:\n [\u003cc02b2ded\u003e] ? __ext4_journalled_invalidatepage+0x117/0x117\n [\u003cc02b2de5\u003e] __ext4_journalled_invalidatepage+0x10f/0x117\n [\u003cc02b2ded\u003e] ? __ext4_journalled_invalidatepage+0x117/0x117\n [\u003cc027d883\u003e] ? lock_buffer+0x36/0x36\n [\u003cc02b2dfa\u003e] ext4_journalled_invalidatepage+0xd/0x22\n [\u003cc0229139\u003e] do_invalidatepage+0x22/0x26\n [\u003cc0229198\u003e] truncate_inode_page+0x5b/0x85\n [\u003cc022934b\u003e] truncate_inode_pages_range+0x156/0x38c\n [\u003cc0229592\u003e] truncate_inode_pages+0x11/0x15\n [\u003cc022962d\u003e] truncate_pagecache+0x55/0x71\n [\u003cc02b913b\u003e] ext4_setattr+0x4a9/0x560\n [\u003cc01ca542\u003e] ? current_kernel_time+0x10/0x44\n [\u003cc026c4d8\u003e] notify_change+0x1c7/0x2be\n [\u003cc0256a00\u003e] do_truncate+0x65/0x85\n [\u003cc0226f31\u003e] ? file_ra_state_init+0x12/0x29\n\n\t \t \t - and -\n\nWARNING: CPU: 1 PID: 1331 at /usr/projects/linux/ext4/fs/jbd2/transaction.c:1396\nirty_metadata+0x14a/0x1ae()\n ...\nCall Trace:\n [\u003cc01b879f\u003e] ? console_unlock+0x3a1/0x3ce\n [\u003cc082cbb4\u003e] dump_stack+0x48/0x60\n [\u003cc0178b65\u003e] warn_slowpath_common+0x89/0xa0\n [\u003cc02ef2cf\u003e] ? jbd2_journal_dirty_metadata+0x14a/0x1ae\n [\u003cc0178bef\u003e] warn_slowpath_null+0x14/0x18\n [\u003cc02ef2cf\u003e] jbd2_journal_dirty_metadata+0x14a/0x1ae\n [\u003cc02d8615\u003e] __ext4_handle_dirty_metadata+0xd4/0x19d\n [\u003cc02b2f44\u003e] write_end_fn+0x40/0x53\n [\u003cc02b4a16\u003e] ext4_walk_page_buffers+0x4e/0x6a\n [\u003cc02b59e7\u003e] ext4_writepage+0x354/0x3b8\n [\u003cc02b2f04\u003e] ? mpage_release_unused_pages+0xd4/0xd4\n [\u003cc02b1b21\u003e] ? wait_on_buffer+0x2c/0x2c\n [\u003cc02b5a4b\u003e] ? ext4_writepage+0x3b8/0x3b8\n [\u003cc02b5a5b\u003e] __writepage+0x10/0x2e\n [\u003cc0225956\u003e] write_cache_pages+0x22d/0x32c\n [\u003cc02b5a4b\u003e] ? ext4_writepage+0x3b8/0x3b8\n [\u003cc02b6ee8\u003e] ext4_writepages+0x102/0x607\n [\u003cc019adfe\u003e] ? sched_clock_local+0x10/0x10e\n [\u003cc01a8a7c\u003e] ? __lock_is_held+0x2e/0x44\n [\u003cc01a8ad5\u003e] ? lock_is_held+0x43/0x51\n [\u003cc0226dff\u003e] do_writepages+0x1c/0x29\n [\u003cc0276bed\u003e] __writeback_single_inode+0xc3/0x545\n [\u003cc0277c07\u003e] writeback_sb_inodes+0x21f/0x36d\n ...\n\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "ae6b0bc8ea85a9dcc11fc2525e821a22ebbb7c83", "tree": "a4f3e153f020a5ca43cb5ea11967f91d0683ff23", "parents": [ "fbd2f7f70bc3c4a793f7133d6d4b800a054da770" ], "author": { "name": "Zidan Wang", "email": "zidan.wang@freescale.com", "time": "Thu Jun 11 19:14:36 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:04 2015 +0800" }, "message": "ASoC: wm8960: the enum of \"DAC Polarity\" should be wm8960_enum[1]\n\ncommit a077e81ec61e07a7f86997d045109f06719fbffe upstream.\n\nthe enum of \"DAC Polarity\" should be wm8960_enum[1].\n\nSigned-off-by: Zidan Wang \u003czidan.wang@freescale.com\u003e\nAcked-by: Charles Keepax \u003cckeepax@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Mark Brown \u003cbroonie@kernel.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "fbd2f7f70bc3c4a793f7133d6d4b800a054da770", "tree": "925917bcd1be59ffa66184530c445611dacf01c5", "parents": [ "61473c581da9f97ea703b8b1a693300e138456e1" ], "author": { "name": "Lior Amsalem", "email": "alior@marvell.com", "time": "Tue May 26 15:07:32 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:04 2015 +0800" }, "message": "dmaengine: mv_xor: bug fix for racing condition in descriptors cleanup\n\ncommit 9136291f1dbc1d4d1cacd2840fb35f4f3ce16c46 upstream.\n\nThis patch fixes a bug in the XOR driver where the cleanup function can be\ncalled and free descriptors that never been processed by the engine (which\nresult in data errors).\n\nThe cleanup function will free descriptors based on the ownership bit in\nthe descriptors.\n\nFixes: ff7b04796d98 (\"dmaengine: DMA engine driver for Marvell XOR engine\")\nSigned-off-by: Lior Amsalem \u003calior@marvell.com\u003e\nSigned-off-by: Maxime Ripard \u003cmaxime.ripard@free-electrons.com\u003e\nReviewed-by: Ofer Heifetz \u003coferh@marvell.com\u003e\nSigned-off-by: Vinod Koul \u003cvinod.koul@intel.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "61473c581da9f97ea703b8b1a693300e138456e1", "tree": "c27307fbfa1cf6539ed8fba4a257b33a13661c80", "parents": [ "0e782ba3f77e7474d0ea1d04a739396b2436cf54" ], "author": { "name": "Bjorn Helgaas", "email": "bhelgaas@google.com", "time": "Tue Jun 09 18:54:07 2015 -0500" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:03 2015 +0800" }, "message": "x86/PCI: Use host bridge _CRS info on Foxconn K8M890-8237A\n\ncommit 1dace0116d0b05c967d94644fc4dfe96be2ecd3d upstream.\n\nThe Foxconn K8M890-8237A has two PCI host bridges, and we can\u0027t assign\nresources correctly without the information from _CRS that tells us which\naddress ranges are claimed by which bridge. In the bugs mentioned below,\nwe incorrectly assign a sound card address (this example is from 1033299):\n\n bus: 00 index 2 [mem 0x80000000-0xfcffffffff]\n ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7f])\n pci_root PNP0A08:00: host bridge window [mem 0x80000000-0xbfefffff] (ignored)\n pci_root PNP0A08:00: host bridge window [mem 0xc0000000-0xdfffffff] (ignored)\n pci_root PNP0A08:00: host bridge window [mem 0xf0000000-0xfebfffff] (ignored)\n ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-ff])\n pci_root PNP0A08:01: host bridge window [mem 0xbff00000-0xbfffffff] (ignored)\n pci 0000:80:01.0: [1106:3288] type 0 class 0x000403\n pci 0000:80:01.0: reg 10: [mem 0xbfffc000-0xbfffffff 64bit]\n pci 0000:80:01.0: address space collision: [mem 0xbfffc000-0xbfffffff 64bit] conflicts with PCI Bus #00 [mem 0x80000000-0xfcffffffff]\n pci 0000:80:01.0: BAR 0: assigned [mem 0xfd00000000-0xfd00003fff 64bit]\n BUG: unable to handle kernel paging request at ffffc90000378000\n IP: [\u003cffffffffa0345f63\u003e] azx_create+0x37c/0x822 [snd_hda_intel]\n\nWe assigned 0xfd_0000_0000, but that is not in any of the host bridge\nwindows, and the sound card doesn\u0027t work.\n\nTurn on pci\u003duse_crs automatically for this system.\n\nLink: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/931368\nLink: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1033299\nSigned-off-by: Bjorn Helgaas \u003cbhelgaas@google.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "0e782ba3f77e7474d0ea1d04a739396b2436cf54", "tree": "7b477f5c678950e190a04f11d1b197b6cba19ea9", "parents": [ "675350c16cb51f1fc0037e60f6315830c541ca60" ], "author": { "name": "Stefan Wahren", "email": "stefan.wahren@i2se.com", "time": "Tue Jun 09 20:09:42 2015 +0000" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:03 2015 +0800" }, "message": "regulator: core: fix constraints output buffer\n\ncommit a7068e3932eee8268c4ce4e080a338ee7b8a27bf upstream.\n\nThe buffer for condtraints debug isn\u0027t big enough to hold the output\nin all cases. So fix this issue by increasing the buffer.\n\nSigned-off-by: Stefan Wahren \u003cstefan.wahren@i2se.com\u003e\nSigned-off-by: Mark Brown \u003cbroonie@kernel.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "675350c16cb51f1fc0037e60f6315830c541ca60", "tree": "df4f71440c5340fb6a4fa4680c8b5eec22715b19", "parents": [ "f3f45008bc736778bf03c7684d3cf070969e3fa7" ], "author": { "name": "Felix Fietkau", "email": "nbd@openwrt.org", "time": "Tue Jun 02 10:38:32 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:03 2015 +0800" }, "message": "ath9k: fix DMA stop sequence for AR9003+\n\ncommit 300f77c08ded96d33f492aaa02549103852f0c12 upstream.\n\nAR93xx and newer needs to stop rx before tx to avoid getting the DMA\nengine or MAC into a stuck state.\nThis should reduce/fix the occurence of \"Failed to stop Tx DMA\" logspam.\n\nSigned-off-by: Felix Fietkau \u003cnbd@openwrt.org\u003e\nSigned-off-by: Kalle Valo \u003ckvalo@codeaurora.org\u003e\n[lizf: Backported to 3.4:\n - initialize ret\n - ath_drain_all_txq() takes a second argument]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "f3f45008bc736778bf03c7684d3cf070969e3fa7", "tree": "1eb69fec9d0926ba1272a250e699f902dfe69242", "parents": [ "7de70086a6aed505182c40fafc07551b5c08b962" ], "author": { "name": "Dmitry Tunin", "email": "hanipouspilot@gmail.com", "time": "Sat Jun 06 20:29:25 2015 +0300" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:03 2015 +0800" }, "message": "ath3k: add support of 13d3:3474 AR3012 device\n\ncommit 0d0cef6183aec0fb6d0c9f00a09ff51ee086bbe2 upstream.\n\nBugLink: https://bugs.launchpad.net/bugs/1427680\n\nThis device requires new firmware files\n AthrBT_0x11020100.dfu and ramps_0x11020100_40.dfu added to\n/lib/firmware/ar3k/ that are not included in linux-firmware yet.\n\nT: Bus\u003d01 Lev\u003d01 Prnt\u003d01 Port\u003d04 Cnt\u003d01 Dev#\u003d 4 Spd\u003d12 MxCh\u003d 0\nD: Ver\u003d 1.10 Cls\u003de0(wlcon) Sub\u003d01 Prot\u003d01 MxPS\u003d64 #Cfgs\u003d 1\nP: Vendor\u003d13d3 ProdID\u003d3474 Rev\u003d00.01\nC: #Ifs\u003d 2 Cfg#\u003d 1 Atr\u003de0 MxPwr\u003d100mA\nI: If#\u003d 0 Alt\u003d 0 #EPs\u003d 3 Cls\u003de0(wlcon) Sub\u003d01 Prot\u003d01 Driver\u003dbtusb\nI: If#\u003d 1 Alt\u003d 0 #EPs\u003d 2 Cls\u003de0(wlcon) Sub\u003d01 Prot\u003d01 Driver\u003dbtusb\n\nSigned-off-by: Dmitry Tunin \u003chanipouspilot@gmail.com\u003e\nSigned-off-by: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "7de70086a6aed505182c40fafc07551b5c08b962", "tree": "b5cca10d6d0f9198b545de54b280d68787079da8", "parents": [ "a8bed8ce6e7b8ec795f3bea3edcb8211d5b96357" ], "author": { "name": "Brian King", "email": "brking@linux.vnet.ibm.com", "time": "Wed May 13 08:50:27 2015 -0500" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:03 2015 +0800" }, "message": "ipr: Increase default adapter init stage change timeout\n\ncommit 45c44b5ff9caa743ed9c2bfd44307c536c9caf1e upstream.\n\nIncrease the default init stage change timeout from 15 seconds to 30 seconds.\nThis resolves issues we have seen with some adapters not transitioning\nto the first init stage within 15 seconds, which results in adapter\ninitialization failures.\n\nSigned-off-by: Brian King \u003cbrking@linux.vnet.ibm.com\u003e\nSigned-off-by: James Bottomley \u003cJBottomley@Odin.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "a8bed8ce6e7b8ec795f3bea3edcb8211d5b96357", "tree": "58b24f188937db561f2a879ef58c30eeb5e7e54d", "parents": [ "3c868f46dd3a85f700b5c3558854ade350d716a6" ], "author": { "name": "Trond Myklebust", "email": "trond.myklebust@primarydata.com", "time": "Mon Jun 01 15:10:25 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:03 2015 +0800" }, "message": "SUNRPC: Fix a memory leak in the backchannel code\n\ncommit 88de6af24f2b48b06c514d3c3d0a8f22fafe30bd upstream.\n\nreq-\u003erq_private_buf isn\u0027t initialised when xprt_setup_backchannel calls\nxprt_free_allocation.\n\nFixes: fb7a0b9addbdb (\"nfs41: New backchannel helper routines\")\nSigned-off-by: Trond Myklebust \u003ctrond.myklebust@primarydata.com\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "3c868f46dd3a85f700b5c3558854ade350d716a6", "tree": "e6c28f80423a67ed4fff8c20959400f4de5b9352", "parents": [ "9fdaa2147db4599620563aba79e99dedc15aacf7" ], "author": { "name": "Chuck Lever", "email": "chuck.lever@oracle.com", "time": "Tue May 26 11:53:52 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:03 2015 +0800" }, "message": "NFS: Fix size of NFSACL SETACL operations\n\ncommit d683cc49daf7c5afca8cd9654aaa1bf63cdf2ad9 upstream.\n\nWhen encoding the NFSACL SETACL operation, reserve just the estimated\nsize of the ACL rather than a fixed maximum. This eliminates needless\nzero padding on the wire that the server ignores.\n\nFixes: ee5dc7732bd5 (\u0027NFS: Fix \"kernel BUG at fs/nfs/nfs3xdr.c:1338!\"\u0027)\nSigned-off-by: Chuck Lever \u003cchuck.lever@oracle.com\u003e\nSigned-off-by: Trond Myklebust \u003ctrond.myklebust@primarydata.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "9fdaa2147db4599620563aba79e99dedc15aacf7", "tree": "0279e41f1113331a0683d9ba0a56ea6f1fa2f420", "parents": [ "0a6a23a3cc4bf60c6fd1fa7070b3af7757b05cdd" ], "author": { "name": "Olga Kornievskaia", "email": "kolga@netapp.com", "time": "Fri May 15 11:45:31 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:03 2015 +0800" }, "message": "fixing infinite OPEN loop in 4.0 stateid recovery\n\ncommit e8d975e73e5fa05f983fbf2723120edcf68e0b38 upstream.\n\nProblem: When an operation like WRITE receives a BAD_STATEID, even though\nrecovery code clears the RECLAIM_NOGRACE recovery flag before recovering\nthe open state, because of clearing delegation state for the associated\ninode, nfs_inode_find_state_and_recover() gets called and it makes the\nsame state with RECLAIM_NOGRACE flag again. As a results, when we restart\nlooking over the open states, we end up in the infinite loop instead of\nbreaking out in the next test of state flags.\n\nSolution: unset the RECLAIM_NOGRACE set because of\ncalling of nfs_inode_find_state_and_recover() after returning from calling\nrecover_open() function.\n\nSigned-off-by: Olga Kornievskaia \u003ckolga@netapp.com\u003e\nSigned-off-by: Trond Myklebust \u003ctrond.myklebust@primarydata.com\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "0a6a23a3cc4bf60c6fd1fa7070b3af7757b05cdd", "tree": "cfe0834385b61414e52da0313277bc7f94b77e98", "parents": [ "f8c1d2aa8f5e14dfcf4c5c3e31ea4dd3812f072f" ], "author": { "name": "Robert Schlabbach", "email": "Robert.Schlabbach@gmx.net", "time": "Tue May 26 00:27:30 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:03 2015 +0800" }, "message": "usb: core: Fix USB 3.0 devices lost in NOTATTACHED state after a hub port reset\n\ncommit fb6d1f7df5d25299fd7b3e84b72b8851d3634764 upstream.\n\nFix USB 3.0 devices lost in NOTATTACHED state after a hub port reset.\n\nDissolve the function hub_port_finish_reset() completely and divide the\nactions to be taken into those which need to be done after each reset\nattempt and those which need to be done after the full procedure is\ncomplete, and place them in the appropriate places in hub_port_reset().\nAlso, remove an unneeded forward declaration of hub_port_reset().\n\nVerbose Problem Description:\n\nUSB 3.0 devices may be \"lost for good\" during a hub port reset.\nThis makes Linux unable to boot from USB 3.0 devices in certain\nconstellations of host controllers and devices, because the USB device is\nlost during initialization, preventing the rootfs from being mounted.\n\nThe underlying problem is that in the affected constellations, during the\nprocessing inside hub_port_reset(), the hub link state goes from 0 to\nSS.inactive after the initial reset, and back to 0 again only after the\nfollowing \"warm\" reset.\n\nHowever, hub_port_finish_reset() is called after each reset attempt and\nsets the state the connected USB device based on the \"preliminary\" status\nof the hot reset to USB_STATE_NOTATTACHED due to SS.inactive, yet when\nthe following warm reset is complete and hub_port_finish_reset() is\ncalled again, its call to set the device to USB_STATE_DEFAULT is blocked\nby usb_set_device_state() which does not allow taking USB devices out of\nUSB_STATE_NOTATTACHED state.\n\nThanks to Alan Stern for guiding me to the proper solution and how to\nsubmit it.\n\nLink: http://lkml.kernel.org/r/trinity-25981484-72a9-4d46-bf17-9c1cf9301a31-1432073240136%20()%203capp-gmx-bs27\nSigned-off-by: Robert Schlabbach \u003crobert_s@gmx.net\u003e\nAcked-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n[lizf: Backported to 3.4:\n - adjust context\n - s/usb_clear_port_feature/clear_port_feature\n - hub_port_warm_reset_required() takes only two arguments]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "f8c1d2aa8f5e14dfcf4c5c3e31ea4dd3812f072f", "tree": "c526bad239ed1f64fed9b31a08e71fa89ba21f22", "parents": [ "b716d0f38305a2bfe98379ce884e34802e2fcadf" ], "author": { "name": "Haggai Eran", "email": "haggai.eran@gmail.com", "time": "Sat May 23 23:13:51 2015 +0300" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:02 2015 +0800" }, "message": "staging: rtl8712: prevent buffer overrun in recvbuf2recvframe\n\ncommit cab462140f8a183e3cca0b51c8b59ef715cb6148 upstream.\n\nWith an RTL8191SU USB adaptor, sometimes the hints for a fragmented\npacket are set, but the packet length is too large. Allocate enough\nspace to prevent memory corruption and a resulting kernel panic [1].\n\n[1] http://www.spinics.net/lists/linux-wireless/msg136546.html\n\nSigned-off-by: Haggai Eran \u003chaggai.eran@gmail.com\u003e\nACKed-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "b716d0f38305a2bfe98379ce884e34802e2fcadf", "tree": "63eba9764f81b2aebb29bf409078764d89958c20", "parents": [ "d5ea436a754c3b117421d4896eda6bc7dddb2f4e" ], "author": { "name": "Uwe Kleine-König", "email": "u.kleine-koenig@pengutronix.de", "time": "Thu May 28 10:22:10 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:02 2015 +0800" }, "message": "mtd: dc21285: use raw spinlock functions for nw_gpio_lock\n\ncommit e5babdf928e5d0c432a8d4b99f20421ce14d1ab6 upstream.\n\nSince commit bd31b85960a7 (which is in 3.2-rc1) nw_gpio_lock is a raw spinlock\nthat needs usage of the corresponding raw functions.\n\nThis fixes:\n\n drivers/mtd/maps/dc21285.c: In function \u0027nw_en_write\u0027:\n drivers/mtd/maps/dc21285.c:41:340: warning: passing argument 1 of \u0027spinlock_check\u0027 from incompatible pointer type\n spin_lock_irqsave(\u0026nw_gpio_lock, flags);\n\n In file included from include/linux/seqlock.h:35:0,\n from include/linux/time.h:5,\n from include/linux/stat.h:18,\n from include/linux/module.h:10,\n from drivers/mtd/maps/dc21285.c:8:\n include/linux/spinlock.h:299:102: note: expected \u0027struct spinlock_t *\u0027 but argument is of type \u0027struct raw_spinlock_t *\u0027\n static inline raw_spinlock_t *spinlock_check(spinlock_t *lock)\n ^\n drivers/mtd/maps/dc21285.c:43:25: warning: passing argument 1 of \u0027spin_unlock_irqrestore\u0027 from incompatible pointer type\n spin_unlock_irqrestore(\u0026nw_gpio_lock, flags);\n ^\n In file included from include/linux/seqlock.h:35:0,\n from include/linux/time.h:5,\n from include/linux/stat.h:18,\n from include/linux/module.h:10,\n from drivers/mtd/maps/dc21285.c:8:\n include/linux/spinlock.h:370:91: note: expected \u0027struct spinlock_t *\u0027 but argument is of type \u0027struct raw_spinlock_t *\u0027\n static inline void spin_unlock_irqrestore(spinlock_t *lock, unsigned long flags)\n\nFixes: bd31b85960a7 (\"locking, ARM: Annotate low level hw locks as raw\")\nSigned-off-by: Uwe Kleine-König \u003cu.kleine-koenig@pengutronix.de\u003e\nSigned-off-by: Brian Norris \u003ccomputersforpeace@gmail.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "d5ea436a754c3b117421d4896eda6bc7dddb2f4e", "tree": "38532e817696d37308a207fcd9710f209d6321b0", "parents": [ "272bc28a42deac776c1c45a88a90559c93a015c7" ], "author": { "name": "Paul E. McKenney", "email": "paulmck@linux.vnet.ibm.com", "time": "Mon May 11 11:13:05 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:02 2015 +0800" }, "message": "rcu: Correctly handle non-empty Tiny RCU callback list with none ready\n\ncommit 6e91f8cb138625be96070b778d9ba71ce520ea7e upstream.\n\nIf, at the time __rcu_process_callbacks() is invoked, there are callbacks\nin Tiny RCU\u0027s callback list, but none of them are ready to be invoked,\nthe current list-management code will knit the non-ready callbacks out\nof the list. This can result in hangs and possibly worse. This commit\ntherefore inserts a check for there being no callbacks that can be\ninvoked immediately.\n\nThis bug is unlikely to occur -- you have to get a new callback between\nthe time rcu_sched_qs() or rcu_bh_qs() was called, but before we get to\n__rcu_process_callbacks(). It was detected by the addition of RCU-bh\ntesting to rcutorture, which in turn was instigated by Iftekhar Ahmed\u0027s\nmutation testing. Although this bug was made much more likely by\n915e8a4fe45e (rcu: Remove fastpath from __rcu_process_callbacks()), this\ndid not cause the bug, but rather made it much more probable. That\nsaid, it takes more than 40 hours of rcutorture testing, on average,\nfor this bug to appear, so this fix cannot be considered an emergency.\n\nSigned-off-by: Paul E. McKenney \u003cpaulmck@linux.vnet.ibm.com\u003e\nReviewed-by: Josh Triplett \u003cjosh@joshtriplett.org\u003e\n[lizf: Backported to 3.4: adjust filename ]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "272bc28a42deac776c1c45a88a90559c93a015c7", "tree": "075e46fbe869c780b3cfdab8c666e8838f50d839", "parents": [ "341b2be2ca6ef035e122c029282278b69409a0fa" ], "author": { "name": "Subbaraya Sundeep Bhatta", "email": "subbaraya.sundeep.bhatta@xilinx.com", "time": "Thu May 21 15:46:48 2015 +0530" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:02 2015 +0800" }, "message": "usb: dwc3: gadget: return error if command sent to DEPCMD register fails\n\ncommit 76e838c9f7765f9a6205b4d558d75a66104bc60d upstream.\n\nWe need to return error to caller if command is not sent to\ncontroller succesfully.\n\nSigned-off-by: Subbaraya Sundeep Bhatta \u003csbhatta@xilinx.com\u003e\nFixes: 72246da40f37 (usb: Introduce DesignWare USB3 DRD Driver)\nSigned-off-by: Felipe Balbi \u003cbalbi@ti.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "341b2be2ca6ef035e122c029282278b69409a0fa", "tree": "18586fc339dc482886862b5d25407d43f13a6f17", "parents": [ "c645884784fb37eceee48e7024585e580942e0c9" ], "author": { "name": "Alex Deucher", "email": "alexander.deucher@amd.com", "time": "Fri May 15 11:48:52 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:02 2015 +0800" }, "message": "drm/radeon: take the mode_config mutex when dealing with hpds (v2)\n\ncommit 39fa10f7e21574a70cecf1fed0f9b36535aa68a0 upstream.\n\nSince we are messing with state in the worker.\n\nv2: drop the changes in the mst worker\n\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "c645884784fb37eceee48e7024585e580942e0c9", "tree": "45a45b81eaf1bef49dfc611aa0021ba09c2218cd", "parents": [ "9219e070a10f0bb7f7cad215803843ed5b578245" ], "author": { "name": "Dan Carpenter", "email": "dan.carpenter@oracle.com", "time": "Thu May 14 11:37:50 2015 +0300" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:02 2015 +0800" }, "message": "rndis_wlan: harmless issue calling set_bit()\n\ncommit e3958e9d60b4570fff709f397ef5c6b8483f40f7 upstream.\n\nThese are used like:\n\n\tset_bit(WORK_LINK_UP, \u0026priv-\u003ework_pending);\n\nThe problem is that set_bit() takes the actual bit number and not a mask\nso static checkers get upset. It doesn\u0027t affect run time because we do\nit consistently, but we may as well clean it up.\n\nFixes: 6010ce07a66c (\u0027rndis_wlan: do link-down state change in worker thread\u0027)\nSigned-off-by: Dan Carpenter \u003cdan.carpenter@oracle.com\u003e\nSigned-off-by: Kalle Valo \u003ckvalo@codeaurora.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "9219e070a10f0bb7f7cad215803843ed5b578245", "tree": "1ffbee694fb08b48b5b262bd85006829f7123d50", "parents": [ "5d78b58c637847cb387c2557d2d70aa2d051844f" ], "author": { "name": "Nicolas Ferre", "email": "nicolas.ferre@atmel.com", "time": "Mon May 11 13:00:31 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:02 2015 +0800" }, "message": "tty/serial: at91: RS485 mode: 0 is valid for delay_rts_after_send\n\ncommit 8687634b7908c42eb700e0469e110e02833611d1 upstream.\n\nIn RS485 mode, we may want to set the delay_rts_after_send value to 0.\nIn the datasheet, the 0 value is said to \"disable\" the Transmitter Timeguard but\nthis is exactly the expected behavior if we want no delay...\n\nMoreover, if the value was set to non-zero value by device-tree or earlier\nioctl command, it was impossible to change it back to zero.\n\nReported-by: Sami Pietikäinen \u003cSami.Pietikainen@wapice.com\u003e\nSigned-off-by: Nicolas Ferre \u003cnicolas.ferre@atmel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "5d78b58c637847cb387c2557d2d70aa2d051844f", "tree": "5eeb09ac7bbe220fdcf18b6ea47ef8b1026af7b4", "parents": [ "5653e9020eac584e6e3f404587065d061348fdaa" ], "author": { "name": "Jesper Dangaard Brouer", "email": "brouer@redhat.com", "time": "Thu May 21 12:16:40 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:02 2015 +0800" }, "message": "pktgen: document ability to add same device to several threads\n\ncommit 2a1ddf27e8189e1d68336c55dd2f305b224ae8f1 upstream.\n\nThe pktgen.txt documentation still claimed that adding same device to\nmultiple threads were not supported, but it have been since 2008 via\ncommit e6fce5b916cd7 (\"pktgen: multiqueue etc.\").\n\nDocument this and describe the naming scheme dev@X, as the procfile name\nstill need to be unique.\n\nFixes: e6fce5b916cd7 (\"pktgen: multiqueue etc.\")\nSigned-off-by: Jesper Dangaard Brouer \u003cbrouer@redhat.com\u003e\nAcked-by: Alexei Starovoitov \u003cast@plumgrid.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "5653e9020eac584e6e3f404587065d061348fdaa", "tree": "5a06b92432e98ed124e2191924b655abb5e3a5cd", "parents": [ "9624869c0556e357fc82d525844dd9241eb11349" ], "author": { "name": "Jesper Dangaard Brouer", "email": "brouer@redhat.com", "time": "Thu May 21 12:16:11 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:02 2015 +0800" }, "message": "pktgen: adjust spacing in proc file interface output\n\ncommit d079abd181950a44cdf31daafd1662388a6c4d2e upstream.\n\nToo many spaces were introduced in commit 63adc6fb8ac0 (\"pktgen: cleanup\ncheckpatch warnings\"), thus misaligning \"src_min:\" to other columns.\n\nFixes: 63adc6fb8ac0 (\"pktgen: cleanup checkpatch warnings\")\nSigned-off-by: Jesper Dangaard Brouer \u003cbrouer@redhat.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "9624869c0556e357fc82d525844dd9241eb11349", "tree": "6b78432763c0541306d526602ef91a0d76bc54e0", "parents": [ "6eb29f1ab00d557b635caba19a112a562957e731" ], "author": { "name": "Axel Lin", "email": "axel.lin@ingics.com", "time": "Fri May 15 09:15:16 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:01 2015 +0800" }, "message": "ASoC: wm8955: Fix setting wrong register for WM8955_K_8_0_MASK bits\n\ncommit 12c350050538c7dc779c083b7342bfd20f74949c upstream.\n\nWM8955_K_8_0_MASK bits is controlled by WM8955_PLL_CONTROL_3 rather than\nWM8955_PLL_CONTROL_2.\n\nSigned-off-by: Axel Lin \u003caxel.lin@ingics.com\u003e\nAcked-by: Charles Keepax \u003cckeepax@opensource.wolfsonmicro.com\u003e\nSigned-off-by: Mark Brown \u003cbroonie@kernel.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "6eb29f1ab00d557b635caba19a112a562957e731", "tree": "782a38559be8da5c7956ef28a08fa068d5c76720", "parents": [ "228ef8e6b00f472a26a35617d539d01478b00b83" ], "author": { "name": "Axel Lin", "email": "axel.lin@ingics.com", "time": "Mon May 11 09:04:06 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:01 2015 +0800" }, "message": "ASoC: wm8903: Fix define for WM8903_VMID_RES_250K\n\ncommit ebb6ad73e645b8f2d098dd3c41d2ff0da4146a02 upstream.\n\nVMID Control 0 BIT[2:1] is VMID Divider Enable and Select\n\n00 \u003d VMID disabled (for OFF mode)\n01 \u003d 2 x 50kΩ divider (for normal operation)\n10 \u003d 2 x 250kΩ divider (for low power standby)\n11 \u003d 2 x 5kΩ divider (for fast start-up)\n\nSo WM8903_VMID_RES_250K should be 2 \u003c\u003c 1, which is 4.\n\nSigned-off-by: Axel Lin \u003caxel.lin@ingics.com\u003e\nSigned-off-by: Mark Brown \u003cbroonie@kernel.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "228ef8e6b00f472a26a35617d539d01478b00b83", "tree": "25269d686308eba56a3a170582b8fa71959c1a56", "parents": [ "17a49a2549c2828144ec542ed2a760ace1b9ef39" ], "author": { "name": "Axel Lin", "email": "axel.lin@ingics.com", "time": "Sun May 10 11:35:06 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:01 2015 +0800" }, "message": "ASoC: wm8737: Fixup setting VMID Impedance control register\n\ncommit 14ba3ec1de043260cecd9e828ea2e3a0ad302893 upstream.\n\nAccording to the datasheet:\nR10 (0Ah) VMID Impedance Control\n\nBIT 3:2 VMIDSEL DEFAULT 00\n\nDESCRIPTION: VMID impedance selection control\n00: 75kΩ output\n01: 300kΩ output\n10: 2.5kΩ output\n\nWM8737_VMIDSEL_MASK is 0xC (VMIDSEL - [3:2]),\nso it needs to left shift WM8737_VMIDSEL_SHIFT bits for setting these bits.\n\nSigned-off-by: Axel Lin \u003caxel.lin@ingics.com\u003e\nSigned-off-by: Mark Brown \u003cbroonie@kernel.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "17a49a2549c2828144ec542ed2a760ace1b9ef39", "tree": "8a7b8b8307134d8625059fd2f0cd944d03e9701d", "parents": [ "074c573dc93a7264a2222595c840a5991e5dfcfe" ], "author": { "name": "Horia Geant?", "email": "horia.geanta@freescale.com", "time": "Mon May 11 20:03:24 2015 +0300" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:01 2015 +0800" }, "message": "crypto: talitos - avoid memleak in talitos_alg_alloc()\n\ncommit 5fa7dadc898567ce14d6d6d427e7bd8ce6eb5d39 upstream.\n\nFixes: 1d11911a8c57 (\"crypto: talitos - fix warning: \u0027alg\u0027 may be used uninitialized in this function\")\nSigned-off-by: Horia Geanta \u003choria.geanta@freescale.com\u003e\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "074c573dc93a7264a2222595c840a5991e5dfcfe", "tree": "8403024ef60ad73dd5449d7de3942ae40dccfe88", "parents": [ "427841d9ea9213bd066e6b2bddba5a70bce90c6d" ], "author": { "name": "Brian Norris", "email": "computersforpeace@gmail.com", "time": "Thu May 07 17:55:16 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:01 2015 +0800" }, "message": "mtd: fix: avoid race condition when accessing mtd-\u003eusecount\n\ncommit 073db4a51ee43ccb827f54a4261c0583b028d5ab upstream.\n\nOn A MIPS 32-cores machine a BUG_ON was triggered because some acesses to\nmtd-\u003eusecount were done without taking mtd_table_mutex.\nkernel: Call Trace:\nkernel: [\u003cffffffff80401818\u003e] __put_mtd_device+0x20/0x50\nkernel: [\u003cffffffff804086f4\u003e] blktrans_release+0x8c/0xd8\nkernel: [\u003cffffffff802577e0\u003e] __blkdev_put+0x1a8/0x200\nkernel: [\u003cffffffff802579a4\u003e] blkdev_close+0x1c/0x30\nkernel: [\u003cffffffff8022006c\u003e] __fput+0xac/0x250\nkernel: [\u003cffffffff80171208\u003e] task_work_run+0xd8/0x120\nkernel: [\u003cffffffff8012c23c\u003e] work_notifysig+0x10/0x18\nkernel:\nkernel:\n Code: 2442ffff ac8202d8 000217fe \u003c00020336\u003e dc820128 10400003\n 00000000 0040f809 00000000\nkernel: ---[ end trace 080fbb4579b47a73 ]---\n\nFixed by taking the mutex in blktrans_open and blktrans_release.\n\nNote that this locking is already suggested in\ninclude/linux/mtd/blktrans.h:\n\nstruct mtd_blktrans_ops {\n...\n\t/* Called with mtd_table_mutex held; no race with add/remove */\n\tint (*open)(struct mtd_blktrans_dev *dev);\n\tvoid (*release)(struct mtd_blktrans_dev *dev);\n...\n};\n\nBut we weren\u0027t following it.\n\nOriginally reported by (and patched by) Zhang and Giuseppe,\nindependently. Improved and rewritten.\n\nReported-by: Zhang Xingcai \u003czhangxingcai@huawei.com\u003e\nReported-by: Giuseppe Cantavenera \u003cgiuseppe.cantavenera.ext@nokia.com\u003e\nTested-by: Giuseppe Cantavenera \u003cgiuseppe.cantavenera.ext@nokia.com\u003e\nAcked-by: Alexander Sverdlin \u003calexander.sverdlin@nokia.com\u003e\nSigned-off-by: Brian Norris \u003ccomputersforpeace@gmail.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "427841d9ea9213bd066e6b2bddba5a70bce90c6d", "tree": "2356fe62cd88e6ca294c94a9129653184bfb3bd4", "parents": [ "4a55c0cfdd8a8b0c39eba5e696c36c33d0879684" ], "author": { "name": "Peter Zijlstra", "email": "peterz@infradead.org", "time": "Tue May 20 15:49:48 2014 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Thu Oct 22 09:20:01 2015 +0800" }, "message": "hrtimer: Allow concurrent hrtimer_start() for self restarting timers\n\ncommit 5de2755c8c8b3a6b8414870e2c284914a2b42e4d upstream.\n\nBecause we drop cpu_base-\u003elock around calling hrtimer::function, it is\npossible for hrtimer_start() to come in between and enqueue the timer.\n\nIf hrtimer::function then returns HRTIMER_RESTART we\u0027ll hit the BUG_ON\nbecause HRTIMER_STATE_ENQUEUED will be set.\n\nSince the above is a perfectly valid scenario, remove the BUG_ON and\nmake the enqueue_hrtimer() call conditional on the timer not being\nenqueued already.\n\nNOTE: in that concurrent scenario its entirely common for both sites\nto want to modify the hrtimer, since hrtimers don\u0027t provide\nserialization themselves be sure to provide some such that the\nhrtimer::function and the hrtimer_start() caller don\u0027t both try and\nfudge the expiration state at the same time.\n\nTo that effect, add a WARN when someone tries to forward an already\nenqueued timer, the most common way to change the expiry of self\nrestarting timers. Ideally we\u0027d put the WARN in everything modifying\nthe expiry but most of that is inlines and we don\u0027t need the bloat.\n\nFixes: 2d44ae4d7135 (\"hrtimer: clean up cpu-\u003ebase locking tricks\")\nSigned-off-by: Peter Zijlstra (Intel) \u003cpeterz@infradead.org\u003e\nCc: Ben Segall \u003cbsegall@google.com\u003e\nCc: Roman Gushchin \u003cklamm@yandex-team.ru\u003e\nCc: Paul Turner \u003cpjt@google.com\u003e\nLink: http://lkml.kernel.org/r/20150415113105.GT5029@twins.programming.kicks-ass.net\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "4a55c0cfdd8a8b0c39eba5e696c36c33d0879684", "tree": "2432062233925a46ab95f86d0f167f74ea4f6765", "parents": [ "1c50a0ae29d0224bd75ff1ace8819ae1f266bf8a" ], "author": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:47 2015 +0800" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:47 2015 +0800" }, "message": "Linux 3.4.109\n" }, { "commit": "1c50a0ae29d0224bd75ff1ace8819ae1f266bf8a", "tree": "fd9d72e85257a95bb4c6248586aa3b960e8cdd67", "parents": [ "aaedb09057b05c7c9e213dc465bff5f70e708535" ], "author": { "name": "Eric Dumazet", "email": "edumazet@google.com", "time": "Sat May 30 09:16:53 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:47 2015 +0800" }, "message": "udp: fix behavior of wrong checksums\n\ncommit beb39db59d14990e401e235faf66a6b9b31240b0 upstream.\n\nWe have two problems in UDP stack related to bogus checksums :\n\n1) We return -EAGAIN to application even if receive queue is not empty.\n This breaks applications using edge trigger epoll()\n\n2) Under UDP flood, we can loop forever without yielding to other\n processes, potentially hanging the host, especially on non SMP.\n\nThis patch is an attempt to make things better.\n\nWe might in the future add extra support for rt applications\nwanting to better control time spent doing a recv() in a hostile\nenvironment. For example we could validate checksums before queuing\npackets in socket receive queue.\n\nSigned-off-by: Eric Dumazet \u003cedumazet@google.com\u003e\nCc: Willem de Bruijn \u003cwillemb@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "aaedb09057b05c7c9e213dc465bff5f70e708535", "tree": "2f2a0c645f970d5f6390ca39ee2e1fe0f2eea790", "parents": [ "a39bf4a8e29c7336c0c72652b7d0dd1cd1b13c51" ], "author": { "name": "Thomas Gleixner", "email": "tglx@linutronix.de", "time": "Fri Feb 07 20:58:41 2014 +0100" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:47 2015 +0800" }, "message": "sched: Queue RT tasks to head when prio drops\n\ncommit 81a44c5441d7f7d2c3dc9105f4d65ad0d5818617 upstream.\n\nThe following scenario does not work correctly:\n\nRunqueue of CPUx contains two runnable and pinned tasks:\n\n T1: SCHED_FIFO, prio 80\n T2: SCHED_FIFO, prio 80\n\nT1 is on the cpu and executes the following syscalls (classic priority\nceiling scenario):\n\n sys_sched_setscheduler(pid(T1), SCHED_FIFO, .prio \u003d 90);\n ...\n sys_sched_setscheduler(pid(T1), SCHED_FIFO, .prio \u003d 80);\n ...\n\nNow T1 gets preempted by T3 (SCHED_FIFO, prio 95). After T3 goes back\nto sleep the scheduler picks T2. Surprise!\n\nThe same happens w/o actual preemption when T1 is forced into the\nscheduler due to a sporadic NEED_RESCHED event. The scheduler invokes\npick_next_task() which returns T2. So T1 gets preempted and scheduled\nout.\n\nThis happens because sched_setscheduler() dequeues T1 from the prio 90\nlist and then enqueues it on the tail of the prio 80 list behind T2.\nThis violates the POSIX spec and surprises user space which relies on\nthe guarantee that SCHED_FIFO tasks are not scheduled out unless they\ngive the CPU up voluntarily or are preempted by a higher priority\ntask. In the latter case the preempted task must get back on the CPU\nafter the preempting task schedules out again.\n\nWe fixed a similar issue already in commit 60db48c (sched: Queue a\ndeboosted task to the head of the RT prio queue). The same treatment\nis necessary for sched_setscheduler(). So enqueue to head of the prio\nbucket list if the priority of the task is lowered.\n\nIt might be possible that existing user space relies on the current\nbehaviour, but it can be considered highly unlikely due to the corner\ncase nature of the application scenario.\n\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Sebastian Andrzej Siewior \u003cbigeasy@linutronix.de\u003e\nSigned-off-by: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nLink: http://lkml.kernel.org/r/1391803122-4425-6-git-send-email-bigeasy@linutronix.de\nSigned-off-by: Ingo Molnar \u003cmingo@kernel.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "a39bf4a8e29c7336c0c72652b7d0dd1cd1b13c51", "tree": "4396d632f68bf748a6bcddbeb82bfe16d52b6b9b", "parents": [ "bee5f3e274eef419680b1349540a9d8032c99289" ], "author": { "name": "Ben Hutchings", "email": "ben@decadent.org.uk", "time": "Mon Jun 15 03:51:55 2015 +0100" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:47 2015 +0800" }, "message": "pipe: iovec: Fix memory corruption when retrying atomic copy as non-atomic\n\npipe_iov_copy_{from,to}_user() may be tried twice with the same iovec,\nthe first time atomically and the second time not. The second attempt\nneeds to continue from the iovec position, pipe buffer offset and\nremaining length where the first attempt failed, but currently the\npipe buffer offset and remaining length are reset. This will corrupt\nthe piped data (possibly also leading to an information leak between\nprocesses) and may also corrupt kernel memory.\n\nThis was fixed upstream by commits f0d1bec9d58d (\"new helper:\ncopy_page_from_iter()\") and 637b58c2887e (\"switch pipe_read() to\ncopy_page_to_iter()\"), but those aren\u0027t suitable for stable. This fix\nfor older kernel versions was made by Seth Jennings for RHEL and I\nhave extracted it from their update.\n\nCVE-2015-1805\n\nReferences: https://bugzilla.redhat.com/show_bug.cgi?id\u003d1202855\nSigned-off-by: Ben Hutchings \u003cben@decadent.org.uk\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "bee5f3e274eef419680b1349540a9d8032c99289", "tree": "8801d9617c76a0cc5cc24fb0e4f79e1914d917df", "parents": [ "bd3fa7572a3793590ac024de5800b98cf2a1acfc" ], "author": { "name": "Ralf Baechle", "email": "ralf@linux-mips.org", "time": "Fri Jun 19 00:46:53 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:47 2015 +0800" }, "message": "NET: ROSE: Don\u0027t dereference NULL neighbour pointer.\n\ncommit d496f7842aada20c61e6044b3395383fa972872c upstream.\n\nA ROSE socket doesn\u0027t necessarily always have a neighbour pointer so check\nif the neighbour pointer is valid before dereferencing it.\n\nSigned-off-by: Ralf Baechle \u003cralf@linux-mips.org\u003e\nTested-by: Bernard Pidoux \u003cf6bvp@free.fr\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "bd3fa7572a3793590ac024de5800b98cf2a1acfc", "tree": "7fe43cc3e6e8a379c660f1dea186cfd975a9a419", "parents": [ "59c4dd5ef990a706cde168d0feec959fbbefb85a" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Wed Jun 10 23:47:14 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:46 2015 +0800" }, "message": "block: fix ext_dev_lock lockdep report\n\ncommit 4d66e5e9b6d720d8463e11d027bd4ad91c8b1318 upstream.\n\n \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n [ INFO: inconsistent lock state ]\n 4.1.0-rc7+ #217 Tainted: G O\n ---------------------------------\n inconsistent {SOFTIRQ-ON-W} -\u003e {IN-SOFTIRQ-W} usage.\n swapper/6/0 [HC0[0]:SC1[1]:HE1:SE0] takes:\n (ext_devt_lock){+.?...}, at: [\u003cffffffff8143a60c\u003e] blk_free_devt+0x3c/0x70\n {SOFTIRQ-ON-W} state was registered at:\n [\u003cffffffff810bf6b1\u003e] __lock_acquire+0x461/0x1e70\n [\u003cffffffff810c1947\u003e] lock_acquire+0xb7/0x290\n [\u003cffffffff818ac3a8\u003e] _raw_spin_lock+0x38/0x50\n [\u003cffffffff8143a07d\u003e] blk_alloc_devt+0x6d/0xd0 \u003c-- take the lock in process context\n[..]\n [\u003cffffffff810bf64e\u003e] __lock_acquire+0x3fe/0x1e70\n [\u003cffffffff810c00ad\u003e] ? __lock_acquire+0xe5d/0x1e70\n [\u003cffffffff810c1947\u003e] lock_acquire+0xb7/0x290\n [\u003cffffffff8143a60c\u003e] ? blk_free_devt+0x3c/0x70\n [\u003cffffffff818ac3a8\u003e] _raw_spin_lock+0x38/0x50\n [\u003cffffffff8143a60c\u003e] ? blk_free_devt+0x3c/0x70\n [\u003cffffffff8143a60c\u003e] blk_free_devt+0x3c/0x70 \u003c-- take the lock in softirq\n [\u003cffffffff8143bfec\u003e] part_release+0x1c/0x50\n [\u003cffffffff8158edf6\u003e] device_release+0x36/0xb0\n [\u003cffffffff8145ac2b\u003e] kobject_cleanup+0x7b/0x1a0\n [\u003cffffffff8145aad0\u003e] kobject_put+0x30/0x70\n [\u003cffffffff8158f147\u003e] put_device+0x17/0x20\n [\u003cffffffff8143c29c\u003e] delete_partition_rcu_cb+0x16c/0x180\n [\u003cffffffff8143c130\u003e] ? read_dev_sector+0xa0/0xa0\n [\u003cffffffff810e0e0f\u003e] rcu_process_callbacks+0x2ff/0xa90\n [\u003cffffffff810e0dcf\u003e] ? rcu_process_callbacks+0x2bf/0xa90\n [\u003cffffffff81067e2e\u003e] __do_softirq+0xde/0x600\n\nNeil sees this in his tests and it also triggers on pmem driver unbind\nfor the libnvdimm tests. This fix is on top of an initial fix by Keith\nfor incorrect usage of mutex_lock() in this path: 2da78092dda1 \"block:\nFix dev_t minor allocation lifetime\". Both this and 2da78092dda1 are\ncandidates for -stable.\n\nFixes: 2da78092dda1 (\"block: Fix dev_t minor allocation lifetime\")\nCc: Keith Busch \u003ckeith.busch@intel.com\u003e\nReported-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: Jens Axboe \u003caxboe@fb.com\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "59c4dd5ef990a706cde168d0feec959fbbefb85a", "tree": "16d348a6f282951517121623d84e561278c9529b", "parents": [ "dbccb188fd76df628517b1f761c0dd3f9fa14e2e" ], "author": { "name": "Vasily Averin", "email": "vvs@parallels.com", "time": "Mon May 05 00:17:48 2014 +0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:46 2015 +0800" }, "message": "bridge: superfluous skb-\u003enfct check in br_nf_dev_queue_xmit\n\ncommit aff09ce303f83bd370772349238482ae422a2341 upstream.\n\nCurrently bridge can silently drop ipv4 fragments.\nIf node have loaded nf_defrag_ipv4 module but have no nf_conntrack_ipv4,\nbr_nf_pre_routing defragments incoming ipv4 fragments\nbut nfct check in br_nf_dev_queue_xmit does not allow re-fragment combined\npacket back, and therefore it is dropped in br_dev_queue_push_xmit without\nincrementing of any failcounters\n\nIt seems the only way to hit the ip_fragment code in the bridge xmit\npath is to have a fragment list whose reassembled fragments go over\nthe mtu. This only happens if nf_defrag is enabled. Thanks to\nFlorian Westphal for providing feedback to clarify this.\n\nDefragmentation ipv4 is required not only in conntracks but at least in\nTPROXY target and socket match, therefore #ifdef is changed from\nNF_CONNTRACK_IPV4 to NF_DEFRAG_IPV4\n\nSigned-off-by: Vasily Averin \u003cvvs@openvz.org\u003e\nSigned-off-by: Pablo Neira Ayuso \u003cpablo@netfilter.org\u003e\nCc: Kirill Tkhai \u003cktkhai@odin.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "dbccb188fd76df628517b1f761c0dd3f9fa14e2e", "tree": "0b9adaa46e2f1ff062612dc6bb1796de87729a9d", "parents": [ "e08ca6278c904bb6bbaadccdf6915b519c1fa142" ], "author": { "name": "Junling Zheng", "email": "zhengjunling@huawei.com", "time": "Mon Jun 01 09:28:00 2015 +0000" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:46 2015 +0800" }, "message": "net: socket: Fix the wrong returns for recvmsg and sendmsg\n\nBased on 08adb7dabd4874cc5666b4490653b26534702ce0 upstream.\n\nWe found that after v3.10.73, recvmsg might return -EFAULT while -EINVAL\nwas expected.\n\nWe tested it through the recvmsg01 testcase come from LTP testsuit. It set\nmsg-\u003emsg_namelen to -1 and the recvmsg syscall returned errno 14, which is\nunexpected (errno 22 is expected):\n\nrecvmsg01 4 TFAIL : invalid socket length ; returned -1 (expected -1),\nerrno 14 (expected 22)\n\nLinux mainline has no this bug for commit 08adb7dab fixes it accidentally.\nHowever, it is too large and complex to be backported to LTS 3.10.\n\nCommit 281c9c36 (net: compat: Update get_compat_msghdr() to match\ncopy_msghdr_from_user() behaviour) made get_compat_msghdr() return\nerror if msg_sys-\u003emsg_namelen was negative, which changed the behaviors\nof recvmsg and sendmsg syscall in a lib32 system:\n\nBefore commit 281c9c36, get_compat_msghdr() wouldn\u0027t fail and it would\nreturn -EINVAL in move_addr_to_user() or somewhere if msg_sys-\u003emsg_namelen\nwas invalid and then syscall returned -EINVAL, which is correct.\n\nAnd now, when msg_sys-\u003emsg_namelen is negative, get_compat_msghdr() will\nfail and wants to return -EINVAL, however, the outer syscall will return\n-EFAULT directly, which is unexpected.\n\nThis patch gets the return value of get_compat_msghdr() as well as\ncopy_msghdr_from_user(), then returns this expected value if\nget_compat_msghdr() fails.\n\nFixes: 281c9c36 (net: compat: Update get_compat_msghdr() to match copy_msghdr_from_user() behaviour)\nSigned-off-by: Junling Zheng \u003czhengjunling@huawei.com\u003e\nSigned-off-by: Hanbing Xu \u003cxuhanbing@huawei.com\u003e\nCc: Li Zefan \u003clizefan@huawei.com\u003e\nCc: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nCc: David Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "e08ca6278c904bb6bbaadccdf6915b519c1fa142", "tree": "4b196514253a9b59ec938a0dad34b8fa4c488ff0", "parents": [ "b10e02daa7abe24c0431cc7a41ead5f628839c01" ], "author": { "name": "Xie XiuQi", "email": "xiexiuqi@huawei.com", "time": "Fri Jan 24 14:00:52 2014 -0600" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:46 2015 +0800" }, "message": "ipmi: fix timeout calculation when bmc is disconnected\n\ncommit e21404dc0ac7ac971c1e36274b48bb460463f4e5 upstream.\n\nLoading ipmi_si module while bmc is disconnected, we found the timeout\nis longer than 5 secs. Actually it takes about 3 mins and 20\nsecs.(HZ\u003d250)\n\nerror message as below:\n Dec 12 19:08:59 linux kernel: IPMI BT: timeout in RD_WAIT [ ] 1 retries left\n Dec 12 19:08:59 linux kernel: BT: write 4 bytes seq\u003d0x01 03 18 00 01\n [...]\n Dec 12 19:12:19 linux kernel: IPMI BT: timeout in RD_WAIT [ ]\n Dec 12 19:12:19 linux kernel: failed 2 retries, sending error response\n Dec 12 19:12:19 linux kernel: IPMI: BT reset (takes 5 secs)\n Dec 12 19:12:19 linux kernel: IPMI BT: flag reset [ ]\n\nFunction wait_for_msg_done() use schedule_timeout_uninterruptible(1) to\nsleep 1 tick, so we should subtract jiffies_to_usecs(1) instead of 100\nusecs from timeout.\n\nReported-by: Hu Shiyuan \u003chushiyuan@huawei.com\u003e\nSigned-off-by: Xie XiuQi \u003cxiexiuqi@huawei.com\u003e\nSigned-off-by: Corey Minyard \u003ccminyard@mvista.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "b10e02daa7abe24c0431cc7a41ead5f628839c01", "tree": "37bf959f45f7fe38a8173e1267336d44da284ef8", "parents": [ "ac573c10cbf023a905dc15c5a2f91887b56ae5a7" ], "author": { "name": "Suresh Siddha", "email": "suresh.b.siddha@intel.com", "time": "Thu Sep 20 11:01:49 2012 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:46 2015 +0800" }, "message": "x86, kvm: fix kvm\u0027s usage of kernel_fpu_begin/end()\n\ncommit b1a74bf8212367be2b1d6685c11a84e056eaaaf1 upstream.\n\nPreemption is disabled between kernel_fpu_begin/end() and as such\nit is not a good idea to use these routines in kvm_load/put_guest_fpu()\nwhich can be very far apart.\n\nkvm_load/put_guest_fpu() routines are already called with\npreemption disabled and KVM already uses the preempt notifier to save\nthe guest fpu state using kvm_put_guest_fpu().\n\nSo introduce __kernel_fpu_begin/end() routines which don\u0027t touch\npreemption and use them instead of kernel_fpu_begin/end()\nfor KVM\u0027s use model of saving/restoring guest FPU state.\n\nAlso with this change (and with eagerFPU model), fix the host cr0.TS vm-exit\nstate in the case of VMX. For eagerFPU case, host cr0.TS is always clear.\nSo no need to worry about it. For the traditional lazyFPU restore case,\nchange the cr0.TS bit for the host state during vm-exit to be always clear\nand cr0.TS bit is set in the __vmx_load_host_state() when the FPU\n(guest FPU or the host task\u0027s FPU) state is not active. This ensures\nthat the host/guest FPU state is properly saved, restored\nduring context-switch and with interrupts (using irq_fpu_usable()) not\nstomping on the active FPU state.\n\nSigned-off-by: Suresh Siddha \u003csuresh.b.siddha@intel.com\u003e\nLink: http://lkml.kernel.org/r/1348164109.26695.338.camel@sbsiddha-desk.sc.intel.com\nCc: Avi Kivity \u003cavi@redhat.com\u003e\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n[xr: Backported to 3.4: Adjust context]\nSigned-off-by: Rui Xiang \u003crui.xiang@huawei.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "ac573c10cbf023a905dc15c5a2f91887b56ae5a7", "tree": "77e09a457eb6b4cc6ea0551296eff307142635ee", "parents": [ "7014d74fb26f9adbd5e275f1858c2aae16e35769" ], "author": { "name": "Suresh Siddha", "email": "suresh.b.siddha@intel.com", "time": "Fri Aug 24 14:12:59 2012 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:46 2015 +0800" }, "message": "x86, kvm: use kernel_fpu_begin/end() in kvm_load/put_guest_fpu()\n\ncommit 9c1c3fac53378c9782c18f80107965578d7b7167 upstream.\n\nkvm\u0027s guest fpu save/restore should be wrapped around\nkernel_fpu_begin/end(). This will avoid for example taking a DNA\nin kvm_load_guest_fpu() when it tries to load the fpu immediately\nafter doing unlazy_fpu() on the host side.\n\nMore importantly this will prevent the host process fpu from being\ncorrupted.\n\nSigned-off-by: Suresh Siddha \u003csuresh.b.siddha@intel.com\u003e\nLink: http://lkml.kernel.org/r/1345842782-24175-4-git-send-email-suresh.b.siddha@intel.com\nCc: Avi Kivity \u003cavi@redhat.com\u003e\nSigned-off-by: H. Peter Anvin \u003chpa@linux.intel.com\u003e\nCc: Rui Xiang \u003crui.xiang@huawei.com\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "7014d74fb26f9adbd5e275f1858c2aae16e35769", "tree": "bc5bec5127386ac5a6fd68cbc647a3157fa8c1b2", "parents": [ "842c36214f1d1715a30ede9430658411a349c839" ], "author": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Fri May 01 22:02:47 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:46 2015 +0800" }, "message": "ipv4: Missing sk_nulls_node_init() in ping_unhash().\n\ncommit a134f083e79fb4c3d0a925691e732c56911b4326 upstream.\n\nIf we don\u0027t do that, then the poison value is left in the -\u003epprev\nbacklink.\n\nThis can cause crashes if we do a disconnect, followed by a connect().\n\nTested-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nReported-by: Wen Xu \u003chotdog3645@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "842c36214f1d1715a30ede9430658411a349c839", "tree": "0cac9bb099f674c0b1021bfc3c6a8a25686014f8", "parents": [ "97186c0935bcdf8b9a72d1d7063577c845c25ef9" ], "author": { "name": "Benjamin Randazzo", "email": "benjamin@randazzo.fr", "time": "Sat Jul 25 16:36:50 2015 +0200" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:46 2015 +0800" }, "message": "md: use kzalloc() when bitmap is disabled\n\ncommit b6878d9e03043695dbf3fa1caa6dfc09db225b16 upstream.\n\nIn drivers/md/md.c get_bitmap_file() uses kmalloc() for creating a\nmdu_bitmap_file_t called \"file\".\n\n5769 file \u003d kmalloc(sizeof(*file), GFP_NOIO);\n5770 if (!file)\n5771 return -ENOMEM;\n\nThis structure is copied to user space at the end of the function.\n\n5786 if (err \u003d\u003d 0 \u0026\u0026\n5787 copy_to_user(arg, file, sizeof(*file)))\n5788 err \u003d -EFAULT\n\nBut if bitmap is disabled only the first byte of \"file\" is initialized\nwith zero, so it\u0027s possible to read some bytes (up to 4095) of kernel\nspace memory from user space. This is an information leak.\n\n5775 /* bitmap disabled, zero the first byte and copy out */\n5776 if (!mddev-\u003ebitmap_info.file)\n5777 file-\u003epathname[0] \u003d \u0027\\0\u0027;\n\nSigned-off-by: Benjamin Randazzo \u003cbenjamin@randazzo.fr\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.com\u003e\n[lizf: Backported to 3.4: fix both branches]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "97186c0935bcdf8b9a72d1d7063577c845c25ef9", "tree": "6c59e36eca02be59ce3528c2b93367629f2050f6", "parents": [ "ea1e8ee07cdf7405111cfa9236935b3da1075f56" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Wed Jan 07 13:49:08 2015 +0100" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:45 2015 +0800" }, "message": "udf: Check length of extended attributes and allocation descriptors\n\ncommit 23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 upstream.\n\nCheck length of extended attributes and allocation descriptors when\nloading inodes from disk. Otherwise corrupted filesystems could confuse\nthe code and make the kernel oops.\n\nReported-by: Carl Henrik Lunde \u003cchlunde@ping.uio.no\u003e\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\n[lizf: Backported to 3.4:\n - call make_bad_inode() and then return\n - relace bs with inode-\u003ei_sb-\u003es_blocksize]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "ea1e8ee07cdf7405111cfa9236935b3da1075f56", "tree": "92bdc9ed00dd2bb76a565de25b5e328aeade8a36", "parents": [ "c0e3f102c50b6bab71d4fe4232e45bf5c67b8be0" ], "author": { "name": "Steven Rostedt", "email": "rostedt@goodmis.org", "time": "Mon Jun 15 17:50:25 2015 -0400" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:45 2015 +0800" }, "message": "tracing: Have filter check for balanced ops\n\ncommit 2cf30dc180cea808077f003c5116388183e54f9e upstream.\n\nWhen the following filter is used it causes a warning to trigger:\n\n # cd /sys/kernel/debug/tracing\n # echo \"((dev\u003d\u003d1)blocks\u003d\u003d2)\" \u003e events/ext4/ext4_truncate_exit/filter\n-bash: echo: write error: Invalid argument\n # cat events/ext4/ext4_truncate_exit/filter\n((dev\u003d\u003d1)blocks\u003d\u003d2)\n^\nparse_error: No error\n\n ------------[ cut here ]------------\n WARNING: CPU: 2 PID: 1223 at kernel/trace/trace_events_filter.c:1640 replace_preds+0x3c5/0x990()\n Modules linked in: bnep lockd grace bluetooth ...\n CPU: 3 PID: 1223 Comm: bash Tainted: G W 4.1.0-rc3-test+ #450\n Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 v02.05 05/07/2012\n 0000000000000668 ffff8800c106bc98 ffffffff816ed4f9 ffff88011ead0cf0\n 0000000000000000 ffff8800c106bcd8 ffffffff8107fb07 ffffffff8136b46c\n ffff8800c7d81d48 ffff8800d4c2bc00 ffff8800d4d4f920 00000000ffffffea\n Call Trace:\n [\u003cffffffff816ed4f9\u003e] dump_stack+0x4c/0x6e\n [\u003cffffffff8107fb07\u003e] warn_slowpath_common+0x97/0xe0\n [\u003cffffffff8136b46c\u003e] ? _kstrtoull+0x2c/0x80\n [\u003cffffffff8107fb6a\u003e] warn_slowpath_null+0x1a/0x20\n [\u003cffffffff81159065\u003e] replace_preds+0x3c5/0x990\n [\u003cffffffff811596b2\u003e] create_filter+0x82/0xb0\n [\u003cffffffff81159944\u003e] apply_event_filter+0xd4/0x180\n [\u003cffffffff81152bbf\u003e] event_filter_write+0x8f/0x120\n [\u003cffffffff811db2a8\u003e] __vfs_write+0x28/0xe0\n [\u003cffffffff811dda43\u003e] ? __sb_start_write+0x53/0xf0\n [\u003cffffffff812e51e0\u003e] ? security_file_permission+0x30/0xc0\n [\u003cffffffff811dc408\u003e] vfs_write+0xb8/0x1b0\n [\u003cffffffff811dc72f\u003e] SyS_write+0x4f/0xb0\n [\u003cffffffff816f5217\u003e] system_call_fastpath+0x12/0x6a\n ---[ end trace e11028bd95818dcd ]---\n\nWorse yet, reading the error message (the filter again) it says that\nthere was no error, when there clearly was. The issue is that the\ncode that checks the input does not check for balanced ops. That is,\nhaving an op between a closed parenthesis and the next token.\n\nThis would only cause a warning, and fail out before doing any real\nharm, but it should still not caues a warning, and the error reported\nshould work:\n\n # cd /sys/kernel/debug/tracing\n # echo \"((dev\u003d\u003d1)blocks\u003d\u003d2)\" \u003e events/ext4/ext4_truncate_exit/filter\n-bash: echo: write error: Invalid argument\n # cat events/ext4/ext4_truncate_exit/filter\n((dev\u003d\u003d1)blocks\u003d\u003d2)\n^\nparse_error: Meaningless filter expression\n\nAnd give no kernel warning.\n\nLink: http://lkml.kernel.org/r/20150615175025.7e809215@gandalf.local.home\n\nCc: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nCc: Ingo Molnar \u003cmingo@redhat.com\u003e\nCc: Arnaldo Carvalho de Melo \u003cacme@kernel.org\u003e\nReported-by: Vince Weaver \u003cvincent.weaver@maine.edu\u003e\nTested-by: Vince Weaver \u003cvincent.weaver@maine.edu\u003e\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\n[lizf: Backported to 3.4: remove the check for OP_NOT, as it\u0027s not supported.]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "c0e3f102c50b6bab71d4fe4232e45bf5c67b8be0", "tree": "adfffc6cdcc1bb5156b9123260bd3407849bc7c2", "parents": [ "501e81d5d6b9434037851749c6194bf3a237b281" ], "author": { "name": "Wang Long", "email": "long.wanglong@huawei.com", "time": "Wed Jun 10 08:12:37 2015 +0000" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:45 2015 +0800" }, "message": "ring-buffer-benchmark: Fix the wrong sched_priority of producer\n\ncommit 108029323910c5dd1ef8fa2d10da1ce5fbce6e12 upstream.\n\nThe producer should be used producer_fifo as its sched_priority,\nso correct it.\n\nLink: http://lkml.kernel.org/r/1433923957-67842-1-git-send-email-long.wanglong@huawei.com\n\nSigned-off-by: Wang Long \u003clong.wanglong@huawei.com\u003e\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "501e81d5d6b9434037851749c6194bf3a237b281", "tree": "9c622a22b2974be516a02db2a05ce4237d6e53b9", "parents": [ "4845c5376dbbf46853b53d5241fbe4d4a2c94b59" ], "author": { "name": "Nikolay Aleksandrov", "email": "razor@blackwall.org", "time": "Tue Jun 09 10:23:57 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:45 2015 +0800" }, "message": "bridge: fix multicast router rlist endless loop\n\ncommit 1a040eaca1a22f8da8285ceda6b5e4a2cb704867 upstream.\n\nSince the addition of sysfs multicast router support if one set\nmulticast_router to \"2\" more than once, then the port would be added to\nthe hlist every time and could end up linking to itself and thus causing an\nendless loop for rlist walkers.\nSo to reproduce just do:\necho 2 \u003e multicast_router; echo 2 \u003e multicast_router;\nin a bridge port and let some igmp traffic flow, for me it hangs up\nin br_multicast_flood().\nFix this by adding a check in br_multicast_add_router() if the port is\nalready linked.\nThe reason this didn\u0027t happen before the addition of multicast_router\nsysfs entries is because there\u0027s a !hlist_unhashed check that prevents\nit.\n\nSigned-off-by: Nikolay Aleksandrov \u003crazor@blackwall.org\u003e\nFixes: 0909e11758bd (\"bridge: Add multicast_router sysfs entries\")\nAcked-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "4845c5376dbbf46853b53d5241fbe4d4a2c94b59", "tree": "1f4fa836cc5d606220ae6fbc5b39d57671cd3c54", "parents": [ "0b6afbdd165890743b64c57c07cbc4e6e3174b35" ], "author": { "name": "Nikolay Aleksandrov", "email": "nikolay@cumulusnetworks.com", "time": "Sat Jun 06 06:49:00 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:45 2015 +0800" }, "message": "bridge: disable softirqs around br_fdb_update to avoid lockup\n\ncommit c4c832f89dc468cf11dc0dd17206bace44526651 upstream.\n\nbr_fdb_update() can be called in process context in the following way:\nbr_fdb_add() -\u003e __br_fdb_add() -\u003e br_fdb_update() (if NTF_USE flag is set)\nso we need to disable softirqs because there are softirq users of the\nhash_lock. One easy way to reproduce this is to modify the bridge utility\nto set NTF_USE, enable stp and then set maxageing to a low value so\nbr_fdb_cleanup() is called frequently and then just add new entries in\na loop. This happens because br_fdb_cleanup() is called from timer/softirq\ncontext. The spin locks in br_fdb_update were _bh before commit f8ae737deea1\n(\"[BRIDGE]: forwarding remove unneeded preempt and bh diasables\")\nand at the time that commit was correct because br_fdb_update() couldn\u0027t be\ncalled from process context, but that changed after commit:\n292d1398983f (\"bridge: add NTF_USE support\")\nUsing local_bh_disable/enable around br_fdb_update() allows us to keep\nusing the spin_lock/unlock in br_fdb_update for the fast-path.\n\nSigned-off-by: Nikolay Aleksandrov \u003cnikolay@cumulusnetworks.com\u003e\nFixes: 292d1398983f (\"bridge: add NTF_USE support\")\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "0b6afbdd165890743b64c57c07cbc4e6e3174b35", "tree": "dc01ced7c4f20a848e2a5ee93bd128f3d82755fe", "parents": [ "a5c75be0e779d38c970b4a2129c238a5bab0dad4" ], "author": { "name": "Wilson Kok", "email": "wkok@cumulusnetworks.com", "time": "Fri Jun 05 00:52:57 2015 -0700" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:45 2015 +0800" }, "message": "bridge: use _bh spinlock variant for br_fdb_update to avoid lockup\n\ncommit 1d7c49037b12016e7056b9f2c990380e2187e766 upstream.\n\nbr_fdb_update() can be called in process context in the following way:\nbr_fdb_add() -\u003e __br_fdb_add() -\u003e br_fdb_update() (if NTF_USE flag is set)\nso we need to use spin_lock_bh because there are softirq users of the\nhash_lock. One easy way to reproduce this is to modify the bridge utility\nto set NTF_USE, enable stp and then set maxageing to a low value so\nbr_fdb_cleanup() is called frequently and then just add new entries in\na loop. This happens because br_fdb_cleanup() is called from timer/softirq\ncontext. These locks were _bh before commit f8ae737deea1\n(\"[BRIDGE]: forwarding remove unneeded preempt and bh diasables\")\nand at the time that commit was correct because br_fdb_update() couldn\u0027t be\ncalled from process context, but that changed after commit:\n292d1398983f (\"bridge: add NTF_USE support\")\n\nSigned-off-by: Wilson Kok \u003cwkok@cumulusnetworks.com\u003e\nSigned-off-by: Nikolay Aleksandrov \u003cnikolay@cumulusnetworks.com\u003e\nFixes: 292d1398983f (\"bridge: add NTF_USE support\")\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" }, { "commit": "a5c75be0e779d38c970b4a2129c238a5bab0dad4", "tree": "dfc7c22f0e5ef1404df9acefe506042898b804b9", "parents": [ "80de203ba1cd3401e8ad7e0044f86c5dc7da3a26" ], "author": { "name": "James Hogan", "email": "james.hogan@imgtec.com", "time": "Thu Jun 04 13:25:27 2015 +0100" }, "committer": { "name": "Zefan Li", "email": "lizefan@huawei.com", "time": "Fri Sep 18 09:20:45 2015 +0800" }, "message": "MIPS: Fix enabling of DEBUG_STACKOVERFLOW\n\ncommit 5f35b9cd553fd64415b563497d05a563c988dbd6 upstream.\n\nCommit 334c86c494b9 (\"MIPS: IRQ: Add stackoverflow detection\") added\nkernel stack overflow detection, however it only enabled it conditional\nupon the preprocessor definition DEBUG_STACKOVERFLOW, which is never\nactually defined. The Kconfig option is called DEBUG_STACKOVERFLOW,\nwhich manifests to the preprocessor as CONFIG_DEBUG_STACKOVERFLOW, so\nswitch it to using that definition instead.\n\nFixes: 334c86c494b9 (\"MIPS: IRQ: Add stackoverflow detection\")\nSigned-off-by: James Hogan \u003cjames.hogan@imgtec.com\u003e\nCc: Ralf Baechle \u003cralf@linux-mips.org\u003e\nCc: Adam Jiang \u003cjiang.adam@gmail.com\u003e\nCc: linux-mips@linux-mips.org\nPatchwork: http://patchwork.linux-mips.org/patch/10531/\nSigned-off-by: Ralf Baechle \u003cralf@linux-mips.org\u003e\nSigned-off-by: Zefan Li \u003clizefan@huawei.com\u003e\n" } ], "next": "80de203ba1cd3401e8ad7e0044f86c5dc7da3a26" }