{"push_id":719972405,"size":97,"distinct_size":0,"ref":"refs/heads/caf/korg/linux-3.14.y","head":"a0768244828d0da096ce957616150220da607be1","before":"e99d350e5ba34ef020d2f3bf585134571f1bb323","commits":[{"sha":"9e56322af5e016ca5dd73dbb5b0e43072a699194","author":{"email":"152d4c5bebf13a5b809d42b4d789cf9d887e6698@gmail.com","name":"Ilya Dryomov"},"message":"crush: ensuring at most num-rep osds are selected\n\ncommit 45002267e8d2699bf9b022315bee3dd13b044843 upstream.\n\nCrush temporary buffers are allocated as per replica size configured\nby the user.  When there are more final osds (to be selected as per\nrule) than the replicas, buffer overlaps and it causes crash.  Now, it\nensures that at most num-rep osds are selected even if more number of\nosds are allowed by the rule.\n\nReflects ceph.git commits 6b4d1aa99718e3b367496326c1e64551330fabc0,\n                          234b066ba04976783d15ff2abc3e81b6cc06fb10.\n\nSigned-off-by: Ilya Dryomov <idryomov@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/9e56322af5e016ca5dd73dbb5b0e43072a699194"},{"sha":"516ec5eb66b0fc63862c487a04d401d3310bc085","author":{"email":"df4bbba3da7ae0371dc686d07d0ceb66ffa78730@gmail.com","name":"Vlad Yasevich"},"message":"net: core: Correct an over-stringent device loop detection.\n\n[ Upstream commit d66bf7dd27573ee5ea90484899ee952c19ccb194 ]\n\nThe code in __netdev_upper_dev_link() has an over-stringent\nloop detection logic that actually prevents valid configurations\nfrom working correctly.\n\nIn particular, the logic returns an error if an upper device\nis already in the list of all upper devices for a given dev.\nThis particular check seems to be a overzealous as it disallows\nperfectly valid configurations.  For example:\n  # ip l a link eth0 name eth0.10 type vlan id 10\n  # ip l a dev br0 typ bridge\n  # ip l s eth0.10 master br0\n  # ip l s eth0 master br0  <--- Will fail\n\nIf you switch the last two commands (add eth0 first), then both\nwill succeed.  If after that, you remove eth0 and try to re-add\nit, it will fail!\n\nIt appears to be enough to simply check adj_list to keeps things\nsafe.\n\nI've tried stacking multiple devices multiple times in all different\ncombinations, and either rx_handler registration prevented the stacking\nof the device linking cought the error.\n\nSigned-off-by: Vladislav Yasevich <vyasevic@redhat.com>\nAcked-by: Jiri Pirko <jiri@resnulli.us>\nAcked-by: Veaceslav Falico <vfalico@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/516ec5eb66b0fc63862c487a04d401d3310bc085"},{"sha":"4ca11e9fe811defdf228d7f579e77b5350c96d02","author":{"email":"c24c0248770ae98831f8a654310d4c2e07514c61@plumgrid.com","name":"Alexei Starovoitov"},"message":"x86: bpf_jit: fix compilation of large bpf programs\n\n[ Upstream commit 3f7352bf21f8fd7ba3e2fcef9488756f188e12be ]\n\nx86 has variable length encoding. x86 JIT compiler is trying\nto pick the shortest encoding for given bpf instruction.\nWhile doing so the jump targets are changing, so JIT is doing\nmultiple passes over the program. Typical program needs 3 passes.\nSome very short programs converge with 2 passes. Large programs\nmay need 4 or 5. But specially crafted bpf programs may hit the\npass limit and if the program converges on the last iteration\nthe JIT compiler will be producing an image full of 'int 3' insns.\nFix this corner case by doing final iteration over bpf program.\n\nFixes: 0a14842f5a3c (\"net: filter: Just In Time compiler for x86-64\")\nReported-by: Daniel Borkmann <daniel@iogearbox.net>\nSigned-off-by: Alexei Starovoitov <ast@plumgrid.com>\nTested-by: Daniel Borkmann <daniel@iogearbox.net>\nAcked-by: Daniel Borkmann <daniel@iogearbox.net>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/4ca11e9fe811defdf228d7f579e77b5350c96d02"},{"sha":"d9c3586ff7b0757d34e475e5eda68586832878ea","author":{"email":"59190c1867e3222b932a0de3c668eb2d980d69a2@gmail.com","name":"Florian Fainelli"},"message":"net: phy: Allow EEE for all RGMII variants\n\n[ Upstream commit 7e14069651591c81046ffaec13c3dac8cb70f5fb ]\n\nRGMII interfaces come in multiple flavors: RGMII with transmit or\nreceive internal delay, no delays at all, or delays in both direction.\n\nThis change extends the initial check for PHY_INTERFACE_MODE_RGMII to\ncover all of these variants since EEE should be allowed for any of these\nmodes, since it is a property of the RGMII, hence Gigabit PHY capability\nmore than the RGMII electrical interface and its delays.\n\nFixes: a59a4d192166 (\"phy: add the EEE support and the way to access to the MMD registers\")\nSigned-off-by: Florian Fainelli <f.fainelli@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/d9c3586ff7b0757d34e475e5eda68586832878ea"},{"sha":"38196b3cb4e9b8e0beb7b30ce39880f0b666f431","author":{"email":"787ae617617698b2b89c353cdfb3f2e4d16ffeb7@enst-bretagne.fr","name":"Florent Fourcot"},"message":"tcp/ipv6: fix flow label setting in TIME_WAIT state\n\n[ Upstream commit 21858cd02dabcf290564cbf4769b101eba54d7bb ]\n\ncommit 1d13a96c74fc (\"ipv6: tcp: fix flowlabel value in ACK messages\nsend from TIME_WAIT\") added the flow label in the last TCP packets.\nUnfortunately, it was not casted properly.\n\nThis patch replace the buggy shift with be32_to_cpu/cpu_to_be32.\n\nFixes: 1d13a96c74fc (\"ipv6: tcp: fix flowlabel value in ACK messages\")\nReported-by: Eric Dumazet <eric.dumazet@gmail.com>\nSigned-off-by: Florent Fourcot <florent.fourcot@enst-bretagne.fr>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/38196b3cb4e9b8e0beb7b30ce39880f0b666f431"},{"sha":"88ad5b3e94ab2fba5bfc2ad4604b15b0aa079a13","author":{"email":"8a741aa8cbd77ebc4a56ddb528ce9fd15d42f034@xmission.com","name":"Eric W. Biederman"},"message":"ipv4: Avoid crashing in ip_error\n\n[ Upstream commit 381c759d9916c42959515ad34a6d467e24a88e93 ]\n\nip_error does not check if in_dev is NULL before dereferencing it.\n\nIThe following sequence of calls is possible:\nCPU A                          CPU B\nip_rcv_finish\n    ip_route_input_noref()\n        ip_route_input_slow()\n                               inetdev_destroy()\n    dst_input()\n\nWith the result that a network device can be destroyed while processing\nan input packet.\n\nA crash was triggered with only unicast packets in flight, and\nforwarding enabled on the only network device.   The error condition\nwas created by the removal of the network device.\n\nAs such it is likely the that error code was -EHOSTUNREACH, and the\naction taken by ip_error (if in_dev had been accessible) would have\nbeen to not increment any counters and to have tried and likely failed\nto send an icmp error as the network device is going away.\n\nTherefore handle this weird case by just dropping the packet if\n!in_dev.  It will result in dropping the packet sooner, and will not\nresult in an actual change of behavior.\n\nFixes: 251da4130115b (\"ipv4: Cache ip_error() routes even when not forwarding.\")\nReported-by: Vittorio Gambaletta <linuxbugs@vittgam.net>\nTested-by: Vittorio Gambaletta <linuxbugs@vittgam.net>\nSigned-off-by: Vittorio Gambaletta <linuxbugs@vittgam.net>\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/88ad5b3e94ab2fba5bfc2ad4604b15b0aa079a13"},{"sha":"57bc6480ec7693ab03c4b81baa679d4383c5844c","author":{"email":"c8883472cb5fbead63941b41bccc869c7deaf90f@redhat.com","name":"Thadeu Lima de Souza Cascardo"},"message":"bridge: fix parsing of MLDv2 reports\n\n[ Upstream commit 47cc84ce0c2fe75c99ea5963c4b5704dd78ead54 ]\n\nWhen more than a multicast address is present in a MLDv2 report, all but\nthe first address is ignored, because the code breaks out of the loop if\nthere has not been an error adding that address.\n\nThis has caused failures when two guests connected through the bridge\ntried to communicate using IPv6. Neighbor discoveries would not be\ntransmitted to the other guest when both used a link-local address and a\nstatic address.\n\nThis only happens when there is a MLDv2 querier in the network.\n\nThe fix will only break out of the loop when there is a failure adding a\nmulticast address.\n\nThe mdb before the patch:\n\ndev ovirtmgmt port vnet0 grp ff02::1:ff7d:6603 temp\ndev ovirtmgmt port vnet1 grp ff02::1:ff7d:6604 temp\ndev ovirtmgmt port bond0.86 grp ff02::2 temp\n\nAfter the patch:\n\ndev ovirtmgmt port vnet0 grp ff02::1:ff7d:6603 temp\ndev ovirtmgmt port vnet1 grp ff02::1:ff7d:6604 temp\ndev ovirtmgmt port bond0.86 grp ff02::fb temp\ndev ovirtmgmt port bond0.86 grp ff02::2 temp\ndev ovirtmgmt port bond0.86 grp ff02::d temp\ndev ovirtmgmt port vnet0 grp ff02::1:ff00:76 temp\ndev ovirtmgmt port bond0.86 grp ff02::16 temp\ndev ovirtmgmt port vnet1 grp ff02::1:ff00:77 temp\ndev ovirtmgmt port bond0.86 grp ff02::1:ff00:def temp\ndev ovirtmgmt port bond0.86 grp ff02::1:ffa1:40bf temp\n\nFixes: 08b202b67264 (\"bridge br_multicast: IPv6 MLD support.\")\nReported-by: Rik Theys <Rik.Theys@esat.kuleuven.be>\nSigned-off-by: Thadeu Lima de Souza Cascardo <cascardo@redhat.com>\nTested-by: Rik Theys <Rik.Theys@esat.kuleuven.be>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/57bc6480ec7693ab03c4b81baa679d4383c5844c"},{"sha":"9dae772fe7d9ca1c39970802df69a2a2cc047028","author":{"email":"e27030aebe9cad8817d34b8c31dbaf301fb798b9@gmail.com","name":"Richard Cochran"},"message":"net: dp83640: fix broken calibration routine.\n\n[ Upstream commit 397a253af5031de4a4612210055935309af4472c ]\n\nCurrently, the calibration function that corrects the initial offsets\namong multiple devices only works the first time.  If the function is\ncalled more than once, the calibration fails and bogus offsets will be\nprogrammed into the devices.\n\nIn a well hidden spot, the device documentation tells that trigger indexes\n0 and 1 are special in allowing the TRIG_IF_LATE flag to actually work.\n\nThis patch fixes the issue by using one of the special triggers during the\nrecalibration method.\n\nSigned-off-by: Richard Cochran <richardcochran@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/9dae772fe7d9ca1c39970802df69a2a2cc047028"},{"sha":"a7aef10597f27af62794556a40cf9648f92f856a","author":{"email":"e27030aebe9cad8817d34b8c31dbaf301fb798b9@gmail.com","name":"Richard Cochran"},"message":"net: dp83640: reinforce locking rules.\n\n[ Upstream commit a935865c828c8cd20501f618c69f659a5b6d6a5f ]\n\nCallers of the ext_write function are supposed to hold a mutex that\nprotects the state of the dialed page, but one caller was missing the\nlock from the very start, and over time the code has been changed\nwithout following the rule.  This patch cleans up the call sites in\nviolation of the rule.\n\nSigned-off-by: Richard Cochran <richardcochran@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/a7aef10597f27af62794556a40cf9648f92f856a"},{"sha":"1f5105d64ea50143a95aabb6b2f86b16580e9350","author":{"email":"4bb1064d1f46929ded0070376617aece30f0ee54@android.com","name":"Mark Salyzyn"},"message":"unix/caif: sk_socket can disappear when state is unlocked\n\n[ Upstream commit b48732e4a48d80ed4a14812f0bab09560846514e ]\n\ngot a rare NULL pointer dereference in clear_bit\n\nSigned-off-by: Mark Salyzyn <salyzyn@android.com>\nAcked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\n----\nv2: switch to sock_flag(sk, SOCK_DEAD) and added net/caif/caif_socket.c\nv3: return -ECONNRESET in upstream caller of wait function for SOCK_DEAD\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/1f5105d64ea50143a95aabb6b2f86b16580e9350"},{"sha":"4d97213d4f0a0c5ee5ad7066c1eb97ada4ffae61","author":{"email":"0f114804888b88d50037b04b42e57b858d851b87@gmail.com","name":"WANG Cong"},"message":"net_sched: invoke ->attach() after setting dev->qdisc\n\n[ Upstream commit 86e363dc3b50bfd50a1f315934583fbda673ab8d ]\n\nFor mq qdisc, we add per tx queue qdisc to root qdisc\nfor display purpose, however, that happens too early,\nbefore the new dev->qdisc is finally set, this causes\nq->list points to an old root qdisc which is going to be\nfreed right before assigning with a new one.\n\nFix this by moving ->attach() after setting dev->qdisc.\n\nFor the record, this fixes the following crash:\n\n ------------[ cut here ]------------\n WARNING: CPU: 1 PID: 975 at lib/list_debug.c:59 __list_del_entry+0x5a/0x98()\n list_del corruption. prev->next should be ffff8800d1998ae8, but was 6b6b6b6b6b6b6b6b\n CPU: 1 PID: 975 Comm: tc Not tainted 4.1.0-rc4+ #1019\n Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011\n  0000000000000009 ffff8800d73fb928 ffffffff81a44e7f 0000000047574756\n  ffff8800d73fb978 ffff8800d73fb968 ffffffff810790da ffff8800cfc4cd20\n  ffffffff814e725b ffff8800d1998ae8 ffffffff82381250 0000000000000000\n Call Trace:\n  [<ffffffff81a44e7f>] dump_stack+0x4c/0x65\n  [<ffffffff810790da>] warn_slowpath_common+0x9c/0xb6\n  [<ffffffff814e725b>] ? __list_del_entry+0x5a/0x98\n  [<ffffffff81079162>] warn_slowpath_fmt+0x46/0x48\n  [<ffffffff81820eb0>] ? dev_graft_qdisc+0x5e/0x6a\n  [<ffffffff814e725b>] __list_del_entry+0x5a/0x98\n  [<ffffffff814e72a7>] list_del+0xe/0x2d\n  [<ffffffff81822f05>] qdisc_list_del+0x1e/0x20\n  [<ffffffff81820cd1>] qdisc_destroy+0x30/0xd6\n  [<ffffffff81822676>] qdisc_graft+0x11d/0x243\n  [<ffffffff818233c1>] tc_get_qdisc+0x1a6/0x1d4\n  [<ffffffff810b5eaf>] ? mark_lock+0x2e/0x226\n  [<ffffffff817ff8f5>] rtnetlink_rcv_msg+0x181/0x194\n  [<ffffffff817ff72e>] ? rtnl_lock+0x17/0x19\n  [<ffffffff817ff72e>] ? rtnl_lock+0x17/0x19\n  [<ffffffff817ff774>] ? __rtnl_unlock+0x17/0x17\n  [<ffffffff81855dc6>] netlink_rcv_skb+0x4d/0x93\n  [<ffffffff817ff756>] rtnetlink_rcv+0x26/0x2d\n  [<ffffffff818544b2>] netlink_unicast+0xcb/0x150\n  [<ffffffff81161db9>] ? might_fault+0x59/0xa9\n  [<ffffffff81854f78>] netlink_sendmsg+0x4fa/0x51c\n  [<ffffffff817d6e09>] sock_sendmsg_nosec+0x12/0x1d\n  [<ffffffff817d8967>] sock_sendmsg+0x29/0x2e\n  [<ffffffff817d8cf3>] ___sys_sendmsg+0x1b4/0x23a\n  [<ffffffff8100a1b8>] ? native_sched_clock+0x35/0x37\n  [<ffffffff810a1d83>] ? sched_clock_local+0x12/0x72\n  [<ffffffff810a1fd4>] ? sched_clock_cpu+0x9e/0xb7\n  [<ffffffff810def2a>] ? current_kernel_time+0xe/0x32\n  [<ffffffff810b4bc5>] ? lock_release_holdtime.part.29+0x71/0x7f\n  [<ffffffff810ddebf>] ? read_seqcount_begin.constprop.27+0x5f/0x76\n  [<ffffffff810b6292>] ? trace_hardirqs_on_caller+0x17d/0x199\n  [<ffffffff811b14d5>] ? __fget_light+0x50/0x78\n  [<ffffffff817d9808>] __sys_sendmsg+0x42/0x60\n  [<ffffffff817d9838>] SyS_sendmsg+0x12/0x1c\n  [<ffffffff81a50e97>] system_call_fastpath+0x12/0x6f\n ---[ end trace ef29d3fb28e97ae7 ]---\n\nFor long term, we probably need to clean up the qdisc_graft() code\nin case it hides other bugs like this.\n\nFixes: 95dc19299f74 (\"pkt_sched: give visibility to mq slave qdiscs\")\nCc: Jamal Hadi Salim <jhs@mojatatu.com>\nSigned-off-by: Cong Wang <xiyou.wangcong@gmail.com>\nAcked-by: Eric Dumazet <edumazet@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/4d97213d4f0a0c5ee5ad7066c1eb97ada4ffae61"},{"sha":"542744f265e23eca08f14a8748a3cbf5feb56cdf","author":{"email":"312c7d941f03386814be517ffdb3e0eb6624e275@google.com","name":"Eric Dumazet"},"message":"udp: fix behavior of wrong checksums\n\n[ Upstream commit beb39db59d14990e401e235faf66a6b9b31240b0 ]\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 <edumazet@google.com>\nCc: Willem de Bruijn <willemb@google.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/542744f265e23eca08f14a8748a3cbf5feb56cdf"},{"sha":"67070968a28bd501e2ff864bab3e95006cca4e00","author":{"email":"d07012418334d2b85843de1e24273f2477041b61@citrix.com","name":"Ian Campbell"},"message":"xen: netback: read hotplug script once at start of day.\n\n[ Upstream commit 31a418986a5852034d520a5bab546821ff1ccf3d ]\n\nWhen we come to tear things down in netback_remove() and generate the\nuevent it is possible that the xenstore directory has already been\nremoved (details below).\n\nIn such cases netback_uevent() won't be able to read the hotplug\nscript and will write a xenstore error node.\n\nA recent change to the hypervisor exposed this race such that we now\nsometimes lose it (where apparently we didn't ever before).\n\nInstead read the hotplug script configuration during setup and use it\nfor the lifetime of the backend device.\n\nThe apparently more obvious fix of moving the transition to\nstate=Closed in netback_remove() to after the uevent does not work\nbecause it is possible that we are already in state=Closed (in\nreaction to the guest having disconnected as it shutdown). Being\nalready in Closed means the toolstack is at liberty to start tearing\ndown the xenstore directories. In principal it might be possible to\narrange to unregister the device sooner (e.g on transition to Closing)\nsuch that xenstore would still be there but this state machine is\nfragile and prone to anger...\n\nA modern Xen system only relies on the hotplug uevent for driver\ndomains, when the backend is in the same domain as the toolstack it\nwill run the necessary setup/teardown directly in the correct sequence\nwrt xenstore changes.\n\nSigned-off-by: Ian Campbell <ian.campbell@citrix.com>\nAcked-by: Wei Liu <wei.liu2@citrix.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/67070968a28bd501e2ff864bab3e95006cca4e00"},{"sha":"fa730505072b85750f21f652783bb595dc22bbd5","author":{"email":"2bfef4e2b953b8463910cf5c5571c19ecd7a208a@rgmadvisors.com","name":"Shawn Bohrer"},"message":"ipv4/udp: Verify multicast group is ours in upd_v4_early_demux()\n\n[ Upstream commit 6e540309326188f769e03bb4c6dd8ff6752930c2 ]\n\n421b3885bf6d56391297844f43fb7154a6396e12 \"udp: ipv4: Add udp early\ndemux\" introduced a regression that allowed sockets bound to INADDR_ANY\nto receive packets from multicast groups that the socket had not joined.\nFor example a socket that had joined 224.168.2.9 could also receive\npackets from 225.168.2.9 despite not having joined that group if\nip_early_demux is enabled.\n\nFix this by calling ip_check_mc_rcu() in udp_v4_early_demux() to verify\nthat the multicast packet is indeed ours.\n\nSigned-off-by: Shawn Bohrer <sbohrer@rgmadvisors.com>\nReported-by: Yurij M. Plotnikov <Yurij.Plotnikov@oktetlabs.ru>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/fa730505072b85750f21f652783bb595dc22bbd5"},{"sha":"44da7386bb0bee83d2a11717e43730c27f4da717","author":{"email":"262b42b771725e3ebec40395f2b058e593df7462@cumulusnetworks.com","name":"Nikolay Aleksandrov"},"message":"bridge: disable softirqs around br_fdb_update to avoid lockup\n\n[ Upstream commit c4c832f89dc468cf11dc0dd17206bace44526651 ]\n\nbr_fdb_update() can be called in process context in the following way:\nbr_fdb_add() -> __br_fdb_add() -> 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't 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 <nikolay@cumulusnetworks.com>\nFixes: 292d1398983f (\"bridge: add NTF_USE support\")\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/44da7386bb0bee83d2a11717e43730c27f4da717"},{"sha":"8c966e7403a9ab45bdc9c6b3c6f8ea21497e3d54","author":{"email":"b6ffd6973e972cb999e8e535ab74da7fee0c035f@ingics.com","name":"Axel Lin"},"message":"iio: adc: twl6030-gpadc: Fix modalias\n\ncommit e5d732186270e0881f47d95610316c0614b21c3e upstream.\n\nRemove extra space between platform prefix and DRIVER_NAME in MODULE_ALIAS.\n\nSigned-off-by: Axel Lin <axel.lin@ingics.com>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/8c966e7403a9ab45bdc9c6b3c6f8ea21497e3d54"},{"sha":"8fdf5cac123483476bc51c5149b83a984eb8bdb2","author":{"email":"3318dc5ce3e4fb7c28a0b841b6801c884e1d0896@metafoo.de","name":"Lars-Peter Clausen"},"message":"iio: adis16400: Report pressure channel scale\n\ncommit 69ca2d771e4e709c5ae1125858e1246e77ef8b86 upstream.\n\nAdd the scale for the pressure channel, which is currently missing.\n\nSigned-off-by: Lars-Peter Clausen <lars@metafoo.de>\nFixes: 76ada52f7f5d (\"iio:adis16400: Add support for the adis16448\")\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/8fdf5cac123483476bc51c5149b83a984eb8bdb2"},{"sha":"220fa1e4d7069b677d6aa9723ff71674decdbb28","author":{"email":"73d292422978d45c9eeef455bb1b24a0db453722@analog.com","name":"Paul Cercueil"},"message":"iio: adis16400: Use != channel indices for the two voltage channels\n\ncommit 7323d59862802ca109451eeda9777024a7625509 upstream.\n\nPreviously, the two voltage channels had the same ID, which didn't cause\nconflicts in sysfs only because one channel is named and the other isn't;\nthis is still violating the spec though, two indexed channels should never\nhave the same index.\n\nSigned-off-by: Paul Cercueil <paul.cercueil@analog.com>\nSigned-off-by: Lars-Peter Clausen <lars@metafoo.de>\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/220fa1e4d7069b677d6aa9723ff71674decdbb28"},{"sha":"209abaeab184e0c75728b380914117b7be2dd89a","author":{"email":"73d292422978d45c9eeef455bb1b24a0db453722@analog.com","name":"Paul Cercueil"},"message":"iio: adis16400: Compute the scan mask from channel indices\n\ncommit c2a8b623a089d52c199e305e7905829907db8ec8 upstream.\n\nWe unfortunately can't use ~0UL for the scan mask to indicate that the\nonly valid scan mask is all channels selected. The IIO core needs the exact\nmask to work correctly and not a super-set of it. So calculate the masked\nbased on the channels that are available for a particular device.\n\nSigned-off-by: Paul Cercueil <paul.cercueil@analog.com>\nSigned-off-by: Lars-Peter Clausen <lars@metafoo.de>\nFixes: 5eda3550a3cc (\"staging:iio:adis16400: Preallocate transfer message\")\nSigned-off-by: Jonathan Cameron <jic23@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/209abaeab184e0c75728b380914117b7be2dd89a"},{"sha":"3bb76d57f40a3d086b386c26e4340ba3017fd471","author":{"email":"b8f3952ea9a7ddc193d05c7cc03f120086c69f1e@fedoraproject.org","name":"Laura Abbott"},"message":"n_tty: Fix auditing support for cannonical mode\n\ncommit 72586c6061ab8c23ffd9f301ed19782a44ff5f04 upstream.\n\nCommit 32f13521ca68bc624ff6effc77f308a52b038bf0\n(\"n_tty: Line copy to user buffer in canonical mode\")\nchanged cannonical mode copying to use copy_to_user\nbut missed adding the call to the audit framework.\nAdd in the appropriate functions to get audit support.\n\nFixes: 32f13521ca68 (\"n_tty: Line copy to user buffer in canonical mode\")\nReported-by: Miloslav Trmač <mitr@redhat.com>\nSigned-off-by: Laura Abbott <labbott@fedoraproject.org>\nReviewed-by: Peter Hurley <peter@hurleysoftware.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Rashed97/caf-kernel-msm-3.10/commits/3bb76d57f40a3d086b386c26e4340ba3017fd471"}]}