{"push_id":839425593,"size":68,"distinct_size":1,"ref":"refs/heads/kangall-v4","head":"4c6827e9dbf15bd764c5127e58c9455f4c91b3a0","before":"a84b307792162d964530ce733254a34bb7d0090d","commits":[{"sha":"8a365df5f42e81178b9c73d53657706cf742734a","author":{"email":"3fddac958924aef220f202ca567388ddab3f14a8@infradead.org","name":"Peter Zijlstra"},"message":"hrtimer: Allow concurrent hrtimer_start() for self restarting timers\n\ncommit 5de2755c8c8b3a6b8414870e2c284914a2b42e4d upstream.\n\nBecause we drop cpu_base->lock 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'll 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't provide\nserialization themselves be sure to provide some such that the\nhrtimer::function and the hrtimer_start() caller don't 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'd put the WARN in everything modifying\nthe expiry but most of that is inlines and we don't need the bloat.\n\nFixes: 2d44ae4d7135 (\"hrtimer: clean up cpu->base locking tricks\")\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Ben Segall <bsegall@google.com>\nCc: Roman Gushchin <klamm@yandex-team.ru>\nCc: Paul Turner <pjt@google.com>\nLink: http://lkml.kernel.org/r/20150415113105.GT5029@twins.programming.kicks-ass.net\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/8a365df5f42e81178b9c73d53657706cf742734a"},{"sha":"52d67bc904c7c371d6045e7c793972aa50be19f3","author":{"email":"ac73eed4b8a8c9127255a2696c52b2e7503720b8@gmail.com","name":"Brian Norris"},"message":"mtd: fix: avoid race condition when accessing mtd->usecount\n\ncommit 073db4a51ee43ccb827f54a4261c0583b028d5ab upstream.\n\nOn A MIPS 32-cores machine a BUG_ON was triggered because some acesses to\nmtd->usecount were done without taking mtd_table_mutex.\nkernel: Call Trace:\nkernel: [<ffffffff80401818>] __put_mtd_device+0x20/0x50\nkernel: [<ffffffff804086f4>] blktrans_release+0x8c/0xd8\nkernel: [<ffffffff802577e0>] __blkdev_put+0x1a8/0x200\nkernel: [<ffffffff802579a4>] blkdev_close+0x1c/0x30\nkernel: [<ffffffff8022006c>] __fput+0xac/0x250\nkernel: [<ffffffff80171208>] task_work_run+0xd8/0x120\nkernel: [<ffffffff8012c23c>] work_notifysig+0x10/0x18\nkernel:\nkernel:\n        Code: 2442ffff  ac8202d8  000217fe <00020336> 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't following it.\n\nOriginally reported by (and patched by) Zhang and Giuseppe,\nindependently. Improved and rewritten.\n\nReported-by: Zhang Xingcai <zhangxingcai@huawei.com>\nReported-by: Giuseppe Cantavenera <giuseppe.cantavenera.ext@nokia.com>\nTested-by: Giuseppe Cantavenera <giuseppe.cantavenera.ext@nokia.com>\nAcked-by: Alexander Sverdlin <alexander.sverdlin@nokia.com>\nSigned-off-by: Brian Norris <computersforpeace@gmail.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/52d67bc904c7c371d6045e7c793972aa50be19f3"},{"sha":"85b1e1e82fbd95237661ff014cd08e8ff95990b2","author":{"email":"6135224f23789828bd8d3b771a2745286516a2b5@freescale.com","name":"Horia Geant?"},"message":"crypto: talitos - avoid memleak in talitos_alg_alloc()\n\ncommit 5fa7dadc898567ce14d6d6d427e7bd8ce6eb5d39 upstream.\n\nFixes: 1d11911a8c57 (\"crypto: talitos - fix warning: 'alg' may be used uninitialized in this function\")\nSigned-off-by: Horia Geanta <horia.geanta@freescale.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/85b1e1e82fbd95237661ff014cd08e8ff95990b2"},{"sha":"6341d5730e2690417f0141a1a4af22d3cc5109e2","author":{"email":"b6ffd6973e972cb999e8e535ab74da7fee0c035f@ingics.com","name":"Axel Lin"},"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 <axel.lin@ingics.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/6341d5730e2690417f0141a1a4af22d3cc5109e2"},{"sha":"28253f1f6774afd000ad8e3f988de4b6642441ba","author":{"email":"b6ffd6973e972cb999e8e535ab74da7fee0c035f@ingics.com","name":"Axel Lin"},"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 = VMID disabled (for OFF mode)\n01 = 2 x 50kΩ divider (for normal operation)\n10 = 2 x 250kΩ divider (for low power standby)\n11 = 2 x 5kΩ divider (for fast start-up)\n\nSo WM8903_VMID_RES_250K should be 2 << 1, which is 4.\n\nSigned-off-by: Axel Lin <axel.lin@ingics.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/28253f1f6774afd000ad8e3f988de4b6642441ba"},{"sha":"eac909e0bb0a2804b8216509096d9e42ca06c2fb","author":{"email":"b6ffd6973e972cb999e8e535ab74da7fee0c035f@ingics.com","name":"Axel Lin"},"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 <axel.lin@ingics.com>\nAcked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/eac909e0bb0a2804b8216509096d9e42ca06c2fb"},{"sha":"a4512341fe1bfafe5066e7f93b76f7150cd2a177","author":{"email":"980bdea81946be3dffddbcbbdb1b5761713ff28c@redhat.com","name":"Jesper Dangaard Brouer"},"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 <brouer@redhat.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/a4512341fe1bfafe5066e7f93b76f7150cd2a177"},{"sha":"13fc71d15cb1ec80cb5f0dc10979712acac1bf5e","author":{"email":"980bdea81946be3dffddbcbbdb1b5761713ff28c@redhat.com","name":"Jesper Dangaard Brouer"},"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 <brouer@redhat.com>\nAcked-by: Alexei Starovoitov <ast@plumgrid.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/13fc71d15cb1ec80cb5f0dc10979712acac1bf5e"},{"sha":"bd5de8e504911d7e712a034acd60df80cc79e88b","author":{"email":"45b517be0e5ec6dc3a39715767c1d18e090d39b4@atmel.com","name":"Nicolas Ferre"},"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 <Sami.Pietikainen@wapice.com>\nSigned-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/bd5de8e504911d7e712a034acd60df80cc79e88b"},{"sha":"a7d3a0423896370a61857c1d56d1730adc1b931c","author":{"email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com","name":"Dan Carpenter"},"message":"rndis_wlan: harmless issue calling set_bit()\n\ncommit e3958e9d60b4570fff709f397ef5c6b8483f40f7 upstream.\n\nThese are used like:\n\n\tset_bit(WORK_LINK_UP, &priv->work_pending);\n\nThe problem is that set_bit() takes the actual bit number and not a mask\nso static checkers get upset.  It doesn't affect run time because we do\nit consistently, but we may as well clean it up.\n\nFixes: 6010ce07a66c ('rndis_wlan: do link-down state change in worker thread')\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Kalle Valo <kvalo@codeaurora.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/a7d3a0423896370a61857c1d56d1730adc1b931c"},{"sha":"69c62729509d9c2544a90e725f130eed74981e6b","author":{"email":"08dc22c6156113f2deff178e35e3ed9b24d6af9e@amd.com","name":"Alex Deucher"},"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 <alexander.deucher@amd.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/69c62729509d9c2544a90e725f130eed74981e6b"},{"sha":"6e04b1db3f7d0a1339d4b800496561fe71c5b94f","author":{"email":"852ef8128b42a63613e8b59bfc81e54a2a35ad7a@xilinx.com","name":"Subbaraya Sundeep Bhatta"},"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 <sbhatta@xilinx.com>\nFixes: 72246da40f37 (usb: Introduce DesignWare USB3 DRD Driver)\nSigned-off-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>\n\nConflicts:\n\tdrivers/usb/dwc3/gadget.c","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/6e04b1db3f7d0a1339d4b800496561fe71c5b94f"},{"sha":"79738c3b5f5bb9f07a8d315872bb06cdbf71f6a1","author":{"email":"1e0ce936bb9b355d257bf5790d2513c3f28be22b@linux.vnet.ibm.com","name":"Paul E. McKenney"},"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's 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's\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 <paulmck@linux.vnet.ibm.com>\nReviewed-by: Josh Triplett <josh@joshtriplett.org>\n[lizf: Backported to 3.4: adjust filename ]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/79738c3b5f5bb9f07a8d315872bb06cdbf71f6a1"},{"sha":"7a39594ef612877c9b16244063e50e04cba084b7","author":{"email":"181323dd666a182bc2d953e52d0ac3ab54cd8391@pengutronix.de","name":"Uwe Kleine-König"},"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 'nw_en_write':\n  drivers/mtd/maps/dc21285.c:41:340: warning: passing argument 1 of 'spinlock_check' from incompatible pointer type\n    spin_lock_irqsave(&nw_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 'struct spinlock_t *' but argument is of type 'struct raw_spinlock_t *'\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 'spin_unlock_irqrestore' from incompatible pointer type\n    spin_unlock_irqrestore(&nw_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 'struct spinlock_t *' but argument is of type 'struct raw_spinlock_t *'\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 <u.kleine-koenig@pengutronix.de>\nSigned-off-by: Brian Norris <computersforpeace@gmail.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/7a39594ef612877c9b16244063e50e04cba084b7"},{"sha":"b44cdcb5a2354312a7482988884d20b630f0ab49","author":{"email":"950eb09aa5363d787c1def6eb81db661edcaf1be@gmail.com","name":"Haggai Eran"},"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 <haggai.eran@gmail.com>\nACKed-by: Larry Finger <Larry.Finger@lwfinger.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/b44cdcb5a2354312a7482988884d20b630f0ab49"},{"sha":"7e82a08218966299fa79a402bcc60da4ef56df2e","author":{"email":"18eed627a5a6bd4f8ddef288b6d923a7b0e298f4@gmx.net","name":"Robert Schlabbach"},"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 <robert_s@gmx.net>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\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 <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/7e82a08218966299fa79a402bcc60da4ef56df2e"},{"sha":"f16ca99d4f9bb979d9163fdc31135ac0cccd2a99","author":{"email":"cf4f46655517f93ff1397f9b2475c875481d562e@netapp.com","name":"Olga Kornievskaia"},"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 <kolga@netapp.com>\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/f16ca99d4f9bb979d9163fdc31135ac0cccd2a99"},{"sha":"5273c1f3f11b4d2b5c1300a57e07dfb6152db9b3","author":{"email":"e7d8216bf9b1956703857d0050bd04192118f43d@oracle.com","name":"Chuck Lever"},"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 ('NFS: Fix \"kernel BUG at fs/nfs/nfs3xdr.c:1338!\"')\nSigned-off-by: Chuck Lever <chuck.lever@oracle.com>\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/5273c1f3f11b4d2b5c1300a57e07dfb6152db9b3"},{"sha":"d42ed5b8cf3e3d6d582aec79bc8f0f87658be21a","author":{"email":"cc958843532c615cbd4920e868f78c7985331a5a@primarydata.com","name":"Trond Myklebust"},"message":"SUNRPC: Fix a memory leak in the backchannel code\n\ncommit 88de6af24f2b48b06c514d3c3d0a8f22fafe30bd upstream.\n\nreq->rq_private_buf isn't initialised when xprt_setup_backchannel calls\nxprt_free_allocation.\n\nFixes: fb7a0b9addbdb (\"nfs41: New backchannel helper routines\")\nSigned-off-by: Trond Myklebust <trond.myklebust@primarydata.com>\n[lizf: Backported to 3.4: adjust context]\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/d42ed5b8cf3e3d6d582aec79bc8f0f87658be21a"},{"sha":"a6981bb00ef4a5fce8c8e4c5f06eb6295ce45037","author":{"email":"bf668d4b220231d97fe248d4ae0ba63a1d887e4c@linux.vnet.ibm.com","name":"Brian King"},"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 <brking@linux.vnet.ibm.com>\nSigned-off-by: James Bottomley <JBottomley@Odin.com>\nSigned-off-by: Zefan Li <lizefan@huawei.com>","distinct":false,"url":"https://api.github.com/repos/Yuskey1989/Nexus_5/commits/a6981bb00ef4a5fce8c8e4c5f06eb6295ce45037"}]}