From: kernel test robot <lkp@intel.com>
To: Kuogee Hsieh <quic_khsieh@quicinc.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Rob Clark <robdclark@chromium.org>,
Abhinav Kumar <quic_abhinavk@quicinc.com>
Subject: [drm-msm:msm-next-plus-fixes 69/72] drivers/gpu/drm/msm/dp/dp_drm.c:246:2-7: WARNING: invalid free of devm_ allocated data
Date: Fri, 10 Dec 2021 19:25:07 +0800 [thread overview]
Message-ID: <202112101918.adnak8vR-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/drm/msm.git msm-next-plus-fixes
head: 1c1dcb9d8883f42ea116d99f78e42a7c399f8278
commit: 8a3b4c17f863cde8e8743edd8faffe916c49b960 [69/72] drm/msm/dp: employ bridge mechanism for display enable and disable
config: nds32-randconfig-c004-20211208 (https://download.01.org/0day-ci/archive/20211210/202112101918.adnak8vR-lkp@intel.com/config)
compiler: nds32le-linux-gcc (GCC) 11.2.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
cocci warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/msm/dp/dp_drm.c:246:2-7: WARNING: invalid free of devm_ allocated data
vim +246 drivers/gpu/drm/msm/dp/dp_drm.c
225
226 struct drm_bridge *msm_dp_bridge_init(struct msm_dp *dp_display, struct drm_device *dev,
227 struct drm_encoder *encoder)
228 {
229 int rc;
230 struct msm_dp_bridge *dp_bridge;
231 struct drm_bridge *bridge;
232
233 dp_bridge = devm_kzalloc(dev->dev, sizeof(*dp_bridge), GFP_KERNEL);
234 if (!dp_bridge)
235 return ERR_PTR(-ENOMEM);
236
237 dp_bridge->dp_display = dp_display;
238
239 bridge = &dp_bridge->bridge;
240 bridge->funcs = &dp_bridge_ops;
241 bridge->encoder = encoder;
242
243 rc = drm_bridge_attach(encoder, bridge, NULL, DRM_BRIDGE_ATTACH_NO_CONNECTOR);
244 if (rc) {
245 DRM_ERROR("failed to attach bridge, rc=%d\n", rc);
> 246 kfree(dp_bridge);
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-10 11:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202112101918.adnak8vR-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=robdclark@chromium.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