From: Hongbo Li <lihongbo22@huawei.com>
To: Dan Carpenter <dan.carpenter@linaro.org>,
<oe-kbuild@lists.linux.dev>, <richard@nod.at>,
<anton.ivanov@cambridgegreys.com>, <johannes@sipsolutions.net>
Cc: <lkp@intel.com>, <oe-kbuild-all@lists.linux.dev>,
<linux-um@lists.infradead.org>, <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] hostfs: convert hostfs to use the new mount api
Date: Fri, 17 May 2024 19:21:09 +0800 [thread overview]
Message-ID: <74576c52-5eca-4961-ada4-a9ec99fb16cf@huawei.com> (raw)
In-Reply-To: <d845ba1a-2b10-4d83-a687-56406ce657c9@suswa.mountain>
Thanks for your attention, I have solved the warnings in the following
patch (the similar title: hostfs: convert hostfs to use the new mount API):
https://lore.kernel.org/all/20240515025536.3667017-1-lihongbo22@huawei.com/
or
https://patchwork.ozlabs.org/project/linux-um/patch/20240515025536.3667017-1-lihongbo22@huawei.com/
It was strange that the kernel test robot did not send the results on
the new patch.
Thanks,
Hongbo
On 2024/5/17 19:01, Dan Carpenter wrote:
> Hi Hongbo,
>
> kernel test robot noticed the following build warnings:
>
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Hongbo-Li/hostfs-convert-hostfs-to-use-the-new-mount-api/20240513-204233
> base: git://git.kernel.org/pub/scm/linux/kernel/git/uml/linux next
> patch link: https://lore.kernel.org/r/20240513124141.3788846-1-lihongbo22%40huawei.com
> patch subject: [PATCH] hostfs: convert hostfs to use the new mount api
> config: um-randconfig-r081-20240517 (https://download.01.org/0day-ci/archive/20240517/202405171154.21q42SWy-lkp@intel.com/config)
> compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project d3455f4ddd16811401fa153298fadd2f59f6914e)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> | Closes: https://lore.kernel.org/r/202405171154.21q42SWy-lkp@intel.com/
>
> smatch warnings:
> fs/hostfs/hostfs_kern.c:960 hostfs_fill_super() error: uninitialized symbol 'host_root'.
>
> vim +/host_root +960 fs/hostfs/hostfs_kern.c
>
> 2c2593890079e8 Hongbo Li 2024-05-13 938 static int hostfs_fill_super(struct super_block *sb, struct fs_context *fc)
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 939 {
> 2c2593890079e8 Hongbo Li 2024-05-13 940 struct hostfs_fs_info *fsi = sb->s_fs_info;
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 941 struct inode *root_inode;
> 2c2593890079e8 Hongbo Li 2024-05-13 942 char *host_root;
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 943 int err;
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 944
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 945 sb->s_blocksize = 1024;
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 946 sb->s_blocksize_bits = 10;
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 947 sb->s_magic = HOSTFS_SUPER_MAGIC;
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 948 sb->s_op = &hostfs_sbops;
> b26d4cd385fc51 Al Viro 2013-10-25 949 sb->s_d_op = &simple_dentry_operations;
> 752fa51e4c5182 Wolfgang Illmeyer 2009-06-30 950 sb->s_maxbytes = MAX_LFS_FILESIZE;
> ce72750f04d68a Sjoerd Simons 2021-11-05 951 err = super_setup_bdi(sb);
> ce72750f04d68a Sjoerd Simons 2021-11-05 952 if (err)
> 74ce793bcbde5c Mickaël Salaün 2023-06-12 953 return err;
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 954
> b58c4e96192ee7 Andy Shevchenko 2020-03-20 955 /* NULL is printed as '(null)' by printf(): avoid that. */
> 2c2593890079e8 Hongbo Li 2024-05-13 956 if (fc->source == NULL)
> 2c2593890079e8 Hongbo Li 2024-05-13 957 host_root = "";
>
> Uninitialized on else path
>
> ^1da177e4c3f41 Linus Torvalds 2005-04-16 958
> 2c2593890079e8 Hongbo Li 2024-05-13 959 fsi->host_root_path =
> 2c2593890079e8 Hongbo Li 2024-05-13 @960 kasprintf(GFP_KERNEL, "%s/%s", root_ino, host_root);
> ^^^^^^^^^
>
>
> 2c2593890079e8 Hongbo Li 2024-05-13 961 if (fsi->host_root_path == NULL)
> 74ce793bcbde5c Mickaël Salaün 2023-06-12 962 return -ENOMEM;
>
next prev parent reply other threads:[~2024-05-17 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 12:41 [PATCH] hostfs: convert hostfs to use the new mount api Hongbo Li
2024-05-13 15:37 ` kernel test robot
2024-05-17 11:01 ` Dan Carpenter
2024-05-17 11:21 ` Hongbo Li [this message]
2024-05-23 10:43 ` Dan Carpenter
2024-05-30 11:47 ` Hongbo Li
-- strict thread matches above, loose matches on Subject: below --
2024-05-15 2:55 [PATCH] hostfs: convert hostfs to use the new mount API Hongbo Li
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=74576c52-5eca-4961-ada4-a9ec99fb16cf@huawei.com \
--to=lihongbo22@huawei.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=dan.carpenter@linaro.org \
--cc=johannes@sipsolutions.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--cc=richard@nod.at \
/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