GitHub PushEvent at 2014-03-02 13:30:31
Repository: net-next-sim
Actor: thehajime
Payload: {"shas":[["1ebf5b72dc8bfbe5e7866ee1a2eb935fc7d050e6","2a0259761cc3e88db42be5300c1579a67c77e65e@samsung.com","staging: lustre: fix GFP_ATOMIC macro usage\n\nGFP_ATOMIC is not a single gfp flag, but a macro which expands to the other\nflags and LACK of __GFP_WAIT flag. To check if caller wanted to perform an\natomic allocation, the code must test __GFP_WAIT flag presence.\n\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Marek Szyprowski",true],["52481e4b00f0f2922f2b0d3a3ee392677476c250","bc74f4f071a5a33f00ab88a6d6385b5e6638b86c@linuxhacker.ru","staging/lustre: fix compile warning with is_vmalloc_addr\n\nRecent commit 175f5475fb9c5800319da4e3c4204413d7280f5c\nintroduced this compile warning (because vaddr is unsigned long),\nso add a cast:\ndrivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c: In function ‘kiblnd_kvaddr_to_page’:\ndrivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c:532:2: warning: passing argument 1 of ‘is_vmalloc_addr’ makes pointer from integer without a cast [enabled by default]\n  if (is_vmalloc_addr(vaddr)) {\n  ^\nIn file included from drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.h:43:0,\n                 from drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c:41:\ninclude/linux/mm.h:336:59: note: expected ‘const void *’ but argument is of type ‘long unsigned int’\n static inline int is_vmalloc_addr(const void *x)\n\nSigned-off-by: Oleg Drokin <green@linuxhacker.ru>\nCC: Laura Abbott <lauraa@codeaurora.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Oleg Drokin",true],["d979f3b0a1f0b5499ab85e68cdf02b56852918b6","51565b4e5841e493fd669866e11ea3c7c0d781cc@gmail.com","Add protocol specific operation for CIFS xattrs\n\nChangeset 666753c3ef8fc88b0ddd5be4865d0aa66428ac35 added protocol\noperations for get/setxattr to avoid calling cifs operations\non smb2/smb3 mounts for xattr operations and this changeset\nadds the calls to cifs specific protocol operations for xattrs\n(in order to reenable cifs support for xattrs which was\ntemporarily disabled by the previous changeset.  We do not\nhave SMB2/SMB3 worker function for setting xattrs yet so\nthis only enables it for cifs.\n\nCCing stable since without these two small changsets (its\nsmall coreq 666753c3ef8fc88b0ddd5be4865d0aa66428ac35 is\nalso needed) calling getfattr/setfattr on smb2/smb3 mounts\ncauses problems.\n\nSigned-off-by: Steve French <smfrench@gmail.com>\nReviewed-by: Shirish Pargaonkar <spargaonkar@suse.com>\nCC: Stable <stable@kernel.org>","Steve French",true],["83e3bc23ef9ce7c03b7b4e5d3d790246ea59db3e","51565b4e5841e493fd669866e11ea3c7c0d781cc@gmail.com","retrieving CIFS ACLs when mounted with SMB2 fails dropping session\n\nThe get/set ACL xattr support for CIFS ACLs attempts to send old\ncifs dialect protocol requests even when mounted with SMB2 or later\ndialects. Sending cifs requests on an smb2 session causes problems -\nthe server drops the session due to the illegal request.\n\nThis patch makes CIFS ACL operations protocol specific to fix that.\n\nAttempting to query/set CIFS ACLs for SMB2 will now return\nEOPNOTSUPP (until we add worker routines for sending query\nACL requests via SMB2) instead of sending invalid (cifs)\nrequests.\n\nA separate followon patch will be needed to fix cifs_acl_to_fattr\n(which takes a cifs specific u16 fid so can't be abstracted\nto work with SMB2 until that is changed) and will be needed\nto fix mount problems when \"cifsacl\" is specified on mount\nwith e.g. vers=2.1\n\nSigned-off-by: Steve French <smfrench@gmail.com>\nReviewed-by: Shirish Pargaonkar <spargaonkar@suse.com>\nCC: Stable <stable@kernel.org>","Steve French",true],["aadbacc7f2f0f359bd562cb95adde3da348fb643","bc74f4f071a5a33f00ab88a6d6385b5e6638b86c@linuxhacker.ru","staging/lustre/lnet: Fix use after free in ksocknal_send\n\nCall to ksocknal_launch_packet might schedule a callback that\nmight free the just sent message, and so subsequent access to it\nvia lntmsg->msg_vmflush goes to freed memory.\n\nInstead we'll just remember if we are in the vmflush thread and\nonly restore if we happened to set mempressure flag.\n\nSigned-off-by: Oleg Drokin <oleg.drokin@intel.com>\nReviewed-on: http://review.whamcloud.com/8667\nIntel-bug-id: https://jira.hpdd.intel.com/browse/LU-4360\nReviewed-by: Liang Zhen <liang.zhen@intel.com>\nReviewed-by: Amir Shehata <amir.shehata@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Oleg Drokin",true],["910827f17496e03d23577c580e2456604caa9f35","bc74f4f071a5a33f00ab88a6d6385b5e6638b86c@linuxhacker.ru","lustre: Account for changelog_ext_rec in CR_MAXSIZE\n\nCR_MAXSIZE needs to account for an llog_changelog_rec that actually\ncontains a changelog_ext_rec structure rather than a changelog_rec.\nWith out doing so, a file size approaching the Linux kernel NAME_MAX\nlength that is renamed to a size also close to, or at, NAME_MAX will\nexceed CR_MAXSIZE and trip an assertion.\n\nSigned-off-by: Christopher J. Morrone <morrone2@llnl.gov>\nReviewed-on: http://review.whamcloud.com/6993\nIntel-bug-id: https://jira.hpdd.intel.com/browse/LU-3587\nReviewed-by: Niu Yawei <yawei.niu@intel.com>\nReviewed-by: Lai Siyao <lai.siyao@intel.com>\nReviewed-by: Oleg Drokin <oleg.drokin@intel.com>\nSigned-off-by: Oleg Drokin <oleg.drokin@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Oleg Drokin",true],["18e042f0c9cb14afa5540dc366eeefe67295d0b9","bc74f4f071a5a33f00ab88a6d6385b5e6638b86c@linuxhacker.ru","lustre: Correct KUC code max changelog msg size\n\nThe kernel to userspace communication routines (KUC) allocate\nand limit the maximum cs_buf size to CR_MAXSIZE.  However this\nfails to account for the fact that the buffer is assumed to begin\nwith a struct kuc_hdr.  To allocate and account for that space,\nwe introduce a new define, KUC_CHANGELOG_MSG_MAXSIZE.\n\nSigned-off-by: Christopher J. Morrone <morrone2@llnl.gov>\nReviewed-on: http://review.whamcloud.com/7406\nIntel-bug-id: https://jira.hpdd.intel.com/browse/LU-3587\nReviewed-by: Andreas Dilger <andreas.dilger@intel.com>\nReviewed-by: jacques-Charles Lafoucriere <jacques-charles.lafoucriere@cea.fr>\nReviewed-by: Oleg Drokin <oleg.drokin@intel.com>\nSigned-off-by: Oleg Drokin <oleg.drokin@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Oleg Drokin",true],["1ea98e4c440eb497e1af1bce31cbba261b081a7b","bc74f4f071a5a33f00ab88a6d6385b5e6638b86c@linuxhacker.ru","lustre: add myself to list of people to CC on lustre patches\n\nSigned-off-by: Oleg Drokin <oleg.drokin@intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Oleg Drokin",true],["b91619c284e53fec09d502f29c1ad7ee4766e664","eec15f2dea0e7d114bf41a5bde8a2858b8f3e893@cavium.com","staging: octeon-usb: Probe via device tree populated platform device.\n\nExtract clocking parameters from the device tree, and remove now dead\ncode and types.\n\nSigned-off-by: David Daney <david.daney@cavium.com>\nTested-by: Aaro Koskinen <aaro.koskinen@iki.fi>\nSigned-off-by: Aaro Koskinen <aaro.koskinen@iki.fi>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","David Daney",true],["fdf2f40c6cb9649e3990bc11fe0b5c155adf555a","31af38f9ca04f10a2e2bd3b840e6f43c8fe11b51@gmail.com","staging: rtl8821ae: Fixed the size of array to macro as discussed by Linus\n\nLinus Torvalds writes:\n\nIt causes an interesting warning for me:\n\ndrivers/staging/rtl8821ae/rtl8821ae/dm.c: In function\n‘rtl8821ae_dm_clear_txpower_tracking_state’:\ndrivers/staging/rtl8821ae/rtl8821ae/dm.c:487:31: warning: iteration 2u\ninvokes undefined behavior [-Waggressive-loop-optimizations]\n   rtldm->bb_swing_idx_ofdm[p] = rtldm->default_ofdm_index;\n                               ^\ndrivers/staging/rtl8821ae/rtl8821ae/dm.c:485:2: note: containing loop\n  for (p = RF90_PATH_A; p < MAX_RF_PATH; ++p) {\n  ^\n\nand gcc is entirely correct: that loop iterates from 0 to 3, and does this:\n\n                rtldm->bb_swing_idx_ofdm[p] = rtldm->default_ofdm_index;\n\nbut the bb_swing_idx_ofdm[] array only has two members. So the last\ntwo iterations will overwrite bb_swing_idx_ofdm_current and the first\nentry in bb_swing_idx_ofdm_base[].\n\nNow, the bug does seem to be benign: bb_swing_idx_ofdm_current isn't\nactually ever *used* as far as I can tell, and the first entry of\nbb_swing_idx_ofdm_base[] will have been written with that same\n\"rtldm->default_ofdm_index\" value.\n\nBut gcc is absolutely correct, and that driver needs fixing.\n\nI've pulled it and will let it be because it doesn't seem to be an\nissue in practice, but please fix it. The obvious fix would seem to\nchange the size of \"2\" to be \"MAX_RF_PATH\", but I'll abstain from\ndoing those kinds of changes in the merge when it doesn't seem to\naffect the build or functionality).\n\nReported-By: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Surendra Patil <surendra.tux@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Surendra Patil",true],["8360fb0d9c21283e6fc12c43ce9ad81d1f9cffef","7a008e9ca14f0bd5b2b4fb5bbf85c809f40f4224@samsung.com","staging/usbip: Fix vhci_hcd attach failure error message to be informative\n\nWhen attach fails due to unsupported and/or invalid bus speed, the message\nvhci_hcd prints out doesn't include any useful information as to what caused\nthe failure. Change the message to be informative and use usb_speed_string()\nto get the right speed string from usb common.\n\nSigned-off-by: Shuah Khan <shuah.kh@samsung.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Shuah Khan",true],["0010b79d56cb1d7717bf146ee59df5a625b0330b","f1b5f81e42c51b2a47410458f46e76abeabf75cc@gmail.com","Staging: ozwpan: Fix null dereference\n\nIf net_dev is NULL memcpy() will Oops.\n\nSigned-off-by: Salym Senyonga <salymsash@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Salym Senyonga",true],["ead00ddca0578aa9984e7e712024aead113e8253","4645f7897fd33786a2ee1264d590b3c400559d85@linuxfoundation.org","Revert \"Staging: dgrp: Refactor the function dgrp_receive() in drrp_net_ops.c\"\n\nThis reverts commit b73db54750482cf3910046c82a84ce8c1684dfbe.\n\nReported-by: Geert Uytterhoeven <geert@linux-m68k.org>\nReported-by: Chen Gang <gang.chen.5i5j@gmail.com>\nCc: Rashika Kheria <rashika.kheria@gmail.com>\nCc: James Hogan <james.hogan@imgtec.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Greg Kroah-Hartman",true],["55834a773fe343912b705bef8114ec93fd337188","1db9dd262beaa64f35756dd39531d9747b7778bb@arm.com","arm64: defconfig: Expand default enabled features\n\nFPGA implementations of the Cortex-A57 and Cortex-A53 are now available\nin the form of the SMM-A57 and SMM-A53 Soft Macrocell Models (SMMs) for\nVersatile Express. As these attach to a Motherboard Express V2M-P1 it\nwould be useful to have support for some V2M-P1 peripherals enabled by\ndefault.\n\nAdditionally a couple of of features have been introduced since the last\ndefconfig update (CMA, jump labels) that would be good to have enabled\nby default to ensure they are build and boot tested.\n\nThis patch updates the arm64 defconfig to enable support for these\ndevices and features. The arm64 Kconfig is modified to select\nHAVE_PATA_PLATFORM, which is required to enable support for the\nCompactFlash controller on the V2M-P1.\n\nA few options which don't need to appear in defconfig are trimmed:\n\n* BLK_DEV - selected by default\n* EXPERIMENTAL - otherwise gone from the kernel\n* MII - selected by drivers which require it\n* USB_SUPPORT - selected by default\n\nSigned-off-by: Mark Rutland <mark.rutland@arm.com>\nSigned-off-by: Catalin Marinas <catalin.marinas@arm.com>","Mark Rutland",true],["d3a874e899b073496d1fe89b6a2d1aa50870874d","a9985f635ca4eb5d7c64df6d16c76aa9811509c5@ispras.ru","staging: gdm72xx: fix leaks at failure path in gdm_usb_probe()\n\nError handling code in gdm_usb_probe() misses to deallocate\ntx_ and rx_structs and to do usb_put_dev().\n\nFound by Linux Driver Verification project (linuxtesting.org).\n\nSigned-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Alexey Khoroshilov",true],["7a081ea20e043f243b6fb9d50448cbe757fbb860","ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","staging: r8188eu: memory corruption handling long ssids\n\nWe should cap the SSID length at NDIS_802_11_LENGTH_SSID (32) characters\nto avoid memory corruption.  If the SSID is too long then I have opted\nto ignore it instead of truncating it.\n\nWe don't need to clear bssid->Ssid.Ssid[0] because this struct is\nallocated with rtw_zmalloc()\n\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nAcked-by: Larry Finger <Larry.Finger@lwfinger.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Dan Carpenter",true],["1e85c1ea1ff2a60659e790ef8ec76c7339445841","382ff55d8e07d1082d179e669636cd1552da4f36@visionengravers.com","staging: comedi: adv_pci1710: fix analog output readback value\n\nThe last value written to a analog output channel is cached in the\nprivate data of this driver for readback.\n\nCurrently, the wrong value is cached in the (*insn_write) functions.\nThe current code stores the data[n] value for readback afer the loop\nhas written all the values. At this time 'n' points past the end of\nthe data array.\n\nFix the functions by using a local variable to hold the data being\nwritten to the analog output channel. This variable is then used\nafter the loop is complete to store the readback value. The current\nvalue is retrieved before the loop in case no values are actually\nwritten..\n\nSigned-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>\nReviewed-by: Ian Abbott <abbotti@mev.co.uk>\nCc: stable <stable@vger.kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","H Hartley Sweeten",true],["ac5b705b22642208764aa784ccc47f093d0212b5","ed689b62f258aca7b8c4cfe3bd37072f12cbc0cd@codeaurora.org","staging: android: sync: Signal pt before sync_timeline object gets destroyed\n\nThere is a race condition\n\nAssume we have *one* sync_fence object, with *one* sync_pt\nwhich belongs to *one* sync_timeline, given this condition,\nsync_timeline->kref will have two counts, one for sync_timeline\n(implicit) and another for sync_pt.\n\nAssume following is the situation on CPU\n\nTheead-1 : (Thread which calls sync_timeline_destroy())\n  -> (some function calls)\n   -> sync_timeline_destory()\n    -> sync_timeline_signal() (CPU is inside this\nfunction after putting reference to sync_timeline)\n\nAt this time Thread-2 comes and does following\n\nThread-2 : (fclose on fence fd)\n> sync_fence_release() -> because of fclose() on fence object\n -> sync_fence_free()\n  -> sync_pt_free()\n   -> kref_put(&pt->parent->kref, sync_timeline_free);\n    -> sync_timeline_free() (CPU is inside this because\nthis time kref will be zero after _put)\n\nThread-2 will free sync_timeline object before Thread-1\nhas finished its work inside sync_timeline_signal.\n\nWith this change we signals all sync_pt before putting\nreference to sync_timeline object.\n\nCc: Colin Cross <ccross@android.com>\nCc: Android Kernel Team <kernel-team@android.com>\nSigned-off-by: Prakash Kamliya <pkamliya@codeaurora.org>\n[jstultz: minor commit subject tweak]\nSigned-off-by: John Stultz <john.stultz@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Prakash Kamliya",true],["8b9e418c013e8b671fc10108ab14243f0657bffd","3dd73d0ce969a322485b5ce820d32986bf35fa1b@idiap.ch","staging: lustre: fix quotactl permission denied (LU-4530)\n\nThe changes introduced in commit 4b1a25f06b30b203 (\"fix build when\nCONFIG_UIDGID_STRICT_TYPE_CHECKS is on\") got the UID check the wrong way\naround, leading to \"Permission denied\" when a regular user attempts to\nretrieve his quota (lfs quota -u ...) but allowing him to retrieve other\nusers quota.\n\nFull details at: https://jira.hpdd.intel.com/browse/LU-4530\n\nCc: Peng Tao <tao.peng@emc.com>\nCc: <stable@vger.kernel.org> # 3.12.x\nCc: <stable@vger.kernel.org> # 3.13.x\nSigned-off-by: Cédric Dufour <cedric.dufour@idiap.ch>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Cédric Dufour - Idiap Research Institute",true],["2ed22e3c3bec5b92b9aba4afdef0cc5e6d859a11","38485a4ec8a14139c43075204ae53dccb385704f@amazon.com","xen-blkback: fix memory leak when persistent grants are used\n\nCurrently shrink_free_pagepool() is called before the pages used for\npersistent grants are released via free_persistent_gnts(). This\nresults in a memory leak when a VBD that uses persistent grants is\ntorn down.\n\nCc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nCc: \"Roger Pau Monné\" <roger.pau@citrix.com>\nCc: Ian Campbell <Ian.Campbell@citrix.com>\nReviewed-by: David Vrabel <david.vrabel@citrix.com>\nCc: linux-kernel@vger.kernel.org\nCc: xen-devel@lists.xen.org\nCc: Anthony Liguori <aliguori@amazon.com>\nSigned-off-by: Matt Rushton <mrushton@amazon.com>\nSigned-off-by: Matt Wilson <msw@amazon.com>\nSigned-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>","Matt Rushton",true]],"size":1000,"ref":"refs/heads/sim-ns3-dev-branch","head":"5e2f2224800928ba8670392f22327524336aa779"}