From: Yue Hu <zbestahu@gmail.com>
To: Xiang Gao <hsiangkao@linux.alibaba.com>
Cc: Yue Hu <huyue2@coolpad.com>,
linux-erofs@lists.ozlabs.org, zhangwen@coolpad.com
Subject: Re: [RFC PATCH] erofs-utils: fsck: support fragments
Date: Wed, 4 Jan 2023 15:26:51 +0800 [thread overview]
Message-ID: <20230104152651.000051df.zbestahu@gmail.com> (raw)
In-Reply-To: <5236b19c-763f-9a5b-a0c1-4c59fa7c6d05@linux.alibaba.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GB18030, Size: 1590 bytes --]
On Wed, 4 Jan 2023 11:32:36 +0800
Xiang Gao <hsiangkao@linux.alibaba.com> wrote:
> On 2023/1/4 11:24, Yue Hu wrote:
> > Hi Xiang,
> >
> > On Wed, 4 Jan 2023 10:48:40 +0800
> > Xiang Gao <hsiangkao@linux.alibaba.com> wrote:
> >
> >> Hi Yue,
> >>
> >> ÔÚ 2022/12/24 17:43, Yue Hu дµÀ:
> >>> From: Yue Hu <huyue2@coolpad.com>
> >>>
> >>> Add compressed fragments support for fsck.erofs.
> >>>
> >>> Signed-off-by: Yue Hu <huyue2@coolpad.com>
> >>> ---
> >>> fsck/main.c | 41 +++++++++++++++++++++++++++++++++++++++--
> >>> lib/zmap.c | 1 +
> >>> 2 files changed, 40 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/fsck/main.c b/fsck/main.c
> >>> index 2a9c501..9babc61 100644
> >>> --- a/fsck/main.c
> >>> +++ b/fsck/main.c
> >>> @@ -421,6 +421,31 @@ static int erofs_verify_inode_data(struct erofs_inode *inode, int outfd)
> >>> if (!(map.m_flags & EROFS_MAP_MAPPED) || !fsckcfg.check_decomp)
> >>> continue;
> >>>
> >>> + if (map.m_flags & EROFS_MAP_FRAGMENT) {
> >>> + struct erofs_inode packed_inode = {
> >>> + .nid = sbi.packed_nid,
> >>> + };
> >>
> >> Sorry for late response.
> >>
> >> a question... why don't we just rely on z_erofs_read_data()?
> >
> > We may fall back to uncompressed mode for packed inode due to 'ENOSPC'.
>
> I think we could just export parts of erofs_pread() to clean up the
> whole erofs_verify_inode_data()...
What's the clean up referring to?
However, i think erofs_verify_inode_data() looks a little duplicate compared to erofs_read_raw_data/z_erofs_read_data().
>
> Thanks,
> Gao Xiang
>
>
next prev parent reply other threads:[~2023-01-04 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 9:43 [RFC PATCH] erofs-utils: fsck: support fragments Yue Hu
2023-01-04 2:48 ` Xiang Gao
2023-01-04 3:24 ` Yue Hu
2023-01-04 3:32 ` Xiang Gao
2023-01-04 7:26 ` Yue Hu [this message]
2023-01-04 7:28 ` Xiang Gao
2023-01-04 7:42 ` Yue Hu
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=20230104152651.000051df.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=huyue2@coolpad.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=zhangwen@coolpad.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