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

2025-01-06 Thread Jeff Xu
On Mon, Jan 6, 2025 at 5:26 PM Isaac Manjarres wrote: > > On Mon, Jan 06, 2025 at 09:35:09AM -0800, Jeff Xu wrote: > > + Kees because this is related to W^X memfd and security. > > > > On Fri, Jan 3, 2025 at 7:04 AM Jann Horn wrote: > > > > > > On Fri, Jan 3, 2025 at 12:32 AM Isaac J. Manjarres >

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

2025-01-06 Thread Isaac Manjarres
On Mon, Jan 06, 2025 at 09:35:09AM -0800, Jeff Xu wrote: > + Kees because this is related to W^X memfd and security. > > On Fri, Jan 3, 2025 at 7:04 AM Jann Horn wrote: > > > > On Fri, Jan 3, 2025 at 12:32 AM Isaac J. Manjarres > > wrote: > > > Android currently uses the ashmem driver [1] for cr

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

2025-01-06 Thread Isaac Manjarres
On Fri, Jan 03, 2025 at 04:03:44PM +0100, Jann Horn wrote: > On Fri, Jan 3, 2025 at 12:32 AM Isaac J. Manjarres > wrote: > > 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,

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

2025-01-06 Thread Kees Cook
On Mon, Jan 06, 2025 at 10:26:27AM -0800, Jeff Xu wrote: > + Kees because this is related to W^X memfd and security. > > On Fri, Jan 3, 2025 at 7:14 AM Jann Horn wrote: > > > > On Fri, Dec 6, 2024 at 7:19 PM Lorenzo Stoakes > > wrote: > > > On Thu, Dec 05, 2024 at 05:09:22PM -0800, Isaac J. Manj

Re: [PATCH v1 0/3] module: Don't fail module loading when setting ro_after_init section RO failed

2025-01-06 Thread Kees Cook
On Fri, Jan 03, 2025 at 05:13:32PM +0100, Petr Pavlu wrote: > On 12/5/24 20:46, Christophe Leroy wrote: > > This series reworks module loading to avoid leaving the module in a > > stale state when protecting ro_after_init section fails. > > > > Once module init has succeded it is too late to cance

Re: [PATCH net-next v2 2/4] netconsole: selftest: Split the helpers from the selftest

2025-01-06 Thread Jakub Kicinski
On Fri, 03 Jan 2025 04:57:50 -0800 Breno Leitao wrote: > Split helper functions from the netconsole basic test into a separate > library file to enable reuse across different netconsole tests. This > change only moves the existing helper functions to lib/sh/lib_netcons.sh > while preserving the sam

Re: [PATCH v2 28/28] cfi: Use RCU while invoking __module_address().

2025-01-06 Thread Sami Tolvanen
Hi, On Mon, Jan 6, 2025 at 10:00 AM Elliot Berman wrote: > > On Thu, Jan 02, 2025 at 04:24:22PM -0800, Sami Tolvanen wrote: > > Hi Elliot, > > > > On Mon, Dec 30, 2024 at 7:33 PM Elliot Berman > > wrote: > > > > > > On Fri, Dec 20, 2024 at 06:41:42PM +0100, Sebastian Andrzej Siewior wrote: > > >

Re: [PATCH v6 2/5] pidfd: add PIDFD_SELF_* sentinels to refer to own thread/process

2025-01-06 Thread Shakeel Butt
On Mon, Dec 02, 2024 at 10:52:13AM +, Lorenzo Stoakes wrote: > On Fri, Nov 08, 2024 at 02:28:14PM +, Lorenzo Stoakes wrote: > > On Wed, Oct 30, 2024 at 04:37:37PM +, Lorenzo Stoakes wrote: > > > On Mon, Oct 28, 2024 at 04:06:07PM +, Lorenzo Stoakes wrote: > > > > I guess I'll try to

Re: (subset) [PATCH 0/5] Add EEPROMs found in the camera sensors on Fairphone 5

2025-01-06 Thread Bartosz Golaszewski
From: Bartosz Golaszewski On Fri, 03 Jan 2025 12:11:56 +0100, Luca Weiss wrote: > While out-of-tree already two of the three camera sensors are working on > this smartphone, getting those upstream-ready will still take a while. > > Until then already enable the EEPROMs found on those camera sen

Re: [PATCH] selftests/nolibc: start qemu with 1 GiB of memory

2025-01-06 Thread Thomas Weißschuh
On 2025-01-06 10:51:52-0700, Shuah Khan wrote: > On 10/7/24 02:10, Thomas Weißschuh wrote: > > Recently the loongarch defconfig stopped working with the default 128 MiB > > of memory. The VM just spins infinitively. > > Increasing the available memory to 1 GiB, similar to s390, fixes the > > issue.

[PATCH v2 7/8] mm/damon: remove DAMON debugfs interface kunit tests

2025-01-06 Thread SeongJae Park
It's time to remove DAMON debugfs interface, which has deprecated long before in February 2023. Read the cover letter of this patch series for more details. Remove kunit tests for the interface, to prevent unnecessary test failures. Signed-off-by: SeongJae Park --- mm/damon/Kconfig

[PATCH v2 6/8] kunit: configs: remove configs for DAMON debugfs interface tests

2025-01-06 Thread SeongJae Park
It's time to remove DAMON debugfs interface, which has deprecated long before in February 2023. Read the cover letter of this patch series for more details. Remove kernel configs for running DAMON debugfs interface kunit tests from the kunit all_tests configuration, to prevent unnecessary noises

[PATCH v2 5/8] selftests/damon: remove tests for DAMON debugfs interface

2025-01-06 Thread SeongJae Park
It's time to remove DAMON debugfs interface, which has deprecated long before in February 2023. Read the cover letter of this patch series for more details. Remove selftests for the interface, to prevent causing unnecessary test failures. Signed-off-by: SeongJae Park --- tools/testing/selftest

[PATCH v2 4/8] selftests/damon/config: remove configs for DAMON debugfs interface selftests

2025-01-06 Thread SeongJae Park
It's time to remove DAMON debugfs interface, which has deprecated long before in February 2023. Read the cover letter of this patch series for more details. Remove configs for selftests of it from DAMON selftests config file, to prevent unnecessary noises from the tests. [1] https://lore.kernel.

Re: [PATCH v3] dt-bindings: remoteproc: qcom,sa8775p-pas: Document QCS8300 remoteproc

2025-01-06 Thread Rob Herring
On Thu, Nov 14, 2024 at 05:23:25PM +0800, Jingyi Wang wrote: > > Hi Maintainers, > > On 9/25/2024 3:21 PM, Jingyi Wang wrote: > > Document the components used to boot the ADSP, CDSP and GPDSP on the > > Qualcomm QCS8300 SoC. Use fallback to indicate the compatibility of the > > remoteproc on the

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

