From: JeffleXu <jefflexu@linux.alibaba.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, Xiang Gao <xiang@kernel.org>,
linux-kernel@vger.kernel.org,
Gao Xiang <hsiangkao@linux.alibaba.com>
Subject: Re: [xiang:jeffle/fscache 2/19] fs/cachefiles/namei.c:478:17: error: label 'out_unuse' used but not defined
Date: Sat, 2 Apr 2022 13:23:49 +0800 [thread overview]
Message-ID: <75ca360f-48a6-38dc-c0cc-d9b0e0d003ce@linux.alibaba.com> (raw)
In-Reply-To: <202204021359.3SIrp1y5-lkp@intel.com>
On 4/2/22 1:18 PM, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/xiang/linux.git jeffle/fscache
> head: c536a60b958806d427fb66e3f53a1201826fdcf4
> commit: 6e3731398f863eec9b10f9e0cead9f2ec09d8b4d [2/19] cachefiles: notify user daemon with anon_fd when looking up cookie
> config: x86_64-randconfig-a011 (https://download.01.org/0day-ci/archive/20220402/202204021359.3SIrp1y5-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/xiang/linux.git/commit/?id=6e3731398f863eec9b10f9e0cead9f2ec09d8b4d
> git remote add xiang https://git.kernel.org/pub/scm/linux/kernel/git/xiang/linux.git
> git fetch --no-tags xiang jeffle/fscache
> git checkout 6e3731398f863eec9b10f9e0cead9f2ec09d8b4d
> # save the config file to linux build tree
> mkdir build_dir
> make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash fs/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> fs/cachefiles/namei.c: In function 'cachefiles_create_tmpfile':
>>> fs/cachefiles/namei.c:478:17: error: label 'out_unuse' used but not defined
> 478 | goto out_unuse;
> | ^~~~
>
>
This patchset depends on "cachefiles: unmark inode in use in error path"
[1].
[1]
https://github.com/lostjeffle/linux/commit/3c71705e777fa75d37f784640a232db14ce62c31
--
Thanks,
Jeffle
prev parent reply other threads:[~2022-04-02 5:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 5:18 kernel test robot
2022-04-02 5:23 ` JeffleXu [this message]
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=75ca360f-48a6-38dc-c0cc-d9b0e0d003ce@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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
all inboxes | Powered by JetHome®