From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Liu Shixin <liushixin2@huawei.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq/irqdesc: hide illegible sysfs warning of kobject_del()
Date: Sat, 12 Nov 2022 09:59:08 +0100 [thread overview]
Message-ID: <Y29gXLqK2wiu7/WK@kroah.com> (raw)
In-Reply-To: <20221112093939.616270-1-liushixin2@huawei.com>
On Sat, Nov 12, 2022 at 05:39:39PM +0800, Liu Shixin wrote:
> If irq_sysfs_add() failed, system will report a warning but don't call
> kobject_put() to release the descriptor.
I can not parse this sentance :(
> Then in irq_sysfs_del(), we continue to call kobject_del(). In such
> situation, kobject_del() will complains about a object with no parent
> like this:
Then we should not be calling irq_sysfs_del() if the call failed. That
is the real fix here.
>
> kernfs: can not remove 'actions', no directory
> WARNING: CPU: 0 PID: 277 at fs/kernfs/dir.c:1615 kernfs_remove_by_name_ns+0xd5/0xe0
> [...]
> Call Trace:
> <TASK>
> remove_files.isra.0+0x3f/0xb0
> sysfs_remove_group+0x68/0xe0
> sysfs_remove_groups+0x41/0x70
> __kobject_del+0x45/0xc0
> kobject_del+0x2a/0x40
> free_desc+0x44/0x70
> irq_free_descs+0x5d/0x90
> [...]
>
> Use kobj->state_in_sysfs to check whether kobject is added succeed. And
> if not, we should not call kobject_del().
That does not describe what you are doing here at all.
>
> Signed-off-by: Liu Shixin <liushixin2@huawei.com>
> ---
> kernel/irq/irqdesc.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/irq/irqdesc.c b/kernel/irq/irqdesc.c
> index a91f9001103c..a820d96210d4 100644
> --- a/kernel/irq/irqdesc.c
> +++ b/kernel/irq/irqdesc.c
> @@ -300,10 +300,11 @@ static void irq_sysfs_del(struct irq_desc *desc)
> /*
> * If irq_sysfs_init() has not yet been invoked (early boot), then
> * irq_kobj_base is NULL and the descriptor was never added.
> + * And the descriptor may be added failed.
> * kobject_del() complains about a object with no parent, so make
> * it conditional.
> */
> - if (irq_kobj_base)
> + if (irq_kobj_base && desc->kobj.parent)
How would the parent be NULL? Parent devices always stick around until
the child is removed, otherwise something is really wrong here. You
should never have to look at the parent.
thanks,
greg k-h
next prev parent reply other threads:[~2022-11-12 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 9:39 [PATCH] genirq/irqdesc: hide illegible sysfs warning of kobject_del() Liu Shixin
2022-11-12 8:59 ` Greg Kroah-Hartman [this message]
2022-11-12 9:19 ` Liu Shixin
2022-11-12 9:34 ` Greg Kroah-Hartman
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=Y29gXLqK2wiu7/WK@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
/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