block: rate-limit capacity change info log #380
Conversation
|
Upstream branch: f824272 |
|
Upstream branch: f824272 |
blktests-ci
bot
force-pushed
the
series/1024097=>linus-master
branch
from
81485fb to
961d0bf
Compare
|
Upstream branch: f824272 |
blktests-ci
bot
force-pushed
the
series/1024097=>linus-master
branch
from
961d0bf to
32a85ee
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
d782508 to
6099a4d
Compare
|
Upstream branch: e7c375b |
blktests-ci
bot
force-pushed
the
series/1024097=>linus-master
branch
from
32a85ee to
3be8df0
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
6099a4d to
5121c4d
Compare
|
Upstream branch: e7c375b |
blktests-ci
bot
force-pushed
the
series/1024097=>linus-master
branch
from
3be8df0 to
794c8dd
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
5121c4d to
4458758
Compare
|
Upstream branch: 8b69055 |
blktests-ci
bot
force-pushed
the
series/1024097=>linus-master
branch
from
794c8dd to
5b0463b
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
4458758 to
6f43942
Compare
|
Upstream branch: fd95357 |
loop devices under heavy stress-ng loop streessor can trigger many capacity change events in a short time. Each event prints an info message from set_capacity_and_notify(), flooding the console and contributing to soft lockups on slow consoles. Switch the printk in set_capacity_and_notify() to pr_info_ratelimited() so frequent capacity changes do not spam the log while still reporting occasional changes. Cc: [email protected] Signed-off-by: Li Chen <[email protected]> Reviewed-by: Bart Van Assche <[email protected]> Reviewed-by: Chaitanya Kulkarni <[email protected]>
blktests-ci
bot
force-pushed
the
series/1024097=>linus-master
branch
from
5b0463b to
f794300
Compare
Pull request for series with
subject: block: rate-limit capacity change info log
version: 1
url: https://patchwork.kernel.org/project/linux-block/list/?series=1024097