From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 4/4] zram: fix possible races between sysfs use and bdev access
Date: Sun, 25 Apr 2021 02:47:25 +0800 [thread overview]
Message-ID: <202104250226.S0ex5vsG-lkp@intel.com> (raw)
In-Reply-To: <20210423011108.11988-5-mcgrof@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2783 bytes --]
Hi Luis,
I love your patch! Yet something to improve:
[auto build test ERROR on block/for-next]
[also build test ERROR on v5.12-rc8 next-20210423]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Luis-Chamberlain/zram-fix-few-sysfs-races/20210423-091311
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/f5a504c4eb54fd32acdbb779e3ede281f3039a5a
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Luis-Chamberlain/zram-fix-few-sysfs-races/20210423-091311
git checkout f5a504c4eb54fd32acdbb779e3ede281f3039a5a
# save the attached .config to linux build tree
make W=1 W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/block/zram/zram_drv.c: In function 'writeback_limit_enable_show':
>> drivers/block/zram/zram_drv.c:451:3: error: 'len' undeclared (first use in this function)
451 | len = -ENODEV;
| ^~~
drivers/block/zram/zram_drv.c:451:3: note: each undeclared identifier is reported only once for each function it appears in
drivers/block/zram/zram_drv.c:469:1: error: control reaches end of non-void function [-Werror=return-type]
469 | }
| ^
cc1: some warnings being treated as errors
vim +/len +451 drivers/block/zram/zram_drv.c
440
441 static ssize_t writeback_limit_enable_show(struct device *dev,
442 struct device_attribute *attr, char *buf)
443 {
444 bool val;
445 struct zram *zram;
446
447 if (!try_module_get(THIS_MODULE))
448 return -ENODEV;
449
450 if (!bdgrab(dev_to_bdev(dev))) {
> 451 len = -ENODEV;
452 goto out_nodev;
453 }
454
455 zram = dev_to_zram(dev);
456
457 down_read(&zram->init_lock);
458 spin_lock(&zram->wb_limit_lock);
459 val = zram->wb_limit_enable;
460 spin_unlock(&zram->wb_limit_lock);
461 up_read(&zram->init_lock);
462 len = scnprintf(buf, PAGE_SIZE, "%d\n", val);
463
464 bdput(dev_to_bdev(dev));
465 out_nodev:
466 module_put(THIS_MODULE);
467
468 return len;
469 }
470
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 41460 bytes --]
next prev parent reply other threads:[~2021-04-24 18:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 1:11 [PATCH v2 0/4] zram: fix few sysfs races Luis Chamberlain
2021-04-23 1:11 ` [PATCH v2 1/4] zram: fix crashes due to use of cpu hotplug multistate Luis Chamberlain
2021-05-19 19:54 ` Minchan Kim
2021-04-23 1:11 ` [PATCH v2 2/4] zram: avoid disksize setting when device is being claimed Luis Chamberlain
2021-05-19 19:56 ` Minchan Kim
2021-04-23 1:11 ` [PATCH v2 3/4] zram: fix deadlock with sysfs attribute usage and driver removal Luis Chamberlain
2021-04-23 1:11 ` [PATCH v2 4/4] zram: fix possible races between sysfs use and bdev access Luis Chamberlain
2021-04-24 18:47 ` kernel test robot [this message]
2021-05-19 20:09 ` [PATCH v2 0/4] zram: fix few sysfs races Minchan Kim
2021-05-19 20:20 ` Luis Chamberlain
2021-05-21 20:01 ` Greg Kroah-Hartman
2021-05-21 20:16 ` Luis Chamberlain
2021-05-21 20:45 ` Greg Kroah-Hartman
2021-05-21 21:08 ` Luis Chamberlain
2021-05-22 7:48 ` Greg Kroah-Hartman
2021-05-25 1:16 ` Luis Chamberlain
2021-05-25 7:41 ` Greg Kroah-Hartman
2021-06-21 23:19 ` Luis Chamberlain
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=202104250226.S0ex5vsG-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.