From: Muchun Song <smuchun@gmail.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: mike.kravetz@oracle.com, linux-mm@kvack.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hugetlbfs: make BUG_ON(!inode) takes effect in hugetlbfs_setattr
Date: Mon, 18 Jan 2021 15:59:48 +0800 [thread overview]
Message-ID: <CAPSr9jFQRujOEa_HcqQ6=+hf-jWiGA=+CeWjgwQK+-993gd4Ow@mail.gmail.com> (raw)
In-Reply-To: <20210116090910.5671-1-linmiaohe@huawei.com>
On Sat, Jan 16, 2021 at 5:11 PM Miaohe Lin <linmiaohe@huawei.com> wrote:
>
> When we reach here with inode = NULL, we should have crashed as inode has
> already been dereferenced via hstate_inode. In order to make BUG_ON(!inode)
> takes effect, we should defer initializing hstate until we really need it.
> Also do this for hugetlbfs_inode_info as it's only used when ia_valid is
> verified with ATTR_SIZE.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> fs/hugetlbfs/inode.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
> index 740693d7f255..9b221b87fbea 100644
> --- a/fs/hugetlbfs/inode.c
> +++ b/fs/hugetlbfs/inode.c
> @@ -755,10 +755,8 @@ static long hugetlbfs_fallocate(struct file *file, int mode, loff_t offset,
> static int hugetlbfs_setattr(struct dentry *dentry, struct iattr *attr)
> {
> struct inode *inode = d_inode(dentry);
> - struct hstate *h = hstate_inode(inode);
If inode == NULL, it will panic here when we access inode->i_sb.
I have seen many other file system implementations about setattr,
they all think that d_inode() will return a non-NULL pointer. So
I prefer to just remove the BUG_ON().
Thanks.
> int error;
> unsigned int ia_valid = attr->ia_valid;
> - struct hugetlbfs_inode_info *info = HUGETLBFS_I(inode);
>
> BUG_ON(!inode);
>
> @@ -767,6 +765,8 @@ static int hugetlbfs_setattr(struct dentry *dentry, struct iattr *attr)
> return error;
>
> if (ia_valid & ATTR_SIZE) {
> + struct hstate *h = hstate_inode(inode);
> + struct hugetlbfs_inode_info *info = HUGETLBFS_I(inode);
> loff_t oldsize = inode->i_size;
> loff_t newsize = attr->ia_size;
>
> --
> 2.19.1
>
next prev parent reply other threads:[~2021-01-18 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 9:09 Miaohe Lin
2021-01-18 7:59 ` Muchun Song [this message]
2021-01-18 8:48 ` Miaohe Lin
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='CAPSr9jFQRujOEa_HcqQ6=+hf-jWiGA=+CeWjgwQK+-993gd4Ow@mail.gmail.com' \
--to=smuchun@gmail.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.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