From: Pavel Begunkov <asml.silence@gmail.com>
To: kernel test robot <oliver.sang@intel.com>, Jens Axboe <axboe@kernel.dk>
Cc: lkp@lists.01.org, lkp@intel.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [io_uring] 811b398582: WARNING:possible_recursive_locking_detected
Date: Mon, 31 Jan 2022 14:42:51 +0000 [thread overview]
Message-ID: <a0dd7976-8b5f-784a-1126-302fb7eaa840@gmail.com> (raw)
In-Reply-To: <20220131131122.GB16385@xsang-OptiPlex-9020>
On 1/31/22 13:11, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with clang-14):
>
> commit: 811b3985828e422a3759cf07a848fa75c17c1db4 ("io_uring: support for user allocated memory for rings/sqes")
> https://github.com/ammarfaizi2/linux-block axboe/linux-block/perf-wip
Would be great if for io_uring related reports it also CCs
io-uring@vger.kernel.org
--
Pavel Begunkov
prev parent reply other threads:[~2022-01-31 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 13:11 kernel test robot
2022-01-31 14:42 ` Pavel Begunkov [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=a0dd7976-8b5f-784a-1126-302fb7eaa840@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--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
Powered by JetHome