On 2/19/25 12:16, Sinadin Shan wrote:
The sched tests are missing a target entry and hence out-of-tree build
support.
For instance:
make -C tools/testing/selftests install INSTALL_LOCATION=/foo/bar
is expected to build the sched tests and place them at /foo/bar.
But this is not observed sinc
On Wed, Feb 19, 2025 at 07:33:01PM +, Sumya Hoque wrote:
>
> Signed-off-by: Sumya Hoque
> ---
> tools/testing/selftests/sysctl/sysctl.sh | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/sysctl/sysctl.sh
> b/tools/testing/selftests/sysctl/
On Wed, Feb 19, 2025 at 9:44 AM Song Liu wrote:
>
> On Tue, Feb 18, 2025 at 10:41 AM Josh Poimboeuf wrote:
> >
> > On Tue, Feb 18, 2025 at 10:20:10AM -0800, Song Liu wrote:
> > > Hi Josh,
> > >
> > > On Mon, Feb 17, 2025 at 10:37 PM Josh Poimboeuf
> > > wrote:
> > > >
> > > > On Mon, Feb 17, 20
From: Jason Gunthorpe
The IOMMU translation for MSI message addresses has been a 2-step process,
separated in time:
1) iommu_dma_prepare_msi(): A cookie pointer containing the IOVA address
is stored in the MSI descriptor when an MSI interrupt is allocated.
2) iommu_dma_compose_msi_msg():
Update MAINTAINERS file to reflect changes to Joel's email address for
upstream work.
Signed-off-by: Joel Fernandes
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6ff7ba6cc270..97aba6b60158 100644
--- a/MAINTAINERS
+++ b/
From: Jason Gunthorpe
The two-step process to translate the MSI address involves two functions,
iommu_dma_prepare_msi() and iommu_dma_compose_msi_msg().
Previously iommu_dma_compose_msi_msg() needed to be in the iommu layer as
it had to dereference the opaque cookie pointer. Now, the previous pa
Now that iommufd does not rely on dma-iommu.c for any purpose. We can
combine the dma-iommu.c iova_cookie and the iommufd_hwpt under the same
union. This union is effectively 'owner data' and can be used by the
entity that allocated the domain. Note that legacy vfio type1 flows
continue to use dma-
A "fault_data" was added exclusively for the iommufd_fault_iopf_handler()
used by IOPF/PRI use cases, along with the attach_handle. Now, the iommufd
version of the sw_msi function will reuse the attach_handle and fault_data
for a non-fault case.
Rename "fault_data" to "iommufd_hwpt" so as not to c
From: Jason Gunthorpe
Currently, IRQ_MSI_IOMMU is selected if DMA_IOMMU is available to provide
an implementation for iommu_dma_prepare/compose_msi_msg(). However, it'll
make more sense for irqchips that call prepare/compose to select it, and
that will trigger all the additional code and data to
[ Background ]
On ARM GIC systems and others, the target address of the MSI is translated
by the IOMMU. For GIC, the MSI address page is called "ITS" page. When the
IOMMU is disabled, the MSI address is programmed to the physical location
of the GIC ITS page (e.g. 0x2020). When the IOMMU is ena
From: Jason Gunthorpe
iommufd has a model where the iommu_domain can be changed while the VFIO
device is attached. In this case, the MSI should continue to work. This
corner case has not worked because the dma-iommu implementation of sw_msi
is tied to a single domain.
Implement the sw_msi mappin
From: Jason Gunthorpe
SW_MSI supports IOMMU to translate an MSI message before the MSI message
is delivered to the interrupt controller. On such systems, an iommu_domain
must have a translation for the MSI message for interrupts to work.
The IRQ subsystem will call into IOMMU to request that a p
From: "Dr. David Alan Gilbert"
nd_region_conflict() has been unused since 2019's
commit a3619190d62e ("libnvdimm/pfn: stop padding pmem namespaces to
section alignment")
Remove it, and the region_confict() helper it uses, and the associated
struct conflict_context.
Signed-off-by: Dr. David Alan
From: "Dr. David Alan Gilbert"
nd_attach_ndns() hasn't been used since 2017's
commit 452bae0aede7 ("libnvdimm: fix nvdimm_bus_lock() vs device_lock()
ordering")
Remove it.
Note the __ version is still used and has been left.
Signed-off-by: Dr. David Alan Gilbert
---
drivers/nvdimm/claim.c
From: "Dr. David Alan Gilbert"
Hi,
A couple of nvdimm dead coding patches; they just
remove entirely unused functions.
Signed-off-by: Dr. David Alan Gilbert
Dr. David Alan Gilbert (2):
libnvdimm: Remove unused nd_region_conflict
libnvdimm: Remove unused nd_attach_ndns
drivers/nvdimm/c
On Wed, Feb 19, 2025 at 06:45:07PM -0500, Joel Fernandes wrote:
>
>
> On 2/19/2025 4:07 PM, Kent Overstreet wrote:
> > On Wed, Feb 19, 2025 at 08:29:47AM -0500, Joel Fernandes wrote:
> >>
> >>
> >> On 2/19/2025 8:22 AM, Paul E. McKenney wrote:
> >>> On Wed, Feb 19, 2025 at 07:43:08AM -0500, Joel
On 2/19/2025 4:07 PM, Kent Overstreet wrote:
> On Wed, Feb 19, 2025 at 08:29:47AM -0500, Joel Fernandes wrote:
>>
>>
>> On 2/19/2025 8:22 AM, Paul E. McKenney wrote:
>>> On Wed, Feb 19, 2025 at 07:43:08AM -0500, Joel Fernandes wrote:
poll_state_synchronize_srcu() uses rcu_seq_done() unlike
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko :
On Wed, 19 Feb 2025 20:41:39 +0100 you wrote:
> The kprobe_multi feature was disabled on ARM64 due to the lack of fprobe
> support.
>
> The fprobe rewrite on function_graph has been recently merged and thus
> brought
Hello RT-list!
I'm pleased to announce the 5.10.234-rt126 stable release.
This release is just an update to the new stable 5.10.234 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 Wed, Feb 19, 2025 at 08:29:47AM -0500, Joel Fernandes wrote:
>
>
> On 2/19/2025 8:22 AM, Paul E. McKenney wrote:
> > On Wed, Feb 19, 2025 at 07:43:08AM -0500, Joel Fernandes wrote:
> >> poll_state_synchronize_srcu() uses rcu_seq_done() unlike
> >> poll_state_synchronize_rcu() which uses rcu_se
On Wed, Feb 19, 2025 at 11:20 AM Lorenzo Stoakes
wrote:
>
> On Wed, Feb 19, 2025 at 10:52:04AM -0800, Kalesh Singh wrote:
> > On Wed, Feb 19, 2025 at 1:17 AM Lorenzo Stoakes
> > wrote:
> > >
> > > On Wed, Feb 19, 2025 at 10:15:47AM +0100, David Hildenbrand wrote:
> > > > On 19.02.25 10:03, Lorenz
On Sun, Apr 14, 2024 at 10:05:05PM +0300, Alexey Dobriyan wrote:
As the title says, ban
.
..
and any name containing '/' as they show in sysfs as directory names:
/sys/module/${mod.name}
sysfs tries to mangle the name and make '/' into '!' which kind of work
but not re
This series implements a driver for a virtio-rtc device conforming to spec
proposal v7 [1]. It includes a PTP clock driver and an RTC class driver
with alarm.
v5 updates
==
Important changes compared to the previous driver series [3] are:
- Update to spec proposal v7 [1].
- Fix multiple
---
base-commit: d3417ac824b98e8773bc04b93e09c4b93c2c6cad
change-id: 20250219-enable_kprobe_multi_tests-c8d53336e5cd
Best regards,
--
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Expose the virtio_rtc clocks as PTP clocks to userspace, similar to
ptp_kvm. virtio_rtc can expose multiple clocks, e.g. a UTC clock and a
monotonic clock.
Userspace should distinguish different clocks through the name assigned by
the driver. In particular, UTC-like clocks can also be distinguishe
Expose the virtio-rtc UTC-like clock as an RTC clock to userspace - if it
is present, and if it does not step on leap seconds. The RTC class enables
the virtio-rtc device to resume the system from sleep states on RTC alarm.
Support RTC alarm if the virtio-rtc alarm feature is present. The
virtio-r
Add PTP_SYS_OFFSET_PRECISE2 support on platforms using the Arm Generic
Timer.
Always report the CP15 virtual counter as the HW counter in use by
arm_arch_timer, since the Linux kernel's usage of the Arm Generic Timer
should always be compatible with this.
Signed-off-by: Peter Hilber
---
Notes:
Add the virtio_rtc module and driver core. The virtio_rtc module implements
a driver compatible with the proposed Virtio RTC device specification.
The Virtio RTC (Real Time Clock) device provides information about current
time. The device can provide different clocks, e.g. for the UTC or TAI time
s
Signed-off-by: Sumya Hoque
---
tools/testing/selftests/sysctl/sysctl.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/sysctl/sysctl.sh
b/tools/testing/selftests/sysctl/sysctl.sh
index 84472b436c07..323468653327 100755
--- a/tools/testing/selfte
On Wed, Feb 19, 2025 at 10:52:04AM -0800, Kalesh Singh wrote:
> On Wed, Feb 19, 2025 at 1:17 AM Lorenzo Stoakes
> wrote:
> >
> > On Wed, Feb 19, 2025 at 10:15:47AM +0100, David Hildenbrand wrote:
> > > On 19.02.25 10:03, Lorenzo Stoakes wrote:
> > > > On Wed, Feb 19, 2025 at 12:25:51AM -0800, Kale
On Wed, Feb 19, 2025 at 1:17 AM Lorenzo Stoakes
wrote:
>
> On Wed, Feb 19, 2025 at 10:15:47AM +0100, David Hildenbrand wrote:
> > On 19.02.25 10:03, Lorenzo Stoakes wrote:
> > > On Wed, Feb 19, 2025 at 12:25:51AM -0800, Kalesh Singh wrote:
> > > > On Thu, Feb 13, 2025 at 10:18 AM Lorenzo Stoakes
>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov :
On Wed, 19 Feb 2025 15:52:59 +0100 you wrote:
> Hi all,
>
> Both tc_links.c and tc_opts.c do their tests on the loopback interface.
> It prevents from parallelizing their executions.
>
> Add a new behaviour to t
On Wed, Feb 19, 2025 at 03:04:51AM +, Sumya Hoque wrote:
> Hello everyone,
> Some minor grammer issues that I have fixed:
> 1. echo "If an error every occurs --> echo "If an error occurs, every
> execution
> 2. Example uses --> Example Usage
>
> Signed-off-by: Sumya Hoque
> ---
> tools/te
On Tue, Feb 18, 2025 at 10:41 AM Josh Poimboeuf wrote:
>
> On Tue, Feb 18, 2025 at 10:20:10AM -0800, Song Liu wrote:
> > Hi Josh,
> >
> > On Mon, Feb 17, 2025 at 10:37 PM Josh Poimboeuf wrote:
> > >
> > > On Mon, Feb 17, 2025 at 08:38:22PM -0800, Song Liu wrote:
> > > > On Fri, Feb 14, 2025 at 3:
* Kalesh Singh [250219 03:35]:
> On Wed, Feb 19, 2025 at 12:25 AM Kalesh Singh wrote:
> >
> > On Thu, Feb 13, 2025 at 10:18 AM Lorenzo Stoakes
> > wrote:
> > >
> > > The guard regions feature was initially implemented to support anonymous
> > > mappings only, excluding shmem.
> > >
> > > This wa
On Mon, 17 Feb 2025, Dmitry V. Levin wrote:
> diff --git a/arch/mips/include/asm/syscall.h b/arch/mips/include/asm/syscall.h
> index ea050b23d428..b956b015641c 100644
> --- a/arch/mips/include/asm/syscall.h
> +++ b/arch/mips/include/asm/syscall.h
> @@ -41,6 +41,20 @@ static inline long syscall_get
On 02/19, Bastien Curutchet (eBPF Foundation) wrote:
> Hi all,
>
> Both tc_links.c and tc_opts.c do their tests on the loopback interface.
> It prevents from parallelizing their executions.
>
> Add a new behaviour to the test_progs framework that creates and opens a
> new network namespace to run
> From: Sinadin Shan
> Sent: Wednesday, February 19, 2025 1:46 AM
> To: sh...@kernel.org
> Cc: linux-kselft...@vger.kernel.org; linux-kernel@vger.kernel.org; Chris
> Hyser; Sinadin Shan
> Subject: [PATCH] selftests: sched: add sched as a default selftest target
>
> The sched tests are missing a
On Wed, Feb 19, 2025 at 09:37:23AM -0400, Jason Gunthorpe wrote:
> On Sat, Feb 08, 2025 at 01:02:33AM -0800, Nicolin Chen wrote:
> > iommu: Turn iova_cookie to dma-iommu private pointer
>
> I suggest you respin this with the updates and stop here at this
> patch, it is enough to get the core inf
On Wed, Feb 19, 2025 at 06:58:36AM -0800, Paul E. McKenney wrote:
> On Sat, Feb 15, 2025 at 11:23:45PM +0100, Frederic Weisbecker wrote:
> > Le Sat, Feb 15, 2025 at 02:38:04AM -0800, Paul E. McKenney a écrit :
> > > On Fri, Feb 14, 2025 at 01:10:52PM +0100, Frederic Weisbecker wrote:
> > > > Le Fri
On 2/19/2025 10:18 AM, Boqun Feng wrote:
> On Wed, Feb 19, 2025 at 05:23:08AM -0800, Paul E. McKenney wrote:
>> On Wed, Feb 19, 2025 at 07:54:24AM -0500, Joel Fernandes wrote:
>>> Update MAINTAINERS file to reflect changes to Joel's email address for
>>> upstream work.
>>>
>>> Signed-off-by: Joe
On Wed, Feb 19, 2025 at 05:23:08AM -0800, Paul E. McKenney wrote:
> On Wed, Feb 19, 2025 at 07:54:24AM -0500, Joel Fernandes wrote:
> > Update MAINTAINERS file to reflect changes to Joel's email address for
> > upstream work.
> >
> > Signed-off-by: Joel Fernandes
>
> For RCU and LKMM:
>
> Revie
Am 19.02.25 um 16:06 schrieb Willem de Bruijn:
Marcus Wichelmann wrote:
Am 18.02.25 um 02:47 schrieb Willem de Bruijn:
[...]
This is pointer comparison, which is tricky wrt type. It likely is
ptrdiff_t and thus signed. But may want to use max_t(long int, ..) to
make this explicit.
Ah, I see,
On 2/19/2025 8:58 AM, Paul E. McKenney wrote:
> On Wed, Feb 19, 2025 at 08:25:38AM -0500, Joel Fernandes wrote:
>> On Tue, Feb 18, 2025 at 09:47:27AM -0800, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following issue on:
>>>
>>> HEAD commit:a64dcfb451e2 Linux 6.14-rc2
>>> git tree:
On Sat, Feb 15, 2025 at 11:23:45PM +0100, Frederic Weisbecker wrote:
> Le Sat, Feb 15, 2025 at 02:38:04AM -0800, Paul E. McKenney a écrit :
> > On Fri, Feb 14, 2025 at 01:10:52PM +0100, Frederic Weisbecker wrote:
> > > Le Fri, Feb 14, 2025 at 01:01:56AM -0800, Paul E. McKenney a écrit :
> > > > On
Marcus Wichelmann wrote:
> Am 18.02.25 um 02:47 schrieb Willem de Bruijn:
> > Marcus Wichelmann wrote:
> >> [...]
> >> + metasize = max(xdp->data - xdp->data_meta, 0);
> >
> > Can xdp->data_meta ever be greater than xdp->data?
>
> When an xdp_buff has no metadata support, then this is marked by
Am 18.02.25 um 02:56 schrieb Willem de Bruijn:
Marcus Wichelmann wrote:
[...]
When running the BPF selftests locally, this incorrect assertion was not
an issue, but the BPF kernel-patches CI failed because of this:
open_tuntap:FAIL:open(/dev/net/tun) unexpected open(/dev/net/tun):
actual
Next patch will add a new feature to test_prog to run tests in a
dedicated namespace if the test name starts with 'ns_'. Here the test
name already starts with 'ns_' and creates some namespaces which would
conflict with the new feature.
Rename the test to avoid this conflict.
Signed-off-by: Basti
Tests are serialized because they all use the loopback interface.
Replace the 'serial_test_' prefixes with 'test_ns_' to benefit from the
new test_prog feature which creates a dedicated namespace for each test,
allowing them to run in parallel.
Signed-off-by: Bastien Curutchet (eBPF Foundation)
Two subtests use the test_in_netns() function to run the test in a
dedicated network namespace. This can now be done directly through the
test_progs framework with a test name starting with 'ns_'.
Replace the use of test_in_netns() by test_ns_* calls.
Signed-off-by: Bastien Curutchet (eBPF Founda
Some tests are serialized to prevent interference with others.
Open a dedicated network namespace when a test name starts with 'ns_' to
allow more test parallelization. Use the test name as namespace name to
avoid conflict between namespaces.
Signed-off-by: Bastien Curutchet (eBPF Foundation)
-
ing/selftests/bpf/prog_tests/tc_links.c | 28 ++---
tools/testing/selftests/bpf/prog_tests/tc_opts.c | 40 +-
tools/testing/selftests/bpf/test_progs.c | 12 ++
4 files changed, 63 insertions(+), 64 deletions(-)
---
base-commit: a814b9be27fb3c3f49343aee4b015b76f
Am 18.02.25 um 02:47 schrieb Willem de Bruijn:
Marcus Wichelmann wrote:
[...]
+ metasize = max(xdp->data - xdp->data_meta, 0);
Can xdp->data_meta ever be greater than xdp->data?
When an xdp_buff has no metadata support, then this is marked by setting
xdp->data_meta to xdp->data + 1. Se
On Tue, Feb 18, 2025 at 02:22:51PM -0500, Rafael Aquini wrote:
> From: Rafael Aquini
>
> We noticed that uffd-stress test was always failing to run when invoked
> for the hugetlb profiles on x86_64 systems with a processor count of 64
> or bigger:
> ...
> # ---
On Wed, Feb 19, 2025 at 08:25:38AM -0500, Joel Fernandes wrote:
> On Tue, Feb 18, 2025 at 09:47:27AM -0800, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:a64dcfb451e2 Linux 6.14-rc2
> > git tree:
> > git://git.kernel.org/pub/scm/linux/kernel/
On Sat, Feb 08, 2025 at 01:02:33AM -0800, Nicolin Chen wrote:
> iommu: Turn iova_cookie to dma-iommu private pointer
I suggest you respin this with the updates and stop here at this
patch, it is enough to get the core infrastructure updated and does
not bring any uAPI changes. The remainder can
On 2/19/2025 8:22 AM, Paul E. McKenney wrote:
> On Wed, Feb 19, 2025 at 07:43:08AM -0500, Joel Fernandes wrote:
>> poll_state_synchronize_srcu() uses rcu_seq_done() unlike
>> poll_state_synchronize_rcu() which uses rcu_seq_done_exact().
>>
>> The rcu_seq_done_exact() makes more sense for pollin
On Tue, Feb 18, 2025 at 09:47:27AM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:a64dcfb451e2 Linux 6.14-rc2
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> for-kernelci
> console output: https://syzkaller.appspot.com
On Wed, Feb 19, 2025 at 07:54:24AM -0500, Joel Fernandes wrote:
> Update MAINTAINERS file to reflect changes to Joel's email address for
> upstream work.
>
> Signed-off-by: Joel Fernandes
For RCU and LKMM:
Reviewed-by: Paul E. McKenney
> ---
> MAINTAINERS | 6 +++---
> 1 file changed, 3 inse
On Wed, Feb 19, 2025 at 07:43:08AM -0500, Joel Fernandes wrote:
> poll_state_synchronize_srcu() uses rcu_seq_done() unlike
> poll_state_synchronize_rcu() which uses rcu_seq_done_exact().
>
> The rcu_seq_done_exact() makes more sense for polling API, as with
> this API, there is a higher chance th
poll_state_synchronize_srcu() uses rcu_seq_done() unlike
poll_state_synchronize_rcu() which uses rcu_seq_done_exact().
The rcu_seq_done_exact() makes more sense for polling API, as with
this API, there is a higher chance that there is a significant delay
between the get_state..() and poll_state..
On 07-02-2025 10:16 pm, Ganapatrao Kulkarni wrote:
On 07-02-2025 07:29 pm, Marc Zyngier wrote:
On Fri, 07 Feb 2025 13:26:41 +,
Ganapatrao Kulkarni wrote:
+ if (is_vcpu_nested(vcpu)) {
+ vcpu_set_reg(vcpu, KVM_ARM64_SYS_REG(SYS_CPTR_EL2), fpen);
+ vcpu_set_reg(vcpu,
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, runs in short bursts for some time. During thi
On Tue, 2025-02-18 at 16:45 -0700, Shuah Khan wrote:
>
> Please send v6 with the suggested changes. Also change the commit
> summary to
>
> "selftests/rseq"
Sure, will do. There was actually a V6 already, so I'm sending a V7.
In the meanwhile there was a discussion about the approach. I'm going
On 18.02.25 20:22, Rafael Aquini wrote:
From: Rafael Aquini
We noticed that uffd-stress test was always failing to run when invoked
for the hugetlb profiles on x86_64 systems with a processor count of 64
or bigger:
...
#
# running ./uffd-stress huge
On 19.02.25 10:03, Lorenzo Stoakes wrote:
On Wed, Feb 19, 2025 at 12:25:51AM -0800, Kalesh Singh wrote:
On Thu, Feb 13, 2025 at 10:18 AM Lorenzo Stoakes
wrote:
The guard regions feature was initially implemented to support anonymous
mappings only, excluding shmem.
This was done such as to in
On Wed, Feb 19, 2025 at 10:15:47AM +0100, David Hildenbrand wrote:
> On 19.02.25 10:03, Lorenzo Stoakes wrote:
> > On Wed, Feb 19, 2025 at 12:25:51AM -0800, Kalesh Singh wrote:
> > > On Thu, Feb 13, 2025 at 10:18 AM Lorenzo Stoakes
> > > wrote:
> > > >
> > > > The guard regions feature was initial
On Wed, Feb 19, 2025 at 12:35:12AM -0800, Kalesh Singh wrote:
> On Wed, Feb 19, 2025 at 12:25 AM Kalesh Singh wrote:
> >
> > On Thu, Feb 13, 2025 at 10:18 AM Lorenzo Stoakes
> > wrote:
> > >
> > > The guard regions feature was initially implemented to support anonymous
> > > mappings only, exclud
The core's internal memory data structure will be refactored to be part
of the k3_r5_rproc structure in a future commit. As a result, internal
memory initialization will need to be performed inside
k3_r5_cluster_rproc_init() after rproc_alloc().
Therefore, move the internal memory initialization f
This series aligns the K3 R5 remoteproc's data structures with that of M4 and
DSP data structures, so that common functionalities between R5, DSP, M4 can be
refactored out later[0]. Thanks to Andrew for suggesting this idea[1], however I
have tweaked the implementation a bit, reasoning in Appendix.
Currently, struct members such as mem, num_mems, reset, tsp, ti_sci and
ti_sci_id are part of the k3_r5_core structure. To align the rproc->priv
data structure of the R5 remote processor with that of the DSP and M4,
move the above members from k3_r5_core to k3_r5_rproc.
Additionally, introduce a v
Enable command writing without trailing '\n':
- the good case
$ echo "reset" > /proc/net/pktgen/pgctrl
- the bad case (before the patch)
$ echo -n "reset" > /proc/net/pktgen/pgctrl
-bash: echo: write error: Invalid argument
- with patch applied
$ echo -n "reset
On Wed, Feb 19, 2025 at 12:25:51AM -0800, Kalesh Singh wrote:
> On Thu, Feb 13, 2025 at 10:18 AM Lorenzo Stoakes
> wrote:
> >
> > The guard regions feature was initially implemented to support anonymous
> > mappings only, excluding shmem.
> >
> > This was done such as to introduce the feature care
Fix hex32_arg parsing for short reads (here 7 hex digits instead of the
expected 8), shift result only on successful input parsing.
- before the patch
$ echo "mpls 123" > /proc/net/pktgen/lo\@0
$ grep mpls /proc/net/pktgen/lo\@0
mpls: 1230
Result: OK:
> > + case IMX_RPROC_RESET_CONTROLLER:
> > + priv->reset = devm_reset_control_get_optional_exclusive(dev,
> > NULL);
>
> Is this optional on purpose? There is no mention of it in the commit
> message. Where is this resets property documented in the dt-bindings?
For this particular
Honour the user given buffer size for the strn_len() calls (otherwise
strn_len() will access memory outside of the user given buffer).
Signed-off-by: Peter Seiderer
Reviewed-by: Simon Horman
---
Changes v5 -> v6
- no changes
Changes v4 -> v5
- split up patchset into part i/ii (suggested by
Replace ENOTSUPP with EOPNOTSUPP, fixes checkpatch hint
WARNING: ENOTSUPP is not a SUSV4 error code, prefer EOPNOTSUPP
and e.g.
$ echo "clone_skb 1" > /proc/net/pktgen/lo\@0
-bash: echo: write error: Unknown error 524
Signed-off-by: Peter Seiderer
Reviewed-by: Simon Horman
---
Changes v
Given an invalid 'rate' command e.g. 'rate 0' the return value is '1',
leading to the following misleading output:
- the good case
$ echo "rate 100" > /proc/net/pktgen/lo\@0
$ grep "Result:" /proc/net/pktgen/lo\@0
Result: OK: rate=100
- the bad case (before the patch)
While taking a look at '[PATCH net] pktgen: Avoid out-of-range in
get_imix_entries' ([1]) and '[PATCH net v2] pktgen: Avoid out-of-bounds
access in get_imix_entries' ([2], [3]) and doing some tests and code review
I detected that the /proc/net/pktgen/... parsing logic does not honour the
user given
Given an invalid 'ratep' command e.g. 'ratep 0' the return value is '1',
leading to the following misleading output:
- the good case
$ echo "ratep 100" > /proc/net/pktgen/lo\@0
$ grep "Result:" /proc/net/pktgen/lo\@0
Result: OK: ratep=100
- the bad case (before the patch)
Enable more flexible parameters syntax, allowing 'param=value' in
addition to the already supported 'param value' pattern (additional
this gives the skipping '=' in count_trail_chars() a purpose).
Tested with:
$ echo "min_pkt_size 999" > /proc/net/pktgen/lo\@0
$ echo "min_pkt_size
On Wed, Feb 19, 2025 at 12:25 AM Kalesh Singh wrote:
>
> On Thu, Feb 13, 2025 at 10:18 AM Lorenzo Stoakes
> wrote:
> >
> > The guard regions feature was initially implemented to support anonymous
> > mappings only, excluding shmem.
> >
> > This was done such as to introduce the feature carefully
Hello *,
On Tue, 18 Feb 2025 13:29:05 +, Simon Horman wrote:
> On Mon, Feb 17, 2025 at 09:47:40AM -0800, Jakub Kicinski wrote:
> > On Sun, 16 Feb 2025 09:17:39 + Simon Horman wrote:
> > > On Fri, Feb 14, 2025 at 08:11:45PM -0800, Jakub Kicinski wrote:
> > > > On Thu, 13 Feb 2025 12:00:25
On Thu, Feb 13, 2025 at 10:18 AM Lorenzo Stoakes
wrote:
>
> The guard regions feature was initially implemented to support anonymous
> mappings only, excluding shmem.
>
> This was done such as to introduce the feature carefully and incrementally
> and to be conservative when considering the variou
On Tue, Feb 18, 2025 at 5:56 PM Frank Li wrote:
>
> On Tue, Feb 18, 2025 at 10:57:09AM +0200, Daniel Baluta wrote:
> > Current code supports EARC PHY Software Reset and EARCSoftware
> > Reset but it is not easily extensible to more reset bits.
> >
> > So, refactor the code in order to easi
85 matches
Mail list logo
