From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH V2 1/2] kobject: don't delay to cleanup module kobject
Date: Tue, 07 Dec 2021 21:58:32 +0800 [thread overview]
Message-ID: <202112072131.XiIJR8RS-lkp@intel.com> (raw)
In-Reply-To: <20211129034509.2646872-2-ming.lei@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3424 bytes --]
Hi Ming,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on v5.16-rc4 next-20211207]
[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/Ming-Lei/kobject-avoid-to-cleanup-kobject-after-module-is-unloaded/20211129-114940
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git 2043727c2882928a10161ddee52b196b7db402fd
config: s390-randconfig-r033-20211207 (https://download.01.org/0day-ci/archive/20211207/202112072131.XiIJR8RS-lkp(a)intel.com/config)
compiler: s390-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/39e48129051282ab6eff0746002e84cf56218bd7
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Ming-Lei/kobject-avoid-to-cleanup-kobject-after-module-is-unloaded/20211129-114940
git checkout 39e48129051282ab6eff0746002e84cf56218bd7
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=s390 SHELL=/bin/bash
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 >>):
lib/kobject.c: In function 'kobject_release':
>> lib/kobject.c:741:29: error: 'module_ktype' undeclared (first use in this function); did you mean 'module_state'?
741 | if (kobj->ktype == &module_ktype)
| ^~~~~~~~~~~~
| module_state
lib/kobject.c:741:29: note: each undeclared identifier is reported only once for each function it appears in
vim +741 lib/kobject.c
725
726 static void kobject_release(struct kref *kref)
727 {
728 struct kobject *kobj = container_of(kref, struct kobject, kref);
729 #ifdef CONFIG_DEBUG_KOBJECT_RELEASE
730 unsigned long delay = HZ + HZ * (get_random_int() & 0x3);
731
732 /*
733 * Don't delay to release module kobject so that we can detect late
734 * kobject release more effectively because module unloading waits
735 * for completion of module kobject release, see mod_kobject_put.
736 *
737 * Meantime mod_kobject_put() always waits for completion of module
738 * kobject's release, CONFIG_DEBUG_KOBJECT_RELEASE is basically
739 * useless for debugging module kobject's release.
740 */
> 741 if (kobj->ktype == &module_ktype)
742 delay = 0;
743
744 pr_info("kobject: '%s' (%p): %s, parent %p (delayed %ld)\n",
745 kobject_name(kobj), kobj, __func__, kobj->parent, delay);
746 INIT_DELAYED_WORK(&kobj->release, kobject_delayed_cleanup);
747
748 schedule_delayed_work(&kobj->release, delay);
749 #else
750 kobject_cleanup(kobj);
751 #endif
752 }
753
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Ming Lei <ming.lei@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kbuild-all@lists.01.org, Petr Mladek <pmladek@suse.com>,
linux-kernel@vger.kernel.org,
Luis Chamberlain <mcgrof@kernel.org>,
Ming Lei <ming.lei@redhat.com>
Subject: Re: [PATCH V2 1/2] kobject: don't delay to cleanup module kobject
Date: Tue, 7 Dec 2021 21:58:32 +0800 [thread overview]
Message-ID: <202112072131.XiIJR8RS-lkp@intel.com> (raw)
In-Reply-To: <20211129034509.2646872-2-ming.lei@redhat.com>
Hi Ming,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on driver-core/driver-core-testing]
[also build test ERROR on v5.16-rc4 next-20211207]
[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/Ming-Lei/kobject-avoid-to-cleanup-kobject-after-module-is-unloaded/20211129-114940
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git 2043727c2882928a10161ddee52b196b7db402fd
config: s390-randconfig-r033-20211207 (https://download.01.org/0day-ci/archive/20211207/202112072131.XiIJR8RS-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/39e48129051282ab6eff0746002e84cf56218bd7
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Ming-Lei/kobject-avoid-to-cleanup-kobject-after-module-is-unloaded/20211129-114940
git checkout 39e48129051282ab6eff0746002e84cf56218bd7
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=s390 SHELL=/bin/bash
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 >>):
lib/kobject.c: In function 'kobject_release':
>> lib/kobject.c:741:29: error: 'module_ktype' undeclared (first use in this function); did you mean 'module_state'?
741 | if (kobj->ktype == &module_ktype)
| ^~~~~~~~~~~~
| module_state
lib/kobject.c:741:29: note: each undeclared identifier is reported only once for each function it appears in
vim +741 lib/kobject.c
725
726 static void kobject_release(struct kref *kref)
727 {
728 struct kobject *kobj = container_of(kref, struct kobject, kref);
729 #ifdef CONFIG_DEBUG_KOBJECT_RELEASE
730 unsigned long delay = HZ + HZ * (get_random_int() & 0x3);
731
732 /*
733 * Don't delay to release module kobject so that we can detect late
734 * kobject release more effectively because module unloading waits
735 * for completion of module kobject release, see mod_kobject_put.
736 *
737 * Meantime mod_kobject_put() always waits for completion of module
738 * kobject's release, CONFIG_DEBUG_KOBJECT_RELEASE is basically
739 * useless for debugging module kobject's release.
740 */
> 741 if (kobj->ktype == &module_ktype)
742 delay = 0;
743
744 pr_info("kobject: '%s' (%p): %s, parent %p (delayed %ld)\n",
745 kobject_name(kobj), kobj, __func__, kobj->parent, delay);
746 INIT_DELAYED_WORK(&kobj->release, kobject_delayed_cleanup);
747
748 schedule_delayed_work(&kobj->release, delay);
749 #else
750 kobject_cleanup(kobj);
751 #endif
752 }
753
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2021-12-07 13:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 3:45 [PATCH V2 0/2] kobject: avoid to cleanup kobject after module is unloaded Ming Lei
2021-11-29 3:45 ` [PATCH V2 1/2] kobject: don't delay to cleanup module kobject Ming Lei
2021-12-03 15:08 ` Greg Kroah-Hartman
2021-12-07 13:58 ` kernel test robot [this message]
2021-12-07 13:58 ` kernel test robot
2021-11-29 3:45 ` [PATCH V2 2/2] kobject: wait until kobject is cleaned up before freeing module Ming Lei
2021-12-03 15:07 ` Greg Kroah-Hartman
2021-12-06 2:13 ` Ming Lei
2021-12-06 8:04 ` Greg Kroah-Hartman
2021-12-07 1:50 ` Ming Lei
2021-12-07 10:32 ` Petr Mladek
2021-12-07 12:51 ` Ming Lei
2021-12-07 14:02 ` Petr Mladek
2022-07-07 4:54 ` Ming Lei
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=202112072131.XiIJR8RS-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.