From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
Subject: [PATCH] staging: erofs: remove rcu_read_lock() in erofs_try_to_free_cached_page
Date: Wed, 20 Feb 2019 11:20:26 +0100 [thread overview]
Message-ID: <20190220102026.GA32312@kroah.com> (raw)
In-Reply-To: <fc058e45-a645-c680-2ce0-19de83fffc2e@huawei.com>
On Wed, Feb 20, 2019@10:38:53AM +0800, Gao Xiang wrote:
> Hi Greg,
>
> Could you consider take some time on these two patches for linux-5.1-rc1?
> 1) staging: erofs: fix race of initializing xattrs of a inode at the same time
> 2) staging: erofs: remove rcu_read_lock() in erofs_try_to_free_cached_page
>
> It will be of great help, especially patch 1 (it could cause potential memleak
> in the race condition without it).
Ok, I'll queue them up now, I was waiting for reviewed-by tags from
others to show up :)
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Gao Xiang <gaoxiang25@huawei.com>
Cc: devel@driverdev.osuosl.org, Chao Yu <chao@kernel.org>,
linux-erofs@lists.ozlabs.org, Chao Yu <yuchao0@huawei.com>,
LKML <linux-kernel@vger.kernel.org>,
weidu.du@huawei.com, Fang Wei <fangwei1@huawei.com>,
Miao Xie <miaoxie@huawei.com>
Subject: Re: [PATCH] staging: erofs: remove rcu_read_lock() in erofs_try_to_free_cached_page
Date: Wed, 20 Feb 2019 11:20:26 +0100 [thread overview]
Message-ID: <20190220102026.GA32312@kroah.com> (raw)
In-Reply-To: <fc058e45-a645-c680-2ce0-19de83fffc2e@huawei.com>
On Wed, Feb 20, 2019 at 10:38:53AM +0800, Gao Xiang wrote:
> Hi Greg,
>
> Could you consider take some time on these two patches for linux-5.1-rc1?
> 1) staging: erofs: fix race of initializing xattrs of a inode at the same time
> 2) staging: erofs: remove rcu_read_lock() in erofs_try_to_free_cached_page
>
> It will be of great help, especially patch 1 (it could cause potential memleak
> in the race condition without it).
Ok, I'll queue them up now, I was waiting for reviewed-by tags from
others to show up :)
greg k-h
next prev parent reply other threads:[~2019-02-20 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 8:46 [PATCH] staging: erofs: remove rcu_read_lock() in erofs_try_to_free_cached_page Gao Xiang
2019-02-16 8:46 ` Gao Xiang
2019-02-20 1:26 ` Chao Yu
2019-02-20 1:26 ` Chao Yu
2019-02-20 2:38 ` Gao Xiang
2019-02-20 2:38 ` Gao Xiang
2019-02-20 10:20 ` Greg Kroah-Hartman [this message]
2019-02-20 10:20 ` Greg Kroah-Hartman
2019-02-20 10:33 ` Gao Xiang
2019-02-20 10:33 ` Gao Xiang
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=20190220102026.GA32312@kroah.com \
--to=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.