From: Jens Axboe <axboe@kernel.dk>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
io-uring@vger.kernel.org
Subject: Re: [linux-next:master] [io_uring] b5d3ae202f: WARNING:at_kernel/sched/core.c:#__might_sleep
Date: Mon, 6 Feb 2023 08:25:25 -0700 [thread overview]
Message-ID: <bb47bbcd-7708-cefa-86aa-8ecd0b466ac3@kernel.dk> (raw)
In-Reply-To: <202302062208.24d3e563-oliver.sang@intel.com>
On 2/6/23 7:38 AM, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed WARNING:at_kernel/sched/core.c:#__might_sleep due to commit (built with gcc-11):
>
> commit: b5d3ae202fbfe055aa2a8ae8524531ee1dcab717 ("io_uring: handle TIF_NOTIFY_RESUME when checking for task_work")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> [test failed on linux-next/master 4fafd96910add124586b549ad005dcd179de8a18]
Sent out and queued up a fix for this, thanks for the report.
--
Jens Axboe
prev parent reply other threads:[~2023-02-06 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 14:38 kernel test robot
2023-02-06 15:25 ` Jens Axboe [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=bb47bbcd-7708-cefa-86aa-8ecd0b466ac3@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--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