On Sun, Sep 29, 2024 at 10:03:23PM -0500, Bjorn Andersson wrote:
> On Fri, Sep 27, 2024 at 04:51:32PM GMT, Wasim Nazir wrote:
> > This test includes:
> > 1) Start/stop test for each rproc instance sequencially
> > 2) Start/stop test for all rproc instances concurrently
> >
>
> This fails
Hi Antonio,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 44badc908f2c85711cb18e45e13119c10ad3a05f]
url:
https://github.com/intel-lab-lkp/linux/commits/Antonio-Quartulli/netlink-add-NLA_POLICY_MAX_LEN-macro/20241002-172734
base: 44badc908f2c85711cb18e4
On Wed, Oct 02, 2024 at 09:41:42AM GMT, Michael S. Tsirkin wrote:
> virtio_transport_send_pkt in now called on transport fast path,
> under RCU read lock. In that case, we have a bug: virtio_add_sgs
> is called with GFP_KERNEL, and might sleep.
>
> Pass the gfp flags as an argument, and use GFP_AT
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni :
On Fri, 27 Sep 2024 12:00:50 +0800 you wrote:
> From: zhang jiao
>
> There is no va_end after va_copy, just add it.
>
> Signed-off-by: zhang jiao
> ---
> tools/testing/selftests/net/tcp_ao/lib/aolib.h | 1 +
> 1 fil
On Tue, 17 Sept 2024 at 08:51, Artur Alves wrote:
>
> Add KUnit tests for the llist data structure. They test the vast
> majority of methods and macros defined in include/linux/llist.h.
>
> These are inspired by the existing tests for the 'list' doubly
> linked in lib/list-test.c. Each test case (
On Tue, 1 Oct 2024 at 07:55, Guenter Roeck wrote:
>
> On 9/30/24 11:50, Guenter Roeck wrote:
> > On 9/30/24 01:37, Vlastimil Babka wrote:
> >> Guenter Roeck reports that the new slub kunit tests added by commit
> >> 4e1c44b3db79 ("kunit, slub: add test_kfree_rcu() and
> >> test_leak_destroy()") ca
gt; Revert it.
> >>
> >> Fixes: e620799c414a ("list: test: fix tests for list_cut_position()")
> >> Cc: I Hsin Cheng
> >> Cc: David Gow
> >> Cc: Andrew Morton
> >> Signed-off-by: Guenter Roeck
> >> ---
> >
>
On Tue, 1 Oct 2024 at 01:06, I Hsin Cheng wrote:
>
> Mending test for list_cut_position*() for the missing check of integer
> "i" after the second loop. The variable should be checked for second
> time to make sure both lists after the cut operation are formed as
> expected.
>
> Signed-off-by: I H
Hi, Josh!
> On Oct 1, 2024, at 07:26, Josh Poimboeuf wrote:
>>
>> diff --git a/Documentation/ABI/testing/sysfs-kernel-livepatch
>> b/Documentation/ABI/testing/sysfs-kernel-livepatch
>> index a5df9b4910dc..2a60b49aa9a5 100644
>> --- a/Documentation/ABI/testing/sysfs-kernel-livepatch
>> +++ b/Do
On Wed, 2 Oct 2024 at 19:56, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 6.6.54 release.
> There are 538 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Resp
On Wed, Oct 02, 2024 at 03:24:45PM +, David Laight wrote:
> I think I know what you are trying to do, and you just fail.
> Whether something can work is another matter, but that code
> can't ever work.
>
> Inside if (a == b) the compiler will always use the same register
> for references to a
> Link:
> https://lore.kernel.org/all/hfcr2aget2zojmqpr4uhlzvnep4vgskblx5b6xf2ddosbsrke7@nt34bxgp7j2x
> Fixes: efcd71af38be ("vsock/virtio: avoid queuing packets when intermediate
> queue is empty")
> Reported-by: Christian Brauner
> Cc: Stefano Garzarella
> Cc: Luigi Leonardi
> Signed-off-by:
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski :
On Fri, 27 Sep 2024 12:13:49 +0800 you wrote:
> The include.sh file is generated for inclusion and should not be executable.
> Otherwise, it will be added to kselftest-list.txt. Additionally, add the
> executable bit for t
On Tue, Oct 01, 2024 at 09:02:04PM -0400, Mathieu Desnoyers wrote:
> This API provides existence guarantees of objects through Hazard
> Pointers (HP).
>
> Each HP domain defines a fixed number of hazard pointer slots (nr_cpus)
> across the entire system.
>
> Its main benefit over RCU is that it a
On Tue, Oct 01, 2024 at 09:02:02PM -0400, Mathieu Desnoyers wrote:
> Compiler CSE and SSA GVN optimizations can cause the address dependency
> of addresses returned by rcu_dereference to be lost when comparing those
> pointers with either constants or previously loaded pointers.
>
> Introduce ptr_
Wasn't this already submitted and commented on?
https://lore.kernel.org/all/20240919111841.20226-1-liaoy...@huawei.com/
On 10/1/24 08:30, Benjamin Tissoires wrote:
This is a slight change from the fundamentals of HID-BPF.
In theory, HID-BPF is abstract to the kernel itself, and makes
only changes at the HID level (through report descriptors or
events emitted to/from the device).
However, we have seen a few use ca
On 10/2/24 09:28, SurajSonawane2415 wrote:
Fix build error in vdso_test_getrandom.c due to missing CLONE_NEWTIME.
Include linux/sched.h to define CLONE_NEWTIME.
Ensure successful compilation by resolving the missing header issue.
Did you run "make headers" before building this test? It builds
On 10/2/24 03:02, Antonio Quartulli wrote:
The ovpn-cli tool can be compiled and used as selftest for the ovpn
kernel module.
Does this test load ovpn module before running tests? If so does
it unload the modules after tests are complete?
It implementes the netlink API and can thus be integr
On Wed, 2024-10-02 at 22:01 +0100, Mark Brown wrote:
> BTW it's probably also worth noting that at least on arm64 (perhaps x86
> is different here?) the shadow stack of a thread that exited won't have
> a token placed on it so it won't be possible to use it with clone3() at
> all unless another tok
On 9/11/24 1:41 AM, Florian Kauer wrote:
@@ -25,14 +28,11 @@ static void test_xdp_with_devmap_helpers(void)
if (!ASSERT_OK_PTR(skel, "test_xdp_with_devmap_helpers__open_and_load"))
return;
- dm_fd = bpf_program__fd(skel->progs.xdp_redir_prog);
- err = bpf_xdp_att
On Wed, Oct 02, 2024 at 02:42:58PM +0100, Mark Brown wrote:
> On Tue, Oct 01, 2024 at 11:03:10PM +, Edgecombe, Rick P wrote:
> > I'm not so sure. The thing is a regular stack can be re-used in full - just
> > set
> > the RSP to the end and take advantage of the w
On 9/30/24 17:18, Jacob Keller wrote:
On 9/22/2024 8:05 AM, Guenter Roeck wrote:
This reverts commit e620799c414a035dea1208bcb51c869744931dbb.
The commit introduces unit test failures.
Expected cur == &entries[i], but
cur == 037fffadfd80
&entries[i] == 037ff
On 10/2/24 03:00, Alessandro Zanni wrote:
Hello,
this email is just a friendly reminder to know if the present patch is going to
be applied or not.
Thank you.
Best Regards,
Alessandro Zanni
No top posting please.
On 24/08/06 02:14, Alessandro Zanni wrote:
Insert raw strings to prevent Py
On Mon, Sep 16, 2024 at 8:51 PM Artur Alves wrote:
>
> Add KUnit tests for the llist data structure. They test the vast
> majority of methods and macros defined in include/linux/llist.h.
>
> These are inspired by the existing tests for the 'list' doubly
> linked in lib/list-test.c. Each test case
SRCU-lite over SRCU for uprobes, taking RCU Tasks Trace
> performance out of the equation.
>
> In uprobes I used basically two benchmarks. One, uprobe-nop, that
> benchmarks entry uprobes (which are the fastest most optimized case,
> using RCU Tasks Trace in A and SRCU in D), and anoth
On Wed, 11 Sep 2024 10:41:18 +0200 Florian Kauer wrote:
> rxq contains a pointer to the device from where
> the redirect happened. Currently, the BPF program
> that was executed after a redirect via BPF_MAP_TYPE_DEVMAP*
> does not have it set.
Acked-by: Jakub Kicinski
e mm refcount - the reason the
lazy-tlb handling uses it is because we already had that refcount and
it was easy to extend on existing logic, not because it's really
required any more.
The lazy-tlb activation is basically "I'm switching to a kernel
thread, so I'll re-use the T
On Wed, Oct 02, 2024 at 04:02:06PM GMT, Stefano Garzarella wrote:
On Wed, Oct 02, 2024 at 09:41:42AM GMT, Michael S. Tsirkin wrote:
virtio_transport_send_pkt in now called on transport fast path,
under RCU read lock. In that case, we have a bug: virtio_add_sgs
is called with GFP_KERNEL, and migh
ID:AuthenticAMD
>>>> Model name: AMD EPYC 9654 96-Core Processor
>>>> CPU family: 25
>>>> Model:17
>>>> Thread(s) per core: 2
>>>> Core(s) per socket:
). I've
noticed I had schedstats and sched debug enabled in my config, so I'll have to
re-run my tests.
A quick re-run of the 128-thread case with schedstats and sched debug
disabled still show around 26% speedup, similar to my prior numbers.
I'm not sure why Jens has much bette
654 96-Core Processor
>> CPU family: 25
>> Model:17
>> Thread(s) per core: 2
>> Core(s) per socket: 96
>> Socket(s):2
>> Stepping: 1
>> Frequency boost: enabled
>>
: 4800.00
Note that Jens Axboe got even more impressive speedups testing this
on his 512-hw-thread EPYC [1] (390% speedup for 192 threads). I've
noticed I had schedstats and sched debug enabled in my config, so I'll
have to re-run my tests.
Thanks,
Mathieu
[1] https://discuss.s
On Fri, Sep 27, 2024 at 02:51:38AM +, Mark-PK Tsai (蔡沛剛) wrote:
> Hi,
>
> Could someone help to review it or provide suggestions?
> Any comments are welcome.
>
> This patch is intended to allow the rproc driver to handle the
> following use-after-free issue:
>
>
> ### UAF log
What does "UA
On Wed, Oct 02, 2024 at 11:26:27AM -0400, Mathieu Desnoyers wrote:
> On 2024-10-02 16:09, Paul E. McKenney wrote:
> > On Tue, Oct 01, 2024 at 09:02:01PM -0400, Mathieu Desnoyers wrote:
> > > Hazard pointers appear to be a good fit for replacing refcount based lazy
> > > active mm tracking.
> > >
>
Hi,
On Mon, 30 Sep 2024, Michael Vetter wrote:
> The test proves that a function that is being kprobed and uses a
> post_handler cannot be livepatched.
>
> Only one ftrace_ops with FTRACE_OPS_FL_IPMODIFY set may be registered
> to any given function at a time.
>
> Signed-off-by: Michael Vetter
On 2024-10-02 16:09, Paul E. McKenney wrote:
On Tue, Oct 01, 2024 at 09:02:01PM -0400, Mathieu Desnoyers wrote:
Hazard pointers appear to be a good fit for replacing refcount based lazy
active mm tracking.
Highlight:
will-it-scale context_switch1_threads
nr threads (-t) speedup
24
From: 'Alan Stern'
> Sent: 02 October 2024 15:15
>
> On Wed, Oct 02, 2024 at 08:13:15AM +, David Laight wrote:
> > From: 'Alan Stern'
> > > Sent: 01 October 2024 23:57
> > >
> > > On Tue, Oct 01, 2024 at 05:11:05PM +, David Laight wrote:
> > > > From: Alan Stern
> > > > > Sent: 30 Septembe
Hi,
On Mon, 30 Sep 2024, Michael Vetter wrote:
> This naming makes more sense according to the directory structure.
> Especially when we later add more paths.
>
> Signed-off-by: Michael Vetter
> ---
> tools/testing/selftests/livepatch/functions.sh | 6 +++---
> 1 file changed, 3 insertions(+),
Le Wed, Oct 02, 2024 at 04:57:38PM +0200, Frederic Weisbecker a écrit :
> Callbacks enqueued after rcutree_report_cpu_dead() fall into RCU barrier
> blind spot. Report any potential misuse.
>
> Reported-by: Paul E. McKenney
> Signed-off-by: Frederic Weisbecker
> ---
> kernel/rcu/tree.c | 3 +++
On 10/2/24 15:52, Guenter Roeck wrote:
> On 10/2/24 03:26, Vlastimil Babka wrote:
>> On 10/1/24 18:20, Vlastimil Babka wrote:
>>> Guenter Roeck reports that the new slub kunit tests added by commit
>>> 4e1c44b3db79 ("kunit, slub: add test_kfree_rcu() and
>>> test_leak_destroy()") cause a lockup on
On Mon, 30 Sep 2024 19:03:52 +0200 Aleksandr Mikhalitsyn wrote:
> > At this point my question is, should we solve the problem higher and
> > show all the modules in /sys/modules, either way?
>
> Probably, yes. We can ask Luis Chamberlain's opinion on this one.
>
> +cc Luis Chamberlain
>
> >
>
On Wed, Oct 02, 2024 at 08:13:15AM +, David Laight wrote:
> From: 'Alan Stern'
> > Sent: 01 October 2024 23:57
> >
> > On Tue, Oct 01, 2024 at 05:11:05PM +, David Laight wrote:
> > > From: Alan Stern
> > > > Sent: 30 September 2024 19:53
> > > >
> > > > On Mon, Sep 30, 2024 at 07:05:06PM +
Hi Antonio,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 44badc908f2c85711cb18e45e13119c10ad3a05f]
url:
https://github.com/intel-lab-lkp/linux/commits/Antonio-Quartulli/netlink-add-NLA_POLICY_MAX_LEN-macro/20241002-172734
base: 44badc908f2c85711cb18e4
On Wed, Oct 02, 2024 at 01:45:15PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Oct 01, 2024 at 08:42:56PM +0200, Aleksa Sarai wrote:
> > On 2024-10-01, Tycho Andersen wrote:
> > > From: Tycho Andersen
> > >
> > > Zbigniew mentioned at Linux Plumber's that systemd is interested in
> > > s
On Tue, Oct 01, 2024 at 09:02:01PM -0400, Mathieu Desnoyers wrote:
> Hazard pointers appear to be a good fit for replacing refcount based lazy
> active mm tracking.
>
> Highlight:
>
> will-it-scale context_switch1_threads
>
> nr threads (-t) speedup
> 24+3%
> 48
On Wed, Oct 02, 2024 at 09:41:42AM GMT, Michael S. Tsirkin wrote:
virtio_transport_send_pkt in now called on transport fast path,
under RCU read lock. In that case, we have a bug: virtio_add_sgs
is called with GFP_KERNEL, and might sleep.
Pass the gfp flags as an argument, and use GFP_ATOMIC on
On Mon, 2024-09-30 at 11:33 +0200, Michael Vetter wrote:
> Thanks to Miroslav, Petr and Marcos for the reviews!
As the only changes were regarding bash nitpicks I keep my review from
earlier patchset, so:
Reviewed-by: Marcos Paulo de Souza
>
> V4:
> Use variable for /sys/kernel/debug.
> Be con
On Tue, Oct 01, 2024 at 08:42:56PM +0200, Aleksa Sarai wrote:
> On 2024-10-01, Tycho Andersen wrote:
> > From: Tycho Andersen
> >
> > Zbigniew mentioned at Linux Plumber's that systemd is interested in
> > switching to execveat() for service execution, but can't, because the
> > contents of /pro
On 10/2/24 03:26, Vlastimil Babka wrote:
On 10/1/24 18:20, Vlastimil Babka wrote:
Guenter Roeck reports that the new slub kunit tests added by commit
4e1c44b3db79 ("kunit, slub: add test_kfree_rcu() and
test_leak_destroy()") cause a lockup on boot on several architectures
when the kunit tests ar
On 10/1/24 09:20, Vlastimil Babka wrote:
Guenter Roeck reports that the new slub kunit tests added by commit
4e1c44b3db79 ("kunit, slub: add test_kfree_rcu() and
test_leak_destroy()") cause a lockup on boot on several architectures
when the kunit tests are configured to be built-in and not module
h it which
> > would face similar issues with having an unusual method for specifying
> > the stack top so I don't know how much we're really winning.
> I'm not so sure. The thing is a regular stack can be re-used in full - just
> set
> the RSP to the end and take ad
On Wed, Sep 11 2024 at 17:11, Huacai Chen wrote:
> Hi, Thomas,
>
> On Fri, Aug 30, 2024 at 5:32 PM Bibo Mao wrote:
>>
>> Interrupts can be routed to maximal four virtual CPUs with one HW
>> EIOINTC interrupt controller model, since interrupt routing is encoded with
>> CPU bitmap and EIOINTC node c
On 9/30/24 3:33 AM, Yaxiong Tian wrote:
From: Yaxiong Tian
To save some running memory,Add __init and __exit to the
module load/unload functions.
Signed-off-by: Yaxiong Tian
---
tools/testing/selftests/bpf/bpf_test_no_cfi/bpf_test_no_cfi.c | 4 ++--
1 file changed, 2 insertions(+), 2 delet
Hello,
On Sun, 29 Sep 2024, Wardenjohn wrote:
> As previous discussion, maintainers think that patch-level sysfs interface is
> the
> only acceptable way to maintain the information of the order that klp_patch
> is
> applied to the system.
>
> However, the previous patch introduce klp_ops int
On Mon, Sep 30, 2024 at 11:59:20PM +, tyrone-wu wrote:
> Previously when retrieving `bpf_link_info.perf_event` for
> kprobe/uprobe/tracepoint, the `name_len` field was not populated by the
> kernel, leaving it to reflect the value initially set by the user. This
> behavior was inconsistent with
Hi Antonio,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 44badc908f2c85711cb18e45e13119c10ad3a05f]
url:
https://github.com/intel-lab-lkp/linux/commits/Antonio-Quartulli/netlink-add-NLA_POLICY_MAX_LEN-macro/20241002-172734
base: 44badc908f2c85711cb18e4
On 10/1/24 18:20, Vlastimil Babka wrote:
> Guenter Roeck reports that the new slub kunit tests added by commit
> 4e1c44b3db79 ("kunit, slub: add test_kfree_rcu() and
> test_leak_destroy()") cause a lockup on boot on several architectures
> when the kunit tests are configured to be built-in and not
Hello,
this email is just a friendly reminder to know if the present patch is going to
be applied or not.
Thank you.
Best Regards,
Alessandro Zanni
On 24/08/06 02:14, Alessandro Zanni wrote:
> Insert raw strings to prevent Python3 from interpreting string literals
> as Unicode strings and "\d"
On 9/27/24 11:15, Jakub Sitnicki wrote:
> On Fri, Sep 27, 2024 at 12:54 AM +02, Michal Luczaj wrote:
>> ...
>> Here's a follow up: my guess is that some checks are missing. I'm not sure
>> if it's the best approach, but this fixes things for me:
>
> So you have already found a bug with a negative
From: 'Alan Stern'
> Sent: 01 October 2024 23:57
>
> On Tue, Oct 01, 2024 at 05:11:05PM +, David Laight wrote:
> > From: Alan Stern
> > > Sent: 30 September 2024 19:53
> > >
> > > On Mon, Sep 30, 2024 at 07:05:06PM +0200, Jonas Oberhauser wrote:
> > > >
> > > >
> > > > Am 9/30/2024 um 6:43 PM
On Wed, 25 Sept 2024 at 19:26, Shuah Khan wrote:
>
> On 9/20/24 04:38, Jakub Kicinski wrote:
> > On Thu, 19 Sep 2024 09:51:47 -0600 Shuah Khan wrote:
> >>> @@ -261,6 +261,7 @@ ifdef INSTALL_PATH
> >>> @ret=1; \
> >>> for TARGET in $(TARGETS) $(INSTALL_DEP_TARGETS); do \
> >>> B
zhangjiao2 writes:
> From: zhang jiao
>
> If there were no anamolies noted, then we can
> simply remove the log file and return,
after the path variable has been initialized.
(minor nit)
>
> Signed-off-by: zhang jiao
> ---
> v1->v2:
> Remove the path after initialization.
>
> to
On Tue, 01 Oct 2024 16:37:30 +0200, Duje Mihanović wrote:
> Hello,
>
> This series adds initial support for the Marvell PXA1908 SoC and
> "samsung,coreprimevelte", a smartphone using the SoC.
>
> USB works and the phone can boot a rootfs from an SD card, but there are
> some warnings in the dme
On Wed, Sep 25, 2024 at 10:24:01AM GMT, Alexei Starovoitov wrote:
> On Tue, Sep 24, 2024 at 12:40 PM Daniel Xu wrote:
> >
> > +
> > +/* Returns constant key value if possible, else -1 */
> > +static long get_constant_map_key(struct bpf_verifier_env *env,
> > +struct
Hit send too early.
On Tue, Oct 1, 2024, at 5:07 PM, Daniel Xu wrote:
> On Wed, Sep 25, 2024 at 10:24:01AM GMT, Alexei Starovoitov wrote:
>> On Tue, Sep 24, 2024 at 12:40 PM Daniel Xu wrote:
>> >
>> > +
>> > +/* Returns constant key value if possible, else -1 */
>> > +static long get_constant_map
ying
> the stack top so I don't know how much we're really winning.
I'm not so sure. The thing is a regular stack can be re-used in full - just set
the RSP to the end and take advantage of the whole stack. A shadow stack can
only be used where there is a token.
> Like we
>
Vishal Annapurve writes:
> On Wed, Sep 11, 2024 at 1:44 AM Ackerley Tng wrote:
>>
>> ...
>> +}
>> +
>> +static void kvm_gmem_evict_inode(struct inode *inode)
>> +{
>> + u64 flags = (u64)inode->i_private;
>> +
>> + if (flags & KVM_GUEST_MEMFD_HUGETLB)
>> + kvm_gmem_huget
On Tue, Oct 01, 2024 at 05:11:05PM +, David Laight wrote:
> From: Alan Stern
> > Sent: 30 September 2024 19:53
> >
> > On Mon, Sep 30, 2024 at 07:05:06PM +0200, Jonas Oberhauser wrote:
> > >
> > >
> > > Am 9/30/2024 um 6:43 PM schrieb Alan Stern:
> > > > On Mon, Sep 30, 2024 at 01:26:53PM +020
On Tue, Oct 1, 2024 at 2:16 PM Petr Pavlu wrote:
>
> On 9/23/24 20:18, Sami Tolvanen wrote:
> > +static void process_variant_type(struct state *state, struct die *cache,
> > + Dwarf_Die *die)
> > +{
> > + process_list_comma(state, cache);
> > + process(cache, "
On Tue, Oct 01, 2024 at 12:06:17PM +0530, Mukesh Ojha wrote:
> On Fri, Sep 27, 2024 at 02:59:09PM -0700, Bjorn Andersson wrote:
> > On Sat, Sep 28, 2024 at 01:07:43AM +0530, Mukesh Ojha wrote:
> > > On Wed, Sep 25, 2024 at 08:41:55PM -0700, Bjorn Andersson wrote:
> > > > On Wed, Sep 25, 2024 at 04:
On Tue, Sep 3, 2024 at 5:38 PM Diego Vieira
wrote:
>
> Add KUnit tests for the kfifo data structure.
> They test the vast majority of macros defined in the kfifo
> header (include/linux/kfifo.h).
>
> These are inspired by the existing tests for the doubly
> linked list in lib/tests/list-test.c (pr
On Tue, Oct 1, 2024 at 2:10 PM Petr Pavlu wrote:
>
> On 9/23/24 20:18, Sami Tolvanen wrote:
> > +static void update_fqn(struct die *cache, Dwarf_Die *die)
> > +{
> > + if (!cache->fqn)
> > + cache->fqn = get_fqn(die) ?: "";
> > +}
>
> When is update_fqn() called with cache->fqn bei
On Tue, Oct 1, 2024 at 2:06 PM Petr Pavlu wrote:
>
> On 9/23/24 20:18, Sami Tolvanen wrote:
> > - for_each(name, get_symbol, &sym);
> > + for_each(name, false, get_symbol, &sym);
> > return sym;
> > }
>
> What is the reason that the for_each() call in symbol_get() is invoked
> with
Hi Petr,
On Tue, Oct 1, 2024 at 2:04 PM Petr Pavlu wrote:
>
> On 9/23/24 20:18, Sami Tolvanen wrote:
> > + if (dwfl_getmodules(dwfl, &process_module, NULL, 0)) {
> > + error("dwfl_getmodules failed for '%s'", argv[n]);
> > + return -1;
> > +
On 2024-10-01, Aleksa Sarai wrote:
> On 2024-10-01, Tycho Andersen wrote:
> > From: Tycho Andersen
> >
> > Zbigniew mentioned at Linux Plumber's that systemd is interested in
> > switching to execveat() for service execution, but can't, because the
> > contents of /proc/pid/comm are the file de
On Tue, Oct 01, 2024 at 10:46:20AM -0300, Jason Gunthorpe wrote:
> On Tue, Oct 01, 2024 at 01:54:05AM -0700, Nicolin Chen wrote:
> > On Thu, Sep 05, 2024 at 10:38:23AM -0700, Nicolin Chen wrote:
> > > On Thu, Sep 05, 2024 at 01:03:53PM -0300, Jason Gunthorpe wrote:
> > > > On Tue, Aug 27, 2024 at 0
On 2024-10-01, Tycho Andersen wrote:
> From: Tycho Andersen
>
> Zbigniew mentioned at Linux Plumber's that systemd is interested in
> switching to execveat() for service execution, but can't, because the
> contents of /proc/pid/comm are the file descriptor which was used,
> instead of the path t
On Tue, Oct 01, 2024 at 10:48:15AM -0300, Jason Gunthorpe wrote:
> On Sun, Sep 29, 2024 at 03:19:42PM +0800, Yi Liu wrote:
> > > So their viommu HW concepts come along with a requirement that there
> > > be a fixed translation for the VM, which we model by attaching a S2
> > > HWPT to the VIOMMU ob
On Mon, Sep 30, 2024 at 03:35:43PM +0900, Kacper Ludwinski wrote:
> This typo has an impact on results of the test results,
> potentially leading to wrong conclusions regarding
> the functionality of a network device.
Did you test this? You are effectively introducing a new test.
Could you include
> My motivation comes from debugging cgroup selftests when strace is quite
> useful and your implementation adds the unnecessary fork which makes the
> strace (slightly) less readable.
This makes sense, thank you for the context. I hadn't considered debugging
considerations much, but I can imagine
On Tue, Oct 01, 2024 at 05:12:38PM +0200, Christian Brauner wrote:
> On Fri, Sep 27, 2024 at 03:21:59PM GMT, Edgecombe, Rick P wrote:
> > Did you catch that a token can be at a different offsets location on the
> > stack
> > depending on args passed to map_shadow_stack? So userspace will need
>
From: Alan Stern
> Sent: 30 September 2024 19:53
>
> On Mon, Sep 30, 2024 at 07:05:06PM +0200, Jonas Oberhauser wrote:
> >
> >
> > Am 9/30/2024 um 6:43 PM schrieb Alan Stern:
> > > On Mon, Sep 30, 2024 at 01:26:53PM +0200, Jonas Oberhauser wrote:
> > > >
> > > >
> > > > Am 9/28/2024 um 4:49 PM sch
On Tue, Oct 01, 2024 at 05:30:51PM +0800, Wenyu Huang wrote:
> 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.
Pls say this in the commit log.
On 9/30/24 13:37, Uladzislau Rezki (Sony) wrote:
> Improve readability of kvfree_rcu_queue_batch() function
> in away that, after a first batch queuing, the loop is break
> and success value is returned to a caller.
>
> There is no reason to loop and check batches further as all
> outstanding obje
This series has been successfully tested. Now when executing the
hugetlb_fault_after_madv selftest the benefits of both patches could
be observed.
# ./hugetlb_fault_after_madv
TAP version 13
1..1
# [INFO] detected default hugetlb page size: 1024 KiB
ok 1 SIGBUS behavior
# Totals: pass:1 fail:0 xfai
On Mon, Sep 30, 2024 at 03:32:25PM GMT, Lorenzo Stoakes wrote:
> On Mon, Sep 30, 2024 at 04:21:23PM GMT, Aleksa Sarai wrote:
> > On 2024-09-30, Lorenzo Stoakes wrote:
> > > On Mon, Sep 30, 2024 at 02:34:33PM GMT, Christian Brauner wrote:
> > > > On Mon, Sep 30, 2024 at 11:39:49AM GMT, Lorenzo Stoa
On Mon, Sep 30, 2024 at 02:07:22PM GMT, Joshua Hahn
wrote:
> The reason I used a fork in the testing is so that I could isolate the niced
> portion of the test to only the CPU hog. If I were to nice(1) --> cg_hog()
> in a single process without forking, this would mean that the cleanup portion
>
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.
On Fri, Sep 27, 2024 at 03:21:59PM GMT, Edgecombe, Rick P wrote:
> On Fri, 2024-09-27 at 10:50 +0200, Christian Brauner wrote:
> > The legacy clone system call had required userspace to know in which
> > direction the stack was growing and then pass down the stack pointer
> > appropriately (e.g., p
On 10/1/24 07:49, Tycho Andersen wrote:
From: Tycho Andersen
We want to ensure that /proc/self/comm stays useful for execveat() callers.
This commit message is vague? What does staying useful mean?
Elaborate on the staying useful and the tests added to ensure.
Add test results as well.
Sig
On Mon, Sep 30, 2024 at 8:10 PM Mark Brown wrote:
>
> The recent addition of support for testing with the x86 specific quirk
> KVM_X86_QUIRK_SLOT_ZAP_ALL disabled in the generic memslot tests broke the
> build of the KVM selftests for all other architectures:
>
> In file included from include/kvm_
On Mon, Sep 30, 2024 at 10:40:30AM -0600, Mathieu Poirier wrote:
> On Mon, Aug 12, 2024 at 03:28:11PM +0800, Lu Baolu wrote:
> > An iommu domain is allocated in rproc_enable_iommu() and is attached to
> > rproc->dev.parent in the same function.
> >
> > Use iommu_paging_domain_alloc() to make it ex
On 9/23/24 20:18, Sami Tolvanen wrote:
> 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.
>
> Sig
On Thu, Sep 05, 2024 at 10:38:23AM -0700, Nicolin Chen wrote:
> On Thu, Sep 05, 2024 at 01:03:53PM -0300, Jason Gunthorpe wrote:
> > On Tue, Aug 27, 2024 at 09:59:43AM -0700, Nicolin Chen wrote:
> > > Introduce a pair of new ioctls to set/unset a per-viommu virtual device id
> > > that should be li
On 9/30/24 20:43, luyun wrote:
在 2024/10/1 04:57, Shuah Khan 写道:
On 9/30/24 02:38, Benjamin Tissoires wrote:
On Sep 29 2024, Yun Lu wrote:
The HID test cases actually run tests using the run-hid-tools-tests.sh
script. However, if installed with "make install", the run-hid-tools-tests.sh
scrip
On Tue, Oct 01, 2024 at 01:54:05AM -0700, Nicolin Chen wrote:
> On Thu, Sep 05, 2024 at 10:38:23AM -0700, Nicolin Chen wrote:
> > On Thu, Sep 05, 2024 at 01:03:53PM -0300, Jason Gunthorpe wrote:
> > > On Tue, Aug 27, 2024 at 09:59:43AM -0700, Nicolin Chen wrote:
> > > > Introduce a pair of new ioct
On 10/1/24 1:55 AM, Guenter Roeck wrote:
> On 9/30/24 11:50, Guenter Roeck wrote:
>> On 9/30/24 01:37, Vlastimil Babka wrote:
>>> Guenter Roeck reports that the new slub kunit tests added by commit
>>> 4e1c44b3db79 ("kunit, slub: add test_kfree_rcu() and
>>> test_leak_destroy()") cause a lockup on
On Tue, Oct 01, 2024 at 12:21:32PM GMT, Christian Brauner wrote:
> On Mon, Sep 30, 2024 at 03:32:25PM GMT, Lorenzo Stoakes wrote:
> > On Mon, Sep 30, 2024 at 04:21:23PM GMT, Aleksa Sarai wrote:
[snip]
> > > Sorry to bike-shed, but to match /proc/self and /proc/thread-self, maybe
> > > they should
On 9/23/24 20:18, Sami Tolvanen wrote:
> 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
1 - 100 of 469563 matches
Mail list logo
