From: kernel test robot <lkp@intel.com>
To: Alfie Varghese <alfievarghese22@gmail.com>,
neil.armstrong@linaro.org, gregkh@linuxfoundation.org,
linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Alfie Varghese <alfievarghese22@gmail.com>
Subject: Re: [PATCH v2] staging: media: meson: vdec: fix advanced concurrency and UAF bugs
Date: Tue, 14 Jul 2026 22:23:48 +0800 [thread overview]
Message-ID: <202607142224.5HqGONfe-lkp@intel.com> (raw)
In-Reply-To: <20260713181602.773-1-alfievarghese22@gmail.com>
Hi Alfie,
kernel test robot noticed the following build errors:
[auto build test ERROR on staging/staging-testing]
url: https://github.com/intel-lab-lkp/linux/commits/Alfie-Varghese/staging-media-meson-vdec-fix-advanced-concurrency-and-UAF-bugs/20260714-023427
base: staging/staging-testing
patch link: https://lore.kernel.org/r/20260713181602.773-1-alfievarghese22%40gmail.com
patch subject: [PATCH v2] staging: media: meson: vdec: fix advanced concurrency and UAF bugs
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260714/202607142224.5HqGONfe-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project b3e6e6dabdc02153552a64fc74ff5c7532447eed)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260714/202607142224.5HqGONfe-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/202607142224.5HqGONfe-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/staging/media/meson/vdec/vdec.c:156:28: error: no member named 'm2m_dev' in 'struct amvdec_session'
156 | v4l2_m2m_job_finish(sess->m2m_dev, sess->m2m_ctx);
| ~~~~ ^
1 error generated.
vim +156 drivers/staging/media/meson/vdec/vdec.c
3e7f51bd96077a Maxime Jourdan 2019-06-06 151
3e7f51bd96077a Maxime Jourdan 2019-06-06 152 static void vdec_m2m_job_abort(void *priv)
3e7f51bd96077a Maxime Jourdan 2019-06-06 153 {
3e7f51bd96077a Maxime Jourdan 2019-06-06 154 struct amvdec_session *sess = priv;
3e7f51bd96077a Maxime Jourdan 2019-06-06 155
3e7f51bd96077a Maxime Jourdan 2019-06-06 @156 v4l2_m2m_job_finish(sess->m2m_dev, sess->m2m_ctx);
3e7f51bd96077a Maxime Jourdan 2019-06-06 157 }
3e7f51bd96077a Maxime Jourdan 2019-06-06 158
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-07-14 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 18:16 [PATCH v2] staging: media: meson: vdec: fix advanced concurrency and UAF bugs Alfie Varghese
2026-07-13 19:37 ` Ferass El Hafidi
2026-07-14 7:15 ` Dan Carpenter
2026-07-14 13:59 ` kernel test robot
2026-07-14 14:23 ` 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=202607142224.5HqGONfe-lkp@intel.com \
--to=lkp@intel.com \
--cc=alfievarghese22@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=llvm@lists.linux.dev \
--cc=neil.armstrong@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox