All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hch-block:integrity-devirtualize 29/30] block/t10-pi.c:335: error: unterminated argument list invoking macro "pr_warn"
Date: Mon, 07 Jun 2021 01:09:00 +0800	[thread overview]
Message-ID: <202106070153.O4e9zb78-lkp@intel.com> (raw)

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

tree:   git://git.infradead.org/users/hch/block.git integrity-devirtualize
head:   984033667ad1babe7a58e171d1bdecf22941244c
commit: 40aefcc7cbe4310ba77510d3c9b808c04a43abbc [29/30] block: split blk_integrity_register
config: i386-randconfig-a013-20210606 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        git remote add hch-block git://git.infradead.org/users/hch/block.git
        git fetch --no-tags hch-block integrity-devirtualize
        git checkout 40aefcc7cbe4310ba77510d3c9b808c04a43abbc
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

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 >>):

   block/t10-pi.c: In function 't10_pi_register':
>> block/t10-pi.c:335: error: unterminated argument list invoking macro "pr_warn"
     335 | MODULE_LICENSE("GPL");
         | 
>> block/t10-pi.c:327:3: error: 'pr_warn' undeclared (first use in this function)
     327 |   pr_warn("blk-integrity: Integrity and hardware inline encryption are not supported together. "
         |   ^~~~~~~
   block/t10-pi.c:327:3: note: each undeclared identifier is reported only once for each function it appears in
>> block/t10-pi.c:327:10: error: expected ';' at end of input
     327 |   pr_warn("blk-integrity: Integrity and hardware inline encryption are not supported together. "
         |          ^
         |          ;
   ......
     335 | MODULE_LICENSE("GPL");
         |           
>> block/t10-pi.c:327:3: error: expected declaration or statement at end of input
     327 |   pr_warn("blk-integrity: Integrity and hardware inline encryption are not supported together. "
         |   ^~~~~~~
>> block/t10-pi.c:327:3: error: expected declaration or statement at end of input


vim +/pr_warn +335 block/t10-pi.c

40aefcc7cbe431 Christoph Hellwig 2021-06-06  278  
40aefcc7cbe431 Christoph Hellwig 2021-06-06  279  /**
40aefcc7cbe431 Christoph Hellwig 2021-06-06  280   * t10_pi_register - Register a gendisk as being T10-PI capable
40aefcc7cbe431 Christoph Hellwig 2021-06-06  281   * @disk:	struct gendisk pointer to make integrity-aware
40aefcc7cbe431 Christoph Hellwig 2021-06-06  282   * @type:	Protetion type
40aefcc7cbe431 Christoph Hellwig 2021-06-06  283   * @flags:	BLK_INTEGRITY_* flags applicatble to this disk
40aefcc7cbe431 Christoph Hellwig 2021-06-06  284   */
40aefcc7cbe431 Christoph Hellwig 2021-06-06  285  void t10_pi_register(struct gendisk *disk, enum t10_dif_type type,
40aefcc7cbe431 Christoph Hellwig 2021-06-06  286  		unsigned int flags)
40aefcc7cbe431 Christoph Hellwig 2021-06-06  287  {
40aefcc7cbe431 Christoph Hellwig 2021-06-06  288  	struct blk_integrity *bi = &disk->queue->integrity;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  289  
40aefcc7cbe431 Christoph Hellwig 2021-06-06  290  	switch (type) {
40aefcc7cbe431 Christoph Hellwig 2021-06-06  291  	case T10_PI_TYPE0_PROTECTION:
40aefcc7cbe431 Christoph Hellwig 2021-06-06  292  		flags &= ~(BLK_INTEGRITY_DEVICE_CAPABLE | BLK_INTEGRITY_APP_TAG);
40aefcc7cbe431 Christoph Hellwig 2021-06-06  293  		break;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  294  	case T10_PI_TYPE2_PROTECTION:
40aefcc7cbe431 Christoph Hellwig 2021-06-06  295  	case T10_PI_TYPE1_PROTECTION:
40aefcc7cbe431 Christoph Hellwig 2021-06-06  296  		if (flags & BLK_INTEGRITY_IP_CHECKSUM)
40aefcc7cbe431 Christoph Hellwig 2021-06-06  297  			bi->profile = &t10_pi_type1_ip;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  298  		else
40aefcc7cbe431 Christoph Hellwig 2021-06-06  299  			bi->profile = &t10_pi_type1_crc;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  300  		break;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  301  	case T10_PI_TYPE3_PROTECTION:
40aefcc7cbe431 Christoph Hellwig 2021-06-06  302  		if (flags & BLK_INTEGRITY_IP_CHECKSUM)
40aefcc7cbe431 Christoph Hellwig 2021-06-06  303  			bi->profile = &t10_pi_type3_ip;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  304  		else
40aefcc7cbe431 Christoph Hellwig 2021-06-06  305  			bi->profile = &t10_pi_type3_crc;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  306  		break;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  307  	default:
40aefcc7cbe431 Christoph Hellwig 2021-06-06  308  		WARN_ON_ONCE(1);
40aefcc7cbe431 Christoph Hellwig 2021-06-06  309  		return;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  310  	}
40aefcc7cbe431 Christoph Hellwig 2021-06-06  311  
40aefcc7cbe431 Christoph Hellwig 2021-06-06  312  	bi->tuple_size = sizeof(struct t10_pi_tuple);
40aefcc7cbe431 Christoph Hellwig 2021-06-06  313  	bi->interval_exp = ilog2(queue_logical_block_size(disk->queue));
40aefcc7cbe431 Christoph Hellwig 2021-06-06  314  	bi->flags = flags | BLK_INTEGRITY_VERIFY | BLK_INTEGRITY_GENERATE;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  315  
40aefcc7cbe431 Christoph Hellwig 2021-06-06  316  	if (!(flags & BLK_INTEGRITY_APP_TAG))
40aefcc7cbe431 Christoph Hellwig 2021-06-06  317  		bi->tag_size = 0;
40aefcc7cbe431 Christoph Hellwig 2021-06-06  318  	else if (type == T10_PI_TYPE3_PROTECTION)
40aefcc7cbe431 Christoph Hellwig 2021-06-06  319  		bi->tag_size = sizeof(u16) + sizeof(u32);
40aefcc7cbe431 Christoph Hellwig 2021-06-06  320  	else
40aefcc7cbe431 Christoph Hellwig 2021-06-06  321  		bi->tag_size = sizeof(u16);
40aefcc7cbe431 Christoph Hellwig 2021-06-06  322  
40aefcc7cbe431 Christoph Hellwig 2021-06-06  323  	blk_queue_flag_set(QUEUE_FLAG_STABLE_WRITES, disk->queue);
40aefcc7cbe431 Christoph Hellwig 2021-06-06  324  
40aefcc7cbe431 Christoph Hellwig 2021-06-06  325  #ifdef CONFIG_BLK_INLINE_ENCRYPTION
40aefcc7cbe431 Christoph Hellwig 2021-06-06  326  	if (disk->queue->ksm) {
40aefcc7cbe431 Christoph Hellwig 2021-06-06 @327  		pr_warn("blk-integrity: Integrity and hardware inline encryption are not supported together. "
40aefcc7cbe431 Christoph Hellwig 2021-06-06  328  		pr_warn("Disabling hardware inline encryption.\n");
40aefcc7cbe431 Christoph Hellwig 2021-06-06  329  		blk_ksm_unregister(disk->queue);
40aefcc7cbe431 Christoph Hellwig 2021-06-06  330  	}
40aefcc7cbe431 Christoph Hellwig 2021-06-06  331  #endif
40aefcc7cbe431 Christoph Hellwig 2021-06-06  332  }
40aefcc7cbe431 Christoph Hellwig 2021-06-06  333  EXPORT_SYMBOL(t10_pi_register);
a754bd5f187497 Herbert Xu        2019-12-23  334  
a754bd5f187497 Herbert Xu        2019-12-23 @335  MODULE_LICENSE("GPL");

:::::: The code at line 335 was first introduced by commit
:::::: a754bd5f1874978f55814b4498f66e4a0fd5b256 block: Allow t10-pi to be modular

:::::: TO: Herbert Xu <herbert@gondor.apana.org.au>
:::::: CC: Jens Axboe <axboe@kernel.dk>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

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

                 reply	other threads:[~2021-06-06 17:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202106070153.O4e9zb78-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.