summaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-strncpy.c
diff options
context:
space:
mode:
authorSudeep Holla <sudeep.holla@arm.com>2025-03-13 18:28:53 +0300
committerJassi Brar <jassisinghbrar@gmail.com>2025-03-27 04:58:26 +0300
commitfa362ffafa51b08cf8e2fcca38e056332f6b9b05 (patch)
treeba4aa7381683281803f365d0a11d80fdb0857db5 /lib/test_fortify/write_overflow-strncpy.c
parent3a675f50415b95f2ae10bfd932e2154ba1a08ee7 (diff)
downloadlinux-fa362ffafa51b08cf8e2fcca38e056332f6b9b05.tar.xz
mailbox: pcc: Always map the shared memory communication address
Currently the shared memory communication address was mapped by the mailbox client drivers leading to all sorts of inconsistencies. It also has resulted in the inconsistent attributes used while mapping the shared memory regions. In order to remove/eliminate any issues, let us ensures the shared memory address is always mapped and unmapped when the PCC channels are requested and release. We need to map them as the ACPI PCCT associates these shared memory with each channel subspace and may need use the status or the flags in the headers of those shared memory communication address regions to manage the transport/channel. Note, until all the drivers using PCC start using this mapped shmem, there might be double mapping of the shared memory address. This shouldn't have any impact on existing mbox client drivers. Since there are no users of pcc_chan_ioremap() and also it is mapped by default, we can stop exporting it and merge the functionality into pcc_mbox_request_channel(). Acked-by: Huisong Li <lihuisong@huawei.com> Tested-by: Huisong Li <lihuisong@huawei.com> Tested-by: Adam Young <admiyo@os.amperecomputing.com> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com> Signed-off-by: Jassi Brar <jassisinghbrar@gmail.com>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy.c')
0 files changed, 0 insertions, 0 deletions