From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>,
"haris.iqbal@ionos.com" <haris.iqbal@ionos.com>,
"jinpu.wang@ionos.com" <jinpu.wang@ionos.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Cc: "jgg@ziepe.ca" <jgg@ziepe.ca>,
"leon@kernel.org" <leon@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] RDMA/rtrs: Don't call kobject_del for srv_path->kobj
Date: Thu, 2 Feb 2023 16:20:57 +0800 [thread overview]
Message-ID: <3e3fd166-6a71-cec8-7d85-6d6b2515d7f6@linux.dev> (raw)
In-Reply-To: <42e231f5-63bb-e145-ce80-d9651a9afee1@fujitsu.com>
On 2/2/23 15:59, lizhijian@fujitsu.com wrote:
> 6af4609c18b3 seems make senses, so i don't want to revert it entirely if possible.
>
> I have a update for this path like below, i am no longer get problem with this new update.
>
> index c76ba29da1e2..5adba0f754b6 100644
> --- a/drivers/infiniband/ulp/rtrs/rtrs-srv-sysfs.c
> +++ b/drivers/infiniband/ulp/rtrs/rtrs-srv-sysfs.c
> @@ -312,9 +312,8 @@ void rtrs_srv_destroy_path_files(struct rtrs_srv_path *srv_path)
>
> if (srv_path->kobj.state_in_sysfs) {
> sysfs_remove_group(&srv_path->kobj, &rtrs_srv_path_attr_group);
> - kobject_del(&srv_path->kobj);
> kobject_put(&srv_path->kobj);
> + rtrs_srv_destroy_once_sysfs_root_folders(srv_path);
> }
>
> - rtrs_srv_destroy_once_sysfs_root_folders(srv_path);
> }
Hmm, I overlooked the kobject hierarchy 😅.
err = kobject_init_and_add(&srv_path->kobj, &ktype,
srv->kobj_paths,
"%s", str);
Pls send a formal patch, and feel free to add my Acked-by.
Thanks,
Guoqing
prev parent reply other threads:[~2023-02-02 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 14:30 [PATCH RFC] RDMA/rtrs: Don't call kobject_del for srv_path->kobj Li Zhijian
2023-02-02 1:41 ` Guoqing Jiang
2023-02-02 3:42 ` lizhijian
2023-02-02 4:09 ` Guoqing Jiang
2023-02-02 7:25 ` lizhijian
2023-02-02 7:59 ` lizhijian
2023-02-02 8:20 ` Guoqing Jiang [this message]
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=3e3fd166-6a71-cec8-7d85-6d6b2515d7f6@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=haris.iqbal@ionos.com \
--cc=jgg@ziepe.ca \
--cc=jinpu.wang@ionos.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.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