From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH v2 01/13] media: v4l2-ctrls-api: fix error handling for v4l2_g_ctrl()
Date: Tue, 22 Oct 2024 02:04:52 +0800 [thread overview]
Message-ID: <202410220105.oP6D4QD7-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <4d36ccf66f48a870c9bc0f7e9fda595505c4d342.1729230718.git.mchehab+huawei@kernel.org>
References: <4d36ccf66f48a870c9bc0f7e9fda595505c4d342.1729230718.git.mchehab+huawei@kernel.org>
TO: Mauro Carvalho Chehab <mchehab@kernel.org>
CC: linux-media@vger.kernel.org
Hi Mauro,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linuxtv-media-stage/master]
[also build test WARNING on linus/master v6.12-rc4]
[cannot apply to next-20241021]
[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/Mauro-Carvalho-Chehab/media-v4l2-ctrls-api-fix-error-handling-for-v4l2_g_ctrl/20241018-181159
base: https://git.linuxtv.org/media_stage.git master
patch link: https://lore.kernel.org/r/4d36ccf66f48a870c9bc0f7e9fda595505c4d342.1729230718.git.mchehab%2Bhuawei%40kernel.org
patch subject: [PATCH v2 01/13] media: v4l2-ctrls-api: fix error handling for v4l2_g_ctrl()
:::::: branch date: 3 days ago
:::::: commit date: 3 days ago
config: i386-randconfig-141-20241021 (https://download.01.org/0day-ci/archive/20241022/202410220105.oP6D4QD7-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202410220105.oP6D4QD7-lkp@intel.com/
smatch warnings:
drivers/media/v4l2-core/v4l2-ctrls-api.c:825 set_ctrl_lock() warn: inconsistent returns 'ctrl->handler->lock'.
vim +825 drivers/media/v4l2-core/v4l2-ctrls-api.c
71c689dc2e732d4 Hans Verkuil 2021-04-27 810
71c689dc2e732d4 Hans Verkuil 2021-04-27 811 /* Helper function for VIDIOC_S_CTRL compatibility */
71c689dc2e732d4 Hans Verkuil 2021-04-27 812 static int set_ctrl_lock(struct v4l2_fh *fh, struct v4l2_ctrl *ctrl,
71c689dc2e732d4 Hans Verkuil 2021-04-27 813 struct v4l2_ext_control *c)
71c689dc2e732d4 Hans Verkuil 2021-04-27 814 {
71c689dc2e732d4 Hans Verkuil 2021-04-27 815 int ret;
71c689dc2e732d4 Hans Verkuil 2021-04-27 816
71c689dc2e732d4 Hans Verkuil 2021-04-27 817 v4l2_ctrl_lock(ctrl);
54c5e2c49a4358b Mauro Carvalho Chehab 2024-10-18 818 ret = user_to_new(c, ctrl);
54c5e2c49a4358b Mauro Carvalho Chehab 2024-10-18 819 if (ret)
54c5e2c49a4358b Mauro Carvalho Chehab 2024-10-18 820 return ret;
71c689dc2e732d4 Hans Verkuil 2021-04-27 821 ret = set_ctrl(fh, ctrl, 0);
71c689dc2e732d4 Hans Verkuil 2021-04-27 822 if (!ret)
54c5e2c49a4358b Mauro Carvalho Chehab 2024-10-18 823 ret = cur_to_user(c, ctrl);
71c689dc2e732d4 Hans Verkuil 2021-04-27 824 v4l2_ctrl_unlock(ctrl);
71c689dc2e732d4 Hans Verkuil 2021-04-27 @825 return ret;
71c689dc2e732d4 Hans Verkuil 2021-04-27 826 }
71c689dc2e732d4 Hans Verkuil 2021-04-27 827
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-10-21 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 18:04 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-18 5:53 [PATCH v2 00/13] Media: fix several issues on drivers Mauro Carvalho Chehab
2024-10-18 5:53 ` [PATCH v2 01/13] media: v4l2-ctrls-api: fix error handling for v4l2_g_ctrl() Mauro Carvalho Chehab
2024-10-18 6:13 ` Hans Verkuil
2024-10-18 6:26 ` Mauro Carvalho Chehab
2024-10-21 18:32 ` Dan Carpenter
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=202410220105.oP6D4QD7-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@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.