From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: kernel test robot <oliver.sang@intel.com>, Jens Axboe <axboe@kernel.dk>
Cc: lkp@lists.01.org, lkp@intel.com, ltp@lists.linux.it,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [net] 5aa32dd9bd: INFO:task_blocked_for_more_than#seconds
Date: Wed, 4 May 2022 14:29:10 +0700 [thread overview]
Message-ID: <64cbe8c1-a93f-1aad-2629-9feb6ee7a20e@gnuweeb.org> (raw)
In-Reply-To: <20220504060305.GF30775@xsang-OptiPlex-9020>
On 5/4/22 1:03 PM, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-11):
>
> commit: 5aa32dd9bdb57e4a26143216df5e90f5e5c3dd2c ("net: add support for fast socket release")
> https://github.com/ammarfaizi2/linux-block axboe/linux-block/sock-nolock.2
>
> in testcase: ltp
> version: ltp-x86_64-14c1f76-1_20220430
> with following parameters:
>
> test: cve
> ucode: 0x28
>
> test-description: The LTP testsuite contains a collection of tools for testing the Linux kernel and related features.
> test-url: http://linux-test-project.github.io/
>
>
> on test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz with 16G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
Hello,
Thank you for the testing effort. But it's an abandoned branch, please stop
testing branch: axboe/linux-block/sock-nolock.2.
As Jens has said previously here:
https://lore.kernel.org/lkml/f8de18da-e6ae-e82c-c6eb-6f4de6ce8e98@kernel.dk
=========================================
On Sat, 30 Apr 2022 at 08:58:21 -0600, Jens Axboe wrote:
>
> Please just stop testing that branch, it's been abandoned.
>
> --
> Jens Axboe
=========================================
--
Ammar Faizi
next prev parent reply other threads:[~2022-05-04 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 6:03 kernel test robot
2022-05-04 7:29 ` Ammar Faizi [this message]
2022-05-04 9:07 ` Oliver Sang
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=64cbe8c1-a93f-1aad-2629-9feb6ee7a20e@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=ltp@lists.linux.it \
--cc=oliver.sang@intel.com \
/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
all inboxes | Powered by JetHome®