mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Lin Ma <linma@zju.edu.cn>,
	mchehab@kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, Lin Ma <linma@zju.edu.cn>
Subject: Re: [PATCH v0] media: dvbdev: adopts refcnt to avoid UAF
Date: Mon, 8 Aug 2022 12:26:48 +0800	[thread overview]
Message-ID: <202208081225.fgMVwVrN-lkp@intel.com> (raw)
In-Reply-To: <20220807145952.10368-1-linma@zju.edu.cn>

Hi Lin,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on media-tree/master]
[also build test WARNING on linus/master v5.19 next-20220805]
[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/Lin-Ma/media-dvbdev-adopts-refcnt-to-avoid-UAF/20220807-230449
base:   git://linuxtv.org/media_tree.git master
reproduce: make htmldocs

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> include/media/dvbdev.h:203: warning: expecting prototype for dvb_device_get(). Prototype was for dvb_device_put() instead

vim +203 include/media/dvbdev.h

   187	
   188		void *priv;
 > 189	};
   190	
   191	/**
   192	 * dvb_device_get - Increase dvb_device reference
   193	 *
   194	 * @dvbdev:	pointer to struct dvb_device
   195	 */
   196	struct dvb_device *dvb_device_get(struct dvb_device *dvbdev);
   197	
   198	/**
   199	 * dvb_device_get - Decrease dvb_device reference
   200	 *
   201	 * @dvbdev:	pointer to struct dvb_device
   202	 */
 > 203	void dvb_device_put(struct dvb_device *dvbdev);
   204	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

      reply	other threads:[~2022-08-08  4:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07 14:59 Lin Ma
2022-08-08  4:26 ` kernel test robot [this message]

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=202208081225.fgMVwVrN-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linma@zju.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®