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 30/30] fs/pstore/../../block/blk.h:143:34: error: 'T10_PI_TYPE1_PROTECTION' undeclared
Date: Mon, 07 Jun 2021 01:07:11 +0800	[thread overview]
Message-ID: <202106070104.yyMMPKXl-lkp@intel.com> (raw)

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

tree:   git://git.infradead.org/users/hch/block.git integrity-devirtualize
head:   984033667ad1babe7a58e171d1bdecf22941244c
commit: 984033667ad1babe7a58e171d1bdecf22941244c [30/30] block: devirtualize the integrity processing
config: m68k-randconfig-r023-20210606 (attached as .config)
compiler: m68k-linux-gcc (GCC) 9.3.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
        git remote add hch-block git://git.infradead.org/users/hch/block.git
        git fetch --no-tags hch-block integrity-devirtualize
        git checkout 984033667ad1babe7a58e171d1bdecf22941244c
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=m68k 

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

   In file included from fs/pstore/blk.c:11:
   fs/pstore/../../block/blk.h: In function 't10_pi_need_remap':
>> fs/pstore/../../block/blk.h:143:34: error: 'T10_PI_TYPE1_PROTECTION' undeclared (first use in this function)
     143 |  return rq->q->integrity.type == T10_PI_TYPE1_PROTECTION ||
         |                                  ^~~~~~~~~~~~~~~~~~~~~~~
   fs/pstore/../../block/blk.h:143:34: note: each undeclared identifier is reported only once for each function it appears in
>> fs/pstore/../../block/blk.h:144:28: error: 'T10_PI_TYPE2_PROTECTION' undeclared (first use in this function)
     144 |   rq->q->integrity.type == T10_PI_TYPE2_PROTECTION;
         |                            ^~~~~~~~~~~~~~~~~~~~~~~


vim +/T10_PI_TYPE1_PROTECTION +143 fs/pstore/../../block/blk.h

   137	
   138	static inline bool t10_pi_need_remap(struct request *rq)
   139	{
   140		if (!blk_integrity_rq(rq))
   141			return false;
   142		/* Type 3 does not have a reference tag so no remapping is required. */
 > 143		return rq->q->integrity.type == T10_PI_TYPE1_PROTECTION ||
 > 144			rq->q->integrity.type == T10_PI_TYPE2_PROTECTION;
   145	}
   146	#else /* CONFIG_BLK_DEV_INTEGRITY */
   147	static inline bool blk_integrity_merge_rq(struct request_queue *rq,
   148			struct request *r1, struct request *r2)
   149	{
   150		return true;
   151	}
   152	static inline bool blk_integrity_merge_bio(struct request_queue *rq,
   153			struct request *r, struct bio *b)
   154	{
   155		return true;
   156	}
   157	static inline bool integrity_req_gap_back_merge(struct request *req,
   158			struct bio *next)
   159	{
   160		return false;
   161	}
   162	static inline bool integrity_req_gap_front_merge(struct request *req,
   163			struct bio *bio)
   164	{
   165		return false;
   166	}
   167	

---
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: 29220 bytes --]

                 reply	other threads:[~2021-06-06 17:07 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=202106070104.yyMMPKXl-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.