Tiffany Yang
a112c9c24c
ANDROID: fsnotify: Do not notify lower fs of open when ENOSYS
...
Even though FUSE supports d_canonical_path, the underlying server may
not implement the operation. In that case, follow the same logic for
filesystems that do not have the canonical path operation instead of
returning early from fsnotify_file with an error.
Bug: 326995824
Test: cts-tradefed run commandAndExit cts -m CtsOsTestCases -t android.os.cts.FileObserverTest
Change-Id: Iae618d4159222b06467b9a0bbb67fb67885aa65e
Signed-off-by: Tiffany Yang <ynaffit@google.com >
(cherry picked from commit 61d32e739d27dd35353a22804023f099b383df3b)
2024-07-31 19:00:38 +00:00
Charan Teja Kalla
7d0a1d6b86
ANDROID: mm: madvise: Avoid counting swap entry references for migration entries
...
Race between the madvise(PAGEOUT) and migration caused by page offline
can make the swp_swapcount()->_swap_info_get emitting the "Bad swap file
entry " message because it is trying to get the info on the migration
entry. Add check if it is a migration entry.
Bug: 356032508
Fixes: aee36dd530quic_charante@quicinc.com >
Signed-off-by: Nikhil V <quic_nprakash@quicinc.com >
2024-07-30 12:04:24 +05:30
Manish Pandey
7fa70ede91
UPSTREAM: scsi: ufs: core: Changing the status to check inflight
...
ufshcd_cmd_inflight() is used to check whether or not a command is in
progress. Make it skip commands that have already completed by changing the !blk_mq_request_started(rq) check into blk_mq_rq_state(rq) !=
MQ_RQ_IN_FLIGHT. We cannot rely on lrbp->cmd since lrbp->cmd is not
cleared when a command completes.
Link: https://lore.kernel.org/linux-scsi/20230517223157.1068210-3-bvanassche@acm.org/
Signed-off-by: SEO HOYOUNG <hy50.seo@samsung.com >
Link: https://lore.kernel.org/r/20240411071444.51873-1-hy50.seo@samsung.com
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com >
Bug: 353887042
(cherry picked from commit 13c28be58c2bdb12e554e01b0e35621060068b11)
Change-Id: I038c3956c55967f38a339a13c16fe7518ee4eb17
Signed-off-by: Manish Pandey <quic_mapa@quicinc.com >
2024-07-26 18:44:19 +00:00
karam.lee
6201b295b8
ANDROID: Update the ABI symbol list
...
Adding the following symbols:
- __traceiter_android_vh_hibernate_state
- __tracepoint_android_vh_hibernate_state
Bug: 342523877
Change-Id: I249ec4ce3b2db80470b2d4d862acf4a882ece199
Signed-off-by: karam.lee <karam.lee@lge.com >
2024-07-26 17:53:16 +00:00
karam.lee
f571d0bdaa
ANDROID: power: add vendor hook to handle hibernate failures
...
The driver or external module may need handling due to hibernate failure.
This error cannot be detected outside of the hibernate() function.
so Add a vendor hook to receive and handle errors in hibernate().
Bug: 342523877
Change-Id: I221e26f571d94e5d5c5aae19937945bb8981f85b
Signed-off-by: karam.lee <karam.lee@lge.com >
2024-07-26 17:53:16 +00:00
Greg Kroah-Hartman
d7387786c2
ANDROID: GKI: remove export of tracing control functions
...
Android GKI kernel modules should NOT have the ability to control the
system-wide tracing functionality, nor query to determine if it is on or
not. So remove the exports of these functions.
Upstream does not wish to do this, so an Android-only change is
required. See the bug id for details.
Bug: 355584612
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com >
Change-Id: I50f69cd9930ddc6b876c5c1dd86f51cfb2ee1bac
2024-07-26 08:34:53 +00:00
Todd Kjos
47af2fba7c
ANDROID: fix kernelci build-break for !CONFIG_ANDROID_VENDOR_OEM_DATA
...
A recent change to add hooks for firmware-based hibernation
added a reference to android_vendor_data1 which breaks
builds that don't enable vendor data.
Fixes: d2cb755a4398 ("ANDROID: vendor hooks: Add hooks to support bootloader based hibernation")
Signed-off-by: Todd Kjos <tkjos@google.com >
Change-Id: I449e968f8d0926c8573150553eed0905faeac3f3
2024-07-25 20:28:25 +00:00
Marcus Ma
918790efaa
ANDROID: GKI: update symbol list file for xiaomi
...
6 function symbol(s) added
'void __traceiter_android_vh_handle_trylock_failed_folio(struct list_head *)'
'void __traceiter_android_vh_folio_trylock_set(struct folio *)'
'void __traceiter_android_vh_folio_trylock_clear(struct folio *)'
'void __traceiter_android_vh_get_folio_trylock_result(struct folio *, bool *)'
'void __traceiter_android_vh_do_folio_trylock(struct folio *, struct rw_semaphore *, bool *, bool *)'
'long reclaim_pages(struct list_head *folio_list)'
5 variable symbol(s) added
'struct tracepoint __tracepoint_android_vh_handle_trylock_failed_folio'
'struct tracepoint __tracepoint_android_vh_folio_trylock_set'
'struct tracepoint __tracepoint_android_vh_folio_trylock_clear'
'struct tracepoint __tracepoint_android_vh_get_folio_trylock_result'
'struct tracepoint __tracepoint_android_vh_do_folio_trylock'
Bug: 353608806
Change-Id: Ibdf1757c41483961074a87f37c60de7db60d8636
Signed-off-by: Marcus Ma <maminghui5@xiaomi.corp-partner.google.com >
2024-07-25 15:45:24 +08:00
Marcus Ma
d01f9af472
ANDROID: vendor_hooks: vendor hooks for optimizing the blocking problem
...
caused by rwsem lock contention of reverse mapping during memory
recycling.
Dear Sir， We want to apply the following five trace hook:
1、trace_android_vh_do_folio_trylock()
2、trace_android_vh_get_folio_trylock_result()
3、trace_android_vh_folio_trylock_clear()
4、trace_android_vh_folio_trylock_set()
5、trace_android_vh_handle_trylock_failed_folio().
The optimization objectives are as follows: In the process of memory
recycling,reverse mapping is indispensable. The role of reverse mapping
is to find all vma or page tables mapped to this page through physical
address or page structure. Therefore,the process of reverse mapping will
inevitably bring synchronous operations. Whether it is file page or an
anonymous page,the synchronization operation is realized through the
rwsem read-write lock. Therefore,when kswapd or the user's key thread
enters direct_reclaim,the rwsem lock will cause the entire recycling
link to be blocked,resulting in low memory recycling efficiency and
affecting the user experience. On Xiaomi mobile phones,there is a
situation in which the reverse mapping is stuck in the rwsem read-write
lock during the file page recycling process,causing the entire recycling link to be blocked,so that the memory cannot be recycled in time. The display on the trace shows that there are a large number of D states,and its block function is rmap_walk_file,therefore,for non-forced
recycling scenarios,try_lock and asynchronous recycling are used to
handle related blocked pages.
Bug: 353608806
Change-Id: I3973c9ddc4e25f8b20e763a4a8aa2dd327e3139d
Signed-off-by: Marcus Ma <maminghui5@xiaomi.corp-partner.google.com >
2024-07-25 15:12:23 +08:00
Geert Uytterhoeven
dd8ee5c242
UPSTREAM: of: reserved_mem: Use proper binary prefix
...
The printed reserved memory information uses the non-standard "K"
prefix, while all other printed values use proper binary prefixes.
Fix this by using "Ki" instead.
While at it, drop the superfluous spaces inside the parentheses, to
reduce printed line length.
Bug: 353554778
Fixes: aeb9267eb6geert+renesas@glider.be >
Link: https://lore.kernel.org/r/20230216083725.1244817-1-geert+renesas@glider.be
Signed-off-by: Rob Herring <robh@kernel.org >
(cherry picked from commit 6ee7afbabcdanesh.petigara@broadcom.com >
Signed-off-by: Pierre Couillaud <pierre@broadcom.com >
2024-07-24 19:19:20 +00:00
Doug Berger
8ea8aeba31
BACKPORT: gpio: of: support gpio-ranges for multiple gpiochip devices
...
Some drivers (e.g. gpio-mt7621 and gpio-brcmstb) have multiple
gpiochip banks within a single device. Unfortunately, the
gpio-ranges property of the device node was being applied to
every gpiochip of the device with device relative GPIO offset
values rather than gpiochip relative GPIO offset values.
This commit makes use of the gpio_chip offset value which can be
non-zero for such devices to split the device node gpio-ranges
property into GPIO offset ranges that can be applied to each
of the relevant gpiochips of the device.
Bug: 353554778
Change-Id: I868f0cd8e4dc8003547a34f3cfd57eece731622f
Signed-off-by: Doug Berger <opendmb@gmail.com >
Acked-by: Florian Fainelli <florian.fainelli@broadcom.com >
Link: https://lore.kernel.org/r/20240424185039.1707812-3-opendmb@gmail.com
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org >
(cherry picked from commit e818cd3c8a345c046edff00b5ad0be4d39f7e4d4)
[danesh: Resolved minor conflict in drivers/gpio/gpiolib-of.c]
Signed-off-by: Danesh Petigara <danesh.petigara@broadcom.com >
Signed-off-by: Pierre Couillaud <pierre@broadcom.com >
2024-07-24 19:19:20 +00:00
Doug Berger
54edf65d08
UPSTREAM: dt-bindings: gpio: brcmstb: add gpio-ranges
...
Add optional gpio-ranges device-tree property to the Broadcom
Set-Top-Box GPIO controller.
Bug: 353554778
Change-Id: I95d9e6153e91d4270e1802c97bb4863de8b494c0
Signed-off-by: Doug Berger <opendmb@gmail.com >
Acked-by: Florian Fainelli <florian.fainelli@broadcom.com >
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org >
Link: https://lore.kernel.org/r/20240424185039.1707812-2-opendmb@gmail.com
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org >
(cherry picked from commit 7c66f8173360556ac0c3c38a91234af5a0a5a4a9)
Signed-off-by: Danesh Petigara <danesh.petigara@broadcom.com >
Signed-off-by: Pierre Couillaud <pierre@broadcom.com >
2024-07-24 19:19:20 +00:00
Paul Lawrence
e0bd441f08
ANDROID: Incremental fs: Retry page faults on non-fatal errors
...
In order to not freeze on corrupt data, we need to turn off
FAULT_FLAG_ALLOW_RETRY. However, this means we no longer retry on EINTR,
so an interrupted read will lead to page faults.
The fault handler does not seem to allow dynamic decisions as to whether
to turn on or off this flag.
To resolve both issues, add a flag to indicate if there are corrupt
pages in a file, and only if there are turn off this flag.
Also fsanitize changed the behavior of mlock - mlock should fail if the
page reads fail, but with fsanitize it returns 0 then page faults on
access. This broke this test, and fsanitize offers little value on test
code, so disable it.
Test: incfs_test passes
Bug: 343532239
Change-Id: Id2ced4be3310109206d65dcc92dea05c05131182
Signed-off-by: Paul Lawrence <paullawrence@google.com >
(cherry picked from commit b7bd4d088751a23209e0636e4d71502ef07b2d33)
2024-07-24 16:18:16 +00:00
Pierre Couillaud
9077d52bd8
ANDROID: GKI: Update symbol list for BCMSTB
...
INFO: 1 function symbol(s) added
'int scsi_resume_device(struct scsi_device*)'
Bug: 355032755
Change-Id: I65f90942b8062c559aeb2cb09394846a39c5e1dc
Signed-off-by: Pierre Couillaud <pierre@broadcom.com >
2024-07-24 04:00:22 +00:00
Bian Jin chen
9fe4f05b40
ANDROID: GKI: Update rockchip symbols for dw_hdmi_qp.
...
4 function symbol(s) added
'const struct drm_edid* drm_edid_alloc(const void*, size_t)'
'int drm_edid_connector_update(struct drm_connector*, const struct drm_edid*)'
'const struct edid* drm_edid_raw(const struct drm_edid*)'
'const struct drm_edid* drm_edid_read_ddc(struct drm_connector*, struct i2c_adapter*)'
Bug: 300024866
Signed-off-by: Bian Jin chen <kenjc.bian@rock-chips.com >
Change-Id: I3085829b4c799b1a38426576841a4bc23ba531ec
2024-07-24 02:47:35 +00:00
Jose Ignacio Tornos Martinez
d2ab7b14ca
UPSTREAM: net: usb: ax88179_178a: improve reset check
...
After ecf848eb934b ("net: usb: ax88179_178a: fix link status when link is
set to down/up") to not reset from usbnet_open after the reset from
usbnet_probe at initialization stage to speed up this, some issues have
been reported.
It seems to happen that if the initialization is slower, and some time
passes between the probe operation and the open operation, the second reset
from open is necessary too to have the device working. The reason is that
if there is no activity with the phy, this is "disconnected".
In order to improve this, the solution is to detect when the phy is
"disconnected", and we can use the phy status register for this. So we will
only reset the device from reset operation in this situation, that is, only
if necessary.
The same bahavior is happening when the device is stopped (link set to
down) and later is restarted (link set to up), so if the phy keeps working
we only need to enable the mac again, but if enough time passes between the
device stop and restart, reset is necessary, and we can detect the
situation checking the phy status register too.
Bug: 339479352
cc: stable@vger.kernel.org # 6.6+
Fixes: ecf848eb934b ("net: usb: ax88179_178a: fix link status when link is set to down/up")
Reported-by: Yongqin Liu <yongqin.liu@linaro.org >
Reported-by: Antje Miederhöfer <a.miederhoefer@gmx.de >
Reported-by: Arne Fitzenreiter <arne_f@ipfire.org >
Tested-by: Yongqin Liu <yongqin.liu@linaro.org >
Tested-by: Antje Miederhöfer <a.miederhoefer@gmx.de >
Change-Id: I0b5944bd0bf353281c884b93c15243c2f395dbbf
Signed-off-by: Jose Ignacio Tornos Martinez <jtornosm@redhat.com >
Signed-off-by: David S. Miller <davem@davemloft.net >
(cherry picked from commit 7be4cb7189f747b4e5b6977d0e4387bde3204e62)
Signed-off-by: Yongqin Liu <yongqin.liu@linaro.org >
2024-07-23 16:25:59 +00:00
Jose Ignacio Tornos Martinez
8cfaae3d49
UPSTREAM: net: usb: ax88179_178a: fix link status when link is set to down/up
...
The idea was to keep only one reset at initialization stage in order to
reduce the total delay, or the reset from usbnet_probe or the reset from
usbnet_open.
I have seen that restarting from usbnet_probe is necessary to avoid doing
too complex things. But when the link is set to down/up (for example to
configure a different mac address) the link is not correctly recovered
unless a reset is commanded from usbnet_open.
So, detect the initialization stage (first call) to not reset from
usbnet_open after the reset from usbnet_probe and after this stage, always
reset from usbnet_open too (when the link needs to be rechecked).
Apply to all the possible devices, the behavior now is going to be the same.
Bug: 339479352
cc: stable@vger.kernel.org # 6.6+
Fixes: 56f78615bcb1 ("net: usb: ax88179_178a: avoid writing the mac address before first reading")
Reported-by: Isaac Ganoung <inventor500@vivaldi.net >
Reported-by: Yongqin Liu <yongqin.liu@linaro.org >
Change-Id: I6314fcc4df3be9624b91545f1cf033144e3ae9ec
Signed-off-by: Jose Ignacio Tornos Martinez <jtornosm@redhat.com >
Reviewed-by: Simon Horman <horms@kernel.org >
Link: https://lore.kernel.org/r/20240510090846.328201-1-jtornosm@redhat.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
(cherry picked from commit ecf848eb934b03959918f5269f64c0e52bc23998)
Signed-off-by: Yongqin Liu <yongqin.liu@linaro.org >
2024-07-23 16:25:59 +00:00
Lee Jones
f21999db6a
UPSTREAM: usb: gadget: configfs: Prevent OOB read/write in usb_string_copy()
...
commit 6d3c721e686ea6c59e18289b400cc95c76e927e0 upstream.
Userspace provided string 's' could trivially have the length zero. Left
unchecked this will firstly result in an OOB read in the form
`if (str[0 - 1] == '\n') followed closely by an OOB write in the form
`str[0 - 1] = '\0'`.
There is already a validating check to catch strings that are too long.
Let's supply an additional check for invalid strings that are too short.
Bug: 346754046
Signed-off-by: Lee Jones <lee@kernel.org >
Cc: stable <stable@kernel.org >
Link: https://lore.kernel.org/r/20240705074339.633717-1-lee@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
(cherry picked from commit d1205033e9joneslee@google.com >
Change-Id: Id9a34f3e5495aef0d2a800a1386210f4d9fa8116
2024-07-23 06:12:28 +00:00
Amit Sunil Dhamne
4a9ef0dc4b
UPSTREAM: usb: typec: tcpm: fix use-after-free case in tcpm_register_source_caps
...
There could be a potential use-after-free case in
tcpm_register_source_caps(). This could happen when:
* new (say invalid) source caps are advertised
* the existing source caps are unregistered
* tcpm_register_source_caps() returns with an error as
usb_power_delivery_register_capabilities() fails
This causes port->partner_source_caps to hold on to the now freed source
caps.
Reset port->partner_source_caps value to NULL after unregistering
existing source caps.
Fixes: 230ecdf71a64 ("usb: typec: tcpm: unregister existing source caps before re-registration")
Cc: stable@vger.kernel.org
Signed-off-by: Amit Sunil Dhamne <amitsd@google.com >
Reviewed-by: Ondrej Jirman <megi@xff.cz >
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com >
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org >
Link: https://lore.kernel.org/r/20240514220134.2143181-1-amitsd@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Bug: 335453765
(cherry picked from commit e7e921918d905544500ca7a95889f898121ba886)
Change-Id: I655ac689dd559dfe22fdf545ef5a39ae056f2bde
Signed-off-by: Amit Sunil Dhamne <amitsd@google.com >
2024-07-22 20:55:16 +00:00
Amit Sunil Dhamne
e8ff0d5cdd
UPSTREAM: usb: typec: tcpm: unregister existing source caps before re-registration
...
Check and unregister existing source caps in tcpm_register_source_caps
function before registering new ones. This change fixes following
warning when port partner resends source caps after negotiating PD contract
for the purpose of re-negotiation.
[ 343.135030][ T151] sysfs: cannot create duplicate filename '/devices/virtual/usb_power_delivery/pd1/source-capabilities'
[ 343.135071][ T151] Call trace:
[ 343.135076][ T151] dump_backtrace+0xe8/0x108
[ 343.135099][ T151] show_stack+0x18/0x24
[ 343.135106][ T151] dump_stack_lvl+0x50/0x6c
[ 343.135119][ T151] dump_stack+0x18/0x24
[ 343.135126][ T151] sysfs_create_dir_ns+0xe0/0x140
[ 343.135137][ T151] kobject_add_internal+0x228/0x424
[ 343.135146][ T151] kobject_add+0x94/0x10c
[ 343.135152][ T151] device_add+0x1b0/0x4c0
[ 343.135187][ T151] device_register+0x20/0x34
[ 343.135195][ T151] usb_power_delivery_register_capabilities+0x90/0x20c
[ 343.135209][ T151] tcpm_pd_rx_handler+0x9f0/0x15b8
[ 343.135216][ T151] kthread_worker_fn+0x11c/0x260
[ 343.135227][ T151] kthread+0x114/0x1bc
[ 343.135235][ T151] ret_from_fork+0x10/0x20
[ 343.135265][ T151] kobject: kobject_add_internal failed for source-capabilities with -EEXIST, don't try to register things with the same name in the same directory.
Fixes: 8203d26905linux-usb@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org >
Signed-off-by: Amit Sunil Dhamne <amitsd@google.com >
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com >
Link: https://lore.kernel.org/r/20240424223227.1807844-1-amitsd@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Bug: 335453765
(cherry picked from commit 230ecdf71a644c9c73e0e6735b33173074ae3f94)
Change-Id: If5c563c16b426c3fb4f8d51bcbda0ba9b72d560a
Signed-off-by: Amit Sunil Dhamne <amitsd@google.com >
2024-07-22 20:55:16 +00:00
Seiya Wang
78b1a8b2e5
ANDROID: GKI: Update symbol list for mtk
...
2 function symbol(s) added
'int rpmsg_chrdev_eptdev_create(struct rpmsg_device*, struct device*, struct rpmsg_channel_info)'
'int rpmsg_chrdev_eptdev_destroy(struct device*, void*)'
1 variable symbol(s) added
'struct class* rpmsg_class'
Bug: 354094574
Change-Id: I3c10ffb4a472076f93190266d38ee5197d663ce3
Signed-off-by: Seiya Wang <seiya.wang@mediatek.com >
2024-07-22 10:16:27 +00:00
Greg Kroah-Hartman
002bba562d
Merge tag 'android14-6.1.90_r00' into android14-6.1
...
This merges up to the 6.1.90 LTS release into the android14-6.1 branch.
Included in here are the following commits:
* c03453567935df421fc4f17db53dd962184d7812909ba1f1b4ca817d44be21e042d29e6536f12fe29b7c5004d74e75e222d325b34984854201b8c8f20b947c90e3023b6390a18bf5741832e71d5ec7c0199895b8b64723dfe76ded4b981b1dd6a6bacd0a976df695f52203a447fd33d8e3e5f356bce3fcf8a8e8c79ed22bd852307fad371d69a64ebf1ff60ee3f0519da4d0205d6e0ac35fc180718e2c583c26ba234a54ee0f708a7e0a01fc53be67dd681710ab64f9d8ac2c404b0ae432ffddf569e3ba9bcc0e5894021d1d2b38f17d1fbb8bdbcfaf3e0561b65fbdc7a4bca2892b8bf690e0a957ea5aa3e60502b907e6dd0117e9c7882362894e6cd214989f882077f56a190e7ca40c42f7e039539a2b995a34410fcad9b3686200ad2ceacda270f05caed833777d7d004981ad28ac21152ed360cf13ba94f6cce3253574405bfe7bf9654526a56e02751d352858b822644fd978884187c0813e2ab753b996e8699d19ebdce660bca6fa2d9af4861f052f4115403dc931f18a1f5814051cbcf325a1c2d4b15e5e1865b77a25bfd1271e9b69459782810873ac0d14f10402424c69dbb225a82005d5b20beb059816be600293599c9ad5e1d3c4b14c8a3f7ecad54c9064163f1c9b9c4adad6d20e3beb83bab058e31a0277e73e8eaf45b5bc301aea205a42d078de8674da3c0740f0ce782b5a74818f56a8b3942debbea5e8ac4490db5bcfc5337318548e2ab92f83d4763a475816446f076ff06a1eaa1af71deecb5b05e6199ab1d84bdb526facda616b0ac25f364f83ca4c7ae24e165190beb491c1c2dcbc050cb08a5291736e3b75c4ca77077eb0a09d992f4a2013f2295faba50f7908a01667a877128b4687606d9421ff9d7d22b80ba648717d51db455c41a004ffbad9c2f69cc1013c787d23897ac5306b1e7feb31a1ad74d208f2bcff1ed2ff8f79b42d1c212e3baccd5ef7ba279976c2f4d426f7e71a7cf3e09465aecc0fb74c00d1e487b8eccf5d43e0722889af25bd4b7c6f9414920588bbbd71a676b17edb9de10b59d18672ad663a4ed7c7720a19f98f214b25a299c5669eba0750253e34029b3c3c4ba8a6c5282b223cfd87d15af82dbbaafbb4652c9b943e99ac882d6b219eae1facfc38e10c9faaa6d2a8b211d05380576f943c3e45c8d17075a935165d226472c1d87d56afa4fe8813a76f5f72a684082b831488647a25b07d0904f9ef9183ada89e4a5a704c267a5833b99cf8a424e713e05558b3b68c43bc4cfef2349dbfd65ff6ac4fdfa55f9b63193b1d011d972f7989b04d6c39f932d295636f0fdb36aedbd0961403bfe0e9367c02a4a6ccb928cde9c00f4048e1a0e2b8480b704d74cb9cdfbbdfa1448287709f7ecd89a9196aeccaa7ff1d7d932a7651004b7ed2400ef4aae2afe20fe6a97a5fc96b07dca157aadcc0283c55d4396bc330a13ab75fd4b09030559f3a6333beb3ff19a5fe446927f8ea42dbe759196617d07d45e811bab2e86c9db58e62e27ef18e6a6ebec40846efa4d5938635ac7dd9ba0db46385a1d3e3521ff1c3c617018bf7c76a2a41d8fdf3afb13db0d16bdf7c0fb8c28d56bad42a408a43b6c9f56faf87c1d6f5bc5ff0e6489cc45fbbcd0534a320dc656b06d327e96157c4421279b6581f5d5e0243b1920588d03399c3e21fa0a214751c754c6ec9f9d68334dde1380c923c67b8dc508933d38d9b355c3e92ad49f31f521ad20db16d1dce1800c9628ef46e0e9fbef5603f9e13704edc9252add0ff348607b37f227cbcdd9ce78d45eec81eaccbe7b911e0121a83be2101c227f5a787f8aac7401e05339968af0a15ff846741e066ec724fbc7c0c90819b18307cc89dbcb829bd4d05f22bc1796f8ed844df11007f18a0df76d737d8cd8e4b0b5d621edc2db3e978b1b32586f7662e341e570d433e4082d447d8de8422f51ddb0c881b495ed29c097739170c182182d6a2c1c0cfabf6e2d61dc118c8cc66808a6fea3fcbd29b50a32c4b53d7d62062029bc9ff88dd8bb129c00146b39906fe999854cb3131b5a25f1205b86b91580ea48b19ff8fed337d44e12efb4dea83d483b75722be42fb6d14e23d19643bf8c98edb087c4488a50c8a50ad26f26abd2e8dc5cffcc760089aa99d42f373397bc65d23bade76ae9ea103d564999f2c46877f5f7e33f6879184a352b7eb492337a4fbbe03315452ecedcd7e394a1b65d1e52a523f14a3ac1c10b4eb0b445005599fc74e367b438b9a71b2b7dc2e6b8784fb60063524c0c5867a49054b3ed2bccc8d1550bd9b94055c66fab1e1202d5f12de4c3fe79b2c830559b2d759ca5962bdc537db5a6cacfaf34a67ebcd5d98c055c5f9fe2c1eeea65ed738cea93dae3e21f5cfed1e00e34ff1cee80b4980af649e5646363a9c459091345b6b8319f1465ff4c8cf0650adb62b859779772aeb805a1b8d3a58af50fcd1993a29664206ff8b30044c66bc5245a6da27f8a7b7b0858b849265da103c0f946f409289d0a157e6634e59f692c547e3893b2562617dbf08298863eaa43d5d1e9f5619d95e7da5bb2d39da708cb244479c7fef70310e55b5055e406d7b4097b1f10f512a01da71c87e811caeb7d153bfbaaaefa79c1543be051f353a94feab04354a5d7bb7aba664845ababa351068b75395ec4b84ed33a0822e2177f94c3f3c1e735deae948ecd513701b0f01ee0b5f96b653cb1e52c95238e1c2bdc87dd15918ac1e0f080a48bfb4b03ca83a7728e4b19fe5eea6d7ee3bf0ca5693dd6d3d9ae356c6270f30f95b9136c2a2863b50bd749c606597a6687a4e0cfb25d4a3f6045ce351a9b20a04635594cca58ead0a04a7161d6b80378af60bb2b2b8ca15861c6925d11fbda292048934b510fbe3a794b016b28b8d80e09202feacd430b4fd5fdacae9d6b0472d5f7dd4831c3ee6768c6737a28d27f66eda08c217d8416b90bf4766a1080110bf1e3b1cb1e21838dfd03e4283b77143704e993abb8384b6df42196bdec029c50bb6fb07dbb10f1574fcb18177fd52c0397b5e6898b8549c2b4b6577a6dc534c07d1fefedc1a08ef93ebc77e8360ac87f941400479494c91e1e9c868cabdf684488466b716b7d785778fefd166fc22904231468c99dfb49bf6583444d7c88f7a7095447d844a3e22943e4fe420a915154c97e93367e87b6df050c49406d598a1f35d7ede622ff8f06550883e072e8351a6c2af9d2e5f8dc1de7ef6a7f9b3c19715ec2512059cf04878942ac7549adcfd56704b87c1bc257171d6aef17ff957cea84ff3d8ac62044c34fe35eb028d1ebd392c47fea781f7c9da2bd00c24ddec90a477dfda4af6d5b4d92233bd583c815c2a1c432f7efda53af089d4554af9690dfa18265a0fc55fb3608fe28fc1781222074eed9d0a4877db987b479109472e71a33b7cb184095cfa2d9b2f6953617df3c2ceb847810dd068ae43df8e64df2990d8eacd3e89846283fe74ea5b8bd417e3c16de7e7030f0a39efe5b6f6940ff35ae88c58d38405d12245080cfd6692e9b580247e0eca167d4b47a92febb7eeb41db7fcb2b21829b618cced37bdaee623178ec5ab2eeab8c47c66cb665900106081616977f5e52d7be01835f3a1b7d1ce2cc755d3fe7b2ba44770fed88a57544e9218aae2cb879b5b7708ec4e8447a9a3745cf6a8431c9e71ca61db388b8e12fc77240f63cbaac2e5487c1250796b18e189442a38e3eaa8613e773d04aea2812ff7ea298dc5dd389bf4acc8025d920886c33d61f1704b923579201dad141b08d18d029111b858638e3b487d0567842b06426737652553bfaa19852698c9fd98cdac206b24444af5dd30fabe50a7f52c8f1210efb4573fea0e111ce74050b69054f4b8b533eeeeebabdae52fbeaf0e799691b243de9116307e7bc1231b189fa199a75d750057beec623ab51ec7fc9f03369955128333aae9bb7b7c6df4650cf5cecba6gregkh@google.com >
2024-07-20 13:53:50 +00:00
Manish Pandey
6d6afa9d3f
FROMGIT: scsi: ufs: core: Suspend clk scaling on no request
...
Currently UFS clk scaling is getting suspended only when the clks are
scaled down. When high load is generated, a huge amount of latency is
added due to scaling up the clk and completing the request post that.
Suspending the scaling in its existing state when high load is generated
improves the random performance KPI by 28%. So suspending the scaling when there are no requests. And the clk would be put in low scaled state when the actual request load is low.
Make this change optional by having the check enabled using vops since for some devices suspending without bringing the clk in low scaled state might have impact on power consumption of the SoC.
The change takes advantage of the hole in 'struct ufs_clk_scaling' before ANDROID_KABI_RESERVE and does not change the size of the struct.
Use __GENKSYMS__ marker to preserve the abi correctly.
Signed-off-by: Ram Prakash Gupta <quic_rampraka@quicinc.com >
Link: https://lore.kernel.org/r/20240627083756.25340-2-quic_rampraka@quicinc.com
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com >
Bug: 351099319
(cherry picked from commit 50183ac2cfb54e027dd36fb22ea1bd1e91e3a08b
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git 6.11/scsi-staging)
Change-Id: I6e11beab7bc56746e7e1ae1ea25f9ab205394ef7
Signed-off-by: Manish Pandey <quic_mapa@quicinc.com >
(cherry picked from commit 78931ac60273825b4141796eb8631424b3690712)
2024-07-19 19:40:17 +00:00
Manish Pandey
f858f0ff4e
FROMGIT: scsi: ufs: qcom: Enable suspending clk scaling on no request
...
Enable suspending clk scaling on no request for Qualcomm SoC.
Signed-off-by: Ram Prakash Gupta <quic_rampraka@quicinc.com >
Link: https://lore.kernel.org/r/20240627083756.25340-3-quic_rampraka@quicinc.com
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com >
Bug: 351099319
(cherry picked from commit ed7dac86f1406d73aed21d0cd1563922031a2fd8
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git 6.11/scsi-staging)
Change-Id: Ifbdc14ceae5a59c04a5977b56a198fd295253b3e
Signed-off-by: Manish Pandey <quic_mapa@quicinc.com >
(cherry picked from commit fcfa54b63051a70ad2467a444001b302e97fe9eb)
2024-07-19 09:55:29 +00:00
Kalesh Singh
f3437db870
ANDROID: 16K: Don't set padding vm_flags on 32-bit archs
...
vma_pad_fixup_flags() and is_mergable_pad_vma() were inadvertently
affecting the vm_flags on 32-bit arch, making some VMAs not mergable.
This causes zygote to crash as the Art GC's heap compaction fails.
The compaction depends on mremap() which will fail when operating on
a range that spans multiple VMAs [1]. This can happen now due to the
incorrect is_mergable_pad_vma() check.
Make all the pgsize_migration APIs no-ops in 32-bit architectures,
since Android only performs ELF segment extension in 64-bit archs.
[1] https://github.com/torvalds/linux/blob/v6.9/mm/mremap.c#L841-L843
Bug: 353667356
Change-Id: Id9b0076ef173d75a4afc85577355d340fce03e65
Signed-off-by: Kalesh Singh <kaleshsingh@google.com >
2024-07-18 17:02:45 +00:00
quic_anane
fc94b39f66
ANDROID: abi_gki_aarch64_qcom: Add groups_free symbol
...
Add groups_free to abi_gki_aarch64_qcom.
1 function symbol(s) added
'void groups_free(struct group_info*)'
Bug: 352712755
Change-Id: I4ee87435608c3050c2ebbe82e3d1b43bfb4700db
Signed-off-by: quic_anane <quic_anane@quicinc.com >
2024-07-18 05:27:55 +05:30
Kuen-Han Tsai
c78828e383
FROMLIST: usb: gadget: u_serial: Add null pointer checks after RX/TX submission
...
Commit ffd603f214ffd603f214stable@vger.kernel.org
Signed-off-by: Kuen-Han Tsai <khtsai@google.com >
Bug: 283247551
Link: https://lore.kernel.org/lkml/20240116141801.396398-1-khtsai@google.com/
Change-Id: Ib850c7d313194074941576a7fdd3a9f58486ad78
Signed-off-by: Kuen-Han Tsai <khtsai@google.com >
2024-07-17 09:15:33 +00:00
Gao Xiang
7de5ae52b1
UPSTREAM: erofs: fix uninitialized page cache reported by KMSAN
...
syzbot reports a KMSAN reproducer [1] which generates a crafted
filesystem image and causes IMA to read uninitialized page cache.
Later, (rq->outputsize > rq->inputsize) will be formally supported
after either large uncompressed pclusters (> block size) or big
lclusters are landed. However, currently there is no way to generate
such filesystems by using mkfs.erofs.
Thus, let's mark this condition as unsupported for now.
[1] https://lore.kernel.org/r/0000000000002be12a0611ca7ff8@google.com
Bug: 353575918
Reported-and-tested-by: syzbot+7bc44a489f0ef0670bd5@syzkaller.appspotmail.com
Fixes: 1ca01520148a ("erofs: refine z_erofs_transform_plain() for sub-page block support")
Reviewed-by: Sandeep Dhavale <dhavale@google.com >
Reviewed-by: Yue Hu <huyue2@coolpad.com >
Reviewed-by: Chao Yu <chao@kernel.org >
Change-Id: I7a8e0bc81c1f4512d3640b243e8124a61d849028
Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com >
Link: https://lore.kernel.org/r/20240304035339.425857-1-hsiangkao@linux.alibaba.com
(cherry picked from commit 893e5e9b7369a02e7ceaa6d98db6739162005b03)
Signed-off-by: Sandeep Dhavale <dhavale@google.com >
2024-07-16 14:26:37 -07:00
Greg Kroah-Hartman
4965ad067b
ANDROID: Fix abi issues in struct sk_buff
...
In commit 18685451fc4e ("inet: inet_defrag: prevent sk release while
still in use"), struct sk_buff dropped an unneeded union structure.
This did not change the actual structure size or layout at all, but the
abi checker didn't like it. So trick it by putting some __GENKSYMS__
markers in to preserve the abi correctly.
Bug: 335584858
Fixes: 18685451fc4e ("inet: inet_defrag: prevent sk release while still in use")
Change-Id: I78ca54f9df3e03cccebc326babf1d84ccb5dc781
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com >
2024-07-16 08:37:58 +00:00
Florian Westphal
47d9c7690e
UPSTREAM: inet: inet_defrag: prevent sk release while still in use
...
ip_local_out() and other functions can pass skb->sk as function argument.
If the skb is a fragment and reassembly happens before such function call
returns, the sk must not be released.
This affects skb fragments reassembled via netfilter or similar
modules, e.g. openvswitch or ct_act.c, when run as part of tx pipeline.
Eric Dumazet made an initial analysis of this bug. Quoting Eric:
Calling ip_defrag() in output path is also implying skb_orphan(),
which is buggy because output path relies on sk not disappearing.
A relevant old patch about the issue was :
8282f274497026b1ddb6edumazet@google.com >
Reported-by: xingwei lee <xrivendell7@gmail.com >
Reported-by: yue sun <samsun1006219@gmail.com >
Reported-by: syzbot+e5167d7144a62715044c@syzkaller.appspotmail.com
Signed-off-by: Florian Westphal <fw@strlen.de >
Reviewed-by: Eric Dumazet <edumazet@google.com >
Link: https://lore.kernel.org/r/20240326101845.30836-1-fw@strlen.de
Signed-off-by: Paolo Abeni <pabeni@redhat.com >
(cherry picked from commit 18685451fc4e546fc0e718580d32df3c0e5c8272)
Bug: 335584858
Change-Id: I008a7b5fc4f51c9ad0ee14cf05ba21ca3ff5d6b3
Cc: Lee Jones <joneslee@google.com >
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com >
2024-07-15 15:03:06 +00:00
zhujingpeng
96d66062d0
ANDROID: GKI: Add initialization for mutex oem_data.
...
Although __mutex_init() already contains a hook, but this
function may be called before the mutex_init hook is registered,
causing mutex's oem_data to be uninitialized and causing unpredictable errors.
Bug: 352181884
Change-Id: I04378d6668fb4e7b93c11d930ac46aae484fc835
Signed-off-by: zhujingpeng <zhujingpeng@vivo.com >
2024-07-10 19:21:56 +00:00
Charan Teja Kalla
9e55f41695
ANDROID: abi_gki_aarch64_qcom: whitelist some mm symbols
...
Whitelist the below symbols:
android_vh_madvise_cold_or_pageout_page
get_shadow_from_swap_cache
Compiler o/p:
INFO: 2 function symbol(s) added
'int __traceiter_android_vh_madvise_cold_or_pageout_page(void*, bool,
struct page*)'
'void* get_shadow_from_swap_cache(swp_entry_t)'
1 variable symbol(s) added
'struct tracepoint
__tracepoint_android_vh_madvise_cold_or_pageout_page'
.
Bug: 350429581
Change-Id: I3f51722c9fcdc666534b4b13c62a2f7f71387242
Signed-off-by: Charan Teja Kalla <quic_charante@quicinc.com >
2024-07-09 19:55:56 +00:00
Charan Teja Kalla
56526cf940
ANDROID: mm: swap: export and whitelist get_shadow_from_swap_cache
...
The shadow entry in the swapcache contains information about
a page that got swapped out during the reclaim which is then used at the
time of refault to determine if a page is going to be a workingset or
not.
Once the page is swapped out, vendors can implement some algorithms on
the swap area to determine if that page can be further pushed down to
slower devices, Eg: say from costly and faster disk to slower disk. But
if a page that is actively used is pushed to slower disk, the swapin is
going to consume time which can show up in PSI events. The side effect
of increased PSI events is, an example, increased kills by LMKD.
Alternatively, vendors can rely on the information stored in the
swapcache and determine if that particular page in the swap can be
further pushed down to slower devices.
Bug: 350429581
Change-Id: Ibeee10d40cc917229fe3b0fd9a6ef34ad27033e1
Signed-off-by: Charan Teja Kalla <quic_charante@quicinc.com >
2024-07-09 19:55:56 +00:00
Charan Teja Kalla
74be75dd10
ANDROID: mm: madvise: vendor hook to tune page flags
...
Users can proactively reclaim the pages of an app once it is in
background using the system calls, like madvise. But it may be possible
that such pages turn out to be the workingset page in the conventional
LRU which while swapping can result into accounting of PSI events.
Although this PSI events is an indication that wrong pages are being
madvised, one can also argue that he is aware of what he is doing using
madvise.
For such clients, add the vendor hook to tune page flags, such as
clearing the Workingset during swapout so that PSI might not get
accounyted during swapin.
Bug: 350429581
Change-Id: I675c57f63a918c5a23df8273006426d0e611c5c5
Signed-off-by: Charan Teja Kalla <quic_charante@quicinc.com >
2024-07-09 19:55:56 +00:00
zhujingpeng
7fc3794962
ANDROID: GKI: Add initialization for rwsem's oem_data and vendor_data.
...
Add initialization for rwsem's oem_data and vendor_data.
The __init_rwsem() already contains a hook, but this function
may be called before the rwsem_init hook is registered,
causing some rwsem's oem_data to be uninitialized and
causing unpredictable errors
Bug: 351133539
Change-Id: I7bbb83894d200102bc7d84e91678f164529097a0
Signed-off-by: zhujingpeng <zhujingpeng@vivo.com >
(cherry picked from commit aaca6b10f1a352dec4596548396f590500f2001b)
2024-07-09 16:59:32 +08:00
Krishna Kurapati
f6b99539f8
UPSTREAM: usb: dwc3: core: Skip setting event buffers for host only controllers
...
On some SoC's like SA8295P where the tertiary controller is host-only
capable, GEVTADDRHI/LO, GEVTSIZ, GEVTCOUNT registers are not accessible.
Trying to access them leads to a crash.
For DRD/Peripheral supported controllers, event buffer setup is done
again in gadget_pullup. Skip setup or cleanup of event buffers if
controller is host-only capable.
Suggested-by: Johan Hovold <johan@kernel.org >
Signed-off-by: Krishna Kurapati <quic_kriskura@quicinc.com >
Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com >
Reviewed-by: Johan Hovold <johan+linaro@kernel.org >
Reviewed-by: Bjorn Andersson <andersson@kernel.org >
Tested-by: Johan Hovold <johan+linaro@kernel.org >
Link: https://lore.kernel.org/r/20240420044901.884098-4-quic_kriskura@quicinc.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
(cherry picked from commit 89d7f962994604a3e3d480832788d06179abefc5
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master)
Bug: 233985973
Change-Id: I66bccca575b3524b8e446f38b154d2434335a65d
Signed-off-by: Krishna Kurapati <quic_kriskura@quicinc.com >
2024-07-08 23:15:01 +00:00
Seiya Wang
ce6f9cab9e
ANDROID: GKI: Update symbol list for mtk
...
1 function symbol(s) added
'int phy_create_lookup(struct phy*, const char*, const char*)'
Bug: 350828988
Change-Id: If747b9e3acdf6e644ee23783f4997aff1d973e64
Signed-off-by: Seiya Wang <seiya.wang@mediatek.com >
2024-07-04 13:53:32 +00:00
Zhifeng Zhu
256660feeb
ANDROID: GKI: Add symbol to symbol list for vivo.
...
1 function symbol added
'int __traceiter_android_rvh_pr_set_vma_name_bypass(void*, struct
mm_struct*,unsigned long , unsigned long , struct anon_vma_name*,int*, bool*))'
1 variable symbol added
'struct tracepoint__tracepoint_android_rvh_pr_set_vma_name_bypass'
Bug: 349739224
Change-Id: I4a3c4478def0400c7110c979ee00781e1b7e6821
Signed-off-by: Zhifeng Zhu <zhifeng.zhu@vivo.com >
2024-07-03 21:50:36 +00:00
Zhifeng Zhu
d256bfafa9
ANDROID: vendor_hooks: add hooks in prctl_set_vma
...
In some special scenarios, some threads are allowed to skip waiting,
write the set_anon_name task into the queue and return directly, thus
improving the system's response speed and performance.
Bug: 349739224
Change-Id: Id3686309da108e242a30cfaf68f859b10215f402
Signed-off-by: Zhifeng Zhu <zhifeng.zhu@vivo.com >
2024-07-03 21:50:36 +00:00
Jiewen Wang
0468527935
ANDROID: GKI: Update symbols list for vivo
...
1 function symbol(s) added
'char* next_arg(char*, char**, char**)'
Bug: 335745207
Change-Id: I4fb57db677682da5b3aa04ae9e299f2aa877a43c
Signed-off-by: Jiewen Wang <jiewen.wang@vivo.com >
2024-07-03 10:42:02 +08:00
Nikhil V
81e9f0610c
UPSTREAM: arm64: mm: Make hibernation aware of KFENCE
...
In the restore path, swsusp_arch_suspend_exit uses copy_page() to
over-write memory. However, with features like KFENCE enabled, there could
be situations where it may have marked some pages as not valid, due to
which it could be reported as invalid accesses.
Consider a situation where page 'P' was part of the hibernation image.
Now, when the resume kernel tries to restore the pages, the same page 'P'
is already in use in the resume kernel and is kfence protected, due to
which its mapping is removed from linear map. Since restoring pages happens
with the resume kernel page tables, we would end up accessing 'P' during
copy and results in kernel pagefault.
The proposed fix tries to solve this issue by marking PTE as valid for such
kfence protected pages.
Bug: 350428411
Co-developed-by: Pavankumar Kondeti <quic_pkondeti@quicinc.com >
Signed-off-by: Pavankumar Kondeti <quic_pkondeti@quicinc.com >
Signed-off-by: Nikhil V <quic_nprakash@quicinc.com >
Link: https://lore.kernel.org/r/20230713070757.4093-1-quic_nprakash@quicinc.com
Signed-off-by: Will Deacon <will@kernel.org >
(cherry picked from commit a8bd38dbc5quic_nprakash@quicinc.com >
2024-07-02 00:47:27 +00:00
Todd Poynor
aa8621e002
ANDROID: Update the ABI symbol list: set_normalized_timespec64
...
Adding the following symbols:
- set_normalized_timespec64
Bug: 350541515
Change-Id: Idf7de820d163d4aef5797a5ef3bb07fcbe81e1c1
Signed-off-by: Todd Poynor <toddpoynor@google.com >
2024-07-01 20:42:47 +00:00
Greg Kroah-Hartman
87fb1f2f1e
Merge tag 'android14-6.1.84_r00' into android14-6.1
...
This catches the android14-6.1 branch up to the 6.1.84 LTS release.
Included in here are the following commits:
* 1dca1fead9b98ce0fe285f29666f69501c229a8a2b84f5edda2b530e8f5d347385861c7b970a145cab062fa3dcdf84d9f77998cfafaf2fd511040d818dbc176220d8cd93e030f2b85a4cc700f511d716f30b3ee9a465f195232b282877633b09c0ac18ca1bcbd100ab101c1d2d4614a3ca35c53cd58084e43b9d72442ac223bc352c12d0306cecf8704d54c8959aacfe3a2d28af770df74c5e0b5419ca7ef7d874cdf12f8dbc48eb1b5332949282064a8a42e16a3e284e15b79dac54f081cd20a6e83b8416da2df7008bf3d6223678cf67ff9d66ae0e7b6c6a45645aaa1d1ce1adc9006b90ba916cd2fcbc181f92abdafa2b9384387eab7b021872e4d3fb72b691954c94016119154946efbdbc959acfd8b0836fc218ccd5244cb8200ead9cc5e9e5547f4afacea433300285192058bb3e4e79b4a64d7aa70c49227eeabcea79d7387bcb77a321a9907c6b226ae43dca8106fffcbf2ba0b2413372c3ffc3fe272b615077e3de4113851ddc3587452a382970083e750c9f7932db06c87d29d4c72c33dc33f560139dfcc4d76d87a9be22052e4c8987242006996d4f2debd9c644b6fb6cdeb9d103aca821c7c00dae493ed133b46417684315dc33e92af3573777eb56551ad70e865dc2cb3eee7775e87f500250a68a352f67c82ed0d7f62fde41ef80ecc7218d8be62a7d3e5222a179936381380a64c3873cb26ee02e3559cd1bbca03f2149f8a56e7a391de92743fe5dc9fad50fd2f24f5df4c386d3155a3d8d8fe5b5948c762cfa00b0e8635e23035d18d5fc3c16994a1e583c99cd2d491d2d56aca5484154e76735d40ab69217ccaa4fb8dc7664ee8bd8f42ba91668e5b3ad3e8e2eadf1adf57f122486a03a70b1c9324868c0ecdb726374dde5d24a79ccdf408837d7ef4f34b79c7773e4f955b372c1efe3f2406b0241d0196f198ca636c676e2ede82dc1131562e06fdd183d47eb40573070c70a3e0581a4dac6589c414138139845240d25bc98657009c3fa70f6b7cea3a9af97cd43ba8277eae2d2570e21852b886bcf9d2cadefd67e570a9f23176ad7bbec4e4d84192e9f907846b832e09df5bc133ef61f5124c74aaf4b1a5aa050e9f82b1cfcf7345280ae696b7c008f914db6fe191df89d8fcb676955d1b7f6c3630ed6b5aac451a621686537b1cf18e5bd6e0f7e6fb16c2f0e05501df7dcfb8a6615ef6e312952d0db184ee09d40993fe0ac10bdf56ba2d484dcc6b99c610f1e6cd8fb4732ac1c233d863cf20704f3652bd0a601e7a7fc32eaf695d33abc2d160ef3ed58d7b3bda2265e6d220778af6c3a342fa318768625f84bbf1eef7fc09cb3ace502b4139fe93308eceec793fb1088d51bb04abf51d7acda20add403f58a6479ad8a4eb6631ede7f1d7e509546fc03dcd51ab42bf299404fd8aab8a0745fc9ef367b3e900b81caf050361c2af7c13e725657b8073c069a2496e37ada371f27c2c8970e8c49f2bdba49e46956a2038d00a43ebdbd39ed85c3113a8093d6e928d0ab375e73b67095647fa87209645433a4aa08d5b2c898469d537040c257185de0b7cddd92b159c5852db52b45a7b6523f9256452891e29477cfeb30ceffd026f8053bb9aab7a5d32783a53b64d68d906eb684e9c010857a2412ffbfea10d95d1442eeb95ecbc7465f142d87c958c8cc05de8e428ca0000f03b821647b5ea241b193719d7f899d81479bf758226fc408c5efffffde338557bef80c0993f7f85d605ddb3a6e334fb1438914cdbd9440b54478d203e2c545b84161656ca92ecff51913c5f29793c3391025ff4e6a09c1be4d586d21d0356a12609c76b707c3fe923f74cd997ba1dee9c25865d4b1c3b5eca881dd09fd9875deeefe5166fc45d7e144e477030b812f706f113d5341ee2957037c1da50fd98712981cf0cab4b6aa21725f8d70aa08323769db86adf1ee75aa6681cc178d7c229c1b5f6150619421ea6147e04a86c0dded0f8b7386876ffd0ba60e394bff903561b70328f7d241e5cd595e239b2e8276bf4b0c547923f07ffd18d7aa587257e192b3c2437dd0980ed8181bf455b2c6766ec94cc586c0c154a7f1fa919ea55ff8f56c393890e7008cf21ddce5b89683cb6c2c5ad233dc7329d2550d7953e6709a2f53ae0f3669e545e4b1c1a64cc7599e8a231bd4d68b1140c58035d8af38f1ac3f337f0acf7d8cba6320e21c3c01b29a5055ee6af7c8a29887ca3d940f52287ed41645a83b220c07b6891ca680fc9b9c621d830032bcbe4512b9acd343a618bcef7eed7e11f7880736286b62bad2da149afee5c71883ed12d7cb8ae8e5ec1ed222ca7386d9b040421ff7ffcac1bd2474a45dabc9b13fd9ec0e06c7979905a157046df9cf77e0d2034a6b92d23e49f4e42ca629b90d1d4ff6a8f8d2b48ecc76bea2dfd5fabc493a56abc609ce8b3c8aa68d9fc2ad7362db2fe955764b4152af9897e722ae3d1063e660319fc6b4f42595630e3aa174995c594bdbd5b5a579ddf031db25e31476426abf9b4fd4a210de889846dfc8a4e063d67e02b66195664d5e5a044b449684e376aa25e54f44b91d54a2c47486973acc18631d43d406e828b3f18c0fe010cb8ede73123c322eb43c0eb0455371ccaaa8e143bf987bc93ecde85d53ebaefe4de4935798df108a9a67eba3e674bba2a0ba00ebe3a9f3c23c2e2c805917bfaa58db621da84f10b5ecf59fba542c8b3c77e54cce8137492acea36be362d00729ae771b805d0606bedcc3629af0d5fefd58b4e3c08c4889a9eaa8b2b26fddfaa2ba4ceb765f673c0e693c1edfcf6d7e897358d6e321dcd7491ec4f454dd7f2d0f61d1f384e4c2c2c32faae8c550f0055c0189516bb548feaf23f3a3f22feb22d2bd30c710e9eee1ce1b32bfbab72a55ca0c7eaee04d15c8bb107052a8cf3a1ec897080a70199742fcb7e70482c6a05e45deff4dd05a9483ee64af9b5ac2ca7a50438adcd01782120c9ab4c82d43406967355a760b6a2ef972506be122c8d23eb47e41c2527480cab5e0b0d1c46ad183ee7136ce106d8ef07a08ebcfd72101966b776e93e0f8837dee677d178e6e28e6508df9a3c70477301ad7bef4258e58820dfdf4c1acacdf24f3d58006813ebd6632a54ac8298f7f1370d133d67e7e9a81950417b494caad9c4a00001d22fe636b9a6e511a6a88b2b14524556f5342ad8db5128c04cc044f6274bafdbf10ef659bca9b82755a7d82efd8d3c264af81ade4892870a5dc84f8c1a3a71f66bd5f4421c74602c12efda47d7f9e833fc0fd14781b306814dc592d1f3e99104299cd54167df69b926799437a111f790c9550b0326bf5c2fade3828fc3ab87ae1b0dc1283fe9c3f449310d3de9829eaa9246ba19403d20e29fde8895bd346b3e5b2fa8810aa5a845a47830443f4364c8f8ba8db9786b17195f1e01eb749a9c3f6d51a91b4680c94312e06e3827715fe790f340e40624af667758629d348e6ed73bb8ec994fed05cf3f407ccbe29f922ae4abb459d437d8bc95d3440806dc32deaa57bbd606ad3e8c2409af4a1a30f1850c0ad785aad10289f682b50b4f0d4b605c3831fc9b4e220ddb7c2b7eae2440e278cb56bb3c04738cfea1c9ad46ccbd0227fdcdcf9a71720fd74fa88877cce250a262a77d85e99f30e12e5f30e6322bc8ec278830cb3cf70472a19af2ce84c2a2ff7095160044ab84866e74f2f748c91a4bfc7586e19c88af06899582ca83fdaeaeaedf7990baa98a2feb8ec9c40281962715264ad09cb8adca52f68644bf5ecda77c1d39b1b6cfa4c766083089ab0ac7a47aaa71023de27cda96738eb21653a17a99d8beed376c9e5f04ec4428499af061634a7b30f5648fba9d7f5eeaa98f34d2c727f83eb33fb18efae216712c698934212a62347635b112a9e8486e46f5bd963ff48ed86e1fa7bc259c196eb804db3c1ad24cc77b670681ba2255528b43ec7e423bb0006c94478f7e5bedb6e5e16f1be52ee92cee16c33dd990820c84be6bea023d846efab55e16c76cfe86f2d7f1d9f8bde96132cc2e15425ac24283936e0f81a0d276d9f33c20211d3df4c515757052b718bb18f88611c1fdc9c23056893f95febbffe093cec79f0386c248775031d2acc42fad9bcd4d7a9545af2a5e2fed151d58bfc6b840a1e33bdd0234bc2befb93fedd55b8a55c77447aa46606534538ef71a93eeca03ede228221af11fcb04e580938979b2ca91f6e8a2f812b4b437af288ecb4907fb68d0697d4862d23f96f86ded73b916bcca1f57a01274d99d267da71cdbd1fcbb4bb2291d6ecab386a8e78b8952e1d992cbc89b0a5fd802a1fd80bac49ae5666fe7b85c855a1a5b79cd961d99374d0639261fed6a1df674f4f1e2dee795fb93bdea4116bd6eeed2186ea40dde02bf5fc333a02b3be8f38b401b44c820998a53248f4ae051b3bae282a7ab56f24bf6ae1ec0043bb21851465c1760abb10d10dbf722df7dbf2c16760b5b89e41b98ed6417ee72160cb6ea81edfc5ec6798cf0aaa5a26e6d2a7515cc676df3518cea837745003b591d8766257c2b8dd353a1a3033583a78b6b6bdfca8c67698325c90f089d77e13fa3326ef790ae577ef93887212608a1d2ecd9b081bf64a7e3e5e8248c0f0439b7d6774ca3ef68d868ec86861aba7b2140ea34fba8c4428e7fd1c70d12ffa0308188e9aff68eaf5eaa406d6c28aefe9283e38fc7d96436365e5267a6af608f8b89a3672ad999aa181977bb962a1ba0e1cc43e7533ed7668e6450d5e46807f9913960a5d59ed95f11b50b8bad575eb8747374709a7e59a4fb2bdee72dbf660e02f3ce8fcbf567c0411dc0e3732d1df05c7c2d1985e61a994b2b0e50fa810008985fd3550fbd3a72180656ee2baab1be3f1aa995e91c95553983d354bb22b54f2476fb80b3e754492f2126305896c8ff4f175de546a46c8615de5d35d346b5d6d4c7bd6dccad82f16716d6aa6c0bf0e5b11ff736ce8cc5e62d1614e1fd69a07188311f49c513f467056108e01aa9e9c7764c4b96f7eabd23425dab9abd34206f3806a0a181996e18f236137085bbd92448f1dcd620af5ee5181f7ae4808867cc9547633c01b3f0fef917dadb09eee84c44b4a8a6c19f157fab03e0db019d22c5ba57762c2d4cca3812a47a328fe81bcd31d467e10507512a7037696cbfc5879d7543167afcf4b8c39b9d95ef751629793a3bb532a304d8c92d9fe6ef245eba76e480801d992088df0b6dc034e92cdc9d71ab2e92ab17ed405b9c03f29476fac758b5760939da28f4d1e0b2e3ec80ea79158ea9395a584c7734a02e16a41e5f0c3497082b0b89b470a4e2f0cae0b66d663da8635a0d43cee5df3b81a5651c44356884346480866cfedde30584c02b9ccbb498f1d6da146803b776d5ac33713825deaef2bf5d28fa5f0e6fed835d415a47d68d777e439607291dec82a8fc46e49f3ac4339001e3c42bce83144ba998fd719e67faff12e823420b3ff1f394334fe2a63a3c1f3c9afdd29726a6293ff942e0de693d68bc0b22568a944faf8a4825822c027078e23edc54a6632e19acbea2a1052f2850bb48189045f29a0bd2e193db1b43011e898b2a3778f3e13d9340ec8ddb904eebfd455a316da31360b41bc65e075d7f47af741d67ced61adba85cc585a344af68866334e352d7ebcb5d85fafd8254ada67116b74edfaad334a07946d956b2e3087505d22444d079b29d3e02fb4559035e04e19ec82b3ca0e351d1aa2c6ff5fb6b117acece41da3d369aeb37eb95e0af52c96f66cd0c4c795b21d2402392bed3a396c409a8f0549370686c909d2271b540625762dfaeac3f3fff7614f5777330c123d5a664585a7350265a753476a48cd378ff6d88c0434378d7ad21f3fd81bfff0acafd6f733d064aecde58f2862e956587affe2f3ea5ec83dc479755cb8ce606d53345c6c2fb3c1eb737331247b2b8a6c75f28dae5463f30f07ba574481d72a4b371e1c1b320920deeec6ccbf6efab88973a8f9b712e63680a78b7be6ef58e017486dadc66f9f22e61f76cb66ff6b12589f615a1f61516f49e8d9f4650d4150f5eb5aa0c564c0c8d8876aae6ee5c4e269255ac53d78fae3f8b5549fbef7dcd8519a80ea5ae62d8c1281137d20da8ef82865e2a0850333a25abfef0cfab40a49efb948d03a9855cb831e9e63cc04dd4403ffbf0ca988e25c4feadb00463b51e90cdf3dec320be2fa53a04c364d77459715232915916083b4c590640f27fc2e99a20f58912cca5f519e51a07102184f3077c3ea7bc9533e07a8901f331b71c43b714fcac22c9a5e0912dce9ede840ae3dc2801873f1752e4711631529134968f7530a4271b788035744b9ef12d049fabeeeb4655d469b84516cc577208f81d8950e8e203bad8dc0aebad6e66d07e7945d93fe2d9b3e1ae188067197e9f27d319df0d93fd40c62a8722cece303ad085eb184a3c10a0cfb7be5e5ec53e3f2ee8afbccc5eb16e641486355e6e04845c265742f4bb1c9fa51d4c4396a412001249d6ca4ff76109a226a4974d928d5c65c475560bc9f87a41d70af82bb9c474d521da8300111cd90034e2d70b5237ecf1afe8dafc066c52e443ed55f444d70889df590040ce2c34adc20b9930e826962abd32d7f5c59ed284c7bfd3289ab8e4cbbc2f0db8cec41a3503bfe04c1278f626221e58310080799058ed71e0f2f91a96b89d36b9a1b4e7f8644b6a8cefe18e9ecddc547dd0508562ca97140f0f326cf7d4121b401a0222b4817f2261eb9942b1414d5e9b8afc22a11ddf6ee3df392b8a3273f67ffc334b9fc47ed389a940963613229059d0f3be5383662fdeb7b5777d37b410226d92dc94c160e30a5e812f70b056a52b3926405765f45085686b9cad078914b17ccd9798faa589723261b4223e807d77ab053fb548ab66730c41548fede1b0998fdd87985d73961e85b3c153929360fd328a3c8fa54e9ab63de24eb0ac219c4c30b27bf4c4965a389ef9787632bc9ecafbf1a5cefe5f488993b329fc4d3f7b3152afc0e0d04e45c65976126f2de39c6312009e89c84422f8745f3592ef8faa53637ed9fdc82ca49e734926a0cea0c330a507eeaad4de30f82597b5dbedec7e5174ac6b53a00459ae532a76072bc732a3d40b402b73dd5f999cf33e6ca127d34b10786ae5f10ed95b7be6c737a1c7c998232d8fcb4c06b290b1bfd859006fc45ee601ccd855a706f6a46d8563b8244dba3eb3a74aa277439e7caf119f2325bf8fc1f1d9f4a37c6c06870a4a26572b03bca856114f199243018f614369d7ebeee513f47467e048154407d9bc5b1301f15dd5816800533fd7b4f4fdcb9196289e337919ef31d9d5523e065f556a352fd1623161f80c22ad76cfcea33b81669f30535918626994a04b0a6cafdb49a012df107179c5662e95a0c9302a6dabdaf6bbfc16756168addca89b4f5034588b13abc11277d189218580e48e66216509a2e38c83c2488fd84a5fae08391b9b651e8530b170eaddf5e297e9a581b17b7e5703735e5b43a4fb42f8e29f988ad25bd33b87fca4a1c00beb06a3b1cbd729bc77af491ac2c79e82d5b4b337644148c1c823c31b18a8d758b8f5e04a9409d33af5f69c475c17f31a244c747e93d2f28c5bc02f60d8d3a5cbc1eaee4dcfe17edc2a9afbe6f4553096e429999729db2e4a5266e75a64c641cf0d857ce31a6cada89ee71787c665d9e8e59af3a42a841a84f2f414a56b3015821680535b604a37e9a52b694b02134e9906ec66a800848748cee44174dc87908b1d4c7e4b1b0d9d2426253943c8b1fcc545a94ffc2b012dcf39d1221b8ea25786f08908613cd1daeea2a19e0042be90211b1f775eaa3666e62f361bfea3963f16cc73ac3624a7472fdbc728c6b2ff103908b218e2f0a9e7fc40377fff39f496219e5dc2e6b4c815c3a482dedda77d4e3bf0a24e0f49b20fd01031217128927c1ade606e08c2a8d27906414f4596437b0b4dd5583552eec287abdcb9e65c5a1ba2c47647795a6a262b78dd052dc9a7a574aa4ea70f3339ddc983b4dd73641d7db48acce750947d0d4638b661fb17bd56edd0f1b6b82ffe7a2c0b07b4237c920f604e0c7ac9c1f7f75745f2b7476ee44af0948a33c3125700c3f642c2bf17c3e134e5bd228706ed6cdbe885d67a4ff3d32a3974b260d2f804b9f1c005ce993ee12c3102050545eb6cd95bad562e5a9f7d7656f25d1694d6e1970b5f2049c66843606b3a996b106200627f46ebe36276cb8f9eef0e4959e6987f8938b9e45394967e2ddf232b8338116686319ab29d516b2b31ba8085195aa90dee697ac535653a6d65abead6ff98641b256f47317fe3616d81c57e5ef85949296ee624dec3068eac7bdaff0d01675aae9e1fbd1cb2a9b13c1af5f3b9d508c89713e746c4e48d639102f4cf97e75fa4e8b40eb2e71a600d7f0c16c292c2f90f48a6eb2e52d623c94fb41e137c2c7a2aa77b5d8bba595eb148fc8087410f19361d570f329523f6a070398d32ceb39bb548be540c44983d3dbfb9d118dda42b1f2b2cb83539ce717bd4120c9ae228cfd0d27ac17796967ddd3785552b7bf2689bebf2753a41f6e170b09038f47e402149c7cd15b066041f23de5fca057ff43d92a5681e1dc2f706fd24675189020513afad028cc6d23c5d83ac2bf13f79a00266589f0f72f058d1c561624ec7504a0d3a5f798bc3c6cc62ce1579cfab21b43ec3c8886a160c3293af3e975828695b7476f6ff7bbad9561989b0ff35f380aeff2041ae3c59355270325fb31e1c1bdaa3851a8f31b93e4cf89416623027309b0ebc442c640653bc5e6d9e7d2e87abcbb44477d45c6feb7f4170a9e803549c0e41c87562488e0e4bc9c84d580de47536935011b7b597a6948b34823205447e64acc4bf19cef229a163479dd84df059d24944900fe270a371ed6f2cf3c8916861e4432d463c7f9c3e94e9359ff1a454dd684d4bbaedda066d78a72a4689a08c194882379081197b42e2c07104bf3f98d7d84309ef7de5d4888754f3d5140c4d5f4058fbaf77195de4ad1733ff3e6a9364ee28d5a4f5ccb527b66771b74ce92d627693e5afcf62f94ad00f9fcc0a109fad23a1ace2b826582659311f593783912cbce6c84dbe8f8685fc1711c57b8478c108731fe001a8494ba2c9e9c9c68d64f35076e3fb453e8abc14ea943c7fbdfeae748df18aedcefae6c3863ca0522627339cccd8b4025679ec194adaa8a42422f8f8c76d3ad7d025e2f4076460046dd2e9f7971a029eb5d89c48337c96ce4903bef3d50e88448a8ccccff3ca5a3cdc0e70123fdbe8c22b23a27fc811d88fbba5f95788301e9f820587505a0ce089f6087851eb79e15569d9e105dd8c018cbe2867177ba1a86ef4f10423c0e359f220d0e176256ff8ac794117a3365bf19f55aac894a1e19185eab30484ab56381ac90e09c016df33789ca656c65eb988da6bc858472d27f6d6eac5953f2c7f8064cb9dd1036fbcadc20519b7da44e999ecc936aa5767decf76286435cd055e891f4a256440799fc5c0c5ffaed76690354e638acb2e9bee1aae84f42d0302e2a57dc3890441cff70e6ff6f6bb22ac1d175500e7ba2e373bfc8ecd288d2e3e6d50d031919fc0e9cff9d2c7337ec2266e142fbe16673d9f1c27857e35ef13e409fb740491528935c0e01ccadfd4297217bcfc12920ff9b083870b02971903538350c09912dd82aaa9239c9be76ad74a46616d3c4f857e2e42ccd0ecc97c81e28882581449f754d0094d31b886ed63fd6c16ec7711beb8acfe5c6c8ef3eb71a906a72d7d7a0e3b6ea09996b37b23c431e50f00e8d0fcc607385d75a30884a44e0221da504a516b1025eaa36be97e9eb76a42074d07a245b8a2f1c981792e4c638b4afc74b02c8932720f378f9291f0d7792e9251145e504727cdd2f3d20b4ed03487a3ca06d042c6841c882d55eb0b4955ad627faedb9357489c465ded4eb2268614f18654bd106ac1c72d4600a6ee5ed6c9225b3557a36970cf05064000f081fcfaa02f2b95b007ba7f9ed884d6b2e17b5dfd1f44e49f98913c07c66b317a2fca1a7b95895e717aecd2a84b576ad443af7236d6df70efe54b9gregkh@google.com >
2024-07-01 09:55:11 +00:00
Todd Kjos
76d91af9da
ANDROID: fix kernelci build breaks due to hid/uhid cyclic dependency
...
An android-only patch to work around frozen KMI for android14 kernels
allows a dependency between hid and uhid if both modules are enabled:
if (IS_ENABLED(CONFIG_UHID) && parser->device->ll_driver == &uhid_hid_driver)
max_buffer_size = UHID_DATA_MAX;
For allmodconfig builds, both hid and uhid are modules so this creates
a cyclic dependancy and we see this error in kernelci tests:
ERROR: Cycle detected: hid -> uhid -> hid
Fix by changeing to IS_BUILTIN() instead of IS_ENABLED() since Android
builds always build uhid into the core kernel.
Fixes: 7668cef283tkjos@google.com >
Change-Id: I622466a42ad94e3606820cf506188bd679078cbf
2024-06-29 19:55:29 +00:00
Todd Kjos
c2dad37627
ANDROID: fix kernelci GCC builds of fips140.ko
...
GCC builds of fips140.ko all fail with these errors. This causes
allmodconfig builds to fail in kernelci.
aarch64-linux-gnu-objcopy: crypto/fips140.ko:
can't dump section '.rela.rodata'
- it does not exist: file format not recognized
Since the Android use-cases for fips140 are clang only, suppress
fips140.ko builds for GCC
Bug: 350087876
Signed-off-by: Todd Kjos <tkjos@google.com >
Change-Id: I742d19bc5172d43a19acd48a248bc2a194f67ca2
2024-06-28 23:05:20 +00:00
Pierre Gondois
8bffcfee7a
UPSTREAM: sched/fair: Use all little CPUs for CPU-bound workloads
...
Running N CPU-bound tasks on an N CPUs platform:
- with asymmetric CPU capacity
- not being a DynamIq system (i.e. having a PKG level sched domain
without the SD_SHARE_PKG_RESOURCES flag set)
.. might result in a task placement where two tasks run on a big CPU
and none on a little CPU. This placement could be more optimal by
using all CPUs.
Testing platform:
Juno-r2:
- 2 big CPUs (1-2), maximum capacity of 1024
- 4 little CPUs (0,3-5), maximum capacity of 383
Testing workload ([1]):
Spawn 6 CPU-bound tasks. During the first 100ms (step 1), each tasks
is affine to a CPU, except for:
- one little CPU which is left idle.
- one big CPU which has 2 tasks affine.
After the 100ms (step 2), remove the cpumask affinity.
Behavior before the patch:
During step 2, the load balancer running from the idle CPU tags sched
domains as:
- little CPUs: 'group_has_spare'. Cf. group_has_capacity() and
group_is_overloaded(), 3 CPU-bound tasks run on a 4 CPUs
sched-domain, and the idle CPU provides enough spare capacity
regarding the imbalance_pct
- big CPUs: 'group_overloaded'. Indeed, 3 tasks run on a 2 CPUs
sched-domain, so the following path is used:
group_is_overloaded()
\-if (sgs->sum_nr_running <= sgs->group_weight) return true;
The following path which would change the migration type to
'migrate_task' is not taken:
calculate_imbalance()
\-if (env->idle != CPU_NOT_IDLE && env->imbalance == 0)
as the local group has some spare capacity, so the imbalance
is not 0.
The migration type requested is 'migrate_util' and the busiest
runqueue is the big CPU's runqueue having 2 tasks (each having a
utilization of 512). The idle little CPU cannot pull one of these
task as its capacity is too small for the task. The following path
is used:
detach_tasks()
\-case migrate_util:
\-if (util > env->imbalance) goto next;
After the patch:
As the number of failed balancing attempts grows (with
'nr_balance_failed'), progressively make it easier to migrate
a big task to the idling little CPU. A similar mechanism is
used for the 'migrate_load' migration type.
Improvement:
Running the testing workload [1] with the step 2 representing
a ~10s load for a big CPU:
Before patch: ~19.3s
After patch: ~18s (-6.7%)
Similar issue reported at:
https://lore.kernel.org/lkml/20230716014125.139577-1-qyousef@layalina.io/
Suggested-by: Vincent Guittot <vincent.guittot@linaro.org >
Signed-off-by: Pierre Gondois <pierre.gondois@arm.com >
Signed-off-by: Ingo Molnar <mingo@kernel.org >
Reviewed-by: Vincent Guittot <vincent.guittot@linaro.org >
Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com >
Acked-by: Qais Yousef <qyousef@layalina.io >
Link: https://lore.kernel.org/r/20231206090043.634697-1-pierre.gondois@arm.com
(cherry picked from commit 3af7524b14198f5159a86692d57a9f28ec9375ce)
Change-Id: I916aa7e56af6addf0eb3a78ec77119324172d9d9
Signed-off-by: John Stultz <jstultz@google.com >
2024-06-28 22:50:37 +00:00
Anton Altaparmakov
a1926c3f2b
ANDROID: GKI: Extend Tuxera symbol list
...
This list covers Tuxera HFS+ file system driver.
16 function symbol(s) added
'int _atomic_dec_and_lock(atomic_t*, spinlock_t*)'
'int blkdev_issue_zeroout(struct block_device*, sector_t, sector_t, gfp_t, unsigned int)'
'int cont_write_begin(struct file*, struct address_space*, loff_t, unsigned int, struct page**, void**, get_block_t*, loff_t*)'
'void fileattr_fill_flags(struct fileattr*, u32)'
'bool filemap_release_folio(struct folio*, gfp_t)'
'int generic_cont_expand_simple(struct inode*, loff_t)'
'struct inode* iget_locked(struct super_block*, unsigned long)'
'void inode_add_bytes(struct inode*, loff_t)'
'struct timespec64 inode_set_ctime_current(struct inode*)'
'int match_octal(substring_t*, int*)'
'char* match_strdup(const substring_t*)'
'int migrate_folio(struct address_space*, struct folio*, struct folio*, enum migrate_mode)'
'const char* page_get_link(struct dentry*, struct inode*, struct delayed_call*)'
'int page_symlink(struct inode*, const char*, int)'
'bool try_to_free_buffers(struct folio*)'
'int utf32_to_utf8(unicode_t, u8*, int)'
1 variable symbol(s) added
'unsigned int dirty_writeback_interval'
Bug: 349994203
Change-Id: Idd44e7c08a223772312d63a0c814616361b15437
Signed-off-by: Anton Altaparmakov <anton@tuxera.com >
2024-06-28 21:08:17 +01:00
John Stultz
6aaa06c15d
FROMLIST: locking/rwsem: Add __always_inline annotation to __down_write_common() and inlined callers
...
Apparently despite it being marked inline, the compiler
may not inline __down_write_common() which makes it difficult
to identify the cause of lock contention, as the wchan of the
blocked function will always be listed as __down_write_common().
So add __always_inline annotation to the common function (as
well as the inlined helper callers) to force it to be inlined
so a more useful blocking function will be listed (via wchan).
This mirrors commit 92cc5d00a4timmurray@google.com >
Cc: Nick Desaulniers <ndesaulniers@google.com >
Cc: Peter Zijlstra <peterz@infradead.org >
Cc: Ingo Molnar <mingo@redhat.com >
Cc: Will Deacon <will@kernel.org >
Cc: Waiman Long <longman@redhat.com >
Cc: Boqun Feng <boqun.feng@gmail.com >
Cc: kernel-team@android.com
Fixes: c995e638cctimmurray@google.com >
Acked-by: Waiman Long <longman@redhat.com >
Change-Id: I72b273149577b8125ea3a5053befbd5cf66bf8ad
Signed-off-by: John Stultz <jstultz@google.com >
Link: https://lore.kernel.org/lkml/20240620174204.1802235-1-jstultz@google.com/
Bug: 332722989
---
v2:
* Add ack tags & minor tweaks to commit message
2024-06-28 16:25:32 +00:00
Eric Biggers
7682e638eb
ANDROID: fips140: remove unnecessary no_sanitize(cfi)
...
gcc segfaults when compiling fips140-module.c because it doesn't like
__attribute__((__no_sanitize__("cfi"))) on fips140_init(). But since
Linux's CFI now uses the kcfi sanitizer instead of cfi, this no
attribute longer did anything anyway. Remove it.
fips140_init() does work with kcfi, though this relies on the initcall
function pointers being typed correctly. They were correct, but for
futureproofing also make it use initcall_t from <linux/init.h>.
Bug: 349612732
Change-Id: Ic5cfaef177b58abf21f1737579d75b4df4d0d09c
Signed-off-by: Eric Biggers <ebiggers@google.com >
2024-06-27 21:04:34 +00:00
Xiaofeng Yuan
681c91500c
ANDROID: GKI: Add symbol to symbol list for vivo.
...
5 function symbol(s) added
'int __traceiter_android_vh_do_anonymous_page(void*, struct vm_area_struct*, struct page*)'
'int __traceiter_android_vh_do_swap_page(void*, struct folio*, pte_t*, struct vm_fault*, swp_entry_t)'
'int __traceiter_android_vh_do_wp_page(void*, struct folio*)'
'int __traceiter_android_vh_shmem_swapin_folio(void*, struct folio*)'
'int __traceiter_android_vh_uprobes_replace_page(void*, struct folio*, struct folio*)'
5 variable symbol(s) added
'struct tracepoint __tracepoint_android_vh_do_anonymous_page'
'struct tracepoint __tracepoint_android_vh_do_swap_page'
'struct tracepoint __tracepoint_android_vh_do_wp_page'
'struct tracepoint __tracepoint_android_vh_shmem_swapin_folio'
'struct tracepoint __tracepoint_android_vh_uprobes_replace_page'
Bug: 336964184
Change-Id: Ie2364fba2569d2514e77eb4fc450c343d8cd4a94
Signed-off-by: Xiaofeng Yuan <yuanxiaofeng@vivo.com >
2024-06-27 19:02:20 +00:00
Tiffany Yang