The macro FUSE_USE_VERSION is never referenced in the code,
just remove it.
Signed-off-by: Ba Jing
---
tools/testing/selftests/memfd/fuse_mnt.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/tools/testing/selftests/memfd/fuse_mnt.c
b/tools/testing/selftests/memfd/fuse_mnt.c
index 6936f2a0
On Fri, Sep 13, 2024 at 11:33 PM Gary Guo wrote:
>
> With `long` mapped to `isize`, `size_t`/`__kernel_size_t` mapped to
> usize and `char` mapped to `u8`, many of the existing casts are no
> longer necessary.
>
> Signed-off-by: Gary Guo
This is great!
Reviewed-by: Alice Ryhl
Hi Krzysztof,
> > + '#extsys-id':
>
> '#' is not correct for sure, that's not a cell specifier.
>
> But anyway, we do not accept in general instance IDs.
> >>>
> >>> I'm happy to replace the instance ID with another solution.
> >>> In our c
+CC linux-kselftest
---
On 22/09/2024 17:16, Gabriela Bittencourt wrote:
Hey all,
We are making these changes as part of a KUnit Hackathon at LKCamp [1].
This patch sets out to refactor fs/unicode/utf8-selftest.c to KUnit tests.
The first commit is the refactoring itself from self test i
From: Jakub Sitnicki
> Sent: 23 September 2024 15:56
>
> On Mon, Sep 23, 2024 at 01:08 PM GMT, David Laight wrote:
> > From: Tiago Lam
>
> [...]
>
> >> To limit its usage, a reverse socket lookup is performed to check if the
> >> configured egress source address and/or port have any ingress sk_
On 9/20/24 20:49, Artur Alves Cavalcante de Barros wrote:
On 9/20/24 4:10 AM, David Gow wrote:
On Fri, 20 Sept 2024 at 00:01, Shuah Khan wrote:
On 9/16/24 18:51, Artur Alves wrote:
Hi all,
This is part of a hackathon organized by LKCAMP[1], focused on writing
tests using KUnit. We reached o
On 23.09.24 07:38, Muhammad Usama Anjum wrote:
grep -rnIF "#define __NR_userfaultfd"
tools/include/uapi/asm-generic/unistd.h:681:#define __NR_userfaultfd 282
arch/x86/include/generated/uapi/asm/unistd_32.h:374:#define
__NR_userfaultfd 374
arch/x86/include/generated/uapi/asm/unistd_64.h:327:#defin
On Mon, Sep 23, 2024 at 03:45 PM GMT, David Laight wrote:
> From: Jakub Sitnicki
>> Sent: 23 September 2024 15:56
>>
>> On Mon, Sep 23, 2024 at 01:08 PM GMT, David Laight wrote:
>> > From: Tiago Lam
>>
>> [...]
>>
>> >> To limit its usage, a reverse socket lookup is performed to check if the
>>
On 9/2/24 21:43, Ba Jing wrote:
These variables are never referenced in the code, just remove it.
remove them?
Add details on how you found this problem in the commit log.
Send v2 with these changes.
Signed-off-by: Ba Jing
---
tools/testing/selftests/damon/access_memory_even.c | 2 --
1
Hi maintainers,
Are there any other concerns I should address for this patch?
On Mon, Sep 9, 2024 at 4:52 PM Philip Chen wrote:
>
> Hi
>
> On Wed, Sep 4, 2024 at 10:54 AM Ira Weiny wrote:
> >
> > Philip Chen wrote:
> > > Hi maintainers,
> > >
> > > Can anyone let me know if this patch makes sen
On Mon, Sep 23, 2024, Ivan Orlov wrote:
> Currently, KVM may return a variety of internal errors to VMM when
> accessing MMIO, and some of them could be gracefully handled on the KVM
> level instead. Moreover, some of the MMIO-related errors are handled
> differently in VMX in comparison with SVM,
On 23/09/2024 13:49, Abdellatif El Khlifi wrote:
> Hi Krzysztof,
>
>>> + '#extsys-id':
>>
>> '#' is not correct for sure, that's not a cell specifier.
>>
>> But anyway, we do not accept in general instance IDs.
>
> I'm happy to replace the i
On 9/22/24 23:38, Muhammad Usama Anjum wrote:
grep -rnIF "#define __NR_userfaultfd"
tools/include/uapi/asm-generic/unistd.h:681:#define __NR_userfaultfd 282
arch/x86/include/generated/uapi/asm/unistd_32.h:374:#define
__NR_userfaultfd 374
arch/x86/include/generated/uapi/asm/unistd_64.h:327:#define
On 9/22/24 23:35, Muhammad Usama Anjum wrote:
...
grep -rnIF "#define __NR_userfaultfd"
tools/include/uapi/asm-generic/unistd.h:681:#define __NR_userfaultfd 282
arch/x86/include/generated/uapi/asm/unistd_32.h:374:#define
__NR_userfaultfd 374
arch/x86/include/generated/uapi/asm/unistd_64.h:327:#
Hi Ba,
On Tue, 3 Sep 2024 11:43:00 +0800 Ba Jing wrote:
> These variables are never referenced in the code, just remove it.
Nice finding, thank you!
I'd prefer having 'selftests/damon/access_memory_even: ' as the commit subject
prefix.
>
> Signed-off-by: Ba Jing
Other than the above trivi
On 9/23/24 08:45, Marcos Paulo de Souza wrote:
On Fri, 2024-09-20 at 13:56 +0200, Michael Vetter wrote:
This patchset adds a test for livepatching a kprobed function.
Thanks to Petr and Marcos for the reviews!
V3:
Save and restore kprobe state also when test fails, by integrating it
into setup
On 9/23/24 09:42, Pedro Orlando wrote:
+CC linux-kselftest
---
On 22/09/2024 17:16, Gabriela Bittencourt wrote:
Hey all,
We are making these changes as part of a KUnit Hackathon at LKCamp [1].
This patch sets out to refactor fs/unicode/utf8-selftest.c to KUnit tests.
The first commit is
Hi Krzysztof,
> >>> + '#extsys-id':
> >>
> >> '#' is not correct for sure, that's not a cell specifier.
> >>
> >> But anyway, we do not accept in general instance IDs.
> >
> > I'm happy to replace the instance ID with another solution.
> >>
Add a basic DWARF parser, which uses libdw to traverse the debugging
information in an object file and looks for functions and variables.
In follow-up patches, this will be expanded to produce symbol versions
for CONFIG_MODVERSIONS from DWARF.
Signed-off-by: Sami Tolvanen
---
kernel/module/Kconf
The compiler may choose not to emit type information in DWARF for all
aliases, but it's possible for each alias to be exported separately.
To ensure we find type information for the aliases as well, read
{section, address} tuples from the symbol table and match symbols also
by address.
Signed-off-
umentation.
Note that v3 is based on next-20240923 as it depends on Masahiro's
scripts/include changes. For x86, we also need a separate small
patch to include asm/ptrace.h in asm/ftrace.h. [5] For your
convenience, you can find this series with all the prerequisites
here:
https://github.
Import list_is_first, list_is_last, list_replace, and list_replace_init.
Signed-off-by: Sami Tolvanen
---
scripts/include/list.h | 50 ++
1 file changed, 50 insertions(+)
diff --git a/scripts/include/list.h b/scripts/include/list.h
index fea1e2b79063..8bd
To avoid duplication between host programs, move the crc32 code to a
shared header file.
Suggested-by: Petr Pavlu
Signed-off-by: Sami Tolvanen
---
scripts/genksyms/genksyms.c | 77 +-
scripts/include/crc32.h | 93 +
2 files cha
Basic types in DWARF repeat frequently and traversing the DIEs using
libdw is relatively slow. Add a simple hashtable based cache for the
processed DIEs.
Signed-off-by: Sami Tolvanen
---
scripts/gendwarfksyms/Makefile| 1 +
scripts/gendwarfksyms/die.c | 143 ++
Add support for expanding DWARF type modifiers, such as pointers,
const values etc., and typedefs. These types all have DW_AT_type
attribute pointing to the underlying type, and thus produce similar
output.
Also add linebreaks and indentation to debugging output to make it
more readable.
Signed-o
Add support for expanding DW_TAG_subroutine_type and the parameters
in DW_TAG_formal_parameter. Use this to also expand subprograms.
Example output with --dump-dies:
subprogram (
formal_parameter pointer_type {
const_type {
base_type char byte_size(1) encoding(6)
}
}
Start making gendwarfksyms more useful by adding support for
expanding DW_TAG_base_type types and basic DWARF attributes.
Example:
$ echo loops_per_jiffy | \
scripts/gendwarfksyms/gendwarfksyms \
--debug --dump-dies vmlinux.o
...
gendwarfksyms: process_symbol: loops_per_jiffy
Recursively expand DWARF structure types, i.e. structs, unions, and
enums. Also include relevant DWARF attributes in type strings to
encode structure layout, for example.
Example output with --dump-dies:
subprogram (
formal_parameter structure_type &str {
member pointer_type {
Add support for expanding DW_TAG_array_type, and the subrange type
indicating array size.
Example source code:
const char *s[34];
Output with --dump-dies:
variable array_type[34] {
pointer_type {
const_type {
base_type char byte_size(1) encoding(6)
}
} byte_size(
Add support for producing genksyms-style symtypes files. Process
die_map to find the longest expansions for each type, and use symtypes
references in type definitions. The basic file format is similar to
genksyms, with two notable exceptions:
1. Type names with spaces (common with Rust) in refer
Expand each structure type only once per exported symbol. This
is necessary to support self-referential structures, which would
otherwise result in infinite recursion, but is still sufficient for
catching ABI changes.
For pointers, limit structure expansion after the first pointer
in the symbol ty
Debugging the DWARF processing can be somewhat challenging, so add
more detailed debugging output for die_map operations. Add the
--dump-die-map flag, which adds color coded tags to the output for
die_map changes.
Signed-off-by: Sami Tolvanen
---
scripts/gendwarfksyms/dwarf.c | 15 ++
Distributions that want to maintain a stable kABI need the ability
to make ABI compatible changes to kernel without affecting symbol
versions, either because of LTS updates or backports.
With genksyms, developers would typically hide these changes from
version calculation with #ifndef __GENKSYMS__
Distributions that want to maintain a stable kABI need the ability
to make ABI compatible changes to kernel data structures without
affecting symbol versions, either because of LTS updates or backports.
With genksyms, developers would typically hide these changes from
version calculation with #ifn
Calculate symbol versions from the fully expanded type strings in
type_map, and output the versions in a genksyms-compatible format.
Signed-off-by: Sami Tolvanen
---
scripts/gendwarfksyms/dwarf.c | 25 +-
scripts/gendwarfksyms/gendwarfksyms.c | 11 ++-
scripts/gendwarfksyms/gendwar
With gendwarfksyms, we need each TU where the EXPORT_SYMBOL() macro
is used to also contain DWARF type information for the symbols it
exports. However, as a TU can also export external symbols and
compilers may choose not to emit debugging information for symbols not
defined in the current TU, the
The compiler may choose not to emit type information in DWARF for
external symbols. Clang, for example, does this for symbols not
defined in the current TU.
To provide a way to work around this issue, add support for
__gendwarfksyms_ptr_ pointers that force the compiler to emit
the necessary type
When MODVERSIONS is enabled, allow selecting gendwarfksyms as the
implementation, but default to genksyms.
Signed-off-by: Sami Tolvanen
---
kernel/module/Kconfig | 25 -
scripts/Makefile | 2 +-
scripts/Makefile.build | 39 +++
Add documentation for gendwarfksyms changes, and the kABI stability
features that can be useful for distributions even though they're not
used in mainline kernels.
Signed-off-by: Sami Tolvanen
---
Documentation/kbuild/gendwarfksyms.rst | 274 +
Documentation/kbuild/index.
On Sun, Sep 22, 2024 at 04:57:07PM +0530, Beleswar Prasad Padhi wrote:
> Since commit 17de3f5fdd35, the IOMMU framework has changed how it handles
> callback ops, moving away from using bus->iommu_ops. The omap-iommu driver
> has not yet been updated to align with these framework changes. Therefor
On Wed, Sep 18, 2024 at 08:10:52AM +, Tian, Kevin wrote:
> > From: Jason Gunthorpe
> > Sent: Saturday, September 14, 2024 10:51 PM
> >
> > On Fri, Sep 13, 2024 at 02:33:59AM +, Tian, Kevin wrote:
> > > > From: Jason Gunthorpe
> > > > Sent: Thursday, September 12, 2024 7:08 AM
> > > >
> >
These variables are never referenced in the code, just remove it.
Signed-off-by: Ba Jing
---
tools/testing/selftests/damon/access_memory_even.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/tools/testing/selftests/damon/access_memory_even.c
b/tools/testing/selftests/damon/access_memory_e
The macro NSEC_PER_MSEC is never referenced in the code, just remove it.
Signed-off-by: Ba Jing
---
tools/testing/selftests/dma/dma_map_benchmark.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/tools/testing/selftests/dma/dma_map_benchmark.c
b/tools/testing/selftests/dma/dma_map_benchmar
Hello RT-list!
I'm pleased to announce the 4.19.322-rt138 stable release. This is just
an update to the 4.19.322 stable release. No RT specific changes.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v4.19-rt
Head
The variable "wret" is never referenced in the code, just remove it.
Signed-off-by: Ba Jing
---
tools/testing/selftests/filesystems/binderfs/binderfs_test.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/testing/selftests/filesystems/binderfs/binderfs_test.c
b/tools/testing/selftests/
Currently, we simply return a KVM internal error with suberror =
KVM_INTERNAL_ERROR_EMULATION if the guest tries to fetch instruction
from MMIO range as we simply can't decode it.
I believe it is not the best thing to do, considering that
1) we don't give enough information to VMM about the iss
Implement the test which covers "weird" mmio usage. The test has 4 test
cases:
1) Guest sets IDT/GDT base to point to an MMIO region. Triple fault and
shutdown are expected there.
2) Guest jumps to MMIO address. Fetches from MMIO are not permitted, so
UD is expected there.
3) Guest sets an IDT ent
Currently, the situation when guest accesses MMIO during event delivery
is handled differently in VMX and SVM: on VMX KVM returns internal error
with suberror = KVM_INTERNAL_ERROR_DELIVERY_EV, when SVM simply goes
into infinite loop trying to execute faulty instruction again and again.
Such a situ
Currently, KVM may return a variety of internal errors to VMM when
accessing MMIO, and some of them could be gracefully handled on the KVM
level instead. Moreover, some of the MMIO-related errors are handled
differently in VMX in comparison with SVM, which produces certain
inconsistency and should
Update the set_memory_region test, test case test_zero_memory_regions to
use an updated exit code if the VM starts with no RAM. Now we are
issuing a triple fault in such a case, not an internal error.
Signed-off-by: Ivan Orlov
---
tools/testing/selftests/kvm/set_memory_region_test.c | 3 ++-
1 f
From: Joshua Hahn
Cgroup-level CPU statistics currently include time spent on
user/system processes, but do not include niced CPU time (despite
already being tracked). This patch exposes niced CPU time to the
userspace, allowing users to get a better understanding of their
hardware limits and can
From: Joshua Hahn
Creates a cgroup with a single nice CPU hog process running.
fork() is called to generate the nice process because un-nicing is
not possible (see man nice(3)). If fork() was not used to generate
the CPU hog, we would run the rest of the cgroup selftest suite as a
nice process.
From: Joshua Hahn
v2 -> v3: Signed-off-by & renamed subject for clarity.
v1 -> v2: Edited commit messages for clarity.
Niced CPU usage is a metric reported in host-level /prot/stat, but is
not reported in cgroup-level statistics in cpu.stat. However, when a
host contains multiple tasks across di
Just an FYI to the reviewers -
Tiago is out this week, so his reponses will be delayed.
On Fri, 2024-09-20 at 13:56 +0200, Michael Vetter wrote:
> This patchset adds a test for livepatching a kprobed function.
>
> Thanks to Petr and Marcos for the reviews!
>
> V3:
> Save and restore kprobe state also when test fails, by integrating it
> into setup_config() and cleanup().
> Rename SY
On Tue, Sep 17, 2024 at 06:56:58PM +0200, Arnaud POULIQUEN wrote:
> Hello Mathieu,
>
> On 9/12/24 17:26, Mathieu Poirier wrote:
> > On Fri, Aug 30, 2024 at 11:51:44AM +0200, Arnaud Pouliquen wrote:
> >> Add support for releasing remote processor firmware through
> >> the Trusted Execution Environm
On Mon, Sep 23, 2024 at 01:08 PM GMT, David Laight wrote:
> From: Tiago Lam
[...]
>> To limit its usage, a reverse socket lookup is performed to check if the
>> configured egress source address and/or port have any ingress sk_lookup
>> match. If it does, traffic is allowed to proceed, otherwise
Hello.
On 9/21/24 07:22, Jiawei Ye wrote:
Hi Miquèl,
I'm sorry for the accidental email sent while testing my email setup. Please
disregard the previous message.
On 9/20/24 19:21, Miquel Raynal wrote:
Hi Jiawei,
jiawei...@foxmail.com wrote on Fri, 20 Sep 2024 04:03:32 +:
In the `mac80
From: Tiago Lam
> Sent: 20 September 2024 18:02
>
> This follows the same rationale provided for the ipv4 counterpart, where
> the sendmsg() path is also extended here to support the IPV6_ORIGDSTADDR
> ancillary message to be able to specify a source address/port. This
> allows users to configure
The macro GUEST_CODE_PIO_PORT is never referenced in the code,
just remove it.
Signed-off-by: Ba Jing
---
tools/testing/selftests/kvm/hardware_disable_test.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/testing/selftests/kvm/hardware_disable_test.c
b/tools/testing/selftests/kvm/hard
ig and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240923/202409231644.4c55582d-...@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
On 9/19/24 09:57, Paolo Abeni wrote:
On 9/7/24 18:42, Justin Iurman wrote:
TL;DR This patch comes from a discussion we had with Jakub and Paolo.
This patch updates the IOAM selftests to support the new "tunsrc"
feature of IOAM. As a consequence, some changes were required. For
example, the IPv6
On Wed, Sep 18, 2024 at 04:43:32PM +0200, Arnaud POULIQUEN wrote:
> Hello Mathieu,
>
> On 8/30/24 11:51, Arnaud Pouliquen wrote:
> > Add support for releasing remote processor firmware through
> > the Trusted Execution Environment (TEE) interface.
> >
> > The tee_rproc_release_fw() function is ca
From: Markus Elfring
Date: Mon, 23 Sep 2024 17:05:39 +0200
A nvdimm_put_key(key) call was immediately used after a return code
check for a change_key() call in this function implementation.
Thus call such a function only once instead directly before the check.
This issue was transformed by using
On Mon, 2024-09-23 at 10:04 -0700, Sean Christopherson wrote:
>
> On Mon, Sep 23, 2024, Ivan Orlov wrote:
> > Currently, KVM may return a variety of internal errors to VMM when
> > accessing MMIO, and some of them could be gracefully handled on the
> > KVM
> > level instead. Moreover, some of the
Hi Ba,
Thank you for revising this patch following my comment.
On Tue, 24 Sep 2024 10:14:26 +0800 Ba Jing wrote:
> By reading the code, I found these variables are never
> referenced in the code. Just remove them.
>
> Signed-off-by: Ba Jing
Reviewed-by: SeongJae Park
Thanks,
SJ
> ---
>
On 9/24/24 07:44, Ba Jing wrote:
By reading the code, I found these variables are never
referenced in the code. Just remove them.
Signed-off-by: Ba Jing
Reviewed-by: Dev Jain
Hi Alexandre,
Thank you for looking at the rtc patch.
I saw you Acked the [PATCH 2/2], not sure when could we see the patch
in kernel master or next branch ?
Thank you,
Joseph.
On 2024/6/21 3:37 AM, Alexandre Belloni wrote:
On 23/05/2024 18:38:07-0700, Joseph Jang wrote:
The rtctest requires
By reading the code, I found these variables are never
referenced in the code. Just remove them.
Signed-off-by: Ba Jing
---
Notes:
v1:
https://lore.kernel.org/all/20240903034300.10443-1-baj...@cmss.chinamobile.com/
v2: Modify the commit subject and commit log.
tools/testing/selftests/damon/ac
On Thu, Jul 18, 2024 at 02:05:04PM -0700, Stephen Boyd wrote:
> Introduce KUnit resource wrappers around platform_driver_register(),
> platform_device_alloc(), and platform_device_add() so that test authors
> can register platform drivers/devices from their tests and have the
> drivers/devices auto
The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:
Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git
tags/rpmsg-v6.12
for you to fetch changes up to c1ddb29709e
The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:
Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git
tags/hwlock-v6.12
for you to fetch changes up to 8dc1bffd6e
On 9/23/24 9:02 PM, Shuah Khan wrote:
> On 9/22/24 23:35, Muhammad Usama Anjum wrote:
>> ...
>>
grep -rnIF "#define __NR_userfaultfd"
tools/include/uapi/asm-generic/unistd.h:681:#define __NR_userfaultfd
282
arch/x86/include/generated/uapi/asm/unistd_32.h:374:#define
__NR_us
From: zhang jiao
There is no va_end after va_copy, just add it.
Signed-off-by: zhang jiao
---
tools/testing/selftests/bpf/test_progs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/bpf/test_progs.c
b/tools/testing/selftests/bpf/test_progs.c
index c7a70e1a1085..78
The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:
Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git
tags/rproc-v6.12
for you to fetch changes up to 38a0e38b31d
75 matches
Mail list logo
