From: Dan Carpenter <dan.carpenter@oracle.com>
To: kbuild@lists.01.org, Russ Weight <russell.h.weight@intel.com>
Cc: lkp@intel.com, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, Xu Yilun <yilun.xu@intel.com>,
Tom Rix <trix@redhat.com>
Subject: drivers/fpga/intel-m10-bmc-sec-update.c:103 flash_count_show() warn: possible memory leak of 'flash_buf'
Date: Fri, 16 Sep 2022 09:56:47 +0300 [thread overview]
Message-ID: <202209160713.HoIRfGTB-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3245cb65fd91cd514801bf91f5a3066d562f0ac4
commit: 154afa5c31cd2de5e6c2c4f35eee390993ee345a fpga: m10bmc-sec: expose max10 flash update count
config: m68k-randconfig-m031-20220914 (https://download.01.org/0day-ci/archive/20220916/202209160713.HoIRfGTB-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 12.1.0
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
smatch warnings:
drivers/fpga/intel-m10-bmc-sec-update.c:103 flash_count_show() warn: possible memory leak of 'flash_buf'
vim +/flash_buf +103 drivers/fpga/intel-m10-bmc-sec-update.c
154afa5c31cd2d Russ Weight 2022-06-06 83 static ssize_t flash_count_show(struct device *dev,
154afa5c31cd2d Russ Weight 2022-06-06 84 struct device_attribute *attr, char *buf)
154afa5c31cd2d Russ Weight 2022-06-06 85 {
154afa5c31cd2d Russ Weight 2022-06-06 86 struct m10bmc_sec *sec = dev_get_drvdata(dev);
154afa5c31cd2d Russ Weight 2022-06-06 87 unsigned int stride, num_bits;
154afa5c31cd2d Russ Weight 2022-06-06 88 u8 *flash_buf;
154afa5c31cd2d Russ Weight 2022-06-06 89 int cnt, ret;
154afa5c31cd2d Russ Weight 2022-06-06 90
154afa5c31cd2d Russ Weight 2022-06-06 91 stride = regmap_get_reg_stride(sec->m10bmc->regmap);
154afa5c31cd2d Russ Weight 2022-06-06 92 num_bits = FLASH_COUNT_SIZE * 8;
154afa5c31cd2d Russ Weight 2022-06-06 93
154afa5c31cd2d Russ Weight 2022-06-06 94 flash_buf = kmalloc(FLASH_COUNT_SIZE, GFP_KERNEL);
154afa5c31cd2d Russ Weight 2022-06-06 95 if (!flash_buf)
154afa5c31cd2d Russ Weight 2022-06-06 96 return -ENOMEM;
154afa5c31cd2d Russ Weight 2022-06-06 97
154afa5c31cd2d Russ Weight 2022-06-06 98 if (FLASH_COUNT_SIZE % stride) {
154afa5c31cd2d Russ Weight 2022-06-06 99 dev_err(sec->dev,
154afa5c31cd2d Russ Weight 2022-06-06 100 "FLASH_COUNT_SIZE (0x%x) not aligned to stride (0x%x)\n",
154afa5c31cd2d Russ Weight 2022-06-06 101 FLASH_COUNT_SIZE, stride);
154afa5c31cd2d Russ Weight 2022-06-06 102 WARN_ON_ONCE(1);
do this check before the kmalloc()?
154afa5c31cd2d Russ Weight 2022-06-06 @103 return -EINVAL;
154afa5c31cd2d Russ Weight 2022-06-06 104 }
154afa5c31cd2d Russ Weight 2022-06-06 105
154afa5c31cd2d Russ Weight 2022-06-06 106 ret = regmap_bulk_read(sec->m10bmc->regmap, STAGING_FLASH_COUNT,
154afa5c31cd2d Russ Weight 2022-06-06 107 flash_buf, FLASH_COUNT_SIZE / stride);
154afa5c31cd2d Russ Weight 2022-06-06 108 if (ret) {
154afa5c31cd2d Russ Weight 2022-06-06 109 dev_err(sec->dev,
154afa5c31cd2d Russ Weight 2022-06-06 110 "failed to read flash count: %x cnt %x: %d\n",
154afa5c31cd2d Russ Weight 2022-06-06 111 STAGING_FLASH_COUNT, FLASH_COUNT_SIZE / stride, ret);
154afa5c31cd2d Russ Weight 2022-06-06 112 goto exit_free;
154afa5c31cd2d Russ Weight 2022-06-06 113 }
154afa5c31cd2d Russ Weight 2022-06-06 114 cnt = num_bits - bitmap_weight((unsigned long *)flash_buf, num_bits);
154afa5c31cd2d Russ Weight 2022-06-06 115
154afa5c31cd2d Russ Weight 2022-06-06 116 exit_free:
154afa5c31cd2d Russ Weight 2022-06-06 117 kfree(flash_buf);
154afa5c31cd2d Russ Weight 2022-06-06 118
154afa5c31cd2d Russ Weight 2022-06-06 119 return ret ? : sysfs_emit(buf, "%u\n", cnt);
154afa5c31cd2d Russ Weight 2022-06-06 120 }
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-16 6:57 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=202209160713.HoIRfGTB-lkp@intel.com \
--to=dan.carpenter@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox