{"shas":[["c6914a6f261aca0c9f715f883a353ae7ff51fe83","d5ec0d24602845f6f4b6a35ef729998d1fba5507@redhat.com","can: Add missing socket check in can/bcm release.\n\nWe can get here with a NULL socket argument passed from userspace,\nso we need to handle it accordingly.\n\nSigned-off-by: Dave Jones <davej@redhat.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","Dave Jones"],["2b7da309ffe602d222558cee4d7e407b96e34b3a","1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.de","md/raid5: remove setting of ->queue_lock\n\nWe previously needed to set ->queue_lock to match the raid5\ndevice_lock so we could safely use queue_flag_* operations (e.g. for\nplugging). which test the ->queue_lock is in fact locked.\n\nHowever that need has completely gone away and is unlikely to come\nback to remove this now-pointless setting.\n\nSigned-off-by: NeilBrown <neilb@suse.de>","NeilBrown"],["3b71bd9337b404baab5c894e066be6b6bf51b1c3","1c00aa603bb92d594c03cff60ecf8e63b2a5bcb1@suse.de","md: Fix dev_sectors on takeover from raid0 to raid4/5\n\nA raid0 array doesn't set 'dev_sectors' as each device might\ncontribute a different number of sectors.\nSo when converting to a RAID4 or RAID5 we need to set dev_sectors\nas they need the number.\nWe have already verified that in fact all devices do contribute\nthe same number of sectors, so use that number.\n\nSigned-off-by: NeilBrown <neilb@suse.de>","NeilBrown"],["fee68723cf6ae00082f70f3eff17fceab2a4f7d7","64c24233a9d187fa82054a1fc6c921727c74711c@intel.com","md: Cleanup after raid45->raid0 takeover\n\nProblem:\nAfter raid4->raid0 takeover operation, another takeover operation\n(e.g raid0->raid10) results \"kernel oops\".\nRoot cause:\nVariables 'degraded' in mddev structure is not cleared\non raid45->raid0 takeover.\n\nThis patch reset this variable.\n\nSigned-off-by: Krzysztof Wojcik <krzysztof.wojcik@intel.com>\nSigned-off-by: NeilBrown <neilb@suse.de>","Krzysztof Wojcik"],["28a8397852011e323d16a1eecd4787d72b7b9a9e","a4536ccde6741af8e48c9e93bd72d10cf78d76ba@gmail.com","md: Update documentation for sync_min and sync_max entries\n\nlinux/Documentation/md.txt is missing description for sync_min and\nsync_max entries.\nThis patch adds description for sync_min and sync_max entries.\n\nSigned-off-by: Roman Ovchinnikov <coolthecold@gmail.com>\nSigned-off-by: NeilBrown <neilb@suse.de>","CoolCold"],["65f8da475995f667af5298c644707dbd9d646ca6","640f819c32779d18b05c5dbcea9a983fa80860c0@de.ibm.com","[S390] dasd: fix race between open and offline\n\nThe dasd_open function uses the private_data pointer of the gendisk to\nfind the dasd_block structure that matches the gendisk. When a DASD\ndevice is set offline, we set the private_data pointer of the gendisk\nto NULL and later remove the dasd_block structure, but there is still\na small race window, in which dasd_open could first read a pointer\nfrom the private_data field and then try to use it, after the structure\nhas already been freed.\nTo close this race window, we will store a pointer to the dasd_devmap\nstructure of the base device in the private_data field. The devmap\nentries are not deleted, and we already have proper locking and\nreference counting in place, so that we can safely get from a devmap\npointer to the dasd_device and dasd_block structures of the device.\n\nSigned-off-by: Stefan Weinhuber <wein@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>","Stefan Weinhuber"],["c708c57e247775928b9a6bce7b4d8d14883bf39b","91a6ce52bf23f30aed3c81da3c0c6b8e332ad699@linux.vnet.ibm.com","[S390] prng: prevent access beyond end of stack\n\nWhile initializing the state of the prng only the first 8 bytes of\nrandom data where used, the second 8 bytes were read from the memory\nafter the stack. If only 64 bytes of the kernel stack are used and\nCONFIG_DEBUG_PAGEALLOC is enabled a kernel panic may occur because of\nthe invalid page access. Use the correct multiplicator to stay within\nthe random data buffer.\n\nSigned-off-by: Jan Glauber <jang@linux.vnet.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>","Jan Glauber"],["e4c031b4f2515e9531d71c8aa779799231dbcd0c","91a6ce52bf23f30aed3c81da3c0c6b8e332ad699@linux.vnet.ibm.com","[S390] fix page table walk for changing page attributes\n\nThe page table walk for changing page attributes used the wrong\naddress for pgd/pud/pmd lookups if the range was bigger than\na pmd entry. Fix the lookup by using the correct address.\n\nSigned-off-by: Jan Glauber <jang@linux.vnet.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>","Jan Glauber"],["bffbbd2df4196a73ffdc16709866dd96eb66aad8","91a6ce52bf23f30aed3c81da3c0c6b8e332ad699@linux.vnet.ibm.com","[S390] qdio: reset error states immediately\n\nThe qdio hardware may surpress further interrupts as long as a SBAL is in\nthe error state. That can lead to unnotified data in the SBALs following\nthe error state. To prevent this behaviour change the SBAL[s] in error\nstate immediately to another program owned state so interrupts are again\nreceived for further traffic on the device.\n\nSigned-off-by: Jan Glauber <jang@linux.vnet.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>","Jan Glauber"],["e35c76cd47c244eaa7a74adaabde4d0a1cadb907","8dcf0f69152f32f23184f83357a3731522e56b9c@de.ibm.com","[S390] pfault: fix token handling\n\nf6649a7e \"[S390] cleanup lowcore access from external interrupts\" changed\nhandling of external interrupts. Instead of letting the external interrupt\nhandlers accessing the per cpu lowcore the entry code of the kernel reads\nalready all fields that are necessary and passes them to the handlers.\nThe pfault interrupt handler was incorrectly converted. It tries to\ndereference a value which used to be a pointer to a lowcore field. After\nthe conversion however it is not anymore the pointer to the field but its\ncontent. So instead of a dereference only a cast is needed to get the\ntask pointer that caused the pfault.\n\nFixes a NULL pointer dereference and a subsequent kernel crash:\n\nUnable to handle kernel pointer dereference at virtual kernel address (null)\nOops: 0004 [#1] SMP\nModules linked in: nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc\n                   loop qeth_l3 qeth vmur ccwgroup ext3 jbd mbcache dm_mod\n                   dasd_eckd_mod dasd_diag_mod dasd_mod\nCPU: 0 Not tainted 2.6.38-2-s390x #1\nProcess cron (pid: 1106, task: 000000001f962f78, ksp: 000000001fa0f9d0)\nKrnl PSW : 0404200180000000 000000000002c03e (pfault_interrupt+0xa2/0x138)\n           R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:0 CC:2 PM:0 EA:3\nKrnl GPRS: 0000000000000000 0000000000000001 0000000000000000 0000000000000001\n           000000001f962f78 0000000000518968 0000000090000002 000000001ff03280\n           0000000000000000 000000000064f000 000000001f962f78 0000000000002603\n           0000000006002603 0000000000000000 000000001ff7fe68 000000001ff7fe48\nKrnl Code: 000000000002c036: 5820d010            l       %r2,16(%r13)\n           000000000002c03a: 1832                lr      %r3,%r2\n           000000000002c03c: 1a31                ar      %r3,%r1\n          >000000000002c03e: ba23d010            cs      %r2,%r3,16(%r13)\n           000000000002c042: a744fffc            brc     4,2c03a\n           000000000002c046: a7290002            lghi    %r2,2\n           000000000002c04a: e320d0000024        stg     %r2,0(%r13)\n           000000000002c050: 07f0                bcr     15,%r0\nCall Trace:\n ([<000000001f962f78>] 0x1f962f78)\n  [<000000000001acda>] do_extint+0xf6/0x138\n  [<000000000039b6ca>] ext_no_vtime+0x30/0x34\n  [<000000007d706e04>] 0x7d706e04\nLast Breaking-Event-Address:\n  [<0000000000000000>] 0x0\n\nFor stable maintainers:\nthe first kernel which contains this bug is 2.6.37.\n\nReported-by: Stephen Powell <zlinuxman@wowway.com>\nCc: Jonathan Nieder <jrnieder@gmail.com>\nCc: stable@kernel.org\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>","Heiko Carstens"],["c7a29e56f0a3526b71e9694b403b8e2cbe9c31e5","640f819c32779d18b05c5dbcea9a983fa80860c0@de.ibm.com","[S390] dasd: check sense type in device change handler\n\nWhen evaluating sense data in dasd_eckd_check_for_device_change, we\nmust always check for the type of sense data in byte 27, bit 0, to\nmake sure that the rest of the sense data is interpreted correctly.\n\nSigned-off-by: Stefan Weinhuber <wein@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>","Stefan Weinhuber"],["9ff4cfb3fcfd48b49fdd9be7381b3be340853aa4","96dcea9914a669842a96acf1583a968a0d4d443b@de.ibm.com","[S390] kvm-390: Let kernel exit SIE instruction on work\n\nFrom: Christian Borntraeger <borntraeger@de.ibm.com>\n\nThis patch fixes the sie exit on interrupts. The low level\ninterrupt handler returns to the PSW address in pt_regs and not\nto the PSW address in the lowcore.\nWithout this fix a cpu bound guest might never leave guest state\nsince the host interrupt handler would blindly return to the\nSIE instruction, even on need_resched and friends.\n\nCc: stable@kernel.org\nSigned-off-by: Carsten Otte <cotte@de.ibm.com>\nSigned-off-by: Christian Borntraeger <borntraeger@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>","Carsten Otte"],["6f4d6dc167a001267eeff18bdea0ce3e9108c662","a10246ea2c3600c1725f8dc718f81b30cd4d07c5@linux.vnet.ibm.com","ehea: Fix a DLPAR bug on ehea_rereg_mrs().\n\nWe are currently continuing if ehea_restart_qps() fails, when we\ndo a memory DLPAR (remove or add more memory to the system).\n\nThis patch just let the NAPI disabled if the ehea_restart_qps()\nfails.\n\nSigned-off-by: Breno Leitao <leitao@linux.vnet.ibm.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","Breno Leitao"],["2430af8b7fa37ac0be102c77f9dc6ee669d24ba9","fd4a61949a28ae8cdd740d5b4a7df30899289069@suse.cz","bonding: 802.3ad - fix agg_device_up\n\nThe slave member of struct aggregator does not necessarily point\nto a slave which is part of the aggregator. It points to the\nslave structure containing the aggregator structure, while\ncompletely different slaves (or no slaves at all) may be part of\nthe aggregator.\n\nThe agg_device_up() function wrongly uses agg->slave to find the state\nof the aggregator.  Use agg->lag_ports->slave instead. The bug has\nbeen introduced by commit 4cd6fe1c6483cde93e2ec91f58b7af9c9eea51ad\n(\"bonding: fix link down handling in 802.3ad mode\").\n\nSigned-off-by: Jiri Bohac <jbohac@suse.cz>\nSigned-off-by: Jay Vosburgh <fubar@us.ibm.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","Jiri Bohac"],["24bdb0b62cc82120924762ae6bc85afc8c3f2b26","22a0c6385d750d07aa383c9f813cf6f0228657d8@eu.citrix.com","xen: do not create the extra e820 region at an addr lower than 4G\n\nDo not add the extra e820 region at a physical address lower than 4G\nbecause it breaks e820_end_of_low_ram_pfn().\n\nIt is OK for us to move the xen_extra_mem_start up and down because this\nis the index of the memory that can be ballooned in/out - it is memory\nnot available to the kernel during bootup.\n\nSigned-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>\nSigned-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>","Stefano Stabellini"],["ee176455e28469e2420032aab3db11ac2ae3eaa8","22a0c6385d750d07aa383c9f813cf6f0228657d8@eu.citrix.com","xen: mask_rw_pte: do not apply the early_ioremap checks on x86_32\n\nThe two \"is_early_ioremap_ptep\" checks in mask_rw_pte are only used on\nx86_64, in fact early_ioremap is not used at all to setup the initial\npagetable on x86_32.\nMoreover on x86_32 the two checks are wrong because the range\npgt_buf_start..pgt_buf_end initially should be mapped RW because\nthe pages in the range are not pagetable pages yet and haven't been\ncleared yet. Afterwards considering the pgt_buf_start..pgt_buf_end is\npart of the initial mapping, xen_alloc_pte is capable of turning\nthe ptes RO when they become pagetable pages.\n\nFix the issue and improve the readability of the code providing two\ndifferent implementation of mask_rw_pte for x86_32 and x86_64.\n\nSigned-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>\nSigned-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>","Stefano Stabellini"],["1574dff8996ab1ed92c09012f8038b5566fce313","fe031bd268e574c3e649d0fd7ef4a978e9d7c1cd@redhat.com","Open with O_CREAT flag set fails to open existing files on non writable directories\n\nAn open on a NFS4 share using the O_CREAT flag on an existing file for\nwhich we have permissions to open but contained in a directory with no\nwrite permissions will fail with EACCES.\n\nA tcpdump shows that the client had set the open mode to UNCHECKED which\nindicates that the file should be created if it doesn't exist and\nencountering an existing flag is not an error. Since in this case the\nfile exists and can be opened by the user, the NFS server is wrong in\nattempting to check create permissions on the parent directory.\n\nThe patch adds a conditional statement to check for create permissions\nonly if the file doesn't exist.\n\nSigned-off-by: Sachin S. Prabhu <sprabhu@redhat.com>\nSigned-off-by: J. Bruce Fields <bfields@redhat.com>","Sachin Prabhu"],["8c230d9a5b5ec7970139acb7e2d165d7a3fe9f9e","19b5733dcea388885746d36043d3568bba5b4df7@nokia.com","UBIFS: fix false space checking failure\n\nThis patch fixes UBIFS mount failure when the debugging support is enabled,\nwe are recovering from a power cut, we were first mounter R/O and we are\nre-mounting R/W. In this case we should not assume that the amount of free\nspace before we have re-mounted R/W and after are equivalent, because\nwhen we have mounted R/O the file-system is in a non-committed state so\nthe amount of free space is slightly smaller, due to the fact that we cannot\npredict the amount of free space precisely before we commit.\n\nThis patch fixes the issue by skipping the debugging check in case of\nrecovery. This issue was reported by Caizhiyong <caizhiyong@huawei.com>\nhere: http://thread.gmane.org/gmane.linux.drivers.mtd/34350/focus=34387\n\nSigned-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>\nReported-by: Caizhiyong <caizhiyong@huawei.com>\nCc: stable@kernel.org [2.6.30+]","Artem Bityutskiy"],["3eff1268994f72266b660782e87f215720c29639","4d9e23a041ac966f5316a7481300d4ae12e806fe@redhat.com","xfs: fix duplicate message output\n\nCommit 957935dc (\"xfs: fix xfs_debug warnings\" broke the logic in\n__xfs_printk(). Instead of only printing one of two possible output\nstrings based on whether the fs has a name or not, it outputs both.\nFix it to only output one message again.\n\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\nReviewed-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Alex Elder <aelder@sgi.com>","Dave Chinner"],["cf568c58eb192368f5e796df935704535b54f451","9cd9d802d23c0ed5e224beabf4ae4a5c478746ef@linaro.org","mach-ux500: fix i2c0 device setup regression\n\nAdding two sets of I2C devices to the same bus doesn't quite work,\natleast not anymore. Stash one array and determine how much of it\nshall be added instead.\n\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","Linus Walleij"]],"repo":"misham/linux-2.6","actor":"misham","ref":"refs/heads/master","size":290,"head":"5933f2ae353a93b1d3b501bc63c925531849bbc7","actor_gravatar":"6cb71342f399bfc33dd2c9f9fafaeb48","push_id":30380897}