From: Yu Kuai <yukuai1@huaweicloud.com>
To: tj@kernel.org, josef@toxicpanda.com, axboe@kernel.dk
Cc: cgroups@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yukuai3@huawei.com,
yukuai1@huaweicloud.com, yi.zhang@huawei.com
Subject: [PATCH v3 0/5] blk-iocost: random bugfix
Date: Mon, 26 Dec 2022 16:58:54 +0800 [thread overview]
Message-ID: <20221226085859.2701195-1-yukuai1@huaweicloud.com> (raw)
From: Yu Kuai <yukuai3@huawei.com>
changes in v3:
- move some patches into separate patchset
- don't return other error number for match_u64() in patch 1
- instead of checking user input separately, set page directly if
'bps + IOC_PAGE_SIZE' will overflow.
Li Nan (2):
blk-iocost: fix divide by 0 error in calc_lcoefs()
blk-iocost: change div64_u64 to DIV64_U64_ROUND_UP in
ioc_refresh_params()
Yu Kuai (3):
blk-iocost: check return value of match_u64()
blk-iocost: don't allow to configure bio based device
blk-iocost: read params inside lock in sysfs apis
block/blk-iocost.c | 31 +++++++++++++++++++++++++------
1 file changed, 25 insertions(+), 6 deletions(-)
--
2.31.1
next reply other threads:[~2022-12-26 8:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 8:58 Yu Kuai [this message]
2022-12-26 8:58 ` [PATCH v3 1/5] blk-iocost: check return value of match_u64() Yu Kuai
2022-12-26 8:58 ` Yu Kuai
2023-01-04 21:48 ` Tejun Heo
2023-01-04 21:48 ` Tejun Heo
2022-12-26 8:58 ` [PATCH v3 2/5] blk-iocost: don't allow to configure bio based device Yu Kuai
2022-12-26 8:58 ` [PATCH v3 3/5] blk-iocost: read params inside lock in sysfs apis Yu Kuai
2022-12-26 8:58 ` Yu Kuai
2022-12-26 8:58 ` [PATCH v3 4/5] blk-iocost: fix divide by 0 error in calc_lcoefs() Yu Kuai
2022-12-26 8:58 ` Yu Kuai
2023-01-04 21:54 ` Tejun Heo
2023-01-05 1:53 ` Yu Kuai
2023-01-05 1:53 ` Yu Kuai
2022-12-26 8:58 ` [PATCH v3 5/5] blk-iocost: change div64_u64 to DIV64_U64_ROUND_UP in ioc_refresh_params() Yu Kuai
2023-01-04 21:48 ` Tejun Heo
2023-01-04 21:48 ` Tejun Heo
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=20221226085859.2701195-1-yukuai1@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.