From: Yangtao Li via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: ming.lei@redhat.com
Cc: rafael@kernel.org, linux-mtd@lists.infradead.org,
naohiro.aota@wdc.com, linux-nilfs@vger.kernel.org,
richard@nod.at, damien.lemoal@opensource.wdc.com,
trond.myklebust@hammerspace.com, xiang@kernel.org,
frank.li@vivo.com, chao@kernel.org, josef@toxicpanda.com,
huyue2@coolpad.com, dsterba@suse.com, jefflexu@linux.alibaba.com,
jaegeuk@kernel.org, konishi.ryusuke@gmail.com,
linux-nfs@vger.kernel.org, clm@fb.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, ocfs2-devel@oss.oracle.com,
anna@kernel.org, linux-fsdevel@vger.kernel.org, jth@kernel.org,
linux-erofs@lists.ozlabs.org, linux-btrfs@vger.kernel.org
Subject: Re: [Ocfs2-devel] [PATCH v3 01/10] kobject: introduce kobject_del_and_put()
Date: Tue, 4 Apr 2023 21:30:37 +0800 [thread overview]
Message-ID: <20230404133037.66927-1-frank.li@vivo.com> (raw)
In-Reply-To: <ZBvgpBzEuFuyOD/c@ovpn-8-16.pek2.redhat.com>
> kobject_put() actually covers kobject removal automatically, which is
> single stage removal. So if you see the two called together, it is
> safe to kill kobject_del() directly.
If the reference count is not abnormal, kobject_put() does contain
what kobject_del() does.
Thx,
Yangtao
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
next prev parent reply other threads:[~2023-04-04 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 16:58 [Ocfs2-devel] [PATCH v3 01/10] kobject: introduce kobject_del_and_put() Yangtao Li via Ocfs2-devel
2023-03-22 23:31 ` Damien Le Moal via Ocfs2-devel
2023-03-23 5:16 ` Ming Lei via Ocfs2-devel
2023-04-04 13:30 ` Yangtao Li via Ocfs2-devel [this message]
2023-03-23 12:26 ` Greg KH via Ocfs2-devel
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=20230404133037.66927-1-frank.li@vivo.com \
--to=ocfs2-devel@oss.oracle.com \
--cc=anna@kernel.org \
--cc=chao@kernel.org \
--cc=clm@fb.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dsterba@suse.com \
--cc=frank.li@vivo.com \
--cc=gregkh@linuxfoundation.org \
--cc=huyue2@coolpad.com \
--cc=jaegeuk@kernel.org \
--cc=jefflexu@linux.alibaba.com \
--cc=josef@toxicpanda.com \
--cc=jth@kernel.org \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=naohiro.aota@wdc.com \
--cc=rafael@kernel.org \
--cc=richard@nod.at \
--cc=trond.myklebust@hammerspace.com \
--cc=xiang@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;
as well as URLs for NNTP newsgroup(s).