2025-01-06 Thread Jeff Xu
+ Kees because this is related to W^X memfd and security. On Fri, Jan 3, 2025 at 7:14 AM Jann Horn wrote: > > On Fri, Dec 6, 2024 at 7:19 PM Lorenzo Stoakes > wrote: > > On Thu, Dec 05, 2024 at 05:09:22PM -0800, Isaac J. Manjarres wrote: > > > + if (is_exec_sealed(seals)) { > > > > A

Re: [RFC PATCH] get_maintainer: decouple subsystem status from maintainer role

2025-01-06 Thread Thorsten Leemhuis
Lo! From the "better reply late than never" department: Thx for picking this up again, much appreciated! On 18.12.24 06:48, Kees Cook wrote: > On Fri, Dec 13, 2024 at 12:29:22PM +0100, Vlastimil Babka wrote: >> The script currently uses the subystem's status (S: field) to change how >> maintainer

Re: [PATCH v2 28/28] cfi: Use RCU while invoking __module_address().

2025-01-06 Thread Elliot Berman
On Thu, Jan 02, 2025 at 04:24:22PM -0800, Sami Tolvanen wrote: > Hi Elliot, > > On Mon, Dec 30, 2024 at 7:33 PM Elliot Berman > wrote: > > > > On Fri, Dec 20, 2024 at 06:41:42PM +0100, Sebastian Andrzej Siewior wrote: > > > __module_address() can be invoked within a RCU section, there is no > > >

Re: [PATCH] selftests/nolibc: start qemu with 1 GiB of memory

2025-01-06 Thread Shuah Khan
On 10/7/24 02:10, Thomas Weißschuh wrote: Recently the loongarch defconfig stopped working with the default 128 MiB of memory. The VM just spins infinitively. Increasing the available memory to 1 GiB, similar to s390, fixes the issue. To avoid having to do this for each architecture on its own, p

Re: [RFC PATCH 1/2] ptp: add PTP_SYS_OFFSET_STAT for xtstamping with status

2025-01-06 Thread Peter Hilber
On Thu, Jan 02, 2025 at 08:21:11AM -0800, Richard Cochran wrote: > On Thu, Jan 02, 2025 at 05:11:01PM +0100, Peter Hilber wrote: > > For sure. But the aim of this proposal is to have an interoperable time > > synchronization solution for VMs through a Virtio device. So the idea is > > to include me

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

2025-01-06 Thread Jeff Xu
+ Kees because this is related to W^X memfd and security. On Fri, Jan 3, 2025 at 7:04 AM Jann Horn wrote: > > On Fri, Jan 3, 2025 at 12:32 AM Isaac J. Manjarres > wrote: > > Android currently uses the ashmem driver [1] for creating shared memory > > regions between processes. Ashmem buffers can

Re: [PATCH v2 0/5] Use Device Lifecycle managed functions in TI R5 Remoteproc driver

2025-01-06 Thread Mathieu Poirier
On Thu, Dec 19, 2024 at 04:35:40PM +0530, Beleswar Padhi wrote: > This series uses various devm_ helpers to simplify device removal path in > ti_k3_r5_remoteproc driver. This is the first series in the TI K3 > Remoteproc refactoring as long planned since [0]. > > Testing Done: > 1. Tested boot of

[PATCH AUTOSEL 6.12 4/8] sched_ext: Fix dsq_local_on selftest

2025-01-06 Thread Sasha Levin
From: Tejun Heo [ Upstream commit ce2b93fc1dfa1c82f2576aa571731c4e5dcc8dd7 ] The dsp_local_on selftest expects the scheduler to fail by trying to schedule an e.g. CPU-affine task to the wrong CPU. However, this isn't guaranteed to happen in the 1 second window that the test is running. Besides,

[PATCH AUTOSEL 6.12 2/8] scx: Fix maximal BPF selftest prog

2025-01-06 Thread Sasha Levin
From: David Vernet [ Upstream commit b8f614207b0d5e4abd6df8d5cb3cc11f009d1d93 ] maximal.bpf.c is still dispatching to and consuming from SCX_DSQ_GLOBAL. Let's have it use its own DSQ to avoid any runtime errors. Signed-off-by: David Vernet Tested-by: Andrea Righi Signed-off-by: Tejun Heo Sig

[PATCH AUTOSEL 6.12 1/8] selftests/sched_ext: fix build after renames in sched_ext API

2025-01-06 Thread Sasha Levin
From: Ihor Solodrai [ Upstream commit ef7009decc30eb2515a64253791d61b72229c119 ] The selftests are falining to build on current tip of bpf-next and sched_ext [1]. This has broken BPF CI [2] after merge from upstream. Use appropriate function names in the selftests according to the recent change

Re: [PATCH v2] module: sign with sha512 instead of sha1 by default

2025-01-06 Thread Thorsten Leemhuis
On 06.01.25 15:05, Petr Pavlu wrote: > On 1/4/25 10:43, Thorsten Leemhuis wrote: >> On 20.10.24 00:57, Luis Chamberlain wrote: >>> On Wed, Oct 16, 2024 at 04:18:41PM +0200, Thorsten Leemhuis wrote: Switch away from using sha1 for module signing by default and use the more modern sha512

Re: [PATCH v2] module: sign with sha512 instead of sha1 by default

2025-01-06 Thread Petr Pavlu
On 1/4/25 10:43, Thorsten Leemhuis wrote: > On 20.10.24 00:57, Luis Chamberlain wrote: >> On Wed, Oct 16, 2024 at 04:18:41PM +0200, Thorsten Leemhuis wrote: >>> Switch away from using sha1 for module signing by default and use the >>> more modern sha512 instead, which is what among others Arch, Fed

Re: [PATCH v1 0/3] module: Don't fail module loading when setting ro_after_init section RO failed

2025-01-06 Thread Petr Pavlu
On 1/4/25 08:39, Christophe Leroy wrote: > Le 03/01/2025 à 17:13, Petr Pavlu a écrit : >> On 12/5/24 20:46, Christophe Leroy wrote: >>> This series reworks module loading to avoid leaving the module in a >>> stale state when protecting ro_after_init section fails. >>> >>> Once module init has succe

Re: [RFC net-next] net: mac802154: Remove unused ieee802154_mlme_tx_one

2025-01-06 Thread Dr. David Alan Gilbert
* Stefan Schmidt (ste...@datenfreihafen.org) wrote: > Hello Dave, > > On 30.12.24 18:44, Dr. David Alan Gilbert wrote: > > * Stefan Schmidt (ste...@datenfreihafen.org) wrote: > > > Hello li...@treblig.org. > > > > > > On Wed, 25 Dec 2024 01:24:23 +, li...@treblig.org wrote: > > > > ieee802154

Re: [PATCH v2 1/3] sysfs: constify bin_attribute argument of sysfs_bin_attr_simple_read()

2025-01-06 Thread Madhavan Srinivasan
On 12/28/24 2:13 PM, Thomas Weißschuh wrote: > Most users use this function through the BIN_ATTR_SIMPLE* macros, > they can handle the switch transparently. > Also adapt the two non-macro users in the same change. Changes looks fine to me. Acked-by: Madhavan Srinivasan > > Signed-off-by: Th

Re: [PATCH net 0/2] bond: fix xfrm offload feature during init

2025-01-06 Thread Hangbin Liu
On Thu, Jan 02, 2025 at 11:33:34AM +0800, Jianbo Liu wrote: > > > Re-locking doesn't look great, glancing at the code I don't see any > > > obvious better workarounds. Easiest fix would be to don't let the > > > drivers sleep in the callbacks and then we can go back to a spin lock. > > > Maybe nvid

Re: [PATCH v3] memcg: fix soft lockup in the OOM process

2025-01-06 Thread Vlastimil Babka
On 12/24/24 03:52, Chen Ridong wrote: > From: Chen Ridong +CC RCU > A soft lockup issue was found in the product with about 56,000 tasks were > in the OOM cgroup, it was traversing them when the soft lockup was > triggered. > > watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [VM Thread:150306

Re: [PATCH 2/3] selftests/bpf: Migrate test_xdp_redirect.sh to xdp_do_redirect.c

2025-01-06 Thread Bastien Curutchet
Hi again, On 1/3/25 2:17 PM, Alexis Lothoré wrote: On 1/3/25 11:10, Bastien Curutchet (eBPF Foundation) wrote: test_xdp_redirect.sh can't be used by the BPF CI. + dummy_prog = bpf_object__find_program_by_name(skel_dummy->obj, "xdp_dummy_prog"); Also missed this one: why not using dir

[PATCHv4 RESEND net-next 2/2] selftests: wireguard: update to using nft for qemu test

2025-01-06 Thread Hangbin Liu
Since we will replace iptables with nft for wireguard netns testing, let's also convert the qemu test to use nft at the same time. Co-developed-by: Phil Sutter Signed-off-by: Phil Sutter Signed-off-by: Hangbin Liu --- .../testing/selftests/wireguard/qemu/Makefile | 40 ++- .../

[PATCHv4 RESEND net-next 1/2] selftests: wireguards: convert iptables to nft

2025-01-06 Thread Hangbin Liu
Convert iptabels to nft as it is the replacement for iptables, which is used by default in most releases. Signed-off-by: Hangbin Liu --- tools/testing/selftests/wireguard/netns.sh | 29 ++ 1 file changed, 19 insertions(+), 10 deletions(-) diff --git a/tools/testing/selftests

[PATCHv4 RESEND net-next 0/2] selftests: wireguards: use nftables for testing

2025-01-06 Thread Hangbin Liu
This patch set convert iptables to nftables for wireguard testing, as iptables is deparated and nftables is the default framework of most releases. v3: drop iptables directly (Jason A. Donenfeld) Also convert to using nft for qemu testing (Jason A. Donenfeld) v2: use one nft table for testing

Re: rust/kernel/lib.rs:17:12 : warning: the feature `new_uninit` has been stable since 1.82.0 and no longer requires an attribute to enable

2025-01-06 Thread Naresh Kamboju
On Sun, 5 Jan 2025 at 19:52, Sasha Levin wrote: > > I'm sorry, this is my bad: I haven't realized anyone else will be > looking at these results... > > Naresh, I'm cheating and using this tree to bisect the issue you've > originally reported in > https://lore.kernel.org/all/ca+g9fyvcbvbabg+m7brkfp