Re: [device-mapper-dm:dm-5.19 132/132] drivers/md/dm.c:1542:18: error: 'result' undeclared

[Mike Snitzer <snitzer@redhat.com>]

On Wed, Mar 23 2022 at  6:57P -0400,
kernel test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git dm-5.19
> head:   7f8ac95a6464b895e3d2b6175f7ee64a4c10fcfe
> commit: 7f8ac95a6464b895e3d2b6175f7ee64a4c10fcfe [132/132] dm: push error handling down to __split_and_process_bio
> config: s390-buildonly-randconfig-r005-20220323 (https://download.01.org/0day-ci/archive/20220324/202203240638.crXQjFY5-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 11.2.0
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?id=7f8ac95a6464b895e3d2b6175f7ee64a4c10fcfe
>         git remote add device-mapper-dm https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git
>         git fetch --no-tags device-mapper-dm dm-5.19
>         git checkout 7f8ac95a6464b895e3d2b6175f7ee64a4c10fcfe
>         # save the config file to linux build tree
>         mkdir build_dir
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=s390 SHELL=/bin/bash drivers/md/
> 
> 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 >>):
> 
>    drivers/md/dm.c: In function '__process_abnormal_io':
> >> drivers/md/dm.c:1542:18: error: 'result' undeclared (first use in this function)
>     1542 |                 *result = BLK_STS_NOTSUPP;
>          |                  ^~~~~~
>    drivers/md/dm.c:1542:18: note: each undeclared identifier is reported only once for each function it appears in
> 

Yeah, I pushed this too soon, fixed now.

But why are you even testing this branch? I didn't include dm-5.19 in
linux-next yet.

Given that it seems strange for the bot to just pick up some branch,
and then spam LKML, dm-devel, etc like it found a meaningful problem.

Mike