From: Greg KH <gregkh@linuxfoundation.org>
To: yu kuai <yukuai3@huawei.com>
Cc: stable@vger.kernel.org, hughd@google.com,
viro@zeniv.linux.org.uk, yi.zhang@huawei.com,
zhengbin13@huawei.com, houtao1@huawei.com
Subject: Re: [4.19.y PATCH] tmpfs: fix unable to remount nr_inodes from limited to unlimited
Date: Wed, 4 Dec 2019 18:31:52 +0100 [thread overview]
Message-ID: <20191204173152.GA3630950@kroah.com> (raw)
In-Reply-To: <20191204131137.10388-1-yukuai3@huawei.com>
On Wed, Dec 04, 2019 at 09:11:37PM +0800, yu kuai wrote:
> tmpfs support 'size', 'nr_blocks' and 'nr_inodes' mount options. mount or
> remount them to zero means unlimited. 'size' and 'br_blocks' can remount
> from limited to unlimited, while 'nr_inodes' can't.
>
> The problem is fixed since upstream commit 0b5071dd323d ("
> shmem_parse_options(): use a separate structure to keep the results"). But
> in order to backport it, the amount of related patches need to backport is
> huge.
>
> So, I made some local changes to fix the problem.
>
> Signed-off-by: yu kuai <yukuai3@huawei.com>
> ---
> mm/shmem.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2019-12-04 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 13:11 [4.19.y PATCH] tmpfs: fix unable to remount nr_inodes from limited to unlimited yu kuai
2019-12-04 17:31 ` Greg KH [this message]
2019-12-04 17:33 ` Greg KH
2019-12-04 20:13 ` Hugh Dickins
2019-12-05 1:41 ` yukuai (C)
2019-12-05 1:22 ` yukuai (C)
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=20191204173152.GA3630950@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=houtao1@huawei.com \
--cc=hughd@google.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
--cc=zhengbin13@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).