From: kernel test robot <lkp@intel.com>
To: "Bence Csókás" <csokas.bence@prolan.hu>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, "Csókás,
Bence" <csokas.bence@prolan.hu>,
"Michael Walle" <mwalle@kernel.org>,
"Richard Weinberger" <richard@nod.at>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>
Subject: Re: [PATCH v2] mtd: Verify written data in paranoid mode
Date: Fri, 9 May 2025 13:28:38 +0800 [thread overview]
Message-ID: <202505091318.0QvCicb9-lkp@intel.com> (raw)
In-Reply-To: <20250508183733.514124-3-csokas.bence@prolan.hu>
Hi Bence,
kernel test robot noticed the following build warnings:
[auto build test WARNING on d76bb1ebb5587f66b0f8b8099bfbb44722bc08b3]
url: https://github.com/intel-lab-lkp/linux/commits/Bence-Cs-k-s/mtd-Verify-written-data-in-paranoid-mode/20250509-024044
base: d76bb1ebb5587f66b0f8b8099bfbb44722bc08b3
patch link: https://lore.kernel.org/r/20250508183733.514124-3-csokas.bence%40prolan.hu
patch subject: [PATCH v2] mtd: Verify written data in paranoid mode
config: i386-buildonly-randconfig-002-20250509 (https://download.01.org/0day-ci/archive/20250509/202505091318.0QvCicb9-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250509/202505091318.0QvCicb9-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/202505091318.0QvCicb9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/mtd/mtdcore.c:1775:12: warning: '_mtd_verify' defined but not used [-Wunused-function]
1775 | static int _mtd_verify(struct mtd_info *mtd, loff_t to, size_t len, const u8 *buf)
| ^~~~~~~~~~~
vim +/_mtd_verify +1775 drivers/mtd/mtdcore.c
1774
> 1775 static int _mtd_verify(struct mtd_info *mtd, loff_t to, size_t len, const u8 *buf)
1776 {
1777 struct device *dev = &mtd->dev;
1778 u_char *verify_buf;
1779 size_t r_retlen;
1780 int ret;
1781
1782 verify_buf = devm_kmalloc(dev, len, GFP_KERNEL);
1783 if (!verify_buf)
1784 return -ENOMEM;
1785
1786 ret = mtd_read(mtd, to, len, &r_retlen, verify_buf);
1787 if (ret < 0)
1788 goto err;
1789
1790 if (len != r_retlen) {
1791 /* We shouldn't see short reads */
1792 dev_err(dev, "Verify failed, written %zd but only read %zd",
1793 len, r_retlen);
1794 ret = -EIO;
1795 goto err;
1796 }
1797
1798 if (memcmp(verify_buf, buf, len)) {
1799 dev_err(dev, "Verify failed, compare mismatch!");
1800 ret = -EIO;
1801 }
1802
1803 err:
1804 devm_kfree(dev, verify_buf);
1805 return ret;
1806 }
1807
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "Bence Csókás" <csokas.bence@prolan.hu>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, "Csókás,
Bence" <csokas.bence@prolan.hu>,
"Michael Walle" <mwalle@kernel.org>,
"Richard Weinberger" <richard@nod.at>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>
Subject: Re: [PATCH v2] mtd: Verify written data in paranoid mode
Date: Fri, 9 May 2025 13:28:38 +0800 [thread overview]
Message-ID: <202505091318.0QvCicb9-lkp@intel.com> (raw)
In-Reply-To: <20250508183733.514124-3-csokas.bence@prolan.hu>
Hi Bence,
kernel test robot noticed the following build warnings:
[auto build test WARNING on d76bb1ebb5587f66b0f8b8099bfbb44722bc08b3]
url: https://github.com/intel-lab-lkp/linux/commits/Bence-Cs-k-s/mtd-Verify-written-data-in-paranoid-mode/20250509-024044
base: d76bb1ebb5587f66b0f8b8099bfbb44722bc08b3
patch link: https://lore.kernel.org/r/20250508183733.514124-3-csokas.bence%40prolan.hu
patch subject: [PATCH v2] mtd: Verify written data in paranoid mode
config: i386-buildonly-randconfig-002-20250509 (https://download.01.org/0day-ci/archive/20250509/202505091318.0QvCicb9-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250509/202505091318.0QvCicb9-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/202505091318.0QvCicb9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/mtd/mtdcore.c:1775:12: warning: '_mtd_verify' defined but not used [-Wunused-function]
1775 | static int _mtd_verify(struct mtd_info *mtd, loff_t to, size_t len, const u8 *buf)
| ^~~~~~~~~~~
vim +/_mtd_verify +1775 drivers/mtd/mtdcore.c
1774
> 1775 static int _mtd_verify(struct mtd_info *mtd, loff_t to, size_t len, const u8 *buf)
1776 {
1777 struct device *dev = &mtd->dev;
1778 u_char *verify_buf;
1779 size_t r_retlen;
1780 int ret;
1781
1782 verify_buf = devm_kmalloc(dev, len, GFP_KERNEL);
1783 if (!verify_buf)
1784 return -ENOMEM;
1785
1786 ret = mtd_read(mtd, to, len, &r_retlen, verify_buf);
1787 if (ret < 0)
1788 goto err;
1789
1790 if (len != r_retlen) {
1791 /* We shouldn't see short reads */
1792 dev_err(dev, "Verify failed, written %zd but only read %zd",
1793 len, r_retlen);
1794 ret = -EIO;
1795 goto err;
1796 }
1797
1798 if (memcmp(verify_buf, buf, len)) {
1799 dev_err(dev, "Verify failed, compare mismatch!");
1800 ret = -EIO;
1801 }
1802
1803 err:
1804 devm_kfree(dev, verify_buf);
1805 return ret;
1806 }
1807
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-09 5:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 18:37 [PATCH v2] mtd: Verify written data in paranoid mode Bence Csókás
2025-05-08 18:37 ` Bence Csókás
2025-05-09 5:28 ` kernel test robot [this message]
2025-05-09 5:28 ` kernel test robot
2025-05-12 8:06 ` Miquel Raynal
2025-05-12 8:06 ` Miquel Raynal
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=202505091318.0QvCicb9-lkp@intel.com \
--to=lkp@intel.com \
--cc=csokas.bence@prolan.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richard@nod.at \
--cc=vigneshr@ti.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.