From: kernel test robot <lkp@intel.com>
To: Vedang Nagar <quic_vnagar@quicinc.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 2/2] media: venus: fix OOB access issue while reading sequence changed events
Date: Sun, 16 Feb 2025 12:57:53 +0800 [thread overview]
Message-ID: <202502161251.lBVyP1dc-lkp@intel.com> (raw)
In-Reply-To: <20250215-venus-security-fixes-v2-2-cfc7e4b87168@quicinc.com>
Hi Vedang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 91e71d606356e50f238d7a87aacdee4abc427f07]
url: https://github.com/intel-lab-lkp/linux/commits/Vedang-Nagar/media-venus-fix-OOB-read-issue-due-to-double-read/20250216-012213
base: 91e71d606356e50f238d7a87aacdee4abc427f07
patch link: https://lore.kernel.org/r/20250215-venus-security-fixes-v2-2-cfc7e4b87168%40quicinc.com
patch subject: [PATCH v2 2/2] media: venus: fix OOB access issue while reading sequence changed events
config: s390-randconfig-002-20250216 (https://download.01.org/0day-ci/archive/20250216/202502161251.lBVyP1dc-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250216/202502161251.lBVyP1dc-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/202502161251.lBVyP1dc-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/media/platform/qcom/venus/hfi_msgs.c:22:42: warning: parameter 'data_ptr' set but not used [-Wunused-but-set-parameter]
22 | static inline int increment_data_ptr(u8 *data_ptr, u32 *rem_bytes)
| ^
1 warning generated.
vim +/data_ptr +22 drivers/media/platform/qcom/venus/hfi_msgs.c
21
> 22 static inline int increment_data_ptr(u8 *data_ptr, u32 *rem_bytes)
23 {
24 if (*rem_bytes < sizeof(u32))
25 return -EINVAL;
26 data_ptr += sizeof(u32);
27 *rem_bytes -= sizeof(u32);
28
29 return 0;
30 }
31
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-02-16 4:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 17:19 [PATCH v2 0/2] venus driver fixes to avoid possible OOB read access Vedang Nagar
2025-02-15 17:19 ` [PATCH v2 1/2] media: venus: fix OOB read issue due to double read Vedang Nagar
2025-03-04 13:45 ` Bryan O'Donoghue
2025-05-13 13:13 ` Dikshita Agarwal
2025-02-15 17:19 ` [PATCH v2 2/2] media: venus: fix OOB access issue while reading sequence changed events Vedang Nagar
2025-02-16 4:57 ` kernel test robot [this message]
2025-03-04 13:35 ` Bryan O'Donoghue
2025-05-13 7:02 ` Dikshita Agarwal
2025-05-13 13:00 ` Vikash Garodia
2025-02-16 16:03 ` [PATCH v2 0/2] venus driver fixes to avoid possible OOB read access Bryan O'Donoghue
2025-03-02 11:58 ` Vedang Nagar
2025-03-02 15:56 ` Bryan O'Donoghue
2025-03-03 13:12 ` Vikash Garodia
2025-03-03 14:56 ` Bryan O'Donoghue
2025-03-03 15:01 ` Vikash Garodia
2025-03-04 13:30 ` Bryan O'Donoghue
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=202502161251.lBVyP1dc-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_vnagar@quicinc.com \
/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.