From: Gao Xiang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: Yiyang Wu <toolmanp@tlmp.cc>
Cc: linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 2/2] erofs: refactor read_inode calling convention
Date: Tue, 3 Sep 2024 10:37:55 +0800 [thread overview]
Message-ID: <ZtZ2gygmwGSAuPgS@debian> (raw)
In-Reply-To: <94737216-af40-44b0-ab3e-e5bfdbffab5f@linux.alibaba.com>
On Mon, Sep 02, 2024 at 05:54:22PM +0800, Gao Xiang wrote:
>
>
> On 2024/9/2 17:34, Yiyang Wu wrote:
> > Refactor out the iop binding behavior out of the erofs_fill_symlink
> > and move erofs_buf into the erofs_read_inode, so that erofs_fill_inode
> > can only deal with inode operation bindings and can be decoupled from
> > metabuf operations. This results in better calling conventions.
> >
> > Note that after this patch, we do not need erofs_buf and ofs as
> > parameters any more when calling erofs_read_inode as
> > all the data operations are now included in itself.
> >
> > Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
> > Link: https://lore.kernel.org/all/20240425222847.GN2118490@ZenIV/
> > Signed-off-by: Yiyang Wu <toolmanp@tlmp.cc>
>
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
>
> Thanks,
> Gao Xiang
Applied with the following minor cleanups:
diff --git a/fs/erofs/inode.c b/fs/erofs/inode.c
index 726a93a0413c..31d811b50291 100644
--- a/fs/erofs/inode.c
+++ b/fs/erofs/inode.c
@@ -16,9 +16,8 @@ static int erofs_fill_symlink(struct inode *inode, void *kaddr,
/* if it cannot be handled with fast symlink scheme */
if (vi->datalayout != EROFS_INODE_FLAT_INLINE ||
- inode->i_size >= bsz || inode->i_size < 0) {
+ inode->i_size >= bsz || inode->i_size < 0)
return 0;
- }
m_pofs += vi->xattr_isize;
/* inline symlink data shouldn't cross block boundary */
@@ -204,7 +203,7 @@ static int erofs_read_inode(struct inode *inode)
static int erofs_fill_inode(struct inode *inode)
{
struct erofs_inode *vi = EROFS_I(inode);
- int err = 0;
+ int err;
trace_erofs_fill_inode(inode);
WARNING: multiple messages have this Message-ID (diff)
From: Gao Xiang <xiang@kernel.org>
To: Yiyang Wu <toolmanp@tlmp.cc>
Cc: linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 2/2] erofs: refactor read_inode calling convention
Date: Tue, 3 Sep 2024 10:37:55 +0800 [thread overview]
Message-ID: <ZtZ2gygmwGSAuPgS@debian> (raw)
In-Reply-To: <94737216-af40-44b0-ab3e-e5bfdbffab5f@linux.alibaba.com>
On Mon, Sep 02, 2024 at 05:54:22PM +0800, Gao Xiang wrote:
>
>
> On 2024/9/2 17:34, Yiyang Wu wrote:
> > Refactor out the iop binding behavior out of the erofs_fill_symlink
> > and move erofs_buf into the erofs_read_inode, so that erofs_fill_inode
> > can only deal with inode operation bindings and can be decoupled from
> > metabuf operations. This results in better calling conventions.
> >
> > Note that after this patch, we do not need erofs_buf and ofs as
> > parameters any more when calling erofs_read_inode as
> > all the data operations are now included in itself.
> >
> > Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
> > Link: https://lore.kernel.org/all/20240425222847.GN2118490@ZenIV/
> > Signed-off-by: Yiyang Wu <toolmanp@tlmp.cc>
>
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
>
> Thanks,
> Gao Xiang
Applied with the following minor cleanups:
diff --git a/fs/erofs/inode.c b/fs/erofs/inode.c
index 726a93a0413c..31d811b50291 100644
--- a/fs/erofs/inode.c
+++ b/fs/erofs/inode.c
@@ -16,9 +16,8 @@ static int erofs_fill_symlink(struct inode *inode, void *kaddr,
/* if it cannot be handled with fast symlink scheme */
if (vi->datalayout != EROFS_INODE_FLAT_INLINE ||
- inode->i_size >= bsz || inode->i_size < 0) {
+ inode->i_size >= bsz || inode->i_size < 0)
return 0;
- }
m_pofs += vi->xattr_isize;
/* inline symlink data shouldn't cross block boundary */
@@ -204,7 +203,7 @@ static int erofs_read_inode(struct inode *inode)
static int erofs_fill_inode(struct inode *inode)
{
struct erofs_inode *vi = EROFS_I(inode);
- int err = 0;
+ int err;
trace_erofs_fill_inode(inode);
next prev parent reply other threads:[~2024-09-03 2:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 8:31 [PATCH V4 0/2] erofs: refactor fast_symlink and read_inode Yiyang Wu via Linux-erofs
2024-09-02 8:31 ` Yiyang Wu
2024-09-02 8:31 ` [PATCH V4 1/2] erofs: use kmemdup_nul in erofs_fill_symlink Yiyang Wu via Linux-erofs
2024-09-02 8:31 ` Yiyang Wu
2024-09-02 8:52 ` Gao Xiang
2024-09-02 9:04 ` Gao Xiang via Linux-erofs
2024-09-02 9:04 ` Gao Xiang
2024-09-09 3:37 ` Chao Yu via Linux-erofs
2024-09-09 3:37 ` Chao Yu
2024-09-02 8:31 ` [PATCH V4 2/2] erofs: refactor read_inode calling convention Yiyang Wu via Linux-erofs
2024-09-02 8:31 ` Yiyang Wu
2024-09-02 8:53 ` Gao Xiang
2024-09-02 9:34 ` Yiyang Wu via Linux-erofs
2024-09-02 9:34 ` Yiyang Wu
2024-09-02 9:54 ` Gao Xiang
2024-09-03 2:37 ` Gao Xiang via Linux-erofs [this message]
2024-09-03 2:37 ` Gao Xiang
2024-09-09 3:41 ` Chao Yu via Linux-erofs
2024-09-09 3:41 ` Chao Yu
2024-09-02 9:36 ` Yiyang Wu via Linux-erofs
2024-09-02 9:36 ` Yiyang Wu
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=ZtZ2gygmwGSAuPgS@debian \
--to=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=toolmanp@tlmp.cc \
--cc=xiang@kernel.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.