From: kernel test robot <oliver.sang@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Peng Fan <peng.fan@nxp.com>, <linux-renesas-soc@vger.kernel.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
<oliver.sang@intel.com>
Subject: Re: [PATCH] of: unittest: Run overlay apply/revert sequence three times
Date: Tue, 29 Aug 2023 12:37:58 +0800 [thread overview]
Message-ID: <202308251623.c4668e73-oliver.sang@intel.com> (raw)
In-Reply-To: <a9fb4eb560c58d11a7f167bc78a137b46e76cf15.1692699743.git.geert%2Brenesas@glider.be>
Hello,
kernel test robot noticed "WARNING:at_fs/kernfs/dir.c:#kernfs_remove_by_name_ns" on:
commit: 95a0a69f906c49a1d6ccdcf226e5bda43559548b ("[PATCH] of: unittest: Run overlay apply/revert sequence three times")
url: https://github.com/intel-lab-lkp/linux/commits/Geert-Uytterhoeven/of-unittest-Run-overlay-apply-revert-sequence-three-times/20230822-182410
base: https://git.kernel.org/cgit/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/all/a9fb4eb560c58d11a7f167bc78a137b46e76cf15.1692699743.git.geert%2Brenesas@glider.be/
patch subject: [PATCH] of: unittest: Run overlay apply/revert sequence three times
in testcase: boot
compiler: gcc-9
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
(please refer to attached dmesg/kmsg for entire log/backtrace)
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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202308251623.c4668e73-oliver.sang@intel.com
[ 24.207339][ T1] OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest5/status
[ 24.209547][ T1] ------------[ cut here ]------------
[ 24.210305][ T1] kernfs: can not remove 'status', no directory
[ 24.211312][ T1] WARNING: CPU: 0 PID: 1 at fs/kernfs/dir.c:1658 kernfs_remove_by_name_ns+0x17/0x76
[ 24.212833][ T1] Modules linked in:
[ 24.213403][ T1] CPU: 0 PID: 1 Comm: swapper Tainted: G W N 6.5.0-rc1-00023-g95a0a69f906c #1
[ 24.214935][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 24.216555][ T1] EIP: kernfs_remove_by_name_ns+0x17/0x76
[ 24.217540][ T1] Code: f0 e8 96 d2 e7 ff 8a 55 df 88 d0 83 c4 18 5b 5e 5f 5d c3 55 89 e5 56 53 83 ec 08 85 c0 75 16 52 68 35 75 4f b2 e8 0e fc e4 ff <0f> 0b 58 b8 fe ff ff ff 5a eb 4d 89 4d f0 89 c3 89 55 f4 e8 69 e6
[ 24.220332][ T1] EAX: 0000002d EBX: ed6ed158 ECX: 00000000 EDX: 00000002
[ 24.221538][ T1] ESI: 00000000 EDI: 00000216 EBP: b42f7d88 ESP: b42f7d70
[ 24.222665][ T1] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010246
[ 24.223933][ T1] CR0: 80050033 CR2: ffddb000 CR3: 02f04000 CR4: 00040690
[ 24.225140][ T1] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[ 24.226298][ T1] DR6: fffe0ff0 DR7: 00000400
[ 24.227115][ T1] Call Trace:
[ 24.227804][ T1] ? show_regs+0x49/0x4f
[ 24.228595][ T1] ? kernfs_remove_by_name_ns+0x17/0x76
[ 24.229560][ T1] ? __warn+0x81/0xfe
[ 24.230152][ T1] ? report_bug+0xb0/0x10c
[ 24.230975][ T1] ? kernfs_remove_by_name_ns+0x17/0x76
[ 24.231914][ T1] ? exc_overflow+0x37/0x37
[ 24.232734][ T1] ? handle_bug+0x2b/0x47
[ 24.233364][ T1] ? exc_invalid_op+0x19/0x55
[ 24.234248][ T1] ? handle_exception+0xfd/0xfd
[ 24.235098][ T1] ? exc_overflow+0x37/0x37
[ 24.235877][ T1] ? kernfs_remove_by_name_ns+0x17/0x76
[ 24.236835][ T1] ? exc_overflow+0x37/0x37
[ 24.237662][ T1] ? kernfs_remove_by_name_ns+0x17/0x76
[ 24.238667][ T1] sysfs_remove_bin_file+0xf/0x11
[ 24.239383][ T1] __of_sysfs_remove_bin_file+0x11/0x1c
[ 24.240341][ T1] __of_update_property_sysfs+0x1e/0x2d
[ 24.241249][ T1] __of_changeset_entry_apply+0x150/0x15a
[ 24.242221][ T1] __of_changeset_apply_entries+0x1b/0x65
[ 24.243185][ T1] ? overlay_notify+0x37/0x81
[ 24.243954][ T1] of_overlay_fdt_apply+0x3e3/0x463
[ 24.244827][ T1] overlay_data_apply+0x5c/0x94
[ 24.245635][ T1] of_unittest_apply_overlay+0x18/0x54
[ 24.246690][ T1] of_unittest_apply_revert_overlay_check+0x57/0x142
[ 24.247934][ T1] of_unittest_overlay+0x2b1/0x8bc
[ 24.248801][ T1] of_unittest+0xcaf/0xcf5
[ 24.249537][ T1] ? sched_clock_noinstr+0x8/0xc
[ 24.250258][ T1] ? of_unittest_changeset+0x838/0x838
[ 24.251123][ T1] do_one_initcall+0x6a/0x1a5
[ 24.251928][ T1] kernel_init_freeable+0x17a/0x1c9
[ 24.252774][ T1] ? rest_init+0x140/0x140
[ 24.253396][ T1] kernel_init+0x12/0xf8
[ 24.254130][ T1] ret_from_fork+0x19/0x24
[ 24.254890][ T1] irq event stamp: 2494581
[ 24.255636][ T1] hardirqs last enabled at (2494593): [<b1067cf6>] __up_console_sem+0x3d/0x52
[ 24.257029][ T1] hardirqs last disabled at (2494604): [<b1067cd9>] __up_console_sem+0x20/0x52
[ 24.258525][ T1] softirqs last enabled at (2494484): [<b1e9fe62>] __do_softirq+0x2aa/0x2d8
[ 24.259940][ T1] softirqs last disabled at (2494473): [<b1008ef8>] do_softirq_own_stack+0x2a/0x30
[ 24.261703][ T1] ---[ end trace 0000000000000000 ]---
[ 24.262682][ T1] ### dt-test ### FAIL of_unittest_apply_revert_overlay_check():2167 overlay_5 failed to create @"/testcase-data/overlay-node/test-bus/test-unittest5" disabled
[ 24.265226][ T1] ### dt-test ### EXPECT / : OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest5/status
[ 24.265263][ T1] ### dt-test ### EXPECT \ : OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest6/status
[ 24.267833][ T1] OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest6/status
[ 24.273345][ T1] ### dt-test ### EXPECT / : OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest6/status
[ 24.273352][ T1] ### dt-test ### EXPECT \ : OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest7/status
[ 24.275907][ T1] OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest7/status
[ 24.281335][ T1] ### dt-test ### EXPECT / : OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest7/status
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230825/202308251623.c4668e73-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2023-08-29 4:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a9fb4eb560c58d11a7f167bc78a137b46e76cf15.1692699743.git.geert%2Brenesas@glider.be>
2023-08-29 4:37 ` kernel test robot [this message]
2023-08-22 10:22 [PATCH] of: unittest: Run overlay apply/revert sequence three times Geert Uytterhoeven
2023-08-22 15:32 ` Rob Herring
2023-08-22 17:52 ` Geert Uytterhoeven
2023-08-22 17:59 ` Rob Herring
2023-08-22 19:21 ` Rob Herring
2023-08-23 7:41 ` Geert Uytterhoeven
2023-08-23 13:26 ` Rob Herring
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=202308251623.c4668e73-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox