From: Greg KH <gregkh@linuxfoundation.org>
To: libaokun@huaweicloud.com
Cc: stable@vger.kernel.org, sashal@kernel.org,
patches@lists.linux.dev, hsiangkao@linux.alibaba.com,
yangerkun@huawei.com, libaokun1@huawei.com,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH 6.1 1/3] netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume()
Date: Tue, 23 Jul 2024 19:55:54 +0200 [thread overview]
Message-ID: <2024072345-glitter-emboss-29a1@gregkh> (raw)
In-Reply-To: <20240719134338.1642739-1-libaokun@huaweicloud.com>
On Fri, Jul 19, 2024 at 09:43:36PM +0800, libaokun@huaweicloud.com wrote:
> From: Baokun Li <libaokun1@huawei.com>
>
> [ Upstream commit 85b08b31a22b481ec6528130daf94eee4452e23f ]
>
> Export fscache_put_volume() and add fscache_try_get_volume()
> helper function to allow cachefiles to get/put fscache_volume
> via linux/fscache-cache.h.
>
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
> Link: https://lore.kernel.org/r/20240628062930.2467993-2-libaokun@huaweicloud.com
> Signed-off-by: Christian Brauner <brauner@kernel.org>
> Stable-dep-of: 522018a0de6b ("cachefiles: fix slab-use-after-free in fscache_withdraw_volume()")
> Stable-dep-of: 5d8f80578907 ("cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie()")
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
> ---
> fs/fscache/internal.h | 2 --
> fs/fscache/volume.c | 14 ++++++++++++++
> include/linux/fscache-cache.h | 6 ++++++
> 3 files changed, 20 insertions(+), 2 deletions(-)
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-07-23 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 13:43 [PATCH 6.1 1/3] netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume() libaokun
2024-07-19 13:43 ` [PATCH 6.1 2/3] cachefiles: fix slab-use-after-free in fscache_withdraw_volume() libaokun
2024-07-19 13:43 ` [PATCH 6.1 3/3] cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie() libaokun
2024-07-23 17:55 ` 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=2024072345-glitter-emboss-29a1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brauner@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=libaokun1@huawei.com \
--cc=libaokun@huaweicloud.com \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yangerkun@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