Select Git revision
Search by author
- Any Author
- authors
-
72162444 72162444 gaochangning
-
Aakash Dave aakash.dave
-
Aaron Kim akim
-
Aaron Kloc akloc
-
Aaron Lan aaron.lan
-
Aaron Nabil aaronna
-
Aaron Pohle aaron.pohle
-
Abbott Chung chung.abbott
-
Abdallah Omar abdallah_omar
-
Abdessamii Chalbi abdessamii.chalbi
-
Abdul Hussain Sirajudeen abdul.hussain
-
Abdullah Alghamdi a.alghamdi
-
Abdullah Elmarghany abdullah_elmarghany
-
Abel Fang abel_fang
-
Abel Vesa
abel.vesa
-
Abhijeet Badurkar abhijeet.badurkar
-
Abhijit Adsule adsule
-
Abhijit Murthy abhijit
-
Abhi Khanal akhanal
-
Abhilash Sahoo abhilashsahoo
- Jun 20, 2022
-
-
Zhipeng Wang authored
Conflicts: include/linux/mm_types.h Change-Id: If943423c84689f43086b4babb6bc2505079eb160
-
- Jun 19, 2022
-
-
Steve Muckle authored
This locks down OWNERS approval to a small group to guard against unintentional breakages. Bug: 235646184 Signed-off-by:Steve Muckle <smuckle@google.com> Change-Id: I58ca467b1e7786e1ad0f6ad67c7a7a5845a91ec6
-
- Jun 18, 2022
-
-
Todd Kjos authored
Set KMI_GENERATION=8 for 6/17 KMI update Leaf changes summary: 4890 artifacts changed (1 filtered out) Changed leaf types summary: 394 (1 filtered out) leaf types changed Removed/Changed/Added functions summary: 0 Removed, 4417 Changed, 4 Added functions Removed/Changed/Added variables summary: 0 Removed, 74 Changed, 1 Added variable 4 Added functions: [A] 'function int rpmsg_chrdev_eptdev_create(rpmsg_device*, device*, rpmsg_channel_info)' [A] 'function int rpmsg_chrdev_eptdev_destroy(device*, void*)' [A] 'function void rproc_del_carveout(rproc*, rproc_mem_entry*)' [A] 'function void rproc_mem_entry_free(rproc_mem_entry*)' 4417 functions with some sub-type change: [C] 'function int __traceiter_android_rvh_gic_v3_set_affinity(void*, irq_data*, const cpumask*, u64*, bool, void*)' at gic_v3.h:19:1 has some sub-type changes: CRC (modversions) changed from 0x2ddc6a81 to 0xc0b21d95 parameter 7 of type 'void*' was added parameter 8 of type 'typedef u64' was added [C] 'function block_device* I_BDEV(inode*)' at bdev.c:42:1 has some sub-type changes: CRC (modversions) changed from 0x9f8a3196 to 0xb8163ad5 [C] 'function void* PDE_DATA(const inode*)' at generic.c:794:1 has some sub-type changes: CRC (modversions) changed from 0xec8a2781 to 0x5927f85f [C] 'function void __ClearPageMovable(page*)' at compaction.c:138:1 has some sub-type changes: CRC (modversions) changed from 0x84c84632 to 0xf30e6b61 ... 4413 omitted; 4416 symbols have only CRC changes 1 Added variable: [A] 'class* rpmsg_class' 74 Changed variables: ... Bug: 235646184 Signed-off-by:Todd Kjos <tkjos@google.com> Signed-off-by:
-
Chao Yu authored
Add PG_oem_reserved in enum pageflags to indicate more status of page for OEM, this flag will be visible only in 64bit platform. Bug: 235673196 Change-Id: I6a8324a5110d13cdb993c1d366824c057cd133dd Signed-off-by:Chao Yu <chao@kernel.org>
-
heshuai1 authored
add ANDROID_OEM_DATA_ARRAY for implement of oem gki. Bug: 235925535 Signed-off-by:heshuai1 <heshuai1@xiaomi.com> Change-Id: Ie2bfc7251266e22a5ee69b226dfd85d6e9cac2f5
-
Tejun Heo authored
Each cset (css_set) is pinned by its tasks. When we're moving tasks around across csets for a migration, we need to hold the source and destination csets to ensure that they don't go away while we're moving tasks about. This is done by linking cset->mg_preload_node on either the mgctx->preloaded_src_csets or mgctx->preloaded_dst_csets list. Using the same cset->mg_preload_node for both the src and dst lists was deemed okay as a cset can't be both the source and destination at the same time. Unfortunately, this overloading becomes problematic when multiple tasks are involved in a migration and some of them are identity noop migrations while others are actually moving across cgroups. For example, this can happen with the following sequence on cgroup1: #1> mkdir -p /sys/fs/cgroup/misc/a/b #2> echo $$ > /sys/fs/cgroup/misc/a/cgroup.procs #3> RUN_A_COMMAND_WHICH_CREATES_MULTIPLE_THREADS & #4> PID=$! #5> echo $PID > /sys/fs/cgroup/misc/a/b/tasks #6> echo $PID > /sys/fs/cgroup/misc/a/cgroup.procs the process including the group leader back into a. In this final migration, non-leader threads would be doing identity migration while the group leader is doing an actual one. After #3, let's say the whole process was in cset A, and that after #4, the leader moves to cset B. Then, during #6, the following happens: 1. cgroup_migrate_add_src() is called on B for the leader. 2. cgroup_migrate_add_src() is called on A for the other threads. 3. cgroup_migrate_prepare_dst() is called. It scans the src list. 4. It notices that B wants to migrate to A, so it tries to A to the dst list but realizes that its ->mg_preload_node is already busy. 5. and then it notices A wants to migrate to A as it's an identity migration, it culls it by list_del_init()'ing its ->mg_preload_node and putting references accordingly. 6. The rest of migration takes place with B on the src list but nothing on the dst list. This means that A isn't held while migration is in progress. If all tasks leave A before the migration finishes and the incoming task pins it, the cset will be destroyed leading to use-after-free. This is caused by overloading cset->mg_preload_node for both src and dst preload lists. We wanted to exclude the cset from the src list but ended up inadvertently excluding it from the dst list too. This patch fixes the issue by separating out cset->mg_preload_node into ->mg_src_preload_node and ->mg_dst_preload_node, so that the src and dst preloadings don't interfere with each other. Signed-off-by:Tejun Heo <tj@kernel.org> Reported-by:
Mukesh Ojha <quic_mojha@quicinc.com> Reported-by:
shisiyuan <shisiyuan19870131@gmail.com> Link: http://lkml.kernel.org/r/1654187688-27411-1-git-send-email-shisiyuan@xiaomi.com Link: https://www.spinics.net/lists/cgroups/msg33313.html Fixes: f817de98 ("cgroup: prepare migration path for unified hierarchy") Cc: stable@vger.kernel.org # v3.16+ (cherry picked from commit 07fd5b6c https://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.19-fixes) Bug: 235577024 Change-Id: Ieaf1c0c8fc23753570897fd6e48a54335ab939ce Signed-off-by:
-
Liujie Xie authored
Forgot export hooks for driver, fix it. Fixes: 1cdcf76b ("ANDROID: vendor_hooks: add hooks in mem_cgroup subsystem") Bug: 192052083 Signed-off-by:
Liujie Xie <xieliujie@oppo.com> Change-Id: I79779406b4dab52ceca02bd5de909d3a0c127cb9 (cherry picked from commit 69c93158)
-
Liujie Xie authored
Add a pglist_data field to record additional node parameters. Bug: 192052083 Signed-off-by:
-
Liujie Xie authored
Export try_to_free_mem_cgroup_pages function to allow vendor modules to reclaim a memory cgroup. Bug: 192052083 Signed-off-by:
-
Liujie Xie authored
Export cgroup_add_legacy_cftypes and a helper function to allow vendor module to expose additional files in the memory cgroup hierarchy. Bug: 192052083 Signed-off-by:
-
Liujie Xie authored
Add hooks to tune memory policy based on mem_cgroup. Bug: 192052083 Signed-off-by:
-
Raghu Bankapur authored
Allow DAI's to be hostless so that no PCM data is sent between DAI and CPU. This allows for power savings as there is no DMA or CPU interaction required vendor hooks will be developed using this fields to enable hostless Bug: 234791256 Signed-off-by:Raghu Bankapur <quic_rbankapu@quicinc.com> Change-Id: Ib926c4e76e9f76d54f3c1402dba676adc49bcf7c
-
Weichao Guo authored
Add ANDROID_OEM_DATA_ARRAY() in struct ufs_hba to support customized features. Bug: 235673196 Signed-off-by:Weichao Guo <guoweichao@oppo.corp-partner.google.com> Change-Id: I30d479d090256447b8e93157e30fc9db92563e46
-
Neeraj Upadhyay authored
Update android_rvh_gic_v3_set_affinity vendor hook to pass redistributor information. This allows configuring affinity controls in the GIC redistributor space. Bug: 180471389 Change-Id: I7325fea4338b39b65027e310a0461b7e7d32e6aa Signed-off-by:
Neeraj Upadhyay <quic_neeraju@quicinc.com> Signed-off-by:
Yogesh Lal <quic_ylal@quicinc.com>
-
Chao Yu authored
Add ANDROID_OEM_DATA(1) in struct bio for more fields recording. Bug: 235673196 Change-Id: Ib56e9e5690d85f20088bf289642544ef9feddc58 Signed-off-by: -
Veerendranath Jakkam authored
The MLO links used for connection with an MLD AP are decided by the driver in case of SME offloaded to driver. Add support for the drivers to indicate the information of links used for MLO connection in connect and roam callbacks, update the connected links information in wdev from connect/roam result sent by driver. Also, send the connected links information to userspace. Add a netlink flag attribute to indicate that userspace supports handling of MLO connection. Drivers must not do MLO connection when this flag is not set. This is to maintain backwards compatibility with older supplicant versions which doesn't have support for MLO connection. Signed-off-by:
Veerendranath Jakkam <quic_vjakkam@quicinc.com> Bug: 233387627 Change-Id: I4aabf721c0976b3410d81fa56fc72408271f9806 Link: https://lore.kernel.org/linux-wireless/1654679797-7740-1-git-send-email-quic_vjakkam@quicinc.com/ Signed-off-by:
-
Johannes Berg authored
Add some optional callbacks for link add/remove so that drivers can react here. Initially, I thought it would be sufficient to just create the link in start_ap etc., but it turns out that's not so simple, since there are quite a few callbacks that can be called: if they're erroneously without start_ap, things might crash. Thus it might be easier for drivers to allocate all the necessary data structures immediately, to not have to worry about it in each callback, since cfg80211 checks that the link ID is valid (has been added.) Signed-off-by:
Johannes Berg <johannes.berg@intel.com> Bug: 233387627 Change-Id: I2974b3b548b27594f269c5474c58b5070ecb0292 (cherry picked from commit c77dc862aaf1b5019fc7f31a9feb49a72de000d9 https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git mld) Signed-off-by:
-
Johannes Berg authored
We wanted to have this sorted by direction (to/from driver), but didn't maintain that well. Sort the file now. Signed-off-by:
-
Johannes Berg authored
For now, we only expect to add links on AP interfaces, we should not be able to remove links on client interfaces even if they have valid links due to making a connection. Also add a note that we should clean up a link when we remove it, we'll need to address that later. Signed-off-by:
-
Johannes Berg authored
For authentication, we need the BSS, the link_id and the AP MLD address to create the link and station, (for now) the driver assigns a link address and sends the frame, the MLD address needs to be the address of the interface. For association, pass the list of BSSes that were selected for the MLO connection, along with extra per-STA profile elements, the AP MLD address and the link ID on which the association request should be sent. Note that for now we don't have a proper way to pass the link address(es) and so the driver/mac80211 will select one, but depending on how that selection works it means that assoc w/o auth data still being around (mac80211 implementation detail) the association won't necessarily work - so this will need to be extended in the future to sort out the link addressing. Signed-off-by:
-
Johannes Berg authored
This function has far too many parameters now, move out the BSS lookup and pass the request struct instead. type=cleanup ticket=none Signed-off-by:
-
Johannes Berg authored
Add the definitions necessary to build and parse some of the multi-link element, the per-STA profile isn't fully included. Signed-off-by:
-
Johannes Berg authored
For MLO we'll need to do this multiple times, so refactor this. For now keep the disconnect_bssid, but we'll need to figure out how to handle that with MLD. Signed-off-by:
-
Johannes Berg authored
Today it makes more sense to pass the necessary parameters to look up the BSS entry to cfg80211_mlme_assoc(), but with MLO we will need to look up multiple, and that gets awkward. Pull the lookup code into the callers so we can change it better. Signed-off-by:
-
Johannes Berg authored
In order to support multi-link operation with multiple links, start adding some APIs. The notable addition here is to have the link ID in a new nl80211 attribute, that will be used to differentiate the links in many nl80211 operations. So far, this patch adds the netlink NL80211_ATTR_MLO_LINK_ID attribute (as well as the NL80211_ATTR_MLO_LINKS attribute) and plugs it through the system in some places, checking the validity etc. along with other infrastructure needed for it. For now, I've decided to include only the over-the-air link ID in the API. I know we discussed that we eventually need to have to have other ways of identifying a link, but for local AP mode and auth/assoc commands as well as set_key etc. we'll use the OTA ID. Also included in this patch is some refactoring of the data structures in struct wireless_dev, splitting for the first time the data into type dependent pieces, to make reasoning about these things easier. Signed-off-by:
-
Veerendranath Jakkam authored
Increase akm_suites array size in struct cfg80211_crypto_settings to 10 and advertise the capability to userspace. This allows userspace to send more than two AKMs to driver in netlink commands such as NL80211_CMD_CONNECT. This capability is needed for implementing WPA3-Personal transition mode correctly with any driver that handles roaming internally. Currently, the possible AKMs for multi-AKM connect can include PSK, PSK-SHA-256, SAE, FT-PSK and FT-SAE. Since the count is already 5, increasing the akm_suites array size to 10 should be reasonable for future usecases. Contains a fix for the issue: Reported-by:
kernel test robot <lkp@intel.com> Signed-off-by:
-
Veerendranath Jakkam authored
Reserve sufficient nl80211 attributes in enum nl80211_commands and enum nl80211_attr to backport upstream UAPI changes. Reserve data fields for upstream backport changes and vendor hooks. Also, add vendor hooks to set/get additional info from driver based on the cfg80211 current context. These APIs can be used to configure/fetch data of the new params added in upstream cfg80211_op calls. Ex: upstream kernel added a new param to existing cfg80211_op "add_key()". The addtional param info added in the upstream kernel can be configured using "android_vh_cfg80211_set_context" before calling "add_key". Bug: 233387627 Change-Id: I99f696ad291ae5965fc6d91bf565cc0c9d423dd5 Signed-off-by: -
Veerendranath Jakkam authored
Adds various macros to create reserved data fields in kernel data structures before the freeze and to use reserved data fields to backport upstream changes after the freeze. Bug: 233387627 Change-Id: Ifbf8444861fa805593ce9b4837cd2653b7b7a0b0 Signed-off-by: -
Johannes Berg authored
This is completely racy, remove it. Signed-off-by:
Kalle Valo <quic_kvalo@quicinc.com> Link: https://lore.kernel.org/r/20220506095451.9852305a92c8.I05155824a1b9059eb59beccde81786dc69de354a@changeid Bug: 233387627 Change-Id: Ibf164291a9c560bf58d8ae6f705803af8181e36d (cherry picked from commit 4255a07a98cb0054947fbe5cb3d6f0b5eb87522b) Signed-off-by:
-
Chao Yu authored
Add ANDROID_OEM_DATA(1) in struct queue_limits to support more limits recording. Bug: 235673196 Signed-off-by: -
Raghu Bankapur authored
lookups The control elements are managed in a single linked list and we traverse the whole list for matching each numid or ctl id per every inquiry of a control element. This is OK-ish for a small number of elements but obviously it doesn't scale. Especially the matching with the ctl id takes time because it checks each field of the snd_ctl_id element, e.g. the name string is matched with strcmp(). This patch adds the hash tables with Xarray for improving the lookup speed of a control element. There are two xarray tables added to the card; one for numid and another for ctl id. For the numid, we use the numid as the index, while for the ctl id, we calculate a hash key. The lookup is done via a single xa_load() execution. As long as the given control element is found on the Xarray table, that's fine, we can give back a quick lookup result. The problem is when no entry hits on the table, and for this case, we have a slight optimization. Namely, the driver checks whether we had a collision on Xarray table, and do a fallback search (linear lookup of the full entries) only if a hash key collision happened beforehand. So, in theory, the inquiry for a non-existing element might take still time even with this patch in a worst case, but this must be pretty rare. The feature is enabled via CONFIG_SND_CTL_FAST_LOOKUP, which is turned on as default. For simplicity, the option can be turned off only when CONFIG_EXPERT is set ("You are expert? Then you manage 1000 knobs"). Link: https://lore.kernel.org/r/20220609180504.775-1-tiwai@suse.de Signed-off-by:Takashi Iwai <tiwai@suse.de> Bug: 234796421 Signed-off-by:
-
Liujie Xie authored
Add a field in mem_cgroup to record additional per-cgroup information for memory policy tuning. Bug: 192052083 Signed-off-by: -
William McVicker authored
As of 07940c36 ("PCI: dwc: Fix MSI page leakage in suspend/resume"), the PCIe designware host driver has been using the driver data allocation for the msi_msg DMA mapping which can result in a DMA_MAPPING_ERROR due to the DMA overflow check in dma_direct_map_page() when the address is greater than 32 bits (reported in [1]). The commit was trying to address a memory leak on suspend/resume by moving the MSI mapping to dw_pcie_host_init(), but subsequently dropped the page allocation thinking it wasn't needed. To fix the DMA mapping issue as well as make msi_msg DMA'able, switch back to allocating a 32-bit page for the msi_msg. To avoid the suspend/resume leak, allocate the page in dw_pcie_host_init() since that shouldn't be called during suspend/resume. [1] https://lore.kernel.org/all/Yo0soniFborDl7+C@google.com/ Link: https://lore.kernel.org/all/20220525223316.388490-1-willmcvicker@google.com/ (cherry picked from commit 27235cd867cf7cd17e8d2384430dc54703419ffc https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci/ctrl/dwc) Bug: 232293973 Signed-off-by:
Will McVicker <willmcvicker@google.com> Signed-off-by:
Bjorn Helgaas <bhelgaas@google.com> Reviewed-by:
Rob Herring <robh@kernel.org> Change-Id: I48f48d069ff27a391cf0043bc23cfe4ac8c32593
-
William McVicker authored
This reverts commit e43c6c73. This was a workaround. Now that the fix has been merged upstream, we can apply that instead. Bug: 232293973 Signed-off-by:
-
Giuliano Procida authored
This change is intended to reduce the chance of a missed ABI break involving vendor hooks. The following types are now fully defined in ABI XML. * `struct binder_transaction` * `struct binder_thread` * `struct binder_proc` * `struct printk_ringbuffer` * `struct printk_record` symbol '__alloc_pages' changed CRC changed from 0x6497cbd to 0x230fd8e5 symbol '__find_vma' changed CRC changed from 0xf11b619f to 0xb0069a61 symbol '__free_pages' changed CRC changed from 0xba5eeb68 to 0xdc394265 ... 195 omitted; 198 symbols have only CRC changes Bug: 233047575 Change-Id: I807227f6161f0a44ec3657dc8cdb8a3fdffc40b3 Signed-off-by:Giuliano Procida <gprocida@google.com>
-
Giuliano Procida authored
This change is intended to reduce the chance of a missed ABI break involving vendor hooks. The following type is now fully defined in ABI XML. * `struct timekeeper` symbol '__traceiter_android_rvh_account_irq' changed CRC changed from 0x18e0dccf to 0x4e82c102 symbol '__traceiter_android_rvh_after_dequeue_task' changed CRC changed from 0x7efc419b to 0x1c0066e1 symbol '__traceiter_android_rvh_after_enqueue_task' changed CRC changed from 0xd6f0f603 to 0xf7eaafb8 ... 75 omitted; 78 symbols have only CRC changes Bug: 233047575 Change-Id: I8c04eede1b9d9e788abce95cb31dbd19916774ef Signed-off-by: -
Chao Yu authored
Add ANDROID_OEM_DATA(1) in struct request_queue to support more request queue's status. Bug: 235673196 Change-Id: Ib55941790f8c9627e47abae044eb7d7ebe658f21 Signed-off-by: -
rongqianfeng authored
Some shrinker add lock in count_objects() may cause lock contention issues and lead all task stall on slab shrink. Add vendor hook in do_shrink_slab() for shrinker->count_objects() latency measuring. Add 3 oem data in shrink_control struct. Two is for shrinker->count_objects() and shrinker->scan_objects() latency measuring, other one to store priority, some shrinker know the reclaimer priority can control the memory reclaim more better. Bug: 188684131 Change-Id: I80e9d90179bb52a99c54d9a067c6fcee835bb2ad Signed-off-by:rongqianfeng <rongqianfeng@vivo.com>
-
Stanley Chu authored
Export below regulator functions to allow vendors to customize regulator configuration in their own platforms. int ufshcd_populate_vreg(struct device *dev, const char *name, struct ufs_vreg **out_vreg); int ufshcd_get_vreg(struct device *dev, struct ufs_vreg *vreg); Bug: 235550312 Link: https://lore.kernel.org/linux-scsi/20220614141655.14409-10-stanley.chu@mediatek.com/ Change-Id: I9990d2e5eb580f160b0c8b4a95b687d754d0767b Signed-off-by:
Stanley Chu <stanley.chu@mediatek.com>
-
Greg Kroah-Hartman authored
Try to mitigate potential future driver core api changes by adding a padding to struct timer_list. Based on a change made to the RHEL/CENTOS 8 kernel. Bug: 151154716 Signed-off-by:Greg Kroah-Hartman <gregkh@google.com> Change-Id: I74673e2271cd757c4871c9bcb69fd73bb22a722b
-
