From: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
To: Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Paul Moore <paul@paul-moore.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org,
James Morris <jmorris@namei.org>,
Andy Shevchenko <andriy.shevchenko@intel.com>
Subject: INFO: BUG: kobject: 'integrity' (000000005198bea8): does not have a release() function, it is broken and must be fixed. See ...
Date: Wed, 8 Mar 2023 15:08:21 +0100 [thread overview]
Message-ID: <60b2b66c-22c9-1d38-ed1c-7b7d95e32720@alu.unizg.hr> (raw)
Hi, all!
This one is said to be bug, if we trust the Linux kernel debug output.
Usually I wouldn't have noticed it, but we were debugging the other module under
supervision from Andy of Intel. So it happened that I was accidentally monitoring
how the kobject_release() was called for kernel objects at shutdown of the OS.
It is past the rsyslog lifetime, so the only way I could capture it was a photo
from the smartphone.
Please see the bug reports from the kernel log:
https://domac.alu.hr/~mtodorov/linux/bugreports/integrity/20230308_123748.jpg
https://domac.alu.hr/~mtodorov/linux/bugreports/integrity/20230308_123752.jpg
The kernel is Linux 6.2.0-mg-andy-devres-12485-gf3a2439f20d9-dirty x86_64
on a LENOVO_MT_10TX_BU_Lenovo_FM_V530S-07ICB running AlmaLinux 8.7.
I was unable to reproduce on the other Lenovo laptop box, for the kernel
refused to boot, unable to find root drive on NVMe (other kernels w/o
CONFIG_DEBUG_KOBJECT=y run smoothly).
Config used is:
https://domac.alu.hr/~mtodorov/linux/bugreports/integrity/config-6.2.0-mg-andy-devres-12485-gf3a2439f20d9-dirty
As I already said to Andy, this might not be a critical bug, for it happens
only at shutdown AFAICS. However, it can be a sign of some more serious problem
in the code. :-/
Hope this helps.
Regards,
Mirsad
--
Mirsad Goran Todorovac
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb, Republic of Croatia
reply other threads:[~2023-03-08 14:10 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=60b2b66c-22c9-1d38-ed1c-7b7d95e32720@alu.unizg.hr \
--to=mirsad.todorovac@alu.unizg.hr \
--cc=andriy.shevchenko@intel.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).