From: Matthieu Baerts <matttbe@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, "David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Netdev <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review
Date: Tue, 10 Oct 2023 18:51:15 +0200 [thread overview]
Message-ID: <6447b32f-abb9-4459-aca5-3d510a66b685@kernel.org> (raw)
In-Reply-To: <CA+G9fYvWCf4fYuQsVLu0NdN+=W73bW1hr1hiokajktNzPFyYtA@mail.gmail.com>
Hi Naresh,
On 09/10/2023 22:43, Naresh Kamboju wrote:
> On Mon, 9 Oct 2023 at 18:46, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>>
>> This is the start of the stable review cycle for the 6.1.57 release.
>> There are 162 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.
>>
>> Responses should be made by Wed, 11 Oct 2023 13:00:55 +0000.
>> Anything received after that time might be too late.
>>
>> The whole patch series can be found in one patch at:
>> https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.57-rc1.gz
>> or in the git tree and branch at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>
>
> The following kernel warnings were noticed several times on arm x15 devices
> running stable-rc 6.1.57-rc1 while running selftests: net: mptcp_connect.sh
> and netfilter: nft_fib.sh.
>
> The possible unsafe locking scenario detected.
>
> FYI,
> Stable-rc/ linux.6.1.y kernel running stable/ linux.6.5.y selftest in this case.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> kselftest: Running tests in net/mptcp
Thank you for having reported the issue and having added MPTCP ML in Cc!
Just to avoid confusions: the "WARNING" you shared when running
'mptcp_connect.sh' selftest appeared before creating the first MPTCP
connection. It looks like there is no reference to MPTCP in the
calltraces. Also, because you have the same issue with nft_fib.sh, I
would say that this issue is not linked to MPTCP but rather to a recent
modification in the IPv6 stack.
By chance, did you start a "git bisect" to identify the commit causing
this issue?
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
next prev parent reply other threads:[~2023-10-10 16:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 12:59 Greg Kroah-Hartman
2023-10-09 18:44 ` SeongJae Park
2023-10-09 20:43 ` Naresh Kamboju
2023-10-10 16:51 ` Matthieu Baerts [this message]
2023-10-10 17:24 ` Eric Dumazet
2023-10-10 18:59 ` Greg Kroah-Hartman
2023-10-09 22:49 ` Shuah Khan
2023-10-09 23:23 ` Florian Fainelli
2023-10-10 5:53 ` Bagas Sanjaya
2023-10-10 8:10 ` Wang Yugui
2023-10-10 11:28 ` Greg Kroah-Hartman
2023-10-10 11:42 ` Wang Yugui
2023-10-10 18:42 ` Greg Kroah-Hartman
2023-10-10 9:51 ` unneeded btrfs changes -- " Pavel Machek
2023-10-10 16:15 ` Greg Kroah-Hartman
2023-10-10 9:59 ` Jon Hunter
2023-10-10 13:21 ` Takeshi Ogasawara
2023-10-10 18:19 ` Guenter Roeck
2023-10-11 9:40 ` Pavel Machek
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=6447b32f-abb9-4459-aca5-3d510a66b685@kernel.org \
--to=matttbe@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=mptcp@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--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
Powered by JetHome