From: Markus Elfring <Markus.Elfring@web.de>
To: Boy Wu <boy.wu@mediatek.com>,
cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, Jens Axboe <axboe@kernel.dk>,
Josef Bacik <josef@toxicpanda.com>, Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Angelo Gioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Boris Burkov" <boris@bur.io>,
"Iverlin Wang (王苳霖)" <Iverlin.Wang@mediatek.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>
Subject: Re: [PATCH] blk-cgroup: add spin_lock for u64_stats_update
Date: Fri, 5 Jul 2024 19:05:39 +0200 [thread overview]
Message-ID: <8f3765db-842d-4568-9ac5-1bd9cab9e952@web.de> (raw)
In-Reply-To: <20240705075544.11315-1-boy.wu@mediatek.com>
> In 32bit SMP systems, if the system is stressed on the sys node
> by processes, it may cause blkcg_fill_root_iostats to have a concurrent
> problem on the seqlock in u64_stats_update, which will cause a deadlock
> on u64_stats_fetch_begin in blkcg_print_one_stat.
Would you like to mark any references to functions with parentheses?
> To prevent this problem, add spin_locks.
Another wording suggestion:
Thus use an additional spin lock.
How do you think about to use a summary phrase like “Add a spin lock for stats update
in blkcg_fill_root_iostats()”?
…
> +++ b/block/blk-cgroup.c
> @@ -1134,9 +1134,15 @@ static void blkcg_fill_root_iostats(void)
> cpu_dkstats->sectors[STAT_DISCARD] << 9;
> }
>
> +#if BITS_PER_LONG == 32
> + spin_lock_irq(&blkg->q->queue_lock);
> +#endif
> flags = u64_stats_update_begin_irqsave(&blkg->iostat.sync);
> blkg_iostat_set(&blkg->iostat.cur, &tmp);
> u64_stats_update_end_irqrestore(&blkg->iostat.sync, flags);
> +#if BITS_PER_LONG == 32
> + spin_unlock_irq(&blkg->q->queue_lock);
> +#endif
…
Under which circumstances would you become interested to apply a statement
like “guard(spinlock_irq)(&blkg->q->queue_lock);”?
https://elixir.bootlin.com/linux/v6.10-rc6/source/include/linux/spinlock.h#L567
Regards,
Markus
next prev parent reply other threads:[~2024-07-05 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 7:55 [PATCH] blk-cgroup: add spin_lock for u64_stats_update boy.wu
2024-07-05 17:05 ` Markus Elfring [this message]
2024-07-08 2:52 ` Boy Wu (吳勃誼)
2024-07-08 5:43 ` Markus Elfring
2024-07-10 6:19 ` Boy Wu (吳勃誼)
2024-07-05 17:13 ` [PATCH] " Tejun Heo
2024-07-08 2:00 ` Boy Wu (吳勃誼)
2024-07-08 18:36 ` tj
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=8f3765db-842d-4568-9ac5-1bd9cab9e952@web.de \
--to=markus.elfring@web.de \
--cc=Iverlin.Wang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=axboe@kernel.dk \
--cc=boris@bur.io \
--cc=boy.wu@mediatek.com \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--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