From: Yue Hu <zbestahu@gmail.com>
To: Gao Xiang <gaoxiang25@huawei.com>
Cc: <yuchao0@huawei.com>, <gregkh@linuxfoundation.org>,
<linux-erofs@lists.ozlabs.org>, <devel@driverdev.osuosl.org>,
<linux-kernel@vger.kernel.org>, <huyue2@yulong.com>,
Miao Xie <miaoxie@huawei.com>
Subject: Re: [PATCH] staging: erofs: don't check special inode layout
Date: Fri, 28 Jun 2019 12:19:52 +0800 [thread overview]
Message-ID: <20190628121952.000028fc.zbestahu@gmail.com> (raw)
In-Reply-To: <276837dc-b18a-6f20-fc33-d988dff5ae9f@huawei.com>
On Fri, 28 Jun 2019 11:50:21 +0800
Gao Xiang <gaoxiang25@huawei.com> wrote:
> Hi Yue,
>
> On 2019/6/28 11:42, Yue Hu wrote:
> > From: Yue Hu <huyue2@yulong.com>
> >
> > Currently, we will check if inode layout is compression or inline if
> > the inode is special in fill_inode(). Also set ->i_mapping->a_ops for
> > it. That is pointless since the both modes won't be set for special
> > inode when creating EROFS filesystem image. So, let's avoid it.
> >
> > Signed-off-by: Yue Hu <huyue2@yulong.com>
>
> Have you test this patch with some actual image with legacy mkfs since
> new mkfs framework have not supported special inode...
Hi Xiang,
I'm studying the testing :)
However, already check the code handling for special inode in leagcy mkfs as below:
```c
break;
case EROFS_FT_BLKDEV:
case EROFS_FT_CHRDEV:
case EROFS_FT_FIFO:
case EROFS_FT_SOCK:
mkfs_rank_inode(d);
break;
default:
erofs_err("inode[%s] file_type error =%d",
d->i_fullpath,
```
No special inode layout operations, so this change should be fine.
Thx.
>
> I think that is fine in priciple, however, in case to introduce some potential
> issues, I will test this patch later. I will give a Reviewed-by tag after I tested
> this patch.
Thanks.
>
> Thanks,
> Gao Xiang
>
> > ---
> > drivers/staging/erofs/inode.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/staging/erofs/inode.c b/drivers/staging/erofs/inode.c
> > index 1433f25..2fe0f6d 100644
> > --- a/drivers/staging/erofs/inode.c
> > +++ b/drivers/staging/erofs/inode.c
> > @@ -205,6 +205,7 @@ static int fill_inode(struct inode *inode, int isdir)
> > S_ISFIFO(inode->i_mode) || S_ISSOCK(inode->i_mode)) {
> > inode->i_op = &erofs_generic_iops;
> > init_special_inode(inode, inode->i_mode, inode->i_rdev);
> > + goto out_unlock;
> > } else {
> > err = -EIO;
> > goto out_unlock;
> >
next prev parent reply other threads:[~2019-06-28 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 3:42 Yue Hu
2019-06-28 3:50 ` Gao Xiang
2019-06-28 4:19 ` Yue Hu [this message]
2019-06-29 8:38 ` Chao Yu
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=20190628121952.000028fc.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gaoxiang25@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=huyue2@yulong.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=yuchao0@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
Powered by JetHome