From: Greg KH <gregkh@linuxfoundation.org>
To: Su Yue <l@damenly.su>
Cc: stable@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH stable 5.10.y 0/2] backport two patches to avoid invalid memory access while mounting btrfs crafted image
Date: Wed, 23 Feb 2022 19:21:42 +0100 [thread overview]
Message-ID: <YhZ7NiRzBF4CSZ2i@kroah.com> (raw)
In-Reply-To: <20220222033117.1421286-1-l@damenly.su>
On Tue, Feb 22, 2022 at 11:31:15AM +0800, Su Yue wrote:
> Due to btrfs_item* helpers name changes in v5.17-rc1, here are two manual
> backport patches. Already verified by running fstests.
>
> Su Yue (2):
> btrfs: tree-checker: check item_size for inode_item
> btrfs: tree-checker: check item_size for dev_item
>
> fs/btrfs/tree-checker.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> --
> 2.34.1
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-02-23 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 3:31 [PATCH stable 5.10.y 0/2] backport two patches to avoid invalid memory access while mounting btrfs crafted image Su Yue
2022-02-22 3:31 ` [PATCH stable 5.10.y 1/2] btrfs: tree-checker: check item_size for inode_item Su Yue
2022-02-22 3:31 ` [PATCH stable 5.10.y 2/2] btrfs: tree-checker: check item_size for dev_item Su Yue
2022-02-23 18:21 ` 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=YhZ7NiRzBF4CSZ2i@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=l@damenly.su \
--cc=linux-btrfs@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