From: Sasha Levin <sashal@kernel.org>
To: Khazhismel Kumykov <khazhy@chromium.org>
Cc: stable@vger.kernel.org, linux-block@vger.kernel.org,
Khazhismel Kumykov <khazhy@google.com>
Subject: Re: [PATCH v5.10 0/5] bfq bic/cgroup interaction uaf fixes
Date: Mon, 13 Mar 2023 22:17:46 -0400 [thread overview]
Message-ID: <ZA/ZSuVSy/r8ANvy@sashalap> (raw)
In-Reply-To: <20230313222757.1103179-1-khazhy@google.com>
On Mon, Mar 13, 2023 at 03:27:52PM -0700, Khazhismel Kumykov wrote:
>Pulls in uaf fix for bfqq->bic along with fixups. I pulled in the
>backport dependencies that were also present in 5.15-lts.
>
>NeilBrown (1):
> block/bfq-iosched.c: use "false" rather than "BLK_RW_ASYNC"
>
>Yu Kuai (4):
> block, bfq: fix possible uaf for 'bfqq->bic'
> block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq
> block, bfq: replace 0/1 with false/true in bic apis
> block, bfq: fix uaf for bfqq in bic_set_bfqq()
>
> block/bfq-cgroup.c | 8 ++++----
> block/bfq-iosched.c | 19 +++++++++++++------
> 2 files changed, 17 insertions(+), 10 deletions(-)
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2023-03-14 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 22:27 [PATCH v5.10 0/5] bfq bic/cgroup interaction uaf fixes Khazhismel Kumykov
2023-03-13 22:27 ` [PATCH v5.10 1/5] block, bfq: fix possible uaf for 'bfqq->bic' Khazhismel Kumykov
2023-03-13 22:27 ` [PATCH v5.10 2/5] block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq Khazhismel Kumykov
2023-03-13 22:27 ` [PATCH v5.10 3/5] block/bfq-iosched.c: use "false" rather than "BLK_RW_ASYNC" Khazhismel Kumykov
2023-03-13 22:27 ` [PATCH v5.10 4/5] block, bfq: replace 0/1 with false/true in bic apis Khazhismel Kumykov
2023-03-13 22:27 ` [PATCH v5.10 5/5] block, bfq: fix uaf for bfqq in bic_set_bfqq() Khazhismel Kumykov
2023-03-14 2:17 ` Sasha Levin [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=ZA/ZSuVSy/r8ANvy@sashalap \
--to=sashal@kernel.org \
--cc=khazhy@chromium.org \
--cc=khazhy@google.com \
--cc=linux-block@vger.kernel.org \
--cc=stable@vger.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