From: Greg KH <gregkh@linuxfoundation.org>
To: Yu Kuai <yukuai3@huawei.com>
Cc: jack@suse.cz, paolo.valente@linaro.org, axboe@kernel.dk,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com
Subject: Re: [PATCH linux-4.19.y 0/5] fix memleak of bfq weights_tree node
Date: Wed, 22 Dec 2021 13:10:13 +0100 [thread overview]
Message-ID: <YcMVpesszGG2EABJ@kroah.com> (raw)
In-Reply-To: <20211221113849.2219126-1-yukuai3@huawei.com>
On Tue, Dec 21, 2021 at 07:38:44PM +0800, Yu Kuai wrote:
> Our test found that bfq_weight_counter can leak quite easy. This problem
> can be fixed by patch 4, and other patches is needed to backport patch
> 4.
>
> Federico Motta (2):
> block, bfq: improve asymmetric scenarios detection
> block, bfq: fix asymmetric scenarios detection
>
> Paolo Valente (3):
> block, bfq: fix decrement of num_active_groups
> block, bfq: fix queue removal from weights tree
> block, bfq: fix use after free in bfq_bfqq_expire
>
> block/bfq-iosched.c | 287 +++++++++++++++++++++++++++-----------------
> block/bfq-iosched.h | 76 +++++++++---
> block/bfq-wf2q.c | 56 +++++----
> 3 files changed, 270 insertions(+), 149 deletions(-)
>
> --
> 2.31.1
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2021-12-22 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 11:38 [PATCH linux-4.19.y 0/5] fix memleak of bfq weights_tree node Yu Kuai
2021-12-21 11:38 ` [PATCH linux-4.19.y 1/5] block, bfq: improve asymmetric scenarios detection Yu Kuai
2021-12-21 11:38 ` [PATCH linux-4.19.y 2/5] block, bfq: fix " Yu Kuai
2021-12-21 11:38 ` [PATCH linux-4.19.y 3/5] block, bfq: fix decrement of num_active_groups Yu Kuai
2021-12-21 11:38 ` [PATCH linux-4.19.y 4/5] block, bfq: fix queue removal from weights tree Yu Kuai
2021-12-21 11:38 ` [PATCH linux-4.19.y 5/5] block, bfq: fix use after free in bfq_bfqq_expire Yu Kuai
2021-12-22 12:10 ` Greg KH [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=YcMVpesszGG2EABJ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).