All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: naohiro.aota@wdc.com, rafael@kernel.org,
	damien.lemoal@opensource.wdc.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, huyue2@coolpad.com,
	jth@kernel.org, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH 1/3] kobject: introduce kobject_is_added()
Date: Thu, 6 Apr 2023 11:59:59 +0200	[thread overview]
Message-ID: <2023040628-cocoa-lizard-9941@gregkh> (raw)
In-Reply-To: <20230406093056.33916-1-frank.li@vivo.com>

On Thu, Apr 06, 2023 at 05:30:54PM +0800, Yangtao Li wrote:
> Add kobject_is_added() to avoid consumers from directly accessing
> the internal variables of kobject.
> 
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
>  include/linux/kobject.h | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/include/linux/kobject.h b/include/linux/kobject.h
> index bdab370a24f4..b5cdb0c58729 100644
> --- a/include/linux/kobject.h
> +++ b/include/linux/kobject.h
> @@ -203,6 +203,11 @@ static inline const struct kobj_type *get_ktype(const struct kobject *kobj)
>  	return kobj->ktype;
>  }
>  
> +static inline int kobject_is_added(struct kobject *kobj)
> +{
> +	return kobj->state_in_sysfs;
> +}
> +

No, this implies that the caller is not doing something correctly as it
should always know if it has added a kobject or not.  Let me review the
please where you used this to find the problems there...

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: xiang@kernel.org, chao@kernel.org, huyue2@coolpad.com,
	jefflexu@linux.alibaba.com, damien.lemoal@opensource.wdc.com,
	naohiro.aota@wdc.com, jth@kernel.org, rafael@kernel.org,
	linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/3] kobject: introduce kobject_is_added()
Date: Thu, 6 Apr 2023 11:59:59 +0200	[thread overview]
Message-ID: <2023040628-cocoa-lizard-9941@gregkh> (raw)
In-Reply-To: <20230406093056.33916-1-frank.li@vivo.com>

On Thu, Apr 06, 2023 at 05:30:54PM +0800, Yangtao Li wrote:
> Add kobject_is_added() to avoid consumers from directly accessing
> the internal variables of kobject.
> 
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
>  include/linux/kobject.h | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/include/linux/kobject.h b/include/linux/kobject.h
> index bdab370a24f4..b5cdb0c58729 100644
> --- a/include/linux/kobject.h
> +++ b/include/linux/kobject.h
> @@ -203,6 +203,11 @@ static inline const struct kobj_type *get_ktype(const struct kobject *kobj)
>  	return kobj->ktype;
>  }
>  
> +static inline int kobject_is_added(struct kobject *kobj)
> +{
> +	return kobj->state_in_sysfs;
> +}
> +

No, this implies that the caller is not doing something correctly as it
should always know if it has added a kobject or not.  Let me review the
please where you used this to find the problems there...

thanks,

greg k-h

  parent reply	other threads:[~2023-04-06 10:00 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06  9:30 [PATCH 1/3] kobject: introduce kobject_is_added() Yangtao Li
2023-04-06  9:30 ` Yangtao Li
2023-04-06  9:30 ` [PATCH 2/3] erofs: convert to use kobject_is_added() Yangtao Li
2023-04-06  9:30   ` Yangtao Li
2023-04-06 10:03   ` Greg KH
2023-04-06 10:03     ` Greg KH
2023-04-06 10:13     ` Gao Xiang
2023-04-06 10:13       ` Gao Xiang
2023-04-06 10:27       ` Greg KH
2023-04-06 10:27         ` Greg KH
2023-04-06 10:55         ` Gao Xiang
2023-04-06 10:55           ` Gao Xiang
2023-04-06 11:19           ` Greg KH
2023-04-06 11:19             ` Greg KH
2023-04-06 12:07     ` Yangtao Li
2023-04-06 12:07       ` Yangtao Li
2023-04-06 13:50       ` Yangtao Li
2023-04-06 13:50         ` Yangtao Li
2023-04-06 14:31       ` Greg KH
2023-04-06 14:31         ` Greg KH
2023-04-06 17:52         ` Yangtao Li
2023-04-06 17:52           ` Yangtao Li
2023-04-07  6:09         ` Yangtao Li
2023-04-07  6:09           ` Yangtao Li
2023-04-07  7:23         ` Yangtao Li
2023-04-07  7:23           ` Yangtao Li
2023-04-06  9:30 ` [PATCH 3/3] zonefs: " Yangtao Li
2023-04-06  9:30   ` Yangtao Li
2023-04-06 10:05   ` Greg KH
2023-04-06 10:05     ` Greg KH
2023-04-06 10:13     ` Damien Le Moal
2023-04-06 10:13       ` Damien Le Moal
2023-04-06 10:26       ` Greg KH
2023-04-06 10:26         ` Greg KH
2023-04-06 10:58         ` Damien Le Moal
2023-04-06 10:58           ` Damien Le Moal
2023-04-06 11:18           ` Greg KH
2023-04-06 11:18             ` Greg KH
2023-04-06 11:23             ` Damien Le Moal
2023-04-06 11:23               ` Damien Le Moal
2023-04-06  9:59 ` Greg KH [this message]
2023-04-06  9:59   ` [PATCH 1/3] kobject: introduce kobject_is_added() Greg KH

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=2023040628-cocoa-lizard-9941@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=frank.li@vivo.com \
    --cc=huyue2@coolpad.com \
    --cc=jth@kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naohiro.aota@wdc.com \
    --cc=rafael@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 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.