On Wed, Jun 11, 2025 at 08:51:17PM -0300, Jason Gunthorpe wrote:
> On Wed, Jun 11, 2025 at 04:43:00PM -0700, Nicolin Chen wrote:
> > So, the test case sets an alignment with HUGEPAGE_SIZE=512MB while
> > allocating buffer_size=64MB:
> > rc = posix_memalign(&self->buffer, HUGEPAGE_SIZE, variant-
On 12.06.25 03:56, Alistair Popple wrote:
On Wed, Jun 11, 2025 at 02:06:52PM +0200, David Hildenbrand wrote:
We setup the cache mode but ... don't forward the updated pgprot to
insert_pfn_pud().
Only a problem on x86-64 PAT when mapping PFNs using PUDs that
require a special cachemode.
Fix it
On Thu, Jun 12, 2025 at 01:32:01PM +0800, Xuewei Niu wrote:
> No comments since last month.
>
> The patch [1], which adds SIOCINQ ioctl support for vsock, depends on this
> patch. Could I get more eyes on this one?
>
> [1]:
> https://lore.kernel.org/lkml/bbn4lvdwh42m2zvi3rdyws66y5ulew32rchtz3kxi
> On Thu, Jun 12, 2025 at 01:32:01PM +0800, Xuewei Niu wrote:
> > No comments since last month.
> >
> > The patch [1], which adds SIOCINQ ioctl support for vsock, depends on this
> > patch. Could I get more eyes on this one?
> >
> > [1]:
> > https://lore.kernel.org/lkml/bbn4lvdwh42m2zvi3rdyws66y
On 12.06.25 06:34, Dan Williams wrote:
David Hildenbrand wrote:
We setup the cache mode but ... don't forward the updated pgprot to
insert_pfn_pud().
Only a problem on x86-64 PAT when mapping PFNs using PUDs that
require a special cachemode.
This is only a problem if the kernel mapped the pud
On 2025/6/12 13:10, Dev Jain wrote:
On 12/06/25 9:24 am, Baolin Wang wrote:
When running the khugepaged selftest for shmem (./khugepaged all:shmem),
I encountered the following test failures:
"
Run test: collapse_full (khugepaged:shmem)
Collapse multiple fully populated PTE table Fail
..
On Mon, Jun 09, 2025 at 03:33:09PM +0800, Cindy Lu wrote:
> This patch introduces functionality to control the vhost worker mode:
>
> - Add two new IOCTLs:
> * VHOST_SET_FORK_FROM_OWNER: Allows userspace to select between
> task mode (fork_owner=1) and kthread mode (fork_owner=0)
> * VHOST
On Mon, Jun 09, 2025 at 03:33:06PM +0800, Cindy Lu wrote:
> In this series, a new UAPI is implemented to allow
> userspace applications to configure their thread mode.
> Changelog v2:
> 1. Change the module_param's name to enforce_inherit_owner, and the default
> value is true.
> 2. Change
Correct the interrupt number of ready and handover in the DTS example.
Fixes: af5da7b0944c ("dt-bindings: remoteproc: qcom,sa8775p-pas: Document the
SA8775p ADSP, CDSP and GPDSP")
Signed-off-by: Lijuan Gao
---
Documentation/devicetree/bindings/remoteproc/qcom,sa8775p-pas.yaml | 2 +-
1 file cha
On Mon, Jun 9, 2025 at 3:34 PM Cindy Lu wrote:
>
> This patch reintroduces kthread mode support in vhost,
> It also introduces struct vhost_worker_ops to abstract
> worker create/stop/wakeup operations.
>
> * Bring back the original vhost_worker() implementation,
> and renamed to vhost_run_work_
On Mon, Jun 9, 2025 at 3:34 PM Cindy Lu wrote:
>
> This patch introduces functionality to control the vhost worker mode:
>
> - Add two new IOCTLs:
> * VHOST_SET_FORK_FROM_OWNER: Allows userspace to select between
> task mode (fork_owner=1) and kthread mode (fork_owner=0)
> * VHOST_GET_FORK
On Mon, Jun 9, 2025 at 3:34 PM Cindy Lu wrote:
>
> The vhost now uses vhost_task and workers as a child of the owner thread.
> While this aligns with containerization principles, it confuses some
> legacy userspace applications, therefore, we are reintroducing kthread
> API support.
>
> Introduce
On 2025/6/12 12:20, Bird, Tim wrote:
collpase in the subject line should be collapse
Good catch. Will fix the typo. Thanks.
-Original Message-
From: Baolin Wang
Subject: [PATCH 2/2] selftests: mm: add shmem collpase as a default test item
Currently, we only test anonymous memory
No comments since last month.
The patch [1], which adds SIOCINQ ioctl support for vsock, depends on this
patch. Could I get more eyes on this one?
[1]:
https://lore.kernel.org/lkml/bbn4lvdwh42m2zvi3rdyws66y5ulew32rchtz3kxirqlllkr63@7toa4tcepax3/#t
Thanks,
Xuewei
On 12/06/25 9:24 am, Baolin Wang wrote:
When running the khugepaged selftest for shmem (./khugepaged all:shmem),
I encountered the following test failures:
"
Run test: collapse_full (khugepaged:shmem)
Collapse multiple fully populated PTE table Fail
...
Run test: collapse_single_pte_entry (
On 12/06/25 9:24 am, Baolin Wang wrote:
Currently, we only test anonymous memory collapse by default. We should also
add shmem collapse as a default test item to catch issues that could break
the test cases.
Signed-off-by: Baolin Wang
---
tools/testing/selftests/mm/run_vmtests.sh | 4
David Hildenbrand wrote:
> Marking PUDs that map a "normal" refcounted folios as special is
> against our rules documented for vm_normal_page().
>
> Fortunately, there are not that many pud_special() check that can be
> mislead and are right now rather harmless: e.g., none so far
> bases decisions
collpase in the subject line should be collapse
-- Tim
> -Original Message-
> From: Baolin Wang
> Subject: [PATCH 2/2] selftests: mm: add shmem collpase as a default test item
>
> Currently, we only test anonymous memory collapse by default. We should also
> add shmem collapse as a def
David Hildenbrand wrote:
> Marking PMDs that map a "normal" refcounted folios as special is
> against our rules documented for vm_normal_page().
>
> Fortunately, there are not that many pmd_special() check that can be
> mislead, and most vm_normal_page_pmd()/vm_normal_folio_pmd() users that
> woul
David Hildenbrand wrote:
> We setup the cache mode but ... don't forward the updated pgprot to
> insert_pfn_pud().
>
> Only a problem on x86-64 PAT when mapping PFNs using PUDs that
> require a special cachemode.
This is only a problem if the kernel mapped the pud in advance of userspace
mapping
Alistair Popple wrote:
> On Wed, Jun 11, 2025 at 02:06:51PM +0200, David Hildenbrand wrote:
> > This is v2 of
> > "[PATCH v1 0/2] mm/huge_memory: don't mark refcounted pages special
> > in vmf_insert_folio_*()"
> > Now with one additional fix, based on mm/mm-unstable.
> >
> > While workin
On Mon, 24 Mar 2025 09:41:00 +0100, Luca Weiss wrote:
> The driver for the SM6350 videocc has been lying around in some branches
> of my git tree for a long time, let's upstream it. It doesn't get any
> better by letting it age!
>
>
Applied, thanks!
[4/4] arm64: dts: qcom: sm6350: Add video c
On Tue, 10 Jun 2025 20:34:51 +0200, Luca Weiss wrote:
> Do some tweaks to the common file for the devices in the 'rhine' family
> of Sony devices, and add a dts for togari.
>
>
Applied, thanks!
[1/4] ARM: dts: qcom: msm8974-sony-xperia-rhine: Enable USB charging
commit: 702639bc50515c97
On Tue, 10 Jun 2025 19:03:48 +0200, Luca Weiss wrote:
> Add an alias for the internal storage so it always becomes mmcblk0 and
> - where applicable - SD card becomes mmcblk1.
>
> This avoids issues with internal storage becoming mmcblk1 unexpectedly
> and aligns this board with other boards that
Currently, we only test anonymous memory collapse by default. We should also
add shmem collapse as a default test item to catch issues that could break
the test cases.
Signed-off-by: Baolin Wang
---
tools/testing/selftests/mm/run_vmtests.sh | 4
1 file changed, 4 insertions(+)
diff --git a
When running the khugepaged selftest for shmem (./khugepaged all:shmem),
I encountered the following test failures:
"
Run test: collapse_full (khugepaged:shmem)
Collapse multiple fully populated PTE table Fail
...
Run test: collapse_single_pte_entry (khugepaged:shmem)
Collapse PTE table with si
On 6/11/25 9:39 AM, Alok Tiwari wrote:
> This patch corrects several minor typos and formatting issues.
> Changes include:
>
> Fixing misspellings like in comments
> - "explict" -> "explicit"
> - "infight" -> "inflight",
> - "with generate" -> "will generate"
>
> formatting in logs
> - Correcting
Change MDSCR_EL1 register holding local variables as uint64_t that reflects
its true register width as well.
Cc: Marc Zyngier
Cc: Oliver Upton
Cc: Joey Gouly
Cc: k...@vger.kernel.org
Cc: kvm...@lists.linux.dev
Cc: linux-kernel@vger.kernel.org
Cc: linux-kselft...@vger.kernel.org
Cc: linux-arm-ke
changed, 6 insertions(+), 6 deletions(-)
---
base-commit: b27cc623e01be9de1580eaa913508b237a7a9673
change-id: 20250611-correct_interrupt_for_remoteproc-9cc1af90abf7
Best regards,
--
Lijuan Gao
+cc (Qi, my colleague who helps testing the modification)
On 2025/6/10 20:23, Frederic Weisbecker wrote:
> Le Mon, Jun 09, 2025 at 02:01:24PM -0400, Joel Fernandes a écrit :
>> During rcu_read_unlock_special(), if this happens during irq_exit(), we
...skipped...
We have tested the below modifica
Fix the incorrect IRQ numbers for ready and handover on sa8775p.
The correct values are as follows:
Fatal interrupt - 0
Ready interrupt - 1
Handover interrupt - 2
Stop acknowledge interrupt - 3
Fixes: df54dcb34ff2e ("arm64: dts: qcom: sa8775p: add ADSP, CDSP and GPDSP
nodes")
Signed-off-by: Liju
On 06/11, Jakub Kicinski wrote:
> On Tue, 10 Jun 2025 10:15:19 -0700 Stanislav Fomichev wrote:
> > Drivers that are using ops lock and don't depend on RTNL lock
> > still need to manage it because udp_tunnel's RTNL dependency.
> > Introduce new udp_tunnel_nic_lock and use it instead of
> > rtnl_loc
On Wed, Jun 11, 2025 at 02:06:53PM +0200, David Hildenbrand wrote:
> Marking PMDs that map a "normal" refcounted folios as special is
> against our rules documented for vm_normal_page().
>
> Fortunately, there are not that many pmd_special() check that can be
> mislead, and most vm_normal_page_pmd
On Wed, Jun 11, 2025 at 02:06:51PM +0200, David Hildenbrand wrote:
> This is v2 of
> "[PATCH v1 0/2] mm/huge_memory: don't mark refcounted pages special
>in vmf_insert_folio_*()"
> Now with one additional fix, based on mm/mm-unstable.
>
> While working on improving vm_normal_page() a
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
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 Wed, Jun 11, 2025 at 02:06:52PM +0200, David Hildenbrand wrote:
> We setup the cache mode but ... don't forward the updated pgprot to
> insert_pfn_pud().
>
> Only a problem on x86-64 PAT when mapping PFNs using PUDs that
> require a special cachemode.
>
> Fix it by using the proper pgprot wher
On Tue, 10 Jun 2025 10:15:19 -0700 Stanislav Fomichev wrote:
> Drivers that are using ops lock and don't depend on RTNL lock
> still need to manage it because udp_tunnel's RTNL dependency.
> Introduce new udp_tunnel_nic_lock and use it instead of
> rtnl_lock. Drop non-UDP_TUNNEL_NIC_INFO_MAY_SLEEP
On Fri, Jun 6, 2025 at 7:50 PM Eugenio Pérez wrote:
>
> Is the expected behavior with vdpa_sim and mlx.
>
> Signed-off-by: Eugenio Pérez
> ---
> drivers/vdpa/vdpa_user/vduse_dev.c | 6 ++
> 1 file changed, 6 insertions(+)
>
Should we squash this into patch 3?
Thanks
On Fri, Jun 6, 2025 at 7:50 PM Eugenio Pérez wrote:
>
> Make one IOTLB domain per address space, and allow the driver to assign
> each ASID to a vq group. Each address space via an dedicated identifier
> (ASID).
>
> During vDPA device allocation, the VDUSE device needs to report the
> number of a
On Wed, Jun 11, 2025 at 04:43:00PM -0700, Nicolin Chen wrote:
> So, the test case sets an alignment with HUGEPAGE_SIZE=512MB while
> allocating buffer_size=64MB:
> rc = posix_memalign(&self->buffer, HUGEPAGE_SIZE, variant->buffer_size);
> vrc = mmap(self->buffer, variant->buffer_size, P
On Wed, Jun 11, 2025 at 02:48:16PM -0700, Nicolin Chen wrote:
> On Wed, Jun 11, 2025 at 10:19:56AM -0700, Nicolin Chen wrote:
> > On Wed, Jun 11, 2025 at 10:04:35AM +0200, Thomas Weißschuh wrote:
> > > On Wed, Jun 11, 2025 at 12:05:25AM -0700, Nicolin Chen wrote:
> > > > 2) parent doesn't seem to w
On Wed, Jun 11, 2025 at 05:44:23PM -0400, Joe Lawrence wrote:
> On 5/9/25 4:17 PM, Josh Poimboeuf wrote:
> > +revert_patches() {
> > + local extra_args=("$@")
> > + local patches=("${APPLIED_PATCHES[@]}")
> > +
> > + for (( i=${#patches[@]}-1 ; i>=0 ; i-- )) ; do
> > + revert_patch
On Wed, 11 Jun 2025 14:06:51 +0200 David Hildenbrand wrote:
> While working on improving vm_normal_page() and friends, I stumbled
> over this issues: refcounted "normal" pages must not be marked
> using pmd_special() / pud_special().
Why is this?
>
> ...
>
> I spent too much time trying to get
Add selftest cases that validate bpftool's expected behavior when
accessing maps protected from modification via security_bpf_map.
The test includes a BPF program attached to security_bpf_map with two maps:
- A protected map that only allows read-only access
- An unprotected map that allows full a
Modify several functions in tools/bpf/bpftool/common.c to allow
specification of requested access for file descriptors, such as
read-only access.
Update bpftool to request only read access for maps when write
access is not required. This fixes errors when reading from maps
that are protected from
> > Modify several functions in tools/bpf/bpftool/common.c to allow
> > specification of requested access for file descriptors, such as
> > read-only access.
> >
> > Update bpftool to request only read access for maps when write
> > access is not required. This fixes errors when reading from maps
>
On 6/11/2025 1:56 PM, Uladzislau Rezki (Sony) wrote:
> Update the documentation about rcu_normal_wake_from_gp parameter.
>
> Signed-off-by: Uladzislau Rezki (Sony)
Reviewed-by: Joel Fernandes
Thanks.
> ---
> Documentation/admin-guide/kernel-parameters.txt | 3 ++-
> 1 file changed, 2 ins
On 6/11/2025 1:56 PM, Uladzislau Rezki (Sony) wrote:
> Automatically enable the rcu_normal_wake_from_gp parameter on
> systems with a small number of CPUs. The activation threshold
> is set to 16 CPUs.
>
> This helps to reduce a latency of normal synchronize_rcu() API
> by waking up GP-waiters
On Wed, Jun 11, 2025 at 10:19:56AM -0700, Nicolin Chen wrote:
> On Wed, Jun 11, 2025 at 10:04:35AM +0200, Thomas Weißschuh wrote:
> > On Wed, Jun 11, 2025 at 12:05:25AM -0700, Nicolin Chen wrote:
> > > 2) parent doesn't seem to wait for the setup() to complete..
> >
> > setup() is called in the ch
> > + make -C tools/bpf/bpftool -s -j"$ncpus" OUTPUT="$output_dir"/ >/dev/null
> > + echo ... finished building bpftool
> > + cd "$pwd"
> > +}
>
>
> Given that you're reusing the BPF selftests infra, you shouldn't have to
> rebuild bpftool as part of the test. It's already built from the
> Ma
On 5/9/25 4:17 PM, Josh Poimboeuf wrote:
> +revert_patches() {
> + local extra_args=("$@")
> + local patches=("${APPLIED_PATCHES[@]}")
> +
> + for (( i=${#patches[@]}-1 ; i>=0 ; i-- )) ; do
> + revert_patch "${patches[$i]}" "${extra_args[@]}"
> + done
> +
> + APPLIED
On Tue, 10 Jun 2025 18:40:45 +0900 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 interface and then confirming that the system
> correctly receives join and removal
From: Ackerley Tng
Adds a selftest to verify interrupts sent to a TDX VM before migration
are successfully handled by the migrated VM.
Co-developed-by: Ryan Afranji
Signed-off-by: Ryan Afranji
Signed-off-by: Ackerley Tng
---
tools/testing/selftests/kvm/Makefile.kvm | 1 +
.../testing/
From: Ackerley Tng
ucalls for non-Coco VMs work by having the guest write to the rdi
register, then perform an io instruction to exit to the host. The host
then reads rdi using kvm_get_regs().
CPU registers can't be read using kvm_get_regs() for TDX, so TDX
guests use MMIO to pass the struct uca
From: Sagi Shahar
Adds selftests for TDX in-place migration.
Signed-off-by: Ryan Afranji
Signed-off-by: Sagi Shahar
---
tools/testing/selftests/kvm/Makefile.kvm | 1 +
.../testing/selftests/kvm/include/kvm_util.h | 20 +
.../selftests/kvm/include/x86/tdx/tdx_util.h | 1 +
tools/te
Refactor the creation and committing of userspace_mem_region to their
own functions so that they can reused by future TDX migration functions.
Signed-off-by: Ryan Afranji
---
tools/testing/selftests/kvm/lib/kvm_util.c | 147 +
1 file changed, 89 insertions(+), 58 deletions(-)
From: Sagi Shahar
Adds the core logic for transferring state between source and
destination TDs during intra-host migration.
Signed-off-by: Sagi Shahar
Co-developed-by: Ryan Afranji
Signed-off-by: Ryan Afranji
---
arch/x86/kvm/vmx/tdx.c | 193 -
1 file
During migration, vCPUs need to be created for an uninitialized VM.
This commit moves the TDX vCPU setup that requires an initialized VM
out of tdx_vcpu_create() and into tdx_td_vcpu_init().
Signed-off-by: Ryan Afranji
---
arch/x86/kvm/vmx/tdx.c | 21 +++--
1 file changed, 11 in
From: Sagi Shahar
Added functionality for moving the mirror EPT table from one TD to a new
one.
This function moves the root of the mirror EPT table and overwrites the
root of the destination.
Signed-off-by: Sagi Shahar
Signed-off-by: Ryan Afranji
---
arch/x86/kvm/mmu.h | 2 ++
arch
From: Sagi Shahar
This should mostly match the logic in sev_vm_move_enc_context_from.
Signed-off-by: Sagi Shahar
Signed-off-by: Ryan Afranji
---
arch/x86/kvm/vmx/main.c| 12 +++-
arch/x86/kvm/vmx/tdx.c | 24
arch/x86/kvm/vmx/x86_ops.h | 1 +
3 files c
Previously, the order for acquiring the locks required for the migration
function move_enc_context_from() was: 1) memslot lock 2) vCPU lock. This
can trigger a deadlock warning because a vCPU IOCTL modifying memslots
will acquire the locks in reverse order: 1) vCPU lock 2) memslot lock.
This patch
From: Sagi Shahar
tdp_mmu_pages counts all the active pages used by the mmu. When we
transfer the state during intra-host migration we need to transfer the
mirror pages but not the direct ones. The direct pages are going to
be re-faulted as needed on the destination, but that approach doesn't
wor
Hello,
This is RFC v2 for the TDX intra-host migration patch series. It
addresses comments in RFC v1 [1] and is rebased onto the latest kvm/next
(v6.16-rc1).
This patchset was built on top of the latest TDX selftests [2] and gmem
linking [3] RFC patch series.
Here is the series stitched together
> > Modify several functions in tools/bpf/bpftool/common.c to allow
> > specification of requested access for file descriptors, such as
> > read-only access.
> >
> > Update bpftool to request only read access for maps when write
> > access is not required. This fixes errors when reading from maps
tics.
>>
>> ERROR: Macros with complex values should be enclosed in parentheses
>> #114: FILE: tools/testing/vsock/util.h:20:
>> +#define _(name, symbol) \
>> +TRANSPORT_##name = BIT(__COUNTER__ - TRANSPORT_COUNTER_BASE),
>>
>> WARNING: Argument 'symbol' is not used in function-like macro
>> #114: FILE: tools/testing/vsock/util.h:20:
>> +#define _(name, symbol) \
>> +TRANSPORT_##name = BIT(__COUNTER__ - TRANSPORT_COUNTER_BASE),
>>
>> WARNING: Argument 'name' is not used in function-like macro
>> #122: FILE: tools/testing/vsock/util.h:28:
>> +#define _(name, symbol) "d " symbol "_transport",
>>
>> Is it ok to ignore this? FWIW, I see the same ERRORs due to similarly used
>> preprocessor directives in fs/bcachefs/alloc_background_format.h, and the
>> same WARNINGs about unused macro arguments in arch/x86/include/asm/asm.h
>> (e.g. __ASM_SEL).
>
> It's just test, so I think it's fine to ignore, but please exaplain it
> in the commit description with also references to other ERRORs/WARNINGs
> like you did here. Let's see what net maintainers think.
Sure, I've added a note. I've also switched the magic macro name '_' to
'x', this seems to be more common.
https://lore.kernel.org/netdev/20250611-vsock-test-inc-cov-v3-0-5834060d9...@rbox.co/
Thanks,
Michal
Increase the coverage of test for UAF due to socket unbinding, and losing
transport in general. It's a follow up to commit 301a62dfb0d0 ("vsock/test:
Add test for UAF due to socket unbinding") and discussion in [1].
The idea remains the same: take an unconnected stream socket with a
transport assi
Increase the coverage of a test implemented in commit 301a62dfb0d0
("vsock/test: Add test for UAF due to socket unbinding"). Take this
opportunity to factor out some utility code, drop a redundant sync between
client and server, and introduce a /proc/kallsyms harvesting logic for
auto-detecting reg
Return a bitmap of registered vsock transports. As guesstimated by grepping
/proc/kallsyms (CONFIG_KALLSYMS=y) for known symbols of type `struct
vsock_transport`, or `struct virtio_transport` in case the vsock_transport
is embedded within.
Note that the way `enum transport` and `transport_ksyms[]`
On Sun, Jun 8, 2025 at 7:38 AM wangfushuai wrote:
>
> When xsend() returns -1 (error), the check 'n < sizeof(buf)' incorrectly
> treats it as success due to unsigned promotion. Explicitly check for -1
> first.
>
> Fixes: a4b7193d8efd ("selftests/bpf: Add sockmap test for redirecting partial
> skb
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Mon, 09 Jun 2025 09:39:24 -0700 you wrote:
> This commit introduces a new vmtest.sh runner for vsock.
>
> It uses virtme-ng/qemu to run tests in a VM. The tests validate G2H,
> H2G, and loopback. The testing tools
On Wed, Jun 11, 2025 at 02:44:35PM -0400, Joe Lawrence wrote:
> > +get_patch_files() {
> > + local patch="$1"
> > +
> > + grep0 -E '^(--- |\+\+\+ )' "$patch" \
> > + | gawk '{print $2}' \
>
> If we split the rest of this line on the tab
Create a socket and bind() it. If binding failed, gracefully return an
error code while preserving `errno`.
Base vsock_bind() on top of it.
Suggested-by: Stefano Garzarella
Reviewed-by: Stefano Garzarella
Signed-off-by: Michal Luczaj
---
tools/testing/vsock/util.c | 24 +--
On Wed, Jun 11, 2025 at 07:47:39PM +0300, Dan Carpenter wrote:
> This seems like a Clang bug, right? The test for _Nullable is reversed
> or something?
My copy of unistd.h has
/* Execute program relative to a directory file descriptor. */
extern int execveat (int __fd, const char *__path, c
On Wed, Jun 11, 2025 at 07:39:21AM -0700, Alok Tiwari wrote:
> This patch corrects several minor typos and formatting issues.
> Changes include:
>
> Fixing misspellings like in comments
> - "explict" -> "explicit"
> - "infight" -> "inflight",
> - "with generate" -> "will generate"
>
> formatting
On Wed, Jun 11, 2025 at 07:39:22AM -0700, Alok Tiwari wrote:
> Use PTR_ERR to return the actual error code when vhost_scsi_make_nexus
> fails to create a session, instead of returning -ENOMEM.
> This ensures more accurate error propagation.
>
> Replace NULL with ERR_PTR(ret) in vhost_scsi_make_tpg
Update the documentation about rcu_normal_wake_from_gp parameter.
Signed-off-by: Uladzislau Rezki (Sony)
---
Documentation/admin-guide/kernel-parameters.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt
b/Documentation/admi
Hi Jiri,
On Wed, Jun 11, 2025 at 3:34 AM Jiri Olsa wrote:
> could this be used in bpftool map dump? ;-) I checked, but it looks like
> bpftool map dump is using something else to dump data.. I admit I haven't
> spent much on time that
I actually started this work by looking at bpftool's dumper,
On Wed, Jun 11, 2025 at 10:50:52AM -0700, Nathan Chancellor wrote:
> On Wed, Jun 11, 2025 at 07:47:39PM +0300, Dan Carpenter wrote:
> > This seems like a Clang bug, right? The test for _Nullable is reversed
> > or something?
>
> My copy of unistd.h has
>
> /* Execute program relative to a dire
On 6/11/25 3:08 PM, Josh Poimboeuf wrote:
> On Wed, Jun 11, 2025 at 02:44:35PM -0400, Joe Lawrence wrote:
>>> +get_patch_files() {
>>> + local patch="$1"
>>> +
>>> + grep0 -E '^(--- |\+\+\+ )' "$patch" \
>>> + | gawk '{print $2}' \
>> If
From: Suresh K C
Refactored the mmap and shmem test logic into a common function
to reduce code duplication and improve maintainability
Changes in v2:
Refactored mmap and shmem tests into a common function
Renamed test function to run_cachestat_test()
Removed test for /proc/cpuinfo a
Automatically enable the rcu_normal_wake_from_gp parameter on
systems with a small number of CPUs. The activation threshold
is set to 16 CPUs.
This helps to reduce a latency of normal synchronize_rcu() API
by waking up GP-waiters earlier and decoupling synchronize_rcu()
callers from regular callba
On 5/9/25 4:17 PM, Josh Poimboeuf wrote:
> Add a klp-build script which automates the generation of a livepatch
> module from a source .patch file by performing the following steps:
>
> - Builds an original kernel with -function-sections and
> -fdata-sections, plus objtool function checksumm
On Wed, Jun 11, 2025 at 09:16:05AM -0700, Paul E. McKenney wrote:
> On Wed, Jun 11, 2025 at 09:05:06AM -0700, Boqun Feng wrote:
> > On Mon, Jun 09, 2025 at 02:01:24PM -0400, Joel Fernandes wrote:
> > > During rcu_read_unlock_special(), if this happens during irq_exit(), we
> > > can lockup if an IP
Queued, thanks.
Paolo
This seems like a Clang bug, right? The test for _Nullable is reversed
or something?
regards,
dan carpenter
On Thu, Jun 05, 2025 at 05:41:01PM +0530, Naresh Kamboju wrote:
> Regressions found on arm, arm64 and x86_64 building warnings with clang-20
> and clang-nightly started from Linux next-202
On Wed, Jun 11, 2025 at 10:04:35AM +0200, Thomas Weißschuh wrote:
> On Wed, Jun 11, 2025 at 12:05:25AM -0700, Nicolin Chen wrote:
> > On Tue, Jun 10, 2025 at 08:46:57PM -0300, Jason Gunthorpe wrote:
> > > On Tue, Jun 10, 2025 at 11:48:44AM -0700, Nicolin Chen wrote:
> > > > On Tue, Jun 10, 2025 at
Hello, Christian!
Imagine my surprise to learn that "make allmodconfig" builds
of the kernel also build userspace components, including
samples/vfs/test-list-all-mounts.c. ;-)
On CentOS, "make allmodconfig" gives a zero exit code, but gets the
following warnings:
In file included from
samples/
Le Mon, Jun 09, 2025 at 02:01:23PM -0400, Joel Fernandes a écrit :
> context_tracking keeps track of whether we're handling IRQ well after
> the preempt masks give take it off their books. We need this
> functionality in a follow-up patch to fix a bug. Provide a helper API
> for the same.
>
> Sign
On Wed, Jun 11, 2025 at 09:33:17AM -0500, Ira Weiny wrote:
> Drew Fustini wrote:
> > On Mon, Jun 09, 2025 at 08:32:41AM -0500, Rob Herring wrote:
> > > On Fri, Jun 06, 2025 at 11:11:17AM -0700, Drew Fustini wrote:
> > > > Convert the PMEM device tree binding from text to YAML. This will allow
> > >
On Mon, Jun 09, 2025 at 02:01:24PM -0400, Joel Fernandes wrote:
> During rcu_read_unlock_special(), if this happens during irq_exit(), we
> can lockup if an IPI is issued. This is because the IPI itself triggers
> the irq_exit() path causing a recursive lock up.
>
> This is precisely what Xiongfen
On Wed, Jun 11, 2025 at 09:05:06AM -0700, Boqun Feng wrote:
> On Mon, Jun 09, 2025 at 02:01:24PM -0400, Joel Fernandes wrote:
> > During rcu_read_unlock_special(), if this happens during irq_exit(), we
> > can lockup if an IPI is issued. This is because the IPI itself triggers
> > the irq_exit() pa
On Tue, Jun 10, 2025 at 03:33:32PM -0400, Joel Fernandes wrote:
>
>
> On 6/10/2025 1:34 PM, Uladzislau Rezki (Sony) wrote:
> > Currently the call_rcu() API does not check whether a callback
> > pointer is NULL. If NULL is passed, rcu_core() will try to invoke
> > it, resulting in NULL pointer der
On Wed, Jun 04, 2025 at 03:19:52AM +, Peng Fan wrote:
> > Subject: [PATCH v4 3/3] remoteproc: imx_rproc: detect and attach to
> > pre-booted remote cores
> >
> > From: Hiago De Franco
> >
> > When the remote core is started before Linux boots (e.g., by the
> > bootloader), the driver current
On Mon, Jun 02, 2025 at 10:19:03AM -0300, Hiago De Franco wrote:
> From: Hiago De Franco
>
> This helper function returns the current power status of a given generic
> power domain.
>
Please correct me if I'm wrong, but this returns the momentary status of
the device's associated genpd, and as
On Wed, Jun 11, 2025 at 3:25 AM Lorenzo Stoakes
wrote:
>
> Thanks for your patient replies :)
>
> OK to save us both time in such a hge back-and-forth - I agree broadly
> with your comments below and I think we are aligned on everything now.
>
> I will try to get you a list of merge scenarios
Hello:
This series was applied to bpf/bpf-next.git (net)
by Daniel Borkmann :
On Mon, 9 Jun 2025 10:08:51 +0800 you wrote:
> Cong reported an issue where running 'test_sockmap' in the current
> bpf-next tree results in an error [1].
>
> The specific test case that triggered the error is a combi
On Wed, Jun 11, 2025 at 04:07:25PM +0200, Luigi Leonardi wrote:
Add a new test to ensure that when the transport changes a null pointer
dereference does not occur. The bug was reported upstream [1] and fixed
with commit 2cb7c756f605 ("vsock/virtio: discard packets if the
transport changes").
KAS
Use PTR_ERR to return the actual error code when vhost_scsi_make_nexus
fails to create a session, instead of returning -ENOMEM.
This ensures more accurate error propagation.
Replace NULL with ERR_PTR(ret) in vhost_scsi_make_tpg to follow kernel
conventions for pointer-returning functions, allowing
This patch corrects several minor typos and formatting issues.
Changes include:
Fixing misspellings like in comments
- "explict" -> "explicit"
- "infight" -> "inflight",
- "with generate" -> "will generate"
formatting in logs
- Correcting log formatting specifier from "%dd" to "%d"
- Adding a mis
1 - 100 of 169 matches
Mail list logo
