Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni :
On Tue, 27 May 2025 11:11:38 +0530 you wrote:
> On linux-next, build for bpf selftest displays a warning:
>
> Warning: Kernel ABI header at 'tools/include/uapi/linux/if_xdp.h'
> differs from late
On 5/27/25 7:41 AM, Saket Kumar Bhaskar wrote:
On linux-next, build for bpf selftest displays a warning:
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_xdp.h'
differs from latest version at 'include/uapi/linux/if_xdp.h'.
Commit 8066e388be48 ("net: add UA
On linux-next, build for bpf selftest displays a warning:
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_xdp.h'
differs from latest version at 'include/uapi/linux/if_xdp.h'.
Commit 8066e388be48 ("net: add UAPI to the header guard in various network
headers&q
When running `make kselftest`, the following compilation warning was
encountered:
mount-notify_test.c: In function ‘fanotify_rmdir’:
mount-notify_test.c:490:17: warning: ignoring return value of ‘chdir’ declared
with attribute ‘warn_unused_result’ [-Wunused-result]
490 | chdir
On Mon, May 12, 2025 at 2:23 AM Greg KH wrote:
>
> On Mon, May 12, 2025 at 02:45:11PM +0530, Saket Kumar Bhaskar wrote:
> > On linux-next, build for bpf selftest displays a warning:
> >
> > Warning: Kernel ABI header at 'tools/include/uapi/linux/if_xdp.h'
On Mon, May 12, 2025 at 02:45:11PM +0530, Saket Kumar Bhaskar wrote:
> On linux-next, build for bpf selftest displays a warning:
>
> Warning: Kernel ABI header at 'tools/include/uapi/linux/if_xdp.h'
> differs from latest version at 'include/uapi/linux/if_xdp.h'
On linux-next, build for bpf selftest displays a warning:
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_xdp.h'
differs from latest version at 'include/uapi/linux/if_xdp.h'.
Commit 8066e388be48 ("net: add UAPI to the header guard in various network
headers&q
h can trigger a confusing "unexpected end of section"
warning which blames .altinstr_replacement rather than the offending
fallthrough function.
Fix that by not caching the section. There's no point in doing that
anyway.
Signed-off-by: Josh Poimboeuf
---
tools/objtool/check.c | 5 +---
On 09/05/25 6:08 pm, Saket Kumar Bhaskar wrote:
On linux-next, build for bpf selftest displays a warning:
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_xdp.h'
differs from latest version at 'include/uapi/linux/if_xdp.h'.
Commit 8066e388be48 ("net: add UA
On linux-next, build for bpf selftest displays a warning:
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_xdp.h'
differs from latest version at 'include/uapi/linux/if_xdp.h'.
Commit 8066e388be48 ("net: add UAPI to the header guard in various network
headers&q
For tests without fixtures the variant argument is unused.
This is intentional, prevent to compiler from complaining.
Example warning:
harness-selftest.c: In function 'wrapper_standalone_pass':
../kselftest_harness.h:181:52: error: unused parameter 'variant'
[-Wer
Fixes and cleanups for various issues in the vDSO selftests.
Signed-off-by: Thomas Weißschuh
---
Changes in v2:
- Refer to -Wstrict-prototypes over -Wold-style-prototypes
- Pick up Acks
- Enable fixed warnings in Makefile
- Link to v1:
https://lore.kernel.org/r/20250502-selftests-vdso-fixes-v1-0
email id.
Yes, please do this.
I have sent a new patch series. The email ids should match now. I have also
addressed the build warning that had appeared earlier so those changes won't
have to be made manually using "git fixup".
Thanks,
Sahil
> > > >
> > > > ./patches/or1k-20250418/0001-openrisc-Refactor-struct-cpuinfo_or1k-to-reduce-dupl.patch
> > > >
> > > > --
On 4/11/25 2:00 PM, Thomas Weißschuh wrote:
> For tests without fixtures the variant argument is unused.
> This is intentional, prevent to compiler from complaining.
>
> Example warning:
>
> harness-selftest.c: In function 'wrapper_standalone_pass':
> ../ks
The previous patch improved the rcu_seq_done_exact() function by adding
a meaningful constant for the guardband.
Ensure that this is working for the future by a quick check during
rcu_gp_init().
Reviewed-by: Paul E. McKenney
Signed-off-by: Joel Fernandes
---
kernel/rcu/tree.c | 6 ++
1 fil
---
WARNING: From:/Signed-off-by: email address mismatch: 'From: Sahil Siddiq
' != 'Signed-off-by: Sahil Siddiq '
total: 0 errors, 1 warnings, 102 lines checked
As you can see above the scripts/checkpatch.pl is failing with the warning
about your email and signed-off-by no
t; ./patches/or1k-20250418/0001-openrisc-Refactor-struct-cpuinfo_or1k-to-reduce-dupl.patch
> >
> > ---
> > WARNING: From:/Signed-off-by: email address mismatch: 'From: Sahil
> > Siddiq &#
:
---
./patches/or1k-20250418/0001-openrisc-Refactor-struct-cpuinfo_or1k-to-reduce-dupl.patch
---
WARNING: From:/Signed-off-by
0001-openrisc-Refactor-struct-cpuinfo_or1k-to-reduce-dupl.patch
-------
WARNING: From:/Signed-off-by: email address mismatch: 'From: Sahil Siddiq
' != 'Signed-off-by: Sahil Siddiq '
total: 0 errors, 1 warnings
gt;> Since long time ago, the only user of vq->log is vhost-net. The concern is
>>>> to add support for more devices (i.e. vhost-scsi or vsock) may reveals
>>>> unknown issue in the vhost API. Add a WARNING.
>>>>
>>>> Suggested-by: Joao Martins
is
> >> to add support for more devices (i.e. vhost-scsi or vsock) may reveals
> >> unknown issue in the vhost API. Add a WARNING.
> >>
> >> Suggested-by: Joao Martins
> >> Signed-off-by: Dongli Zhang
> >
> >
> > Userspace can trigger
gt; unknown issue in the vhost API. Add a WARNING.
>>
>> Suggested-by: Joao Martins
>> Signed-off-by: Dongli Zhang
>
>
> Userspace can trigger this I think, this is a problem since
> people run with reboot on warn.
I think it will be a severe kernel bug (page faul
On Wed, Apr 02, 2025 at 11:29:54PM -0700, Dongli Zhang wrote:
> Since long time ago, the only user of vq->log is vhost-net. The concern is
> to add support for more devices (i.e. vhost-scsi or vsock) may reveals
> unknown issue in the vhost API. Add a WARNING.
>
> Suggeste
For tests without fixtures the variant argument is unused.
This is intentional, prevent to compiler from complaining.
Example warning:
harness-selftest.c: In function 'wrapper_standalone_pass':
../kselftest_harness.h:181:52: error: unused parameter 'variant'
[-Wer
On 09.04.25 12:31, David Hildenbrand wrote:
On 09.04.25 12:25, Anshuman Khandual wrote:
On 4/9/25 15:51, David Hildenbrand wrote:
On 09.04.25 12:09, Anshuman Khandual wrote:
On 4/9/25 15:27, David Hildenbrand wrote:
On 09.04.25 11:50, Anshuman Khandual wrote:
Following build warning
On 4/7/25 00:52, Thomas Weißschuh wrote:
For tests without fixtures the variant argument is unused.
This is intentional, prevent to compiler from complaining.
Include the warning in the change log for reference.
Signed-off-by: Thomas Weißschuh
---
tools/testing/selftests
On 4/9/25 15:51, David Hildenbrand wrote:
> On 09.04.25 12:09, Anshuman Khandual wrote:
>>
>>
>> On 4/9/25 15:27, David Hildenbrand wrote:
>>> On 09.04.25 11:50, Anshuman Khandual wrote:
>>>> Following build warning comes up for cow test as 'tran
On 09.04.25 12:25, Anshuman Khandual wrote:
On 4/9/25 15:51, David Hildenbrand wrote:
On 09.04.25 12:09, Anshuman Khandual wrote:
On 4/9/25 15:27, David Hildenbrand wrote:
On 09.04.25 11:50, Anshuman Khandual wrote:
Following build warning comes up for cow test as 'transferred'
On 09.04.25 12:09, Anshuman Khandual wrote:
On 4/9/25 15:27, David Hildenbrand wrote:
On 09.04.25 11:50, Anshuman Khandual wrote:
Following build warning comes up for cow test as 'transferred' variable has
not been initialized. Fix the warning via zero init for the variabl
On 4/9/25 15:27, David Hildenbrand wrote:
> On 09.04.25 11:50, Anshuman Khandual wrote:
>> Following build warning comes up for cow test as 'transferred' variable has
>> not been initialized. Fix the warning via zero init for the variable.
>>
>>
On 09.04.25 11:50, Anshuman Khandual wrote:
Following build warning comes up for cow test as 'transferred' variable has
not been initialized. Fix the warning via zero init for the variable.
CC cow
cow.c: In function ‘do_test_vmsplice_in_parent’:
cow.c:365:61: warning: ‘transf
Following build warning comes up for cow test as 'transferred' variable has
not been initialized. Fix the warning via zero init for the variable.
CC cow
cow.c: In function ‘do_test_vmsplice_in_parent’:
cow.c:365:61: warning: ‘transferred’ may be used uninitialized
[-Wmaybe-uni
For tests without fixtures the variant argument is unused.
This is intentional, prevent to compiler from complaining.
Signed-off-by: Thomas Weißschuh
---
tools/testing/selftests/kselftest_harness.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/kselft
Hi Stafford,
On 4/3/25 7:36 PM, Stafford Horne wrote:
[...]
I will just take this fix and apply it to the series (git fixup) rather than
take this patch as is. Also, as registers should be unsigned short, I think
we should change the type to that.
I will fixup patches in place.
Sure thing.
ke use of the mtspr
> macro.
>
> The kernel test robot reported an asm constraint-related warning and
> error related to the usage of mtspr in these functions. This is because
> the compiler is unable to verify that the constraints are not breached
> by functions which call cache_l
Since long time ago, the only user of vq->log is vhost-net. The concern is
to add support for more devices (i.e. vhost-scsi or vsock) may reveals
unknown issue in the vhost API. Add a WARNING.
Suggested-by: Joao Martins
Signed-off-by: Dongli Zhang
---
drivers/vhost/vhost.c |
Commit c5c6fd8be51207f0abd3 ("openrisc: Introduce new utility functions
to flush and invalidate caches") introduced new functions to flush or
invalidate a range of addresses. These functions make use of the mtspr
macro.
The kernel test robot reported an asm constraint-related warning
ca2f73a167 R15: 0001
[ cut here ]--------
WARNING: CPU: 0 PID: 5302 at net/core/dev.c:12104
__dev_change_net_namespace+0x16f9/0x1890 net/core/dev.c:12104
Modules linked in:
CPU: 0 UID: 0 PID: 5302 Comm: syz-executor142 Not tainted
6.14.0-syzkaller-03565-gf6e0150b2003
On Wed, Mar 26, 2025 at 10:50:13PM +, Joel Fernandes wrote:
>
>
> > On Mar 26, 2025, at 6:36 PM, Paul E. McKenney wrote:
> >
> > On Mon, Mar 24, 2025 at 01:01:54PM -0400, Joel Fernandes wrote:
> >> The previous patch improved the rcu_seq_done_exact() function by adding
> >> a meaningful co
> On Mar 26, 2025, at 6:36 PM, Paul E. McKenney wrote:
>
> On Mon, Mar 24, 2025 at 01:01:54PM -0400, Joel Fernandes wrote:
>> The previous patch improved the rcu_seq_done_exact() function by adding
>> a meaningful constant for the guardband.
>>
>> Ensure that this is working for the future by
On Mon, Mar 24, 2025 at 01:01:54PM -0400, Joel Fernandes wrote:
> The previous patch improved the rcu_seq_done_exact() function by adding
> a meaningful constant for the guardband.
>
> Ensure that this is working for the future by a quick check during
> rcu_gp_init().
>
> Signed-off-by: Joel Fern
The previous patch improved the rcu_seq_done_exact() function by adding
a meaningful constant for the guardband.
Ensure that this is working for the future by a quick check during
rcu_gp_init().
Signed-off-by: Joel Fernandes
---
kernel/rcu/tree.c | 5 +
1 file changed, 5 insertions(+)
diff
Since long time ago, the only user of vq->log is vhost-net. The concern is
to add support for more devices (i.e. vhost-scsi or vsock) may reveals
unknown issue in the vhost API. Add a WARNING.
Suggested-by: Joao Martins
Signed-off-by: Dongli Zhang
---
drivers/vhost/vhost.c |
From: "Paul E. McKenney"
The WARN_ON_ONCE() in ct_kernel_exit_state() follows the call to
ct_state_inc(), which means that RCU is not watching this WARN_ON_ONCE().
This can (and does) result in extraneous lockdep warnings when this
WARN_ON_ONCE() triggers. These extraneous warnings are the oppos
For tests without fixtures the variant argument is unused.
This is intentional, prevent to compiler from complaining.
Signed-off-by: Thomas Weißschuh
---
tools/testing/selftests/kselftest_harness.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/kselft
Direct HLT instruction execution causes #VEs for TDX VMs which is routed
to hypervisor via TDCALL. safe_halt() routines execute HLT in STI-shadow
so IRQs need to remain disabled until the TDCALL to ensure that pending
IRQs are correctly treated as wake events.
Emit warning and fail emulation if
Direct HLT instruction execution causes #VEs for TDX VMs which is routed
to hypervisor via TDCALL. safe_halt() routines execute HLT in STI-shadow
so IRQs need to remain disabled until the TDCALL to ensure that pending
IRQs are correctly treated as wake events.
Emit warning and fail emulation if
Direct HLT instruction execution causes #VEs for TDX VMs which is routed
to hypervisor via TDCALL. safe_halt() routines execute HLT in STI-shadow
so IRQs need to remain disabled until the TDCALL to ensure that pending
IRQs are correctly treated as wake events.
Emit warning and fail emulation if
yzbot-assets/f03793fc001b/vmlinux-a64dcfb4.xz
>>> kernel image:
>>> https://storage.googleapis.com/syzbot-assets/ae71c33eae14/Image-a64dcfb4.gz.xz
>>>
>>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>>> Reported-by: syzbot+ae5b
ts/ae71c33eae14/Image-a64dcfb4.gz.xz
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+ae5b16688c0c675b1...@syzkaller.appspotmail.com
> >
> > [ cut here ]
> > WARNING: CPU: 0 PID:
is.com/syzbot-assets/f03793fc001b/vmlinux-a64dcfb4.xz
> kernel image:
> https://storage.googleapis.com/syzbot-assets/ae71c33eae14/Image-a64dcfb4.gz.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+ae5b16688c0c675b1...@syzkaller.appsp
u fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ae5b16688c0c675b1...@syzkaller.appspotmail.com
[ cut here ]
WARNING: CPU: 0 PID: 6430 at kernel/rcu/srcutree.c:1798
srcu_invoke_callbacks+0x368/0x3d8
Modules linked in:
CPU: 0 UID: 0 PID: 6430
On Tue, 11 Feb 2025 10:32:55 +0100 "Arnd Bergmann" wrote:
> On Tue, Feb 11, 2025, at 10:23, Naresh Kamboju wrote:
> > Regressions on arm64 Juno-r2 device while running LTP syscalls tests
> > madvise01 warnings on the Linux next-20250210 tag.
> >
> > First seen on next-20250210
> > Good: next-2025
ession is reproducible with CONFIG_ARM64_64K_PAGES=y
>
> Test regression: LTP madvise01 WARNING include/linux/rwsem.h madvise_unlock
> Reported-by: Linux Kernel Functional Testing
>
> ## Test log
> command: madvise01
> [ 1190.422933] /usr/local/bin/kirk[359]: starting test madvis
t; This regression is reproducible with CONFIG_ARM64_64K_PAGES=y
>
> Test regression: LTP madvise01 WARNING include/linux/rwsem.h madvise_unlock
> Reported-by: Linux Kernel Functional Testing
>
> ## Test log
> command: madvise01
> [ 1190.422933] /usr/local/bin/kirk[359]: starting
Regressions on arm64 Juno-r2 device while running LTP syscalls tests
madvise01 warnings on the Linux next-20250210 tag.
First seen on next-20250210
Good: next-20250207
Bad: next-20250210
This regression is reproducible with CONFIG_ARM64_64K_PAGES=y
Test regression: LTP madvise01 WARNING include
On Fri, Feb 07, 2025 at 10:45:39AM -0800, Breno Leitao wrote:
> On Fri, Feb 07, 2025 at 05:26:06PM +, Mark Brown wrote:
> > On Fri, Feb 07, 2025 at 03:06:42AM -0800, Breno Leitao wrote:
> > > Fix compiler warning about potentially uninitialized orig_fpmr variable:
Hello Mark,
On Fri, Feb 07, 2025 at 05:26:06PM +, Mark Brown wrote:
> On Fri, Feb 07, 2025 at 03:06:42AM -0800, Breno Leitao wrote:
> > Fix compiler warning about potentially uninitialized orig_fpmr variable:
> >
> > testcases/fpmr_siginfo.c: In function ‘fpmr_presen
Since long time ago, the only user of vq->log is vhost-net. The concern is
to add support for more devices (i.e. vhost-scsi or vsock) may reveals
unknown issue in the vhost API. Add a WARNING.
Suggested-by: Joao Martins
Signed-off-by: Dongli Zhang
---
drivers/vhost/vhost.c |
On Fri, Feb 07, 2025 at 03:06:42AM -0800, Breno Leitao wrote:
> Fix compiler warning about potentially uninitialized orig_fpmr variable:
>
> testcases/fpmr_siginfo.c: In function ‘fpmr_present’:
> testcases/fpmr_siginfo.c:68:25: warning: ‘orig_fpmr’ may be used
> u
Fix compiler warning about potentially uninitialized orig_fpmr variable:
testcases/fpmr_siginfo.c: In function ‘fpmr_present’:
testcases/fpmr_siginfo.c:68:25: warning: ‘orig_fpmr’ may be used
uninitialized in this function [-Wmaybe-uninitialized
On Thu, Feb 06, 2025 at 02:15:09AM -0800, Paul E. McKenney wrote:
> The WARN_ON_ONCE() in ct_kernel_exit_state() follows the call to
> ct_state_inc(), which means that RCU is not watching this WARN_ON_ONCE().
> This can (and does) result in extraneous lockdep warnings when this
> WARN_ON_ONCE() tri
The WARN_ON_ONCE() in ct_kernel_exit_state() follows the call to
ct_state_inc(), which means that RCU is not watching this WARN_ON_ONCE().
This can (and does) result in extraneous lockdep warnings when this
WARN_ON_ONCE() triggers. These extraneous warnings are the opposite
of helpful.
Therefore,
ll pop out as the following.
> >
> > CC pidfd_fdinfo_test
> > pidfd_fdinfo_test.c: In function ‘child_fdinfo_nspid_test’:
> > pidfd_fdinfo_test.c:231:13: warning: implicit declaration of function \
> > ‘mount’ [-Wimplicit-function-declaration]
> >
Hello *,
On Wed, 5 Feb 2025 13:50:31 +0800, I Hsin Cheng
wrote:
> In the compilation of pidfs_setns_test.c , a warning as the following
> will pop out.
>
> pidfd_setns_test.c: In function ‘current_nsset_setup’:
> pidfd_setns_test.c:173:54: warning: implicit declaration of func
.c: In function ‘child_fdinfo_nspid_test’:
> pidfd_fdinfo_test.c:231:13: warning: implicit declaration of function \
> ‘mount’ [-Wimplicit-function-declaration]
> 231 | r = mount(NULL, "/", NULL, MS_REC | MS_PRIVATE, 0);
> | ^
> pidfd_fdinfo_test.c:231:36: erro
When compiling selftests files under tools/testing/selftests/pidfd/ ,
some compiling errors and warnings will pop out as the following.
CC pidfd_fdinfo_test
pidfd_fdinfo_test.c: In function ‘child_fdinfo_nspid_test’:
pidfd_fdinfo_test.c:231:13: warning: implicit declaration of function
In the compilation of pidfs_setns_test.c , a warning as the following
will pop out.
pidfd_setns_test.c: In function ‘current_nsset_setup’:
pidfd_setns_test.c:173:54: warning: implicit declaration of function \
‘ioctl’ [-Wimplicit-function-declaration]
173 | self
From: Brian Norris
[ Upstream commit 7687c66c18c66d4ccd9949c6f641c0e7b5773483 ]
If the header is included in a test without
certain other headers, it produces compiler warnings like:
In file included from [...]
../include/kunit/platform_device.h:15:57: warning: ‘struct completion’
declared
From: Brian Norris
[ Upstream commit 7687c66c18c66d4ccd9949c6f641c0e7b5773483 ]
If the header is included in a test without
certain other headers, it produces compiler warnings like:
In file included from [...]
../include/kunit/platform_device.h:15:57: warning: ‘struct completion’
declared
On Thu, Jan 16, 2025 at 03:03:56PM +0100, Uladzislau Rezki wrote:
> Hello, Cheung Wall!
>
> >
> > I am writing to report a potential vulnerability identified in the
> > Linux Kernel version v6.12-rc4. This vulnerability was discovered
> > while i was testing the kernel.
> >
> > Linux Kernel Repo
Hello, Cheung Wall!
>
> I am writing to report a potential vulnerability identified in the
> Linux Kernel version v6.12-rc4. This vulnerability was discovered
> while i was testing the kernel.
>
> Linux Kernel Repository Git Commit:
> 42f7652d3eb527d03665b09edac47f85fb600924 (tag: v6.12-rc4)
>
Hello,
I am writing to report a potential vulnerability identified in the
Linux Kernel version v6.12-rc4. This vulnerability was discovered
while i was testing the kernel.
Linux Kernel Repository Git Commit:
42f7652d3eb527d03665b09edac47f85fb600924 (tag: v6.12-rc4)
Bug Location: 0010:rcu_sr_norm
On Wed, Dec 11, 2024 at 11:09:46AM +0530, Naresh Kamboju wrote:
[Gentle Reminder]
On Mon, 26 Aug 2024 at 18:50, Naresh Kamboju wrote:
The following kernel warning is noticed on all arch and all devices while
running selftests: core: unshare_test on Linux next-20240823 and next-20240826
[ cut here ]--------
WARNING: CPU: 0 PID: 5837 at net/ieee802154/core.c:258
cfg802154_switch_netns+0x3c7/0x3d0 net/ieee802154/core.c:258
Modules linked in:
CPU: 0 UID: 0 PID: 5837 Comm: syz-executor125 Not tainted
6.13.0-rc6-syzkaller-00918-g7b24f164cf00 #0
Hardware name: Google Google Compute Engine/Goog
On Sun, 5 Jan 2025 at 19:52, Sasha Levin wrote:
>
> I'm sorry, this is my bad: I haven't realized anyone else will be
> looking at these results...
>
> Naresh, I'm cheating and using this tree to bisect the issue you've
> originally reported in
> https://lore.kernel.org/all/ca+g9fyvcbvbabg+m7brkfp
I'm sorry, this is my bad: I haven't realized anyone else will be
looking at these results...
Naresh, I'm cheating and using this tree to bisect the issue you've
originally reported in
https://lore.kernel.org/all/ca+g9fyvcbvbabg+m7brkfpgcgzuck+khhtfx7hfvw6gmn2x...@mail.gmail.com/
.
It seems we c
On Sun, Jan 5, 2025 at 2:33 PM Miguel Ojeda
wrote:
>
> Thanks for the report! I think there is nothing to be done here given
> the details above.
To clarify: v6.11.y is newer (and EOL), v6.12.y LTS is newer, and
older LTSs had the Rust toolchain pinned.
If there is something I am missing, please
eem unrelated, old but rebased/recommitted recently (without SoB).
> warning: the feature `new_uninit` has been stable since 1.82.0 and no
> longer requires an attribute to enable
> --> /rust/kernel/lib.rs:17:12
>|
> 17 | #![feature(new_uninit)]
>|
The following kselftest rust builds failed on sashal/linus-next.git
due to following build warnings / errors.
Good: 829d8581c398a96deea1d6bc78578950347dcbec
Bad: b2d472701a703596889c3fd067fd8929aeffc4be
Build error:
--
warning: the feature `new_uninit` has been stable since 1.82.0
On Sat, 14 Dec 2024 at 02:09, Brian Norris wrote:
>
> If the header is included in a test without
> certain other headers, it produces compiler warnings like:
>
> In file included from [...]
> ../include/kunit/platform_device.h:15:57: warning: ‘struct completion’
> declared
syzbot has found a reproducer for the following issue on:
HEAD commit:a0e3919a2df2 Merge tag 'usb-6.13-rc3' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15a4c34458
kernel config: https://syzkaller.appspot.com/x/.config?x=b874549
If the header is included in a test without
certain other headers, it produces compiler warnings like:
In file included from [...]
../include/kunit/platform_device.h:15:57: warning: ‘struct completion’
declared inside parameter list will not be visible outside of this
definition or declaration
[Gentle Reminder]
On Mon, 26 Aug 2024 at 18:50, Naresh Kamboju wrote:
>
> The following kernel warning is noticed on all arch and all devices while
> running selftests: core: unshare_test on Linux next-20240823 and
> next-20240826.
>
> First seen on next-20240823.
>
ue, please add the following tag to the commit:
Reported-by: syzbot+bd5829ba3619f08e2...@syzkaller.appspotmail.com
R10: R11: 0246 R12: 0002
R13: R14: 7f2cedb45fa0 R15: 7ffcd711e1d8
[ cut here ]--------
WARNING: CPU: 0
---[ cut here ]
WARNING: CPU: 0 PID: 5337 at net/core/dev.c:11738
__dev_change_net_namespace+0x16ed/0x1820 net/core/dev.c:11738
Modules linked in:
CPU: 0 UID: 0 PID: 5337 Comm: syz.0.0 Not tainted
6.12.0-syzkaller-09073-g9f16d5e6f220 #0
Hardware name: QEMU Standard PC (Q35 + ICH9
On 2024-11-04 12:47:26 [+0100], Peter Zijlstra wrote:
> On Mon, Nov 04, 2024 at 12:45:06PM +0100, Peter Zijlstra wrote:
> > diff --git a/mm/kasan/generic.c b/mm/kasan/generic.c
> > index 6310a180278b..ac9f6682bb2f 100644
> > --- a/mm/kasan/generic.c
> > +++ b/mm/kasan/generic.c
> > @@ -521,12 +521,
From: "Paul E. McKenney"
Currently, once an RCU CPU stall warning decides to dump the stalling
CPUs' stacks, the rcu_dump_cpu_stacks() function persists until it
has gone through the full list. Unfortunately, if the stalled grace
periods ends midway through, this function will be
On Mon, 4 Nov 2024 at 12:45, Peter Zijlstra wrote:
>
> On Mon, Nov 04, 2024 at 12:25:03PM +0100, Vlastimil Babka wrote:
> > On 11/4/24 12:11, Vlastimil Babka wrote:
>
> > >> __alloc_pages_noprof+0x292/0x710 mm/page_alloc.c:4771
> > >> alloc_pages_mpol_noprof+0x3e8/0x680 mm/mempolicy.c:2265
> > >
On Mon, Nov 04, 2024 at 12:25:03PM +0100, Vlastimil Babka wrote:
> On 11/4/24 12:11, Vlastimil Babka wrote:
> >> __alloc_pages_noprof+0x292/0x710 mm/page_alloc.c:4771
> >> alloc_pages_mpol_noprof+0x3e8/0x680 mm/mempolicy.c:2265
> >> stack_depot_save_flags+0x666/0x830 lib/stackdepot.c:627
> >>
On Mon, Nov 04, 2024 at 12:45:06PM +0100, Peter Zijlstra wrote:
> diff --git a/mm/kasan/generic.c b/mm/kasan/generic.c
> index 6310a180278b..ac9f6682bb2f 100644
> --- a/mm/kasan/generic.c
> +++ b/mm/kasan/generic.c
> @@ -521,12 +521,12 @@ size_t kasan_metadata_size(struct kmem_cache *cache,
> bool
On 11/1/24 13:04, Muhammad Usama Anjum wrote:
> On 11/1/24 4:15 PM, Mirsad Todorovac wrote:
>> Coccinelle gives WARNING recommending the use of ARRAY_SIZE() macro
>> definition
>> to improve the code readability:
>>
>> ./tools/testing/selftests/x86/syscall_nu
On 11/1/24 14:48, Peter Xu wrote:
> On Fri, Nov 01, 2024 at 12:15:25PM +0100, Mirsad Todorovac wrote:
>> Coccinelle gives WARNING recommending the use of ARRAY_SIZE() macro
>> definition
>> to improve the code readability:
>>
>> ./tools/testing/selftest
On Fri, Nov 01, 2024 at 12:15:25PM +0100, Mirsad Todorovac wrote:
> Coccinelle gives WARNING recommending the use of ARRAY_SIZE() macro definition
> to improve the code readability:
>
> ./tools/testing/selftests/mm/uffd-unit-tests.c:1484:32-33: WARNING: Use
> ARRAY_SIZE
&g
On 11/1/24 4:15 PM, Mirsad Todorovac wrote:
> Coccinelle gives WARNING recommending the use of ARRAY_SIZE() macro definition
> to improve the code readability:
>
> ./tools/testing/selftests/x86/syscall_numbering.c:316:35-36: WARNING: Use
> ARRAY_SIZE
>
> Fixes: 15c82d98
Coccinelle gives WARNING recommending the use of ARRAY_SIZE() macro definition
to improve the code readability:
./tools/testing/selftests/x86/syscall_numbering.c:316:35-36: WARNING: Use
ARRAY_SIZE
Fixes: 15c82d98a0f78 ("selftests/x86/syscall: Update and extend
syscall_numbering_64")
Coccinelle gives WARNING recommending the use of ARRAY_SIZE() macro definition
to improve the code readability:
./tools/testing/selftests/mm/uffd-unit-tests.c:1484:32-33: WARNING: Use
ARRAY_SIZE
./tools/testing/selftests/mm/uffd-unit-tests.c:1485:30-31: WARNING: Use
ARRAY_SIZE
Fixes
Le Wed, Oct 16, 2024 at 09:18:52AM -0700, Paul E. McKenney a écrit :
> Hello!
>
> This series contains RCU CPU stall-warning changes for v6.13:
>
> 1.Delete unused rcu_gp_might_be_stalled() function.
>
> 2. Stop stall warning from dumping stacks if grace period e
Currently, once an RCU CPU stall warning decides to dump the stalling
CPUs' stacks, the rcu_dump_cpu_stacks() function persists until it
has gone through the full list. Unfortunately, if the stalled grace
periods ends midway through, this function will be dumping stacks of
innocent-bystander
1 - 100 of 7510 matches
Mail list logo
