On 3/24/2025 2:42 PM, Malaya Kumar Rout wrote:
> Static Analyis for bench_htab_mem.c with cppcheck:error
> tools/testing/selftests/bpf/benchs/bench_htab_mem.c:284:3:
> error: Resource leak: fd [resourceLeak]
> tools/testing/selftests/bpf/prog_tests/sk_assign.c:41:3:
> error: Resource leak: tc [r
On Wed, 2025-03-26 at 17:44 +0100, Frederic Weisbecker wrote:
>
> It's not the first time I get such a report on an out of tree
> kernel. The problem is I don't know if the tainted modules are
> involved. But something is probably making an offline CPU visible
> within
> the hierarchy on get_nohz_
On 3/31/25 7:13 PM, Tejun Heo wrote:
Hello,
On Sun, Mar 30, 2025 at 05:52:39PM -0400, Waiman Long wrote:
...
One possible way to fix this is to iterate the dying cpusets as well and
avoid using the exclusive CPUs in those dying cpusets. However, this
can still cause random partition creation fa
This commit adds a new rcutorture.n_up_down kernel boot parameter
that specifies the number of outstanding SRCU up/down readers, which
begin in kthread context and end in an hrtimer handler. There is a new
kthread ("rcu_torture_updown") that scans an per-reader array looking
for elements whose rea
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski :
On Fri, 28 Mar 2025 15:27:15 +0100 you wrote:
> Here are 4 unrelated patches:
>
> - Patch 1: fix a NULL pointer when two SYN-ACK for the same request are
> handled in parallel. A fix for up to v5.9.
>
> - Patch 2: sel
On Sun, Mar 30, 2025 at 05:52:48PM -0400, Waiman Long wrote:
> The current cgroup directory layout for running the partition state
> transition tests is mainly suitable for testing local partitions as
> well as with a mix of local and remote partitions. It is not that
> suitable for doing extensive
The torture.sh --do-rt command-line parameter is intended to mimic -rt
kernels. Now that CONFIG_PREEMPT_RT is upstream, this commit makes this
mimicking more precise.
Note that testing of RCU priority boosting is disabled in favor
of forward-progress testing of RCU callbacks. If it turns out to
Hello,
On Sun, Mar 30, 2025 at 05:52:39PM -0400, Waiman Long wrote:
...
> One possible way to fix this is to iterate the dying cpusets as well and
> avoid using the exclusive CPUs in those dying cpusets. However, this
> can still cause random partition creation failures or other anomalies
> due to
Hello!
The following series improves testing of SRCU-fast and SRCU up/down,
deprecates SRCU-lite, enables torture.sh to skip non-debug testing,
and adds testing for Rust's RCU bindings. The Rust RCU patch is very
much in RFC state, but I am posting it anyway for wider exposure.
1. Make srcu
The test waits for coredump to finish by busy-waiting for the
stackdump_values file to be created. The maximum wait time is 10 seconds.
This doesn't work for slow machine (qemu-system-riscv64), because coredump
takes longer.
Switch to use waitpid().
With this, the stack_values file doesn't need
On Mon, Mar 31, 2025 at 11:14:10PM +0200, Frederic Weisbecker wrote:
> Le Mon, Mar 31, 2025 at 11:28:47AM -0700, Paul E. McKenney a écrit :
> > > So I'm unfortunately asking again if it wouldn't be a good idea to have a
> > > single
> > > global state counter that lives in the root node so that we
Le Mon, Mar 31, 2025 at 11:28:47AM -0700, Paul E. McKenney a écrit :
> > So I'm unfortunately asking again if it wouldn't be a good idea to have a
> > single
> > global state counter that lives in the root node so that we don't have it
> > duplicated in rcu_state.gp_seq.
> >
> > This involves som
Hello RT-list!
I'm pleased to announce the 5.10.235-rt129 stable release.
While working on the stable update 5.10.235-rt128, a build problem
on the be2net driver was discovered on RT. That inconvenience was
fixed, hence the release of 5.10.235-rt129.
You can get this release via the git tree at:
The down/up SRCU reader testing uses an hrtimer handler to exit the SRCU
read-side critical section. This might be delayed, and if delayed for
too long, it can prevent the rcutorture run from completing. This commit
therefore complains if the hrtimer handler is delayed for more than
ten seconds.
The srcu_lockdep.sh currently blindly trusts the rcutorture SRCU-P
scenario to build its kernel with lockdep enabled. Of course, this
dependency might not be obvious to someone rebalancing SRCU scenarios.
This commit therefore adds code to srcu_lockdep.sh that verifies that
the .config file has lo
Mixing different flavors of RCU readers is forbidden, for example, you
should not use srcu_read_lock() and srcu_read_lock_nmisafe() on the same
srcu_struct structure. There are checks for this, but these checks are
not tested on a regular basis. This commit therefore adds such tests
to srcu_lockd
This commit creates counters in the rcu_torture_one_read_state_updown
structure that check for a call to ->up_read() that lacks a matching
call to ->down_read().
While in the area, add end-of-run cleanup code that prevents calls to
rcu_torture_updown_hrt() from happening after the test has moved o
The rcu_torture_one_read() function is designed for RCU readers that are
confined to a task, such that a single thread of control extends from the
beginning of a given RCU read-side critical section to its end. This does
not suffice for things like srcu_down_read() and srcu_up_read(), where
the cr
On Mon, Mar 31, 2025 at 12:10:58AM +0200, Frederic Weisbecker wrote:
> Le Thu, Mar 27, 2025 at 10:09:48AM -0700, Paul E. McKenney a écrit :
> > On Wed, Mar 26, 2025 at 10:42:52PM +, Joel Fernandes wrote:
> > >
> > >
> > > > On Mar 26, 2025, at 6:33 PM, Paul E. McKenney
> > > > wrote:
> > >
On Fri, Mar 21, 2025 at 02:07:31PM -0400, Gregory Price wrote:
> Device capacity intended for use as system ram should be aligned to the
> architecture-defined memory block size or that capacity will be silently
> truncated and capacity stranded.
>
> As hotplug dax memory becomes more prevelant, t
On Mon, Mar 31, 2025 at 07:26:45AM +, Reshetova, Elena wrote:
> > > > + default:
> > > > + pr_err("EUPDATESVN: unknown error %d\n", ret);
> > > > + break;
> > > > + }
> > >
> > > Overall, I think you're right in that "inversion" does make sense,
> > > now
The test's runtime (nearly 20s) is dangerously close to the limit (30s) on
qemu-system-riscv64:
$ time ./stackdump_test > /dev/null
real0m19.210s
user0m0.077s
sys 0m0.359s
There could be machines slower than qemu-system-riscv64. Therefore raise
the test timeout to 2 minutes to be safe
The buffer pointer "line" is not initialized. This pointer is passed to
getline().
It can still work if the stack is zero-initialized, because getline() can
work with a NULL pointer as buffer.
But this is obviously broken. This bug shows up while running the test on a
riscv64 machine.
Fix it by
2025-03-28, 10:14:27 +0100, Antonio Quartulli wrote:
> Hi Sabrina,
>
> do you plan to drop more comments at the patchset at this point?
Yes, I had a couple of small comments here and there that I didn't
think strictly required a respin, but I'll send them out now since
there'll be more iteration.
From: "Paul E. McKenney"
[ Upstream commit d31e31365b5b6c0cdfc74d71be87234ced564395 ]
Currently, srcu_get_delay() can be called concurrently, for example,
by a CPU that is the first to request a new grace period and the CPU
processing the current grace period. Although concurrent access is
harm
From: "Paul E. McKenney"
[ Upstream commit d31e31365b5b6c0cdfc74d71be87234ced564395 ]
Currently, srcu_get_delay() can be called concurrently, for example,
by a CPU that is the first to request a new grace period and the CPU
processing the current grace period. Although concurrent access is
harm
"Miguel Ojeda" writes:
> On Fri, Mar 21, 2025 at 10:18 AM Andreas Hindborg
> wrote:
>>
>> Add the trait `ParseInt` for parsing string representations of integers
>> where the string representations are optionally prefixed by a radix
>> specifier. Implement the trait for the primitive integer ty
Hi song,
On 10:15 Thu 20 Mar , Song Liu wrote:
> With proper exception boundary detection, it is possible to implment
> arch_stack_walk_reliable without sframe.
>
> Note that, arch_stack_walk_reliable does not guarantee getting reliable
> stack in all scenarios. Instead, it can reliably detec
QE tested this series of v8 with virtio-net regression tests,
everything works fine.
Tested-by: Lei Yang
On Fri, Mar 28, 2025 at 6:04 PM Cindy Lu wrote:
>
> In commit 6e890c5d5021 ("vhost: use vhost_tasks for worker threads"),
> the vhost now uses vhost_task and operates as a child of the
> own
On Fri, Mar 28, 2025 at 05:08:26PM -0600, Shuah Khan wrote:
> On 3/26/25 07:02, Mark Brown wrote:
> > This bug is now in mainline. A fix was posted by Thomas the day after
> > the original report:
> >
> > https://lore.kernel.org/r/20250321-uapi-consistency-v1-1-439070118...@linutronix.de
>
On 10:15 Thu 20 Mar , Song Liu wrote:
> This is largely based on [1] by Suraj Jitindar Singh.
>
> Test coverage:
>
> - Passed manual tests with samples/livepatch.
> - Passed all but test-kprobe.sh in selftests/livepatch.
> test-kprobe.sh is expected to fail, because arm64 doesn't have
> K
On Fri, Mar 21, 2025 at 10:18 AM Andreas Hindborg wrote:
>
> Add the trait `ParseInt` for parsing string representations of integers
> where the string representations are optionally prefixed by a radix
> specifier. Implement the trait for the primitive integer types.
>
> Tested-by: Daniel Almeida
On Thu, Mar 27, 2025 at 06:32:27PM +0100, Thomas Gleixner wrote:
> On Thu, Mar 27 2025 at 16:42, Miroslav Lichvar wrote:
> > On Thu, Mar 27, 2025 at 10:22:31AM +0100, Thomas Gleixner wrote:
> > To clearly see the difference with the new code, I made an attempt
> > to update the old linux-tktest sim
33 matches
Mail list logo
