On Thu, 19 Jun 2025 at 05:37, Rae Moar wrote:
>
> On Sat, Jun 14, 2025 at 4:47 AM David Gow wrote:
> >
> > From: Ujwal Jain
> >
> > Currently, the in-kernel kunit test case timeout is 300 seconds. (There
> > is a separate timeout mechanism for the whole test execution in
> > kunit.py, but that's
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 kernel config + your
> > hardw
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 anycast notifications.
The test relies on the iproute2 version to be 6.13+.
在 2025/6/19 05:36, Shuah Khan 写道:
On 6/15/25 23:06, Shuai Xue wrote:
The pidfd_test fails on the ARM64 platform with the following error:
Bail out! pidfd_poll check for premature notification on child thread exec
test: Failed
When exception-trace is enabled, the kernel logs the detail
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Mon, 16 Jun 2025 09:21:11 -0700 you wrote:
> Recently bnxt had to grow back a bunch of rtnl dependencies because
> of udp_tunnel's infra. Add separate (global) mutext to protect
> udp_tunnel state.
>
> v5:
> - re
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_premapped in
> + * virtnet_add
On Wed, Jun 18, 2025 at 8:06 PM Nicolas Dichtel
wrote:
>
> Le 16/06/2025 à 08:28, Cindy Lu a écrit :
> > This patch reintroduces kthread mode for vhost workers and provides
> > configuration to select between kthread and task worker.
> >
> > - Add 'fork_owner' parameter to vhost_dev to let users s
On Wed, Jun 18, 2025 at 02:29:37PM -0700, Kees Cook wrote:
On Sat, Jun 14, 2025 at 09:48:39AM -0400, Sasha Levin wrote:
This patch series introduces a framework for formally specifying kernel
APIs, addressing the long-standing challenge of maintaining stable
interfaces between the kernel and use
Thanks for the review feedback, I will move the clean up to a seaparte patch.
On Thu, Jun 19, 2025 at 3:20 AM Simon Horman wrote:
>
> On Wed, Jun 18, 2025 at 07:40:25PM +0900, Yuyang Huang wrote:
> > This commit adds a new kernel selftest to verify RTNLGRP_IPV6_ACADDR
> > notifications. The test
On Fri, May 9, 2025 at 1:30 PM Josh Poimboeuf wrote:
>
> +
> +# Make sure git re-stats the changed files
> +git_refresh() {
> + local patch="$1"
> + local files=()
> +
> + [[ ! -d "$SRC/.git" ]] && return
As a user of git worktrees, my $SRC/.git is a file containing a key:
value
From: Adam Honse
Add support for the touchkeys on the Samsung Galaxy Note 3 (hlte).
Signed-off-by: Adam Honse
Signed-off-by: Luca Weiss
---
Changes in v2:
- Fix schema validation failure, adjust i2c-gpio node name
- Fix misplaced S-o-b (hopefully)
- Link to v1:
https://lore.kernel.org/r/20250
On Sat, Jun 14, 2025 at 4:47 AM David Gow wrote:
>
> From: Ujwal Jain
>
> Currently, the in-kernel kunit test case timeout is 300 seconds. (There
> is a separate timeout mechanism for the whole test execution in
> kunit.py, but that's unrelated.) However, tests marked 'slow' or 'very
> slow' may
On 6/15/25 23:06, Shuai Xue wrote:
The pidfd_test fails on the ARM64 platform with the following error:
Bail out! pidfd_poll check for premature notification on child thread exec
test: Failed
When exception-trace is enabled, the kernel logs the details:
#echo 1 > /proc/sys/debug/exc
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.
What happens if this change isn't made?
The fuse_mnt.c file is
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 value of ‘chdir’ declared
with attribute ‘warn_unused_result’ [-Wunused
On Sat, Jun 14, 2025 at 09:48:39AM -0400, Sasha Levin wrote:
> This patch series introduces a framework for formally specifying kernel
> APIs, addressing the long-standing challenge of maintaining stable
> interfaces between the kernel and user-space programs. As outlined in
> previous discussions
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/testing/selftests/pid_namespace/pid_max.c | 1 +
1 file changed, 1 insertion(+)
d
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 outcomes overflow or underflow, respectively. This
> commit adds selftests
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 ops = param_ops_path(¶m.ptype);
> +
>
Hello RT-list!
I'm pleased to announce the 5.10.238-rt132 stable release.
This release is just an update to the new stable 5.10.238 version and
no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt
On Sun, 15 Jun 2025 22:35:02 +0200, André Apitzsch wrote:
> This dts adds support for BQ Aquaris X5 Plus (Longcheer L9360) released
> in 2016.
>
> Add a device tree with initial support for:
>
> - GPIO keys
> - NFC
> - SDHCI
> - Status LED
> - Touchscreen
>
> [...]
Applied, thanks!
[1/4] arm
On 6/13/25 03:12, Gabriele Monaco wrote:
A task in the kernel (task_mm_cid_work) runs somewhat periodically to
compact the mm_cid for each process. Add a test to validate that it runs
correctly and timely.
The test spawns 1 thread pinned to each CPU, then each thread, including
the main one, run
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 can be found in the link below.
Link:
https://lore.kernel.org/all/CAOQ4uxjKFXOKQxP
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
>
> 2 file
On Thu, 12 Jun 2025 10:39:31 +0800, Lijuan Gao wrote:
> The Ready and Handover interrupt numbers for sa8775p are incorrect. The
> correct interrupt numbers are as follows. So they need to be corrected.
>
> Fatal interrupt - 0
> Ready interrupt - 1
> Handover interrupt - 2
> Stop acknowledge inte
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() {
> +[b'-', rest @ ..] => {
>
On Thu Jun 12, 2025 at 3:40 PM CEST, Andreas Hindborg wrote:
> When we add parameter support to the module macro, we want to be able to
> pass a reference to `ModuleInfo` to a helper function. That is not possible
> when we move out of the local `modinfo`. So change the function to access
> the loc
On Thu Jun 12, 2025 at 3:40 PM CEST, Andreas Hindborg wrote:
> Showcase the rust module parameter support by adding a module parameter to
> the `rust_minimal` sample.
>
> Signed-off-by: Andreas Hindborg
Reviewed-by: Benno Lossin
---
Cheers,
Benno
> ---
> samples/rust/rust_minimal.rs | 10
On Wed, Jun 18, 2025 at 07:40:25PM +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
When operating in split mode, it is a valid usecase to have
only one core enabled in the cluster. Remove exact core count
expecatation from the driver.
Signed-off-by: Tanmay Shah
---
Changes in v3:
- Fix commit message
- Add details about split mode configuration in comment
Change in v2:
On Wed, Jun 18, 2025, at 18:56, Sebastian Andrzej Siewior wrote:
> On 2025-06-18 13:39:46 [-0300], André Almeida wrote:
>>
>> Ops, I forgot to address them. I will do it for v5.
>>
>> > - You say 64bit x86-64 does not have the problem due the compat syscall.
>> >Arm64 has this problem. New ar
On 2025-06-18 13:39:46 [-0300], André Almeida wrote:
>
> Ops, I forgot to address them. I will do it for v5.
>
> > - You say 64bit x86-64 does not have the problem due the compat syscall.
> >Arm64 has this problem. New arm64 do not provide arm32 facility. You
> >introduce the syscall here
Hi Sebastian,
Thanks for the feedback!
Em 18/06/2025 04:08, Sebastian Andrzej Siewior escreveu:
On 2025-06-17 15:34:17 [-0300], André Almeida wrote:
This patch adds a new robust_list() syscall. The current syscall
can't be expanded to cover the following use case, so a new one is
needed. This
On 6/16/25 19:21, Stanislav Fomichev wrote:
> udp_tunnel_push_rx_port will grab mutex in the next patch so
> we can't use rcu. geneve_offload_rx_ports is called
> from geneve_netdevice_event for NETDEV_UDP_TUNNEL_PUSH_INFO and
> NETDEV_UDP_TUNNEL_DROP_INFO which both have ASSERT_RTNL.
> Entries are
On 6/16/25 19:21, Stanislav Fomichev wrote:
> We won't be able to sleep soon in vxlan_offload_rx_ports and won't be
> able to grab sock_lock. Instead of having separate spinlock to
> manage sockets, rely on rtnl lock. This is similar to how geneve
> manages its sockets.
>
> Signed-off-by: Stanisla
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 code, we have to export the
> relevant symbols.
>
> I
Em Wed, 18 Jun 2025 23:27:13 +0900
"Alexandre Courbot" escreveu:
> On Tue Jun 17, 2025 at 7:20 PM JST, Mauro Carvalho Chehab wrote:
> > Em Tue, 17 Jun 2025 11:03:18 +0200
> > Mauro Carvalho Chehab escreveu:
> >
> >> Em Tue, 17 Jun 2025 10:49:38 +0200
> >> Mauro Carvalho Chehab escreveu:
> >>
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 18/06/25 5:27 pm, Lorenzo Stoakes wrote:
On Wed, Jun 18, 2025 at 05:15:50PM +0530, D
Em Wed, 18 Jun 2025 23:16:47 +0900
"Alexandre Courbot" escreveu:
> Hi Mauro,
>
> On Tue Jun 17, 2025 at 5:49 PM JST, Mauro Carvalho Chehab wrote:
> > Hi Alex,
> >
> > Em Tue, 27 May 2025 23:03:39 +0900
> > Alexandre Courbot escreveu:
> >
> >> > > > Btw, I was looking at:
> >> > > >
> >> > > >
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 18/06/25 5:27 pm, Lorenzo Stoakes wrote:
> > > > On Wed, Jun 18, 2025 at 05:15:50PM +0530, Dev Jain wrote:
> > > > Are you
On Wed, Jun 18, 2025 at 03:14:41PM +0530, Souradeep Chowdhury wrote:
> Device awake calls are only present in the recovery path of remoteproc.
This is not the problem, this merely documents a related fact. Might be
worth mention after the problem has been established.
> If an user stops and start
On Tue Jun 17, 2025 at 7:20 PM JST, Mauro Carvalho Chehab wrote:
> Em Tue, 17 Jun 2025 11:03:18 +0200
> Mauro Carvalho Chehab escreveu:
>
>> Em Tue, 17 Jun 2025 10:49:38 +0200
>> Mauro Carvalho Chehab escreveu:
>>
>> > Hi Alex,
>> >
>> > Em Tue, 27 May 2025 23:03:39 +0900
>> > Alexandre Courbot
On 18/06/25 7:37 pm, Lorenzo Stoakes wrote:
On Wed, Jun 18, 2025 at 07:28:16PM +0530, Dev Jain wrote:
On 18/06/25 5:27 pm, Lorenzo Stoakes wrote:
On Wed, Jun 18, 2025 at 05:15:50PM +0530, Dev Jain wrote:
Are you accounting for sys.max_map_count? If not, then you'll be hitting that
first.
run
Hi Mauro,
On Tue Jun 17, 2025 at 5:49 PM JST, Mauro Carvalho Chehab wrote:
> Hi Alex,
>
> Em Tue, 27 May 2025 23:03:39 +0900
> Alexandre Courbot escreveu:
>
>> > > > Btw, I was looking at:
>> > > >
>> > > > https://github.com/chromeos/virtio-media
>> > > >
>> > > > (I'm assuming that this
On Wed, Jun 18, 2025 at 07:28:16PM +0530, Dev Jain wrote:
>
> On 18/06/25 5:27 pm, Lorenzo Stoakes wrote:
> > On Wed, Jun 18, 2025 at 05:15:50PM +0530, Dev Jain wrote:
> > Are you accounting for sys.max_map_count? If not, then you'll be hitting
> > that
> > first.
>
> run_vmtests.sh will run the t
On 18/06/2025 14.26, Petr Pavlu wrote:
> The function move_module() uses the variable t to track how many memory
> types it has allocated and consequently how many should be freed if an
> error occurs.
>
> The variable is initially set to 0 and is updated when a call to
> module_memory_alloc() fai
On 18/06/2025 14.26, Petr Pavlu wrote:
> All error conditions in move_module() set the return value by updating the
> ret variable. Therefore, it is not necessary to the initialize the variable
> when declaring it.
>
> Remove the unnecessary initialization.
>
> Signed-off-by: Petr Pavlu
> Review
On 18/06/25 5:27 pm, Lorenzo Stoakes wrote:
On Wed, Jun 18, 2025 at 05:15:50PM +0530, Dev Jain wrote:
On 18/06/25 5:07 pm, Lorenzo Stoakes wrote:
On Wed, Jun 18, 2025 at 04:58:56PM +0530, Dev Jain wrote:
MAP_CHUNK_SIZE was chosen randomly. Good to see it translates into something
logical :
\
"cr6", "cr7", "xer", "lr", "ctr", "memory"\
); \
- _rval; \
+ _r3;\
})
#else
---
base-commit: 52da431bf03b5506203bca27fe14a97895c80faf
change-id: 20250618-vdso-vdso_call-uninit-ccc33be00568
Best regards,
--
Thomas Weißschuh
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.
Based on (potentially erroneous) hypothesis, you will find a suggestion for an
alternative to the anonymous inode approach,
With CONFIG_MEM_ALLOC_PROFILING=n, vmlinux and all modules unnecessarily
contain the symbols __start_alloc_tags and __stop_alloc_tags, which define
an empty range. In the case of modules, the presence of these symbols also
forces the linker to create an empty .codetag.alloc_tags section.
Update co
On 16/06/2025 23.11, Mina Almasry wrote:
On Mon, Jun 16, 2025 at 2:29 AM Jesper Dangaard Brouer wrote:
On 15/06/2025 22.59, Mina Almasry wrote:
From: Jesper Dangaard Brouer
We frequently consult with Jesper's out-of-tree page_pool benchmark to
evaluate page_pool changes.
Import the bench
Checking transport_{h2g,g2h} != NULL may race with vsock_core_unregister().
Make sure pointers remain valid.
KASAN: null-ptr-deref in range [0x0118-0x011f]
RIP: 0010:vsock_dev_do_ioctl.isra.0+0x58/0xf0
Call Trace:
__x64_sys_ioctl+0x12d/0x190
do_syscall_64+0x92/0x1c0
entr
transport_{h2g,g2h,dgram,local} may become NULL on vsock_core_unregister().
Make sure a poorly timed `rmmod transport` won't lead to a NULL/stale
pointer dereference.
Note that these oopses are pretty unlikely to happen in the wild. Splats
were collected after sprinkling kernel with mdelay()s.
Si
Function may race with vsock_core_unregister(): transport_g2h may become
NULL after the NULL check. Protect from a potential null-ptr-deref.
KASAN: null-ptr-deref in range [0x0118-0x011f]
RIP: 0010:vsock_find_cid+0x47/0x90
Call Trace:
__vsock_bind+0x4b2/0x720
vsock_bind+0
On Wed, Jun 18, 2025 at 01:31:09AM +0530, ALOK TIWARI wrote:
>
>
> Thanks Simon,
>
> On 6/18/2025 12:07 AM, Simon Horman wrote:
> > On Sun, Jun 15, 2025 at 10:39:11AM -0700, Alok Tiwari wrote:
> > > This patch fixes multiple typos and improves comment clarity across
> > > vhost.c.
> > > - Correc
Transport assignment may race with module unload. Protect new_transport
from becoming a stale pointer.
This also takes care of an insecure call in vsock_use_local_transport();
add a lockdep assert.
BUG: unable to handle page fault for address: fbfff8056000
Oops: Oops: [#1] SMP KASAN
RIP:
All error conditions in move_module() set the return value by updating the
ret variable. Therefore, it is not necessary to the initialize the variable
when declaring it.
Remove the unnecessary initialization.
Signed-off-by: Petr Pavlu
Reviewed-by: Sami Tolvanen
---
kernel/module/main.c | 3 +--
The function move_module() uses the variable t to track how many memory
types it has allocated and consequently how many should be freed if an
error occurs.
The variable is initially set to 0 and is updated when a call to
module_memory_alloc() fails. However, move_module() can fail for other
reaso
The first patch is an actual fix. The second patch is a minor related
cleanup.
Changes since v1 [1]:
- Initialize t to MOD_MEM_NUM_TYPES in move_module(), instead of assigning
the value later.
- Merge the definitions of the variables i and ret in move_module().
[1]
https://lore.kernel.org/linu
On Tue, 17 Jun 2025 at 21:36, Hiago De Franco wrote:
>
> From: Hiago De Franco
>
> When the remote core is started before Linux boots (e.g., by the
> bootloader), the driver currently is not able to attach because it only
> checks for cores running in different partitions. If the core was kicked
Le 16/06/2025 à 08:28, Cindy Lu a écrit :
> This patch reintroduces kthread mode for vhost workers and provides
> configuration to select between kthread and task worker.
>
> - Add 'fork_owner' parameter to vhost_dev to let users select kthread
> or task mode. Default mode is task mode(VHOST_FOR
On Wed, Jun 18, 2025 at 12:57:38PM +0100, Lorenzo Stoakes wrote:
> Are you accounting for sys.max_map_count? If not, then you'll be hitting that
> first.
* vm.max_map_count
On Wed, Jun 18, 2025 at 05:15:50PM +0530, Dev Jain wrote:
>
> On 18/06/25 5:07 pm, Lorenzo Stoakes wrote:
> > On Wed, Jun 18, 2025 at 04:58:56PM +0530, Dev Jain wrote:
> > > MAP_CHUNK_SIZE was chosen randomly. Good to see it translates into
> > > something logical : )
> > >
> > > So I guess I am c
On Wed, Jun 18, 2025 at 12:37:29PM +0100, Lorenzo Stoakes wrote:
> On Wed, Jun 18, 2025 at 04:58:56PM +0530, Dev Jain wrote:
> >
> > MAP_CHUNK_SIZE was chosen randomly. Good to see it translates into
> > something logical : )
> >
To correct myself for being an idiot before, 256 x 4 KB is 1 MB not
On 18/06/25 5:07 pm, Lorenzo Stoakes wrote:
On Wed, Jun 18, 2025 at 04:58:56PM +0530, Dev Jain wrote:
MAP_CHUNK_SIZE was chosen randomly. Good to see it translates into something
logical : )
So I guess I am correct, if we can find two VMAs (except at the edge of the
high addr boundary)
with
On Wed, Jun 18, 2025 at 04:58:56PM +0530, Dev Jain wrote:
>
> MAP_CHUNK_SIZE was chosen randomly. Good to see it translates into something
> logical : )
>
> So I guess I am correct, if we can find two VMAs (except at the edge of the
> high addr boundary)
> with a gap of greater than MAP_CHUNK_SIZ
On 18/06/25 4:52 pm, Lorenzo Stoakes wrote:
On Mon, Jun 16, 2025 at 09:57:10PM +0530, Dev Jain wrote:
On 16/06/25 9:36 pm, Aboorva Devarajan wrote:
From: Donet Tom
3./proc/self/maps may not always have gaps smaller than MAP_CHUNK_SIZE.
The gap between the first high address mapping and the p
On Tue, Jun 17, 2025 at 04:46:57PM -0700, Nicolin Chen wrote:
> On Tue, Jun 17, 2025 at 08:01:36PM -0300, Jason Gunthorpe wrote:
> > On Tue, Jun 17, 2025 at 02:23:41PM -0700, Nicolin Chen wrote:
> > > On Tue, Jun 17, 2025 at 08:59:48AM -0300, Jason Gunthorpe wrote:
> > > > On Mon, Jun 16, 2025 at 0
Add tests for NUMA memory policy binding and NUMA aware allocation in
guest_memfd. This extends the existing selftests by adding proper
validation for:
- KVM GMEM set_policy and get_policy() vm_ops functionality using
mbind() and get_mempolicy()
- NUMA policy application before and after memory a
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 code, we have to export the
relevant symbols.
In the future, guest_memfd might be moved to core-mm, at which point the
sy
Previously, guest-memfd allocations followed local NUMA node id in absence
of process mempolicy, resulting in arbitrary memory allocation.
Moreover, mbind() couldn't be used by the VMM as guest memory wasn't
mapped into userspace when allocation occurred.
Enable NUMA policy support by implementin
Add dedicated inode structure (kvm_gmem_inode_info) and slab-allocated
inode cache for guest memory backing, similar to how shmem handles inodes.
This adds the necessary allocation/destruction functions and prepares
for upcoming guest_memfd NUMA policy support changes.
Signed-off-by: Shivank Garg
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 callers to specify a NUMA policy during page cache
alloca
From: Ackerley Tng
guest_memfd's inode represents memory the guest_memfd is
providing. guest_memfd's file represents a struct kvm's view of that
memory.
Using a custom inode allows customization of the inode teardown
process via callbacks. For example, ->evict_inode() allows
customization of the
KVM guest_memfd is implementing its own inodes to store metadata for
backing memory using a custom filesystem. This requires the ability to
allocate an anonymous inode with security context using
anon_inode_make_secure_inode().
As guest_memfd currently resides in the KVM module, we need to export
This series introduces NUMA-aware memory placement support for KVM guests
with guest_memfd memory backends. It builds upon Fuad Tabba's work that
enabled host-mapping for guest_memfd memory [1] and can be applied directly
on KVM tree (branch:queue, base commit:7915077245) [2].
== Background ==
KV
On Mon, Jun 16, 2025 at 09:57:10PM +0530, Dev Jain wrote:
>
> On 16/06/25 9:36 pm, Aboorva Devarajan wrote:
> > From: Donet Tom
> > 3./proc/self/maps may not always have gaps smaller than MAP_CHUNK_SIZE.
> > The gap between the first high address mapping and the previous mapping
> > is not smaller
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 anycast notifications.
The test relies on the iproute2 version to be 6.13+.
On 18/06/25 3:36 pm, Donet Tom wrote:
On Mon, Jun 16, 2025 at 09:57:10PM +0530, Dev Jain wrote:
Hi Dev
On 16/06/25 9:36 pm, Aboorva Devarajan wrote:
From: Donet Tom
In this patch, we are fixing three issues in the virtual_address_range
test.
1. validate_addr() checks if the allocated addr
Sorry, please ignore this patch. Accidentally send the old patch again.
On Wed, Jun 18, 2025 at 7:32 PM Yuyang Huang wrote:
>
> This commit adds a new kernel selftest to verify RTNLGRP_IPV4_MCADDR
> and RTNLGRP_IPV6_MCADDR notifications. The test works by adding and
> removing a dummy interf
This commit adds a new kernel selftest to verify RTNLGRP_IPV4_MCADDR
and RTNLGRP_IPV6_MCADDR notifications. The test works by adding and
removing a dummy interface and then confirming that the system
correctly receives join and removal notifications for the 224.0.0.1
and ff02::1 multicast addresses
On Mon, Jun 16, 2025 at 09:57:10PM +0530, Dev Jain wrote:
>
Hi Dev
> On 16/06/25 9:36 pm, Aboorva Devarajan wrote:
> > From: Donet Tom
> >
> > In this patch, we are fixing three issues in the virtual_address_range
> > test.
> >
> > 1. validate_addr() checks if the allocated address is within
On Tue Jun 17, 2025 at 5:22 PM UTC, Peter Xu wrote:
> ERROR: munmap (errno=22, @uffd-common.c:277)
Looks the same as what I reported here:
https://lore.kernel.org/all/daitjkyrqmfd.olouws7up...@google.com/
> Ujwal, can you reproduce these issues and have a look?
The script I mentioned in that ot
Device awake calls are only present in the recovery path of remoteproc.
If an user stops and starts rproc by using the sysfs interface, then on
pm suspension the firmware fails to load as the request_firmware call
under adsp_load relies on usermodehelper process which gets freezed on
pm suspension.
Add a call to dev_dstats_rx_dropped_add() in nsim_queue_free() to
account for the number of packets dropped when purging the skb queue.
This improves the accuracy of RX drop statistics reported by netdevsim.
local_bh_{disable, enable}() protection is used to disable preemption,
which is necessary
Introduce the dev_dstats_rx_dropped_add() helper to allow incrementing
the rx_drops per-CPU statistic by an arbitrary value, rather than just
one. This is useful for drivers or code paths that need to account for
multiple dropped packets at once, such as when dropping entire queues.
Reviewed-by: J
When the RX side of netdevsim was added, the RX statistics were missing,
making the driver unusable for GenerateTraffic() test framework.
This patch adds proper statistics tracking on RX side, complementing the
TX path.
Reviewed-by: Joe Damato
Signed-off-by: Breno Leitao
---
drivers/net/netdev
Replace custom statistics tracking with the kernel's dstats infrastructure
to simplify code and improve consistency with other network drivers.
This change:
- Sets dev->pcpu_stat_type = NETDEV_PCPU_STAT_DSTATS for automatic
automatic allocation and deallocation.
- Removes manual stats fields and
The netdevsim driver previously lacked RX statistics support, which
prevented its use with the GenerateTraffic() test framework, as this
framework verifies traffic flow by checking RX byte counts.
This patch migrates netdevsim from its custom statistics collection to
the NETDEV_PCPU_STAT_DSTATS fr
On Mon, Jun 16, 2025 at 09:21:13AM -0700, Stanislav Fomichev wrote:
> We won't be able to sleep soon in vxlan_offload_rx_ports and won't be
> able to grab sock_lock. Instead of having separate spinlock to
> manage sockets, rely on rtnl lock. This is similar to how geneve
> manages its sockets.
>
>
On 2025-06-17 15:34:17 [-0300], André Almeida wrote:
> This patch adds a new robust_list() syscall. The current syscall
> can't be expanded to cover the following use case, so a new one is
> needed. This new syscall allows users to set multiple robust lists per
> process and to have either 32bit or
92 matches
Mail list logo
