{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":207067179,"defaultBranch":"lineage-21","name":"android_kernel_nokia_sdm660","ownerLogin":"LineageOS","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2019-09-08T05:38:51.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/24304779?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1711131547.0","currentOid":""},"activityList":{"items":[{"before":"79f199349ddacc8fa173d51874942ba834baf3a8","after":"8f897d59bc7379a718a3963ca2ba3a62a25dfdac","ref":"refs/heads/lineage-21","pushedAt":"2024-03-22T18:19:07.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"usb: dwc3: Handle charging behavior when usb data is disabled\n\nBug: 221009551\nTest: build, boot\nSigned-off-by: Jimmy Hu \nChange-Id: I82add2a6cb5e3060c930105b1b8b4f45da85f5f8","shortMessageHtmlLink":"usb: dwc3: Handle charging behavior when usb data is disabled"}},{"before":"c5726ceff06d9b62fee635b2d229b93c5074ae9f","after":"79f199349ddacc8fa173d51874942ba834baf3a8","ref":"refs/heads/lineage-21","pushedAt":"2024-03-20T05:28:54.000Z","pushType":"push","commitsCount":11,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"arm64: insn: Fix ldadd instruction encoding\n\ncommit c5e2edeb01ae9ffbdde95bdcdb6d3614ba1eb195 upstream.\n\nGCC 8.1.0 reports that the ldadd instruction encoding, recently added to\ninsn.c, doesn't match the mask and couldn't possibly be identified:\n\n linux/arch/arm64/include/asm/insn.h: In function 'aarch64_insn_is_ldadd':\n linux/arch/arm64/include/asm/insn.h:280:257: warning: bitwise comparison always evaluates to false [-Wtautological-compare]\n\nBits [31:30] normally encode the size of the instruction (1 to 8 bytes)\nand the current instruction value only encodes the 4- and 8-byte\nvariants. At the moment only the BPF JIT needs this instruction, and\ndoesn't require the 1- and 2-byte variants, but to be consistent with\nour other ldr and str instruction encodings, clear the size field in the\ninsn value.\n\nFixes: 34b8ab091f9ef57a (\"bpf, arm64: use more scalable stadd over ldxr / stxr loop in xadd\")\nAcked-by: Daniel Borkmann \nReported-by: Kuninori Morimoto \nChange-Id: I914ba0c9ca65af2996d6b67bf45a0d9fabd0ec92\nSigned-off-by: Yoshihiro Shimoda \nSigned-off-by: Jean-Philippe Brucker \nSigned-off-by: Will Deacon \nSigned-off-by: Greg Kroah-Hartman ","shortMessageHtmlLink":"arm64: insn: Fix ldadd instruction encoding"}},{"before":"e95fa6cef2584fd91c6576900c89678a45fbe9cd","after":"c5726ceff06d9b62fee635b2d229b93c5074ae9f","ref":"refs/heads/lineage-21","pushedAt":"2024-01-12T20:40:34.000Z","pushType":"push","commitsCount":11,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"bpf, arm64: use more scalable stadd over ldxr / stxr loop in xadd\n\ncommit 34b8ab091f9ef57a2bb3c8c8359a0a03a8abf2f9 upstream.\n\nSince ARMv8.1 supplement introduced LSE atomic instructions back in 2016,\nlets add support for STADD and use that in favor of LDXR / STXR loop for\nthe XADD mapping if available. STADD is encoded as an alias for LDADD with\nXZR as the destination register, therefore add LDADD to the instruction\nencoder along with STADD as special case and use it in the JIT for CPUs\nthat advertise LSE atomics in CPUID register. If immediate offset in the\nBPF XADD insn is 0, then use dst register directly instead of temporary\none.\n\nChange-Id: I77c90fb42f826fab672db94eddc9e16bbba3a65f\nSigned-off-by: Daniel Borkmann \nAcked-by: Jean-Philippe Brucker \nAcked-by: Will Deacon \nSigned-off-by: Alexei Starovoitov \nSigned-off-by: Greg Kroah-Hartman ","shortMessageHtmlLink":"bpf, arm64: use more scalable stadd over ldxr / stxr loop in xadd"}},{"before":"42789a7310fe84bc5554853f822bed4950cf1134","after":"2abe836a583ee41b41f4fc5c254a0111e56d0668","ref":"refs/heads/lineage-20","pushedAt":"2024-01-12T20:40:03.000Z","pushType":"push","commitsCount":11,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"bpf, arm64: use more scalable stadd over ldxr / stxr loop in xadd\n\ncommit 34b8ab091f9ef57a2bb3c8c8359a0a03a8abf2f9 upstream.\n\nSince ARMv8.1 supplement introduced LSE atomic instructions back in 2016,\nlets add support for STADD and use that in favor of LDXR / STXR loop for\nthe XADD mapping if available. STADD is encoded as an alias for LDADD with\nXZR as the destination register, therefore add LDADD to the instruction\nencoder along with STADD as special case and use it in the JIT for CPUs\nthat advertise LSE atomics in CPUID register. If immediate offset in the\nBPF XADD insn is 0, then use dst register directly instead of temporary\none.\n\nChange-Id: I77c90fb42f826fab672db94eddc9e16bbba3a65f\nSigned-off-by: Daniel Borkmann \nAcked-by: Jean-Philippe Brucker \nAcked-by: Will Deacon \nSigned-off-by: Alexei Starovoitov \nSigned-off-by: Greg Kroah-Hartman ","shortMessageHtmlLink":"bpf, arm64: use more scalable stadd over ldxr / stxr loop in xadd"}},{"before":"425bbbba5c3b30991cfb8a7292ad305c1946a528","after":"e95fa6cef2584fd91c6576900c89678a45fbe9cd","ref":"refs/heads/lineage-21","pushedAt":"2024-01-08T06:20:46.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"sched: deadline: Add missing WALT code\n\nCAF did not use WALT on msm-4.4 kernels and left out important WALT\nbits.\n\nChange-Id: If5de7100e010f299bd7b2c62720ff309a98c569d","shortMessageHtmlLink":"sched: deadline: Add missing WALT code"}},{"before":"38ebafb7c959c97ae8c8e6406ae77d53a3c0e921","after":"42789a7310fe84bc5554853f822bed4950cf1134","ref":"refs/heads/lineage-20","pushedAt":"2024-01-08T06:20:05.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"sched: deadline: Add missing WALT code\n\nCAF did not use WALT on msm-4.4 kernels and left out important WALT\nbits.\n\nChange-Id: If5de7100e010f299bd7b2c62720ff309a98c569d","shortMessageHtmlLink":"sched: deadline: Add missing WALT code"}},{"before":"dc4f1e378a003c1839941327e7962210211ad2f0","after":"38ebafb7c959c97ae8c8e6406ae77d53a3c0e921","ref":"refs/heads/lineage-20","pushedAt":"2024-01-04T17:43:14.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"fixup! ARM64: configs: Enable CFQ group schedule\n\nChange-Id: Ib0ea0655a9d9af490e6ec898cf2249781c6d53c2\n(cherry picked from commit 425bbbba5c3b30991cfb8a7292ad305c1946a528)","shortMessageHtmlLink":"fixup! ARM64: configs: Enable CFQ group schedule"}},{"before":"dc4f1e378a003c1839941327e7962210211ad2f0","after":"425bbbba5c3b30991cfb8a7292ad305c1946a528","ref":"refs/heads/lineage-21","pushedAt":"2024-01-04T17:42:59.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"fixup! ARM64: configs: Enable CFQ group schedule\n\nChange-Id: Ib0ea0655a9d9af490e6ec898cf2249781c6d53c2","shortMessageHtmlLink":"fixup! ARM64: configs: Enable CFQ group schedule"}},{"before":"e23a0362738712b559fda8d9b02d893f09a020b5","after":"dc4f1e378a003c1839941327e7962210211ad2f0","ref":"refs/heads/lineage-21","pushedAt":"2023-11-27T02:38:07.000Z","pushType":"push","commitsCount":56,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"bpf: avoid false sharing of map refcount with max_entries\n\n[ upstream commit be95a845cc4402272994ce290e3ad928aff06cb9 ]\n\nIn addition to commit b2157399cc98 (\"bpf: prevent out-of-bounds\nspeculation\") also change the layout of struct bpf_map such that\nfalse sharing of fast-path members like max_entries is avoided\nwhen the maps reference counter is altered. Therefore enforce\nthem to be placed into separate cachelines.\n\npahole dump after change:\n\n struct bpf_map {\n const struct bpf_map_ops * ops; /* 0 8 */\n struct bpf_map * inner_map_meta; /* 8 8 */\n void * security; /* 16 8 */\n enum bpf_map_type map_type; /* 24 4 */\n u32 key_size; /* 28 4 */\n u32 value_size; /* 32 4 */\n u32 max_entries; /* 36 4 */\n u32 map_flags; /* 40 4 */\n u32 pages; /* 44 4 */\n u32 id; /* 48 4 */\n int numa_node; /* 52 4 */\n bool unpriv_array; /* 56 1 */\n\n /* XXX 7 bytes hole, try to pack */\n\n /* --- cacheline 1 boundary (64 bytes) --- */\n struct user_struct * user; /* 64 8 */\n atomic_t refcnt; /* 72 4 */\n atomic_t usercnt; /* 76 4 */\n struct work_struct work; /* 80 32 */\n char name[16]; /* 112 16 */\n /* --- cacheline 2 boundary (128 bytes) --- */\n\n /* size: 128, cachelines: 2, members: 17 */\n /* sum members: 121, holes: 1, sum holes: 7 */\n };\n\nNow all entries in the first cacheline are read only throughout\nthe life time of the map, set up once during map creation. Overall\nstruct size and number of cachelines doesn't change from the\nreordering. struct bpf_map is usually first member and embedded\nin map structs in specific map implementations, so also avoid those\nmembers to sit at the end where it could potentially share the\ncacheline with first map values e.g. in the array since remote\nCPUs could trigger map updates just as well for those (easily\ndirtying members like max_entries intentionally as well) while\nhaving subsequent values in cache.\n\nQuoting from Google's Project Zero blog [1]:\n\n Additionally, at least on the Intel machine on which this was\n tested, bouncing modified cache lines between cores is slow,\n apparently because the MESI protocol is used for cache coherence\n [8]. Changing the reference counter of an eBPF array on one\n physical CPU core causes the cache line containing the reference\n counter to be bounced over to that CPU core, making reads of the\n reference counter on all other CPU cores slow until the changed\n reference counter has been written back to memory. Because the\n length and the reference counter of an eBPF array are stored in\n the same cache line, this also means that changing the reference\n counter on one physical CPU core causes reads of the eBPF array's\n length to be slow on other physical CPU cores (intentional false\n sharing).\n\nWhile this doesn't 'control' the out-of-bounds speculation through\nmasking the index as in commit b2157399cc98, triggering a manipulation\nof the map's reference counter is really trivial, so lets not allow\nto easily affect max_entries from it.\n\nSplitting to separate cachelines also generally makes sense from\na performance perspective anyway in that fast-path won't have a\ncache miss if the map gets pinned, reused in other progs, etc out\nof control path, thus also avoids unintentional false sharing.\n\n [1] https://googleprojectzero.blogspot.ch/2018/01/reading-privileged-memory-with-side.html\n\nSigned-off-by: Daniel Borkmann \nSigned-off-by: Alexei Starovoitov \nSigned-off-by: Greg Kroah-Hartman \nChange-Id: Id113157c85bdad735e2b10ceaf40eabb24f10130","shortMessageHtmlLink":"bpf: avoid false sharing of map refcount with max_entries"}},{"before":"c25ae8ba5fb5c29a551ae7bf81dd43e189248aba","after":"dc4f1e378a003c1839941327e7962210211ad2f0","ref":"refs/heads/lineage-20","pushedAt":"2023-11-27T02:38:07.000Z","pushType":"push","commitsCount":62,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"bpf: avoid false sharing of map refcount with max_entries\n\n[ upstream commit be95a845cc4402272994ce290e3ad928aff06cb9 ]\n\nIn addition to commit b2157399cc98 (\"bpf: prevent out-of-bounds\nspeculation\") also change the layout of struct bpf_map such that\nfalse sharing of fast-path members like max_entries is avoided\nwhen the maps reference counter is altered. Therefore enforce\nthem to be placed into separate cachelines.\n\npahole dump after change:\n\n struct bpf_map {\n const struct bpf_map_ops * ops; /* 0 8 */\n struct bpf_map * inner_map_meta; /* 8 8 */\n void * security; /* 16 8 */\n enum bpf_map_type map_type; /* 24 4 */\n u32 key_size; /* 28 4 */\n u32 value_size; /* 32 4 */\n u32 max_entries; /* 36 4 */\n u32 map_flags; /* 40 4 */\n u32 pages; /* 44 4 */\n u32 id; /* 48 4 */\n int numa_node; /* 52 4 */\n bool unpriv_array; /* 56 1 */\n\n /* XXX 7 bytes hole, try to pack */\n\n /* --- cacheline 1 boundary (64 bytes) --- */\n struct user_struct * user; /* 64 8 */\n atomic_t refcnt; /* 72 4 */\n atomic_t usercnt; /* 76 4 */\n struct work_struct work; /* 80 32 */\n char name[16]; /* 112 16 */\n /* --- cacheline 2 boundary (128 bytes) --- */\n\n /* size: 128, cachelines: 2, members: 17 */\n /* sum members: 121, holes: 1, sum holes: 7 */\n };\n\nNow all entries in the first cacheline are read only throughout\nthe life time of the map, set up once during map creation. Overall\nstruct size and number of cachelines doesn't change from the\nreordering. struct bpf_map is usually first member and embedded\nin map structs in specific map implementations, so also avoid those\nmembers to sit at the end where it could potentially share the\ncacheline with first map values e.g. in the array since remote\nCPUs could trigger map updates just as well for those (easily\ndirtying members like max_entries intentionally as well) while\nhaving subsequent values in cache.\n\nQuoting from Google's Project Zero blog [1]:\n\n Additionally, at least on the Intel machine on which this was\n tested, bouncing modified cache lines between cores is slow,\n apparently because the MESI protocol is used for cache coherence\n [8]. Changing the reference counter of an eBPF array on one\n physical CPU core causes the cache line containing the reference\n counter to be bounced over to that CPU core, making reads of the\n reference counter on all other CPU cores slow until the changed\n reference counter has been written back to memory. Because the\n length and the reference counter of an eBPF array are stored in\n the same cache line, this also means that changing the reference\n counter on one physical CPU core causes reads of the eBPF array's\n length to be slow on other physical CPU cores (intentional false\n sharing).\n\nWhile this doesn't 'control' the out-of-bounds speculation through\nmasking the index as in commit b2157399cc98, triggering a manipulation\nof the map's reference counter is really trivial, so lets not allow\nto easily affect max_entries from it.\n\nSplitting to separate cachelines also generally makes sense from\na performance perspective anyway in that fast-path won't have a\ncache miss if the map gets pinned, reused in other progs, etc out\nof control path, thus also avoids unintentional false sharing.\n\n [1] https://googleprojectzero.blogspot.ch/2018/01/reading-privileged-memory-with-side.html\n\nSigned-off-by: Daniel Borkmann \nSigned-off-by: Alexei Starovoitov \nSigned-off-by: Greg Kroah-Hartman \nChange-Id: Id113157c85bdad735e2b10ceaf40eabb24f10130","shortMessageHtmlLink":"bpf: avoid false sharing of map refcount with max_entries"}},{"before":"836ac2a718ae8beafdcfda458b3fbed1d9626fc1","after":"e23a0362738712b559fda8d9b02d893f09a020b5","ref":"refs/heads/lineage-21","pushedAt":"2023-11-19T17:32:53.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"fixup! ARM: dts: msm: Move to second stage init\n\nChange-Id: I559738e075be116ff3d92fcf44a216517fc387b0","shortMessageHtmlLink":"fixup! ARM: dts: msm: Move to second stage init"}},{"before":"c25ae8ba5fb5c29a551ae7bf81dd43e189248aba","after":"836ac2a718ae8beafdcfda458b3fbed1d9626fc1","ref":"refs/heads/lineage-21","pushedAt":"2023-11-09T22:30:07.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"ARM: dts: msm: Move to second stage init\n\nChange-Id: Ia7642d730b0a68e045f19c6a3fd00ce3c8844379","shortMessageHtmlLink":"ARM: dts: msm: Move to second stage init"}},{"before":null,"after":"c25ae8ba5fb5c29a551ae7bf81dd43e189248aba","ref":"refs/heads/lineage-21","pushedAt":"2023-11-09T22:00:34.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"BACKPORT: qcacld-3.0: Ignore CSA request for invalid channel\n\nIn present scenario, STA disconnects with AP if it receives\ninvalid channel in CSA IE. In this case STA shouldn't\ndisconnect with AP as this request may come from a spoof AP.\n\nIgnore this CSA request as it might be from spoof AP and\nif it is from genuine AP heart beat failure happens and\nresults in disconnection. After disconnection DUT may\nreconnect to same or other APs.\n\nChange-Id: I840508dd27d8c313a3e8f74c4e1f5aa64eecf6f9\nCRs-Fixed: 3390251","shortMessageHtmlLink":"BACKPORT: qcacld-3.0: Ignore CSA request for invalid channel"}},{"before":"e231e2beb6852488104a2bb7e9c8b5b7b970ca8a","after":"c25ae8ba5fb5c29a551ae7bf81dd43e189248aba","ref":"refs/heads/lineage-20","pushedAt":"2023-09-22T14:51:11.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"BACKPORT: qcacld-3.0: Ignore CSA request for invalid channel\n\nIn present scenario, STA disconnects with AP if it receives\ninvalid channel in CSA IE. In this case STA shouldn't\ndisconnect with AP as this request may come from a spoof AP.\n\nIgnore this CSA request as it might be from spoof AP and\nif it is from genuine AP heart beat failure happens and\nresults in disconnection. After disconnection DUT may\nreconnect to same or other APs.\n\nChange-Id: I840508dd27d8c313a3e8f74c4e1f5aa64eecf6f9\nCRs-Fixed: 3390251","shortMessageHtmlLink":"BACKPORT: qcacld-3.0: Ignore CSA request for invalid channel"}},{"before":"5af51b1a867c74660c853fee71aad690d43322ea","after":"e231e2beb6852488104a2bb7e9c8b5b7b970ca8a","ref":"refs/heads/lineage-20","pushedAt":"2023-07-27T17:26:19.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"fixup! ANDROID: sched/rt: rt cpu selection integration with EAS.\n\nChange-Id: Icb4282cc7cc3b190b739fc3ef649077208953f8b","shortMessageHtmlLink":"fixup! ANDROID: sched/rt: rt cpu selection integration with EAS."}},{"before":"6326ace68ad2abe052ba9fdcf399bd207c6297a2","after":"5af51b1a867c74660c853fee71aad690d43322ea","ref":"refs/heads/lineage-20","pushedAt":"2023-07-26T19:20:16.000Z","pushType":"push","commitsCount":32,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"BACKPORT: cpufreq: schedutil: Avoid using invalid next_freq\n\nIf the next_freq field of struct sugov_policy is set to UINT_MAX,\nit shouldn't be used for updating the CPU frequency (this is a\nspecial \"invalid\" value), but after commit b7eaf1aab9f8 (cpufreq:\nschedutil: Avoid reducing frequency of busy CPUs prematurely) it\nmay be passed as the new frequency to sugov_update_commit() in\nsugov_update_single().\n\nFix that by adding an extra check for the special UINT_MAX value\nof next_freq to sugov_update_single().\n\nFixes: b7eaf1aab9f8 (cpufreq: schedutil: Avoid reducing frequency of busy CPUs prematurely)\nReported-by: Viresh Kumar \nCc: 4.12+ # 4.12+\nChange-Id: Idf4ebe9e912f983598255167d2065e47562ab83d\nSigned-off-by: Rafael J. Wysocki \nAcked-by: Viresh Kumar \nSigned-off-by: Rafael J. Wysocki \n(cherry picked from commit 97739501f207efe33145b918817f305b822987f8)\nSigned-off-by: Nathan Chancellor ","shortMessageHtmlLink":"BACKPORT: cpufreq: schedutil: Avoid using invalid next_freq"}},{"before":"7334370788561873bfd032d2047b15ea377128d3","after":"6326ace68ad2abe052ba9fdcf399bd207c6297a2","ref":"refs/heads/lineage-20","pushedAt":"2023-07-19T21:10:59.000Z","pushType":"push","commitsCount":51,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"sched: Take irq_sparse lock during the isolation\n\nirq_migrate_all_off_this_cpu() is used to migrate IRQs and this\nfunction checks for all active irq in the allocated_irqs mask.\nirq_migrate_all_off_this_cpu() expects the caller to take irq_sparse\nlock to avoid race conditions while accessing allocated_irqs\nmask variable. Prevent a race between irq alloc/free and irq\nmigration by adding irq_sparse lock across CPU isolation.\n\nChange-Id: I9edece1ecea45297c8f6529952d88b3133046467\nSigned-off-by: Prasad Sodagudi ","shortMessageHtmlLink":"sched: Take irq_sparse lock during the isolation"}},{"before":"6202ebd8d028ab14daa096363dad8244cf430079","after":"7334370788561873bfd032d2047b15ea377128d3","ref":"refs/heads/lineage-20","pushedAt":"2023-06-20T21:31:32.626Z","pushType":"push","commitsCount":1,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"power: smb-lib: Fix mutex acquisition deadlock on PD hard reset\n\nMutex acquisition deadlock can happen while cancelling cc_dettach\nwork during pd_hard_reset from the function usbin_plugin_hard_reset\n_locked on vbus rise which is called in the same lock context that\nwe try to acquire in the cc_dettach work routine.\nCheck if cc_dettach work is running during pd_hard_reset and use\ntrylock instead of mutex_lock to prevent any deadlock if mutext is\nalready held.\n\nChange-Id: I5530deb9e654d3d12ba1b4bc6876f36127a0d5a5\nSigned-off-by: Umang Agrawal ","shortMessageHtmlLink":"power: smb-lib: Fix mutex acquisition deadlock on PD hard reset"}},{"before":"8462d3406280fb70330941b9a236a62a6e496273","after":"6202ebd8d028ab14daa096363dad8244cf430079","ref":"refs/heads/lineage-20","pushedAt":"2023-06-09T18:30:06.906Z","pushType":"push","commitsCount":1,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"ASoC: msm-pcm-q6-v2: Add dsp buf check\n\nCurrent logic copies user buf size of data\nfrom the avail dsp buf at a given offset.\nIf this offset returned from DSP in READ_DONE event\ngoes out of bounds or is corrupted, then it can lead to\nout of bounds DSP buffer access, resulting in memory fault.\nFix is to add check for this buf offset, if it is within\nthe buf size range.\n\nChange-Id: I7753cc6db394704dbb959477150141d42b836bef\nSigned-off-by: Soumya Managoli \nCVE-2023-21657\nSigned-off-by: Kevin F. Haggerty ","shortMessageHtmlLink":"ASoC: msm-pcm-q6-v2: Add dsp buf check"}},{"before":"3aba1cd4de1faa6c74c5d5623b6d0eddfc57d344","after":"8462d3406280fb70330941b9a236a62a6e496273","ref":"refs/heads/lineage-20","pushedAt":"2023-06-09T18:29:30.306Z","pushType":"push","commitsCount":1,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"qcacld-3.0: Fix OOB in wma_scan_roam.c\n\nCurrently in wma_extscan_hotlist_match_event_handler\nAPI, dest_hotlist get memory allocation based on numap\nwhich takes value from event->total_entries.\nBut numap is limited to WMA_EXTSCAN_MAX_HOTLIST_ENTRIES\nand event->total_entries more than WMA_EXTSCAN_MAX_HOTLIST_ENTRIES\ncan cause out of bound issue.\n\nFix is to populate dest_hotlist->numOfAps from numap\ninstead of event->total_entries to avoid any out of bound issue.\n\nChange-Id: I756f7e4a4dcd454508bba83d4a8bbbb139530905\nCRs-Fixed: 3346781\nCVE-2023-21656\nSigned-off-by: Kevin F. Haggerty ","shortMessageHtmlLink":"qcacld-3.0: Fix OOB in wma_scan_roam.c"}},{"before":"44e5aecd52da36ffb3693e05a9981cca0d288e04","after":"3aba1cd4de1faa6c74c5d5623b6d0eddfc57d344","ref":"refs/heads/lineage-20","pushedAt":"2023-06-09T18:19:41.278Z","pushType":"push","commitsCount":1,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"power: qpnp-smb2: Implement battery charging_enabled node\n\nChange-Id: Id08c169f0c507390eab070d1ae77bfb992b50b81","shortMessageHtmlLink":"power: qpnp-smb2: Implement battery charging_enabled node"}},{"before":"b9d0174fb3f163a8f0de539eb21b8eab68e1d7e7","after":"44e5aecd52da36ffb3693e05a9981cca0d288e04","ref":"refs/heads/lineage-20","pushedAt":"2023-05-17T02:16:58.955Z","pushType":"push","commitsCount":3,"pusher":{"login":"lineageos-gerrit","name":null,"path":"/lineageos-gerrit","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/24783018?s=80&v=4"},"commit":{"message":"Revert \"kernel: Only expose su when daemon is running\"\n\nThis patch is no longer necessary because we no longer ship\nsu add-ons, which is this patch initially designed for. Now\nit causes another issue which breaks custom root solution\nsuch as Magisk, as Magisk switches worker tmpfs dir to RO\ninstead of RW for safety reasons and happens to satisfy\nMS_RDONLY check for su file, resulting in su file totally\ninaccessible.\n\nThis reverts commit 51954dff09eaa554464770e2f865d713766d8297.\n\nChange-Id: If25a9ef7e64c79412948f4619e08faaedb18aa13","shortMessageHtmlLink":"Revert \"kernel: Only expose su when daemon is running\""}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEHQaTSwA","startCursor":null,"endCursor":null}},"title":"Activity ยท LineageOS/android_kernel_nokia_sdm660"}