[dm:for-next 26/26] drivers/md/dm-crypt.c:3068:2: error: 't' undeclared; did you mean 'ti'?

[dm:for-next 26/26] drivers/md/dm-crypt.c:3068:2: error: 't' undeclared; did you mean 'ti'?

[kbuild test robot]

[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
head:   08575fd060d7f88f674509461b32d86b272093d9
commit: 08575fd060d7f88f674509461b32d86b272093d9 [26/26] dm crypt: don't decrease device limits
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
        git checkout 08575fd060d7f88f674509461b32d86b272093d9
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   drivers/md/dm-crypt.c: In function 'crypt_io_hints':
>> drivers/md/dm-crypt.c:3068:2: error: 't' undeclared (first use in this function); did you mean 'ti'?
     t->io_min = max_t(unsigned, limits->io_min, cc->sector_size);
     ^
     ti
   drivers/md/dm-crypt.c:3068:2: note: each undeclared identifier is reported only once for each function it appears in

vim +3068 drivers/md/dm-crypt.c

  3051	
  3052	static void crypt_io_hints(struct dm_target *ti, struct queue_limits *limits)
  3053	{
  3054		struct crypt_config *cc = ti->private;
  3055	
  3056		/*
  3057		 * Unfortunate constraint that is required to avoid the potential
  3058		 * for exceeding underlying device's max_segments limits -- due to
  3059		 * crypt_alloc_buffer() possibly allocating pages for the encryption
  3060		 * bio that are not as physically contiguous as the original bio.
  3061		 */
  3062		limits->max_segment_size = PAGE_SIZE;
  3063	
  3064		limits->logical_block_size =
  3065			max_t(unsigned short, limits->logical_block_size, cc->sector_size);
  3066		limits->physical_block_size =
  3067			max_t(unsigned, limits->physical_block_size, cc->sector_size);
> 3068		t->io_min = max_t(unsigned, limits->io_min, cc->sector_size);
  3069	}
  3070	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 64128 bytes --]

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]

Re: [dm:for-next 26/26] drivers/md/dm-crypt.c:3068:2: error: 't' undeclared; did you mean 'ti'?

[Mike Snitzer]

On Fri, Aug 10 2018 at  3:12pm -0400,
kbuild test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
> head:   08575fd060d7f88f674509461b32d86b272093d9
> commit: 08575fd060d7f88f674509461b32d86b272093d9 [26/26] dm crypt: don't decrease device limits
> config: i386-allmodconfig (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
> reproduce:
>         git checkout 08575fd060d7f88f674509461b32d86b272093d9
>         # save the attached .config to linux build tree
>         make ARCH=i386 
> 
> All errors (new ones prefixed by >>):
> 
>    drivers/md/dm-crypt.c: In function 'crypt_io_hints':
> >> drivers/md/dm-crypt.c:3068:2: error: 't' undeclared (first use in this function); did you mean 'ti'?
>      t->io_min = max_t(unsigned, limits->io_min, cc->sector_size);
>      ^
>      ti
>    drivers/md/dm-crypt.c:3068:2: note: each undeclared identifier is reported only once for each function it appears in


Fixed up, needed to be: limits->io_min = max_t(unsigned, limits->io_min, cc->sector_size);

Sorry for the noise...

And thanks,
Mike