Re: [PATCH v7 01/18] tools: Add gendwarfksyms

On Fri, Dec 20, 2024 at 6:07 AM Sami Tolvanen wrote: > +int main(int argc, char **argv) > +{ > + unsigned int n; > + int opt; > + > + struct option opts[] = { { "debug", 0, NULL, 'd' }, You can add "static const" to opts[] here. I like the array initializer formatted like foll

Re: [PATCH] vhost/net: Set num_buffers for virtio 1.0

On 2024/12/27 10:29, Jason Wang wrote: On Thu, Dec 26, 2024 at 7:54 PM Michael S. Tsirkin > wrote: On Mon, Nov 11, 2024 at 09:27:45AM +0800, Jason Wang wrote: > On Wed, Nov 6, 2024 at 4:54 PM Michael S. Tsirkin mailto:m...@redhat.com>> wrote: > > > >

[RFC PATCH v2 1/2] mm/memfd: Add support for F_SEAL_FUTURE_EXEC to memfd

Android currently uses the ashmem driver [1] for creating shared memory regions between processes. Ashmem buffers can initially be mapped with PROT_READ, PROT_WRITE, and PROT_EXEC. Processes can then use the ASHMEM_SET_PROT_MASK ioctl command to restrict--never add--the permissions that the buffer

[RFC PATCH v2 2/2] selftests/memfd: Add tests for F_SEAL_FUTURE_EXEC

Add tests to ensure that F_SEAL_FUTURE_EXEC behaves as expected. Signed-off-by: Isaac J. Manjarres --- tools/testing/selftests/memfd/memfd_test.c | 79 ++ 1 file changed, 79 insertions(+) diff --git a/tools/testing/selftests/memfd/memfd_test.c b/tools/testing/selftests/memf

[RFC PATCH v2 0/2] Add file seal to prevent future exec mappings

Android uses the ashmem driver [1] for creating shared memory regions between processes. The ashmem driver exposes an ioctl command for processes to restrict the permissions an ashmem buffer can be mapped with. Buffers are created with the ability to be mapped as readable, writable, and executable

[PATCH 3/3 v2] Revert "rcu/nocb: Fix rcuog wake-up from offline softirq"

This reverts commit f7345ccc62a4b880cf76458db5f320725f28e400. swake_up_one_online() has been removed because hrtimers can now assign a proper online target to hrtimers queued from offline CPUs. Therefore remove the related hackery. Signed-off-by: Frederic Weisbecker --- kernel/rcu/tree_nocb.h |

[PATCH 1/3 v2] hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING

hrtimers are migrated away from the dying CPU to any online target at the CPUHP_AP_HRTIMERS_DYING stage in order not to delay bandwidth timers handling tasks involved in the CPU hotplug forward progress. However wake ups can still be performed by the outgoing CPU after CPUHP_AP_HRTIMERS_DYING. Tho

[PATCH 2/3 v2] rcu: Remove swake_up_one_online() bandaid

It's now ok to perform a wake-up from an offline CPU because the resulting armed scheduler bandwidth hrtimers are now correctly targeted by hrtimer infrastructure. Remove the obsolete hackerry. Signed-off-by: Frederic Weisbecker --- kernel/rcu/tree.c | 34 +-

[PATCH 0/3 v2] hrtimer: Fix timers queued locally from offline CPUs

5c0930ccaad5 ("hrtimers: Push pending hrtimers away from outgoing CPU earlier") was introduced to fix stalls with scheduler bandwidth timers getting migrated while some kthreads handling CPU hotplug rely on bandwidth. However this has introduced several other issues which used to be confined to RC

Re: [PATCH] arm64: dts: qcom: sm7225-fairphone-fp4: Drop extra qcom,msm-id value

On Fri, 20 Dec 2024 09:55:01 +0100, Luca Weiss wrote: > The ID 434 is for SM6350 while 459 is for SM7225. Fairphone 4 is only > SM7225, so drop the unused 434 entry. > > Applied, thanks! [1/1] arm64: dts: qcom: sm7225-fairphone-fp4: Drop extra qcom,msm-id value commit: 7fb88e0d4dc1a40a2

Re: [PATCH 0/2] Add missing parent_map to clocks in SM6350 clock drivers

On Fri, 20 Dec 2024 10:03:29 +0100, Luca Weiss wrote: > If a clk_rcg2 has a parent, it should also have parent_map defined, > otherwise we'll get a NULL pointer dereference when calling clk_set_rate > on those clocks. > > Correct this on clocks in both gcc-sm6350 and dispcc-sm6350. > > > [...]

Re: [PATCH] arm64: dts: qcom: sm6350: Fix uart1 interconnect path

On Fri, 20 Dec 2024 09:59:50 +0100, Luca Weiss wrote: > The path MASTER_QUP_0 to SLAVE_EBI_CH0 would be qup-memory path and not > qup-config. Since the qup-memory path is not part of the qcom,geni-uart > bindings, just replace that path with the correct path for qup-config. > > Applied, thanks

Re: [PATCH] sev-snp: parse MP tables for VMware hypervisor

On Thu, Dec 19, 2024 at 6:44 AM Ajay Kaher wrote: > > For VMware hypervisor, SEV-SNP enabled VM's could boot without UEFI. > In this case, mpparse_find_mptable() has to be called to parse MP > tables which contains boot information. > > Fixes: 0f4a1e80989a ("x86/sev: Skip ROM range scans and valid

Re: [PATCH v4 2/2] riscv: selftests: Add a ptrace test to verify syscall parameter modification

On 2024-12-26 21:35, Dmitry V. Levin wrote: > On Thu, Dec 26, 2024 at 06:52:52PM +0800, Celeste Liu wrote: >> This test checks that orig_a0 allows a syscall argument to be modified, >> and that changing a0 does not change the syscall argument. >> >> Co-developed-by: Quan Zhou >> Signed-off-by: Q

Re: [PATCH v4 2/2] riscv: selftests: Add a ptrace test to verify syscall parameter modification

On Thu, Dec 26, 2024 at 06:52:52PM +0800, Celeste Liu wrote: > This test checks that orig_a0 allows a syscall argument to be modified, > and that changing a0 does not change the syscall argument. > > Co-developed-by: Quan Zhou > Signed-off-by: Quan Zhou > Co-developed-by: Charlie Jenkins > Sign

Re: [PATCH] vhost/net: Set num_buffers for virtio 1.0

On Mon, Nov 11, 2024 at 09:27:45AM +0800, Jason Wang wrote: > On Wed, Nov 6, 2024 at 4:54 PM Michael S. Tsirkin wrote: > > > > On Sun, Sep 15, 2024 at 10:35:53AM +0900, Akihiko Odaki wrote: > > > The specification says the device MUST set num_buffers to 1 if > > > VIRTIO_NET_F_MRG_RXBUF has not be

Re: [PATCH v2 2/2] riscv: selftests: Add a ptrace test to verify syscall parameter modification

On 2024-12-20 05:36, Charlie Jenkins wrote: > On Fri, Dec 20, 2024 at 05:29:45AM +0800, Celeste Liu wrote: >> >> On 2024-12-20 02:26, Charlie Jenkins wrote: >>> On Tue, Dec 03, 2024 at 01:55:07PM +0100, Andrew Jones wrote: On Tue, Dec 03, 2024 at 05:30:05PM +0800, Celeste Liu wrote: > Fr

[PATCH v4 0/2] riscv/ptrace: add new regset to access original a0 register

/all/59505464-c84a-403d-972f-d4b2055ee...@gmail.com/ Signed-off-by: Celeste Liu --- Changes in v4: - Fix a copy paste error in selftest. (Forget to commit...) - Link to v3: https://lore.kernel.org/r/20241226-riscv-new-regset-v3-0-f5b964658...@coelacanthus.name Changes in v3: - Use return 0

Re: [PATCH v3 2/2] riscv: selftests: Add a ptrace test to verify syscall parameter modification

On 2024-12-26 18:45, Celeste Liu wrote: > This test checks that orig_a0 allows a syscall argument to be modified, > and that changing a0 does not change the syscall argument. > > Co-developed-by: Quan Zhou > Signed-off-by: Quan Zhou > Co-developed-by: Charlie Jenkins > Signed-off-by: Charlie

[PATCH v3 0/2] riscv/ptrace: add new regset to access original a0 register

The orig_a0 is missing in struct user_regs_struct of riscv, and there is no way to add it without breaking UAPI. (See Link tag below) Like NT_ARM_SYSTEM_CALL do, we add a new regset name NT_RISCV_ORIG_A0 to access original a0 register from userspace via ptrace API. Link: https://lore.kernel.org/

[PATCH v4 2/2] riscv: selftests: Add a ptrace test to verify syscall parameter modification

This test checks that orig_a0 allows a syscall argument to be modified, and that changing a0 does not change the syscall argument. Co-developed-by: Quan Zhou Signed-off-by: Quan Zhou Co-developed-by: Charlie Jenkins Signed-off-by: Charlie Jenkins Reviewed-by: Björn Töpel Signed-off-by: Celest

[PATCH v4 1/2] riscv/ptrace: add new regset to access original a0 register

The orig_a0 is missing in struct user_regs_struct of riscv, and there is no way to add it without breaking UAPI. (See Link tag below) Like NT_ARM_SYSTEM_CALL do, we add a new regset name NT_RISCV_ORIG_A0 to access original a0 register from userspace via ptrace API. Fixes: e2c0cdfba7f6 ("RISC-V: U

[PATCH v3 2/2] riscv: selftests: Add a ptrace test to verify syscall parameter modification

This test checks that orig_a0 allows a syscall argument to be modified, and that changing a0 does not change the syscall argument. Co-developed-by: Quan Zhou Signed-off-by: Quan Zhou Co-developed-by: Charlie Jenkins Signed-off-by: Charlie Jenkins Reviewed-by: Björn Töpel Signed-off-by: Celest

[PATCH v3 1/2] riscv/ptrace: add new regset to access original a0 register

The orig_a0 is missing in struct user_regs_struct of riscv, and there is no way to add it without breaking UAPI. (See Link tag below) Like NT_ARM_SYSTEM_CALL do, we add a new regset name NT_RISCV_ORIG_A0 to access original a0 register from userspace via ptrace API. Fixes: e2c0cdfba7f6 ("RISC-V: U