From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Netdev <netdev@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, Qingfang DENG <qingfang.deng@siflower.com.cn>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
Masahide NAKAMURA <nakam@linux-ipv6.org>,
Ville Nuorvala <vnuorval@tcs.hut.fi>,
Arnd Bergmann <arnd@arndb.de>, Pavel Machek <pavel@denx.de>
Subject: Re: [PATCH 6.4 0/6] 6.4.3-rc2 review
Date: Wed, 12 Jul 2023 22:01:33 -0600 [thread overview]
Message-ID: <6b374e37-68b3-346a-a6b7-212640e9c868@gmail.com> (raw)
In-Reply-To: <20230712110240.2b232f84@kernel.org>
On 7/12/23 12:02 PM, Jakub Kicinski wrote:
> On Wed, 12 Jul 2023 18:41:46 +0530 Naresh Kamboju wrote:
>> That is the commit id from stable-rc tree.
>>
>> I have re-tested the reported issues multiple times and
>> it seems that it is intermittently reproducible.
>> Following list of links shows kernel crashes while testing
>> selftest net pmtu.sh
>>
>> 1)
>> Unable to handle kernel paging request at virtual address
>> https://lkft.validation.linaro.org/scheduler/job/6579624#L4648
>>
>>
>> 2)
>> include/net/neighbour.h:302 suspicious rcu_dereference_check() usage!
>>
>> https://lkft.validation.linaro.org/scheduler/job/6579625#L7500
>> https://lkft.validation.linaro.org/scheduler/job/6579626#L7509
>> https://lkft.validation.linaro.org/scheduler/job/6579622#L7537
>> https://lkft.validation.linaro.org/scheduler/job/6579623#L7469
>
> Nothing jumps out at me.
>
> David, any ideas?
No. Since it is a selftest in the linux repo, any chance for a git
bisect based on that one test?
prev parent reply other threads:[~2023-07-13 4:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230709203826.141774942@linuxfoundation.org>
2023-07-10 11:41 ` [PATCH 6.4 0/6] 6.4.3-rc2 review Naresh Kamboju
2023-07-12 3:15 ` Jakub Kicinski
2023-07-12 8:31 ` Pavel Machek
2023-07-12 13:11 ` Naresh Kamboju
2023-07-12 18:02 ` Jakub Kicinski
2023-07-13 4:01 ` David Ahern [this message]
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=6b374e37-68b3-346a-a6b7-212640e9c868@gmail.com \
--to=dsahern@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=conor@kernel.org \
--cc=davem@davemloft.net \
--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-kselftest@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=nakam@linux-ipv6.org \
--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=qingfang.deng@siflower.com.cn \
--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 \
--cc=vnuorval@tcs.hut.fi \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).