{"push_id":1914731941,"size":87,"distinct_size":0,"ref":"refs/heads/caf/3.10/torvalds/master","head":"8d31f80eb38819e4f2905ad21c0e8998382a08f7","before":"bfa738cf3dfae2111626650f86135f93c5ff0a22","commits":[{"sha":"d1510a2e5ab6cb3a67f1c55ca5e7a6d2c6dec340","author":{"name":"Chris Gorman","email":"ef1f84a60aefba412ed0d006575696f303c09a56@gmail.com"},"message":"i2c: mux: pinctrl: mention correct module name in Kconfig help text\n\nKconfig says the resulting module is pinctrl-i2cmux, but the module when\nbuilt is i2c-mux-pinctrl.\n\nFixes: ae58d1e40698 (\"i2c: Add generic I2C multiplexer using pinctrl API\")\nSigned-off-by: Chris Gorman <chrisjohgorman@gmail.com>\nSigned-off-by: Peter Rosin <peda@axentia.se>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/d1510a2e5ab6cb3a67f1c55ca5e7a6d2c6dec340"},{"sha":"6ab1d8da972d4c4e318607e96c5ecb32101c80f4","author":{"name":"Paolo Valente","email":"0746d5f4a6f626638aa0b8efd4c4604c7ad14e9c@linaro.org"},"message":"block, bfq: reset in_service_entity if it becomes idle\n\nBFQ implements hierarchical scheduling by representing each group of\nqueues with a generic parent entity. For each parent entity, BFQ\nmaintains an in_service_entity pointer: if one of the child entities\nhappens to be in service, in_service_entity points to it.  The\nresetting of these pointers happens only on queue expirations: when\nthe in-service queue is expired, i.e., stops to be the queue in\nservice, BFQ resets all in_service_entity pointers along the\nparent-entity path from this queue to the root entity.\n\nFunctions handling the scheduling of entities assume, naturally, that\nin-service entities are active, i.e., have pending I/O requests (or,\nas a special case, even if they have no pending requests, they are\nexpected to receive a new request very soon, with the scheduler idling\nthe storage device while waiting for such an event). Unfortunately,\nthe above resetting scheme of the in_service_entity pointers may cause\nthis assumption to be violated.  For example, the in-service queue may\nhappen to remain without requests because of a request merge. In this\ncase the queue does become idle, and all related data structures are\nupdated accordingly. But in_service_entity still points to the queue\nin the parent entity. This inconsistency may even propagate to\nhigher-level parent entities, if they happen to become idle as well,\nas a consequence of the leaf queue becoming idle. For this queue and\nparent entities, scheduling functions have an undefined behaviour,\nand, as reported, may easily lead to kernel crashes or hangs.\n\nThis commit addresses this issue by simply resetting the\nin_service_entity field also when it is detected to point to an entity\nbecoming idle (regardless of why the entity becomes idle).\n\nReported-by: Laurentiu Nicola <lnicola@dend.ro>\nSigned-off-by: Paolo Valente <paolo.valente@linaro.org>\nTested-by: Laurentiu Nicola <lnicola@dend.ro>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/6ab1d8da972d4c4e318607e96c5ecb32101c80f4"},{"sha":"46d556e6aaa0ec4dc83648ab1ca3d01dd2fa3ea3","author":{"name":"Paolo Valente","email":"0746d5f4a6f626638aa0b8efd4c4604c7ad14e9c@linaro.org"},"message":"block, bfq: consider also in_service_entity to state whether an entity is active\n\nGroups of BFQ queues are represented by generic entities in BFQ. When\na queue belonging to a parent entity is deactivated, the parent entity\nmay need to be deactivated too, in case the deactivated queue was the\nonly active queue for the parent entity. This deactivation may need to\nbe propagated upwards if the entity belongs, in its turn, to a further\nhigher-level entity, and so on. In particular, the upward propagation\nof deactivation stops at the first parent entity that remains active\neven if one of its child entities has been deactivated.\n\nTo decide whether the last non-deactivation condition holds for a\nparent entity, BFQ checks whether the field next_in_service is still\nnot NULL for the parent entity, after the deactivation of one of its\nchild entity. If it is not NULL, then there are certainly other active\nentities in the parent entity, and deactivations can stop.\n\nUnfortunately, this check misses a corner case: if in_service_entity\nis not NULL, then next_in_service may happen to be NULL, although the\nparent entity is evidently active. This happens if: 1) the entity\npointed by in_service_entity is the only active entity in the parent\nentity, and 2) according to the definition of next_in_service, the\nin_service_entity cannot be considered as next_in_service. See the\ncomments on the definition of next_in_service for details on this\nsecond point.\n\nHitting the above corner case causes crashes.\n\nTo address this issue, this commit:\n1) Extends the above check on only next_in_service to controlling both\nnext_in_service and in_service_entity (if any of them is not NULL,\nthen no further deactivation is performed)\n2) Improves the (important) comments on how next_in_service is defined\nand updated; in particular it fixes a few rather obscure paragraphs\n\nReported-by: Eric Wheeler <bfq-sched@lists.ewheeler.net>\nReported-by: Rick Yiu <rick_yiu@htc.com>\nReported-by: Tom X Nguyen <tom81094@gmail.com>\nSigned-off-by: Paolo Valente <paolo.valente@linaro.org>\nTested-by: Eric Wheeler <bfq-sched@lists.ewheeler.net>\nTested-by: Rick Yiu <rick_yiu@htc.com>\nTested-by: Laurentiu Nicola <lnicola@dend.ro>\nTested-by: Tom X Nguyen <tom81094@gmail.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/46d556e6aaa0ec4dc83648ab1ca3d01dd2fa3ea3"},{"sha":"54e22f265e872ae140755b3318521d400a094605","author":{"name":"Linus Lüssing","email":"a5c6a8a492e92d195952376875d6b60c8f2e89b8@c0d3.blue"},"message":"batman-adv: fix TT sync flag inconsistencies\n\nThis patch fixes an issue in the translation table code potentially\nleading to a TT Request + Response storm. The issue may occur for nodes\ninvolving BLA and an inconsistent configuration of the batman-adv AP\nisolation feature. However, since the new multicast optimizations, a\nsingle, malformed packet may lead to a mesh-wide, persistent\nDenial-of-Service, too.\n\nThe issue occurs because nodes are currently OR-ing the TT sync flags of\nall originators announcing a specific MAC address via the\ntranslation table. When an intermediate node now receives a TT Request\nand wants to answer this on behalf of the destination node, then this\nintermediate node now responds with an altered flag field and broken\nCRC. The next OGM of the real destination will lead to a CRC mismatch\nand triggering a TT Request and Response again.\n\nFurthermore, the OR-ing is currently never undone as long as at least\none originator announcing the according MAC address remains, leading to\nthe potential persistency of this issue.\n\nThis patch fixes this issue by storing the flags used in the CRC\ncalculation on a a per TT orig entry basis to be able to respond with\nthe correct, original flags in an intermediate TT Response for one\nthing. And to be able to correctly unset sync flags once all nodes\nannouncing a sync flag vanish for another.\n\nFixes: e9c00136a475 (\"batman-adv: fix tt_global_entries flags update\")\nSigned-off-by: Linus Lüssing <linus.luessing@c0d3.blue>\nAcked-by: Antonio Quartulli <a@unstable.cc>\n[sw: typo in commit message]\nSigned-off-by: Simon Wunderlich <sw@simonwunderlich.de>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/54e22f265e872ae140755b3318521d400a094605"},{"sha":"b962e2cd357f2a529fe14387092401e6552f43d6","author":{"name":"Shawn Guo","email":"44d7acaa3f4e23fe307094648d49a2fc39e70f10@linaro.org"},"message":"pinctrl: zte: fix dereference of 'data' in zx_set_mux()\n\nIt fixes the following Smatch complaint:\n\ndrivers/pinctrl/zte/pinctrl-zx.c:76 zx_set_mux()\nwarn: variable dereferenced before check 'data' (see line 67)\n\nReported-by: Dan Carpenter <dan.carpenter@oracle.com>\nFixes: cbff0c4d27f4 (\"pinctrl: add ZTE ZX pinctrl driver support\")\nSigned-off-by: Shawn Guo <shawn.guo@linaro.org>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/b962e2cd357f2a529fe14387092401e6552f43d6"},{"sha":"65ff135b4f748f7d5f0d6a21b860e88a0d1fb7c5","author":{"name":"Kunihiko Hayashi","email":"d37f8e02e890baa16b4dc3d8469dc25954e9a95f@socionext.com"},"message":"pinctrl: uniphier: fix USB3 pin assignment for Pro4\n\nAccording to pinctrl assignment for Pro4, each definition of USB#2 and\nUSB#3 are as follows.\n\n  184: USB2VBUS\n  185: USB2OD\n  186: USB2ID\n  187: USB3VBUS\n  188: USB3OD\n\nUSB#2 has an additional pin \"USB2ID\", but the chip doesn't use this pin\nwhile in host-mode. Considering this pin, the pin definitions for USB#3\nshould be {187, 188}.\n\nSigned-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>\nAcked-by: Masahiro Yamada <yamada.masahiro@socionext.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/65ff135b4f748f7d5f0d6a21b860e88a0d1fb7c5"},{"sha":"c64ffff7a9d1eee6624d3eaab36968fe6df31a9f","author":{"name":"Andy Shevchenko","email":"81dea222a65099eed47626c53d6f56bdfbcbb7bf@linux.intel.com"},"message":"i2c: core: Allow empty id_table in ACPI case as well\n\nFor now empty ID table is not allowed with ACPI and prevents driver to\nbe probed.\n\nAdd a check to allow empty ID table.\n\nThis introduces a helper i2c_acpi_match_device().\n\nNote, we rename some static function in i2c-core-acpi.c to distinguish\nwith public API.\n\nFixes: da10c06a044b (\"i2c: Make I2C ID tables non-mandatory for DT'ed devices\")\nSigned-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nTested-by: Rajmohan Mani <rajmohan.mani@intel.com>\nAcked-by: Mika Westerberg <mika.westerberg@linux.intel.com>\n[wsa: needed to get some drivers probed again]\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/c64ffff7a9d1eee6624d3eaab36968fe6df31a9f"},{"sha":"d81ece747d8727bb8b1cfc9a20dbe62f09a4e35a","author":{"name":"Icenowy Zheng","email":"64c40edd0dc04061a867cb569405127102951f02@aosc.io"},"message":"pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver\n\nThe PH16 pin has a function with mux id 0x5, which is the DET pin of the\n\"sim\" (smart card reader) IP block.\n\nThis function is missing in old versions of A10/A20 SoCs' datasheets and\nuser manuals, so it's also missing in the old drivers. The newest A10\nDatasheet V1.70 and A20 Datasheet V1.41 contain this pin function, and\nit's discovered during implementing R40 pinctrl driver.\n\nAdd it to the driver. As we now merged A20 pinctrl driver to the A10\none, we need to only fix the A10 driver now.\n\nFixes: f2821b1ca3a2 (\"pinctrl: sunxi: Move Allwinner A10 pinctrl\ndriver to a driver of its own\")\n\nSigned-off-by: Icenowy Zheng <icenowy@aosc.io>\nReviewed-by: Chen-Yu Tsai <wens@csie.org>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/d81ece747d8727bb8b1cfc9a20dbe62f09a4e35a"},{"sha":"22acc37b8681461707a3fc73505af808f9af8260","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"i2c: designware: Print clock freq on invalid clock freq error\n\nWhen we refuse to probe due to an invalid clock frequency, log\nthe frequency which is causing this error.\n\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nReviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/22acc37b8681461707a3fc73505af808f9af8260"},{"sha":"682c6c2188f39d13548ccdc89c9888fbcb547889","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"i2c: designware: Some broken DSTDs use 1MiHz instead of 1MHz\n\nAt least the Acer Iconia Tab8 / aka W1-810 uses 1MiHz instead of\n1MHz for one of its busses, fix this up to 1MHz instead of failing\nthe probe of that bus.\n\nThis fixes the accelerometer on the Acer Iconia Tab8 not working.\n\nCc: stable@vger.kernel.org\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nReviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/682c6c2188f39d13548ccdc89c9888fbcb547889"},{"sha":"c69b9e1278a2a23482a12bf56e54463f03b9e3f1","author":{"name":"Wolfram Sang","email":"fdae3fe83782164199e727a16ce9ff637adc829c@the-dreams.de"},"message":"Merge branch 'i2c-mux/for-current' of https://github.com/peda-r/i2c-mux into i2c/for-current","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/c69b9e1278a2a23482a12bf56e54463f03b9e3f1"},{"sha":"5871a1538cd2d7a4a18e5e21adc7e9e6dab702e2","author":{"name":"Russell King","email":"8640768d851c67eb4c0e8bfcf2aabcc8010b9372@armlinux.org.uk"},"message":"i2c: allow i2c-versatile for ARM MPS platforms\n\nAllow i2c-versatile to be enabled for ARM MPS platforms.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/5871a1538cd2d7a4a18e5e21adc7e9e6dab702e2"},{"sha":"9c80034921d1ece5c0e3241ba1645bce32387684","author":{"name":"Wolfram Sang","email":"fdae3fe83782164199e727a16ce9ff637adc829c@the-dreams.de"},"message":"i2c: rephrase explanation of I2C_CLASS_DEPRECATED\n\nHopefully making clear that it is not needed for new drivers.\n\nSigned-off-by: Wolfram Sang <wsa@the-dreams.de>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/9c80034921d1ece5c0e3241ba1645bce32387684"},{"sha":"d9535cb7b7603aeb549c697ecdf92024e4d0a650","author":{"name":"Grygorii Strashko","email":"6313aa67c79f49bbc5c7e7685d9d3910b42c6984@ti.com"},"message":"ptp: introduce ptp auxiliary worker\n\nMany PTP drivers required to perform some asynchronous or periodic work,\nlike periodically handling PHC counter overflow or handle delayed timestamp\nfor RX/TX network packets. In most of the cases, such work is implemented\nusing workqueues. Unfortunately, Kernel workqueues might introduce\nsignificant delay in work scheduling under high system load and on -RT,\nwhich could cause misbehavior of PTP drivers due to internal counter\noverflow, for example, and there is no way to tune its execution policy and\npriority manuallly.\n\nHence, The kthread_worker can be used insted of workqueues, as it create\nseparte named kthread for each worker and its its execution policy and\npriority can be configured using chrt tool.\n\nThis prblem was reported for two drivers TI CPSW CPTS and dp83640, so\ninstead of modifying each of these driver it was proposed to add PTP\nauxiliary worker to the PHC subsystem.\n\nThe patch adds PTP auxiliary worker in PHC subsystem using kthread_worker\nand kthread_delayed_work and introduces two new PHC subsystem APIs:\n\n- long (*do_aux_work)(struct ptp_clock_info *ptp) callback in\nptp_clock_info structure, which driver should assign if it require to\nperform asynchronous or periodic work. Driver should return the delay of\nthe PTP next auxiliary work scheduling time (>=0) or negative value in case\nfurther scheduling is not required.\n\n- int ptp_schedule_worker(struct ptp_clock *ptp, unsigned long delay) which\nallows schedule PTP auxiliary work.\n\nThe name of kthread_worker thread corresponds PTP PHC device name \"ptp%d\".\n\nSigned-off-by: Grygorii Strashko <grygorii.strashko@ti.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/d9535cb7b7603aeb549c697ecdf92024e4d0a650"},{"sha":"999f129289ab1599e7cdc08804a9b5ec4e1418f4","author":{"name":"Grygorii Strashko","email":"6313aa67c79f49bbc5c7e7685d9d3910b42c6984@ti.com"},"message":"net: ethernet: ti: cpts: convert to use ptp auxiliary worker\n\nThere could be significant delay in CPTS work schedule under high system\nload and on -RT which could cause CPTS misbehavior due to internal counter\noverflow. Usage of own kthread_worker allows to avoid such kind of issues\nand makes it possible to tune priority of CPTS kthread_worker thread on -RT\n(thread name \"cpts\").\n\nHence, the CPTS driver is converted to use PTP auxiliary worker as PHC\nsubsystem implements such functionality in a generic way now.\n\nSigned-off-by: Grygorii Strashko <grygorii.strashko@ti.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/999f129289ab1599e7cdc08804a9b5ec4e1418f4"},{"sha":"0d5f54fec0a18eea5e4ac005646fd2bc2118636c","author":{"name":"Grygorii Strashko","email":"6313aa67c79f49bbc5c7e7685d9d3910b42c6984@ti.com"},"message":"net: ethernet: ti: cpts: fix tx timestamping timeout\n\nWith the low speed Ethernet connection CPDMA notification about packet\nprocessing can be received before CPTS TX timestamp event, which is set\nwhen packet actually left CPSW while cpdma notification is sent when packet\npushed in CPSW fifo.  As result, when connection is slow and CPU is fast\nenough TX timestamping is not working properly.\n\nFix it, by introducing TX SKB queue to store PTP SKBs for which Ethernet\nTransmit Event hasn't been received yet and then re-check this queue\nwith new Ethernet Transmit Events by scheduling CPTS overflow\nwork more often (every 1 jiffies) until TX SKB queue is not empty.\n\nSide effect of this change is:\n - User space tools require to take into account possible delay in TX\ntimestamp processing (for example ptp4l works with tx_timestamp_timeout=400\nunder net traffic and tx_timestamp_timeout=25 in idle).\n\nSigned-off-by: Grygorii Strashko <grygorii.strashko@ti.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/0d5f54fec0a18eea5e4ac005646fd2bc2118636c"},{"sha":"a93439cce2c1d31469e8245c504dbb6d1bed8749","author":{"name":"Grygorii Strashko","email":"6313aa67c79f49bbc5c7e7685d9d3910b42c6984@ti.com"},"message":"net: ethernet: ti: cpts: fix fifo read in cpts_find_ts\n\nNow the call chain\n cpts_find_ts()\n  |- cpts_fifo_read(cpts, CPTS_EV_PUSH)\n\nwill stop reading CPTS FIFO if PUSH event is found. But this is not\nexpected and CPTS FIFI should be completely drained here. This is most\nprobably copy-paste error and it has no negative impact as CPTS_EV_PUSH\nshould not be present in FIFO without TS_PUSH request and\ncpts_systim_read() and cpts_find_ts() synchronized by spin_lock.\n\nCorrect above by calling cpts_fifo_read() with -1 parameter, so it will\nread all CPTS event from FIFO.\n\nSigned-off-by: Grygorii Strashko <grygorii.strashko@ti.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/a93439cce2c1d31469e8245c504dbb6d1bed8749"},{"sha":"fdaa419bb24cc191f2dce2ec19af1ef7c5076a36","author":{"name":"David S. Miller","email":"79caf591e37e1438a2d55ae59670d5cd0d717764@davemloft.net"},"message":"Merge branch 'ethernet-ti-cpts-fix-tx-timestamping-timeout'\n\nGrygorii Strashko says:\n\n====================\nnet: ethernet: ti: cpts: fix tx timestamping timeout\n\nWith the low Ethernet connection speed cpdma notification about packet\nprocessing can be received before CPTS TX timestamp event, which is set\nwhen packet actually left CPSW while cpdma notification is sent when packet\npushed in CPSW fifo. As result, when connection is slow and CPU is fast\nenough TX timestamping is not working properly.\nIssue was discovered using timestamping tool on am57x boards with Ethernet link\nspeed forced to 100M and on am335x-evm with Ethernet link speed forced to 10M.\n\nPatch3 - This series fixes it by introducing TX SKB queue to store PTP SKBs for\nwhich Ethernet Transmit Event hasn't been received yet and then re-check this\nqueue with new Ethernet Transmit Events by scheduling CPTS overflow\nwork more often until TX SKB queue is not empty.\n\nPatch 1,2 - As CPTS overflow work is time critical task it important to ensure\nthat its scheduling is not delayed. Unfortunately, There could be significant\ndelay in CPTS work schedule under high system load and on -RT which could cause\nCPTS misbehavior due to internal counter overflow and there is no way to tune\nCPTS overflow work execution policy and priority manually. The kthread_worker\ncan be used instead of workqueues, as it creates separate named kthread for\neach worker and its its execution policy and priority can be configured\nusing chrt tool. Instead of modifying CPTS driver itself it was proposed to\nit was proposed to add PTP auxiliary worker to the PHC subsystem [1], so\nother drivers can benefit from this feature also.\n\n[1] https://www.spinics.net/lists/netdev/msg445392.html\n\nchanges in v4:\n- fixed memleak in ptp_clock_register()\n- undocumented change in cpts_find_ts() moved to separate patch (minor fix)\n\nchanges in v3:\n- patch 1: added proper error handling in ptp_clock_register.\n  minor comments applied.\n\nchanges in v2:\n- added PTP auxiliary worker to the PHC subsystem\n\nLinks\nv3: https://www.spinics.net/lists/netdev/msg446058.html\nv2: https://www.spinics.net/lists/netdev/msg445859.html\nv1: https://www.spinics.net/lists/netdev/msg445387.html\n====================\n\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/fdaa419bb24cc191f2dce2ec19af1ef7c5076a36"},{"sha":"40413955ee265a5e42f710940ec78f5450d49149","author":{"name":"yujuan.qi","email":"762cd0c24b097243fa1c2cdb5c17f73596ef5786@mediatek.com"},"message":"Cipso: cipso_v4_optptr enter infinite loop\n\nin for(),if((optlen > 0) && (optptr[1] == 0)), enter infinite loop.\n\nTest: receive a packet which the ip length > 20 and the first byte of ip option is 0, produce this issue\n\nSigned-off-by: yujuan.qi <yujuan.qi@mediatek.com>\nAcked-by: Paul Moore <paul@paul-moore.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/40413955ee265a5e42f710940ec78f5450d49149"},{"sha":"be73b3043bf465455d4c9b88f68e03b6447bcfb0","author":{"name":"K. Den","email":"920e0c5baa5df768dcc4c39370daa63f87210e85@klaipeden.com"},"message":"vxlan: fix remcsum when GRO on and CHECKSUM_PARTIAL boundary is outer UDP\n\nIn the case that GRO is turned on and the original received packet is\nCHECKSUM_PARTIAL, if the outer UDP header is exactly at the last\ncsum-unnecessary point, which for instance could occur if the packet\ncomes from another Linux guest on the same Linux host, we have to do\neither remcsum_adjust or set up CHECKSUM_PARTIAL again with its\ncsum_start properly reset considering RCO.\n\nHowever, since b7fe10e5ebac(\"gro: Fix remcsum offload to deal with frags\nin GRO\") that barrier in such case could be skipped if GRO turned on,\nhence we pass over it and the inner L4 validation mistakenly reckons\nit as a bad csum.\n\nThis patch makes remcsum_offload being reset at the same time of GRO\nremcsum cleanup, so as to make it work in such case as before.\n\nFixes: b7fe10e5ebac (\"gro: Fix remcsum offload to deal with frags in GRO\")\nSigned-off-by: Koichiro Den <den@klaipeden.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-3.18/commits/be73b3043bf465455d4c9b88f68e03b6447bcfb0"}]}
{"actor":{"display_login":"akhilnarang"}}