Rui Chen
dbb9fda3cf
ANDROID: fs: add vendor hook to collect IO statistics
...
Add vendor hook to get metainfo of direct/buffered read and write.
Determine hot files in each performance-sensitive user scenario.
Bug: 380502059
Change-Id: Ie7604852df637d6664afd72e87bd6d4b14bbc2a2
Signed-off-by: Rui Chen <chenrui9@honor.com >
2024-12-12 13:12:30 -08:00
Udipto Goswami
b9ba16d91d
UPSTREAM: usb: xhci: Implement xhci_handshake_check_state() helper
...
In some situations where xhci removal happens parallel to xhci_handshake,
we encounter a scenario where the xhci_handshake can't succeed, and it
polls until timeout.
If xhci_handshake runs until timeout it can on some platforms result in
a long wait which might lead to a watchdog timeout.
Add a helper that checks xhci status during the handshake, and exits if
set state is entered. Use this helper in places where xhci_handshake is
called unlocked and has a long timeout. For example xhci command timeout
and xhci reset.
[commit message and code comment rewording -Mathias]
Signed-off-by: Udipto Goswami <quic_ugoswami@quicinc.com >
Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com >
Link: https://lore.kernel.org/r/20231019102924.2797346-18-mathias.nyman@linux.intel.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Bug: 383443034
Change-Id: Iec54af32dcf6b07075e3f084dba914fc43635ee6
(cherry picked from commit 6ccb83d6c4972ebe6ae49de5eba051de3638362c)
Signed-off-by: Faisal Hassan <quic_faisalh@quicinc.com >
2024-12-11 12:49:35 -08:00
Todd Kjos
191acd0d6a
Revert "UPSTREAM: unicode: Don't special case ignorable code points"
...
This reverts commit 62bbb08add179b68e2ce0ede59f3c4b37d6c92a8.
Reason for revert: b/382800956
Bug: 382800956
Change-Id: Ic7a0cdbb060c12c1628a5859d795e78cd6b9341d
Signed-off-by: Todd Kjos <tkjos@google.com >
(cherry picked from commit c376628415656f16d398aad95c218a06805038bd)
Signed-off-by: Lee Jones <joneslee@google.com >
2024-12-11 18:44:17 +00:00
Todd Kjos
0a310649d8
Reapply "UPSTREAM: unicode: Don't special case ignorable code points"
...
This reverts commit e1ba90026d98e53f5736131f3363424e83315f00.
Reapplying only to re-revert with the correct Change-Id
Bug: 382800956
Signed-off-by: Todd Kjos <tkjos@google.com >
Change-Id: Icdd08040f04ed7e85d31b7f8551ee2ef1d0b95b0
2024-12-11 18:21:53 +00:00
meixie
e318dc4c06
ANDROID: abi_gki_aarch64_qcom: Update symbols list for Qcom
...
Update symbols list for Qcom
Symbols added:
default_qdisc_ops
dev_activate
dev_deactivate
dev_graft_qdisc
gnet_stats_add_basic
gnet_stats_add_queue
gnet_stats_basic_sync_init
gnet_stats_copy_basic
gnet_stats_copy_queue
mq_change_real_num_tx
netdev_txq_to_tc
noop_qdisc
pfifo_fast_ops
pfifo_qdisc_ops
qdisc_create_dflt
qdisc_hash_add
qdisc_put
qdisc_reset
qdisc_tree_reduce_backlog
qdisc_watchdog_cancel
qdisc_watchdog_init
qdisc_watchdog_init_clockid
qdisc_watchdog_schedule_range_ns
rtnl_kfree_skbs
sock_queue_err_skb
Bug: 369460491
Change-Id: I1d0b22f03250d3c33d6fd23cf02f6d014444a2b4
Signed-off-by: meixie <quic_meixie@quicinc.com >
2024-12-11 08:08:21 -08:00
Todd Kjos
904ebc320c
Revert "UPSTREAM: unicode: Don't special case ignorable code points"
...
This reverts commit 8097478ae8tkjos@google.com >
2024-12-11 01:17:34 +00:00
Vincent Donnefort
0f332d7edc
ANDROID: KVM: arm64: Fix missing mutex init for hyp trace readers
...
Prevent the kernel from crashing when using the hypervisor tracing.
While bringing locking for the nVHE hyp tracing readers, init has been
omitted. This resulted in a stack trace with the following signature
when tracing was enabled:
[ 85.897294][ T6772] Call trace:
[ 85.900420][ T6772] __list_add_valid+0x78/0xbc
[ 85.904937][ T6772] __mutex_add_waiter+0x54/0x138
[ 85.909711][ T6772] __mutex_lock+0x344/0xdac
[ 85.914054][ T6772] __mutex_lock_slowpath+0x14/0x24
[ 85.919003][ T6772] mutex_lock+0x40/0xec
[ 85.922998][ T6772] hyp_trace_pipe_read+0x37c/0x418
[ 85.927948][ T6772] vfs_read+0x100/0x2c0
[ 85.931942][ T6772] ksys_read+0x78/0xe8
[ 85.935850][ T6772] __arm64_sys_read+0x1c/0x2c
[ 85.940367][ T6772] invoke_syscall+0x58/0x11c
[ 85.944794][ T6772] el0_svc_common+0xb4/0xf4
[ 85.949137][ T6772] do_el0_svc+0x2c/0xb0
[ 85.953132][ T6772] el0_svc+0x2c/0x90
[ 85.956865][ T6772] el0t_64_sync_handler+0x68/0xb4
[ 85.961728][ T6772] el0t_64_sync+0x1a4/0x1a8
[ 85.966072][ T6772] Code: d4210000 d0007080 91271c00 9423d9aa
Bug: 229972309
Bug: 380818540
Test: enable hypervisor tracing per-cpu and fetch hyp events
Fixes: 34305ad4b1vdonnefort@google.com >
Signed-off-by: Sebastian Ene <sebastianene@google.com >
2024-12-10 13:41:18 +00:00
yipeng xiang
affd0c0263
ANDROID: mm: EXPORT_SYMBOL_GPL(reclaim_pages) position adjustment
...
EXPORT_SYMBOL_GPL(reclaim_pages) should follow reclaim_pages, not __reclaim_pages.
Bug: 365902592
Change-Id: Ieb1b991e40c8893af679fc3c3d711cd0ae049c9c
Signed-off-by: yipeng xiang <yipengxiang@honor.corp-partner.google.com >
2024-12-09 23:59:03 +00:00
Seiya Wang
d8ccecb7c2
ANDROID: GKI: Update symbol list for mtk
...
1 function symbol(s) added
'unsigned int tty_buffer_space_avail(struct tty_port*)'
Bug: 383039133
Change-Id: Ic92096ecc482c120b8cda325a7f2ae44f99e8527
Signed-off-by: Seiya Wang <seiya.wang@mediatek.com >
2024-12-09 17:28:05 +00:00
Jiri Kosina
853ec04e2d
UPSTREAM: HID: core: zero-initialize the report buffer
...
[ Upstream commit 177f25d1292c7e16e1199b39c85480f7f8815552 ]
Since the report buffer is used by all kinds of drivers in various ways, let's
zero-initialize it during allocation to make sure that it can't be ever used
to leak kernel memory via specially-crafted report.
Bug: 380395346
Fixes: 27ce405039bsevens@google.com >
Acked-by: Benjamin Tissoires <bentiss@kernel.org >
Signed-off-by: Jiri Kosina <jkosina@suse.com >
Signed-off-by: Sasha Levin <sashal@kernel.org >
(cherry picked from commit 9d9f5c75c0joneslee@google.com >
Change-Id: I31f64f2745347137bbc415eb35b7fab5761867f3
2024-12-09 12:10:24 +00:00
Seiya Wang
c276c53965
ANDROID: GKI: Update symbol list for mtk
...
1 function symbol(s) added
'int snd_pcm_format_set_silence(snd_pcm_format_t, void*, unsigned int)'
Bug: 382303912
Signed-off-by: Seiya Wang <seiya.wang@mediatek.com >
Change-Id: I7de7c367b52114b9770697cf3eaeb47008a0e52b
2024-12-06 13:04:12 +00:00
Saravana Kannan
fddf80a6ac
UPSTREAM: of: property: fw_devlink: Add support for "post-init-providers" property
...
Add support for this property so that dependency cycles can be broken and
fw_devlink can do better probe/suspend/resume ordering between devices in a
dependency cycle.
Signed-off-by: Saravana Kannan <saravanak@google.com >
Acked-by: "Rafael J. Wysocki" <rafael@kernel.org >
Reviewed-by: Rob Herring <robh@kernel.org >
Link: https://lore.kernel.org/r/20240305050458.1400667-4-saravanak@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
(cherry picked from commit 135116f3d01402b610e00dd54f3b059a3faf35de)
Change-Id: I49e29a38ebc5b0a663d8d336512be1b56ca607c7
Bug: 347344057
2024-12-06 01:31:16 +00:00
Saravana Kannan
b865d3ed06
UPSTREAM: driver core: Add FWLINK_FLAG_IGNORE to completely ignore a fwnode link
...
A fwnode link between specific supplier-consumer fwnodes can be added
multiple times for multiple reasons. If that dependency doesn't exist,
deleting the fwnode link once doesn't guarantee that it won't get created
again.
So, add FWLINK_FLAG_IGNORE flag to mark a fwnode link as one that needs to
be completely ignored. Since a fwnode link's flags is an OR of all the
flags passed to all the fwnode_link_add() calls to create that specific
fwnode link, the FWLINK_FLAG_IGNORE flag is preserved and can be used to
mark a fwnode link as on that need to be completely ignored until it is
deleted.
Signed-off-by: Saravana Kannan <saravanak@google.com >
Acked-by: "Rafael J. Wysocki" <rafael@kernel.org >
Reviewed-by: Rob Herring <robh@kernel.org >
Link: https://lore.kernel.org/r/20240305050458.1400667-3-saravanak@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
(cherry picked from commit b7e1241d8f77ed64404a5e4450f43a319310fc91)
Change-Id: If9cbc4adf796816a6c04de049d57d7a5d0858e27
Bug: 347344057
2024-12-06 01:31:16 +00:00
Saravana Kannan
0a05df9c8a
UPSTREAM: driver core: Adds flags param to fwnode_link_add()
...
Allow the callers to set fwnode link flags when adding fwnode links.
Signed-off-by: Saravana Kannan <saravanak@google.com >
Acked-by: "Rafael J. Wysocki" <rafael@kernel.org >
Reviewed-by: Rob Herring <robh@kernel.org >
Link: https://lore.kernel.org/r/20240305050458.1400667-2-saravanak@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
(cherry picked from commit 75cde56a5b504d07a64ce0e3f8c7410df70308a3)
Change-Id: Idb03ec39da06d58052cd8080d39c2efe0ad9d3af
Bug: 347344057
2024-12-06 01:31:16 +00:00
Qi Han
182b090f35
UPSTREAM: f2fs: modify f2fs_is_checkpoint_ready logic to allow more data to be written with the CP disable
...
When the free segment is used up during CP disable, many write or
ioctl operations will get ENOSPC error codes, even if there are
still many blocks available. We can reproduce it in the following
steps:
dd if=/dev/zero of=f2fs.img bs=1M count=65
mkfs.f2fs -f f2fs.img
mount f2fs.img f2fs_dir -o checkpoint=disable:10%
cd f2fs_dir
i=1 ; while [[ $i -lt 50 ]] ; do (file_name=./2M_file$i ; dd \
if=/dev/random of=$file_name bs=1M count=2); i=$((i+1)); done
sync
i=1 ; while [[ $i -lt 50 ]] ; do (file_name=./2M_file$i ; truncate \
-s 1K $file_name); i=$((i+1)); done
sync
dd if=/dev/zero of=./file bs=1M count=20
In f2fs_need_SSR() function, it is allowed to use SSR to allocate
blocks when CP is disabled, so in f2fs_is_checkpoint_ready function,
can we judge the number of invalid blocks when free segment is not
enough, and return ENOSPC only if the number of invalid blocks is
also not enough.
Signed-off-by: Qi Han <hanqi@vivo.com >
Reviewed-by: Chao Yu <chao@kernel.org >
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org >
(cherry picked from commit 84b5bb8bf0f6a78c232a20c2eecdbb8112ac2703)
Signed-off-by: Daniel Rosenberg <drosen@google.com >
(cherry picked from https://android-review.googlesource.com/q/commit:225caf3bdf7a4977ae50ba9b5c5470a16d480100 )
Merged-In: I41ad315f603cd764d0e9b8ef984447e7116b1514
Change-Id: I41ad315f603cd764d0e9b8ef984447e7116b1514
2024-12-05 01:19:03 +00:00
Chao Yu
38149d5303
BACKPORT: f2fs: introduce get_available_block_count() for cleanup
...
There are very similar codes in inc_valid_block_count() and
inc_valid_node_count() which is used for available user block
count calculation.
This patch introduces a new helper get_available_block_count()
to include those common codes, and used it to clean up codes.
Change-Id: Ie2ce55bdac091bc4880478eeba2a76e1608726e3
Signed-off-by: Chao Yu <chao@kernel.org >
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org >
(cherry picked from commit 0f1c6ede6da9f7c5dd7380b74a64850298279168)
[Added line for F2FS_IO_ALIGNED, which was removed in later kernels]
Signed-off-by: Daniel Rosenberg <drosen@google.com >
2024-12-05 01:18:53 +00:00
Mukesh Ojha
997d1e6f69
FROMGIT: pinmux: Use sequential access to access desc->pinmux data
...
When two client of the same gpio call pinctrl_select_state() for the
same functionality, we are seeing NULL pointer issue while accessing
desc->mux_owner.
Let's say two processes A, B executing in pin_request() for the same pin
and process A updates the desc->mux_usecount but not yet updated the
desc->mux_owner while process B see the desc->mux_usecount which got
updated by A path and further executes strcmp and while accessing
desc->mux_owner it crashes with NULL pointer.
Serialize the access to mux related setting with a mutex lock.
cpu0 (process A) cpu1(process B)
pinctrl_select_state() { pinctrl_select_state() {
pin_request() { pin_request() {
...
....
} else {
desc->mux_usecount++;
desc->mux_usecount && strcmp(desc->mux_owner, owner)) {
if (desc->mux_usecount > 1)
return 0;
desc->mux_owner = owner;
} }
Bug: 376023321
Bug: 381832937
Link: https://lore.kernel.org/lkml/20241014192930.1539673-1-quic_mojha@quicinc.com/
Signed-off-by: Mukesh Ojha <quic_mojha@quicinc.com >
(cherry picked from commit 5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git for-next)
Change-Id: Ib417544f0dcc5174d6f9b01d0243c19162f82fff
Signed-off-by: Mukesh Ojha <quic_mojha@quicinc.com >
Signed-off-by: Srinivasarao Pathipati <quic_c_spathi@quicinc.com >
2024-12-02 22:09:46 +00:00
Florian Fainelli
fa34bcaf9e
BACKPORT: firmware: arm_scmi: Support 'reg-io-width' property for shared memory
...
Some shared memory areas might only support a certain access width,
such as 32-bit, which memcpy_{from,to}_io() does not adhere to at least
on ARM64 by making both 8-bit and 64-bit accesses to such memory.
Update the shmem layer to support reading from and writing to such
shared memory area using the specified I/O width in the Device Tree. The
various transport layers making use of the shmem.c code are updated
accordingly to pass the I/O accessors that they store.
Bug: 369085303
Change-Id: I97d80dd4027fe8290781ad7fc3859c2bdaf34522
Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com >
Message-Id: <20240827182450.3608307-3-florian.fainelli@broadcom.com >
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com >
(cherry picked from commit 2cd7f3db25feeb7c204e36df9f1bb13bea3a3a20)
Signed-off-by: Danesh Petigara <danesh.petigara@broadcom.com >
Signed-off-by: Pierre Couillaud <pierre@broadcom.com >
2024-12-02 20:18:26 +00:00
Florian Fainelli
c9e7fc262f
UPSTREAM: dt-bindings: sram: Document reg-io-width property
...
Some SRAMs need to be accessed with a specific access width, define
the 'reg-io-width' property specifying such access sizes.
Bug: 369085303
Change-Id: I8848088221053fbd462d4f7310fffab861944879
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org >
Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com >
Message-Id: <20240827182450.3608307-2-florian.fainelli@broadcom.com >
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com >
(cherry picked from commit 14b2157a9c14481c3b967d8d1a95972bf885fb88)
Signed-off-by: Danesh Petigara <danesh.petigara@broadcom.com >
Signed-off-by: Pierre Couillaud <pierre@broadcom.com >
2024-12-02 20:18:26 +00:00
Seiya Wang
cdea241bf6
ANDROID: GKI: Update symbol list for mtk
...
5 function symbol(s) added
'void* devm_memremap_pages(struct device*, struct dev_pagemap*)'
'int rproc_detach(struct rproc*)'
'struct socket* tun_get_socket(struct file*)'
'struct ptr_ring* tun_get_tx_ring(struct file*)'
'void tun_ptr_free(void*)'
Bug: 381284575
Signed-off-by: Seiya Wang <seiya.wang@mediatek.com >
Change-Id: I593a5dd82f5b7fde7bb3ebbd74fead839fcfdf9f
2024-12-02 18:43:37 +00:00
Quentin Perret
a887a44ace
ANDROID: KVM: arm64: Always check state from host_ack_unshare()
...
Similar to how we failed to cross-check the state from the completer's
PoV on the hyp_ack_unshare() path, we fail to do so from
host_ack_unshare().
This shouldn't cause problems in practice as this can only be called on
the guest_unshare_host() path, and guest currently don't have the
ability to share their pages with anybody other than the host. But this
again is rather fragile, so let's simply do the proper check -- it isn't
very costly thanks to the hyp_vmemmap optimisation.
Bug: 381409114
Change-Id: I3770b7db55c579758863e41f50ab30f6a8bb4a0c
Signed-off-by: Quentin Perret <qperret@google.com >
2024-11-29 10:43:14 +00:00
Quentin Perret
fb69bae8ea
FROMLIST: KVM: arm64: Always check the state from hyp_ack_unshare()
...
There are multiple pKVM memory transitions where the state of a page is
not cross-checked from the completer's PoV for performance reasons.
For example, if a page is PKVM_PAGE_OWNED from the initiator's PoV,
we should be guaranteed by construction that it is PKVM_NOPAGE for
everybody else, hence allowing us to save a page-table lookup.
When it was introduced, hyp_ack_unshare() followed that logic and bailed
out without checking the PKVM_PAGE_SHARED_BORROWED state in the
hypervisor's stage-1. This was correct as we could safely assume that
all host-initiated shares were directed at the hypervisor at the time.
But with the introduction of other types of shares (e.g. for FF-A or
non-protected guests), it is now very much required to cross check this
state to prevent the host from running __pkvm_host_unshare_hyp() on a
page shared with TZ or a non-protected guest.
Thankfully, if an attacker were to try this, the hyp_unmap() call from
hyp_complete_unshare() would fail, hence causing to WARN() from
__do_unshare() with the host lock held, which is fatal. But this is
fragile at best, and can hardly be considered a security measure.
Let's just do the right thing and always check the state from
hyp_ack_unshare().
Bug: 381409114
Link: https://lore.kernel.org/kvmarm/20241128154406.602875-1-qperret@google.com/
Change-Id: Id3bbd1fc3c75df506b0919f4d6f7be74b6f013f3
Signed-off-by: Quentin Perret <qperret@google.com >
2024-11-29 10:42:31 +00:00
Greg Kroah-Hartman
bfad6b019c
Merge tag 'android14-6.1.115_r00' into android14-6.1
...
Merge up to the 6.1.115 LTS release into android14-6.1. Changes in here
include:
* 47a8b5f3ed0d968ced730d968ced73500bbbbd01241398329a241398329aad46e48e1bb5dc5b7de7b5dc5b7de7f70f79522724aed1b46202ab44d3c125fe64922f235eaacf5cd1b2d786e523304adf2971f14a9f5c25326b9c1358c7f44c7b55d01b652ef51343f346ccbc10647a23f9cef17eba392e13556cc23898e68f6cd4d5bb92d847a35e042ef81f6fb12b0948fb88f8093a2a6bc6ac81ed1bdd6270ea93bb7700b7cf7ee2291d102c4e58695b966c61928ffba8d917b946e7b4473c39d486bd22713dcf33e479e547e314a23e15a5c8e7d3b72e7c5a0c17150ef5f10d831b6bc5f72123039b4aafbc795bc1aa58d24f6b51aac8f6711bfdd1ee0ae1df9552f2727c20cf5eb5c5316d04a90df5dc7d73bdbc96c231bdbc96c231a01987cd90aa56ea3b7deb4c6fe20a50c2cffdcf6dffd7067da566b71fedd321732352d321732352d8f298eb66637edb1156f068284cf13067fd9c8aa84978a9cd5d9054b9f74f7b586aaecb7c388b59a035df0b98bcba86e03b580b3189c188bc4fe48b72c0f482e3a3ff23f7c3872932cf75618ee79e8164d63557dea9faac881876210223c214b45fa0cec466415717a419868e8ed01040d82b45eed27b88dd7a6c914c1159e77ccfc22c748834ce87f724047f9b58a64628327558b21f633ac7df731451a16af267bcb22e6c3d838783380bcd5aa8bb558c55a5c5efbe731b3aee75909fd82cacc625ca7ef58ce4bfff915c97535085db57983df5e9ef56f28f2269fae9c0cd1a45a7ce8a2ba332a3d23d7c15117f94bce1afaa21354b3847ea2c3766fac9fc35bb2e1fe19bf49e9061b8628cbbd7b5876a6e82510939715660bcc4dd4faa6e3e66dc2ad8e8819bb6ec117522aba100699df62691d36876793907958f8343f427524f656271edf620e38ce081ad84e7f56a30c5cd67af3c17deee4bd7138a43e8aed9bc5085816eff2a9c402931b55b2be4796adf538dd2826873db02753a9010a116e7c3347a5c653ede876ac72d539ddda5d9675f063bbf1e3216a2bd61fe371f0840b72b1b4c9ed9edc3428c114f41279491b82cf827628e82e2701af2abd3429683804e366ee5a1b7ce549f61968109ce491112d48de29a701ba9c6fc9f4c5f170ef41a17a4ac2d681fa845cc3094585b5ff4ed40d1c6d52ac941fea67d4a02bfeb3710effffa001d7e2cd71a2d54fb72e445df65487b24136d908263286e95124c5429a548f8773e7458a6cdae3dfd7278730bdf77be235258c70d0be1e87568a204de065652376d15bad785ca88f931e0deb60b16e36d975b04fa6e2ee414193749e04e158833b519ec9b9654594049dee8983121da179f14841bb7a563f9dae76382da3aedc99c661caba1e58fb7ddbad1606090bb18c8ea940d5cd775efbb03015b6329318ca89bc5bee1b68cb82ef632bfb8895ab72942b3262e13e230e0906e0dae53d09f115071beb59e96972e08b7f9f7c872df2d026274cd218a0a49eaa35ab8275657419aaead533d2f30aef1ed2bded851ecd8e4a23e7b6d8c5824973f4b6436ee799f41a0c86f17fcafb2159b78a2458411a033053d901fe8e9f2a12a4a14351a472cbcac6db8ea701c1849ff80a98104081901129863ce626d98d22eca03990e5b2abae021dc97d508ea45f1e87c81b23c8bb53e220b6f53c947b337e5eb485fbdc2dcc0685ab4057b1165eb42ef45fee376dd679c3b9dacff209b616e935d8aa778fbe087314dbee9fe64f3b66c995eb34999d1db64cb409e4d5ecb6e037ec6f9fa3dd285ba6f227089811e2027bbab47ad9470ac9786270a6f9df36999328f2aba8e65814eb2a4a2dad364b12b061c0a4d4dbef64a81800ef0bf171b5e8643778de19d7f06caaae025636317e5cf9f26994cfca048f222d24a0b1a309a6a518a9e62d9b2ee0b894eee6f6a8a3dc841e38dfea4be20fa4b832c5a9ec4db1b184af7ba39a1fec9ec7dd95501bd8c133e074e9336ee5192e144cdfc07bbf80ee119cf7dbcb90518ccf8660a0b243d96aec20cf07f204deb104c86fd4499d29d05ffc978026869dc79c24e58d18dba06f93a3b2a29d0c3cd27d85f7de759fceaabb1c50afab5e900a361231ced8a17e4f2043985e6f0abe6f172ec8fc23ebc114b2a046328b4891bab09afbaeb1ef44fb30b132800e37bcbfa3a83eb2219e5f9727c7874977deff23e59b7031f06fd756ec0fe3756f9ecda20889ca0d4513a831e19e565a031434243bae792617a27abbde44b4486ec941763b0c94992097d24d5e7701cabd26a15b4182497940fd9d7fc32467238b11a086d4dae221aed91464e52300d9cd2e664c667ecf68d16c71e5f5341210f7fd7459431f1ca5c4f9616d00140a4265251e7507ab6a5be0621e30fd85f503315e19353fb8225da3343bc085014a7c916a9839c37fdb37de9491f12cf028381edae6e6e3d54d90d17e82da76b4d08de0456460f7c21e98539a3be0202945ea0b7af388608196a15614bfb20509c4198dfdc409b7af29735668f8ec83b196f47595f03a7f601b7d22a79ffcd2b08a6de71cc4492873afeceda8575452da51e0c9e9a3a48957d6a2f28192d1b8d7a97c900e55c1132e01090759e9e87adc619e923b3a925279e5a4cd9c5a0fc80faf6afeb9fae1a346f3287c0a8d74fbe3fca85a2bb0c5d005005e2e159af017667ad2d07a38ec9ff5e0f8953ce249a4c68d66c612c40438c8d7dfd317c4c68ee70c5eb7f38ca877f130b8f5ad212f48f5ad212f41aea6c05770f6dcaf4cd8f482bb7e2d90aa3b1e7f27c9aabfc5de0b8ca7c5de0b8ca7c8409539dbbb541831a5d76feedc74b6a39c8f5c89a9747288b94438143fe75aa45ece3563550b619bc16154fde40081f2107deec6368c0c43068b25522deeb6a70e4340fef882a2d6b24f0b4ab78f4ad49c0fbd5e730c3d3d9b7ced98072d36e39646d7a78ed917133ed36591af2dc566bf54bc1944b4253632344b9efae315bcc308ef4af06717cfc972acb4d9f717a6ffc2f4a5a71fc2f4a5a71de3120b8f2889304120e8266ae6eaf97a79933fb0857b1c57378fa420e23b80d8c2c55737e75df3a6dad158fbb6a5ca0ab944dab65aafbb52f1fbb06c66562408c4d49102c240a27f6cb3b11ceb17e6f1d750606fe9496004146ea15b254ad0a2cfe7a893ae45be849a2493904e9b6fdfd6f8da4babb895c7600bc3a689af86455eb1d4359411db5d407666490be6ffc6ae80eadb360ec5b06acbe2a9237e80d07d3db8105a521ff2141ff83a68a27beff507e9ebeff507e9e2d1f7543294061e07f04d730f53bf593c574989c5ff787ebd039b5ecc927bc26503532b2e1167d219fcade799cec84214a34609bdfae6f3a38e30849345788c46454adbacfa1bfe95355a65a708abb7db942e1b572e6cdd72aa5aba6841a6c4d9a5864c35c6cfbc539e780662c8cb8421b2a3d8e1cb8b75d86872f5a7671e1a9912f4d58b0e90d21526498d2a23f0ea8ddbea229ba8bacebeb375face9c778a2ec134c185538c5618390351912b9d67b33d69a08808ccede872544abf6b6ca1fb7942afc474e3fa0d01053f910fe44b3bfbfaffd54d4f4d47234b07ecfecad07c14fab87aa793e166c0121928aed032a3c80f64414fb4c3e71201f66f02929f429f85e4c6fddf325fa2760bafc1a84887f4c1cfee9e013335639cd069d327b83370824141df5a85a306c8641fd7c4608ca24cb24b49cae50bfa1f3c5c70e1dca463cd7ebeb8f32f6cf9273733d8ca9e2852a0246e2a268b0f5064debdc4190ebc392ad722d2d8fc48e40fef1d8a412e212433812169643ce25f33ba89e9e80e4e76432335606d17c631ba03d7ecc91fe9da40aea63c71eb38a04d13249c0df89797d918c5fece930c0d32ff64c8701e7ba68c834e304cc533257b50bb05d43e1ad455153497611080e6c9a399c9a0ba06fdd6354229828936dec342f5f0cbacdc34fbb1a2843173b7fb32a541fcc0b65b03123d84f2de6dc51885e7b5e231620ca51c417f7db9e6b3a4e2f113c87ab3af744f057579a67bc2cbf7525f07c20c6ee6fe058502f137f6720858bcec933964e1813e52f732b16ea7701cb2e751c82dfdd1e3181aba693b1bbf41277df5c2072f02c0d1b94b3c424cf79398ff8767d10bc6e5a48afb170bae483774b90d2eb45f37a1d9e5eafa0b75ad9b049894eb1b1a661d9cca304414f39b1dd2ea55fca083a08a65f61921082354835cea96d9fd7e74e6801ed129878bbc3d15b51db04892a6367d3f04cbd87b99ef3abfaa876b910d3eb28b12060abdedea5401d4c3e7b30d0b9f5a02d7f5b248be8578e6b44c11fc535ba34b0e9d5b5abf22ca480863d80cc97bea9f57bfed2d3a2251e013f9a4465e5ebb915bda702a439381aac9473a763af9f5d9f08876d7655a629c520bb4b446d87c2024b1a58cdd03afcb6757823c1359e89f4de79ecbdbe51323c9f0c9d59eba34000e707b532e802998dacca5a114b399e105c2d773d817ac43c97c90a88cd8aab2d7e7cf9d5ee48f16aac4a30ad89a6e3aa99b13a9fedf51ab82eba3b0cc5fc19e8a7c4cf1bf89d2997dce49040fd5f4ac1a91e7ba299de8cc0a1b76803bba4aefe7bcba0a48c1d08cb350fbd04497003c0c58a52d7a23d6029e70f1e222a4b2495c8e272f3ccd855b4e8da54b7f8d5a50e048f39f42861046d771ae0943462d8e2bc85088df7a574f904c0306041536d188f7c724a5b058aa89b330c238da83f4c36edf51fbd0e24e5e6a2773e0a4bc4b699b934e479157f9fb4f201e05b40193ff7360ed438e52cd02611ff00e03f00aa4acfc1def24be0cf57612a85b778bc25bc4da4cf2b3c0d416eb41553085fe90a13f60c959bf125a138e658227d9d10f502d2d7198314189fdfec74d685759d02ea18779c0e63f2b3dcf220c9ec862cd84395b901dc3499fcb5518017199b69a80f78947e4dca5ef2759d7f570d6729b0b2dc1eaa465d3bad19a3dde078212738388d958cbda41727af79fa5f9875aa1df31112bc48a11125c764f87f80c0be7bcff282db3895de6a9bb884bc51ebfd9b73e235728e0087dc9e7059121bb38f0fe5621176cf4e0b68aecad3093a9f89fbb0d2bc5bc1ee87f455076cdb8668a599da16c80a2033642bb3368d3c933e7f90e0efcff6ce7495f32191e50eefe2e6a1c6cbefd65ac6cbefd65a7fc56eee606a8752206783793aa9b132f348ecc1f3a0893cea5dcde464da1bd4ef8e1cf1420f23584d6f089748589be64748bdd82c47b2781f3a97a3dd8118ed434f3ea50d840d8ca4c1ee9230a59edafcb8a66d831bec6782a2635deca1800cabf388efc029de15fa27a8fabc54d6114993e02bf4c101d719c62981b2b40b027a0ca07bd453b1dd50c5f3ca6b289c556858c2a66ad3b48ee5bb2587a8e15d3efc357e7817523a1f3420d3c09281baea98284fc490320cfc07d8696bc7afbf1467582271446b65c071446b65c0842d9156be0f05d6c337ea2cdf4da0b566c7d8a2fbffc4367fda03308716d181caa76bdffe86df26dffe86df2625703a3c9804ca17fbc86d5124a2b197ab36524385045e51c70cf462ae2a5d96aca286f064999164417a471454f7f78d7b0a1c19a8ae09a28711c53ef6633a3e1e997ba888963ff50bc627fa47f96ee73714f62ecb0e7877d1bbe01c8c1d39970d6010f88f925510ce73c007575b25281a36af71147efd68d2e4c7790d71147efd6871147efd6872b2ef7bb366cffb20a07cc626f64db994e205c082f1eb02de27d626695a732413d5ae732413d5aef8a2930015ed8fe130e59eb76d51688b9f7d8d71b7ad70d2c5b986ec200fb986ec200f0d8cce74eaab205e1c3841fbdd4524b2d1ef31ec1524f792e0540fb13120e972e1aa2a245f11d10d8586888429489f52759d8e7bc5030f26b07bd2e1d59222286cb11d62de8fe0ae93934c6a53f877c4efbc1e1164bd1412948f89debcc2aa5b22c038fb5410d152905c8d007c14ca6ed002a9019d9a9caa612dcc892c57d47886d4fe72cb35dd8221be47546c5b621ff4bdefb8ce7cbdefb8ce7c3d2411f4ed5400fb4b3abd3f77037b79388644fcbf2425de2a06326a8da65f00218ce5ec9b165aacedca00ad79869caa8de80d945405ae26a4cb98984fe1c955b260312ae739d1b2d2a9c95fb2b18be9da7f1b85e112aea494953322fa8f2a571a9f0529cec9d5035c7c887efda1736fa1df08b26f0b6f8e81d927aed724be9dd89d453e776fac265a7021e693090b74f0d57c71c859fd6367ea9ea9169c7e34c5f3592f2b6a58b8ce51ee3e8b2933ebc7db40b858a3714db4eebec9879191ced077db657ca82526fce514611fd8920d25340b6114edf6925eb20d968ae12602d9b600ccc0416b64197b4bb814fac8bc96c4983eab317cc29ec71c57d61a437ea2bcfd9b81b22d56336387d93296137227f9637a5bd2fb92ec5f1b54ce5d63cbf473eb1fbdfcc37f8bb22dfd640205764531cd18c9acabdcbf8753228588907073ff64413e6ae66b34870ac49e031e91cc4ec6602ec5c96002f892a0cffc6027e283cf1d425ee0b1f4746f2d79b83a80e21cb094fedb2625c5d480d24932dfd9b6bbedc64de009a37294fb0480e07330fb94458dba84a563d136818216173144e1ecc7021966b022597cbd6d7fb9a871594b2039cb9f3991518bd425d2fb389514696564c9c508a92e0e23ae425589d4afac4818b0962ccf1c75d335932d862492434724a1e1a686cef7a5f795f94145f63f4bb990d4c80c4a359164adfa0deb5266964a6d385e0c7ea4ccad4f086571e4905ac73f81915ac73f819174d108c611e9b3aaeab4a64f30db1251c87c89b50124ed187c45db20bdb53e19c475c123838bef2a61267370065212a53c0ef88f1145e13dba83d3c815bea004e9ecf134cfb91dc7520bd5a3f77b5d16d4f1531d42e947b2546ac322ff60126066698885604f8ef4e84ea3592cf0ddfa237e64335426e9746f0b16cee8e19c6fe81d0557c1d220bf8a150986b628bdb723aec4bdcacb53ddffedb459415a41888397bf789881c602aa351782b0f0daa8abfda768f0572b8467f68523e0f2ea32883e4af595035794e953cb3f6db08c3ede3a9fd0fe32b4c328bf681e989b006651f27f949622d18b3b1882dc7ce14f00e97f4c66cd55f121e508be4e85369e54f33960f4b8a8eb1138807211a88fe6402e99b4be5bf36f79d7508ecf6d75f6eeadd9589516d0074d8fb7ed7aabe187c663156b1013ac5acae994949be87e412adf3683cd4ad543b3f8889632d35022bbbc48fdeaa1914d146645108a7b48c7f7c60e39c84ceb546f1bd4e5a74db1e6e80a1b09ed537092c53345e9266434af1664b0ea7196b403aa52bea28d50829f24ee68e83f3672ef163b7427c83a58c8d13dc493ca0ff5d05521a39de4afc57636d4275a3991f39cad27fa0457af6ce8b6ab44abc71e8917ae0e16521a2a32ab43a15f5f028c887041ad39b06bfa97fd767840f8e3b2fb076551222fb9e017517146e94278833056cc9b4ee9498545fe302ce37564886a4e6fbb908005786c444fb5293532188a72261c7d0311227c0987d9c2175ff1a6ec2777e57fec660a3fe81f0c998b538973959341e25d2ee97cd31f42d4ba86c89e10c6090d125de8e470e32d748b726ae9443ff59f75a923d99c42c3a9ed81622212981218bdcd728f46673125e582df22a0ee419b5e787db6553328b15ac9d4285413b47345e4c1229f5ec0ccbab6cea8350448b8382743964488725434d19aa859864f410100a35ec65a2dd7f4fc2bc1da993b73c0d0422ab01564cf2a3920e7669bf968de6c5e3a45ec170e255cddbdaad1239c25faf72df2bd963554b53055ac9838a8cfdd5c21ab18ba23d2d2ecd436abe09d6b06bbb52cf6d5bd7bca286463969cc95be5520e956893a3de94327a145d6ec204f62c012ecfda415bca6e4f8d8abbb040b71d99db5ca4b42c87032ebecc79e06c2d260ea4ce26a198d3be34c9c7d3e115e2c47344e8b3e13d032d60ea4653586420c96d0aaa0c0997d65b98a730f45522deed5dea3e66b8c3b27a638f91148b484a261410329d3434d7b8d3d4a76f25895de9f812ca13a024d3465bcf854b4f1e1ba1053b0a481a216fa8edc4bad37b620baafd476c47b1ce7203aafca50e7124f30b34ff92dbc7446417f8c8321225055324103363e9a4dd5fa2f2dbf0880c18add0db2556e538161a8becd0175407d6147b5e333a114738809feef4ea89abbedf95378d407887ad11997d77159149a8d9917193gregkh@google.com >
2024-11-28 18:15:09 +00:00
Xiuhong Wang
93460febf9
UPSTREAM: f2fs: fix fiemap failure issue when page size is 16KB
...
After enable 16K page size, an infinite loop may occur in
fiemap (fm_length=UINT64_MAX) on a file, such as the 16KB
scratch.img during the remount operation in Android.
The condition for whether fiemap continues to map is to check
whether the number of bytes corresponding to the next map.m_lblk
exceeds blks_to_bytes(inode,max_inode_blocks(inode)) if there are HOLE.
The latter does not take into account the maximum size of a file with 16KB
page size, so the loop cannot be jumped out.
The following is the fail trace:
When f2fs_map_blocks reaches map.m_lblk=3936, it needs to go to the
first direct node block, so the map is 3936 + 4090 = 8026,
The next map is the second direct node block, that is,
8026 + 4090 = 12116,
The next map is the first indirect node block, that is,
12116 + 4090 * 4090 = 16740216,
The next map is the second indirect node block, that is,
16740216 + 4090 * 4090 = 33468316,
The next map is the first double indirect node block, that is,
33468316 + 4090 * 4090 * 4090 = 68451397316
Since map.m_lblk represents the address of a block, which is 32
bits, truncation will occur, that is, 68451397316 becomes
4026887876, and the number of bytes corresponding to the block
number does not exceed blks_to_bytes(inode,max_inode_blocks(inode)),
so the loop will not be jumped out.
The next time, it will be considered that it should still be a
double indirect node block, that is,
4026887876 + 4090 * 4090 * 4090 = 72444816876, which will be
truncated to 3725340140, and the loop will not be jumped out.
156.374871: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 0, start blkaddr = 0x8e00, len = 0x200, flags = 2,seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.374916: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 512, start blkaddr = 0x0, len = 0x0, flags = 0 , seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.374920: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 513, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
......
156.385747: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 3935, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.385752: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 3936, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.385755: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 8026, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.385758: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 12116, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.385761: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 16740216, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.385764: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 33468316, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.385767: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 4026887876, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.385770: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 3725340140, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.385772: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 4026887876, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
156.385775: f2fs_map_blocks: dev = (254,57), ino = 7449, file offset = 3725340140, start blkaddr = 0x0, len = 0x0, flags = 0, seg_type = 8, may_create = 0, multidevice = 0, flag = 1, err = 0
Commit a6a010f5def5 ("f2fs: Restrict max filesize for 16K f2fs")
has set the maximum allowed file size to (U32_MAX + 1) * F2FS_BLKSIZE,
so max_file_blocks should be used here to limit it, that is,
maxbytes defined above. And the max_inode_blocks function is not
called by other functions except here, so cleanup it.
Signed-off-by: Xiuhong Wang <xiuhong.wang@unisoc.com >
Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com >
Reviewed-by: Chao Yu <chao@kernel.org >
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org >
(cherry picked from commit a7a7c1d423a6351a6541e95c797da5358e5ad1ea)
Bug: 375052311
Test: fiemap_writer_test --gtest_filter=FiemapWriterTest.CreateUnalignedFile
Signed-off-by: Daniel Rosenberg <drosen@google.com >
(cherry picked from https://android-review.googlesource.com/q/commit:fffd1d38a4e6b678e915859b77b50fe207ac0613 )
Merged-In: I9ac9e56550716bd118c832e5e092792b7d231097
Change-Id: I9ac9e56550716bd118c832e5e092792b7d231097
2024-11-27 21:43:31 +00:00
Seiya Wang
3a856b7c13
ANDROID: GKI: Update symbol list for mtk
...
1 function symbol(s) added
'int hci_cmd_sync_status(struct hci_dev*, u16, u32, const void*, u32)'
Bug: 380913021
Signed-off-by: Seiya Wang <seiya.wang@mediatek.com >
Change-Id: I80c88da3392ae2634672d21f5f64b853f359fbdd
2024-11-26 19:35:29 +00:00
Pedro Tammela
929ff4817a
UPSTREAM: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT
...
[ Upstream commit 2e95c4384438adeaa772caa560244b1a2efef816 ]
In qdisc_tree_reduce_backlog, Qdiscs with major handle ffff: are assumed
to be either root or ingress. This assumption is bogus since it's valid
to create egress qdiscs with major handle ffff:
Budimir Markovic found that for qdiscs like DRR that maintain an active
class list, it will cause a UAF with a dangling class pointer.
In 066a3b5b23066a3b5b23markovicbudimir@gmail.com >
Suggested-by: Jamal Hadi Salim <jhs@mojatatu.com >
Tested-by: Victor Nogueira <victor@mojatatu.com >
Signed-off-by: Pedro Tammela <pctammela@mojatatu.com >
Signed-off-by: Jamal Hadi Salim <jhs@mojatatu.com >
net/sched/sch_api.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Simon Horman <horms@kernel.org >
Bug: 377197048
Link: https://patch.msgid.link/20241024165547.418570-1-jhs@mojatatu.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
Signed-off-by: Sasha Levin <sashal@kernel.org >
(cherry picked from commit 597cf9748cjoneslee@google.com >
Change-Id: I4ef8bee1095f7c51e4d458b25cd331018188b3d6
2024-11-25 16:23:10 +00:00
Dmitry Antipov
7cd56b010f
UPSTREAM: net: sched: use RCU read-side critical section in taprio_dump()
...
[ Upstream commit b22db8b8befe90b61c98626ca1a2fbb0505e9fe3 ]
Fix possible use-after-free in 'taprio_dump()' by adding RCU
read-side critical section there. Never seen on x86 but
found on a KASAN-enabled arm64 system when investigating
https://syzkaller.appspot.com/bug?extid=b65e0af58423fc8a73aa :
[T15862] BUG: KASAN: slab-use-after-free in taprio_dump+0xa0c/0xbb0
[T15862] Read of size 4 at addr ffff0000d4bb88f8 by task repro/15862
[T15862]
[T15862] CPU: 0 UID: 0 PID: 15862 Comm: repro Not tainted 6.11.0-rc1-00293-gdefaf1a2113a-dirty #2
[T15862] Hardware name: QEMU QEMU Virtual Machine, BIOS edk2-20240524-5.fc40 05/24/2024
[T15862] Call trace:
[T15862] dump_backtrace+0x20c/0x220
[T15862] show_stack+0x2c/0x40
[T15862] dump_stack_lvl+0xf8/0x174
[T15862] print_report+0x170/0x4d8
[T15862] kasan_report+0xb8/0x1d4
[T15862] __asan_report_load4_noabort+0x20/0x2c
[T15862] taprio_dump+0xa0c/0xbb0
[T15862] tc_fill_qdisc+0x540/0x1020
[T15862] qdisc_notify.isra.0+0x330/0x3a0
[T15862] tc_modify_qdisc+0x7b8/0x1838
[T15862] rtnetlink_rcv_msg+0x3c8/0xc20
[T15862] netlink_rcv_skb+0x1f8/0x3d4
[T15862] rtnetlink_rcv+0x28/0x40
[T15862] netlink_unicast+0x51c/0x790
[T15862] netlink_sendmsg+0x79c/0xc20
[T15862] __sock_sendmsg+0xe0/0x1a0
[T15862] ____sys_sendmsg+0x6c0/0x840
[T15862] ___sys_sendmsg+0x1ac/0x1f0
[T15862] __sys_sendmsg+0x110/0x1d0
[T15862] __arm64_sys_sendmsg+0x74/0xb0
[T15862] invoke_syscall+0x88/0x2e0
[T15862] el0_svc_common.constprop.0+0xe4/0x2a0
[T15862] do_el0_svc+0x44/0x60
[T15862] el0_svc+0x50/0x184
[T15862] el0t_64_sync_handler+0x120/0x12c
[T15862] el0t_64_sync+0x190/0x194
[T15862]
[T15862] Allocated by task 15857:
[T15862] kasan_save_stack+0x3c/0x70
[T15862] kasan_save_track+0x20/0x3c
[T15862] kasan_save_alloc_info+0x40/0x60
[T15862] __kasan_kmalloc+0xd4/0xe0
[T15862] __kmalloc_cache_noprof+0x194/0x334
[T15862] taprio_change+0x45c/0x2fe0
[T15862] tc_modify_qdisc+0x6a8/0x1838
[T15862] rtnetlink_rcv_msg+0x3c8/0xc20
[T15862] netlink_rcv_skb+0x1f8/0x3d4
[T15862] rtnetlink_rcv+0x28/0x40
[T15862] netlink_unicast+0x51c/0x790
[T15862] netlink_sendmsg+0x79c/0xc20
[T15862] __sock_sendmsg+0xe0/0x1a0
[T15862] ____sys_sendmsg+0x6c0/0x840
[T15862] ___sys_sendmsg+0x1ac/0x1f0
[T15862] __sys_sendmsg+0x110/0x1d0
[T15862] __arm64_sys_sendmsg+0x74/0xb0
[T15862] invoke_syscall+0x88/0x2e0
[T15862] el0_svc_common.constprop.0+0xe4/0x2a0
[T15862] do_el0_svc+0x44/0x60
[T15862] el0_svc+0x50/0x184
[T15862] el0t_64_sync_handler+0x120/0x12c
[T15862] el0t_64_sync+0x190/0x194
[T15862]
[T15862] Freed by task 6192:
[T15862] kasan_save_stack+0x3c/0x70
[T15862] kasan_save_track+0x20/0x3c
[T15862] kasan_save_free_info+0x4c/0x80
[T15862] poison_slab_object+0x110/0x160
[T15862] __kasan_slab_free+0x3c/0x74
[T15862] kfree+0x134/0x3c0
[T15862] taprio_free_sched_cb+0x18c/0x220
[T15862] rcu_core+0x920/0x1b7c
[T15862] rcu_core_si+0x10/0x1c
[T15862] handle_softirqs+0x2e8/0xd64
[T15862] __do_softirq+0x14/0x20
Bug: 377467434
Fixes: 18cdd2f099vinicius.gomes@intel.com >
Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru >
Link: https://patch.msgid.link/20241018051339.418890-2-dmantipov@yandex.ru
Signed-off-by: Paolo Abeni <pabeni@redhat.com >
Signed-off-by: Sasha Levin <sashal@kernel.org >
(cherry picked from commit 5d28246724joneslee@google.com >
Change-Id: I26f8129021be29645ae37f9aaea4644352b8154e
2024-11-25 15:59:02 +00:00
Yeongjin Gil
226e9f92a0
UPSTREAM: f2fs: compress: don't redirty sparse cluster during {,de}compress
...
In f2fs_do_write_data_page, when the data block is NULL_ADDR, it skips
writepage considering that it has been already truncated.
This results in an infinite loop as the PAGECACHE_TAG_TOWRITE tag is not
cleared during the writeback process for a compressed file including
NULL_ADDR in compress_mode=user.
This is the reproduction process:
1. dd if=/dev/zero bs=4096 count=1024 seek=1024 of=testfile
2. f2fs_io compress testfile
3. dd if=/dev/zero bs=4096 count=1 conv=notrunc of=testfile
4. f2fs_io decompress testfile
To prevent the problem, let's check whether the cluster is fully
allocated before redirty its pages.
Bug: 325092012
Fixes: 5fdb322ff2sj1557.seo@samsung.com >
Reviewed-by: Sunmin Jeong <s_min.jeong@samsung.com >
Tested-by: Jaewook Kim <jw5454.kim@samsung.com >
Change-Id: I0abb6bca0bb227f4f895c59e28b47b203ba0f280
Signed-off-by: Yeongjin Gil <youngjin.gil@samsung.com >
Reviewed-by: Chao Yu <chao@kernel.org >
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org >
(cherry picked from commit f785cec298c95d00058560c0715233294a04b8f3)
2024-11-22 23:15:05 +00:00
Chao Yu
84a9f618b5
UPSTREAM: f2fs: compress: don't {,de}compress non-full cluster
...
f2fs won't compress non-full cluster in tail of file, let's skip
dirtying and rewrite such cluster during f2fs_ioc_{,de}compress_file.
Bug: 325092012
Change-Id: I88e6b431b27b4768a312e0977ebe1c9e9cc23600
Signed-off-by: Chao Yu <chao@kernel.org >
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org >
(cherry picked from commit 025b3602b5
2024-11-22 23:15:05 +00:00
Chao Yu
3b2e004494
UPSTREAM: f2fs: allow f2fs_ioc_{,de}compress_file to be interrupted
...
This patch allows f2fs_ioc_{,de}compress_file() to be interrupted, so that,
userspace won't be blocked when manual {,de}compression on large file is
interrupted by signal.
Bug: 325092012
Change-Id: I020026926732b184f227621cd64506dae92a00a1
Signed-off-by: Chao Yu <chao@kernel.org >
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org >
(cherry picked from commit 3a2c0e55f9
2024-11-22 23:15:05 +00:00
Chao Yu
24492cb6b9
UPSTREAM: f2fs: compress: do sanity check on cluster when CONFIG_F2FS_CHECK_FS is on
...
This patch covers sanity check logic on cluster w/ CONFIG_F2FS_CHECK_FS,
otherwise, there will be performance regression while querying cluster
mapping info.
Callers of f2fs_is_compressed_cluster() only care about whether cluster
is compressed or not, rather than # of valid blocks in compressed cluster,
so, let's adjust f2fs_is_compressed_cluster()'s logic according to
caller's requirement.
Bug: 325092012
Change-Id: Ie3ddef60c5a3cdb2b18b0261f7188d39b7147935
Signed-off-by: Chao Yu <chao@kernel.org >
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org >
(cherry picked from commit 2aaea533bf063ed3b442df5fe5f6abfc538054c9)
2024-11-22 23:15:05 +00:00
Daeho Jeong
268f1fed50
UPSTREAM: f2fs: support SEEK_DATA and SEEK_HOLE for compression files
...
Fix to support SEEK_DATA and SEEK_HOLE for compression files
Bug: 325092012
Change-Id: Iba62c53e634682205f84c8dc3566ab8df9079158
Signed-off-by: Daeho Jeong <daehojeong@google.com >
Reviewed-by: Chao Yu <chao@kernel.org >
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org >
(cherry picked from commit a94c7fded76bfd1a061deae7be80fedbfa26774e)
2024-11-22 23:15:05 +00:00
Aleksei Vetrov
672918d432
ANDROID: add file for recording allowed ABI breaks
...
The tooling is configured to block any changes that has a chance to
break ABI, including the possibly safe:
* replacement of ANDROID_KABI_RESERVE with ANDROID_KABI_USE
* changes to internal structures that are not accessible to modules
* addition of enumerators
These changes are difficult for the tooling to identify as definitively
non-breaking, therefore, a human reviewer must check the change and
approve it as non-breaking.
This change adds a file to record the approval with the change that was
marked as breaking. This allows the tooling to:
* unblock presubmits for the change
* don't block presubmits when it is cherry-picked to another branch
* filter compatibility reports between a release branch and a tip of the
development branch it was forked from
The file is prefilled with all breaks that happened from the KMI freeze.
Bug: 365521273
Change-Id: I63fbed5c364cb8c7bd149bf40d084d3d87533bf7
Signed-off-by: Aleksei Vetrov <vvvvvv@google.com >
2024-11-22 12:01:11 +00:00
zhengwei
1ca5db7e29
ANDROID: GKI: update symbol list for honor
...
1 function symbol(s) added
'int __traceiter_android_rvh_hw_protection_shutdown(void*, const char*)'
1 variable symbol(s) added
'struct tracepoint __tracepoint_android_rvh_hw_protection_shutdown'
Bug: 380204228
Change-Id: Ia2f4df5e3555feb420813cc92ab784fc58012fff
Signed-off-by: zhengwei <zhengwei2@honor.com >
2024-11-21 20:08:11 +08:00
Dezhi Huang
13f2b693c7
ANDROID: vendor_hooks: add hook to record reboot reason
...
Add hook to record the reason for calling hw_protection_shutdown
Bug: 380204228
Bug: 334006616
Change-Id: I9dce8056693c96f1d5f1fab9af02a2e68ed6ab91
Signed-off-by: Dezhi Huang <huangdezhi@hihonor.com >
(cherry picked from commit 70e95a10a553c0c530694b8939d25fbb984647d0)
2024-11-21 19:47:56 +08:00
Carlos Llamas
51bee18173
BACKPORT: FROMGIT: binder: add delivered_freeze to debugfs output
...
Add the pending proc->delivered_freeze work to the debugfs output. This
information was omitted in the original implementation of the freeze
notification and can be valuable for debugging issues.
Fixes: d579b04a52a1 ("binder: frozen notification")
Cc: stable@vger.kernel.org
Signed-off-by: Carlos Llamas <cmllamas@google.com >
Acked-by: Todd Kjos <tkjos@google.com >
Reviewed-by: Alice Ryhl <aliceryhl@google.com >
Link: https://lore.kernel.org/r/20240926233632.821189-9-cmllamas@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Bug: 366003708
(cherry picked from commit cb2aeb2ec25884133110ffe5a67ff3cf7dee5ceb
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
char-misc-next)
Change-Id: Ifc9a22b52e38c35af661732486fa1f154adb34de
[cmllamas: fix KMI break with proc_wrapper()]
Signed-off-by: Carlos Llamas <cmllamas@google.com >
2024-11-20 17:21:07 +00:00
Carlos Llamas
2791dfac50
BACKPORT: FROMGIT: binder: fix memleak of proc->delivered_freeze
...
If a freeze notification is cleared with BC_CLEAR_FREEZE_NOTIFICATION
before calling binder_freeze_notification_done(), then it is detached
from its reference (e.g. ref->freeze) but the work remains queued in
proc->delivered_freeze. This leads to a memory leak when the process
exits as any pending entries in proc->delivered_freeze are not freed:
unreferenced object 0xffff38e8cfa36180 (size 64):
comm "binder-util", pid 655, jiffies 4294936641
hex dump (first 32 bytes):
b8 e9 9e c8 e8 38 ff ff b8 e9 9e c8 e8 38 ff ff .....8.......8..
0b 00 00 00 00 00 00 00 3c 1f 4b 00 00 00 00 00 ........<.K.....
backtrace (crc 95983b32):
[<000000000d0582cf>] kmemleak_alloc+0x34/0x40
[<000000009c99a513>] __kmalloc_cache_noprof+0x208/0x280
[<00000000313b1704>] binder_thread_write+0xdec/0x439c
[<000000000cbd33bb>] binder_ioctl+0x1b68/0x22cc
[<000000002bbedeeb>] __arm64_sys_ioctl+0x124/0x190
[<00000000b439adee>] invoke_syscall+0x6c/0x254
[<00000000173558fc>] el0_svc_common.constprop.0+0xac/0x230
[<0000000084f72311>] do_el0_svc+0x40/0x58
[<000000008b872457>] el0_svc+0x38/0x78
[<00000000ee778653>] el0t_64_sync_handler+0x120/0x12c
[<00000000a8ec61bf>] el0t_64_sync+0x190/0x194
This patch fixes the leak by ensuring that any pending entries in
proc->delivered_freeze are freed during binder_deferred_release().
Fixes: d579b04a52a1 ("binder: frozen notification")
Cc: stable@vger.kernel.org
Signed-off-by: Carlos Llamas <cmllamas@google.com >
Reviewed-by: Alice Ryhl <aliceryhl@google.com >
Acked-by: Todd Kjos <tkjos@google.com >
Link: https://lore.kernel.org/r/20240926233632.821189-8-cmllamas@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Bug: 366003708
(cherry picked from commit 1db76ec2b4b206ff943e292a0b55e68ff3443598
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
char-misc-next)
Change-Id: Iafdec3421c521b4b591b94455deba7ee5102c8ca
[cmllamas: drop BINDER_STAT_FREEZE and use proc_wrapper()]
Signed-off-by: Carlos Llamas <cmllamas@google.com >
2024-11-20 17:21:07 +00:00
Carlos Llamas
c5233c5678
FROMGIT: binder: allow freeze notification for dead nodes
...
Alice points out that binder_request_freeze_notification() should not
return EINVAL when the relevant node is dead [1]. The node can die at
any point even if the user input is valid. Instead, allow the request
to be allocated but skip the initial notification for dead nodes. This
avoids propagating unnecessary errors back to userspace.
Fixes: d579b04a52a1 ("binder: frozen notification")
Cc: stable@vger.kernel.org
Suggested-by: Alice Ryhl <aliceryhl@google.com >
Link: https://lore.kernel.org/all/CAH5fLghapZJ4PbbkC8V5A6Zay-_sgTzwVpwqk6RWWUNKKyJC_Q@mail.gmail.com/ [1]
Signed-off-by: Carlos Llamas <cmllamas@google.com >
Acked-by: Todd Kjos <tkjos@google.com >
Link: https://lore.kernel.org/r/20240926233632.821189-7-cmllamas@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Bug: 366003708
(cherry picked from commit ca63c66935b978441055e3d87d30225267f99329
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
char-misc-next)
Change-Id: I03af1eedfeb194f5a775388cbb4e7487e4a5dfc0
Signed-off-by: Carlos Llamas <cmllamas@google.com >
2024-11-20 17:21:07 +00:00
Carlos Llamas
194a332e5f
FROMGIT: binder: fix BINDER_WORK_CLEAR_FREEZE_NOTIFICATION debug logs
...
proc 699
context binder-test
thread 699: l 00 need_return 0 tr 0
ref 25: desc 1 node 20 s 1 w 0 d 00000000c03e09a3
unknown work: type 11
proc 640
context binder-test
thread 640: l 00 need_return 0 tr 0
ref 8: desc 1 node 3 s 1 w 0 d 000000002bb493e1
has cleared freeze notification
Fixes: d579b04a52a1 ("binder: frozen notification")
Cc: stable@vger.kernel.org
Suggested-by: Alice Ryhl <aliceryhl@google.com >
Signed-off-by: Carlos Llamas <cmllamas@google.com >
Reviewed-by: Alice Ryhl <aliceryhl@google.com >
Acked-by: Todd Kjos <tkjos@google.com >
Link: https://lore.kernel.org/r/20240926233632.821189-6-cmllamas@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Bug: 366003708
(cherry picked from commit 595ea72efff9fa65bc52b6406e0822f90841f266
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
char-misc-next)
Change-Id: Ic6311aaea2040aaf4534cdaa4cbfa378afe31869
Signed-off-by: Carlos Llamas <cmllamas@google.com >
2024-11-20 17:21:06 +00:00
Pierre Couillaud
5b095ade12
ANDROID: GKI: Update symbol list for BCMSTB
...
INFO: 1 function symbol(s) added
'unsigned long __alloc_pages_bulk(gfp_t, int, nodemask_t*, int, struct list_head*, struct page**)'
refs #SWANDROID-14843
Bug: 379775015
Change-Id: I7834e0e8b49e568e4f517109d21000b7f1352b70
Signed-off-by: Pierre Couillaud <pierre@broadcom.com >
2024-11-19 18:58:08 +00:00
Jing Wei
516ca8799f
ANDROID: psi: Add vendor hooks for PSI tracing
...
Add hooks to capture various per-zone memory stats when
a trigger threshold is hit.
Bug: 379593530
Change-Id: Ia748b9525da3996366802f536e66eaa35af4416e
Signed-off-by: Jing Wei <jing.wei5@transsion.com >
2024-11-19 18:06:45 +00:00
Daniel Okazaki
4a105e4e1c
ANDROID: ABI: Update pixel symbol list
...
Adding the following symbols:
- klist_add_head
- klist_add_tail
- klist_init
- klist_iter_exit
- klist_iter_init
- klist_next
- klist_node_attached
- klist_remove
Bug: 308028804
Change-Id: Ibfe7f62f18a36ca4ca6e07dc8ddf0a7fdde5114c
Signed-off-by: Daniel Okazaki <dtokazaki@google.com >
(cherry picked from commit 35cf4d8eab4665136971dc66c163c9cd18907c3a)
2024-11-19 17:35:25 +00:00
zhengwei
6cf2e7d968
ANDROID: GKI: update symbol list for honor
...
INFO: 2 function symbol(s) added
'int __traceiter_android_vh_slab_alloc_node(void*, void*, unsigned long, struct kmem_cache*)'
'int __traceiter_android_vh_slab_free(void*, unsigned long, struct kmem_cache*)'
2 variable symbol(s) added
'struct tracepoint __tracepoint_android_vh_slab_alloc_node'
'struct tracepoint __tracepoint_android_vh_slab_free'
Bug: 379598560
Change-Id: I27e41cf5545297e6c62a581d677a298bd629ad3e
Signed-off-by: zhengwei <zhengwei2@honor.com >
2024-11-18 19:36:48 +08:00
Dezhi Huang
eb0102684f
ANDROID: vendor_hooks: add hook to record slab alloc and free
...
Add hook to record slab usage for calling slab_alloc_node and
slab_free check for memory leaks.
Bug: 379598560
Bug: 341216009
Change-Id: Ibb5f77b8244096fc999190244d197b7a40e6591c
Signed-off-by: Dezhi Huang <huangdezhi@hihonor.com >
(cherry picked from commit d5c66ad281a72e29802ae72fec0526e58a151377)
2024-11-18 19:33:14 +08:00
Greg Kroah-Hartman
47a8b5f3ed
Merge 0d968ced73 ("mm/page_alloc: treat RT tasks similar to __GFP_HIGH") into android14-6.1-lts
...
Steps on the way to 6.1.116
Change-Id: I6502f70497285f1569aecf03c33c126b96d3001b
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com >
2024-11-17 12:22:19 +00:00
Greg Kroah-Hartman
500bbbbd01
Merge 241398329a ("mm/page_alloc: rename ALLOC_HIGH to ALLOC_MIN_RESERVE") into android14-6.1-lts
...
Steps on the way to 6.1.116
Change-Id: Ib7c11329d114065714cd5d11ef69e65ab4d0bd51
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com >
2024-11-17 12:20:06 +00:00
Greg Kroah-Hartman
ad46e48e1b
Merge b5dc5b7de7 ("cxl/port: Fix cxl_bus_rescan() vs bus_rescan_devices()") into android14-6.1-lts
...
Steps on the way to 6.1.116
Resolves merge conflicts in:
net/wireless/core.c
Change-Id: Ia10a58f63842e7bbc9440d960071985de9a399b8
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com >
2024-11-17 12:16:30 +00:00
Greg Kroah-Hartman
0df5dc7d73
Merge bdbc96c231 ("fsdax: dax_unshare_iter needs to copy entire blocks") into android14-6.1-lts
...
Steps on the way to 6.1.116
Resolves merge conflicts in:
fs/iomap/buffered-io.c
Change-Id: Ibe7e7f5a94bee171200931351878cf40e37b8bbc
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com >
2024-11-16 18:13:00 +00:00
Greg Kroah-Hartman
a566b71fed
Merge d321732352 ("netfilter: nft_payload: sanitize offset and length before calling skb_checksum()") into android14-6.1-lts
...
Steps on the way to 6.1.116
Change-Id: If62fadaf5fbd6d9663368509dd05b285a930f6d5
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com >
2024-11-16 18:04:20 +00:00
Greg Kroah-Hartman
bb558c55a5
Revert "genetlink: hold RCU in genlmsg_mcast()"
...
This reverts commit ae53d09f11gregkh@google.com >
2024-11-16 16:30:41 +00:00
Rui Chen