From: Dan Carpenter <error27@gmail.com>
To: tj@kernel.org
Cc: linux-block@vger.kernel.org
Subject: [bug report] memcontrol: schedule throttling if we are congested
Date: Fri, 6 Jan 2023 17:58:55 +0300 [thread overview]
Message-ID: <Y7g3L6fntnTtOm63@kili> (raw)
Hello Tejun Heo,
The patch 2cf855837b89: "memcontrol: schedule throttling if we are
congested" from Jul 3, 2018, leads to the following Smatch static
checker warning:
block/blk-cgroup.c:1863 blkcg_schedule_throttle() warn: sleeping in atomic context
The call tree looks like:
ioc_rqos_merge() <- disables preempt
__cgroup_throttle_swaprate() <- disables preempt
-> blkcg_schedule_throttle()
Here is one of the callers:
mm/swapfile.c
3657 spin_lock(&swap_avail_lock);
^^^^^^^^^^^^^^^^^^^^^^^^^^^
Takes spin lock.
3658 plist_for_each_entry_safe(si, next, &swap_avail_heads[nid],
3659 avail_lists[nid]) {
3660 if (si->bdev) {
3661 blkcg_schedule_throttle(si->bdev->bd_disk, true);
^^^^^^^^^^^^^^^^^^^^^^^
Calls blkcg_schedule_throttle().
3662 break;
3663 }
3664 }
block/blk-cgroup.c
1851 void blkcg_schedule_throttle(struct gendisk *disk, bool use_memdelay)
1852 {
1853 struct request_queue *q = disk->queue;
1854
1855 if (unlikely(current->flags & PF_KTHREAD))
1856 return;
1857
1858 if (current->throttle_queue != q) {
1859 if (!blk_get_queue(q))
1860 return;
1861
1862 if (current->throttle_queue)
1863 blk_put_queue(current->throttle_queue);
^^^^^^^^^^^^^^
Sleeps.
1864 current->throttle_queue = q;
1865 }
1866
1867 if (use_memdelay)
1868 current->use_memdelay = use_memdelay;
1869 set_notify_resume(current);
1870 }
regards,
dan carpenter
next reply other threads:[~2023-01-06 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 14:58 Dan Carpenter [this message]
2023-01-06 17:33 ` [bug report] memcontrol: schedule throttling if we are congested Tejun Heo
2023-01-06 18:49 ` Jens Axboe
2023-01-06 19:09 ` Luis Chamberlain
2023-01-06 20:34 ` [PATCH block/for-6.2-fixes] block: Drop spurious might_sleep() from blk_put_queue() Tejun Heo
2023-01-06 20:45 ` Luis Chamberlain
2023-01-06 20:47 ` Tejun Heo
2023-01-06 20:52 ` Jens Axboe
2023-01-07 8:36 ` Dan Carpenter
2023-01-08 17:49 ` Christoph Hellwig
2023-01-09 3:30 ` Jens Axboe
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=Y7g3L6fntnTtOm63@kili \
--to=error27@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=tj@kernel.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