Received: by 2002:ac8:156:0:b0:3e0:cd10:60c8 with SMTP id f22csp2350094qtg; Wed, 22 Mar 2023 22:24:22 -0700 (PDT) X-Google-Smtp-Source: AK7set+VhUXKQ6rMDfPAYzVzgtZsOGGEPVbsAE1knHEOlNIiA4jST6ZjXHOioJQd1JUuoRv1htdF X-Received: by 2002:a17:902:f691:b0:1a1:be45:9857 with SMTP id l17-20020a170902f69100b001a1be459857mr6521346plg.1.1679549062604; Wed, 22 Mar 2023 22:24:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679549062; cv=none; d=google.com; s=arc-20160816; b=CR05L/YzggCWnvOIWfFSlvog2nTzM2xnne1hwnxQOovNPqEFO4Zd9/LiN0s7uqhBdZ VxF8gHxWpFEmDDGGKowOEH6nVqZWeKka6HFSav/gVyrrJ2k+XxYRX0fpDJgEba99GR9Z Vvz6/utaDCDPiMdz6F7oysJ3Z7H7ThSxS3plhSGFPf9MWD5xx6Zpg4SGoYy4ISPIq2Pv XPsi4t8a6e+TqAyD00JBFSY/B4FPeO8GAT7AOuHzTalNLI8KgpvaX+SUpIepmMc9ZYby hjgC+KD/uvflALD0sfHaTOl607QPdmEaLPWhCGkKQEfQZoa0HKQQPvbTy6pU3AKYZuHT y6Ag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=HoUzTMO8R5MhPq7S8OoMssryl9/6eR6zluDti49MEro=; b=ClngYxezMD8eqKJld/vfRZrXd2Wr7dYAJT2fMcn3I2xX0FeyTJe6OwRX9/YdRJKxO+ 2CkFxSqxYqNsQi/FSCud6gCfK6Us/mxURdscTUXoVg+8BsiMi0PQh3PVdS4760/AsF8q 3aFE8Gx7K2e4srp3nz9gLNcFIMm2r6GNHFHjwoSRyop5PsHDXVvB87SVUUrvNiSYPQr0 F3R1U+gS4AaqSQF/VCaqLoJMdqDAmO7a4yf8jYNhhNSBfJNm7X4VBSEMW0t0pVzGc26D IpZKSC7bXoQUN0GsnTvvZTpQz0jQlKuDVOpdBO4XwI/q6APB38trmau6P3Mx++9oc9yl exgA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=eDNhgma4; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d17-20020a170902ced100b001a18ec2d863si11464491plg.112.2023.03.22.22.24.10; Wed, 22 Mar 2023 22:24:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=eDNhgma4; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229917AbjCWFRz (ORCPT + 99 others); Thu, 23 Mar 2023 01:17:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44258 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230219AbjCWFRk (ORCPT ); Thu, 23 Mar 2023 01:17:40 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4D20F1F5C4 for ; Wed, 22 Mar 2023 22:16:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1679548612; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=HoUzTMO8R5MhPq7S8OoMssryl9/6eR6zluDti49MEro=; b=eDNhgma4RHwHo38UjyW4mFPa+ytR2DlR2DQhp7HfmCF63ds7b2521j6UMry4gpKdrYGsw1 SlsDJDZFruvM7qvS6B8FN3jcC/qtU5Q7V2gFWDfBZbHbwsCZVRfCOIxUIGLEseQpGVCLv1 THLYBYqEBQa0Q9tXhdictkx96Sdkv+Q= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-179-KY9zo7YzPqyCZhglvOgcqw-1; Thu, 23 Mar 2023 01:16:43 -0400 X-MC-Unique: KY9zo7YzPqyCZhglvOgcqw-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 362258828C2; Thu, 23 Mar 2023 05:16:41 +0000 (UTC) Received: from ovpn-8-16.pek2.redhat.com (ovpn-8-16.pek2.redhat.com [10.72.8.16]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6D3854021B1; Thu, 23 Mar 2023 05:16:24 +0000 (UTC) Date: Thu, 23 Mar 2023 13:16:20 +0800 From: Ming Lei To: Yangtao Li Cc: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com, xiang@kernel.org, chao@kernel.org, huyue2@coolpad.com, jefflexu@linux.alibaba.com, jaegeuk@kernel.org, trond.myklebust@hammerspace.com, anna@kernel.org, konishi.ryusuke@gmail.com, mark@fasheh.com, jlbec@evilplan.org, joseph.qi@linux.alibaba.com, richard@nod.at, djwong@kernel.org, damien.lemoal@opensource.wdc.com, naohiro.aota@wdc.com, jth@kernel.org, gregkh@linuxfoundation.org, rafael@kernel.org, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org, linux-erofs@lists.ozlabs.org, linux-f2fs-devel@lists.sourceforge.net, linux-nfs@vger.kernel.org, linux-nilfs@vger.kernel.org, ocfs2-devel@oss.oracle.com, linux-mtd@lists.infradead.org, linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, ming.lei@redhat.com Subject: Re: [PATCH v3 01/10] kobject: introduce kobject_del_and_put() Message-ID: References: <20230322165830.55071-1-frank.li@vivo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230322165830.55071-1-frank.li@vivo.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.10 X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 23, 2023 at 12:58:30AM +0800, Yangtao Li wrote: > There are plenty of using kobject_del() and kobject_put() together > in the kernel tree. This patch wraps these two calls in a single helper. > > Signed-off-by: Yangtao Li > --- > v3: > -convert to inline helper > v2: > -add kobject_del_and_put() users > include/linux/kobject.h | 13 +++++++++++++ > lib/kobject.c | 3 +-- > 2 files changed, 14 insertions(+), 2 deletions(-) > > diff --git a/include/linux/kobject.h b/include/linux/kobject.h > index bdab370a24f4..e21b7c22e355 100644 > --- a/include/linux/kobject.h > +++ b/include/linux/kobject.h > @@ -112,6 +112,19 @@ extern struct kobject * __must_check kobject_get_unless_zero( > struct kobject *kobj); > extern void kobject_put(struct kobject *kobj); > > +/** > + * kobject_del_and_put() - Delete kobject. > + * @kobj: object. > + * > + * Unlink kobject from hierarchy and decrement the refcount. > + * If refcount is 0, call kobject_cleanup(). > + */ > +static inline void kobject_del_and_put(struct kobject *kobj) > +{ > + kobject_del(kobj); > + kobject_put(kobj); > +} 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. thanks, Ming