{"push_id":1281787472,"size":444,"distinct_size":0,"ref":"refs/heads/linaro/linux-linaro-lsk-v4.4-rt-test","head":"7b324954a4d9bbef9d6acd7c329f6e1289c1d7cb","before":"c8a04d19821f8ee3ba047681cf23f46722caf596","commits":[{"sha":"391a07164bd14666258390629af929582705db52","author":{"name":"Sebastian Andrzej Siewior","email":"995b3fbc38a4ce5fd89792210752e6a9ba719593@linutronix.de"},"message":"Merge tag 'v4.4.12' into linux-4.4.y-rt\n\nThis is the 4.4.12 stable release","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/391a07164bd14666258390629af929582705db52"},{"sha":"cd557119be458514d390c53fff73608dc326f564","author":{"name":"Sebastian Andrzej Siewior","email":"995b3fbc38a4ce5fd89792210752e6a9ba719593@linutronix.de"},"message":"v4.4.12-rt18\n\nSigned-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/cd557119be458514d390c53fff73608dc326f564"},{"sha":"24383c57b6f7a380ea808fd2acb3c48be1d1cebb","author":{"name":"Thomas Gleixner","email":"352b5f5ba0189d2583768a9bb8247f98115b9038@linutronix.de"},"message":"perf/x86/intel/rapl: Make PMU lock raw\n\nUpstream commit: a208749c6426 (\"perf/x86/intel/rapl: Make PMU lock raw\")\n\nThis lock is taken in hard interrupt context even on Preempt-RT. Make it raw\nso RT does not have to patch it.\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Andi Kleen <andi.kleen@intel.com>\nCc: Arnaldo Carvalho de Melo <acme@redhat.com>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Harish Chegondi <harish.chegondi@intel.com>\nCc: Jacob Pan <jacob.jun.pan@linux.intel.com>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Kan Liang <kan.liang@intel.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Stephane Eranian <eranian@google.com>\nCc: Vince Weaver <vincent.weaver@maine.edu>\nCc: linux-kernel@vger.kernel.org\nCc: stable-rt@vger.kernel.org\nLink: http://lkml.kernel.org/r/20160222221012.669411833@linutronix.de\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/24383c57b6f7a380ea808fd2acb3c48be1d1cebb"},{"sha":"91103dcc87625e1d15df67ef94a7421cf11660f0","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"sched,preempt: Fix preempt_count manipulations\n\nVikram reported that his ARM64 compiler managed to 'optimize' away the\npreempt_count manipulations in code like:\n\n\tpreempt_enable_no_resched();\n\tput_user();\n\tpreempt_disable();\n\nIrrespective of that fact that that is horrible code that should be\nfixed for many reasons, it does highlight a deficiency in the generic\npreempt_count manipulators. As it is never right to combine/elide\npreempt_count manipulations like this.\n\nTherefore sprinkle some volatile in the two generic accessors to\nensure the compiler is aware of the fact that the preempt_count is\nobserved outside of the regular program-order view and thus cannot be\noptimized away like this.\n\nx86; the only arch not using the generic code is not affected as we\ndo all this in asm in order to use the segment base per-cpu stuff.\n\nCc: stable@vger.kernel.org\nCc: stable-rt@vger.kernel.org\nCc: Thomas Gleixner <tglx@linutronix.de>\nFixes: a787870924db (\"sched, arch: Create asm/preempt.h\")\nReported-by: Vikram Mulukutla <markivx@codeaurora.org>\nTested-by: Vikram Mulukutla <markivx@codeaurora.org>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nSigned-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/91103dcc87625e1d15df67ef94a7421cf11660f0"},{"sha":"e36cdee287f769894d6059c726f9d5dca602b399","author":{"name":"Sebastian Andrzej Siewior","email":"995b3fbc38a4ce5fd89792210752e6a9ba719593@linutronix.de"},"message":"kernel/rtmutex: only warn once on a try lock from bad context\n\nOne warning should be enough to get one motivated to fix this. It is\npossible that this happens more than once and so starts flooding the\noutput. Later the prints will be suppressed so we only get half of it.\nDepending on the console system used it might not be helpfull.\n\nSigned-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/e36cdee287f769894d6059c726f9d5dca602b399"},{"sha":"39f6ab68402e6be5668188b9c9ebe0d83ce1d49b","author":{"name":"Sebastian Andrzej Siewior","email":"995b3fbc38a4ce5fd89792210752e6a9ba719593@linutronix.de"},"message":"kernel/printk: Don't try to print from IRQ/NMI region\n\nOn -RT we try to acquire sleeping locks which might lead to warnings\nfrom lockdep or a warn_on() from spin_try_lock() (which is a rtmutex on\nRT).\nWe don't print in general from a IRQ off region so we should not try\nthis via console_unblank() / bust_spinlocks() as well.\n\nSigned-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/39f6ab68402e6be5668188b9c9ebe0d83ce1d49b"},{"sha":"86e11f59ef0585c69847d3993f5f98d0af414d9c","author":{"name":"Sebastian Andrzej Siewior","email":"995b3fbc38a4ce5fd89792210752e6a9ba719593@linutronix.de"},"message":"arm: lazy preempt: correct resched condition\n\nIf we get out of preempt_schedule_irq() then we check for NEED_RESCHED\nand call the former function again if set because the preemption counter\nhas be zero at this point.\nHowever the counter for lazy-preempt might not be zero therefore we have\nto check the counter before looking at the need_resched_lazy flag.\n\nCc: stable-rt@vger.kernel.org\nSigned-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/86e11f59ef0585c69847d3993f5f98d0af414d9c"},{"sha":"f68819e461b46ed661225ddce8ae3916cd25b9ab","author":{"name":"Sebastian Andrzej Siewior","email":"995b3fbc38a4ce5fd89792210752e6a9ba719593@linutronix.de"},"message":"v4.4.12-rt19\n\nSigned-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/f68819e461b46ed661225ddce8ae3916cd25b9ab"},{"sha":"0dec8c0d67c64401d97122e4eba347ccc5850622","author":{"name":"James Bottomley","email":"c61de33534998ae239ac3bcee9c77ffbb5713c74@HansenPartnership.com"},"message":"scsi_lib: correctly retry failed zero length REQ_TYPE_FS commands\n\ncommit a621bac3044ed6f7ec5fa0326491b2d4838bfa93 upstream.\n\nWhen SCSI was written, all commands coming from the filesystem\n(REQ_TYPE_FS commands) had data.  This meant that our signal for needing\nto complete the command was the number of bytes completed being equal to\nthe number of bytes in the request.  Unfortunately, with the advent of\nflush barriers, we can now get zero length REQ_TYPE_FS commands, which\nconfuse this logic because they satisfy the condition every time.  This\nmeans they never get retried even for retryable conditions, like UNIT\nATTENTION because we complete them early assuming they're done.  Fix\nthis by special casing the early completion condition to recognise zero\nlength commands with errors and let them drop through to the retry code.\n\nReported-by: Sebastian Parschauer <s.parschauer@gmx.de>\nSigned-off-by: James E.J. Bottomley <jejb@linux.vnet.ibm.com>\nTested-by: Jack Wang <jinpu.wang@profitbricks.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/0dec8c0d67c64401d97122e4eba347ccc5850622"},{"sha":"c54c115da7214a41a697180964cf6d7a5a50b599","author":{"name":"Ewan D. Milne","email":"cded145a908be3e02214f20f5d969606627c9934@redhat.com"},"message":"scsi: Add QEMU CD-ROM to VPD Inquiry Blacklist\n\ncommit fbd83006e3e536fcb103228d2422ea63129ccb03 upstream.\n\nLinux fails to boot as a guest with a QEMU CD-ROM:\n\n[    4.439488] ata2.00: ATAPI: QEMU CD-ROM, 0.8.2, max UDMA/100\n[    4.443649] ata2.00: configured for MWDMA2\n[    4.450267] scsi 1:0:0:0: CD-ROM            QEMU     QEMU CD-ROM      0.8. PQ: 0 ANSI: 5\n[    4.464317] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen\n[    4.464319] ata2.00: BMDMA stat 0x5\n[    4.464339] ata2.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 0 dma 16640 in\n[    4.464339]          Inquiry 12 01 00 00 ff 00res 48/20:02:00:24:00/00:00:00:00:00/a0 Emask 0x2 (HSM violation)\n[    4.464341] ata2.00: status: { DRDY DRQ }\n[    4.465864] ata2: soft resetting link\n[    4.625971] ata2.00: configured for MWDMA2\n[    4.628290] ata2: EH complete\n[    4.646670] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen\n[    4.646671] ata2.00: BMDMA stat 0x5\n[    4.646683] ata2.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 0 dma 16640 in\n[    4.646683]          Inquiry 12 01 00 00 ff 00res 48/20:02:00:24:00/00:00:00:00:00/a0 Emask 0x2 (HSM violation)\n[    4.646685] ata2.00: status: { DRDY DRQ }\n[    4.648193] ata2: soft resetting link\n\n...\n\nFix this by suppressing VPD inquiry for this device.\n\nSigned-off-by: Ewan D. Milne <emilne@redhat.com>\nReported-by: Jan Stancek <jstancek@redhat.com>\nTested-by: Jan Stancek <jstancek@redhat.com>\nReviewed-by: Johannes Thumshirn <jthumshirn@suse.de>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/dianlujitao/CAF_kernel_msm-3.18/commits/c54c115da7214a41a697180964cf6d7a5a50b599"},{"sha":"23cdd8c3cbe9d790f23d7f9ae14e9b828f56f69c","author":{"name":"Richard Alpe","email":"2cddf75a0c06f7765f0d68efc9832a4c62ba6b65@ericsson.com"},"message":"tipc: check nl sock before parsing nested attributes\n\n[ Upstream commit 45e093ae2830cd1264677d47ff9a95a71f5d9f9c ]\n\nMake sure the socket for which the user is listing publication exists\nbefore parsing the socket netlink attributes.\n\nPrior to this patch a call without any socket caused a NULL pointer\ndereference in tipc_nl_publ_dump().\n\nTested-and-reported-by: Baozeng Ding <sploving1@gmail.com>\nSigned-off-by: Richard Alpe <richard.alpe@ericsson.com>\nAcked-by: Jon Maloy <jon.maloy@ericsson.cm>\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/dianlujitao/CAF_kernel_msm-3.18/commits/23cdd8c3cbe9d790f23d7f9ae14e9b828f56f69c"},{"sha":"49543942beb1b9ca95709d6cfa67708932aa4d11","author":{"name":"Herbert Xu","email":"b06c1e85ee1d40a691f7eaf317640579555a220e@gondor.apana.org.au"},"message":"netlink: Fix dump skb leak/double free\n\n[ Upstream commit 92964c79b357efd980812c4de5c1fd2ec8bb5520 ]\n\nWhen we free cb->skb after a dump, we do it after releasing the\nlock.  This means that a new dump could have started in the time\nbeing and we'll end up freeing their skb instead of ours.\n\nThis patch saves the skb and module before we unlock so we free\nthe right memory.\n\nFixes: 16b304f3404f (\"netlink: Eliminate kmalloc in netlink dump operation.\")\nReported-by: Baozeng Ding <sploving1@gmail.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\nAcked-by: Cong Wang <xiyou.wangcong@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/dianlujitao/CAF_kernel_msm-3.18/commits/49543942beb1b9ca95709d6cfa67708932aa4d11"},{"sha":"6a58f3e12e8e5c330940b38cc8c98d52171aefa8","author":{"name":"Richard Alpe","email":"2cddf75a0c06f7765f0d68efc9832a4c62ba6b65@ericsson.com"},"message":"tipc: fix nametable publication field in nl compat\n\n[ Upstream commit 03aaaa9b941e136757b55c4cf775aab6068dfd94 ]\n\nThe publication field of the old netlink API should contain the\npublication key and not the publication reference.\n\nFixes: 44a8ae94fd55 (tipc: convert legacy nl name table dump to nl compat)\nSigned-off-by: Richard Alpe <richard.alpe@ericsson.com>\nAcked-by: Jon Maloy <jon.maloy@ericsson.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/dianlujitao/CAF_kernel_msm-3.18/commits/6a58f3e12e8e5c330940b38cc8c98d52171aefa8"},{"sha":"835d0122a57ffaea43162d0e7a4f5bf25d2af78b","author":{"name":"Jiri Pirko","email":"a7e702c6c67814648a4f7569508b76ff202ca280@mellanox.com"},"message":"switchdev: pass pointer to fib_info instead of copy\n\n[ Upstream commit da4ed55165d41b1073f9a476f1c18493e9bf8c8e ]\n\nThe problem is that fib_info->nh is [0] so the struct fib_info\nallocation size depends on number of nexthops. If we just copy fib_info,\nwe do not copy the nexthops info and driver accesses memory which is not\nours.\n\nGiven the fact that fib4 does not defer operations and therefore it does\nnot need copy, just pass the pointer down to drivers as it was done\nbefore.\n\nFixes: 850d0cbc91 (\"switchdev: remove pointers from switchdev objects\")\nSigned-off-by: Jiri Pirko <jiri@mellanox.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/dianlujitao/CAF_kernel_msm-3.18/commits/835d0122a57ffaea43162d0e7a4f5bf25d2af78b"},{"sha":"bccd56fad0433ef1ed0661bb3a4055503cdec4e9","author":{"name":"Jason Wang","email":"74f299602f66bf37e22877b931fc5996e932eb30@redhat.com"},"message":"tuntap: correctly wake up process during uninit\n\n[ Upstream commit addf8fc4acb1cf79492ac64966f07178793cb3d7 ]\n\nWe used to check dev->reg_state against NETREG_REGISTERED after each\ntime we are woke up. But after commit 9e641bdcfa4e (\"net-tun:\nrestructure tun_do_read for better sleep/wakeup efficiency\"), it uses\nskb_recv_datagram() which does not check dev->reg_state. This will\nresult if we delete a tun/tap device after a process is blocked in the\nreading. The device will wait for the reference count which was held\nby that process for ever.\n\nFixes this by using RCV_SHUTDOWN which will be checked during\nsk_recv_datagram() before trying to wake up the process during uninit.\n\nFixes: 9e641bdcfa4e (\"net-tun: restructure tun_do_read for better\nsleep/wakeup efficiency\")\nCc: Eric Dumazet <edumazet@google.com>\nCc: Xi Wang <xii@google.com>\nCc: Michael S. Tsirkin <mst@redhat.com>\nSigned-off-by: Jason Wang <jasowang@redhat.com>\nAcked-by: Eric Dumazet <edumazet@google.com>\nAcked-by: Michael S. Tsirkin <mst@redhat.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/dianlujitao/CAF_kernel_msm-3.18/commits/bccd56fad0433ef1ed0661bb3a4055503cdec4e9"},{"sha":"5b7ea922e1754107f77d146011612f2e42600cc1","author":{"name":"Eric W. Biederman","email":"e4ccc9f9b54eebd6cb8fc7643b8083f628b68ff2@xmission.com"},"message":"bpf: Use mount_nodev not mount_ns to mount the bpf filesystem\n\n[ Upstream commit e27f4a942a0ee4b84567a3c6cfa84f273e55cbb7 ]\n\nWhile reviewing the filesystems that set FS_USERNS_MOUNT I spotted the\nbpf filesystem.  Looking at the code I saw a broken usage of mount_ns\nwith current->nsproxy->mnt_ns. As the code does not acquire a\nreference to the mount namespace it can not possibly be correct to\nstore the mount namespace on the superblock as it does.\n\nReplace mount_ns with mount_nodev so that each mount of the bpf\nfilesystem returns a distinct instance, and the code is not buggy.\n\nIn discussion with Hannes Frederic Sowa it was reported that the use\nof mount_ns was an attempt to have one bpf instance per mount\nnamespace, in an attempt to keep resources that pin resources from\nhiding.  That intent simply does not work, the vfs is not built to\nallow that kind of behavior.  Which means that the bpf filesystem\nreally is buggy both semantically and in it's implemenation as it does\nnot nor can it implement the original intent.\n\nThis change is userspace visible, but my experience with similar\nfilesystems leads me to believe nothing will break with a model of each\nmount of the bpf filesystem is distinct from all others.\n\nFixes: b2197755b263 (\"bpf: add support for persistent maps/progs\")\nCc: Hannes Frederic Sowa <hannes@stressinduktion.org>\nAcked-by: Daniel Borkmann <daniel@iogearbox.net>\nSigned-off-by: \"Eric W. Biederman\" <ebiederm@xmission.com>\nAcked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\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/dianlujitao/CAF_kernel_msm-3.18/commits/5b7ea922e1754107f77d146011612f2e42600cc1"},{"sha":"ab1f253ddccc235520fa4f70d32a8dd6bf8ef346","author":{"name":"Hannes Frederic Sowa","email":"384333b8ca49bccf53afadd43ca0007cb9efc1df@stressinduktion.org"},"message":"udp: prevent skbs lingering in tunnel socket queues\n\n[ Upstream commit e5aed006be918af163eb397e45aa5ea6cefd5e01 ]\n\nIn case we find a socket with encapsulation enabled we should call\nthe encap_recv function even if just a udp header without payload is\navailable. The callbacks are responsible for correctly verifying and\ndropping the packets.\n\nAlso, in case the header validation fails for geneve and vxlan we\nshouldn't put the skb back into the socket queue, no one will pick\nthem up there.  Instead we can simply discard them in the respective\nencap_recv functions.\n\nSigned-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\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/dianlujitao/CAF_kernel_msm-3.18/commits/ab1f253ddccc235520fa4f70d32a8dd6bf8ef346"},{"sha":"f5f16bf66d7e07e5a04f07226caefeaf3136c83a","author":{"name":"Nicolas Dichtel","email":"6738a2db8b42127254341bdb65a9775d52a2feaa@6wind.com"},"message":"uapi glibc compat: fix compilation when !__USE_MISC in glibc\n\n[ Upstream commit f0a3fdca794d1e68ae284ef4caefe681f7c18e89 ]\n\nThese structures are defined only if __USE_MISC is set in glibc net/if.h\nheaders, ie when _BSD_SOURCE or _SVID_SOURCE are defined.\n\nCC: Jan Engelhardt <jengelh@inai.de>\nCC: Josh Boyer <jwboyer@fedoraproject.org>\nCC: Stephen Hemminger <shemming@brocade.com>\nCC: Waldemar Brodkorb <mail@waldemar-brodkorb.de>\nCC: Gabriel Laskar <gabriel@lse.epita.fr>\nCC: Mikko Rapeli <mikko.rapeli@iki.fi>\nFixes: 4a91cb61bb99 (\"uapi glibc compat: fix compile errors when glibc net/if.h included before linux/if.h\")\nSigned-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.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/dianlujitao/CAF_kernel_msm-3.18/commits/f5f16bf66d7e07e5a04f07226caefeaf3136c83a"},{"sha":"bfe951d547bf15bf1192abd20773e6603dacadf1","author":{"name":"Daniel Borkmann","email":"4b94a04674ad2c69d990e94ab196ac3f8e9e03d4@iogearbox.net"},"message":"bpf, inode: disallow userns mounts\n\n[ Upstream commit 612bacad78ba6d0a91166fc4487af114bac172a8 ]\n\nFollow-up to commit e27f4a942a0e (\"bpf: Use mount_nodev not mount_ns\nto mount the bpf filesystem\"), which removes the FS_USERNS_MOUNT flag.\n\nThe original idea was to have a per mountns instance instead of a\nsingle global fs instance, but that didn't work out and we had to\nswitch to mount_nodev() model. The intent of that middle ground was\nthat we avoid users who don't play nice to create endless instances\nof bpf fs which are difficult to control and discover from an admin\npoint of view, but at the same time it would have allowed us to be\nmore flexible with regard to namespaces.\n\nTherefore, since we now did the switch to mount_nodev() as a fix\nwhere individual instances are created, we also need to remove userns\nmount flag along with it to avoid running into mentioned situation.\nI don't expect any breakage at this early point in time with removing\nthe flag and we can revisit this later should the requirement for\nthis come up with future users. This and commit e27f4a942a0e have\nbeen split to facilitate tracking should any of them run into the\nunlikely case of causing a regression.\n\nFixes: b2197755b263 (\"bpf: add support for persistent maps/progs\")\nSigned-off-by: Daniel Borkmann <daniel@iogearbox.net>\nAcked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>\nAcked-by: Alexei Starovoitov <ast@kernel.org>\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/dianlujitao/CAF_kernel_msm-3.18/commits/bfe951d547bf15bf1192abd20773e6603dacadf1"},{"sha":"450db517b9223908ab5c1a9b5ddce3b6c4d75b18","author":{"name":"Edward Cree","email":"8ad9e791d4a688eb80fcc280ef9e0a7e0f9d0db5@solarflare.com"},"message":"sfc: on MC reset, clear PIO buffer linkage in TXQs\n\n[ Upstream commit c0795bf64cba4d1b796fdc5b74b33772841ed1bb ]\n\nOtherwise, if we fail to allocate new PIO buffers, our TXQs will try to\nuse the old ones, which aren't there any more.\n\nFixes: 183233bec810 \"sfc: Allocate and link PIO buffers; map them with write-combining\"\nSigned-off-by: Edward Cree <ecree@solarflare.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/dianlujitao/CAF_kernel_msm-3.18/commits/450db517b9223908ab5c1a9b5ddce3b6c4d75b18"}]}
{"actor":{"display_login":"dianlujitao"}}