From: kernel test robot <[email protected]>
To: Kanchan Joshi <[email protected]>,
[email protected], [email protected], [email protected],
[email protected], [email protected]
Cc: [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], Kanchan Joshi <[email protected]>
Subject: Re: [PATCH 10/10] nvme: add separate handling for user integrity buffer
Date: Fri, 26 Apr 2024 18:57:50 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Hi Kanchan,
kernel test robot noticed the following build errors:
[auto build test ERROR on 24c3fc5c75c5b9d471783b4a4958748243828613]
url: https://github.com/intel-lab-lkp/linux/commits/Kanchan-Joshi/block-set-bip_vcnt-correctly/20240426-024916
base: 24c3fc5c75c5b9d471783b4a4958748243828613
patch link: https://lore.kernel.org/r/20240425183943.6319-11-joshi.k%40samsung.com
patch subject: [PATCH 10/10] nvme: add separate handling for user integrity buffer
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20240426/[email protected]/config)
compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project e6c3289804a67ea0bb6a86fadbe454dd93b8d855)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240426/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
>> drivers/nvme/host/core.c:1014:31: error: member reference base type 'void' is not a structure or union
1014 | if (bio_integrity(req->bio)->bip_flags &
| ~~~~~~~~~~~~~~~~~~~~~~~^ ~~~~~~~~~
1 error generated.
vim +/void +1014 drivers/nvme/host/core.c
971
972 static inline blk_status_t nvme_setup_rw(struct nvme_ns *ns,
973 struct request *req, struct nvme_command *cmnd,
974 enum nvme_opcode op)
975 {
976 u16 control = 0;
977 u32 dsmgmt = 0;
978
979 if (req->cmd_flags & REQ_FUA)
980 control |= NVME_RW_FUA;
981 if (req->cmd_flags & (REQ_FAILFAST_DEV | REQ_RAHEAD))
982 control |= NVME_RW_LR;
983
984 if (req->cmd_flags & REQ_RAHEAD)
985 dsmgmt |= NVME_RW_DSM_FREQ_PREFETCH;
986
987 cmnd->rw.opcode = op;
988 cmnd->rw.flags = 0;
989 cmnd->rw.nsid = cpu_to_le32(ns->head->ns_id);
990 cmnd->rw.cdw2 = 0;
991 cmnd->rw.cdw3 = 0;
992 cmnd->rw.metadata = 0;
993 cmnd->rw.slba =
994 cpu_to_le64(nvme_sect_to_lba(ns->head, blk_rq_pos(req)));
995 cmnd->rw.length =
996 cpu_to_le16((blk_rq_bytes(req) >> ns->head->lba_shift) - 1);
997 cmnd->rw.reftag = 0;
998 cmnd->rw.apptag = 0;
999 cmnd->rw.appmask = 0;
1000
1001 if (ns->head->ms) {
1002 /*
1003 * If formated with metadata, the block layer always provides a
1004 * metadata buffer if CONFIG_BLK_DEV_INTEGRITY is enabled. Else
1005 * we enable the PRACT bit for protection information or set the
1006 * namespace capacity to zero to prevent any I/O.
1007 */
1008 if (!blk_integrity_rq(req)) {
1009 if (WARN_ON_ONCE(!nvme_ns_has_pi(ns->head)))
1010 return BLK_STS_NOTSUPP;
1011 control |= NVME_RW_PRINFO_PRACT;
1012 } else {
1013 /* process user-created integrity */
> 1014 if (bio_integrity(req->bio)->bip_flags &
1015 BIP_INTEGRITY_USER) {
1016 nvme_setup_user_integrity(ns, req, cmnd,
1017 &control);
1018 goto out;
1019 }
1020 }
1021
1022 switch (ns->head->pi_type) {
1023 case NVME_NS_DPS_PI_TYPE3:
1024 control |= NVME_RW_PRINFO_PRCHK_GUARD;
1025 break;
1026 case NVME_NS_DPS_PI_TYPE1:
1027 case NVME_NS_DPS_PI_TYPE2:
1028 control |= NVME_RW_PRINFO_PRCHK_GUARD |
1029 NVME_RW_PRINFO_PRCHK_REF;
1030 if (op == nvme_cmd_zone_append)
1031 control |= NVME_RW_APPEND_PIREMAP;
1032 nvme_set_ref_tag(ns, cmnd, req);
1033 break;
1034 }
1035 }
1036 out:
1037 cmnd->rw.control = cpu_to_le16(control);
1038 cmnd->rw.dsmgmt = cpu_to_le32(dsmgmt);
1039 return 0;
1040 }
1041
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-04-26 10:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240425184649epcas5p42f6ddbfb1c579f043a919973c70ebd03@epcas5p4.samsung.com>
2024-04-25 18:39 ` [PATCH 00/10] Read/Write with meta/integrity Kanchan Joshi
[not found] ` <CGME20240425184651epcas5p3404f2390d6cf05148eb96e1af093e7bc@epcas5p3.samsung.com>
2024-04-25 18:39 ` [PATCH 01/10] block: set bip_vcnt correctly Kanchan Joshi
2024-04-27 7:02 ` Christoph Hellwig
2024-04-27 14:16 ` Keith Busch
2024-04-29 10:59 ` Kanchan Joshi
2024-05-01 7:45 ` Christoph Hellwig
2024-05-01 8:03 ` Keith Busch
[not found] ` <CGME20240425184653epcas5p28de1473090e0141ae74f8b0a6eb921a7@epcas5p2.samsung.com>
2024-04-25 18:39 ` [PATCH 02/10] block: copy bip_max_vcnt vecs instead of bip_vcnt during clone Kanchan Joshi
2024-04-27 7:03 ` Christoph Hellwig
2024-04-29 11:28 ` Kanchan Joshi
2024-04-29 12:04 ` Keith Busch
2024-04-29 17:07 ` Christoph Hellwig
2024-04-30 8:25 ` Keith Busch
2024-05-01 7:46 ` Christoph Hellwig
2024-05-01 7:50 ` Christoph Hellwig
[not found] ` <CGME20240425184656epcas5p42228cdef753cf20a266d12de5bc130f0@epcas5p4.samsung.com>
2024-04-25 18:39 ` [PATCH 03/10] block: copy result back to user meta buffer correctly in case of split Kanchan Joshi
2024-04-27 7:04 ` Christoph Hellwig
[not found] ` <CGME20240425184658epcas5p2adb6bf01a5c56ffaac3a55ab57afaf8e@epcas5p2.samsung.com>
2024-04-25 18:39 ` [PATCH 04/10] block: avoid unpinning/freeing the bio_vec incase of cloned bio Kanchan Joshi
2024-04-27 7:05 ` Christoph Hellwig
2024-04-29 11:40 ` Kanchan Joshi
2024-04-29 17:09 ` Christoph Hellwig
2024-05-01 13:02 ` Kanchan Joshi
2024-05-02 7:12 ` Christoph Hellwig
2024-05-03 12:01 ` Kanchan Joshi
[not found] ` <CGME20240425184700epcas5p1687590f7e4a3f3c3620ac27af514f0ca@epcas5p1.samsung.com>
2024-04-25 18:39 ` [PATCH 05/10] block, nvme: modify rq_integrity_vec function Kanchan Joshi
2024-04-27 7:18 ` Christoph Hellwig
2024-04-29 11:34 ` Kanchan Joshi
2024-04-29 17:11 ` Christoph Hellwig
[not found] ` <CGME20240425184702epcas5p1ccb0df41b07845bc252d69007558e3fa@epcas5p1.samsung.com>
2024-04-25 18:39 ` [PATCH 06/10] block: modify bio_integrity_map_user argument Kanchan Joshi
2024-04-27 7:19 ` Christoph Hellwig
[not found] ` <CGME20240425184704epcas5p3b9eb6cce9c9658eb1d0d32937e778a5d@epcas5p3.samsung.com>
2024-04-25 18:39 ` [PATCH 07/10] block: define meta io descriptor Kanchan Joshi
[not found] ` <CGME20240425184706epcas5p1d75c19d1d1458c52fc4009f150c7dc7d@epcas5p1.samsung.com>
2024-04-25 18:39 ` [PATCH 08/10] io_uring/rw: add support to send meta along with read/write Kanchan Joshi
2024-04-26 14:25 ` Jens Axboe
2024-04-29 20:11 ` Kanchan Joshi
[not found] ` <CGME20240425184708epcas5p4f1d95cd8d285614f712868d205a23115@epcas5p4.samsung.com>
2024-04-25 18:39 ` [PATCH 09/10] block: add support to send meta buffer Kanchan Joshi
2024-04-26 15:21 ` Keith Busch
2024-04-29 11:47 ` Kanchan Joshi
[not found] ` <CGME20240425184710epcas5p2968bbc40ed10d1f0184bb511af054fcb@epcas5p2.samsung.com>
2024-04-25 18:39 ` [PATCH 10/10] nvme: add separate handling for user integrity buffer Kanchan Joshi
2024-04-25 19:56 ` Keith Busch
2024-04-26 10:57 ` kernel test robot [this message]
2024-04-26 14:19 ` [PATCH 00/10] Read/Write with meta/integrity Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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