From: Jonathan Calmels <jcalmels@nvidia.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: linux-erofs@lists.ozlabs.org, xiang@kernel.org
Subject: Re: [PATCH] erofs-utils: lib: relax erofs_write_device_table() device table check
Date: Thu, 12 Feb 2026 09:00:18 -0800 [thread overview]
Message-ID: <aY4EXe96VKXsCb8R@nvidia.com> (raw)
In-Reply-To: <a4712179-0675-464d-8991-301e260f15bb@linux.alibaba.com>
On Thu, Feb 12, 2026 at 05:13:31PM +0800, Gao Xiang wrote:
> External email: Use caution opening links or attachments
>
>
> Hi Jonathan,
>
> On 2026/2/12 08:13, Jonathan Calmels wrote:
> > Avoid returning an error in erofs_write_device_table()
> > if a new device slot table hasn't been allocated.
> > Rationale is to allow erofs_importer_flush_all() to succeed when
> > dealing with images with pre-existing device slots.
> >
> > Signed-off-by: Jonathan Calmels <jcalmels@nvidia.com>
>
> Thanks for the patch, could you elaborate how to use this?
>
> A detailed command line usage would be better.
>
> (Also honestly I will try to release erofs-utils 1.9 in
> a few days for the upcoming ubuntu LTS, so I have to
> finish erofs fsmerge feature for compression layout
> after the version is released...)
>
> Thanks,
> Gao Xiang
I'm relying on the library not the CLI, I think the equivalent would be:
mkfs.erofs -Efragments,noinline_data,ztailpacking a.erofs a/
mkfs.erofs -Efragments,noinline_data,ztailpacking b.erofs b/
mkfs.erofs merged.erofs a.erofs b.erofs
mkfs.erofs --incremental=data merged.erofs c/
It does seem to work as expected after the patch, but let me know if I
missed anything.
Thanks
> > ---
> > lib/super.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/super.c b/lib/super.c
> > index a203f96..d38396f 100644
> > --- a/lib/super.c
> > +++ b/lib/super.c
> > @@ -392,7 +392,7 @@ int erofs_write_device_table(struct erofs_sb_info *sbi)
> > if (!sbi->extra_devices)
> > goto out;
> > if (!bh)
> > - return -EINVAL;
> > + goto out;
> >
> > pos = erofs_btell(bh, false);
> > if (pos == EROFS_NULL_ADDR) {
>
next prev parent reply other threads:[~2026-02-12 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 0:13 [PATCH] erofs-utils: lib: relax erofs_write_device_table() device table check Jonathan Calmels
2026-02-12 9:13 ` Gao Xiang
2026-02-12 17:00 ` Jonathan Calmels [this message]
2026-02-12 17:21 ` Gao Xiang
2026-02-12 18:33 ` [PATCH v2] " Jonathan Calmels
2026-02-13 1:13 ` [PATCH v3] " Jonathan Calmels
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=aY4EXe96VKXsCb8R@nvidia.com \
--to=jcalmels@nvidia.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--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