On Thu, Jan 30, 2025 at 2:29 AM Prasanna Kumar T S M
wrote:
> On 30-01-2025 15:52, Prasanna Kumar T S M wrote:
> >
> > On 28-01-2025 03:03, Weinan Liu wrote:
> > > This change introduces a kernel space unwinder using sframe table for
> > > architectures without ORC unwinder support.
> > >
> > > T
On Thu, Jan 30, 2025 at 2:22 AM Prasanna Kumar T S M
wrote:
> On 28-01-2025 03:03, Weinan Liu wrote:
> > diff --git a/include/linux/sframe_lookup.h b/include/linux/sframe_lookup.h
> > new file mode 100644
> > index ..1c26cf1f38d4
> > --- /dev/null
> > +++ b/include/linux/sframe_lookup
On 2/1/25 12:23 AM, Daniel Xu wrote:
Hi Yonghong,
On Thu, Jan 30, 2025 at 10:28:11PM -0800, Yonghong Song wrote:
On 1/30/25 2:33 PM, Daniel Xu wrote:
Since 67ab80a01886 ("selftests/bpf: Prefer static linking for LLVM
libraries"), only statically linking test_progs is supported. However,
On Sat, 1 Feb 2025 at 10:51, Masahiro Yamada wrote:
>
> This commit addresses the issue by leveraging modpost. Symbol names
> passed to symbol_get() are recorded in the special .no_trim_symbol
> section, which is then parsed by modpost to forcibly keep such symbols.
> The .no_trim_symbol section i
Test that very high constant map keys are not interpreted as an error
value by the verifier. This would previously fail.
Signed-off-by: Daniel Xu
---
.../selftests/bpf/progs/verifier_array_access.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/tools/testing/selftests/bpf
Two fixes for nullness elision. See commits for more details.
Daniel Xu (3):
bpf: verifier: Do not extract constant map keys for irrelevant maps
bpf: selftests: Test constant key extraction on irrelevant maps
bpf: verifier: Disambiguate get_constant_map_key() errors
kernel/bpf/verifier.c
Linus observed that the symbol_request(utf8_data_table) call fails when
CONFIG_UNICODE=y and CONFIG_TRIM_UNUSED_KSYMS=y.
symbol_get() relies on the symbol data being present in the ksymtab for
symbol lookups. However, EXPORT_SYMBOL_GPL(utf8_data_table) is dropped
due to CONFIG_TRIM_UNUSED_KSYMS, a
On Sat, Feb 01, 2025 at 12:12:46PM +0100, Christian Brauner wrote:
> > Intent is for Christian to take this in his tree (if he so wishes) to be
> > clear!
>
> If you send me an updated blurb I can fold it.
Thanks, I therefore propose replacing the cover letter blurb with the below:
8<
If
Add the first version of the virtio-media driver.
This driver acts roughly as a V4L2 relay between user-space and the
virtio virtual device on the host, so it is relatively simple, yet
unconventional. It doesn't use VB2 or other frameworks typically used in
a V4L2 driver, and most of its complexit
On Thu, Jan 30, 2025, at 7:41 PM, Daniel Xu wrote:
> Hi Ilya,
>
> On Thu, Jan 30, 2025, at 2:06 AM, Ilya Leoshkevich wrote:
>> On Wed, 2025-01-29 at 10:45 -0700, Daniel Xu wrote:
>>> On Wed, Jan 29, 2025 at 09:49:12AM -0700, Daniel Xu wrote:
>>> > Hi Ilya,
>>> >
>>> > On Wed, Jan 29, 2025 at 03
On 30/01/25 12:32, Christophe Leroy wrote:
Le 29/01/2025 à 19:17, Purva Yeshi a écrit :
On 27/01/25 13:32, Christophe Leroy wrote:
Le 26/01/2025 à 11:59, Purva Yeshi a écrit :
[Vous ne recevez pas souvent de courriers de purvayeshi...@gmail.com.
Découvrez pourquoi ceci est important à
htt
> Intent is for Christian to take this in his tree (if he so wishes) to be
> clear!
If you send me an updated blurb I can fold it.
On Sat, Feb 01, 2025 at 11:41:58AM +0100, Thomas Weißschuh wrote:
> On 2025-02-01 11:34:38+0100, Willy Tarreau wrote:
> > On Thu, Jan 30, 2025 at 08:54:03PM +0100, Thomas Weißschuh wrote:
> > > From: Thomas Weißschuh
> > >
> > > Add an allocation-free implementation of readdir() and related
> > >
On 2025-02-01 11:34:38+0100, Willy Tarreau wrote:
> On Thu, Jan 30, 2025 at 08:54:03PM +0100, Thomas Weißschuh wrote:
> > From: Thomas Weißschuh
> >
> > Add an allocation-free implementation of readdir() and related
> > functions. The implementation is modelled after the one for FILE.
>
> I thin
On Thu, Jan 30, 2025 at 08:54:03PM +0100, Thomas Weißschuh wrote:
> From: Thomas Weißschuh
>
> Add an allocation-free implementation of readdir() and related
> functions. The implementation is modelled after the one for FILE.
I think you'd need to mention/remind the two important points that
com
On Thu, Jan 23, 2025 at 08:37:41AM +0100, Thomas Weißschuh wrote:
> Avoid using a stale test kernel configuration by always synchronizing
> it to the current source tree.
> kbuild is smart enough to avoid spurious rebuilds.
>
> Shuffle the code around a bit to keep all the commands with side-effec
On Thu, Jan 23, 2025 at 08:37:37AM +0100, Thomas Weißschuh wrote:
> kbuild already contains logic to merge predefines snippets into a
> defconfig file. This already works nicely with the current "defconfig"
> target. Make use of the snippet and drop the custom logic.
>
> Signed-off-by: Thomas Weiß
On Sat, Feb 01, 2025 at 11:17:28AM +0100, Thomas Weißschuh wrote:
> On 2025-02-01 11:13:05+0100, Willy Tarreau wrote:
> > On Thu, Jan 23, 2025 at 08:37:37AM +0100, Thomas Weißschuh wrote:
> > > kbuild already contains logic to merge predefines snippets into a
> > > defconfig file. This already work
On Wed, Jan 22, 2025 at 07:43:44PM +0100, Thomas Weißschuh wrote:
> Support for 32-bit s390 is very easy to implement and useful for
> testing. For example I used to test some generic compat_ptr() logic,
> which is only testable on 32-bit s390.
>
> The series depends on my other series
> "selftest
On 2025-02-01 11:13:05+0100, Willy Tarreau wrote:
> On Thu, Jan 23, 2025 at 08:37:37AM +0100, Thomas Weißschuh wrote:
> > kbuild already contains logic to merge predefines snippets into a
> > defconfig file. This already works nicely with the current "defconfig"
> > target. Make use of the snippet
On Thu, Jan 23, 2025 at 08:37:40AM +0100, Thomas Weißschuh wrote:
> Some targets use the test kernel configuration.
> Executing defconfig in the same make invocation as those targets results
> in errors as the configuration may be in an inconsistent state during
> reconfiguration.
> Avoid this by i
On Thu, Jan 23, 2025 at 08:37:39AM +0100, Thomas Weißschuh wrote:
> "mrproper" unnecessarily cleans a lot of files.
> kbuild is smart enough to handle changed configurations,
> so the cleanup is not necessary and only leads to excessive rebuilds.
Generally for me the mrproper has been needed when
On Thu, Jan 23, 2025 at 08:37:38AM +0100, Thomas Weißschuh wrote:
> The "prepare" target does not need to be run manually.
> kbuild knows when to use it on its own and the target is not even
> documented.
>
> Signed-off-by: Thomas Weißschuh
> ---
> tools/testing/selftests/nolibc/Makefile | 2 +-
Hi Yonghong,
On Thu, Jan 30, 2025 at 10:28:11PM -0800, Yonghong Song wrote:
>
>
>
> On 1/30/25 2:33 PM, Daniel Xu wrote:
> > Since 67ab80a01886 ("selftests/bpf: Prefer static linking for LLVM
> > libraries"), only statically linking test_progs is supported. However,
> > some distros only provid
24 matches
Mail list logo
