From: kernel test robot <lkp@intel.com>
To: Ma Ke <make_ruc2021@163.com>,
airlied@gmail.com, daniel@ffwll.ch, javierm@redhat.com,
lyude@redhat.com, mripard@kernel.org,
u.kleine-koenig@pengutronix.de, noralf@tronnes.org,
tzimmermann@suse.de
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i2c/ch7006: fix a possible null pointer dereference
Date: Sat, 7 Oct 2023 13:17:06 +0800 [thread overview]
Message-ID: <202310071306.7oXVHYob-lkp@intel.com> (raw)
In-Reply-To: <20231007031712.3997144-1-make_ruc2021@163.com>
Hi Ma,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on linus/master v6.6-rc4 next-20231006]
[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/Ma-Ke/drm-i2c-ch7006-fix-a-possible-null-pointer-dereference/20231007-112036
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20231007031712.3997144-1-make_ruc2021%40163.com
patch subject: [PATCH] drm/i2c/ch7006: fix a possible null pointer dereference
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20231007/202310071306.7oXVHYob-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231007/202310071306.7oXVHYob-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/202310071306.7oXVHYob-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/i2c/ch7006_drv.c: In function 'ch7006_encoder_get_modes':
>> drivers/gpu/drm/i2c/ch7006_drv.c:239:42: warning: variable 'encoder_mode' set but not used [-Wunused-but-set-variable]
239 | struct drm_display_mode *encoder_mode;
| ^~~~~~~~~~~~
vim +/encoder_mode +239 drivers/gpu/drm/i2c/ch7006_drv.c
226
227 static int ch7006_encoder_get_modes(struct drm_encoder *encoder,
228 struct drm_connector *connector)
229 {
230 struct ch7006_priv *priv = to_ch7006_priv(encoder);
231 const struct ch7006_mode *mode;
232 int n = 0;
233
234 for (mode = ch7006_modes; mode->mode.clock; mode++) {
235 if (~mode->valid_scales & 1<<priv->scale ||
236 ~mode->valid_norms & 1<<priv->norm)
237 continue;
238
> 239 struct drm_display_mode *encoder_mode;
240 encoder_mode = drm_mode_duplicate(encoder->dev, &mode->mode);
241 if (!mode)
242 continue;
243
244 n++;
245 }
246
247 return n;
248 }
249
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-07 5:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 3:17 Ma Ke
2023-10-07 5:17 ` kernel test robot [this message]
2023-10-09 21:45 ` Lyude Paul
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=202310071306.7oXVHYob-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=make_ruc2021@163.com \
--cc=mripard@kernel.org \
--cc=noralf@tronnes.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@pengutronix.de \
/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®