On Mon, Jun 9, 2025 at 7:51 AM Christoph Hellwig wrote:
>
> Before you add new features to vduse, please remove the broken abuse of
> the DMA API first. Without that no new feature work should go into
> this code.
>
Hi Christoph,
This code does not touch the DMA API at all. Actually, we could e
This patch has been successfully tested. All the khugepaged shmem tests passed.
# ./khugepaged khugepaged:shmem
Save THP and khugepaged settings... OK
Allocate huge page on fault... OK
Split huge PMD on MADV_DONTNEED... OK
Run test: collapse_full (khugepaged:shmem)
Collapse multiple fully populat
On 6/19/2025 9:33 PM, Matthew Wilcox wrote:
> On Wed, Jun 18, 2025 at 11:29:31AM +, Shivank Garg wrote:
>> From: Shivansh Dhiman
>>
>> Add NUMA mempolicy support to the filemap allocation path by introducing
>> new APIs that take a mempolicy argument:
>> - filemap_grab_folio_mpol()
>> - fil
Hi Joel,
kernel test robot noticed the following build errors:
[auto build test ERROR on rcu/rcu/dev]
[also build test ERROR on linus/master v6.16-rc2 next-20250619]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--bas
When running `make kselftest`, the following compilation warning was
encountered:
mount-notify_test.c: In function ‘fanotify_rmdir’:
mount-notify_test.c:490:17: warning: ignoring return value of ‘chdir’ declared
with attribute ‘warn_unused_result’ [-Wunused-result]
490 | chdir(
When build kernel selftests on Ubuntu 24.04, I got a compiler error:
mount-notify_test.c:22:3: error: conflicting types for ‘__kernel_fsid_t’; have
‘struct ’
22 | } __kernel_fsid_t;
| ^~~
In file included from .../linux/usr/include/asm/posix_types_64.h:18,
On Fri, Jun 20, 2025 at 1:02 AM Shuah Khan wrote:
>
> On 6/19/25 01:43, Chen Linxuan wrote:
> > On Thu, Jun 19, 2025 at 5:21 AM Shuah Khan
> > wrote:
> >>
> >> On 6/9/25 20:05, Chen Linxuan wrote:
> >>> When writing a test for fusectl, I referred to this Makefile as a
> >>> reference for creatin
On Fri, Jun 20, 2025 at 5:41 AM Shuah Khan wrote:
>
> On 6/19/25 13:00, John Hubbard wrote:
> > On 6/19/25 10:00 AM, Shuah Khan wrote:
> >> On 6/19/25 01:46, Chen Linxuan wrote:
> >>> On Thu, Jun 19, 2025 at 5:23 AM Shuah Khan
> >>> wrote:
> On 6/9/25 20:07, Chen Linxuan wrote:
> > ...
> >>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Wed, 18 Jun 2025 01:32:41 -0700 you wrote:
> The netdevsim driver previously lacked RX statistics support, which
> prevented its use with the GenerateTraffic() test framework, as this
> framework verifies traffic
On Thu, Jun 19, 2025 at 5:55 PM Eduard Zingerman wrote:
>
> On Thu, 2025-06-19 at 17:13 -0400, Harishankar Vishwanathan wrote:
> > On Wed, Jun 18, 2025 at 5:22 PM Eduard Zingerman wrote:
> > >
> > > On Tue, 2025-06-17 at 19:17 -0400, Harishankar Vishwanathan wrote:
[...]
> Hm, I see, that's an in
On Thu, 2025-06-19 at 17:13 -0400, Harishankar Vishwanathan wrote:
> On Wed, Jun 18, 2025 at 5:22 PM Eduard Zingerman wrote:
> >
> > On Tue, 2025-06-17 at 19:17 -0400, Harishankar Vishwanathan wrote:
> > > The previous commit improves the precision in scalar(32)_min_max_add,
> > > and scalar(32)_
On 6/19/25 15:40, Shuah Khan wrote:
On 6/19/25 13:00, John Hubbard wrote:
On 6/19/25 10:00 AM, Shuah Khan wrote:
On 6/19/25 01:46, Chen Linxuan wrote:
On Thu, Jun 19, 2025 at 5:23 AM Shuah Khan wrote:
On 6/9/25 20:07, Chen Linxuan wrote:
...
diff --git a/tools/testing/selftests/filesystems
On 6/19/25 13:00, John Hubbard wrote:
On 6/19/25 10:00 AM, Shuah Khan wrote:
On 6/19/25 01:46, Chen Linxuan wrote:
On Thu, Jun 19, 2025 at 5:23 AM Shuah Khan wrote:
On 6/9/25 20:07, Chen Linxuan wrote:
...
diff --git a/tools/testing/selftests/filesystems/mount-notify/mount-
notify_test.c b
On Wed, Jun 18, 2025 at 5:22 PM Eduard Zingerman wrote:
>
> On Tue, 2025-06-17 at 19:17 -0400, Harishankar Vishwanathan wrote:
> > The previous commit improves the precision in scalar(32)_min_max_add,
> > and scalar(32)_min_max_sub. The improvement in precision occurs in
> > cases when all outcome
Module aliases are used by userspace to identify the correct module to
load for a detected hardware. The currently supported RPMSG device IDs for
this module include "rpmsg-raw", but the module alias is "rpmsg_chrdev".
Use the helper macro MODULE_DEVICE_TABLE(rpmsg) to export the correct
supported
Le 19/06/2025 à 21:04, Abhinav Ananthu a écrit :
I apologize for the mistake in the signed-off email address in the previous
patch.
Convert the debugfs show() functions in remoteproc_debugfs.c to use
sysfs_emit() instead of scnprintf(). The sysfs_emit() helper is the
preferred way to format sys
I apologize for the mistake in the signed-off email address in the previous
patch.
Convert the debugfs show() functions in remoteproc_debugfs.c to use
sysfs_emit() instead of scnprintf(). The sysfs_emit() helper is the
preferred way to format sysfs output as it ensures the output is
properly boun
On 6/19/25 10:00 AM, Shuah Khan wrote:
On 6/19/25 01:46, Chen Linxuan wrote:
On Thu, Jun 19, 2025 at 5:23 AM Shuah Khan
wrote:
On 6/9/25 20:07, Chen Linxuan wrote:
...
diff --git a/tools/testing/selftests/filesystems/mount-notify/mount-
notify_test.c b/tools/testing/selftests/filesystems/mou
Convert the debugfs show() functions in remoteproc_debugfs.c to use
sysfs_emit() instead of scnprintf(). The sysfs_emit() helper is the
preferred way to format sysfs output as it ensures the output is
properly bounded to PAGE_SIZE and simplifies the code.
This patch addresses three instances of sc
There was a memory leak bug in DAMOS sysfs memcg_path file. Add a
selftest to ensure the bug never comes back.
Signed-off-by: SeongJae Park
---
tools/testing/selftests/damon/Makefile| 1 +
.../selftests/damon/sysfs_memcg_path_leak.sh | 43 +++
2 files changed, 44 inser
Users can leak memory by repeatedly writing a string to DAMOS sysfs
memcg_path file. Fix it (patch 1) and add a selftest (patch 2) to avoid
reoccurrance of the bug.
SeongJae Park (2):
mm/damon/sysfs-schemes: free old damon_sysfs_scheme_filter->memcg_path
on write
selftets/damon: add a tes
From: Jesper Dangaard Brouer
We frequently consult with Jesper's out-of-tree page_pool benchmark to
evaluate page_pool changes.
Import the benchmark into the upstream linux kernel tree so that (a)
we're all running the same version, (b) pave the way for shared
improvements, and (c) maybe one day
Add two new refscale test cases to compare the performance of
traditional local_irq_disable()/local_irq_enable() with the newer
local_interrupt_disable()/local_interrupt_enable() APIs.
The local_interrupt_disable()/local_interrupt_enable() APIs are
introduced to provide a Rust-compatible interface
Add two new refscale test cases to compare the performance of
traditional local_irq_disable()/local_irq_enable() with the newer
local_interrupt_disable()/local_interrupt_enable() APIs.
The local_interrupt_disable()/local_interrupt_enable() APIs are
introduced to provide a Rust-compatible interface
On 6/19/25 01:46, Chen Linxuan wrote:
On Thu, Jun 19, 2025 at 5:23 AM Shuah Khan wrote:
On 6/9/25 20:07, Chen Linxuan wrote:
When running `make kselftest`, the following compilation warning was
encountered:
mount-notify_test.c: In function ‘fanotify_rmdir’:
mount-notify_test.c:490:17: warni
On Thu, Jun 19, 2025 at 9:58 AM Jakub Kicinski wrote:
>
> On Thu, 19 Jun 2025 08:37:05 -0700 Mina Almasry wrote:
> > Jakub, this patch was marked 'changes requested' for good reason, but
> > after investigation we found the patch itself is good and the issues
> > were elsewhere. What do I do here?
On 6/19/25 01:43, Chen Linxuan wrote:
On Thu, Jun 19, 2025 at 5:21 AM Shuah Khan wrote:
On 6/9/25 20:05, Chen Linxuan wrote:
When writing a test for fusectl, I referred to this Makefile as a
reference for creating a FUSE daemon in the selftests.
While doing so, I noticed that there is a minor
On Thu, 19 Jun 2025 08:37:05 -0700 Mina Almasry wrote:
> Jakub, this patch was marked 'changes requested' for good reason, but
> after investigation we found the patch itself is good and the issues
> were elsewhere. What do I do here? A resend of v4? Or does this un
> 'changes requested' as-is?
Do
On 6/19/25 13:13, Shivank Garg wrote:
>
>
> On 6/18/2025 8:42 PM, Gregory Price wrote:
>> On Wed, Jun 18, 2025 at 11:29:32AM +, Shivank Garg wrote:
>>> KVM guest_memfd wants to implement support for NUMA policies just like
>>> shmem already does using the shared policy infrastructure. As
>>>
On 12/06/2025 16.53, Thomas WeiÃschuh wrote:
> The struct was moved to the public header file in
> commit c8e21ced08b3 ("module: fix kdb's illicit use of struct module_use.").
> Back then the structure was used outside of the module core.
> Nowadays this is not true anymore, so the structure can be
On Fri, 20 Jun 2025 01:13:28 +0900 Masahiro Yamada wrote:
> > IIUC you made the kernel spew nearly 5000 warnings on every W=1 build
> > to "encourage" others to help fix a fairly innocuous problem.
> > I appreciate the work that goes into separating the headers but it's
> > hardly urgent enough to
On 19/06/25 9:01 pm, Donet Tom wrote:
eOn Thu, Jun 19, 2025 at 02:32:19PM +0530, Dev Jain wrote:
On 19/06/25 1:53 pm, Donet Tom wrote:
On Wed, Jun 18, 2025 at 08:13:54PM +0530, Dev Jain wrote:
On 18/06/25 8:05 pm, Lorenzo Stoakes wrote:
On Wed, Jun 18, 2025 at 07:47:18PM +0530, Dev Jain wro
On Fri, Jun 20, 2025 at 1:01 AM Jakub Kicinski wrote:
>
> On Sun, 1 Jun 2025 22:31:29 +0900 Masahiro Yamada wrote:
> > The problem was described in commit 5b20755b7780 ("init: move THIS_MODULE
> > from to ").
> >
> > To summarize it again here: is included by most C files,
> > even though only
On Sun, 1 Jun 2025 22:31:29 +0900 Masahiro Yamada wrote:
> The problem was described in commit 5b20755b7780 ("init: move THIS_MODULE
> from to ").
>
> To summarize it again here: is included by most C files,
> even though only some of them actually export symbols. This is because
> some headers
On Wed, Jun 18, 2025 at 11:29:31AM +, Shivank Garg wrote:
> From: Shivansh Dhiman
>
> Add NUMA mempolicy support to the filemap allocation path by introducing
> new APIs that take a mempolicy argument:
> - filemap_grab_folio_mpol()
> - filemap_alloc_folio_mpol()
> - __filemap_get_folio_mpol()
On Thu, Jun 19, 2025 at 3:24 AM Jesper Dangaard Brouer wrote:
> > Does this alleviate your concern? Or do you still see an issue here?
> > There is still a delta between our results, on different
> > hardware/configs but results are in a sane range now.
>
> Now the results a sane and in range :-)
eOn Thu, Jun 19, 2025 at 02:32:19PM +0530, Dev Jain wrote:
>
> On 19/06/25 1:53 pm, Donet Tom wrote:
> > On Wed, Jun 18, 2025 at 08:13:54PM +0530, Dev Jain wrote:
> > > On 18/06/25 8:05 pm, Lorenzo Stoakes wrote:
> > > > On Wed, Jun 18, 2025 at 07:47:18PM +0530, Dev Jain wrote:
> > > > > On 18/06/
On Thu, 19 Jun 2025 21:17:03 +0700 Bui Quang Minh wrote:
> > I think Michael mention he's AFK so while we wait could you fix this
> > kdoc? I'm not sure whether the kdoc is really necessary here, but if
> > you want to keep it you have to document the return value:
> >
> > Warning: drivers/net/virt
On 6/18/25 13:29, Shivank Garg wrote:
> From: Shivansh Dhiman
>
> Add NUMA mempolicy support to the filemap allocation path by introducing
> new APIs that take a mempolicy argument:
> - filemap_grab_folio_mpol()
> - filemap_alloc_folio_mpol()
> - __filemap_get_folio_mpol()
>
> These APIs allow c
Hi Arnaud,
Thanks for review.
On Wed, Jun 18, 2025 at 03:07:36PM +0200, Arnaud POULIQUEN wrote:
> Hello Dawei,
>
>
> Please find a few comments below. It is not clear to me which parts of your
> implementation are mandatory and which are optional "nice-to-have"
> optimizations.
It's more like
With a rootfs built using libbpf's BPF CI [1], we can run specific tests
as follows:
$ ../libbpf-ci/rootfs/mkrootfs_debian.sh --arch ppc64el --distro noble
$ PLATFORM=ppc64el CROSS_COMPILE=powerpc64le-linux-gnu- \
tools/testing/selftests/bpf/vmtest.sh \
-l libbpf-vmtest-rootfs-*-noble-ppc6
On 6/19/25 09:11, Jakub Kicinski wrote:
On Sun, 15 Jun 2025 22:13:32 +0700 Bui Quang Minh wrote:
+/**
+ * buf_to_xdp() - convert the @buf context to xdp_buff
+ * @vi: virtnet_info struct
+ * @rq: the receive queue struct
+ * @buf: the xdp_buff pointer that is passed to virtqueue_add_inbuf_premap
On Thu Jun 12, 2025 at 3:40 PM CEST, Andreas Hindborg wrote:
> +/// A wrapper for kernel parameters.
> +///
> +/// This type is instantiated by the [`module!`] macro when module
> parameters are
> +/// defined. You should never need to instantiate this type directly.
> +///
> +/// Note: This type
On Thu Jun 19, 2025 at 2:20 PM CEST, Andreas Hindborg wrote:
> "Benno Lossin" writes:
>> On Thu Jun 12, 2025 at 3:40 PM CEST, Andreas Hindborg wrote:
>>> +
>>> +// SAFETY: C kernel handles serializing access to this type. We never
>>> access it
>>> +// from Rust module.
>>> +unsafe impl Sync for
"Benno Lossin" writes:
> On Thu Jun 19, 2025 at 1:12 PM CEST, Andreas Hindborg wrote:
>> I'm having a difficult time parsing. Are you suggesting that we guard
>> against implementations of `TryInto` that misbehave?
>
> Let me try a different explanation:
>
> The safety requirement for implementin
"Benno Lossin" writes:
> On Thu Jun 12, 2025 at 3:40 PM CEST, Andreas Hindborg wrote:
>> +
>> +fn emit_params(&mut self, info: &ModuleInfo) {
>> +let Some(params) = &info.params else {
>> +return;
>> +};
>> +
>> +for param in params {
>> +let op
On Thu Jun 19, 2025 at 1:12 PM CEST, Andreas Hindborg wrote:
> I'm having a difficult time parsing. Are you suggesting that we guard
> against implementations of `TryInto` that misbehave?
Let me try a different explanation:
The safety requirement for implementing the `FromStrRadix`:
/// The
"Benno Lossin" writes:
> On Thu Jun 12, 2025 at 3:40 PM CEST, Andreas Hindborg wrote:
>> Add types and traits for interfacing the C moduleparam API.
>>
>> Signed-off-by: Andreas Hindborg
>> ---
>> rust/kernel/lib.rs | 1 +
>> rust/kernel/module_param.rs | 201
>>
On Thu, 19 Jun 2025 10:40:15 +0100,
Ganapatrao Kulkarni wrote:
>
>
> [Sorry for late reply]
>
> On 5/29/2025 5:18 PM, Marc Zyngier wrote:
> > On Thu, 29 May 2025 11:29:58 +0100,
> > Ganapatrao Kulkarni wrote:
> >>
> >>
> >> Hi Eric,
> >>
> >> On 5/28/2025 6:58 PM, Eric Auger wrote:
> >>> Hi
On 6/18/2025 8:42 PM, Gregory Price wrote:
> On Wed, Jun 18, 2025 at 11:29:32AM +, Shivank Garg wrote:
>> KVM guest_memfd wants to implement support for NUMA policies just like
>> shmem already does using the shared policy infrastructure. As
>> guest_memfd currently resides in KVM module cod
"Benno Lossin" writes:
> On Thu Jun 12, 2025 at 3:40 PM CEST, Andreas Hindborg wrote:
>> +pub trait ParseInt: private::FromStrRadix + TryFrom {
>> +/// Parse a string according to the description in [`Self`].
>> +fn from_str(src: &BStr) -> Result {
>> +match src.deref() {
>> +
On Thu, Jun 19, 2025 at 12:51:16PM +0900, Yuyang Huang wrote:
> This commit adds a new kernel selftest to verify RTNLGRP_IPV6_ACADDR
> notifications. The test works by adding/removing a dummy interface,
> enabling packet forwarding, and then confirming that user space can
> correctly receive anycas
On 19/06/2025 06.19, Mina Almasry wrote:
On Wed, Jun 18, 2025 at 5:46 AM Jesper Dangaard Brouer wrote:
Something is off with benchmark numbers compared to the OOT version.
I assume you're comparing my results (my kernel config + my hardware +
upstream benchmark) with your results (your ke
On Thu, 12 Jun 2025 17:40:29 +0800, Chen Linxuan wrote:
> This patch add a simple functional test for the "abort" file
> in fusectlfs (/sys/fs/fuse/connections/ID/about).
>
> A simple fuse daemon is added for testing.
>
> Related discussion can be found in the link below.
>
> [...]
Applied to t
On Wed, Jun 18, 2025 at 02:52:08PM -0600, Shuah Khan wrote:
> On 6/12/25 03:40, Chen Linxuan wrote:
> > This patch add a simple functional test for the "abort" file
> > in fusectlfs (/sys/fs/fuse/connections/ID/about).
> >
> > A simple fuse daemon is added for testing.
> >
> > Related discussion
[Sorry for late reply]
On 5/29/2025 5:18 PM, Marc Zyngier wrote:
On Thu, 29 May 2025 11:29:58 +0100,
Ganapatrao Kulkarni wrote:
Hi Eric,
On 5/28/2025 6:58 PM, Eric Auger wrote:
Hi Ganapatrao,
On 5/12/25 12:52 PM, Ganapatrao Kulkarni wrote:
This patch series makes the selftest work with
On 19/06/25 1:53 pm, Donet Tom wrote:
On Wed, Jun 18, 2025 at 08:13:54PM +0530, Dev Jain wrote:
On 18/06/25 8:05 pm, Lorenzo Stoakes wrote:
On Wed, Jun 18, 2025 at 07:47:18PM +0530, Dev Jain wrote:
On 18/06/25 7:37 pm, Lorenzo Stoakes wrote:
On Wed, Jun 18, 2025 at 07:28:16PM +0530, Dev Jai
On Wed, Jun 18, 2025 at 08:13:54PM +0530, Dev Jain wrote:
>
> On 18/06/25 8:05 pm, Lorenzo Stoakes wrote:
> > On Wed, Jun 18, 2025 at 07:47:18PM +0530, Dev Jain wrote:
> > > On 18/06/25 7:37 pm, Lorenzo Stoakes wrote:
> > > > On Wed, Jun 18, 2025 at 07:28:16PM +0530, Dev Jain wrote:
> > > > > On 1
On Thu, Jun 19, 2025 at 5:23 AM Shuah Khan wrote:
>
> On 6/9/25 20:07, Chen Linxuan wrote:
> > When running `make kselftest`, the following compilation warning was
> > encountered:
> >
> > mount-notify_test.c: In function ‘fanotify_rmdir’:
> > mount-notify_test.c:490:17: warning: ignoring return
On Thu, Jun 19, 2025 at 5:21 AM Shuah Khan wrote:
>
> On 6/9/25 20:05, Chen Linxuan wrote:
> > When writing a test for fusectl, I referred to this Makefile as a
> > reference for creating a FUSE daemon in the selftests.
> > While doing so, I noticed that there is a minor issue in the Makefile.
>
>
On Fri, Jun 06, 2025 at 09:55:11AM +0800, Peng Fan (OSS) wrote:
>i.MX95 features a Cortex-M33 core, six Cortex-A55 cores, and
>one Cortex-M7 core. The System Control Management Interface(SCMI)
>firmware runs on the M33 core. The i.MX95 SCMI firmware named System
>Manager(SM) includes vendor extensi
On Tue, Jun 17, 2025 at 04:34:47PM -0300, Hiago De Franco wrote:
>From: Hiago De Franco
>
>This patch series depends on Ulf's patches that are currently under
>review, "pmdomain: Add generic ->sync_state() support to genpd" [1].
>Without them, this series is not going to work.
>
>For the i.MX8X an
On Thu, Jun 19, 2025 at 5:25 AM Shuah Khan wrote:
>
> On 6/9/25 20:08, Chen Linxuan wrote:
> > I failed to build this test on Ubuntu 24.04.
> > Compiler complained about undefined functions mount, umount and some
> > mount related flags.
> >
> > Signed-off-by: Chen Linxuan
> > ---
> > tools/tes
On Thu, Jun 19, 2025 at 5:25 AM Shuah Khan wrote:
>
> On 6/9/25 20:08, Chen Linxuan wrote:
> > I failed to build this test on Ubuntu 24.04.
> > Compiler complained about undefined functions mount, umount and some
> > mount related flags.
> >
> > Signed-off-by: Chen Linxuan
> > ---
> > tools/tes
64 matches
Mail list logo
