From: Philip Li <philip.li@intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: kernel test robot <lkp@intel.com>,
Geliang Tang <geliangtang@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
mptcp@lists.01.org, lkp@lists.01.org
Subject: Re: [MPTCP] Re: [selftests] f2ff7f11f9: WARNING:suspicious_RCU_usage
Date: Wed, 28 Oct 2020 07:00:39 +0800 [thread overview]
Message-ID: <20201027230039.GA25647@intel.com> (raw)
In-Reply-To: <c971b9f8-fd4a-292f-a7d8-8f6ef43c347e@tessares.net>
On Tue, Oct 27, 2020 at 04:07:28PM +0100, Matthieu Baerts wrote:
> Hi all,
>
> On 27/10/2020 14:16, kernel test robot wrote:
> > Greeting,
> >
> > FYI, we noticed the following commit (built with gcc-9):
> >
> > commit: f2ff7f11f9a74842245db52d685bf9bc7ac2c4b1 ("selftests: mptcp: add ADD_ADDR IPv6 test cases")
> > https://github.com/multipath-tcp/mptcp_net-next.git export
>
> Thanks for the maintainer of the kernel test robot at Intel for this bug
> report!
thanks, you are welcome!
>
> FYI, this was already reported earlier:
>
> https://github.com/multipath-tcp/mptcp_net-next/issues/102
Thanks for the info, we didn't notice this. We will take a look
of reported issues in future to avoid duplicated report.
>
> And Geliang is working on a fix (a v2 is available).
>
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
> _______________________________________________
> mptcp mailing list -- mptcp@lists.01.org
> To unsubscribe send an email to mptcp-leave@lists.01.org
next prev parent reply other threads:[~2020-10-27 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 13:16 kernel test robot
2020-10-27 15:07 ` [MPTCP] " Matthieu Baerts
2020-10-27 23:00 ` Philip Li [this message]
2020-10-28 19:08 ` [MPTCP] " Matthieu Baerts
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=20201027230039.GA25647@intel.com \
--to=philip.li@intel.com \
--cc=geliangtang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.01.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