On 2024/10/10 23:50, Shuah Khan wrote:
On 10/10/24 06:16, zhouyuhang wrote:
From: zhouyuhang
The libcap commit aca076443591 ("Make cap_t operations thread safe.")
added a
__u8 mutex at the beginning of the struct _cap_struct,it changes the
offset of
the members in the structure that breaks
On Fri, Oct 11, 2024 at 10:35:18AM GMT, Shiraz Hashim wrote:
> On Thu, Oct 10, 2024 at 08:57:56AM +0200, neil.armstr...@linaro.org wrote:
> > On 08/10/2024 08:21, Mukesh Ojha wrote:
> > > On Mon, Oct 07, 2024 at 08:22:39PM +0530, Mukesh Ojha wrote:
> > > > On Mon, Oct 07, 2024 at 10:05:08AM +0200,
From: Xiu Jianfeng
When compiling the cgroup selftests with the following command:
make -C tools/testing/selftests/cgroup/
the compiler complains as below:
test_cpu.c: In function ‘test_cpucg_nice’:
test_cpu.c:284:39: error: incompatible type for argument 2 of ‘hog_cpus_timed’
284 |
On Thu, 2024-10-10 at 21:44 +0200, Alessandro Zanni wrote:
> This fix solves this error, when calling kselftest with targets
> "net/rds":
>
> The error was found by running tests manually with the command:
> make kselftest TARGETS="net/rds"
>
> The patch also specifies to import ip() function fro
> Gur Stavi wrote:
> > > Gur Stavi wrote:
> > > > > Gur Stavi wrote:
> > > > > > > Gur Stavi wrote:
> > > > > > > > >> @@ -1846,21 +1846,21 @@ static int fanout_add(struct
> sock
> > > *sk,
> > > > > > > struct fanout_args *args)
> > > > > > > > >> err = -EINVAL;
> > > > > > > > >>
> > > > > >
On Thu, Oct 10, 2024 at 08:57:56AM +0200, neil.armstr...@linaro.org wrote:
> On 08/10/2024 08:21, Mukesh Ojha wrote:
> > On Mon, Oct 07, 2024 at 08:22:39PM +0530, Mukesh Ojha wrote:
> > > On Mon, Oct 07, 2024 at 10:05:08AM +0200, neil.armstr...@linaro.org wrote:
> > > > On 04/10/2024 23:23, Mukesh
The samples/bpf has become outdated and often does not follow up with
the latest. This commit removes obsolete tracing-related tests.
Specifically, 'test_overhead' is duplicate with selftests (and bench),
and 'test_override_return', 'test_probe_write_user' tests are obsolete
since they have been r
This patch removes the obsolete cgroup related tests. These tests are
now redundant because their functionality is already covered by more
modern and comprehensive tests under selftests/bpf.
The following files are removed:
- test_current_task_under_cgroup: tests bpf_current_task_under_cgroup()
This patch continues the migration and removal process for cgroup
sock_create tests to selftests.
The test being migrated verifies the ability of cgroup BPF to block the
creation of specific types of sockets using a verdict. Specifically, the
test denies socket creation when the socket is of type
This patch migrates the old test for cgroup BPF that sets
sk_bound_dev_if, mark, and priority when AF_INET{6} sockets are created.
The most closely related tests under selftests are 'test_sock' and
'sockopt'. However, these existing tests serve different purposes.
'test_sock' focuses mainly on veri
The BPF testing framework has evolved significantly over time. However,
some legacy tests in the samples/bpf directory have not kept up with
these changes. These outdated tests can cause confusion and increase
maintenance efforts.
This patchset focuses on migrating outdated cgroup and tracing-rela
On Fri, Oct 11, 2024 at 09:51:07AM +0800, zhang warden wrote:
>
>
> > On Oct 10, 2024, at 23:51, Josh Poimboeuf wrote:
> >
> > Maybe add a replace=[true|false] module parameter.
> >
>
> How to do it?
> Isn't the way we build modules using make?
> How to set this replace value?
See for examp
The samples/bpf has become outdated and often does not follow up with
the latest. This commit removes obsolete tracing-related tests.
Specifically, 'test_overhead' is duplicate with selftests (and bench),
and 'test_override_return', 'test_probe_write_user' tests are obsolete
since they have been r
This patch removes the obsolete cgroup related tests. These tests are
now redundant because their functionality is already covered by more
modern and comprehensive tests under selftests/bpf.
The following files are removed:
- test_current_task_under_cgroup: tests bpf_current_task_under_cgroup()
This patch continues the migration and removal process for cgroup
sock_create tests to selftests.
The test being migrated verifies the ability of cgroup BPF to block the
creation of specific types of sockets using a verdict. Specifically, the
test denies socket creation when the socket is of type
This patch migrates the old test for cgroup BPF that sets
sk_bound_dev_if, mark, and priority when AF_INET{6} sockets are created.
The most closely related tests under selftests are 'test_sock' and
'sockopt'. However, these existing tests serve different purposes.
'test_sock' focuses mainly on veri
The BPF testing framework has evolved significantly over time. However,
some legacy tests in the samples/bpf directory have not kept up with
these changes. These outdated tests can cause confusion and increase
maintenance efforts.
This patchset focuses on migrating outdated cgroup and tracing-rela
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko :
On Wed, 9 Oct 2024 22:57:37 -0700 you wrote:
> Removed unnecessary `fd = -1` assignments after closing file descriptors.
> because it will be assigned by the function bpf_prog_load().This improves
> code readability
> On Oct 10, 2024, at 23:51, Josh Poimboeuf wrote:
>
> Maybe add a replace=[true|false] module parameter.
>
How to do it?
Isn't the way we build modules using make?
How to set this replace value?
Regards
Wardenjohn
On 10/9/24 3:12 AM, Alexis Lothoré (eBPF Foundation) wrote:
Current test only checks attach/detach on cpu map type program, and so
does not check that it can be properly executed, neither that it
redirects correctly.
Update the existing test to extend its coverage:
- keep the redirected program
Hello:
This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau :
On Wed, 09 Oct 2024 12:12:06 +0200 you wrote:
> Hello,
> this small series aims to increase coverage of xdp features in
> test_progs. The initial versions proposed to rework test_xdp_features.sh
> to make it fit in tes
On 10/10/24 12:15, Lorenzo Stoakes wrote:
Add tests to assert that PIDFD_SELF_* correctly refers to the current
thread and process.
This is only practically meaningful to pidfd_send_signal() and
pidfd_getfd(), but also explicitly test that we disallow this feature for
setns() where it would make
Gur Stavi wrote:
> > Gur Stavi wrote:
> > > > Gur Stavi wrote:
> > > > > > Gur Stavi wrote:
> > > > > > > >> @@ -1846,21 +1846,21 @@ static int fanout_add(struct sock
> > *sk,
> > > > > > struct fanout_args *args)
> > > > > > > >>err = -EINVAL;
> > > > > > > >>
> > > > > > > >>spin_
On 10/8/24 21:59, Yunsheng Lin wrote:
On 2024/10/9 3:56, Shuah Khan wrote:
On 10/8/24 05:20, Yunsheng Lin wrote:
The testing is done by ensuring that the fragment allocated
from a frag_frag_cache instance is pushed into a ptr_ring
instance in a kthread binded to a specified cpu, and a kthread
b
This fix solves this error, when calling kselftest with targets "net/rds":
The error was found by running tests manually with the command:
make kselftest TARGETS="net/rds"
The patch also specifies to import ip() function from the utils module.
Signed-off-by: Alessandro Zanni
---
Notes:
v2:
On 2024-10-10 at 16:21+ Patrick Roy wrote:
> On Tue, 2024-10-08 at 20:56 +0100, Sean Christopherson wrote:
> > Another (slightly crazy) approach would be use protection keys to provide
> > the
> > security properties that you want, while giving KVM (and userspace) a
> > quick-and-easy
> > ove
On 24/10/09 07:40, Jakub Kicinski wrote:
> On Tue, 8 Oct 2024 10:22:53 +0200 Alessandro Zanni wrote:
> > This fix solves this error, when calling kselftest with targets "net/rds":
> >
> > selftests: net/rds: test.py
> > Traceback (most recent call last):
> > File "tools/testing/selftests/net/rd
This fix solves this error, when calling kselftest with targets
"drivers/net":
File "tools/testing/selftests/net/lib/py/nsim.py", line 64, in __init__
if e.errno == errno.ENOSPC:
NameError: name 'errno' is not defined
The error was found by running tests manually with the command:
make kselftes
On Wed, Oct 9, 2024 at 11:46 PM Zhu Jun wrote:
>
> The error check is no longer needed for this test case,
> simplifying the code.
>
> Signed-off-by: Zhu Jun
> ---
> tools/testing/selftests/bpf/prog_tests/signal_pending.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
please add b...
Add tests to assert that PIDFD_SELF_* correctly refers to the current
thread and process.
This is only practically meaningful to pidfd_send_signal() and
pidfd_getfd(), but also explicitly test that we disallow this feature for
setns() where it would make no sense.
We cannot reasonably wait on our
It is useful to be able to utilise pidfd mechanisms to reference the
current thread or process (from a userland point of view - thread group
leader from the kernel's point of view).
Therefore introduce PIDFD_SELF_THREAD to refer to the current thread, and
PIDFD_SELF_THREAD_GROUP to refer to the cu
The means by which a pid is determined from a pidfd is duplicated, with
some callers holding a reference to the (pid)fd, and others explicitly
pinning the pid.
Introduce __pidfd_get_pid() which abstracts both approaches and provide
optional output parameters for file->f_flags and the fd (the latte
If you wish to utilise a pidfd interface to refer to the current process or
thread it is rather cumbersome, requiring something like:
int pidfd = pidfd_open(getpid(), 0 or PIDFD_THREAD);
...
close(pidfd);
Or the equivalent call opening /proc/self. It is more convenient t
On 24/10/09 07:32, Jakub Kicinski wrote:
> On Wed, 9 Oct 2024 00:01:33 +0200 Alessandro Zanni wrote:
> > This fix solves this error, when calling kselftest with targets
> > "drivers/net":
> >
> > File "tools/testing/selftests/net/lib/py/nsim.py", line 64, in __init__
> > if e.errno == errno.EN
Lee Jones, 2024-10-10T09:35:19+01:00:
> On Thu, 10 Oct 2024, Lee Jones wrote:
>
> > On Wed, 09 Oct 2024, Karel Balej wrote:
> >
> > > Lee Jones, 2024-10-09T11:06:43+01:00:
> > > > On Fri, 20 Sep 2024 18:12:34 +0200, Karel Balej wrote:
> > > > > RTC lives on the base register page of the chip. Add
After a CPU has set itself offline and before it eventually calls
rcutree_report_cpu_dead(), there are still opportunities for callbacks
to be enqueued, for example from a softirq. When that happens on NOCB,
the rcuog wake-up is deferred through an IPI to an online CPU in order
not to call into the
On Tue, 2024-10-08 at 20:56 +0100, Sean Christopherson wrote:
> On Tue, Oct 08, 2024, Ackerley Tng wrote:
>> Patrick Roy writes:
>>> For the "non-CoCo with direct map entries removed" VMs that we at AWS
>>> are going for, we'd like a VM type with host-controlled in-place
>>> conversions which d
> Gur Stavi wrote:
> > > Gur Stavi wrote:
> > > > > Gur Stavi wrote:
> > > > > > >> @@ -1846,21 +1846,21 @@ static int fanout_add(struct sock
> *sk,
> > > > > struct fanout_args *args)
> > > > > > >> err = -EINVAL;
> > > > > > >>
> > > > > > >> spin_lock(&po->bind_lock);
> > > > >
On Tue, Sep 10, 2024 at 11:43:57PM +, Ackerley Tng wrote:
> The faultability xarray is stored on the inode since faultability is a
> property of the guest_memfd's memory contents.
>
> In this RFC, presence of an entry in the xarray indicates faultable,
> but this could be flipped so that prese
On Thu, Oct 10, 2024 at 05:38:34PM +0200, Frederic Weisbecker wrote:
> Le Wed, Oct 09, 2024 at 11:07:19AM -0700, Paul E. McKenney a écrit :
> > This commit creates a new srcu-lite option for the refscale.scale_type
> > module parameter that selects srcu_read_lock_lite() and
> > srcu_read_unlock_lit
> Gur Stavi wrote:
> > PACKET socket can retain its fanout membership through link down and up
> > and leave a fanout while closed regardless of link state.
> > However, socket was forbidden from joining a fanout while it was not
> > RUNNING.
> >
> > This patch allows PACKET socket to join fanout w
Hi,
On Thu, Oct 10, 2024 at 1:57 AM Thorsten Leemhuis wrote:
>
> On 10.10.24 10:42, Sedat Dilek wrote:
> > On Thu, Oct 10, 2024 at 10:29 AM Sedat Dilek wrote:
> >> On Thu, Oct 10, 2024 at 10:19 AM Thorsten Leemhuis
> >> wrote:
> >>> On 10.10.24 09:00, Thorsten Leemhuis wrote:
> >>
> >> That wa
On Thu, Oct 10, 2024 at 11:11:56PM +0800, zhang warden wrote:
> > IIUC, you only need to test the stack order by loading LP modules. In
> > this case you could use our currently existing LP testing module for
> > that, right? That's what we currently do when testing different sysfs
> > attributes.
On 10/10/24 06:16, zhouyuhang wrote:
From: zhouyuhang
The libcap commit aca076443591 ("Make cap_t operations thread safe.") added a
__u8 mutex at the beginning of the struct _cap_struct,it changes the offset of
the members in the structure that breaks the assumption made in the "struct
libcap"
Le Wed, Oct 09, 2024 at 11:07:19AM -0700, Paul E. McKenney a écrit :
> This commit creates a new srcu-lite option for the refscale.scale_type
> module parameter that selects srcu_read_lock_lite() and
> srcu_read_unlock_lite().
>
> Signed-off-by: Paul E. McKenney
> Cc: Alexei Starovoitov
> Cc: An
Fix KVM IA32_RTIT_CTL MSR validation logic so that if RTIT_CTL_TRACEEN
bit is cleared, then other bits are allowed to change also. For example,
writing 0 to IA32_RTIT_CTL in order to stop tracing, is valid.
Fixes: bf8c55d8dc09 ("KVM: x86: Implement Intel PT MSRs read/write emulation")
Cc: sta...@v
Hi, Marcos!
> On Oct 10, 2024, at 20:31, Marcos Paulo de Souza wrote:
>
> On Tue, 2024-10-08 at 15:52 +0800, Wardenjohn wrote:
>> Add selftest test cases to sysfs attribute 'stack_order'.
>>
>> Signed-off-by: Wardenjohn
>> ---
>> .../testing/selftests/livepatch/test-sysfs.sh | 71
>>
Add struct perf_event_attr members to support pause and resume of AUX area
tracing.
Signed-off-by: Adrian Hunter
Acked-by: Ian Rogers
Reviewed-by: Andi Kleen
---
tools/include/uapi/linux/perf_event.h | 11 ++-
tools/perf/util/perf_event_attr_fprintf.c | 3 +++
2 files changed, 13
On 10.10.24 16:41, Heiko Carstens wrote:
On Thu, Oct 10, 2024 at 02:31:31PM +0200, David Hildenbrand wrote:
On 10.10.24 10:41, Mario Casquero wrote:
This series has been successfully tested along with the QEMU's series.
Virtio-mem devices could be resized, plugged and unplugged seamlessly.
The
On Thu, Oct 10, 2024 at 02:31:31PM +0200, David Hildenbrand wrote:
> On 10.10.24 10:41, Mario Casquero wrote:
> > This series has been successfully tested along with the QEMU's series.
> > Virtio-mem devices could be resized, plugged and unplugged seamlessly.
> > The memory information displayed is
Add a simple sub-test to the "Miscellaneous Intel PT testing" test to
check pause / resume.
Signed-off-by: Adrian Hunter
Acked-by: Ian Rogers
Reviewed-by: Andi Kleen
---
tools/perf/tests/shell/test_intel_pt.sh | 28 +
1 file changed, 28 insertions(+)
diff --git a/tools
Document the use of aux-action config term and provide a simple example.
Signed-off-by: Adrian Hunter
Acked-by: Ian Rogers
Reviewed-by: Andi Kleen
---
Changes in V5:
Added more examples
tools/perf/Documentation/perf-intel-pt.txt | 108 +
1 file changed, 108 inse
Improve format of config terms and section references.
Signed-off-by: Adrian Hunter
Acked-by: Ian Rogers
Reviewed-by: Andi Kleen
---
tools/perf/Documentation/perf-intel-pt.txt | 486 +++--
1 file changed, 267 insertions(+), 219 deletions(-)
diff --git a/tools/perf/Documentatio
Display "feature is not supported" error message if aux_start_paused,
aux_pause or aux_resume result in a perf_event_open() error.
Signed-off-by: Adrian Hunter
Acked-by: Ian Rogers
Reviewed-by: Andi Kleen
---
tools/perf/util/evsel.c | 10 +-
tools/perf/util/evsel.h | 1 +
2 files chan
Add parsing for aux-action to accept "pause", "resume" or "start-paused"
values.
"start-paused" is valid only for AUX area events.
"pause" and "resume" are valid only for events grouped with an AUX area
event as the group leader. However, like with aux-output, the events
will be automatically gr
Add a new common config term "aux-action" to use for configuring AUX area
trace pause / resume. The value is a string that will be parsed in a
subsequent patch.
Signed-off-by: Adrian Hunter
Acked-by: Ian Rogers
Reviewed-by: Andi Kleen
---
Changes in V7:
Add aux-action to perf_pmu__fo
Events with aux actions or aux sampling expect the PMI to coincide with the
event, which does not happen for large PEBS, so do not enable large PEBS in
that case.
Signed-off-by: Adrian Hunter
Reviewed-by: Andi Kleen
---
Changes in V11:
Remove definition of has_aux_action() because it h
Prevent tracing to start if aux_paused.
Implement support for PERF_EF_PAUSE / PERF_EF_RESUME. When aux_paused, stop
tracing. When not aux_paused, only start tracing if it isn't currently
meant to be stopped.
Signed-off-by: Adrian Hunter
Reviewed-by: Andi Kleen
---
Changes in V12:
Reba
Gur Stavi wrote:
> > Gur Stavi wrote:
> > > > Gur Stavi wrote:
> > > > > >> @@ -1846,21 +1846,21 @@ static int fanout_add(struct sock *sk,
> > > > struct fanout_args *args)
> > > > > >>err = -EINVAL;
> > > > > >>
> > > > > >>spin_lock(&po->bind_lock);
> > > > > >> - if (packet_sock_flag(po
Hardware traces, such as instruction traces, can produce a vast amount of
trace data, so being able to reduce tracing to more specific circumstances
can be useful.
The ability to pause or resume tracing when another event happens, can do
that.
Add ability for an event to "pause" or "resume" AUX a
Add a test that starts Intel PT traces on host and guest. The test requires
support for Intel PT and having Host/Guest mode enabled i.e. kvm_intel
module parameter pt_mode=1.
Signed-off-by: Adrian Hunter
---
tools/testing/selftests/kvm/Makefile | 1 +
.../selftests/kvm/include/x86_64/
Ensure Intel PT tracing is disabled before VM-Entry in Intel PT Host/Guest
mode.
Intel PT has 2 modes for tracing virtual machines. The default is System
mode whereby host and guest output to the host trace buffer. The other is
Host/Guest mode whereby host and guest output to their own buffers.
Ho
If the trace data buffer becomes full, a truncated flag [T] is reported
in PERF_RECORD_AUX. In some cases, the size reported is 0, even though
data must have been added to make the buffer full.
That happens when the buffer fills up from empty to full before the
Intel PT driver has updated the buf
Hi
Note for V12:
There was a small conflict between the Intel PT changes in
"KVM: x86: Fix Intel PT Host/Guest mode when host tracing" and the
changes in this patch set, so I have put the patch sets together,
along with outstanding fix "perf/x86/intel/pt: Fix buffer
On Wed, Oct 9, 2024 at 11:13 AM Paul E. McKenney wrote:
>
> On Tue, Oct 08, 2024 at 07:03:50PM -0700, Paul E. McKenney wrote:
> > On Wed, Oct 02, 2024 at 05:00:03PM +0200, Frederic Weisbecker wrote:
> > > Le Wed, Oct 02, 2024 at 04:57:38PM +0200, Frederic Weisbecker a écrit :
> > > > Callbacks enq
Gur Stavi wrote:
> PACKET socket can retain its fanout membership through link down and up
> and leave a fanout while closed regardless of link state.
> However, socket was forbidden from joining a fanout while it was not
> RUNNING.
>
> This patch allows PACKET socket to join fanout while not RUNN
Le Thu, Oct 10, 2024 at 01:16:41AM -0700, Boqun Feng a écrit :
> On Wed, Oct 02, 2024 at 04:57:36PM +0200, Frederic Weisbecker wrote:
> > It's more convenient to benefit from the fallthrough feature of
> > switch / case to handle the timer state machine. Also a new state is
> > about to be added th
On Tue, 2024-10-08 at 15:52 +0800, Wardenjohn wrote:
> Add selftest test cases to sysfs attribute 'stack_order'.
>
> Signed-off-by: Wardenjohn
> ---
> .../testing/selftests/livepatch/test-sysfs.sh | 71
> +++
> .../selftests/livepatch/test_modules/Makefile | 5 +-
> .../test_klp
On 10.10.24 10:41, Mario Casquero wrote:
This series has been successfully tested along with the QEMU's series.
Virtio-mem devices could be resized, plugged and unplugged seamlessly.
The memory information displayed is correct and reboot doesn't cause
any issue.
Tested-by: Mario Casquero
Than
From: zhouyuhang
The libcap commit aca076443591 ("Make cap_t operations thread safe.") added a
__u8 mutex at the beginning of the struct _cap_struct,it changes the offset of
the members in the structure that breaks the assumption made in the "struct
libcap"
definition in clone3_cap_checkpoint_re
> I realized another possible problem. We should consider adding ifindex
> Field to struct packet_fanout to be used for lookup of an existing match.
> There is little sense to bind sockets to different interfaces and then
> put them in the same fanout group.
> If you agree, I can prepare a separate
> Subject: [PATCH net-next v03 1/3] af_packet: allow fanout_add when socket
> is not RUNNING
>
> PACKET socket can retain its fanout membership through link down and up
> and leave a fanout while closed regardless of link state.
> However, socket was forbidden from joining a fanout while it was no
Add a test that validates that an unbound packet socket cannot create/join
a fanout group.
Signed-off-by: Gur Stavi
---
tools/testing/selftests/net/psock_fanout.c | 36 ++
1 file changed, 36 insertions(+)
diff --git a/tools/testing/selftests/net/psock_fanout.c
b/tools/testi
Modify test_control_group to have toggle parameter.
When toggle is non-zero, loopback device will be set down for the
initialization of fd[1] which is still expected to successfully join
the fanout.
Signed-off-by: Gur Stavi
---
tools/testing/selftests/net/psock_fanout.c | 42
PACKET socket can retain its fanout membership through link down and up
and leave a fanout while closed regardless of link state.
However, socket was forbidden from joining a fanout while it was not
RUNNING.
This patch allows PACKET socket to join fanout while not RUNNING.
The previous test for R
PACKET socket can retain its fanout membership through link down and up
and leave a fanout while closed regardless of link state.
However, socket was forbidden from joining a fanout while it was not
RUNNING.
This scenario was identified while studying DPDK pmd_af_packet_drv.
Since sockets are only
On Thu, 10 Oct 2024 07:40:36 +1100, Aleksa Sarai wrote:
> While we do currently return -EFAULT in this case, it seems prudent to
> follow the behaviour of other syscalls like clone3. It seems quite
> unlikely that anyone depends on this error code being EFAULT, but we can
> always revert this if it
On Thu, Oct 10, 2024 at 10:57 AM Thorsten Leemhuis wrote:
>
> On 10.10.24 10:42, Sedat Dilek wrote:
> > On Thu, Oct 10, 2024 at 10:29 AM Sedat Dilek wrote:
> >> On Thu, Oct 10, 2024 at 10:19 AM Thorsten Leemhuis
> >> wrote:
> >>> On 10.10.24 09:00, Thorsten Leemhuis wrote:
> >>
> >> That was wr
On Thu, Oct 10, 2024 at 10:57 AM Thorsten Leemhuis wrote:
>
> On 10.10.24 10:42, Sedat Dilek wrote:
> > On Thu, Oct 10, 2024 at 10:29 AM Sedat Dilek wrote:
> >> On Thu, Oct 10, 2024 at 10:19 AM Thorsten Leemhuis
> >> wrote:
> >>> On 10.10.24 09:00, Thorsten Leemhuis wrote:
> >>
> >> That was wr
On 10.10.24 10:42, Sedat Dilek wrote:
> On Thu, Oct 10, 2024 at 10:29 AM Sedat Dilek wrote:
>> On Thu, Oct 10, 2024 at 10:19 AM Thorsten Leemhuis
>> wrote:
>>> On 10.10.24 09:00, Thorsten Leemhuis wrote:
>>
>> That was wrong in the original code which you moved:
>>
>> +config MODULE_SIG_SHA384
>
On Thu, Oct 10, 2024 at 10:29 AM Sedat Dilek wrote:
>
> On Thu, Oct 10, 2024 at 10:19 AM Thorsten Leemhuis
> wrote:
> >
> > On 10.10.24 09:00, Thorsten Leemhuis wrote:
> > > Avoid build errors with allmodconfig on Fedora Linux 41+ by reordering
> > > the Kconfig choices so modules are signed wit
This series has been successfully tested along with the QEMU's series.
Virtio-mem devices could be resized, plugged and unplugged seamlessly.
The memory information displayed is correct and reboot doesn't cause
any issue.
Tested-by: Mario Casquero
On Tue, Sep 10, 2024 at 9:16 PM David Hildenbran
On Wed, 09 Oct 2024, Lee Jones wrote:
> On Fri, 20 Sep 2024 18:12:34 +0200, Karel Balej wrote:
> > RTC lives on the base register page of the chip. Add definitions of the
> > registers needed for a basic set/read time functionality.
> >
> >
>
> Applied, thanks!
>
> [1/2] mfd: 88pm886: add the
On Thu, 10 Oct 2024, Lee Jones wrote:
> On Wed, 09 Oct 2024, Karel Balej wrote:
>
> > Lee Jones, 2024-10-09T11:06:43+01:00:
> > > On Fri, 20 Sep 2024 18:12:34 +0200, Karel Balej wrote:
> > > > RTC lives on the base register page of the chip. Add definitions of the
> > > > registers needed for a b
On Thu, Oct 10, 2024 at 09:15:59AM +0200, Krzysztof Kozlowski wrote:
> On 09/10/2024 16:04, Shiraz Hashim wrote:
> > On Mon, Oct 07, 2024 at 06:25:01PM +0200, Dmitry Baryshkov wrote:
> >> On Mon, 7 Oct 2024 at 17:35, Mukesh Ojha wrote:
> >>>
> >>> On Sun, Oct 06, 2024 at 10:38:01PM +0300, Dmitry B
On Wed, 09 Oct 2024, Karel Balej wrote:
> Lee Jones, 2024-10-09T11:06:43+01:00:
> > On Fri, 20 Sep 2024 18:12:34 +0200, Karel Balej wrote:
> > > RTC lives on the base register page of the chip. Add definitions of the
> > > registers needed for a basic set/read time functionality.
> > >
> > >
> >
On Thu, Oct 10, 2024 at 10:19 AM Thorsten Leemhuis wrote:
>
> On 10.10.24 09:00, Thorsten Leemhuis wrote:
> > Avoid build errors with allmodconfig on Fedora Linux 41+ by reordering
> > the Kconfig choices so modules are signed with sha512 by default. That
> > way sha1 will be avoided, which before
On Wed, Oct 09, 2024 at 11:34:30PM GMT, huangwenyu1...@gmail.com wrote:
From: Wenyu Huang
It used for testing in tools/virtio/vringh_test.c.
If vring_new_virtqueue supports packed vring, we can add support for
packed vring to vringh and test it.
Are you also working on that changes?
Signed
On Wed, Oct 02, 2024 at 04:57:36PM +0200, Frederic Weisbecker wrote:
> It's more convenient to benefit from the fallthrough feature of
> switch / case to handle the timer state machine. Also a new state is
> about to be added that will take advantage of it.
>
> No intended functional change.
>
>
Alessandro Zanni writes:
> This fix solves this error, when calling kselftest with targets "drivers/net":
>
> File "tools/testing/selftests/net/lib/py/nsim.py", line 64, in __init__
> if e.errno == errno.ENOSPC:
> NameError: name 'errno' is not defined
>
> The module errno makes available sta
Remove unnecessary semicolons reported by Coccinelle/coccicheck and the
semantic patch at scripts/coccinelle/misc/semicolon.cocci.
Signed-off-by: Chen Ni
---
tools/testing/selftests/timers/set-timer-lat.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests
On 09/10/2024 16:04, Shiraz Hashim wrote:
> On Mon, Oct 07, 2024 at 06:25:01PM +0200, Dmitry Baryshkov wrote:
>> On Mon, 7 Oct 2024 at 17:35, Mukesh Ojha wrote:
>>>
>>> On Sun, Oct 06, 2024 at 10:38:01PM +0300, Dmitry Baryshkov wrote:
On Sat, Oct 05, 2024 at 02:53:54AM GMT, Mukesh Ojha wrote:
On 10.10.24 09:00, Thorsten Leemhuis wrote:
> Avoid build errors with allmodconfig on Fedora Linux 41+ by reordering
> the Kconfig choices so modules are signed with sha512 by default. That
> way sha1 will be avoided, which beforehand was chosen by default on
> x86_64 when running allmodconfig -- w
> Gur Stavi wrote:
> > > Gur Stavi wrote:
> > > > >> @@ -1846,21 +1846,21 @@ static int fanout_add(struct sock *sk,
> > > struct fanout_args *args)
> > > > >> err = -EINVAL;
> > > > >>
> > > > >> spin_lock(&po->bind_lock);
> > > > >> -if (packet_sock_flag(po, PACKET_SOCK_RUNNING) &&
>
Avoid build errors with allmodconfig on Fedora Linux 41+ by reordering
the Kconfig choices so modules are signed with sha512 by default. That
way sha1 will be avoided, which beforehand was chosen by default on
x86_64 when running allmodconfig -- which on the latest Fedora leads to
the following bui
95 matches
Mail list logo
