Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Jingbo Xu <jefflexu@linux.alibaba.com>,
	xiang@kernel.org, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH 05/13] erofs-utils: lib: keep self maintained devname
Date: Mon, 14 Aug 2023 14:55:01 +0800	[thread overview]
Message-ID: <478771d2-d73e-0bf7-0e8e-179c8f8a55c9@linux.alibaba.com> (raw)
In-Reply-To: <b141d8aa-c8a4-63db-3400-901492c92dd0@linux.alibaba.com>



On 2023/8/14 14:43, Gao Xiang wrote:
> 
> 
> On 2023/8/14 11:42, Jingbo Xu wrote:
>> Keep self allocated and maintained devname in erofs_sb_info.
>>
>> Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>
>> ---

...


>> @@ -95,7 +97,11 @@ int dev_open(struct erofs_sb_info *sbi, const char *dev)
>>           return -EINVAL;
>>       }
>> -    sbi->devname = dev;
>> +    sbi->devname = strdup(dev);
> 
> Could we move sbi->devname assignment to the beginning of the function?
> e.g.
> 
>      ..
>          sbi->devname = strdup(dev);
>          if (!sbi->devname)
>                  return -ENOMEM;
> 
>          fd = open(dev, O_RDWR | O_CREAT | O_BINARY, 0644);
>      ...
> 
> 
>> +    if (!sbi->devname) {
>> +        close(fd);
>> +        return -ENOMEM;
>> +    }

After a second thought, since there are already several `close(fd);` in the
error paths and they are unavoidable.  So it looks good to me now:

Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>

Thanks,
Gao Xiang

  reply	other threads:[~2023-08-14  6:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14  3:42 [PATCH 00/13] erofs-utils: mkfs: introduce rebuild mode Jingbo Xu
2023-08-14  3:42 ` [PATCH 01/13] erofs-utils: fix overriding of i_rdev for special device Jingbo Xu
2023-08-14  5:42   ` Gao Xiang
2023-08-14  3:42 ` [PATCH 02/13] erofs-utils: lib: add list_splice_tail() helper Jingbo Xu
2023-08-14  5:50   ` Gao Xiang
2023-08-14  3:42 ` [PATCH 03/13] erofs-utils: lib: read i_ino in erofs_read_inode_from_disk() Jingbo Xu
2023-08-14  6:03   ` Gao Xiang
2023-08-14  3:42 ` [PATCH 04/13] erofs-utils: lib: fix erofs_init_devices() in multidev mode Jingbo Xu
2023-08-14  6:39   ` Gao Xiang
2023-08-14  3:42 ` [PATCH 05/13] erofs-utils: lib: keep self maintained devname Jingbo Xu
2023-08-14  6:43   ` Gao Xiang
2023-08-14  6:55     ` Gao Xiang [this message]
2023-08-14  3:42 ` [PATCH 06/13] erofs-utils: lib: make erofs_get_unhashed_chunk() global Jingbo Xu
2023-08-14  3:42 ` [PATCH 07/13] erofs-utils: lib: add erofs_read_xattrs_from_disk() helper Jingbo Xu
2023-08-14  6:46   ` Gao Xiang
2023-08-14  6:59     ` Jingbo Xu
2023-08-14  3:42 ` [PATCH 08/13] erofs-utils: lib: add erofs_inode_tag_opaque() helper Jingbo Xu
2023-08-14  7:05   ` Gao Xiang
2023-08-14  3:42 ` [PATCH 09/13] erofs-utils: lib: add erofs_insert_ihash() helper Jingbo Xu
2023-08-14  3:42 ` [PATCH 10/13] erofs-utils: lib: add erofs_rebuild_dump_tree() helper Jingbo Xu
2023-08-14  3:42 ` [PATCH 11/13] erofs-utils: lib: add erofs_rebuild_get_dentry() helper Jingbo Xu
2023-08-14  3:42 ` [PATCH 12/13] erofs-utils: lib: add erofs_rebuild_load_tree() helper Jingbo Xu
2023-08-14  3:42 ` [PATCH 13/13] erofs-utils: mkfs: introduce rebuild mode Jingbo Xu

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=478771d2-d73e-0bf7-0e8e-179c8f8a55c9@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=jefflexu@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