All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC v1 1/4] nvmet-trace: avoid dereferencing pointer too early
Date: Tue, 29 Aug 2023 19:21:28 +0800	[thread overview]
Message-ID: <202308291952.LKh4QF9k-lkp@intel.com> (raw)
In-Reply-To: <20230829091350.16156-2-dwagner@suse.de>

Hi Daniel,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on hch-configfs/for-next]
[also build test WARNING on linus/master v6.5 next-20230829]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Daniel-Wagner/nvmet-trace-avoid-dereferencing-pointer-too-early/20230829-171734
base:   git://git.infradead.org/users/hch/configfs.git for-next
patch link:    https://lore.kernel.org/r/20230829091350.16156-2-dwagner%40suse.de
patch subject: [RFC v1 1/4] nvmet-trace: avoid dereferencing pointer too early
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20230829/202308291952.LKh4QF9k-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230829/202308291952.LKh4QF9k-lkp@intel.com/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 <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308291952.LKh4QF9k-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/nvme/target/trace.c:214:13: warning: no previous prototype for 'nvmet_trace_ctrl_name' [-Wmissing-prototypes]
     214 | const char *nvmet_trace_ctrl_name(struct trace_seq *p, struct nvmet_ctrl *ctrl)
         |             ^~~~~~~~~~~~~~~~~~~~~


vim +/nvmet_trace_ctrl_name +214 drivers/nvme/target/trace.c

a5448fdc469d67 Minwoo Im 2019-06-12  213  
a5448fdc469d67 Minwoo Im 2019-06-12 @214  const char *nvmet_trace_ctrl_name(struct trace_seq *p, struct nvmet_ctrl *ctrl)
a5448fdc469d67 Minwoo Im 2019-06-12  215  {
a5448fdc469d67 Minwoo Im 2019-06-12  216  	const char *ret = trace_seq_buffer_ptr(p);
a5448fdc469d67 Minwoo Im 2019-06-12  217  
a5448fdc469d67 Minwoo Im 2019-06-12  218  	/*
a5448fdc469d67 Minwoo Im 2019-06-12  219  	 * XXX: We don't know the controller instance before executing the
a5448fdc469d67 Minwoo Im 2019-06-12  220  	 * connect command itself because the connect command for the admin
a5448fdc469d67 Minwoo Im 2019-06-12  221  	 * queue will not provide the cntlid which will be allocated in this
a5448fdc469d67 Minwoo Im 2019-06-12  222  	 * command.  In case of io queues, the controller instance will be
a5448fdc469d67 Minwoo Im 2019-06-12  223  	 * mapped by the extra data of the connect command.
a5448fdc469d67 Minwoo Im 2019-06-12  224  	 * If we can know the extra data of the connect command in this stage,
a5448fdc469d67 Minwoo Im 2019-06-12  225  	 * we can update this print statement later.
a5448fdc469d67 Minwoo Im 2019-06-12  226  	 */
a5448fdc469d67 Minwoo Im 2019-06-12  227  	if (ctrl)
a5448fdc469d67 Minwoo Im 2019-06-12  228  		trace_seq_printf(p, "%d", ctrl->cntlid);
a5448fdc469d67 Minwoo Im 2019-06-12  229  	else
a5448fdc469d67 Minwoo Im 2019-06-12  230  		trace_seq_printf(p, "_");
a5448fdc469d67 Minwoo Im 2019-06-12  231  	trace_seq_putc(p, 0);
a5448fdc469d67 Minwoo Im 2019-06-12  232  
a5448fdc469d67 Minwoo Im 2019-06-12  233  	return ret;
a5448fdc469d67 Minwoo Im 2019-06-12  234  }
a5448fdc469d67 Minwoo Im 2019-06-12  235  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-08-29 11:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29  9:13 [RFC v1 0/4] nvmet-fc blktests & autoconnect fixes Daniel Wagner
2023-08-29  9:13 ` [RFC v1 1/4] nvmet-trace: avoid dereferencing pointer too early Daniel Wagner
2023-08-29 11:21   ` kernel test robot [this message]
2023-08-29 19:55   ` kernel test robot
2023-08-29 20:37   ` kernel test robot
2023-09-05  6:48   ` Christoph Hellwig
2023-09-05  8:24     ` Daniel Wagner
2023-09-05  8:33       ` Christoph Hellwig
2023-09-06 11:00   ` Hannes Reinecke
2023-09-06 15:19   ` kernel test robot
2023-08-29  9:13 ` [RFC v1 2/4] nvmet-trace: null terminate device name string correctly Daniel Wagner
2023-09-05  6:49   ` Christoph Hellwig
2023-09-05 10:25     ` Daniel Wagner
2023-09-06 11:01   ` Hannes Reinecke
2023-08-29  9:13 ` [RFC v1 3/4] nvmet-fc: untangle cross refcounting objects Daniel Wagner
2023-09-06 11:22   ` Hannes Reinecke
2023-09-11 10:08     ` Daniel Wagner
2023-08-29  9:13 ` [RFC v1 4/4] nvmet-discovery: do not use invalid port Daniel Wagner
2023-09-05  6:50   ` Christoph Hellwig
2023-09-05 10:40     ` Daniel Wagner
2023-09-11 14:44       ` Daniel Wagner
2023-09-11 18:19         ` Daniel Wagner
2023-09-12  6:38           ` Daniel Wagner
2023-09-13 11:35             ` Christoph Hellwig
2023-09-13 11:59               ` Daniel Wagner
2023-09-06 11:23   ` Hannes Reinecke
2023-08-29  9:13 ` [RFC v1 4/4] nvmet-discovery: Do " Daniel Wagner

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=202308291952.LKh4QF9k-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dwagner@suse.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.