From: Sasha Levin <sashal@kernel.org>
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
gregkh@linuxfoundation.org, patches@lists.linux.dev,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@nabladev.com,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 6.18 000/314] 6.18.17-rc1 review
Date: Thu, 12 Mar 2026 06:06:49 -0400 [thread overview]
Message-ID: <abKQOUd0Uv4WTcYN@laps> (raw)
In-Reply-To: <xbjybmha7fdnnm5gn6p6jyppf4ud2r72rfabvej6egg545ozsu@a4qj43d3iu36>
On Thu, Mar 12, 2026 at 02:35:11PM +0800, Shung-Hsi Yu wrote:
>Hi Sasha,
>
>On Tue, Mar 10, 2026 at 07:19:29AM -0400, Sasha Levin wrote:
>>
>> This is the start of the stable review cycle for the 6.18.17 release.
>> There are 314 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.
>
>BPF selftest is failing due to backported commit efc11a667878 ("bpf:
>Improve bounds when tnum has a single possible value"). The fix is
>commit 024cea2d647e ("selftests/bpf: Avoid simplification of crafted
>bounds test"). Can you pick that up for both 6.18 and 6.19?
Will do.
>FWIW this failure does not point to actual issue of the codebase, just
>that the selftest's expectation not aligning with the kernel.
Great!
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-03-12 10:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 11:19 [PATCH 6.18 000/314] 6.18.17-rc1 review Sasha Levin
2026-03-10 12:47 ` Brett A C Sheffield
2026-03-10 16:41 ` Dileep malepu
2026-03-10 18:32 ` Jeffrin Thalakkottoor
2026-03-10 18:53 ` Florian Fainelli
2026-03-10 23:20 ` Ron Economos
2026-03-11 2:18 ` Peter Schneider
2026-03-11 12:16 ` Mark Brown
2026-03-11 20:56 ` Shuah Khan
2026-03-11 21:25 ` Barry K. Nathan
2026-03-12 6:35 ` Shung-Hsi Yu
2026-03-12 10:06 ` Sasha Levin [this message]
2026-03-12 8:58 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=abKQOUd0Uv4WTcYN@laps \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=shung-hsi.yu@suse.com \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox