On Fri, 14 Mar 2025 at 03:27, Rae Moar wrote:
>
> Add test to check for the infinite loop caused by the inability
> to parse a late test plan.
>
> The test parses the following output:
> TAP version 13
> ok 4 test4
> 1..4
>
> Signed-off-by: Rae Moar
> ---
Reviewed-by: David Gow
Cheers,
-- D
On Fri, 14 Mar 2025 at 03:27, Rae Moar wrote:
>
> A bug was identified where the KTAP below caused an infinite loop:
>
> TAP version 13
> ok 4 test_case
> 1..4
>
> The infinite loop was caused by the parser not parsing a test plan
> if following a test result line.
>
> Fix this bug by parsing t
A bug was identified where the KTAP below caused an infinite loop:
TAP version 13
ok 4 test_case
1..4
The infinite loop was caused by the parser not parsing a test plan
if following a test result line.
Fix this bug by parsing test plan line to avoid the infinite loop.
Signed-off-by: Rae Moar
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko :
On Tue, 11 Mar 2025 14:16:47 +0530 you wrote:
> The SO_RCVLOWAT option is defined as 18 in the selftest header,
> which matches the generic definition. However, on powerpc,
> SO_RCVLOWAT is defined as 16. This discrep
On Thu, Mar 13, 2025 at 10:13:23PM +, Nikita Kalyazin wrote:
> Yes, that's right, mmap() + memcpy() is functionally sufficient. write() is
> an optimisation. Most of the pages in guest_memfd are only ever accessed by
> the vCPU (not userspace) via TDP (stage-2 pagetables) so they don't need
>
On 13/03/2025 19:12, Peter Xu wrote:
On Thu, Mar 13, 2025 at 03:25:16PM +, Nikita Kalyazin wrote:
On 12/03/2025 19:32, Peter Xu wrote:
On Wed, Mar 12, 2025 at 05:07:25PM +, Nikita Kalyazin wrote:
However if MISSING is not registered, the kernel will auto-populate with a
clear page
This series adds support for the FocalTech FT8716 touchscreen to the
edt-ft5x06 driver. It was tested on the BQ Aquaris X (bq-bardock) and BQ
Aquaris X Pro (bq-bardockpro).
Jens Reidel (2):
dt-bindings: input: touchscreen: edt-ft5x06: Document FT8716 support
Input: edt-ft5x06 - add support for
On Tue, Mar 11, 2025 at 12:43:57AM +0530, Sahil Siddiq wrote:
> Add cacheinfo support for OpenRISC.
>
> Currently, a few CPU cache attributes pertaining to OpenRISC processors
> are exposed along with other unrelated CPU attributes in the procfs file
> system (/proc/cpuinfo). However, a few cache
This driver is compatible with the FocalTech FT8716 touchscreen, which
supports up to 10 concurrent touch points. Add a compatible for it.
Signed-off-by: Jens Reidel
---
drivers/input/touchscreen/edt-ft5x06.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/input/touchscreen/edt
Document FocalTech FT8716 support by adding the compatible.
Signed-off-by: Jens Reidel
---
.../devicetree/bindings/input/touchscreen/edt-ft5x06.yaml| 1 +
1 file changed, 1 insertion(+)
diff --git
a/Documentation/devicetree/bindings/input/touchscreen/edt-ft5x06.yaml
b/Documentation/de
ups, but none of the
obvious things seem to work. Worst-case, I don't think it'd be a
_problem_ to make EFI + AMD_MEM_ENCRYPT the default for the
x86_64/qemu KUnit configuration.
I tried again starting with a clean linux_next repo next-20250313
- Ran tests first
- Built allmodconfi
On 12.03.25 11:17 AM, I Hsin Cheng wrote:
> Currenyly the implementation of "Guard" methods are basically wrappers
> around rcu's function within kernel. Building the kernel with llvm
> 18.1.8 on x86_64 machine will generate the following symbols:
>
> $ nm vmlinux | grep ' _R'.*Guard | rustfilt
>
ALU sanitization was introduced to ensure that a subsequent ptr access
can never go OOBs, even under speculation. This is required because we
currently allow speculative scalar confusion. This is the case because
Spectre v4 sanitization only adds a nospec after critical stores (e.g.,
scalar overwri
On Thu, Mar 13, 2025 at 11:12 AM Breno Leitao wrote:
>
> On Fri, Mar 07, 2025 at 05:27:41PM -0800, 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 ge
On Thu, Feb 01, 2024 at 07:57:45PM +0100, Harald Mommer wrote:
> Hello,
>
> I thought there would be some more comments coming and I could address
> everything in one chunk. Not the case, besides your comments silence.
>
> On 08.01.24 20:34, Christophe JAILLET wrote:
> >
> > Hi,
> > a few nits b
On Fri, Mar 07, 2025 at 05:27:41PM -0800, 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
On Fri, Mar 07, 2025 at 05:27:42PM -0800, 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 do
On Thu, Mar 13, 2025 at 10:16 AM Kent Overstreet
wrote:
>
> On Thu, Mar 13, 2025 at 03:29:20PM +0100, Petr Pavlu wrote:
> > 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
This trades verification complexity for runtime overheads due to the
nospec inserted because of the EINVAL.
With increased limits this allows applying mitigations to large BPF
progs such as the Parca Continuous Profiler's prog. However, this
requires a jump-seq limit of 256k. In any case, the same
On Thu, Mar 13, 2025 at 05:31:11PM +, Ajay Kaher wrote:
> For VMware hypervisor, SEV-SNP enabled VM's could boot without UEFI.
VMs
mingo, pls fix up while applying.
> In this case, mpparse_find_mptable() has to be called to parse MP
> tables which contains boot information.
>
> Fixes: 0f4a1
Main reason is, that it will later allow us to fall back to a nospec for
certain errors in push_stack().
This changes the sanitization-case to returning -ENOMEM. However, this
is more fitting as -EFAULT would indicate a verifier-internal bug.
Signed-off-by: Luis Gerhorst
Acked-by: Henriette Herz
Insert a nospec before the access to prevent it from ever using an index
that is subject to speculative scalar-confusion.
Signed-off-by: Luis Gerhorst
Acked-by: Henriette Herzog
Cc: Maximilian Ott
Cc: Milan Stephan
---
kernel/bpf/verifier.c | 24
1 file changed, 12 in
This implements the core of the series and causes the verifier to fall
back to mitigating Spectre v1 using speculation barriers. The approach
was presented at LPC'24 [1] and RAID'24 [2].
This has the unfortunate consequence that Spectre v1 mitigations now
only support architectures which implement
This is made to clarify that this flag will cause a nospec to be added
after this insn and can therefore be relied upon to reduce speculative
path analysis.
Signed-off-by: Luis Gerhorst
Cc: Henriette Herzog
Cc: Maximilian Ott
Cc: Milan Stephan
---
include/linux/bpf_verifier.h | 2 +-
kernel/b
JITs can set bpf_jit_bypass_spec_v1/v4() if they want the verifier to
skip analysis/patching for the respective vulnerability. For v4, this
will reduce the number of barriers the verifier inserts. For v1, it
allows more programs to be accepted.
The primary motivation for this is to not regress unp
This prevents us from trying to recover from these on speculative paths
in the future.
Signed-off-by: Luis Gerhorst
Acked-by: Henriette Herzog
Cc: Maximilian Ott
Cc: Milan Stephan
---
kernel/bpf/verifier.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/bpf/ve
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
This changes the semantics of BPF_NOSPEC (previously a v4-only barrier)
to always emit a speculation barrier that works against both Spectre v1
AND v4. If mitigation is not needed on an architecture, the backend
should set bpf_jit_bypass_spec_v4/v1().
As of now, this commit only has the user-visib
For platforms using the Arm Generic Timer, add precise cross-timestamping
support to virtio_rtc.
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 H
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
This series implements a driver for a virtio-rtc device conforming to spec
proposal v8 [1]. It includes a PTP clock driver and an RTC class driver
with alarm.
v6 updates
==
v6 fixes the PTP clock name length, and a few style issues, some of which
resulted in warnings.
Overview
On Tue, Feb 25, 2025 at 08:02:50PM +0900, Kunihiko Hayashi wrote:
> There are two variables that indicate the interrupt type to be used
> in the next test execution, "irq_type" as global and test->irq_type.
>
> The global is referenced from pci_endpoint_test_get_irq() to preserve
> the current typ
For VMware hypervisor, SEV-SNP enabled VM's could boot without UEFI.
In this case, mpparse_find_mptable() has to be called to parse MP
tables which contains boot information.
Fixes: 0f4a1e80989a ("x86/sev: Skip ROM range scans and validation for SEV-SNP
guests")
Co-developed-by: Ye Li
Signed-off
This improves the expressiveness of unprivileged BPF by inserting
speculation barriers instead of rejecting the programs.
The approach was previously presented at LPC'24 [1] and RAID'24 [2].
To mitigate the Spectre v1 (PHT) vulnerability, the kernel rejects
potentially-dangerous unprivileged BPF
Mark these cases as non-recoverable to later prevent them from being
cought when they occur during speculative path verification.
Signed-off-by: Luis Gerhorst
Acked-by: Henriette Herzog
Cc: Maximilian Ott
Cc: Milan Stephan
---
kernel/bpf/verifier.c | 36 ++--
1
This is required to catch the errors later and fall back to a nospec if
on a speculative path.
Move code into do_check_insn(), replace
* "continue" with "return INSN_IDX_MODIFIED"
* "goto process_bpf_exit" with "return PROCESS_BPF_EXIT"
* "do_print_state = " with "*do_print_state = "
Signed-off-b
On Thu, Mar 13, 2025 at 03:29:20PM +0100, Petr Pavlu wrote:
> 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 t
On Thu, Mar 13, 2025 at 05:40:19PM +0100, Frederic Weisbecker wrote:
> Le Fri, Feb 14, 2025 at 01:10:43AM -0800, Paul E. McKenney a écrit :
> > On Fri, Feb 14, 2025 at 12:25:57AM +0100, Frederic Weisbecker wrote:
> > > When a grace period is started, the ->expmask of each node is set up
> > > from
On Tue, Feb 25, 2025 at 08:02:51PM +0900, Kunihiko Hayashi wrote:
> The global variable "irq_type" preserves the current value of
> ioctl(GET_IRQTYPE).
>
> However, all tests that use interrupts first call ioctl(SET_IRQTYPE)
> to set test->irq_type, then write the value of test->irq_type into the
Le Fri, Feb 14, 2025 at 01:10:43AM -0800, Paul E. McKenney a écrit :
> On Fri, Feb 14, 2025 at 12:25:57AM +0100, Frederic Weisbecker wrote:
> > When a grace period is started, the ->expmask of each node is set up
> > from sync_exp_reset_tree(). Then later on each leaf node also initialize
> > its -
On Tue, Mar 11, 2025 at 08:53:02PM +0100, David Hildenbrand wrote:
> > 2. 9pfs seems to pass the f_type through from the host. So you can't
> > detect it this way anyway.
> >
> > [3. I guess overlayfs & friends would also be an issue here although
> > that doesn't affect my usecase.]
> >
> > Anyw
Some tests introduce memory leaks by not freeing all the pkt_stream
objects they're creating.
Fix these memory leaks.
Signed-off-by: Bastien Curutchet (eBPF Foundation)
---
tools/testing/selftests/bpf/xskxceiver.c | 32 +++-
1 file changed, 31 insertions(+), 1 delet
On Tue, Mar 11, 2025 at 10:58:03AM +0200, Daniel Baluta wrote:
> This patch series adds support to control the Run/Stall DSP bits found on
> i.MX8MP via the reset controller API instead of using the syscon API.
>
> DSP found on i.MX8MP doesn't have a direct reset line so according to hardware
> de
On 12/03/2025 19:32, Peter Xu wrote:
On Wed, Mar 12, 2025 at 05:07:25PM +, Nikita Kalyazin wrote:
However if MISSING is not registered, the kernel will auto-populate with a
clear page, ie there is no way to inject custom content from userspace. To
explain my use case a bit more, the popu
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 10 Mar 2025, at 13:32, Zi Yan wrote:
> On 10 Mar 2025, at 12:14, Zi Yan wrote:
>
>> On 7 Mar 2025, at 12:39, Zi Yan wrote:
>>
>>> This is a preparation patch, both added functions are not used yet.
>>>
>>> The added __split_unmapped_folio() is able to split a folio with its
>>> mapping removed
On Di, 2025-03-11 at 10:58 +0200, Daniel Baluta wrote:
> Current code supports EARC PHY Software Reset and EARC Software Reset
> but it is not easily extensible to more reset bits.
>
> So, refactor the code in order to easily allow more reset bits in the
> future.
>
> Reviewed-by: Peng Fan
> Rev
__testapp_validate_traffic() calls exit_on_error() on failures. This
exits the program immediately and can lead to memory leaks.
Return TEST_FAILURE instead of calling exit_on_error().
Signed-off-by: Bastien Curutchet (eBPF Foundation)
---
tools/testing/selftests/bpf/xskxceiver.c | 6 +++---
1
Gentle Reminder.
On 3/3/2025 2:38 PM, Souradeep Chowdhury wrote:
Add device awake calls in case of rproc boot and rproc shutdown path.
Currently, device awake call is only present in the recovery path
of remoteproc. If a user stops and starts rproc by using the sysfs
interface, then on pm suspe
bitmap is used before being initialized.
Initialize it to zero before using it.
Signed-off-by: Bastien Curutchet (eBPF Foundation)
---
tools/testing/selftests/bpf/xskxceiver.c | 4
1 file changed, 4 insertions(+)
diff --git a/tools/testing/selftests/bpf/xskxceiver.c
b/tools/testing/self
TX and RX workers can fail in many places. These failures trigger a call
to exit_on_error() which exits the program immediately and can lead to
memory leak.
Add return value to functions that can fail.
Handle failures more smoothly through report_failure().
Signed-off-by: Bastien Curutchet (eBPF
test_xsk.c isn't part of the test_progs framework.
Integrate the tests defined by test_xsk.c into the test_progs framework
through a new file : prog_tests/xsk.c. ZeroCopy mode isn't tested in it
as veth peers don't support it.
Move test_xsk{.c/.h} to prog_tests/.
Add the find_bit library to test_p
Hi all,
This patch series continues the work to migrate the script tests into
prog_tests.
The test_xsk.sh script tests lots of AF_XDP use cases. The tests it uses
are defined in xksxceiver.c. As this script is used to test real
hardware, the goal here is to keep it as is and only integrate the
te
Hi all,
On 3/13/25 11:47 AM, Bastien Curutchet (eBPF Foundation) wrote:
Hi all,
This patch series continues the work to migrate the script tests into
prog_tests.
The test_xsk.sh script tests lots of AF_XDP use cases. The tests it uses
are defined in xksxceiver.c. As this script is used to test
Some tests are flaky (especially on s390). So they don't fit in the CI.
Remove flaky tests from the tests table so they won't be run by the CI
in upcoming patch.
Create a flaky_tests table to hold them.
Use the flaky table in xskxceiver.c so the tests remain available for HW
in test_xsk.sh.
Signe
test_xsk.c uses the kselftest framework. This isn't compatible with the
test_progs framework.
Add a XSK_SELTFEST define that allows to enable/disable the kselftest
usage.
Signed-off-by: Bastien Curutchet (eBPF Foundation)
---
tools/testing/selftests/bpf/Makefile | 2 +-
tools/testing/selfte
If any allocation in the pkt_stream_*() helpers fail, exit_on_error() is
called. This terminates the program immediately and can lead to memory
leaks.
Return NULL in case of allocation failure.
Return TEST_FAILURE when something goes wrong in the packet generation.
Signed-off-by: Bastien Curutche
xskxceiver depends on kselftests which prevent from integrating it into
the test_progs framework.
Wrap the ksft_*() calls behind macros to ease the future integration into
test_progs.
Signed-off-by: Bastien Curutchet (eBPF Foundation)
---
tools/testing/selftests/bpf/xskxceiver.c | 109
init_iface() doesn't have any return value while it can fail. In case of
failure it calls exit_on_error() which will terminate the test
immediately.
Add a return value to init_iface() so errors can be handled more
smoothly.
Signed-off-by: Bastien Curutchet (eBPF Foundation)
---
tools/testing/s
xsk_reattach_xdp calls exit_on_error() on failures. This exits the
program immediately and can lead to memory leaks.
Add a return value to the functions handling XDP attachments to handle
errors more smoothly.
Signed-off-by: Bastien Curutchet (eBPF Foundation)
---
tools/testing/selftests/bpf/x
exit_on_error() is called when gettimeofday() fails. This exits the
program immediately and can lead to memory leaks.
Return TEST_FAILURE instead of calling exit_on_error()
Signed-off-by: Bastien Curutchet (eBPF Foundation)
---
tools/testing/selftests/bpf/xskxceiver.c | 8
1 file chan
On Thu, Mar 13, 2025 at 02:42:10PM +0530, Souradeep Chowdhury wrote:
> Gentle Reminder.
>
>
> On 3/3/2025 2:38 PM, Souradeep Chowdhury wrote:
> > Add device awake calls in case of rproc boot and rproc shutdown path.
> > Currently, device awake call is only present in the recovery path
> > of remo
Hi Mathieu,
On Di, 2025-03-11 at 10:27 -0600, Mathieu Poirier wrote:
> Thanks for the re-spin. I will wait for Shawn and Sascha to review their
> respective bits before picking up this set.
Acked-by: Philipp Zabel
for merging the whole series via rproc.
regards
Philipp
On Di, 2025-03-11 at 10:58 +0200, Daniel Baluta wrote:
> We can Run/Stall the DSP via audio block control bits found in audiomix.
> Implement this functionality using the reset controller and use assert
> for Stall and deassert for Run.
>
> Reviewed-by: Peng Fan
> Reviewed-by: Frank Li
> Signed-
On 3/13/25 00:21, Sami Tolvanen wrote:
> Hi Petr,
>
> On Wed, Mar 12, 2025 at 5:05 AM Petr Pavlu wrote:
>>
>> On 3/7/25 01:12, Sami Tolvanen wrote:
>>> On Thu, Mar 06, 2025 at 06:28:58PM +0100, Christophe Leroy wrote:
Le 06/03/2025 à 14:13, Petr Pavlu a écrit :
> Section .static_call_sit
66 matches
Mail list logo
