From: Greg KH <greg@kroah.com>
To: driz2t <driz2t@qq.com>
Cc: stable <stable@vger.kernel.org>, xiang <xiang@kernel.org>,
chao <chao@kernel.org>, jefflexu <jefflexu@linux.alibaba.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
syzbot+016d861797fd718491a8
<syzbot+016d861797fd718491a8@syzkaller.appspotmail.com>
Subject: Re: [PATCH 6.1.y] erofs: get rid of z_erofs_fill_inode()
Date: Wed, 8 Apr 2026 15:25:06 +0200 [thread overview]
Message-ID: <2026040834-mower-award-5880@gregkh> (raw)
In-Reply-To: <tencent_4CAC91CB31E29B2052C48E4A15D379060905@qq.com>
On Wed, Mar 25, 2026 at 07:11:22PM +0800, driz2t wrote:
> [ Upstream commit 4fdadd5b0f0c723c812842454f8cca1619f2e731 ]
>
> Prior to big pclusters, non-compact compression indexes could have
> empty headers.
>
> Avoid the legacy path since it can be handled properly as a specific
> compression header with z_erofs_fill_inode_lazy() too.
>
> Tested with existing erofs-utils versions.
>
> Link: https://lore.kernel.org/r/20230413092241.73829-1-hsiangkao@linux.alibaba.com
> Link: https://syzkaller.appspot.com/bug?extid=016d861797fd718491a8
> Reported-by: syzbot+016d861797fd718491a8@syzkaller.appspotmail.com
> Tested-by: syzbot+016d861797fd718491a8@syzkaller.appspotmail.com
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> Signed-off-by: Changjian Liu <driz2t@qq.com>
> ---
> fs/erofs/inode.c | 12 ++++++++----
> fs/erofs/internal.h | 2 --
> fs/erofs/zmap.c | 18 ------------------
> 3 files changed, 8 insertions(+), 24 deletions(-)
I see multiple versions from you sent, yet no clue as to which one is
correct, so I'm dropping them all. Please fix up and send a new one
properly versioned.
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-08 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 11:11 [PATCH 6.1.y] erofs: get rid of z_erofs_fill_inode() driz2t
2026-04-08 13:25 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-25 6:57 driz2t
2026-03-25 7:15 ` Gao Xiang
2026-03-24 12:48 driz2t
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=2026040834-mower-award-5880@gregkh \
--to=greg@kroah.com \
--cc=chao@kernel.org \
--cc=driz2t@qq.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+016d861797fd718491a8@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox