{"push_id":2043023963,"size":174,"distinct_size":174,"ref":"refs/heads/cm-14.1","head":"8bebfd0f4962ff53221f8d32d563dfe51b6062bb","before":"153d5a3128daf9417af74ef718b6c907ec3c097b","commits":[{"sha":"c722d373fdf59e1c831d48d26267a719e37a2234","author":{"name":"Nick Desaulniers","email":"b951273a67bf33267cd4dff69171cdef4e5efbe7@google.com"},"message":"Revert \"proc: smaps: Allow smaps access for CAP_SYS_RESOURCE\"\n\nThis reverts commit 2d39f683c5f48bfdd574d4c3c188ae9b15747c65.\n\nBug: 34951864\nBug: 36468447\nChange-Id: I87bd92e096c6c28a53b9ecf302ae008f5e58eba1\nSigned-off-by: Nick Desaulniers <ndesaulniers@google.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/c722d373fdf59e1c831d48d26267a719e37a2234"},{"sha":"77b6eea31cdd7048ce4af8ede39d60b237d87aa8","author":{"name":"Utkarsh Saxena","email":"a77f4916ff39fc133abd3bb49cf55a0c1b56ef54@codeaurora.org"},"message":"msm: ipa: Fix for missing int overflow check in the refcount library\n\nOverflow of reference counter can lead to memory leak.\n\nBefore incrementing the reference count, check with\nU32_MAX and return for error check.\n\nBug: 35467471\nChange-Id: Ib96d36574ee086ec73c9836110cb2c98e8ae3d66\nAcked-by: Mohammed Javid <mjavid@qti.qualcomm.com>\nSigned-off-by: Utkarsh Saxena <usaxena@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/77b6eea31cdd7048ce4af8ede39d60b237d87aa8"},{"sha":"9fa699793110268a701b618f0e66bc49291791dc","author":{"name":"Jin Qian","email":"0a9aa3d3574a19f4323dcc26c6c102ebcca97ce1@google.com"},"message":"BACKPORT: f2fs: sanity check log_blocks_per_seg\n\nf2fs currently only supports 4KB block size and 2MB segment size.\nSanity check log_blocks_per_seg == 9, i.e. 2MB/4KB = (1 << 9)\n\nPartially\n(cherry-picked from commit 9a59b62fd88196844cee5fff851bee2cfd7afb6e)\n\nf2fs: do more integrity verification for superblock\n\nDo more sanity check for superblock during ->mount.\n\nSigned-off-by: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>\n\nBug: 36817013\nChange-Id: I0be52e54fba82083068337ceb9f7ad985a87319f\nSigned-off-by: Jin Qian <jinqian@google.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/9fa699793110268a701b618f0e66bc49291791dc"},{"sha":"4e265176c877a45dcdf0f0436c7e705c4a919a0b","author":{"name":"Dennis Cagle","email":"1c958d084f7278f93cbdf16f75fd9d20fa6ac1af@codeaurora.org"},"message":"qcdev: Check the digest length during the SHA operations\n\nCheck the digest length to avoid buffer overflow while\ndoing the SHA operations.\n\nBug: 36591162\nCRs-Fixed: 2045061\nChange-Id: I4d3fb20723f59e905a672edaf84ee5d0865905b1\nSigned-off-by: Brahmaji K <bkomma@codeaurora.org>\nSigned-off-by: Dennis Cagle <d-cagle@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/4e265176c877a45dcdf0f0436c7e705c4a919a0b"},{"sha":"eec3bbf746a6a06db9cf2891f21a32770667c9ec","author":{"name":"Robb Glasser","email":"b0c5b77df4bff135c4bb9b77cfba385da1f20c54@google.com"},"message":"Prevent potential double frees in sg driver\n\nsg_ioctl could be spammed by requests, leading to a double free in\n__free_pages. This protects the entry points of sg_ioctl where the\nmemory could be corrupted by a double call to __free_pages if multiple\nrequests are happening concurrently.\n\nBug:35644812\n\nChange-Id: Ie13f65beb6974430f90292e2742841b26aecb8b1\nSigned-off-by: Robb Glasser <rglasser@google.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/eec3bbf746a6a06db9cf2891f21a32770667c9ec"},{"sha":"9eca3eeac2a1b82c43b3704748828faee0a8d569","author":{"name":"Ben Seri","email":"9c85637c38b80821c7bd8a03bde7b59da81ab77d@armis.com"},"message":"Bluetooth: Properly check L2CAP config option output buffer length\n\ncommit e860d2c904d1a9f38a24eb44c9f34b8f915a6ea3 upstream.\n\nValidate the output buffer length for L2CAP config requests and responses\nto avoid overflowing the stack buffer used for building the option blocks.\n\nChange-Id: I2538f2a98ded3dfbcd78e65a636b42f5afe66c37\nCc: stable@vger.kernel.org\nSigned-off-by: Ben Seri <ben@armis.com>\nSigned-off-by: Marcel Holtmann <marcel@holtmann.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/9eca3eeac2a1b82c43b3704748828faee0a8d569"},{"sha":"9cfaf44f535cb8062952b6a92116dcf60e7c2c29","author":{"name":"Hugh Dickins","email":"11bd16bbccd141ee47d9426ad06afbc74b915cf0@google.com"},"message":"mm: larger stack guard gap, between vmas\n\ncommit 1be7107fbe18eed3e319a6c3e83c78254b693acb upstream.\n\nStack guard page is a useful feature to reduce a risk of stack smashing\ninto a different mapping. We have been using a single page gap which\nis sufficient to prevent having stack adjacent to a different mapping.\nBut this seems to be insufficient in the light of the stack usage in\nuserspace. E.g. glibc uses as large as 64kB alloca() in many commonly\nused functions. Others use constructs liks gid_t buffer[NGROUPS_MAX]\nwhich is 256kB or stack strings with MAX_ARG_STRLEN.\n\nThis will become especially dangerous for suid binaries and the default\nno limit for the stack size limit because those applications can be\ntricked to consume a large portion of the stack and a single glibc call\ncould jump over the guard page. These attacks are not theoretical,\nunfortunatelly.\n\nMake those attacks less probable by increasing the stack guard gap\nto 1MB (on systems with 4k pages; but make it depend on the page size\nbecause systems with larger base pages might cap stack allocations in\nthe PAGE_SIZE units) which should cover larger alloca() and VLA stack\nallocations. It is obviously not a full fix because the problem is\nsomehow inherent, but it should reduce attack space a lot.\n\nOne could argue that the gap size should be configurable from userspace,\nbut that can be done later when somebody finds that the new 1MB is wrong\nfor some special case applications.  For now, add a kernel command line\noption (stack_guard_gap) to specify the stack gap size (in page units).\n\nImplementation wise, first delete all the old code for stack guard page:\nbecause although we could get away with accounting one extra page in a\nstack vma, accounting a larger gap can break userspace - case in point,\na program run with \"ulimit -S -v 20000\" failed when the 1MB gap was\ncounted for RLIMIT_AS; similar problems could come with RLIMIT_MLOCK\nand strict non-overcommit mode.\n\nInstead of keeping gap inside the stack vma, maintain the stack guard\ngap as a gap between vmas: using vm_start_gap() in place of vm_start\n(or vm_end_gap() in place of vm_end if VM_GROWSUP) in just those few\nplaces which need to respect the gap - mainly arch_get_unmapped_area(),\nand and the vma tree's subtree_gap support for that.\n\nOriginal-patch-by: Oleg Nesterov <oleg@redhat.com>\nOriginal-patch-by: Michal Hocko <mhocko@suse.com>\nSigned-off-by: Hugh Dickins <hughd@google.com>\nAcked-by: Michal Hocko <mhocko@suse.com>\nTested-by: Helge Deller <deller@gmx.de> # parisc\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n[Hugh Dickins: Backported to 3.2]\n[bwh: Fix more instances of vma->vm_start in sparc64 impl. of\n arch_get_unmapped_area_topdown() and generic impl. of\n hugetlb_get_unmapped_area()]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\n\nChange-Id: Ic6897a71683a9ac2c220103fb4abcb6c5f92fc14","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/9cfaf44f535cb8062952b6a92116dcf60e7c2c29"},{"sha":"1527de267087aeea9f1415497a7c7bae7fd69684","author":{"name":"Helge Deller","email":"1f1989f8847b0c866a7c344d7b6e7f5b396fbba1@gmx.de"},"message":"Allow stack to grow up to address space limit\n\ncommit bd726c90b6b8ce87602208701b208a208e6d5600 upstream.\n\nFix expand_upwards() on architectures with an upward-growing stack (parisc,\nmetag and partly IA-64) to allow the stack to reliably grow exactly up to\nthe address space limit given by TASK_SIZE.\n\nChange-Id: Ia8c551bafd5bdf8d6e67c081bf651705890b3420\nSigned-off-by: Helge Deller <deller@gmx.de>\nAcked-by: Hugh Dickins <hughd@google.com>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/1527de267087aeea9f1415497a7c7bae7fd69684"},{"sha":"d019af6a28302c0a9635f294d37dcdfa77162f91","author":{"name":"Kees Cook","email":"999bfbbf6e15a9d6aba3dfebadcec55340f87c3f@chromium.org"},"message":"fs/exec.c: account for argv/envp pointers\n\ncommit 98da7d08850fb8bdeb395d6368ed15753304aa0c upstream.\n\nWhen limiting the argv/envp strings during exec to 1/4 of the stack limit,\nthe storage of the pointers to the strings was not included.  This means\nthat an exec with huge numbers of tiny strings could eat 1/4 of the stack\nlimit in strings and then additional space would be later used by the\npointers to the strings.\n\nFor example, on 32-bit with a 8MB stack rlimit, an exec with 1677721\nsingle-byte strings would consume less than 2MB of stack, the max (8MB /\n4) amount allowed, but the pointers to the strings would consume the\nremaining additional stack space (1677721 * 4 == 6710884).\n\nThe result (1677721 + 6710884 == 8388605) would exhaust stack space\nentirely.  Controlling this stack exhaustion could result in\npathological behavior in setuid binaries (CVE-2017-1000365).\n\n[akpm@linux-foundation.org: additional commenting from Kees]\nFixes: b6a2fea39318 (\"mm: variable length argument support\")\nLink: http://lkml.kernel.org/r/20170622001720.GA32173@beast\nSigned-off-by: Kees Cook <keescook@chromium.org>\nAcked-by: Rik van Riel <riel@redhat.com>\nAcked-by: Michal Hocko <mhocko@suse.com>\nCc: Alexander Viro <viro@zeniv.linux.org.uk>\nCc: Qualys Security Advisory <qsa@qualys.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n[bwh: Backported to 3.2: use ACCESS_ONCE() instead of READ_ONCE()]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\n\nChange-Id: Id4490b29b3d786e7bf72d2dccef0f5d198427a9c","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/d019af6a28302c0a9635f294d37dcdfa77162f91"},{"sha":"073be717998d3f9993bcbdd9c8b8a9384a984023","author":{"name":"Takashi Iwai","email":"dd0a9a4ae370c51e6d7099900a4bf6656524e055@suse.de"},"message":"ALSA: timer: Fix race between read and ioctl\n\ncommit d11662f4f798b50d8c8743f433842c3e40fe3378 upstream.\n\nThe read from ALSA timer device, the function snd_timer_user_tread(),\nmay access to an uninitialized struct snd_timer_user fields when the\nread is concurrently performed while the ioctl like\nsnd_timer_user_tselect() is invoked.  We have already fixed the races\namong ioctls via a mutex, but we seem to have forgotten the race\nbetween read vs ioctl.\n\nThis patch simply applies (more exactly extends the already applied\nrange of) tu->ioctl_lock in snd_timer_user_tread() for closing the\nrace window.\n\nChange-Id: I7b0a4f37ac15739df249b09d5f5865b8c9f9957e\nReported-by: Alexander Potapenko <glider@google.com>\nTested-by: Alexander Potapenko <glider@google.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/073be717998d3f9993bcbdd9c8b8a9384a984023"},{"sha":"d22794d61d5f27fc77247d70f76eeb6b68a108ee","author":{"name":"Takashi Iwai","email":"dd0a9a4ae370c51e6d7099900a4bf6656524e055@suse.de"},"message":"ALSA: timer: Fix missing queue indices reset at SNDRV_TIMER_IOCTL_SELECT\n\nsnd_timer_user_tselect() reallocates the queue buffer dynamically, but\nit forgot to reset its indices.  Since the read may happen\nconcurrently with ioctl and snd_timer_user_tselect() allocates the\nbuffer via kmalloc(), this may lead to the leak of uninitialized\nkernel-space data, as spotted via KMSAN:\n\n  BUG: KMSAN: use of unitialized memory in snd_timer_user_read+0x6c4/0xa10\n  CPU: 0 PID: 1037 Comm: probe Not tainted 4.11.0-rc5+ #2739\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011\n  Call Trace:\n   __dump_stack lib/dump_stack.c:16\n   dump_stack+0x143/0x1b0 lib/dump_stack.c:52\n   kmsan_report+0x12a/0x180 mm/kmsan/kmsan.c:1007\n   kmsan_check_memory+0xc2/0x140 mm/kmsan/kmsan.c:1086\n   copy_to_user ./arch/x86/include/asm/uaccess.h:725\n   snd_timer_user_read+0x6c4/0xa10 sound/core/timer.c:2004\n   do_loop_readv_writev fs/read_write.c:716\n   __do_readv_writev+0x94c/0x1380 fs/read_write.c:864\n   do_readv_writev fs/read_write.c:894\n   vfs_readv fs/read_write.c:908\n   do_readv+0x52a/0x5d0 fs/read_write.c:934\n   SYSC_readv+0xb6/0xd0 fs/read_write.c:1021\n   SyS_readv+0x87/0xb0 fs/read_write.c:1018\n\nThis patch adds the missing reset of queue indices.  Together with the\nprevious fix for the ioctl/read race, we cover the whole problem.\n\nReported-by: Alexander Potapenko <glider@google.com>\nTested-by: Alexander Potapenko <glider@google.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/d22794d61d5f27fc77247d70f76eeb6b68a108ee"},{"sha":"1476a4a02ecd09cc6f1243c89e8ed10bac2d5896","author":{"name":"Thomas Gleixner","email":"352b5f5ba0189d2583768a9bb8247f98115b9038@linutronix.de"},"message":"timerfd: Protect the might cancel mechanism proper\n\ncommit 1e38da300e1e395a15048b0af1e5305bd91402f6 upstream.\n\nThe handling of the might_cancel queueing is not properly protected, so\nparallel operations on the file descriptor can race with each other and\nlead to list corruptions or use after free.\n\nProtect the context for these operations with a seperate lock.\n\nThe wait queue lock cannot be reused for this because that would create a\nlock inversion scenario vs. the cancel lock. Replacing might_cancel with an\natomic (atomic_t or atomic bit) does not help either because it still can\nrace vs. the actual list operation.\n\nBug: 36266767\n\nReported-by: Dmitry Vyukov <dvyukov@google.com>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: \"linux-fsdevel@vger.kernel.org\"\nCc: syzkaller <syzkaller@googlegroups.com>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nCc: linux-fsdevel@vger.kernel.org\nLink: http://lkml.kernel.org/r/alpine.DEB.2.20.1701311521430.3457@nanos\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Siqi Lin <siqilin@google.com>\nChange-Id: I122753e0920e51757d3012cd1a133e823719be51","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/1476a4a02ecd09cc6f1243c89e8ed10bac2d5896"},{"sha":"3242fac25a2cfb549ad6853d737814a265ec8dd5","author":{"name":"Jin Qian","email":"0a9aa3d3574a19f4323dcc26c6c102ebcca97ce1@google.com"},"message":"UPSTREAM: f2fs: sanity check segment count\n\ncommit b9dd46188edc2f0d1f37328637860bb65a771124 upstream.\n\nF2FS uses 4 bytes to represent block address. As a result, supported\nsize of disk is 16 TB and it equals to 16 * 1024 * 1024 / 2 segments.\n\nSigned-off-by: Jin Qian <jinqian@google.com>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nBug: 36815012\nChange-Id: I30ea36df066bc07e32e767336b7cae12063fe415","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/3242fac25a2cfb549ad6853d737814a265ec8dd5"},{"sha":"b4813f634421f4a520f66b6a53f4754cce6f6c9a","author":{"name":"Jin Qian","email":"0a9aa3d3574a19f4323dcc26c6c102ebcca97ce1@android.com"},"message":"BACKPORT: f2fs: sanity check checkpoint segno and blkoff\n\nMake sure segno and blkoff read from raw image are valid.\n\nFixed conflicts due to missing commit 1e968fdfe69e\n(\"f2fs: introduce f2fs_cp_error for readability\") and commit 6bacf52fb58a\n(\"f2fs: add unlikely() macro for compiler more aggressively\").\n\n(url https://sourceforge.net/p/linux-f2fs/mailman/message/35835945)\n\nSigned-off-by: Jin Qian <jinqian@google.com>\nSigned-off-by: Siqi Lin <siqilin@google.com>\nBug: 36588520\nChange-Id: Iba66ab97d3d0870ea48b5ef192d9075f225a934a","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/b4813f634421f4a520f66b6a53f4754cce6f6c9a"},{"sha":"a86cb24d43f85d2beaf7afd1232c69cb893b3a2b","author":{"name":"Siena Richard","email":"d38b195d0a21dccff7df190f3906e3fea13874b3@codeaurora.org"},"message":"ASoC: msm: qdsp6v2: extend validation of virtual address\n\nValidate a buffer virtual address is fully within the region before\nreturning the region to ensure functionality for an extended edge case.\n\nChange-Id: Iba3e080889980f393d6a9f0afe0231408b92d654\nSigned-off-by: Siena Richard <sienar@codeaurora.org>\nCRs-fixed: 1108461\n\nBug: 38195131\nChange-Id: Ib527a380a857719bff8254be514133528bd64c75","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/a86cb24d43f85d2beaf7afd1232c69cb893b3a2b"},{"sha":"ba5559722a7c70d918550d6733913cd3b078af46","author":{"name":"Gaoxiang Chen","email":"e7c95b2efcc6251eae2b715eaa0e35cb73e46ad3@codeaurora.org"},"message":"msm: camera: fix off-by-one overflow in msm_isp_get_bufq\n\nIn msm_isp_get_bufq, if bufq_index equals buf_mgr->num_buf_q,\nit will pass the check, leading to off-by-one overflow\n(exceed the length of array by one element).\n\nCRs-Fixed: 2031677\nBug: 36136563\nChange-Id: I7ea465897e2c37de6ca0155c3e225f1444b3cf13\nSigned-off-by: Gaoxiang Chen <gaochen@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/ba5559722a7c70d918550d6733913cd3b078af46"},{"sha":"5b36f5faa405ed1e1eb26f2f176ce1dbc2ae0afa","author":{"name":"Srinivas Girigowda","email":"a31baf9905f545cc28ca3ed31e582f4e1f5462f1@codeaurora.org"},"message":"prima: Avoid concurrent matrix max param overread\n\nqcacld2.0 to prima propgation\n\nCurrently there is no nl policy defined for vendor sub command\nQCA_NL80211_VENDOR_SUBCMD_GET_CONCURRENCY_MATRIX which may result in\nbuffer overread error.\n\nTo resolve this, add nl policy.\n\nChange-Id: I155efdbb07f1c5fe300bb2be0c2a3fe07c7e134b\nCRs-Fixed: 2058452\nBug: 37712167\nSigned-off-by: Srinivas Girigowda <sgirigow@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/5b36f5faa405ed1e1eb26f2f176ce1dbc2ae0afa"},{"sha":"3575839a7704e5a6a453e6a55a4b44e4f0a3707c","author":{"name":"Ashish Kumar Dhanotiya","email":"7d699db8eba266aab8757e9baa4e23ab2cb09870@codeaurora.org"},"message":"prima: Fix Uninitialized memory issue\n\nqcacld2.0 to prima propgation\n\nThere is a possibility to read uninitialized memory within api\n__wlan_hdd_cfg80211_testmode.\n\nTo resolve this issue, initilaize buffer hb_params with zero.\n\nBug: 62456806\nChange-Id: Ia8061610a8c35aa7290177c0dcd2c5c36d9fcb35\nCRs-Fixed: 2061755\nSigned-off-by: Ecco Park <eccopark@google.com>","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/3575839a7704e5a6a453e6a55a4b44e4f0a3707c"},{"sha":"877788b4052cf8a84ecc1b78af67dab18346b95a","author":{"name":"Agrawal Ashish","email":"beec61756d83ba88d1ff81315ad83fedd155cc31@qti.qualcomm.com"},"message":"wlan: Check for max number of num_dscp_exceptions in QOS map set.\n\nIn ConvertQosMapsetFrame, dscp_exceptions is max of 21 size but\nthere is no limit check for num_dscp_exceptions.\nCheck for max size for num_dscp_exceptions.\n\nChange-Id: Id098da5231b4f3e40abe369e52960859091dc200\nCRs-Fixed: 931435","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/877788b4052cf8a84ecc1b78af67dab18346b95a"},{"sha":"5a14fad6d3dd963b6cc17b3229c0bcac8edf3478","author":{"name":"Agrawal Ashish","email":"beec61756d83ba88d1ff81315ad83fedd155cc31@qti.qualcomm.com"},"message":"wlan: Check for max number of num_dscp_exceptions in QOS map set.\n\nIn ConvertQosMapsetFrame, dscp_exceptions is max of 21 size but\ncurrently its 22.\nCheck for max size for num_dscp_exceptions.\n\nChange-Id: I2cdaa94ea0a899ba8c1d11f17b78b48b0e669433\nCRs-Fixed: 933494","distinct":true,"url":"https://api.github.com/repos/mdmower/android_kernel_huawei_msm8928/commits/5a14fad6d3dd963b6cc17b3229c0bcac8edf3478"}]}
{"actor":{"display_login":"mdmower"}}