[PATCH] clone3: clone3_cap_checkpoint_restore: remove unused MAX_PID_NS_LEVEL macro

The macro MAX_PID_NS_LEVEL is never referenced in the code, so remove it. Signed-off-by: Ba Jing --- tools/testing/selftests/clone3/clone3_cap_checkpoint_restore.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/tools/testing/selftests/clone3/clone3_cap_checkpoint_restore.c b/tools/testing

[PATCH v2] kselftests: mm: Fix wrong __NR_userfaultfd value

grep -rnIF "#define __NR_userfaultfd" tools/include/uapi/asm-generic/unistd.h:681:#define __NR_userfaultfd 282 arch/x86/include/generated/uapi/asm/unistd_32.h:374:#define __NR_userfaultfd 374 arch/x86/include/generated/uapi/asm/unistd_64.h:327:#define __NR_userfaultfd 323 arch/x86/include/generated

Re: [PATCH 1/2] kselftests: mm: Fix wrong __NR_userfaultfd value

... >> grep -rnIF "#define __NR_userfaultfd" >> tools/include/uapi/asm-generic/unistd.h:681:#define __NR_userfaultfd 282 >> arch/x86/include/generated/uapi/asm/unistd_32.h:374:#define >> __NR_userfaultfd 374 >> arch/x86/include/generated/uapi/asm/unistd_64.h:327:#define >> __NR_userfaultfd 323 >>

Re: [RFC 00/31] objtool, livepatch: Livepatch module generation

On 2024/9/12 0:20, Josh Poimboeuf wrote: ... Do not get me wrong. I do not expect that the upstream variant would be feature complete from the beginning. I just want to get a picture how far it is. The code will be maintained only when it would have users. And it would have users only when it

Re: [RESEND PATCH v1 0/7]vhost: Add support of kthread API

On Thu, 12 Sept 2024 at 10:11, Jason Wang wrote: > > > > On Thu, Sep 12, 2024 at 12:17 AM Mike Christie > wrote: >> >> On 9/10/24 10:45 PM, Jason Wang wrote: >> >>> It depends on how we define "secure". There's plenty of users of >> >>> kthread and if I was not wrong, mike may still need to fix

Re: [PATCH] mailbox, remoteproc: omap2+: fix compile testing

On Mon, Sep 9, 2024 at 3:38 PM Arnd Bergmann wrote: > > From: Arnd Bergmann > > Selecting CONFIG_OMAP2PLUS_MBOX while compile testing > causes a build failure: > > WARNING: unmet direct dependencies detected for OMAP2PLUS_MBOX > Depends on [n]: MAILBOX [=y] && (ARCH_OMAP2PLUS || ARCH_K3) > Se

[PATCH 1/1] lib/crc16_kunit.c: add KUnit tests for crc16

Add Kunit tests for the kernel's implementation of the standard CRC-16 algorithm (). The test data consists of 100 randomly-generated test cases, validated against a reference implementation. This implementation follows roughly the same logic as lib/crc32test.c, but without the performance measure

[PATCH 0/1] Add KUnit tests for lib/crc16.c

Hi all, This patch was developed during a hackathon organized by LKCAMP [1], with the objective of writing KUnit tests, both to introduce people to the kernel development process and to learn about different subsystems (with the positive side effect of improving the kernel test coverage, of course

Re: [PATCH v1 5/5] remoteproc: add support for Microchip IPC remoteproc platform driver

On 18/09/2024 17:51, valentina.fernandezala...@microchip.com wrote: > On 16/09/2024 21:18, Krzysztof Kozlowski wrote: >> EXTERNAL EMAIL: Do not click links or open attachments unless you know the >> content is safe >> >> On 12/09/2024 19:00, Valentina Fernandez wrote: >>> The Microchip family of R

Re: [PATCH v2 1/5] dt-bindings: remoteproc: sse710: Add the External Systems remote processors

On 19/09/2024 11:35, Abdellatif El Khlifi wrote: > Hi Krzysztof, > >>> Add devicetree binding schema for the External Systems remote processors >>> >>> The External Systems remote processors are provided on the Corstone-1000 >>> IoT Reference Design Platform via the SSE-710 subsystem. >>> >>> For

Re: [RFC PATCH v2 1/3] ipv4: Support setting src port in sendmsg().

Le ven. 20 sept. 2024 à 19:03, Tiago Lam a écrit : > > sendmsg() doesn't currently allow users to set the src port from which > egress traffic should be sent from. This is possible if a user wants to > configure the src address from which egress traffic should be sent from > - with the IP_PKTINFO

[PATCH] Revert "list: test: fix tests for list_cut_position()"

This reverts commit e620799c414a035dea1208bcb51c869744931dbb. The commit introduces unit test failures. Expected cur == &entries[i], but cur == 037fffadfd80 &entries[i] == 037fffadfd60 # list_test_list_cut_position: pass:0 fail:1 skip:0 total:1 not ok 21 l

Re: [PATCH v2 7/7] kunit, slub: add test_kfree_rcu() and test_leak_destroy()

On 9/21/24 23:16, Hyeonggon Yoo wrote: On Sun, Sep 22, 2024 at 6:25 AM Vlastimil Babka wrote: On 9/21/24 23:08, Guenter Roeck wrote: On 9/21/24 13:40, Vlastimil Babka wrote: +CC kunit folks On 9/20/24 15:35, Guenter Roeck wrote: Hi, Hi, On Wed, Aug 07, 2024 at 12:31:20PM +0200, Vlastim

Re: [PATCH 1/1] remoteproc: Use iommu_paging_domain_alloc()

On 29-08-2024 11:47, Beleswar Prasad Padhi wrote: Hi All, On 22/08/24 21:47, Mathieu Poirier wrote: Hi Baolu, Sorry for the late reply, this slipped through the cracks. On Mon, Aug 12, 2024 at 03:28:11PM +0800, Lu Baolu wrote: > An iommu domain is allocated in rproc_enable_iommu() and is a

[RFC PATCH v1 1/1] hpref: Hazard Pointers with Reference Counter

Boqun Feng's patch series and LPC talk gave me a few ideas I wanted to try. I figured we could improve the concept of reference counters by adding a hazard-pointer protected fast-path to them. This API combines hazard pointers and reference counters. It uses hazard pointers as fast-paths, and fall

Re: [PATCH bpf-next v2] selftests/bpf: convert test_xdp_features.sh to test_progs

Hello all, sorry for the slow feedback, I have been off last week. On 9/14/24 15:38, Jakub Kicinski wrote: > On Sat, 14 Sep 2024 11:25:47 +0200 Lorenzo Bianconi wrote: >> On Sep 13, Martin KaFai Lau wrote: >>> test a physical network device that supports a certain XDP features. >>> >>> iiuc, test_

Re: [PATCH bpf-next v2 1/2] bpf: verifier: Support eliding map lookup nullness

On Fri, Sep 20, 2024 at 03:05:35PM GMT, Eduard Zingerman wrote: > On Sun, 2024-09-15 at 21:45 -0600, Daniel Xu wrote: > > This commit allows progs to elide a null check on statically known map > > lookup keys. In other words, if the verifier can statically prove that > > the lookup will be in-bound

Re: [RFC PATCH 1/1] hpref: Hazard Pointers with Reference Counter

On 2024-09-21 23:07, Lai Jiangshan wrote: +/* + * hpref_hp_get: Obtain a reference to a stable object, protected either + * by hazard pointer (fast-path) or using reference + * counter as fall-back. + */ +static inline +bool hpref_hp_get(struct hpref_node **node_p, str